DCS Crashes at "Waiting for pooled tasks - 1" Every time, reguardless of Aircraft/Map/Mission

[BJ55]

I see you're running 560.94, the latest decent driver for pre 50 series is 566.36, so if you want you can try it later. Just for curiosity, have you tried also previous chipset drivers?

Do you have another SSD in order to install DCS outside of C:?

Just for curiosity, can you upload the screenshots of cpu, memory and disk usage graphs from DCS start to ctd?

[sabreman]

So I have been able to 100% confirm it's a hardware issue. I ripped the SSD out of my computer and hooked it up to an old laptop through a seta>usb hookup, and after windows updated it's drivers (and a restart) DCS worked flawlessly. 

So now I at least know that it's neither the drive nor software. The hard part comes trying to figure out what component is actually bad. I did swap my two ram sticks around to see if that would do anything, but no dice, also made sure everything was connected well.

 

I've now switched to testing with OCCT (thanks DCS support for showing me this app exists!), so far I've hit all of the standard stability tests for like 5-10 minutes without any errors, so I'm gonna switch to running them all for at least an hour at a time to see what breaks. Anyone have any insights on how to troubleshoot mysterious hardware issues that only show up in very specific circumstances? I'm fairly certain it's not my GPU or CPU, and I've definitely heard of both power supplies and ram chips causing really hard to diagnose issues.....

 

Edit: 

As an small update, second memtest passed with zero errors overnight, so at this point I think I can confidently rule out ram. I'll still run all ram-related tests from occt to be safe though. 

Currently running the power supply test while at work, we'll see what happens.

Edited 20 hours ago by sabreman

[BJ55]

Previously you wrote "This computer with the same hardware, used to work flawlessly a few months back", that's why I've never thought about a HW issue, btw, I've had a similar behaviour in the past with a borked (Asus) BIOS update, worth checking. Best of luck!