“Display driver stopped responding and has recovered” error.

Anonymous
2009-10-13T16:38:34+00:00
  • Running Windows 7, 32-bi,t on a Lenovo W500. Display Driver: ATI Mobility Radeon HD 3650.
  • The error message (“display driver stopped responding & has recovered”) follows a system freeze, a short blackout. Then everything works fine.
  • Downloaded the most current driver from the company's Web site.
  • Seeemd to work for a day, but now I'm getting the same behavior.

Crabby Office Lady

Windows for home | Previous Windows versions | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2012-01-27T00:10:30+00:00

Hello Crabby Office Lady,

This error can happen because of an outdated video driver, to many programs running at one time or even high CPU activity. There is a link to a KB article on the following post that gives more info on the issue and helps to fix it, see:

http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/error-display-driver-stopped-responding-and-has/1b6c2b8b-b0a7-49d9-bc3b-e9cc98d51004

L.D.

Was this answer helpful?

40+ people found this answer helpful.
0 comments No comments

334 additional answers

Sort by: Oldest
  1. Anonymous
    2011-01-27T00:55:59+00:00

    Thanks Maxstr. I've made that registry change and we'll see how it goes.

    By the way, I'm running 64bit windows and it didn't say 34bit where you said it would, it just said DWORD 32bit. QWORD says 64bit.

    Thanks again!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2011-01-27T02:51:53+00:00

    Thanks Maxstr. I've made that registry change and we'll see how it goes.

     

    By the way, I'm running 64bit windows and it didn't say 34bit where you said it would, it just said DWORD 32bit. QWORD says 64bit.

     

    Thanks again!

    No problem, I hope it works for you. After I made the change myself, I never had it happen again. As for the "34-bit", that was a typo :)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2011-01-28T01:03:59+00:00

    Hi again,

    I changed the value to 6 hex, and the fault still occurred, then changed it to 10 hex, and the problem is still there.

    With the longer times the problem is even more annoying as the whole screen locks up, and nothing can be done until the delay time is up.

    On that forum you linked to it says to try and set that value to zero. I'll do that now and see what happens.

    Thanks again!

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2011-01-28T01:21:42+00:00

    Hi again,

     

    I changed the value to 6 hex, and the fault still occurred, then changed it to 10 hex, and the problem is still there.

    With the longer times the problem is even more annoying as the whole screen locks up, and nothing can be done until the delay time is up.

    On that forum you linked to it says to try and set that value to zero. I'll do that now and see what happens.

    Thanks again!

    Sorry to hear that it didn't work. Sometimes it stops the crashes, but like I mentioned in my post, it's not a fix. The good news is that now you know that it's not a Windows issue, so that narrows it down to either driver or hardware. Do you have any video cards laying around that you can swap and test? Or maybe your motherboard has built-in video? Have you tried completely un-installing the driver, and just using the default Windows driver?

    Was this answer helpful?

    0 comments No comments