Display driver not responding...

[jawsykilla]

Hi,

Recently I have noticed that when playing games my screen will either go black and quit to desktop and I get a message saying "Display driver stopped responding and has recovered", my game then quits. It has happened in BF3, Skyrim, Saints Row 3 and Minecraft.

My specs...

AMD Phenom II X6 1090t @ 3.2GHz (was 3.6 but put back to stock to rule out)
Asus Sabertooth 990FX
8GB Corsair Vengeance 1866MHz @ 1600MHz (Underclocked to rule out)
MSI Twin FrozR III 6950 2GB @ reference speeds
Crucial M4 128GB
Asus Axe Square Gold CPU Cooler
Antec 1100
CoolerMaster GX750

Windows 7 Professional (64-Bit)
Catalyst 12.3

At first I thought this could be due to overheating so I installed HWMonitor and the highest logged temperature was 61 C. Not hot enough for my card to be failing due to heat. I don't think my PSU is at fault as 750W is definitely high enough for my system specs and using HWMonitor all of my voltages are stable when gaming or otherwise. My CPU gets to about 42 C on max load so that isn't overheating.

Next I thought it was a driver issue so I have upgraded from the ones supplied with my video card CD to the latest, which at the time was 12.3, and I still have issues. I then updated to 12.4 and the same thing again. Win 7 is set for display to never go to sleep and I have changed the registry value per the microsoft article for GPU timeout.

The problem is very intermittent, sometimes I can be gaming for hours and other times it does it 10 minutes in. It seems like a software issue but I don't know where to start.

Has anyone experienced this and/or resolved the issue? Any help would be highly appreciated

Thanks,
Jordan

 

[Gregster]

I did experience this on a 560TI and it was the exact same symptoms as what you are getting. I had several things to try which helped but never sorted it.

The fix in the end though was a voltage boost. Try adding a little more volts with MSI Afterburner. If that does not fix it, try a little more. If still no good, I would be inclined to think something else is wrong.

Hope this helps.

 

[andicole0]

I've seen this quite a bit with nVidia drivers and there are lots of solutions, nVidia seem to have accepted there is a driver issue.

I suspect a look at the ATI forums would reveal the same sort of issue.

Andi.

BTW have a look at the signature FAQ before you get a warning from a Don.

 

[Gregster]

I've seen this quite a bit with nVidia drivers and there are lots of solutions, nVidia seem to have accepted there is a driver issue.

I suspect a look at the ATI forums would reveal the same sort of issue.

Andi.

BTW have a look at the signature FAQ before you get a warning from a Don.

After all my researching, I found it to be the OC non reference cards that were the problem from NVIDIA. I tried many different drivers and probably tried all that had ever been released for my card.

My symptoms were the same as the OP. Fine for a couple of months and then just started happening. Maybe some vendors of AMD are sending cards out right on the edge, so a voltage increase will help steady it.

TDR issues do effect both cards but do tend to mainly sit on NVIDIA's side.

 

[Hagar]

I have experienced this message but it was on a totally different scale of computer.

Intel E3400 with 2GB DDR2, this is a work desktop and used shared ram on the motherboard graphics.

No messages with windows XP although it started when machines were upgraded to windows 7.

Possibly poor win 7 drivers, it has been resolved by using an NV300 graphics card to replace the onboard.

Symptoms were usually with having several engineering applications running and scrolling through IE or large word docs. So probably low free memory availability.

 

[jawsykilla]

Thanks for the info. I'll try bumping up the voltage in CCC tonight and see if I can get it to fail, if not we may be on to a winner. Seems ridiculous that I have to mess with the default settings to get a stable card. *waves fist*

 

[Defiance_co]

Had that error with both flavours of gpu's

Each time it was purely driver related

So far it's been 50/50 for both the green and red side hehe

Try going back a few drivers

Rem : If it's not broke don't fix it