• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Display drive has stopped responding and has recovered

7beauties

Member
No good deed goes unpunished; I upgraded my system to the following:

Windows 7 Home Premium 64 bit OS
Gigabyte GA-890FX-UD5 mobo supporting USB 3.0 and SATA 3.0
Phenom II X4 965 Deneb 3.4Ghz CPU
16GB PC1333 DDR3 RAM
PC Power and Cooling 950 Watt PSU
a pair of Radeon HD 5870's in Crossfire mode
Sound Blaster X-Fi Titanium "Fatal1ty" Champion sound card
Seagate Barracuda XT 6/Gbs 2TB HDD

In spite of all this upgrade goodness, my desktop will freeze, go blank and recover with the message bubble that "display driver stopped responding and has recovered." Moreover, when I try to play certain games via Steam my system will sometimes crash to a BSOD with the error message to this effect: "attempt to reset display driver and timeout failed," etc.

What the heck is going on? After spending all this money I'm going nuts and am very unhappy. Is anyone familiar with this situation? I've noticed on the Microsoft Support Forums many such similar posts, many by people who use Nvidia parts. What are we doing wrong? When I paired my two Radeon HD 5870's in Crossfire, I used two bridging straps. Was I supposed to use only one of them? If I was supposed to use only one, which tabs was it supposed to bridge? Can someone very smart in here help me? I've not over-clocked anything, BTW. Thank you.
 
Are you using the latest catalyst video drivers? I have never seen this error on my desktop with a 5850, but I do see it a lot on my Atom netbook which has some terrible intel integrated graphics. I suspect it is entirely driver related but intel doesn't offer any newer drivers in my case.
 
which bridge doesn't matter... using both doesn't help...

pull out one card and see what happens...

sounds like all new stuff... sometimes new stuff don't work...

and the sb cards have been fabled to be troublemakers sometimes... maybe pull it out first... may just need to put it in a different slot so it uses a different irq...
 
Ive been having this problem with a 4850 for a long time. Bugs the shizzle out of me but Ive never found a solution, even underclocking/undervolting the card additional cooling etc. No driver revision has worked, or even simply not installing one (let microsoft use its default driver). It seems the problem only appears on newer cards, a few 4 series, and a lot of 5 series. I have to wonder if theyre just making shitty cards or something, bad bios or something or bad core...it does seem to act like a CPU thats not really stable.
 
Thank you for your responses. I appreciate it. I have the latest Catalyst driver, ver. 10.9. I haven't over-clocked anything. I have used two Crossfire straps to bridge the pair of video cards, but Cubeless suggests that this wasn't necessary. I guess I can try benchmarking my system with Everest Ultimate and see what I find out. Man, there are a ton of posts just like mine on Microsoft's Support Forums, but I've only found replies here. Again, thank you for the suggestions and replies.
 
I had this same problem with my 4870X2 (before it died...need to update my sig). I also was/am running W7_x64, latest Cats, motherboard drivers, BIOS...you name it, I had the newest available. Don't know if you are aware but Steam has had MAJOR issues for the past 3 weeks or so with L4D2 patches. Seems that their patches don't play nice with user-created maps ("Extras" in Steam) and cause all sorts of issues. Being that Steam patches all by itself with no user option to "notify me but do not download/install" we are left w/zero choice but to deal with it and hope Steam fixes it.

Not saying your prob is Steam-related; just saying what I've experienced. Getting down to basics, could be something as simple as something in the new Cat drivers not playing nice with soemthing in a recent Windows update. Happens all the time in the server world (Win update breaking something SQL/PHP/Java/etc related and crashing the box).
 
Back
Top