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

"reverted my google theme to default" Hmm - Maybe this ? Yet another example of why persistant TDR can be so difficult to fix. Good to hear it's going well.

OK its been about a week since i did the things that i did on my PC. and the problem seems to had went away this whole week of usage. I dont know exactly what I did that was the cure. But after stooping around like a crazy maniac I tried what some people say etc., since my kernel issue didnt pop up with gaming or any other programs except google. I figure they are the culprit! Anyways things ive done was the Microsoft Fixit where they change the TDR delay but that still gave me some kernel issues when using google. So i went further and uninstalled Java and Flash and reverted my google theme to default. And thats it! Its been a week and no popups!! im cured!!! /knocksonwood!

I hadn't seen the part about disabling the PCIe link state before. Hope it keeps your TDR's at bay. 'Off' looks to be the default setting for the High Performance option on my machine. I've been using a Balanced power plan (monitor off after 15min and Sleep after 25min), and just looked and see my PCIe is set to Moderate power savings, which I also assume is default for the Balanced power plan. I've noticed High Performance is a common power setting suggestion for laptops when running games. Interesting that you didn't get a TDR with a game running. I believe the few TDR's I've experienced where with games pushing the system. It does look as if the TDR 'solution' to premature BSOD is one of those 'seemed like a good idea at the time' things, and while a BSOD can be equally frustrating to troubleshoot, at least you only had to deal with one error system. Looking further into the article I notice they mention down clocking the RAM speed. This is something that caught me out a couple of years ago. I was unaware that some speeds are considered OC speed even though it was not advertised as such, so while DDR3 1600MHz was heavily marketed they didn't say that you had to OC the cpu to get over 1333MHz stable. I had a long discussion on the Corsair forums about their marketing tactics in relation to that. I see the motherboard mfg's are advertising certain RAM speeds with an (OC) lately.

I was getting the tdr blank screen every minute or so but I could open planetside 2 and just leave it running and it never did it. Here is what I did and it hasn't done it in almost two hours now. I used solution number one from this website. http://www.instructables.com/id/How-to-Fix-the-Nvlddmkm-Error/ It has worked so far, it is a microsoft os glitch, has too be. This problem is plastered all over the net and it's all kinds of computer types etc. Anyway, so far solution 1 has fixed it. I'll repost if it screws up or if it doesn't in a couple of days. I hope this helps someone, this is the stupidest problem I have ever encountered in 20 years of computing and building.

“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

2013-04-06T02:24:36+00:00

"reverted my google theme to default"

Hmm - Maybe this ? Yet another example of why persistant TDR can be so difficult to fix.

Good to hear it's going well.
Was this answer helpful?

0 comments No comments
Anonymous

2013-04-05T05:53:51+00:00

OK its been about a week since i did the things that i did on my PC. and the problem seems to had went away this whole week of usage. I dont know exactly what I did that was the cure. But after stooping around like a crazy maniac I tried what some people say etc., since my kernel issue didnt pop up with gaming or any other programs except google. I figure they are the culprit! Anyways things ive done was the Microsoft Fixit where they change the TDR delay but that still gave me some kernel issues when using google. So i went further and uninstalled Java and Flash and reverted my google theme to default. And thats it! Its been a week and no popups!! im cured!!! /knocksonwood!
Was this answer helpful?

0 comments No comments
Anonymous

2013-04-03T08:51:03+00:00

I hadn't seen the part about disabling the PCIe link state before. Hope it keeps your TDR's at bay.

'Off' looks to be the default setting for the High Performance option on my machine.

I've been using a Balanced power plan (monitor off after 15min and Sleep after 25min), and just looked and see my PCIe is set to Moderate power savings, which I also assume is default for the Balanced power plan.

I've noticed High Performance is a common power setting suggestion for laptops when running games.

Interesting that you didn't get a TDR with a game running. I believe the few TDR's I've experienced

where with games pushing the system.

It does look as if the TDR 'solution' to premature BSOD is one of those 'seemed like a good idea at the time' things, and while a BSOD can be equally frustrating to troubleshoot, at least you only had to deal with one error system.

Looking further into the article I notice they mention down clocking the RAM speed. This is something

that caught me out a couple of years ago. I was unaware that some speeds are considered OC speed

even though it was not advertised as such, so while DDR3 1600MHz was heavily marketed they didn't

say that you had to OC the cpu to get over 1333MHz stable. I had a long discussion on the Corsair

forums about their marketing tactics in relation to that.

I see the motherboard mfg's are advertising certain RAM speeds with an (OC) lately.
Was this answer helpful?

0 comments No comments
Anonymous

2013-04-02T16:41:38+00:00

I was getting the tdr blank screen every minute or so but I could open planetside 2 and just leave it running and it never did it. Here is what I did and it hasn't done it in almost two hours now. I used solution number one from this website.

http://www.instructables.com/id/How-to-Fix-the-Nvlddmkm-Error/

It has worked so far, it is a microsoft os glitch, has too be. This problem is plastered all over the net and it's all kinds of computer types etc. Anyway, so far solution 1 has fixed it. I'll repost if it screws up or if it doesn't in a couple of days. I hope this helps someone, this is the stupidest problem I have ever encountered in 20 years of computing and building.
Was this answer helpful?

0 comments No comments