Display driver stopped working and recovered itself

[vincedea]

Alright so i have a gigabyte gtx 560 ti and ever since i played dead island i have been getting this messagethat my display driver stopped working and recovered itself. It also does it when i play bf3 beta. It has only happened 2 times when using firefox. Any ideas on what the issue may be. I have used driver sweeper to do a clean install of the drivers. The has been solid for like 5 months maybe more. But yes it is very annoying And im hoping i can get a fix beforr bf3 is offically out. Thanks

 

[Seero]

Alright so i have a gigabyte gtx 560 ti and ever since i played dead island i have been getting this messagethat my display driver stopped working and recovered itself. It also does it when i play bf3 beta. It has only happened 2 times when using firefox. Any ideas on what the issue may be. I have used driver sweeper to do a clean install of the drivers. The has been solid for like 5 months maybe more. But yes it is very annoying And im hoping i can get a fix beforr bf3 is offically out. Thanks

Driver bugs may cause that, hardware malfunction may cause that, memory fault may cause that, and bad sector on storage may also cause that.

Chances are, it is the driver. If you are using that latest beta driver, then it is the driver.

 

[BD231]

There are a lot of people having that same issue with the BF3 beta driver, I had the same thing happen today but I was just using my desktop not gaming. Hopefully the final WHQL's fix this.

 

[velis]

I had an ASUS P5K-E Mobo that had a borked PCIEx controller (most probably, I had no way of confirming).
The stopped responding and has recovered was pretty common for my 5870 then (among other, more serious problems).
Replaced the mobo, never had the issue again...

 

[birthdaymonkey]

I was also having this problem with my OCed 560 Ti and the latest betas. I turned off the OC and reverted to the latest WHQLs and haven't had it happen since.

 

[Chiropteran]

There are a lot of people having that same issue with the BF3 beta driver, I had the same thing happen today but I was just using my desktop not gaming. Hopefully the final WHQL's fix this.

You must be confused, he has an nvidia card. Everybody knows nvidia drivers are flawless.

 

[Meghan54]

You must be confused, he has an nvidia card. Everybody knows nvidia drivers are flawless.

Riiiiight.

I had the same crap with a 560 Ti myself. It's been relegated to its box and a 6970 replaced it. No more driver crashes.

And I'm having a devil of a time getting rid of that 560 Ti.......

 

[DirkGently1]

Uninstall drivers and card. Re-seat the card in the slot. Re-install drivers.

 

[Philgag]

Re-seating the card? Would a unproprely seated card barely work if work at all?

I got this error once while browsing the web on my new build (see sig)."Only" once in about two week of intense usage. and that's while using lastest AMD official driver. I'm guessing its related to a driver glitch because I gamed a lot (BF3, deus-ex) and everything else have been rock solid.

Have you tried updating to lastest mobo bios?

 

[birthdaymonkey]

Had the display driver crash again with the 280.26 WHQLs. Annoying. Reverted to 275... I was on that driver for a long time without any problems, so if I get this error again I'll know it is something other than a driver problem. Googling the error with 280.26 gets quite a few reports from other 560 users experiencing the same issue.

 

[edplayer]

I had the same problem with the beta drivers and my 460

Not 100% sure of the cause but its most likely AMD's fault









or Obama's

 

[vincedea]

Had the display driver crash again with the 280.26 WHQLs. Annoying. Reverted to 275... I was on that driver for a long time without any problems, so if I get this error again I'll know it is something other than a driver problem. Googling the error with 280.26 gets quite a few reports from other 560 users experiencing the same issue.

have you had the issue wheny ou went back tot he 275 drivers?

 

[birthdaymonkey]

have you had the issue wheny ou went back tot he 275 drivers?

I've been using them for about 36 hours now and haven't experienced a display driver crash. However, the crash didn't happen to me every day either. I'm optimistic at least.

 

[DirkGently1]

Re-seating the card? Would a unproprely seated card barely work if work at all?

Look around the forums. Lot's of people have had problems with cards not being seated properly, throwing up Driver not responding issues and other glitches. It happened to me and i almost put in for an RMA before getting to the root of the problem. Do you want to mess around forever with different drivers without first ensuring the card is seated?

I'm not sure what has happened with this generation of cards but there's something off with the way these 5 series cards fit in the slot/case. With my GTX570 it just doesn't 'fit' comfortably the way every other cards i've owned has, and others have said the same.

Regardless, if you have hardware trouble of any kind you should always start with connectors etc before worrying about drivers.

 

[Attic]

Had the display driver crash again with the 280.26 WHQLs. Annoying. Reverted to 275... I was on that driver for a long time without any problems, so if I get this error again I'll know it is something other than a driver problem. Googling the error with 280.26 gets quite a few reports from other 560 users experiencing the same issue.

I get see this on my 460 1GB with the 280.26's as well. Though I have seen it on other driver sets as well.

It is extremly rare for me. I attributed it to my overclock, 800mhz.

 

[gramboh]

This is a well documented problem, there's a massive thread over at NVIDIA's official forums. For me personally, I've had the problem ever since the 275.50 betas, it was the worst with 280.26 and still occurs on the newest BF3 beta drivers.

I turned my card down to factory OC from the additional OC I had which helped a bunch. I also disabled hardware acceleration in Flash and upgraded to Firefox 7.0.1 both which helped reduce the driver crashes on desktop use, I just get one every few days now whereas I was getting 10+ a day on desktop use.

Games have not caused problems for me since turning down to factory OC (BF3 beta, BC2, Witcher 2, SHIFT2, TF2). The problem seems to be related to voltage regulation/changing power states.

 

[vincedea]

This is a well documented problem, there's a massive thread over at NVIDIA's official forums. For me personally, I've had the problem ever since the 275.50 betas, it was the worst with 280.26 and still occurs on the newest BF3 beta drivers.

I turned my card down to factory OC from the additional OC I had which helped a bunch. I also disabled hardware acceleration in Flash and upgraded to Firefox 7.0.1 both which helped reduce the driver crashes on desktop use, I just get one every few days now whereas I was getting 10+ a day on desktop use.

Games have not caused problems for me since turning down to factory OC (BF3 beta, BC2, Witcher 2, SHIFT2, TF2). The problem seems to be related to voltage regulation/changing power states.

voltages??? how so? so even if i formatted i could still get this problem? sigh its so annoying.

 

[yuppiejr]

The issue is likely the well documented TDR crash problem, easy fix with a reg hack and reboot (it was acknowledged by nvidia as a valid workaround to boot):

http://forums.nvidia.com/index.php?showtopic=211808

I'd been chasing this problem with over 30 laptops and a dozen desktops at work that manifested different "video card" issues including the " Display driver nvlddmkm stopped responding and has successfully recovered" event viewer warning.

Sometimes I would get random pink splotches on the screen before the error, sometimes I'd lose DVI output to all displays and then get it back a few minutes later...sometimes the machine would just dump with the error code above (either Windows error or a full on bluescreen)

All work perfectly now, driver 280.26, I wasted hours testing everything including replacing/reseating video cards, different power supplies, fresh Windows/driver loads, etc... I should send a bill to nVidia for wasting hours of billable time with more of their shitty drivers.

"Well hello i am currently on 285.38 BF3 Beta drivers and believe i have found a fix for this TDR problem after doing a ton of research. Editing 2 Simple Registry Files has so far as of 3 days fixed it. No TDR Crash No "Nvidia Driver has stopped responding commonly in firefox. Well on 285.38 drivers i was getting tons of TDR crashes..........277 did not have this. Well the Fix was simply delaying TDR Latency to report....I am sharing this in hoping i can help many people with this and see how this current fix works. So far NO TDR crashes and by now i would have several so it is working so far. The fix is as follows and im hoping this fix will work. Why am im not going back to 277? Well performance is very high on 285.38 drivers and off course the BF3 Beta. And the TDR was a problem because it would reverse any overclock i had applied. the TDR crash happened non OCed btw also all 280.XX drivers have caused this. Simply Delaying win 7 TDR Delay from 2 Seconds (the Default) To 60 Seconds and the report fixed it. the following registry keys i changed. Navigate to


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ GraphicsDrivers]


Then create a a REG_DWORD file called TdrDelay and set the value to 60



ex. "TdrDelay"=dword:00000060 (60 seconds)



Then navigate to
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ GraphicsDrivers\DCI]


and Create a Value called

"Timeout"=dword:00000060


Having created both of these words in the specified paths, you need to reboot the machine. The timout issue should now be fixed.

As an alternative, synchronizing threads can alleviate this issue. Reduction in kernel size and execution time can also do the trick."

 

[birthdaymonkey]

I reverted to 275.33 a couple weeks ago and haven't had the crash happen since. None of the games I play (only SC2 at the moment) seem to get much benefit from the newer drivers, I'll just wait for nvidia to get their act together... hopefully in the next release.

I thought ATI's drivers were supposed to suck?

 

[stahlhart]

Alright so i have a gigabyte gtx 560 ti and ever since i played dead island i have been getting this messagethat my display driver stopped working and recovered itself. It also does it when i play bf3 beta. It has only happened 2 times when using firefox. Any ideas on what the issue may be. I have used driver sweeper to do a clean install of the drivers. The has been solid for like 5 months maybe more. But yes it is very annoying And im hoping i can get a fix beforr bf3 is offically out. Thanks

Having the same issue here, but has only occurred twice for me, and only in 2D (I think browser usage in both cases). Have not had a single GPU-related hiccup prior to this, but then this is the first time I've run beta drivers in the current build.

 

[VirtualLarry]

I'm on 280.26 WHQL, and have had no problems to speak up. I did have some problems with BOINC and CUDA GPU-using apps, when they existed or paused (release the GPU), it seemed to leave it in an unstable state, and I often got screen freezes or black screens, but that was with a 275.x driver.

 

[vincedea]

Well after the beta ended for bf3 i also uninstLled a few games and i have only goten a crash like maybe one time and it was broswrring with firefox. Not sure what next step i should take would be really gay if i cant play bf properly

 

[BD231]

You must be confused, he has an nvidia card. Everybody knows nvidia drivers are flawless.

I love the way their drivers make cards explode in real time, a company that agrees there's clearly no substitue for real fire in the land of 3D.

 

[eldeorn]

I've had this purple screen crashing/driver reset since I bought my GTX 570 two months ago, and everytime i played Dead Island it crashed within a minute or two. When I zoned outside to the top of the light tower, it crashed 100% of the times almost instantly.

Last night, I forced my nvidia drivers to always run MSAA = OFF and Anisotropic = 8x, and voila, Dead Island ran fine for 2 hours straight with no issues.

Today I've played for another 5 hours without issues.

PS. I had these problems with all the drivers from 270 to the latest 295 beta.

PPS. I've also experienced problems with CS:Source, and that's where I figured it could have to do with one of the filtering settings, since I did a reinstall of it and it ran fine for a week with default settings (filters off), until I changed to 4x msaa & 4xAni. Then it decided to start crashing again. So my conclusion... it's either the Edge Smoothing/MSAA or the Anisotropic setting that is bad. I'm not gonna bother to test which it is until I'm sure it's 100% stable for like a week at least.

 

[peonyu]

My experience with crashes like that come down to two things and both are related -

Core clock and or Memory speeds on your card.

Even a card that is NOT overclocked can have stability issues related to core speed or memory...The way to test if that is your problem ? Download MSI Afterburner, and underclock your Core and Memory by 50mhz each.

No more crashing ? Either live with having to keep your card underclocked or RMA it.

The other culprit which [in my experience atleast] is rare, is system memory or CPU instability. Drivers can also do it, as can a bad PSU.

Try out Afterburner though, takes 5 min to DL and set it up.