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

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.

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

I tried FixIt but it didn't find any issues on my computer

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 Thanks for that link. Meanwhile I have installed NVidias Beta driver 260.89 to see if that makes any difference. If I still get the failure I will try that Reg fix.

“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

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

2010-10-15T02:50:40+00:00

I tried FixIt but it didn't find any issues on my computer
Was this answer helpful?

0 comments No comments
Anonymous

2010-10-15T06:15:41+00:00

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

Thanks for that link. Meanwhile I have installed NVidias Beta driver 260.89 to see if that makes any difference. If I still get the failure I will try that Reg fix.
Was this answer helpful?

0 comments No comments