This began on day one of a clean install of Windows 10. It only occurs when Folding@home is running and I launch another program. It never happens when Folding@home is paused or not running. No program, game, or application causes these errors on the system by itself, F@H must always be running for them to occur.
If the machine is folding on the GPU and any 3D accelerated program is started, they frequently cause a one-time "Display driver nvlddmkm stopped responding and has successfully recovered." error to occur. It can be as simple as opening a static JPEG in the old photo viewer (occurs 4 of 5 times I view any image), and less frequently when I launch a video in VLC or open Chrome. If I open GPU utilities such as Precision X, I will sometimes receive a chain of these errors until I close the program or kill F@H. Rarely the same programs run without a single occurrence.
Simple "Display driver nvlddmkm stopped responding and has successfully recovered" error in the event logs, no details given. I wonder if it is as simple as adjusting a timeout window in the drivers, but so far I've not had any luck.
7.4.4
Windows 10
NVIDIA Titan Black (358.50)
System is stock, no OCing.
I've yet to find any instability with the system using various utilities. I went as far as underclocking the GPU and even raised its voltage, but that did not change the frequency of these driver reset errors. I can therefore only conclude there is some kind of NVIDIA driver/Windows 10/F@H specific problem that is causing this. It reminds me a lot of the Windows Vista & fledgling GPU folding days all over again, just without the actual BSoDs this time.
![Mr. Green :mrgreen:](./images/smilies/icon_mrgreen.gif)