• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Display Driver stopped responding and has recovered crashes

A

Andy T

Senior member
I recently started to experience the following phenomenon:
While doing general purpose computing, my screen would go black for a few seconds, then the video would return along with the following message:
"The video driver has stopped responding and has recovered..." This keeps on happening every 5-10 minutes along with a hard crash.
Strangely enough, I am able to play Crysis 2 for extended periods of time with no issue.
My research didn't lead me to any specific cause/solution. What are some things I can try?

Thanks!

My system spec:
cpu: I5-2500K @ stock speed
mobo: Asus P8Z68 - V Pro - Bios is not latest
Video: eVGA Gforce GTX 560Ti @ retail clock. I am running latest Nvidia driver
Ram: Gskill 8GB
PSU: XFX 650W
I am using intel's SRT technology with Crucial C300 SSD drive set in Enhanced mode. Therefore I also have RAID turned on in BIOS.
OS: Windows 7 64 bit with SP 1, N edition
All temperatures are normal (GPU @ ~40 C in idle, CPU @ 32 C in idle, Mobo @ 30C in idle)
 
My last GTX 460 got the same problem with tons of artifacting and instability. RMAed and the replacement got no issues.
 
Update to the latest Display Driver for your card, and if that doesn't help try some older ones. It might be worth physically pulling out and re-seating the card to start with. Several people including me had similar issues because the card had slipped out a bit.
 
Reseating of the card didin't do anything. However, rolling back to an older version of the drivers appears to have fixed the problem. I had no issues last night (knock on wood).
 
Andy T said:
Reseating of the card didin't do anything. However, rolling back to an older version of the drivers appears to have fixed the problem. I had no issues last night (knock on wood).
Click to expand...

If the issue seems to be resolved, I suppose we can chalk it up to a bad driver version. What was the version number of the drivers that were giving you problems?
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top