Error: Display driver stopped responding and has recovered. Display driver NVIDIA Windows Kernel Mode Driver, Version 275.36 stopped responding and has successfully recovered.
Our graphics department was just recently upgraded to Windows 7 x64 machines. These are Quad Core 8 GB Intel boxes. The video cards are brand new NVIDIA Quadro 2000. The user stated that the error message happens frequently through out the day and randomly when completing different tasks.
Display driver nvlddmkm stopped responding and was recovered.
Display driver atikmdag stopped responding and was recovered.
Display driver xxxxxxxx stopped responding and was recovered.
Blue Screen Of Death – nvlddmkm.sys
Blue Screen Of Death – stikmdag.sys
Blue Screen Of Death – xxxxxxxx.sys
This is a post from an NVIDIA forum moderator jimbonbon.
…this is not an nVidia issue. It is not an ATI issue either. These errors are triggered by a Windows service called 'Timeout Detection and Recovery' (TDR). You will only see this error on Windows Vista and Windows 7, as TDR is a feature of the new WDDM driver model (implemented first in Windows Vista). TDR is supposed to be there to help stop BSOD's by resetting the GPU and/or driver when there is an issue. If the problem happens multiple times in a row, a BSOD can occur.
Common issues that can cause a TDR:
- Incorrect memory timings or voltages
- Insufficient/problematic PSU
- Corrupt driver install
- Unstable overclocks (GPU or CPU)
- Incorrect MB voltages (generally NB/SB)
- Faulty graphics card
- The issue can potentially be caused by a badly written driver or piece of software, but this is an unlikely cause in most cases.
- Driver conflicts
- Another possibility that people tend not to like to hear, is that you are simply asking too much of your graphics card. What I mean by this, is that if you have your settings too high and the graphics card struggles and falls to very low FPS, then something graphically complex occurs, it could trigger a TDR.
I checked all of the above in this situation and was still unsuccessful.
User was still having this issue. I have since replaced the motherboard and everything is work perfectly now.
: If you are still receiving this error message go to this link and try some of the other troubleshooting techniques listed.