Display driver NVIDIA Windows Kernel Mode Driver, Version XXX.XX stopped responding and has successfully recovered

This is for my Sager NP8690 and the gaming forum is no help, so I am posting it for clevo folk and hope no one moves it and someone can help.

I've not found a good way to remedy this error message, Display driver NVIDIA Windows Kernel Mode Driver, Version XXX.XX stopped responding and has successfully recovered, or what causes it.

Cupid shows that my temps are <60C when this message occurs. It happens in Diablo3, SC2, Dead Island, probably more that I can't think of now. Skyrim, Portal 1&2, Prototype and L4D run fine at <80C.

I've changed my driver to the newest and the oldest as well as a few middle ones. I don't have a driver scrubber, but followed a complete Nvida removal from BradleyW.

I've tested my ram and it's fine.

My machine is a Sager NP8690
Windows 7 home Premium 64 bit
8G ram 1333
Intel quad core I7 Q720 at 1600MHz
Nvida 285M
video driver (tried them all that are certified for the 285M)

I don't believe that my GPU is a brick because it plays some games real well. Any suggestions?

 

why not mention what else you tried as well > http://forum.notebookreview.com/gam...ed-responding-has-successfully-recovered.html like driver sweeper.

 

There are dozens of threads on various forums about his problem and not once does any driver change fix the problem regardless of how clean of an install it is. I've manually removed all traces of the video driver and used Driver Sweeper.

It is not a ram problem (ran ram test on 4 GB) Increased to 8 GB (reran mem test on both sticks)

Not a fan problem (clean fans religiously)

Not a temp problem (used Cupid to test temps, no correlation was found)

 

With all that you have tried, it seems your only 2 options now may be either:

a) complete wipe and re-installation of the OS and drivers.

b) if the above fails to resolve the issues, your GPU may be failing.

 

Have you tried switching from adaptive to performace mode?

Have you tried switching physx from automatic to the GPU (don't know why but read somewhere that it solved the issue for some)?

 

so why in your original post on the gaming thread and here have you mentioned changing your drivers so many times if you already read it elsewhere that its not a driver problem.
for the last 5 years with that error message its been fixed for numerous members by changing their drivers.

as mentioned reinstall your OS and be done with it.

 

Good point, I haven't ran into this issue since I set Physx to my GTX-580M instead of "automatic".
(Also, I have "adaptive" set everywhere instead of performance mode and don't run into this issue, so perhaps the power management mode settings doesn't have an impact on this issue).

 

I do change the power management to performance mode and that helped with Dead Space games, but those games just didn't work well. They never lead to the "stopped and recovered" error message.

I've just changed my Physx to my 285M and will see how that works tonight. Thanks for the suggestion

Reinstalling my OS is not possible as I have too many programs that only allow you to install them twice (mathmatic, chemdraw, and others through the university) then you have to rebuy them. I created an image once I had everything loaded, but I didn't understand that a backup was the same thing and so I only have a recent time point.

 

I am having this problem in my desktop pc (hd 6970, and i5 Sandy Bridge). OS reinstallation hasn't solved the issue. It could be a faulty cpu/gpu as suggested here.

Sent from my GT-N7000 using Tapatalk 2

 

Go on LaptopVideo2Go and find a driver there, should fix it

 

Thanks for the suggestion, changed the Physx to my GPU and tried a little diablo 3. It crashed within 10 min with the same error message. It's baffling how I can play Skyrim all day and Diablo 3 crashes in 10 minutes. Maybe XoticPC service can help, but that seems unlikely as at least one of their employs had the same problem. He fixed it by going from windows 7 64 bit to windows 7 32 bit, but that didn't work for others on the forum.