Account closed as requested
Partial workaround for Bugcheck 0x116, nvlddmkm.sys, VIDEO_TDR_ERROR
Partial workaround for Bugcheck code: 0x116 in module nvlddmkm.sys, VIDEO_TDR_ERROR
As many other people, I too faced this problem after upgrading my desktop system to Windows 10. Did some research and testing, now I'd like to share my knowledge.
In general, according to the web resources the problem is bound mostly to GeForce cards utilized under Windows 10 and manifests itself under two completely different conditions - under heavy load esp. playing games, or under lightweight or no load, for example web browsing. Fortunately I have no experience with the first case, my system is rock stable under load (FarCry 2, Stalker Clear Sky). On the other hand, it sometimes restarted itself without an evident cause, mostly not being used at all.
At this point I started experimenting, here are my observations.
The problem IS hardware-dependent. My notebook equipped with GeForce adapter too does not exhibit this behavior.
The problem IS OS-dependent. Tested W7 and W10 using the same W7 drivers, with completely different results.
The problem IS NOT dependent on graphic driver version number. Tested many versions of drivers, with consistent results.
Furthermore, I identified two conditions which may initiate the problem: while my computer goes into sleep state or while it finishes time-consuming operation - for example, copying ~120GB file in FreeCommander. Both conditions are related to the power saving mechanisms of PCs.
Finally I discover all settings needed to make my system as stable as it used to be for years while using Windows 7. Here they are.
Power Options - Plan:
- set Put the computer to sleep to Never
Power Options - Choose what the power button does:
- uncheck Show Sleep in Power menu
Power Options - Advanced Settings:
- set PCI Express Link State PM to Disabled
- set USB selective suspend to Disabled
(for Classic Shell installed only)
Classic Start Menu - Settings:
- fill Shutdown Menu Items with options "switch_user;logoff;lock;restart;hibernate" (excluding Sleep)
There is no need to disable power saving for processor, the problem is bound to PCI Express bus and devices. Also hibernation can be used without problems.
Tested on my desktop only, I cannot guarantee success for other systems, but you may give it a try. This workaround is suboptimal for notebooks too, I am aware of it. But I think a stable system is still more important than longer battery life.
In my opinion, the problem isn't caused by neither bad graphic driver nor faulty hardware, it lays in interaction between hardware (motherboard + graphic card), OS and drivers while servicing power savings. It only manifests itself in graphic driver nvlddmkm.sys (and only under Windows 10), the same driver itself works ok in older OS. To find a culprit, we have to look at the way how the new OS manages entering/exiting power states on some motherboards and graphic cards. Resolving it is job for Microsoft guys i'm afraid.
Conclusion: If you encounter 0x116 errors while your computer is/becomes lazy, at first you may try to completely disable all power saving options instead of fiddling with drivers.
Last edited by valihrach; 15 Dec 2015 at 15:12.