• 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.

display driver stopped responding but has now recovered

Associate
Joined
26 Sep 2013
Posts
218
built my first pc yester (for the second time becuase of other problems)

you may have encountered or know the error in my title.

i have a r7 260x which has been recently been released and i am getting that error, i dont know what to do or where to start ive looked at many other forums that are about the same topic but i have no idea where to start troubleshooting
 
Any Overclocking? This error happens when you dont have enough Voltage for the Overclock..
If you not Overclocking maybe try a clean driver install.
 
Any Overclocking? This error happens when you dont have enough Voltage for the Overclock..
If you not Overclocking maybe try a clean driver install.

no overclocked and ive tried uninstalling the graphics card drivers then reinstalling, it crashed once on boot and for several hours (6 hours) it didnt crash on me and just now it crashed again.

i guess the reinstallation helped but not really.
 
Think it is a driver bug I was getting this happen a lot on the 13.11 beta 8 driver but switching to the 13.11 beta 9 driver has fixed it for me.
 
Had this issue with both a 6850 and a 7850.

Try underclocking the card in AMD overdrive. If it works at lower clocks, it's likely the card isn't getting enough voltage. You try upping the voltage a tad to see if it helps, but personally I'd just RMA the card, especially since it's a new build.

The 7850 I had ran at reduced clocks (around ~500 on the core or so) but no amount of voltage tweaking could get it to run at stock speeds so I RMA'd. I tried the 6850 in multiple computers and configurations but I gave up in the end since it was easier to just RMA.
 
Just uninstalled the old then then reboot install the latest beta driver been fine since not had a single driver has stopped responding error message since
 
Back
Top Bottom