Nvidia display driver has stopped responding and has recovered

KingPepe

Honorable
Jun 15, 2013
1
0
10,510
A couple days ago, my games (Saints Row/Skyim/Arma3) started to either crash to desktop with the message "display driver stopped responding and has recovered" or just black-screened and returned to the game with lag. After several attempts at fixing the problem, I've scanned my entire computer for malware and viruses, installed old, new and beta drivers for my GPU, and changed my Nvidia power management mode to "prefer maximum performance". None of these have produced any effect. I have a GeForce 660 GTX graphics card. The GPU's temperature was readout at 45 C. I would appreciate any help you can offer.
 

nocturnal7x

Distinguished
Dec 2, 2008
277
0
18,810
Ive been having this issue with borderlands 2 with 320.18 on a gtx 780. I can play planetside 2 for hours on end with no issues, but in borderlands 2 this issue happens completely randomly and often, could be in the first 5 min of playing or after an hour.
 

Gee1337

Honorable
Jun 16, 2013
36
0
10,530
I've sometimes had this problem with my AMD HD7700 and usually, I have found that this is down to a corrupted driver. Have you tried scrubbing the driver then reinstalling it cleanly?
 

PallindroneT3604

Honorable
Dec 12, 2012
80
0
10,660
I'd be suspect of your power supply. Unbuffered or inconsistent voltage (going either to your CPU/HDD(SSD)/RAM-------as well as your GPU can cause these anomalies. At idle, you might be getting good, strong voltage readings....but maybe under a load, the PS is flaking out. Just a guess. If you have another PS to try out and substitute, see if everything smooths out.
 

Kim Andersen

Honorable
Sep 14, 2013
2
0
10,510
To me it seem as if you have the same problem many has. There is a plethora of explanations and solutions. Too many boast that they have fixed it. However, as I have walked through a gazillion threads, I have come to the conclusion, that there might be a multitude of causes, and thus a multitude of "fixes".

Hence, I would recommend you follow my lead. If it is possible, hand the card in and get another one. Use the warranty, and cross your fingers.

I have used 320.08, 320.49 as well as 326.01 and all of them have been futile. Also I have tried some of the other jazzy tricks, and they do not work - again because I believe there is a multitude of reasons.
 

amarksman

Honorable
Aug 11, 2013
32
0
10,530


Try the solution I posted, using 314.22
 

Kim Andersen

Honorable
Sep 14, 2013
2
0
10,510


I definitely think that reverting to the aforementioned driver is the most promising answer. It has been mentioned in tonnes of forums although some also indicate problems with the option. As I got my card the 12th of September, I will want to hear from the sellers first. If not, I will mod an inf and use your solution. If I remember, I will also post my results :) Anyway, thank you for posting it :)