Folding Forum

I haven't had a BSOD/GSOD on Build 25140 while crunching Folding@Home, for several days.
I think the 516.40 driver has fixed the problem!

I'm currently doing testing of the new 516.40 driver, on the new Win11 Insider Dev Channel build 25140. So far, results seem promising.

Okay. Just repro'd the problem in Win11 Insider Beta channel, build 22621.160. Dang. Now I'll switch to the Release partition to test there.

So, while I can easily repro the issue on Win11 Insider Dev Channel, I'm not easily able to repro the issue on Win11 Insider Beta Channel over the past 2 days. So, the issue may be currently restricted to Dev Channel.

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 co...

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

Same problem with overclocks removed. Reverting to 511.79.

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.

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

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

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

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

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...

Same issue here.

Hi Jimbo, I understand the staff is at critical load, and now isn't the right time to make changes you deem trivial. However, as someone who recently re-joined F@h, I saw an opportunity for improvement, and put forth effort to learn, document, and politely request. So, it is what it is, and I hope w...