“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: Newest
  1. Anonymous
    2010-10-15T02:50:28+00:00

    That reference does define the problem, however what "simple registry setting" is required to fix it?  In my case W7 x 32) I have none of the "tdr" keys referenced in my registry.  The closest thing I have in HKLM\System\CurrentControlSet\Control\GraphicsDrivers is a setting called DCI which has a timeout value of 7.

    I believe you need to add those keys yourself. Microsoft stresses that they are used for debugging purposes only. I'm not certain whether you need to create a key called "TdrLevel" and within that key create the reg_dword "TdrDelay", or if the "TdrDelay" goes into the GraphicsDrivers key. I just added both, and set it to 6 (probably decimal, but they don't specify it), so it's on a 6 second timeout instead of 2.

    Whether this still works in Windows 7, I don't know. But the TDR technology is certainly still in Windows 7, so it very likely still works.

    Here is another link where people talk about the TDR setting: http://forums.amd.com/devforum/messageview.cfm?catid=328&threadid=100142

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2010-10-15T02:24:30+00:00

    That reference does define the problem, however what "simple registry setting" is required to fix it?  In my case W7 x 32) I have none of the "tdr" keys referenced in my registry.  The closest thing I have in HKLM\System\CurrentControlSet\Control\GraphicsDrivers is a setting called DCI which has a timeout value of 7.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2010-10-15T01:40:26+00:00

    It's a Microsoft "feature" called Timeout Detection and Recovery   or TDR. It's a WDDM function that resets the driver if it thinks the framerate has slowed down so much that it's crashing.

    A simple registry setting might solve this problem:

    http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2010-10-14T07:38:56+00:00

    Hi

    I had the same issue until few days ago. Downloaded Microsoft Fix It tool and ran it.

    http://fixitcenter.support.microsoft.com/Portal/GetStarted

    http://download.microsoft.com/download/D/7/E/D7E37511-A7CA-4C8B-B61B-1C90895D9823/FixitCenter_Run.exe

    It deleted & repaired some FF or something video codecs.

    The problem disappeared.

    Was this answer helpful?

    0 comments No comments