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

I got the same problem with my HP, and here is how I fixed it. If it keeps freezing on you and wouldn't let you do anything for more than 30 seconds then restart your machine in Safe Mode. Then go to your Device Mananger -> right click on my computer ( or Computer) and choose Properties, then click on Device Manager. Click on the arrow to show the installed driver. Right click on the driver and choose Update Driver Software. Select "Browse My Computer For Driver Software". Next, select "Let me pick from a list of device drivers on my computer". Then choose the older version of the driver to install. In my case, I installed the original version that was installed when I purchased my laptop. I believe that the problem is the updated version isn't compatible with my hardware. I hope this help. HP Pavillion Notebook Windows 7 Home Premium 64 bit (upgraded from XP) ATI Radeon HD 3200 Have been dogged by this problem for years (since upgrade to Win 7) and tried many other fixes to no avail. This is the one that appears to have corrected the problem for me (I also un-clicked the 'enable power play option' in the ATI ccc as per one other poster). I was just about to give up on this old laptop and now hope to get a few more miles out of it. Thanks for posting this solution!

2013-Jan: Same issue on a Windows 7 32-bit Dell with an EVGA GeForce 6200 video card (Nvidia chipset) in an AGP 8x slot and the latest applicable driver 307.74 installed. Yes; an old motherboard. Oddly, this issue was occurring prior to installing this "new" (newly purchased) card. I was surprised to see the error reappear today. Have a few apps open, at the time issue occurred: Excel, QuickBooks, Outlook, Firefox. Not very CPU-intensive apps. This is frustrating...

I tried it and, hard to believe, it really works! >:-0

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

“Display driver stopped responding and has recovered” error.

Anonymous

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

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

Answer accepted by question author

Anonymous

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.

0 comments

334 additional answers

Anonymous

2013-02-06T16:31:15+00:00

I got the same problem with my HP, and here is how I fixed it.

If it keeps freezing on you and wouldn't let you do anything for more than 30 seconds then restart your machine in Safe Mode.

Then go to your Device Mananger -> right click on my computer ( or Computer) and choose Properties, then click on Device Manager.

Click on the arrow to show the installed driver. Right click on the driver and choose Update Driver Software. Select "Browse My Computer For Driver Software". Next, select "Let me pick from a list of device drivers on my computer". Then choose the older version of the driver to install. In my case, I installed the original version that was installed when I purchased my laptop. I believe that the problem is the updated version isn't compatible with my hardware. I hope this help.

HP Pavillion Notebook

Windows 7 Home Premium 64 bit (upgraded from XP)

ATI Radeon HD 3200

Have been dogged by this problem for years (since upgrade to Win 7) and tried many other fixes to no avail. This is the one that appears to have corrected the problem for me (I also un-clicked the 'enable power play option' in the ATI ccc as per one other poster). I was just about to give up on this old laptop and now hope to get a few more miles out of it. Thanks for posting this solution!
Was this answer helpful?

0 comments No comments
Anonymous

2013-01-28T04:34:52+00:00

2013-Jan: Same issue on a Windows 7 32-bit Dell with an EVGA GeForce 6200 video card (Nvidia chipset) in an AGP 8x slot and the latest applicable driver 307.74 installed. Yes; an old motherboard.

Oddly, this issue was occurring prior to installing this "new" (newly purchased) card. I was surprised to see the error reappear today.

Have a few apps open, at the time issue occurred: Excel, QuickBooks, Outlook, Firefox. Not very CPU-intensive apps.

This is frustrating...
Was this answer helpful?

0 comments No comments
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
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