“Display driver stopped responding and has recovered” error.

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.

"set the TDR values to 0 instead of the default 2"

Which key are you referring to ? With the TdrDelay  key,  2  was the original default value = 2sec ,

so setting it to 0 means you should have a higher likelihood of a TDR.

Setting the TDR value up to 8 or 10 (I set mine to 5) should be adequate in regard to it being too sensitive.

To disable TDR  you would use the following key (so I've read. No need to try it yet) -

 -HKLM\System\CurrentControlSet\Control\GraphicsDrivers.

-Add following  DWORD    TdrLevel

• Set the value to  0 .

However, disabling TDR is more likely to end up with what the TDR is supposed to prevent, a BSOD.

Well,  it's not supposed to prevent BSOD altogether, just premature BSOD's caused by a lag in the system.

• But, there could be an advantage to getting a BSOD over a TDR . I'm not positive, but if there

is no dump file created when a TDR occurs then the dump file created from a BSOD could reveal

the real cause of the TDR's.

Check your Windows  \ minidump  folder and see if there are any dmp files. If so, upload them along

with your  msinfo32  file  to  Skydrive for analysis (Starting a new thread in the Hardware or Performance forums would better than carrying on with this old thread).

I'm not going to be simplistic as PH was earlier with his fix that was supposed to work for everyone

(everyone downloads a virus from a torrent site ? ).

As I said earlier. There is no one fix, and I can't really add to all those options that you guys may have tried (especially without know everything you have tried). I can only reiterate - Don't keep hammering

away at installing different  graphics drivers. Particularly when you have installed Windows fresh.

Using Firefox 11.0  here. Never tried Chrome. My Nvidia Machine currently has the 310.90 driver

and my ATI machine has the 13.1 driver, but I've never used any driver that caused TDR or BSOD.

I have had a corrupt driver install, but not a faulty driver.

So, if both of you (dlvrd and Marc) are getting TDR with only the basic system install  -

eg- Windows updates (don't do the 'optional' updates), system drivers, browsers, AV and a game or

two and are still experiencing TDR,  then  you still should  verify there are no software/services conflicts

by running via Clean Boot -

How to troubleshoot a problem by performing a clean boot in Windows Vista or in Windows 7

Still getting TDR ? It's looking more like hardware fault somewhere. While re-flowing the solder on

a motherboard has been know to do wonders, it will not fix leaking capacitors or borked PCIe slots.

It all has to be checked - HDD, gpu, RAM , the lot. I believe I also mentioned gpu voltage tweaks and

psu's in  an earlier post.

More reading -

NVIDIA Statement on TDR Errors - NVIDIA Forums

The nvlddmkm error - What is it? - NVIDIA Forums

.

I have reformatted, installed a variety of display drivers, re-flowed the solder on the motherboard in my oven at 385 degrees Fahrenheit, and some other checks. I don't know what else to do so if you figure something out please post the solution here.