I too have been having the problems with the accursed "Display Driver stopped responding and has recovered
" / "Display Driver NVIDIA Windows Kernal Mode Driver, version 311.06 stopped responding and has successfully recovered
" error messages. Also BSODs which look like they're in a similar vein.
I don't play games on my machine but I will need to run Premier Pro CS6 on it. Over the last week or so I have followed almost every suggestion I could find in this thread and elsewhere for solving this immensely frustrating issue, and, although I've managed to reduce the frequency of the problem, I have so far been unable to eliminate it. Frankly I'm at my wit's end - so I'm flinging myself at the mercy of this forum in the hope of a solution.
My GPU is an NVIDIA GeForce GTX 285
, my PSU is a brand new Corsair CX750
(i.e. 750 watt) and my OS is Windows 7 64-bit. There's more details about my rig under "System Specs" in my profile.
So far in my attempts to resolve this infuriating error I have tried the following...
I was able to run Memtest v4.0 for about two hours with high CPU temperatures (I monitor them with CoreTemp) and no errors were detected in Memtest until a BSOD shut the computer down. The period that elapsed before the BSOD was about normal - in other words the stressing of the CPU and RAM did not seem to hasten the time of failure.
I was able to run Furmark v1.10.6 for an hour or so - with GPU temperatures of around 90 degrees C for most of that time - before finally getting the error message: "The NVIDIA Open GL driver detected a problem with the display driver and is unable to continue. The application must close. Error code: 3"
Following Lucius2571's suggestion I have removed my graphics card, cleaned up the contacts, and re-seated it in a different slot.
Following Cyberius' sugestion, I've also checked my GPU's innards, but I found it to be surprisingly free of dust and fluff.
I've tried using the latest Beta drivers
from NVIDIA for my GTX 285 but that didn't help, so instead I used Driver Sweeper (well actually it's successor Driver Fusion) to uninstall those drivers and in their place I installed an old driver - version 285.62 from October 2011. Many folk have mentioned this helped and I think it helped me too. The errors and BSODs seemed to occur less after clean installing the 285.62 drivers, but occur they sadly still did.
I've gone into - Control Panel > System and Security > Power Options
- and selected "High Performance".
I've gone into - NVIDIA Control Panel > 3D Settings > Power Management Mode
- and set it to "Prefer Maximum Performance"
I think all of these last three changes improved things somewhat - when I first started up my machine I could go for an hour or so browsing the internet (no gaming) without any problems before eventually getting a "Display Driver stopped responding..." message. After that they would become more frequent, culminating in a BSOD.
Eventually, frustrated by all this, I made a change that I really didn't want to. I switched off the lovely glassy translucent "Aero" themes by going into - Control Panel > System and Security > Advanced System Settings (aka System Properties) > Advanced > Performance: Settings
- and selecting "Adjust for best performance".
Gosh what an ugly Windows 2000 style display this has left me with! - but it has also given me the best improvement so far in eliminating "Display Driver stopped responding..." errors and BSODs. When carring out regular computer functions such as web browsing or running Outlook, this change appears to have almost (but not completely) eliminated the problem. I even managed to run Memtest right through the night without it detecting any errors.
However, the system still crashes after about 4 hours of doing humdrum activities like web browsing and writing emails or documents. If I run Furmark the system scrashes sooner. Now, though, I get a slightly different error... "The NVIDIA Open GL driver detected a problem with the display driver and is unable to continue. The application must close. Error code: 7"
... So it seems I've progressed (if that's the right word) from Furmark giving me "Error code 3
" to it giving me "Error code 7
" - whatever those codes mean. Does anyone know?
Incidentally, a few days ago I found a rather handy summary of many of the trouble shooting suggestions mentioned earlier in this thread. It came too late for me, but it might be useful to others: Fixing the Nvlddmkm Error (Display driver has stopped responding)
I think that out of the 9 techniques suggested in that summary the only thing I haven't already tried is making changes to the registry. Before I resort to that scarey option, are there any other tricks I haven't tried yet that might help the situation?
Finally, if I do resort to the Registry trick and find it doesn't work, should I just conclude it's time to ditch my NVIDIA GeForce GTX 285 ? I'm on a pretty tight budget here at the moment so very reluctant to if I can avoid it. I note however that it's a model of GPU that pre-dates the launch of my OS, Windows 7. I wonder if that's somehow causing issues. Any thoughts on that?
As I mentioned I'm not a gamer, but I do need to use my rig for HD video editing, so it's essential I debug this pain-in-the-bum error for that. Also I'd love to be able to use Aero themes again - they're just so pretty... so very, very pretty...
Help me SevenForum Obi Wans. You're my only hope...
(SF Diagnostic Tool log attached)