"Display driver AMD driver has stopped responding and has recovered" Help?

E

EYS

n00b
Joined
Dec 23, 2010
Messages
9
Well about a month ago I put together my first build and everything has been working great so far (Fast, plays all games I throw at it greatly) except the only problem is if I play a game it will randomly shut down maybe 15-30 mins into game play to a black screen and a few seconds later and my monitors will read "No DVI signal". And then I'll have to reboot my system. Although if I get to the task manager fast enough before it completely shuts down I can get to my desktop where it will read "display driver AMD driver has stopped responding and has recovered".

Sometimes it wont do it for a while, but other times it will do it often when I'm playing games. Although it has done it once when I was just browsing the Internet and right after it did it my computer went to the blue screen.

Here are the specs.

Monitors: ASUS VH242H Black 23.6" (3, I have an Eyefinity setup)

Case: COOLER MASTER HAF 932 BE

CPU: AMD Phenom II X6 1090T BE

CPU cooler: COOLER MASTER Hyper 212

GPU: GIGABYTE Radeon HD 6970

PSU: CORSAIR 650W

Motherboard: GIGABYTE GA-890FXA-UD5

RAM: G.SKILL Ripjaws Series CL7 4GB

SSD: Mushkin Enhanced Callisto Deluxe 2.5" 40GB SATA II MLC SSD

HDD: Western Digital Caviar Blue 320GB 7200 RPM

All the temperatures are fine so it's not overheating.

I've uninstalled drivers, I've installed/reinstalled the latest drivers even multiple times. (11.1)

I've Updated the BIOS on the motherboard.

I haven't overclocked anything yet.

It does it with just one monitor running too so its not eyefinity.

I don't know what to do, any ideas? Thanks a lot if you can.

*****UPDATE***** 3/10/11

Well I RMA'd it and yet the problem still occurs, Right now my BIO's are at optimal defaults and I've also tried it with optimal defaults with the RAM at it's native settings. I honestly have no clue what to do now. Any ideas? Thanks
 
Last edited:
This happens to my computer from time to time too. It never happened when I had drivers from about 6 months ago, even since it has happened. It's probably the drivers.
 
i get this when i try to run multiple instance of video file going driver issue most likely
but in my case monitor just flashes for few seconds and it fixes itself
your problem seems to be beyond driver issue i suggest rmaing too
 
since it's a 69xx series, unless your PSU is having issues, it's probably a bad card.

I would RMA

(On 58xx series, the driver not responding issue was fairly common, it's not on the 6xxx series and the symptoms you describe are definitely not normal even for the older 58xx series)
 
You have a bad card, probably the core is faulty. I get messages like that if I overclock the core too much. Get a new one.
 
Alright I'm gonna try some old versions of drivers first. But if that doesn't work out, I guess I'll rma it.

Thanks everyone though!
 
Well I RMA'd it and yet the problem still occurs, Right now my BIO's are at optimal defaults and I've also tried it with optimal defaults with the RAM at it's native settings. I honestly have no clue what to do now. Any ideas? Thanks
 
Can try reformatting your system and starting fresh. If no luck, it might possibly be the board at fault. It's not inconceivable you got a faulty card back from the RMA though, so keep that in mind.
 
I had the same problem. I changed PSU's, which I needed to do anyways and also tried different drivers on different windows installs. Ended up being the video card. I RMA'd my XFX 6950 back to them and they just received it today and I'll see what they say.
 
samuelmorris said:
Can try reformatting your system and starting fresh. If no luck, it might possibly be the board at fault. It's not inconceivable you got a faulty card back from the RMA though, so keep that in mind.
Click to expand...

Alright, I'll give that a try. And man, I hope I don't have to send another thing back, especially if its to the manufacturer haha
.
ratedm said:
I had the same problem. I changed PSU's, which I needed to do anyways and also tried different drivers on different windows installs. Ended up being the video card. I RMA'd my XFX 6950 back to them and they just received it today and I'll see what they say.
Click to expand...

Could it be my psu? I would think 650w is enough for my system, or maybe not?

Thanks guys.
 
It could be that the power supply is craping out on you since switching cards didn't help. I had all sorts of little problems with stability when I had my old Silverstone Strider. I tried switching out all of my hardware for testing, but the instability continued. I decided to try and see if a new PSU would help and bought a Strider Plus on sale and everything was stable again. Unfortunately, even high-quality power supplies can go bad.
 
Use a driver sweeper to clean out the driver. Then look for this file

atikmdag

Delete it

Reinstall your drivers
 
I had the exact same problem several months ago when I installed 10.9 if I remember right. That was with a 4850. Searched all thru Google and never found any real answers. Finally on a pure guess, I uninstalled CCC and that did the trick. Im now running a 5870 and if I install CCC, I get the same crap. So whenever I install a new driver, I immediately uninstall CCC and everything works fine. I dont know why or how but in my case at least, regardless of which driver I used, no matter how many times I swept drivers and regardless of which card I use, if CCC is installed, I get random crashes and the "driver has stopped responding" crap.

Give it a try. Hopefully this fixes your problem too.
 
Update to the latest drivers. If everything is stock and it's still not working properly, it might be best to send the card back.

Could it be my psu? I would think 650w is enough for my system, or maybe not?

Thanks guys.
Click to expand...
It should be fine. AMD recommends a 550W PSU minimum for a 6970, though if your PSU is really old or it is from a crappy, no-name manufacturer, then it could be that it has trouble supplying that much power constantly.
 
Corsair PSUs don't usually come under the 'crappy no-name' banner, though I don't rate their new CX series.
 
My Geforce 285 does that from time to time when it starts getting really hot. I was wondering the same thing one day, when I opened the case and nearly gave myself 2nd degree burns from holding the video card.

Now that I keep the side open, it doesn't give me that driver restart crap much anymore. Once I get the money though, I'm going to replace the power sucking furnace for something new.
 
SicKlown42012 said:
It could be that the power supply is craping out on you since switching cards didn't help. I had all sorts of little problems with stability when I had my old Silverstone Strider. I tried switching out all of my hardware for testing, but the instability continued. I decided to try and see if a new PSU would help and bought a Strider Plus on sale and everything was stable again. Unfortunately, even high-quality power supplies can go bad.
Click to expand...

Hmmm, well if everything else doesn't work, I guess I'll try a new psu.

Spooony said:
Use a driver sweeper to clean out the driver. Then look for this file

atikmdag

Delete it

Reinstall your drivers
Click to expand...

I've used driver sweeper multiple times and it still didn't work or is the certain file in another location?

Gym Rat said:
I had the exact same problem several months ago when I installed 10.9 if I remember right. That was with a 4850. Searched all thru Google and never found any real answers. Finally on a pure guess, I uninstalled CCC and that did the trick. Im now running a 5870 and if I install CCC, I get the same crap. So whenever I install a new driver, I immediately uninstall CCC and everything works fine. I dont know why or how but in my case at least, regardless of which driver I used, no matter how many times I swept drivers and regardless of which card I use, if CCC is installed, I get random crashes and the "driver has stopped responding" crap.

Give it a try. Hopefully this fixes your problem too.
Click to expand...

Alright I'll try that, thanks.

Mr. Pedantic said:
Update to the latest drivers. If everything is stock and it's still not working properly, it might be best to send the card back.
Click to expand...

Yeah I have 11.2, I've also used older ones too, still not working.


Thanks guys for the input.
 
I had this exact same problem - and in my case the problem was incompatible RAM.

It seems the 1090T's internal memory controller is extremely picky. My first memory sticks were on the motherboard manufacturer's QVL list, but not on the memory manufacturer's recommended list. The machine would randomly crash in games; sometimes I could play for hours and sometimes it would crash after 5 minutes.

Have you checked your machine for stability? 24 hour Prime95 on blend (with the old RAM mine could crash after 12 hours)? Memtest?
 
kevral said:
I had this exact same problem - and in my case the problem was incompatible RAM.

It seems the 1090T's internal memory controller is extremely picky. My first memory sticks were on the motherboard manufacturer's QVL list, but not on the memory manufacturer's recommended list. The machine would randomly crash in games; sometimes I could play for hours and sometimes it would crash after 5 minutes.

Have you checked your machine for stability? 24 hour Prime95 on blend (with the old RAM mine could crash after 12 hours)? Memtest?
Click to expand...

Yeah Some other people have told me that, and the RAM I have isn't on the RAM compatible list for this motherboard so that may be it. But this was the RAM everyone was telling me to get in the beginning and they said it would work.

And Memtest didn't come across any errors and I ran it for about 15 hours. Although Prime95 ran across the problem "FATAL ERROR: Rounding was 0.5, expected less than 0.4" in all the cores. I think it was the blend test as I recall which people said that getting that error in the blend test would mostly mean a problem with memory.
 
If you are failing Prime95 then there is definitely something wrong - and not the graphics card.

Blend tests many parts of your machine. Which part is failing could be indicated by which size FFTs are running when it gets the rounding errors, I think mine used to throw errors around 1024K when I had faulty RAM.

I literally went through 4 motherboards (Asus Crosshair IV Formula, my local shop kept thinking the mobo was the culprit) and 3 pairs of different memory sticks before I found a combination that worked. In between this I would run Prime and MemTest without errors for hours on end, until either one would suddenly throw errors the n'th time around.
 
I had the same problem with my sons computer. there is a forum at the amd site for the same issiue. I fixed mine by chaging from the aero desktop to the basic. Some catalyst control center problem. But many people are having the problem------. I actaully remember just installing the drivers also. Not the control center. I found the link i used at the amd forum



http://forums.amd.com/game/messageview.cfm?catid=260&threadid=120896
 
Last edited:
Well nothing else worked so I guess I'll order some different ram and try that.
 
"Display driver has stopped responding and has recovered" is a Windows diagnostic message triggered by its TDR, and is caused by million different things.

Link from NV forum explaining TDR error (since AMD forums look crappy as ever)

Common issues that can cause a TDR:
- Bad memory
- Insufficient/problematic PSU
- Corrupt driver install
- Overheating
- Unstable overclocks (GPU or CPU)
- Incorrect MB voltages (generally NB/SB)
- Faulty graphics card
- Your asking too much of your graphics card. Not one that many people like to hear, but as the blurb from Microsoft states, if your game falls below a certain FPS and something graphically complex occurs, it could trigger a TDR.
- The issue can potentially be caused by a badly written driver or piece of software, but this is an unlikely cause in most cases.
Click to expand...
 
The display driver have stopped.

clean out and reinstall the drivers
Disable your antivirus
 
HohnyF said:
"Display driver has stopped responding and has recovered" is a Windows diagnostic message triggered by its TDR, and is caused by million different things.

Link from NV forum explaining TDR error (since AMD forums look crappy as ever)
Click to expand...


Hmmm, well the ones I haven't really looked into is the bad memory and the bad psu. Although I might need to look into the nb/sb voltages some more. I messed with them a little but not too much.

Spooony said:
The display driver have stopped.

clean out and reinstall the drivers
Disable your antivirus
Click to expand...

I've done this many times, with many different drivers, nothing worked.
 
I used to get an error like this swapping between ATI and Nvidia cards...same thing. Took me two months to figure out it was a bad stick of patriot memory.
 
Ive been getting the same issue for a LONG time...im using an 800w XFX PSU. It's memory no doubt about it. I would get it A TON using an ASUS M4A89 motherboard and the same gskill ram thats in my sig. I switched motherboards to the MSI and the BSODs are gone but Bad Company 2 (which surefire does it all the time) still CTDs occasionally but whats more annoying is that the system is able to recover itself without booting the game. The unfortunate side effect though is that your fps drops down to a slideshow for about 15-20 seconds.

Ive done a ton of research over the year or so that ive had this issue and it almost always comes back to memory incompatibility. I replaced the motherboard first as the M4A89GTD seems to have a ton more issues then just memory incompatibility (bad ground on USB headers for one).
 
I have come across this and it has helped a few people.

Originally posted by: Seithennin Guys, here's the fix, and i have tested two different computers with it.



it worked for me 100%.



This fix should affect all users from XP to win7! There is a special option called DeadLock Detection. It is an advanced driver security policy but is not needed. Ok here is what you do, you go to start and run Verifier Then check display information about the currently verified drivers and click Next. From there click Add and add the driver ATIKMPAG.SYS. then click on change. From there untick Deadlock detection, then hit Next 2 times and then finish. Next Step: See if it fixed your issue! Final Step: If Step 1 fixed your issue then open Verifier again and select Create Custom settings. From there tick Select individual settings from a full list. Then click on Next, then check all the options that were enabled from the first step EXCEPT Deadlock detection. Then click Next, then tick Select driver names from a list. From there you want to check the file atikmpag.sys, then click on Finish and Restart.



I'm curious why this option is checked on the radeon driver system files as display drivers can't directly own resources. and "DeadLock Detection" is NOT needed.
 
I get this error when running a game in pseudo full screen mode while trying to watch a video in VLC at the same time, or instead of VLC if I open a browser and try viewing any flash based video like YouTube, it'll crash my game to desktop with this error
 
EYS did you ever find a solution to this? I have the same problem and tried most of these steps (going to try uninstalling CCC but I doubt that will work).
 
I've been getting this error for months now. It happens about once every few hours. It most especially happens when move windows around between monitors.

The entire screen will freeze, for 5 seconds I can move the mouse still, then a few seconds it is completely locked up, then for 1 second I get a greyish black/white old tv snow like screen. It then recovers and tells me that it has recovered.

I tried everything on the list except disabling this service you spoke of.
 
Like i have said before, to me it got fixed when i upped my 2d speeds, specially my 2d memory speeds.

Kinda like they did here but with all numbers according to your vidcard.

http://forums.amd.com/game/messageview.cfm?catid=260&threadid=123699&enterthread=y


EDIT TO ADD:
My card is a 6850, and the problem is more or less that for some reason my system is too slow to send the correct 3d numbers to the vidcard, so it begins to try and use what originally was a very low 2d setting of 100mhz core and 300mhz mem to do vids or 3d renders, and it triggers the timeout delay detection which makes windows say that the driver stopped working.
 
Last edited:
Revdarian said:
Like i have said before, to me it got fixed when i upped my 2d speeds, specially my 2d memory speeds.

Kinda like they did here but with all numbers according to your vidcard.

http://forums.amd.com/game/messageview.cfm?catid=260&threadid=123699&enterthread=y


EDIT TO ADD:
My card is a 6850, and the problem is more or less that for some reason my system is too slow to send the correct 3d numbers to the vidcard, so it begins to try and use what originally was a very low 2d setting of 100mhz core and 300mhz mem to do vids or 3d renders, and it triggers the timeout delay detection which makes windows say that the driver stopped working.
Click to expand...

this sounds similar to when i'm playing FFXI in pseudo fullscreen mode and my 3D clocks sometimes don't kick in, because the graphics driver doesn't detect i'm actually playing a game (something about ATI drivers not playing nice with windowed games)
 
I have noticed that this very very rarely happens when playing a game. It is almost only in windows. Upping the 2d speed sounds like it would fix it. I'll give it a try.
 
I started having this problem about two months ago. Everything in my system has been there since the release of the 5850. I think this is being caused by ether the AMD driver or a Microsoft update. I did to a fresh format on my drive and I haven't seen any problems so far.
 
You must log in or register to reply here.
Back
Top