“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
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

334 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2016-04-15T23:00:06+00:00

    Well, I had my computer in for repair and to have the AMD driver updated.....it's still doing it, just not as often   :(

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-04-15T11:27:14+00:00

    Oh, I'm 64-bit.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-04-15T11:25:42+00:00

    I am on HP desktop windows 8.1.  It just happened to me few minutes ago.  Got this computer for Christmas 2014.  Do I need to update the driver?

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-01-16T01:02:56+00:00

    I have a brand new Dell windows 10 and I am getting the same error message.

    Was this answer helpful?

    0 comments