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 get the error "Display driver stopped responding and has recovered" But i only get it when i play Battlefield bad company 2, and i got the latest version so i can't understand what the problem is and i got an Ati Radeon HD5770

This is definitely a Microsoft problem! If you read through this entire thread this error occurs on many different brands of computers with all kinds of hardware configurations. I have HP laptop with an Nvidia GPU. I have installed every available latest update possible for both the graphics GPU and the chipset and the error continues to happen. The only thing prevents it from happening is to roll the driver back to the basic VGA driver that comes with the Windows version you are installing. And that limits display options, resolution and using any higher res graphics functions for video or display. I just tried the registry change and we'll see what happens. Microsoft needs to step up and fix this problem. It has went on too long on too many different types of hardware for it to be a hardware problem or heat related on any of the other BS solutions that has been eluded to in this forum. What seems to fix the problem for one doesn't fix it for all. The common thread in this whole forum has been the "Display driver has stopped responding and has recovered" followed by extremely slow operation or crashes. C'mon Microsoft, fix this problem instead of sending us updates that make problems worse or make problems that didn't exist before. Put those high priced software engineers to work diagnosing what the root cause of the problem is. Too many problems noted in too many forums across the web with too many users with too many different hardware configurations to keep saying its a driver or hardware problem. And by the way how about pushing a fix for the orange screen calendar gadget in Windows update. It's about time for some real fixes!

Same problem here but even worth. it a Brand new PC (not a laptop) running a Quadro FX 2000 PC is an ASUS cmputer Win 7 64 and computer most of the time will not recover at all simply shuts down. when working in VGA mode no problem. It must be something with the graphics card. Hate this

Microsoft introduced a feature called Timeout Detection and Recovery (TDR) since Windows Vista. Basically it is a timer that counts how many seconds the video card has stopped responding to the OS (2 seconds by default) and it assumes the video card or driver has crashed. It restarts the video subsystem in an attempt to prevent a crash. Why this happens is anyone's guess. Maybe some system files related to video get corrupted, or the video drivers are poorly written, or the video card has a hardware fault. It could also be a program that drops the frame-rate too low, like a high-end (or buggy) game. Either way it's Windows reacting to a problem. The following is a way to extend the time Windows waits before it restarts the video. It doesn't "fix" the original issue, but it should prevent most, if not all, of the TDR's from happening. It's like disabling airbags in a car because they keep randomly deploying- it's not really a fix, but at least you can drive again :) Note: If you are not familiar with editing the registry, I wouldn't recommend changing the TDR. It involves creating new keys and values, which have to be exactly the same as the instructions, even the capitalization. Click Start, Run, and type "regedit" Navigate to: HKey Local Machine\System\CurrentControlSet\Control\ Locate the "GraphicsDrivers" key, and right-click on it. Click "New" and "DWORD Value" (it will say 32-bit if you are on a Windows 64-bit) Label the new value "TdrDelay" Double click on TdrDelay, and enter the number of seconds you want Windows to wait before timing out. The default is two seconds, so start out with 6, and you can make it a few seconds longer if it doesn't fix the issue. Close the registry editor and reboot the computer. This applies to any video card, Nvidia, ATI, or other. More info here: http://www.microsoft.com/whdc/device/display/wddm_timeout.mspx (they say Vista but it also works with Windows 7 32/64) and a forum post here: http://forums.amd.com/devforum/messageview.cfm?catid=328&threadid=100142 You say to add a TdrDelay, but there is already one there. Should I just edit that one? And when I do go to edit it, it's set to 14 seconds by default, not 2.

“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

2011-06-19T20:07:04+00:00

i get the error "Display driver stopped responding and has recovered" But i only get it when i play Battlefield bad company 2, and i got the latest version so i can't understand what the problem is and i got an Ati Radeon HD5770
Was this answer helpful?

0 comments No comments
Anonymous

2011-06-18T13:13:46+00:00

This is definitely a Microsoft problem!

If you read through this entire thread this error occurs on many different brands of computers with all kinds of hardware configurations.

I have HP laptop with an Nvidia GPU.

I have installed every available latest update possible for both the graphics GPU and the chipset and the error continues to happen.

The only thing prevents it from happening is to roll the driver back to the basic VGA driver that comes with the Windows version you are installing.

And that limits display options, resolution and using any higher res graphics functions for video or display.

I just tried the registry change and we'll see what happens.

Microsoft needs to step up and fix this problem.

It has went on too long on too many different types of hardware for it to be a hardware problem or heat related on any of the other BS solutions that has been eluded to in this forum.

What seems to fix the problem for one doesn't fix it for all.

The common thread in this whole forum has been the "Display driver has stopped responding and has recovered" followed by extremely slow operation or crashes.

C'mon Microsoft, fix this problem instead of sending us updates that make problems worse or make problems that didn't exist before.

Put those high priced software engineers to work diagnosing what the root cause of the problem is.

Too many problems noted in too many forums across the web with too many users with too many different hardware configurations to keep saying its a driver or hardware problem.

And by the way how about pushing a fix for the orange screen calendar gadget in Windows update.

It's about time for some real fixes!
Was this answer helpful?

0 comments No comments
Anonymous

2011-06-17T06:31:38+00:00

Same problem here but even worth.

it a Brand new PC (not a laptop) running a Quadro FX 2000

PC is an ASUS cmputer

Win 7 64

and computer most of the time will not recover at all simply shuts down.

when working in VGA mode no problem.

It must be something with the graphics card.

Hate this
Was this answer helpful?

0 comments No comments
Anonymous

2011-06-14T22:34:40+00:00
Microsoft introduced a feature called Timeout Detection and Recovery (TDR) since Windows Vista. Basically it is a timer that counts how many seconds the video card has stopped responding to the OS (2 seconds by default) and it assumes the video card or driver has crashed. It restarts the video subsystem in an attempt to prevent a crash. Why this happens is anyone's guess. Maybe some system files related to video get corrupted, or the video drivers are poorly written, or the video card has a hardware fault. It could also be a program that drops the frame-rate too low, like a high-end (or buggy) game. Either way it's Windows reacting to a problem.

The following is a way to extend the time Windows waits before it restarts the video. It doesn't "fix" the original issue, but it should prevent most, if not all, of the TDR's from happening. It's like disabling airbags in a car because they keep randomly deploying- it's not really a fix, but at least you can drive again :)

Note: If you are not familiar with editing the registry, I wouldn't recommend changing the TDR. It involves creating new keys and values, which have to be exactly the same as the instructions, even the capitalization.

Click Start, Run, and type "regedit"

Navigate to: HKey Local Machine\System\CurrentControlSet\Control\

Locate the "GraphicsDrivers" key, and right-click on it.

Click "New" and "DWORD Value" (it will say 32-bit if you are on a Windows 64-bit)

Label the new value "TdrDelay"

Double click on TdrDelay, and enter the number of seconds you want Windows to wait before timing out. The default is two seconds, so start out with 6, and you can make it a few seconds longer if it doesn't fix the issue.

Close the registry editor and reboot the computer.

This applies to any video card, Nvidia, ATI, or other.

More info here:

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

(they say Vista but it also works with Windows 7 32/64)

and a forum post here:

http://forums.amd.com/devforum/messageview.cfm?catid=328&threadid=100142
You say to add a TdrDelay, but there is already one there. Should I just edit that one? And when I do go to edit it, it's set to 14 seconds by default, not 2.
Was this answer helpful?

0 comments No comments