• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

Bit of a problem

Doco

Doco

Doco

Associate
Joined
16 Aug 2011
Posts
1,569
Location
Ireland
So I was encountering a bit of a problem recently when playing Diablo 3, every so often (and quite frequently at times) where the screen would go blank on me and would take a while to restore itself, originally I thought it was the game freezing or lagging, but it turns out it was "display driver has stopped responding and has been recovered", wasn't overly sure what the problem was but I restored my gpu to its factory settings (I had it O.C.) and the problem went away, so its obvious it was the O.C. but what I dont really get is what it was about the O.C. that was causing the problem, D3 isnt the most demanding of games, and I've played heavier demanding games without any problems, skyrim, BF3, Dirt 3 etc with the same O.C. and I'd say similar settings (high-ish settings - on a 720p tv, so the resolution helps play ad decent settings)
Any reason why D3 encounters the display driver problem but no any other game? I can also note that it wasnt a temperature issue, temps never gone above 60 ( havnt seen it over 55 but I'l round up), so any info would be helpful (is it just that the card is starting to fail or is it software related, running 12.6 CCC)
 
Just curious if anyone else has this problem? or knows why its happening, I know the solution is just to not have the card overclocked when playing Diablo 3, and havnt had any issues since, but it's bugging me why I get a display driver stopped responding error on only that game? and why my OC seems fine one other games?
Thanks for reading and any info you have.
 
2. Things to try:

1. Change drivers - seems that some drivers are causing this issue for some and not others.
2. If your card is overclocked (or not tbh) add a little more volts (0.06)

Hopefully one of those will sort your problem. This is not uncommon but seems to be happening quite a bit recently, so maybe more so drivers.
 
Thanks for the advice, im currently running 12.6 CCC with driver 8.980.0.0 and the only update I can find is the beta 12.7 CCC with driver 8.981.2.0, is it worth updating to the beta? ( I've no problem running beta drivers if they're better than the older ones, eg i was using 12.6 beta but that was because 12.4 was terrible, would you recommend the 12.7?)

And as for the voltage, the card gets its power from the pci slot, it has no power connectors, am I still able to increase the voltage to the card?
 
I think 12.4 was mentioned as a good driver but maybe AMD users can confirm. Try the drivers first and I will investigate with that card.
 
downloaded 12.7 driver and within half an hour display driver error ( with O.C ) but just got the official 12.8 update, so we'll see how it runs, it's obv. the overclock, and Diablo 3 runs grand on stock settings so its not as if im missing out, just something that was annoying me lol
 
12.8 have been reported as giving a BSOD (only 1 person). Hopefully they will be ok for you. If not, try the 12.4's and see how that works out.
 
You must log in or register to reply here.
Back
Top Bottom