Display Driver Briefly Stops,during Hot Jobs

Running "folding@home" (medium)
Had display flash off and on twice in last 2 days.
Admin Event: Display driver nvlddmkm stopped responding and has successfully recovered.
Both cores running pushing max temp limits on CPU about 65c an GPU about 80c according to speccy.
So, the obvious action is to lower the ambient temp ( rid dust bunnies, etc) and run in light load when I am on doing stuff.
Questions: Anything significantly known about this driver? Maybe a PSU problem? Any folding tweaks to be
done? Can anyone verify my research results for max temps on CPU 68c and GPU 98c? Finally, when speccy temps change from yellow (orange) to red, is there any relation to actual hardware maximum?

Will appreciate any advice/comments to help me keep this machine folding@home for MG team 12072

 

Have a look at these 2 possible solutions.
http://www.instructables.com/id/How-to-Fix-the-Nvlddmkm-Error/
http://ccm.net/faq/6210-nvidia-nvlddmkm-sys-error-message

There are other scenarios that cause the nvlddmkm error.

 

Ty Eldon for the quick response. I think heat is the first thing to attack, so sat will be a day to open all and blow dusties bye bye.

 

There is also an issue I have run into with Windows 10. If the system does not receive a response in an allotted time (2 seconds) from the graphics driver, Windows will reset it.

Fixing this issue requires editing, or creating a registry key (DWORD 32bit, QWORD 64bit) which is not advisable unless you know what you are doing.

If you feel confident you can do it, this may solve your issue:

1). Press Win+R (Windows key and R key) at the same time. A Run dialog box will appear.
Type regedit in the run box then click OK button. Then the “Registry” Editor will open.


https://www.drivereasy.com/wp-content/uploads/2016/02/img_56d1514256cf9.png


2). Browse to and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers


https://www.drivereasy.com/wp-content/uploads/2016/02/img_56d15158994b0.png


3). On the Edit menu in the right pane, right-click on the blank place. Click New, and then select the following registry value from the drop-down menu specific to your version of Windows.


If your PC is running 32-bit operating system, follow these steps:


a. Select DWORD (32-bit) Value.


https://www.drivereasy.com/wp-content/uploads/2016/02/img_56d151767ad5b.png


b. Type TdrDelay as the Name and click Enter.


https://www.drivereasy.com/wp-content/uploads/2016/02/img_56d15185e69a6.png


c. Double-click TdrDelay and add “8” for the Value data and click OK.


https://www.drivereasy.com/wp-content/uploads/2016/02/img_56d151958257a.png


If your PC is running 64-bit operating system, follow steps below:


a. Select QWORD (64-bit) Value.


https://www.drivereasy.com/wp-content/uploads/2016/02/img_56d151bc4d971.png


b. Type TdrDelay as the Name and click Enter.


https://www.drivereasy.com/wp-content/uploads/2016/02/img_56d151caa9437.png


c. Double-click TdrDelay and add “8” for the Value data and click OK.


https://www.drivereasy.com/wp-content/uploads/2016/02/img_56d151d356250.png


4). Restart your PC for the changes to take effect.

After modifying the registry here, if a problem occurs and you are not sure how to restore the registry, you can delete the added TdrDelay Name and restart your PC.

 

Thx Mekanic, will try your solution next if I still get more fails. In meantime, trying a couple changes found in Eldon's link
http://www.instructables.com/id/How-to-Fix-the-Nvlddmkm-Error/
Changed theme from Aero to Windows Classic, and set Nvidia 3D PhysX control from Auto to GeForce GT 620

 

You're welcome.

I added the key to my registry, as my ATI driver was being reset randomly for no apparent reason. Repeatedly. Quite annoying when you're emulating a classic game, and trying to relax whilst doing it...

 

Also changed Power Options from Balanced to High Performance

 

Turning off TDR detection isn't the best way of curing the underlying problem, trouble is, the causes for those 0x116/0x117's are very tricky to pin down. The best troubleshooting resource for them that I've seen/used is at Sysnative.

 

I didn't turn it off. I just increased the amount of time to wait for a response. Such prevents Windows from resetting the adapter without cause.

 

Without cause. Really?

 

In my case, yes. Since increasing the time limit for a response by the graphics driver to the system, I have had absolutely no reset issues. A lack of patience on the part of Windows 10 was the culprit. With the increase in response time no matter what I'm doing from streaming video to emulating a classic game there are no more resets.