4090 dpc watchdog violation BSOD
Posted: Fri Dec 27, 2024 3:51 pm
I usually process some work units for you as a soak test of new gaming/server hardware. Recently I had a computer come in with a 3070; getting an upgrade to a 4090. Client stated that there were some stability concerns so I started with a soak test using F@H older version - with the advanced control. 1x GPU slot + 7x CPU slots (8 core cpu). Which was ran for some hours, then the 4090 was added and it was ran some more with no issues. Folding was then paused (I pressed finish and waited for it to end) and some real world 3d application testing was completed. All without issues. Usually I remove F@H before delivering the finished systems, or simply reinstall the entire O/S in the case of servers.
Fast forward 4 days for the 4090 PC and the computer is reliably BSOD as soon as it logs in. Safe mode not impacted, normal mode with no GPU driver not impacted. Running 566.36, clean installed. Got the system back in and put old card back in, no stability problems. Then I start an RMA for the GPU before noticing the computer was using a lot of power for an idle system. Upon further investigation I've forgotten to remove F@H from the system . So typically I would still say sorry I think the GPU is faulty but something doesnt feel 'right' here.
No other software is triggering instability in my testing. Including other GPU compute tasks that are causing higher (GPU) power usage then F@H. Furmark ran for several hours without crashing or overheating. Power target was then increased to ensure we have headroom and no issues seen (500w power draw). MSI Kombustor ran for several hours with no errors or issues detected. BSOD observed is always DPC_Watchdog_Violation; basically as soon as the computer logs in, even when stone cold. Looking around on the forum other people report that this can be hardware or software issue.
Sadly I needed to get the system operational and delivered back to the client so I have not managed to collect information about potential that a specific work unit seems to trigger this but I felt you may find my experience useful.
Fast forward 4 days for the 4090 PC and the computer is reliably BSOD as soon as it logs in. Safe mode not impacted, normal mode with no GPU driver not impacted. Running 566.36, clean installed. Got the system back in and put old card back in, no stability problems. Then I start an RMA for the GPU before noticing the computer was using a lot of power for an idle system. Upon further investigation I've forgotten to remove F@H from the system . So typically I would still say sorry I think the GPU is faulty but something doesnt feel 'right' here.
No other software is triggering instability in my testing. Including other GPU compute tasks that are causing higher (GPU) power usage then F@H. Furmark ran for several hours without crashing or overheating. Power target was then increased to ensure we have headroom and no issues seen (500w power draw). MSI Kombustor ran for several hours with no errors or issues detected. BSOD observed is always DPC_Watchdog_Violation; basically as soon as the computer logs in, even when stone cold. Looking around on the forum other people report that this can be hardware or software issue.
Sadly I needed to get the system operational and delivered back to the client so I have not managed to collect information about potential that a specific work unit seems to trigger this but I felt you may find my experience useful.