BSODs on 512.15+ drivers

[JacobKlein]

I am getting Blue Screen Of Death (BSOD) 0x000000D1, on multiple PCs, when crunching Folding@Home, on NVIDIA drivers 512.15+
My workaround is to install 511.79, which does not give a BSOD.

Is anybody else having this same problem?

Note 1:
I manually overclock and test my GPUs, but this BSOD problem persists even when overclocks are removed.
I tested both 512.15 and 512.59, but both have the problem.

Note 2:
I believe I also repro'd the problem crunching PrimeGrid Genefer on PC 1, so it seems these drivers might be broken for GPU crunching in general, instead of being broken only for Folding@Home.

PC 1:
Windows 11
GPU 1: RTX 2080
GPU 2: GTX 1660 Super
CPU: AMD Ryzen 9 3950X
RAM: 128 GB

PC 2:
Windows 10
GPU 1: GTX 980 Ti
GPU 2: GTX 980
GPU 3: GTX 970
CPU: Intel i7-5960X
RAM: 64 GB

Regards,
Jacob Klein

[toTOW]

Do you have some additional information in Windows Event Viewer before or after the BSOD ?

I'm still using 511.79 on all m systems, but I might try to update to a newer version to check ...

[JacobKlein]

No additional information, but I've been saving the Memory.DMP files and passing them on to NVIDIA.
Can anyone reproduce this problem?

[JacobKlein]

My testing indicates that 512.77 may have fixed the 0x000000D1 BSOD problems that I was having.
I will continue to test.

[JacobKlein]

Well, now I'm getting 0x0000003D BSODs on driver 512.77. Will continue to test.

[Neil-B]

I run the latest versions of nvidia drivers and haven't been having any issues ... given lack of others seeing this issue I'd hazard a guess that it is an issue linked to a combination of software running that I'd peculiar to the way you configure your systems that is triggering these ... the variety of hardware you are having issues across feels like it isn't hardware related ... maybe even just a non fah software package tripping the systems when fah is loading them ... hope you track down the issue

[toTOW]

Bug Check 0xD1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

Last time I saw this on one of my machines, it was related to CPU overclocking being unstable ...

Bug Check 0x3D: INTERRUPT_EXCEPTION_NOT_HANDLED

I have never seen this one, but since it's still about interruptions, it's probably related to the original one ...

[JacobKlein]

So far, 512.95 seems to be a winner for Folding@Home work. I haven't had any 0x000000D1 or 0x0000003D blue screens, yet!

[JacobKlein]

512.95 just gave me 0x0000003D crunching Folding@Home while my GPUs were overclocked. Reported it to NVIDIA. Will retest with overclocks removed, and revert to 511.79 if necessary.

[JacobKlein]

Same problem with overclocks removed. Reverting to 511.79.

[toTOW]

512.95 seem fine on my systems, but an old laptop with 980M is showing more instabilities with some video playback applications when overclocked ...

But these are GPU driver resets, no BSOD ...

[Lazvon]

Running 512.77 on 5 systems (2x3080Ti, 2x3090, and a 3090Ti). No issues at all.

[JacobKlein]

Are those systems you're actively also using, like watching YouTube videos and browsing in browsers, while crunching?

[Lazvon]

If that was to me, one of them is, yes, the 3090Ti. The rest are just old primary systems that become folders.

[JacobKlein]

Looking at my notes:
BSOD "0x000000D1" affected 512.15 to 512.59, and happened on Win10 and Win11 Release builds, as well as Win11 Insider builds.
BSOD "0x0000003D" affected 512.77 to current, and I've reproduced it using Win11 Insider Dev / Beta / Release Preview builds.

I'll continue to test, for sure.

But so far I definitely have a repro on Win 11 Dev / Beta / Release Preview, while using Folding@Home, with GPUs not overclocked, and Afterburner uninstalled, and iCUE uninstalled. I'm going to try to get a repro while Sidebar Diagnostics is uninstalled, and if I do, then I'll switch to the Release partition to see if it repros there.

The issue is real.