“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
    2012-12-15T21:54:40+00:00

    Yes, I got the very latest driver here http://bit.ly/MhqWK

    My motherboard is NOT overheated. This is a brand new, just out of the box Lenovo W500. The issue has nothing to do with temp.

    Thanks, but this is not the answer.


    Crabby Office Lady

    You are right Crabby Lady it's neither the driver nor dust bunnies on the mother board nor low voltage not to much or to little memory been following this nonsense you over a year now and the implementation of Win8 only made things slightly different but has not corrected the situation.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2012-12-19T19:14:03+00:00

    I have tested both ny pieces of ram and one of them gives the error.  I run my computer know with one piece. luckely it's a 4 GB piece. 

    Seriously if you have tried everything in this thread and nothing works, check your RAM. Just remove or replace it and see if it helps.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-01-10T15:40:31+00:00

    Many 3D cards require a minimum voltage to be stable, but when "idle", they are basically asleep so everything should be ok.

    I have strong reasons to believe this analysis over any other one, that never lead to a solution.

    I have the problem about once a day in average (but sometimes never in a whole week) since ages and have tried pretty everything without luck...

    Her my observations:

    I NEVER had the problem when the GPU was under load, NEVER when e.g. PowerDirector is converting HD software and asks raw power from the GPU, so it's NOT overheating, for sure!

    I NEVER have seen the problem neither when the computer was full idle.

    But what I am sure is that to 90% it happens when the computer was idle for at least one or two minutes immediately after I begun to work again (frequently upon starty an eMail reply with Thunderbird).

    So all that confirms my strong beliving that it is an undervoltage problem.

    I came to the idea to combine a potential solution with some public wellfare:

    I will install BOINC http://boinc.berkeley.edu/download.php and let my GPU work for the science e.g. Rosetta@home with 20-30 % of its computing power, so it will not be idle. ;-)

    Logically the undervoltage problem should disappear.

    Did someone try that?

    You may do it as well and return your experience...

    Looking forward to hearing from you

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2013-01-12T21:12:14+00:00

    I tried it and, hard to believe, it really works!

    >:-0

    Was this answer helpful?

    0 comments No comments