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

Yesterday I removed one of my 4 gb memory modules. Until know everthing works fine. I have tested it extensivly with all the applications en games that used to cause the error. No problems yet. I 'll keep on testing this configuration for a week. Then I will do the same with the replaced module to check of one of them is bad or that the problem lies elsewhere. With the two modules in place I had also problems with running them on the advertised speed. Without increasing the RAM-voltage the system rebooted by it self, especially when cold. Does that makes sense to anyone? conf: AMD A8-3870 Asrock A75M-HVS RAM Corsair CML8GX3M2A1600C9 NO graphic card.

i have this problem too ,,Display driver Amd radeon stoped working and successefully recovered back,i..i try everything,update last driver..fix registry keys,all advice i find on net..i watch tempts...clean my fan and heatsink..but nothing help,and i have it until 15minutes ago...this post help me fix problem,i have acer aspire 4gb ram...i just reduces 2gb ram and now have 2gb ram and its work perfect for now...i will tell if problem come back,but sure i dont want it back..so if someone have this problem pls try do the same thing,maybe it help you..and good luck with it. but can this problem with ram fix and what led up to the problem to appear ,can i upgrade my ram to 4gb again,and if someone know how fix that problem..??

You do seem to have a good comprehension of what the TDR is - " Seems like the only thing the message tells you is the driver involved, but not much else." and realise a TDR can be caused by many things. However, this thread has gone on far too long and has to many people adding more questions who have different systems and software setups, and who think they all have the same issue because they get the TDR error message. This is unfortunately incorrect, just as it would be if they were experiencing BSOD instead of the error that is meant to keep people from getting premature BSOD (TDR is a failed attempt at this). There is no one fix for TDR. Personally, I reckon this thread should be closed, and people need to start their own as they will get better attention from respondents on these forums if they do so. With so many questions it's difficult to target a single poster (asking a new question is often called hijacking for this reason). May I suggest you start a new thread and also include your system specifications and what fixes you have tried with the information you posted here (avoids you having to read suggestions that you have already read/tried). I will leave other comments and suggestions out for now as it would only encourage more posters with more questions, rather than more suggestions for fixes. I lied ;) - If you are not having problems with games tweaking up the gpu voltage will not help as games are more system intensive than photo editing. A voltage tweak is generally only required on a factory overclocked card (due to not all gpu's being equal, or well selected for these cards) . btw - There are no Monopoly$oft employees on this forum. .

Hi Everyone. I recently built a new system from scratch (except the monitor, which is inconsequential to this problem) and, using Win8 Pro 64-bit, am experiencing this problem intermittently. While I have done some gaming since the build (LOTRO MMO, Skyrim, Oblivion, Stalker, etc...) I have yet to experience the issue during one of those sessions. Where I have experienced it often is when editing photos using Windows Photo Gallery. I'm not sure if this points to any single cause but the one that comes to mind is where I've read previously in this thread about power to the GPU (voltages?). I am currently in the process of cleaning/updating all my drivers (a task I was planning anyway) and while I don't believe it will solve the problem, I will certainly post any info if it's at all helpful. Seems like the problem here is that there is no one from MS either contributing to or watching this thread (issue). It seems reasonable to think that an interim solution is to, at the very least, create some addition logging around the event. Seems like the only thing the message tells you is the driver involved, but not much else.

“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

2012-12-15T12:18:11+00:00

Yesterday I removed one of my 4 gb memory modules. Until know everthing works fine. I have tested it extensivly with all the applications en games that used to cause the error. No problems yet.

I 'll keep on testing this configuration for a week. Then I will do the same with the replaced module to check of one of them is bad or that the problem lies elsewhere.

With the two modules in place I had also problems with running them on the advertised speed. Without increasing the RAM-voltage the system rebooted by it self, especially when cold.

Does that makes sense to anyone?

conf:

AMD A8-3870

Asrock A75M-HVS

RAM Corsair CML8GX3M2A1600C9

NO graphic card.
Was this answer helpful?

0 comments No comments
Anonymous

2012-12-11T13:16:41+00:00

i have this problem too ,,Display driver Amd radeon stoped working and successefully recovered back,i..i try everything,update last driver..fix registry keys,all advice i find on net..i watch tempts...clean my fan and heatsink..but nothing help,and i have it until 15minutes ago...this post help me fix problem,i have acer aspire 4gb ram...i just reduces 2gb ram and now have 2gb ram and its work perfect for now...i will tell if problem come back,but sure i dont want it back..so if someone have this problem pls try do the same thing,maybe it help you..and good luck with it.

but can this problem with ram fix and what led up to the problem to appear ,can i upgrade my ram to 4gb again,and if someone know how fix that problem..??
Was this answer helpful?

0 comments No comments
Anonymous

2012-12-06T05:50:26+00:00

You do seem to have a good comprehension of what the TDR is -

" Seems like the only thing the message tells you is the driver involved, but not much else."

and realise a TDR can be caused by many things.

However, this thread has gone on far too long and has to many people adding more questions

who have different systems and software setups, and who think they all have the same issue because they get the TDR error message.

This is unfortunately incorrect, just as it would be if they were experiencing BSOD instead of the error that is meant to keep people from getting premature BSOD (TDR is a failed attempt at this).

There is no one fix for TDR. Personally, I reckon this thread should be closed, and people need

to start their own as they will get better attention from respondents on these forums if they do so. With so many questions it's difficult to target a single poster (asking a new question is often called hijacking for this reason).

May I suggest you start a new thread and also include your system specifications and what fixes you have tried with the information you posted here (avoids you having to read suggestions that you have already read/tried).

I will leave other comments and suggestions out for now as it would only encourage more

posters with more questions, rather than more suggestions for fixes.

I lied ;) - If you are not having problems with games tweaking up the gpu voltage will not help

as games are more system intensive than photo editing. A voltage tweak is generally only

required on a factory overclocked card (due to not all gpu's being equal, or well selected for

these cards) .

btw - There are no Monopoly$oft employees on this forum.

.
Was this answer helpful?

0 comments No comments
Anonymous

2012-12-05T16:49:15+00:00

Hi Everyone. I recently built a new system from scratch (except the monitor, which is inconsequential to this problem) and, using Win8 Pro 64-bit, am experiencing this problem intermittently. While I have done some gaming since the build (LOTRO MMO, Skyrim, Oblivion, Stalker, etc...) I have yet to experience the issue during one of those sessions. Where I have experienced it often is when editing photos using Windows Photo Gallery. I'm not sure if this points to any single cause but the one that comes to mind is where I've read previously in this thread about power to the GPU (voltages?). I am currently in the process of cleaning/updating all my drivers (a task I was planning anyway) and while I don't believe it will solve the problem, I will certainly post any info if it's at all helpful.

Seems like the problem here is that there is no one from MS either contributing to or watching this thread (issue). It seems reasonable to think that an interim solution is to, at the very least, create some addition logging around the event. Seems like the only thing the message tells you is the driver involved, but not much else.
Was this answer helpful?

0 comments No comments