Graphics card driver has stopped responding and has recovered

[Suina]

I am running a GeForce 9500 GT on my Windows 7 64-bit machine. Everything was working perfectly until a few days ago when I had to forcefully restart my computer several times while trying to troubleshoot a problem with my monitor not receiving the signal. Changing the DVI cable fixed it instantly, so I assume it was just a faulty wire, but ever since I've been unable to run any graphic card taxing application properly. When I try the screen flashes, the window gets garbled up and I get an error message saying that my driver has stopped responding and recovered. The program works "normally" afterwards except that the whole process repeats itself at every loading screen, scene change etc.

I have tried reinstalling the driver and followed the instruction here "Display driver stopped responding and has recovered" error in Windows 7 or Windows Vista (though only method one really applied and caused a blue screen).

Any advice would be greatly appreciated.

 

[archer]

Hi Suina, Welcome to Seven forums.

As per your post you just changed the cable, right? While changing the cable, any hardware might have be disloacted (RAM, or power cables). First thing I will suggest to you is to reseat the RAM sticks (Also, please update your system specs). Check for any loose cables and plug them back.

Clean out dust out of the CPU and cabinet. After all this if the issue is not resolved, then we can check the drivers.

Get the latest drivers for your card and also download DriverSweeper.
Uninstall the drivers, run DriverSweeper to remove the left overs of the drivers. Do a clean install of the drivers. Reboot the PC and then check.

Keep us posted.

 

[madcratebuilder]

The most important thing is run the DriverSweeper listed above. I would run it twice with a reboot in between, then install the latest driver for the card.

These errors can be caused by overclocking the gpu also.

 

[Dorothydix]

I have the exact same problem using latest drivers updated yesterday. GTX660. The problem seemed to resolve itself once I did this but today it has returned. I've run Malwarebytes and antivirus scans but nothing related to this appeared. A few day ago,according to the logs, it was occurring every hour,on the hour which leads me to believe it was viral or spyware but not the case. I have tried several "fix once and for all" suggestions online but none of them have resolved it. This has been an ongoing problem for years and no end of reseating ram or blowing out dust etc. will fix it.

 

[system2146]

I have the exact same problem using latest drivers updated yesterday. GTX660. The problem seemed to resolve itself once I did this but today it has returned. I've run Malwarebytes and antivirus scans but nothing related to this appeared. A few day ago,according to the logs, it was occurring every hour,on the hour which leads me to believe it was viral or spyware but not the case. I have tried several "fix once and for all" suggestions online but none of them have resolved it. This has been an ongoing problem for years and no end of reseating ram or blowing out dust etc. will fix it.

Hey Dorothydix,

I was having what the OP posted with my GTX 590, I tryed older drivers, almost 2 years old from today and checked to see if my card had been overclocked with Asus GPU Tweak, but they were all at default clock speeds.

So the last thing I did was reseated the graphics card, blew out any dust that might have been in the PCIE slot and wiped clean the graphics cards pcie connector (the long gold pcie x16 insert that goes into the motherboard)

So far i've ran benchmarks like Heaven Benchmark and FurMark graphics card stressing tools and playing games and I haven't had 1 problem so far, about 12 hours error free. **Try the latest Nvidia drivers to if you haven't already**

(also I didn't need to re-seat my RAM but so far so good, I am thinking it was dust and or a re-seat needed for my graphics card)

Just thought I would quote ya but you posted this over 192 days ago so good luck if you don't read this.

Regards,

Sean