Blo*dy d*mn that Technet site. I keep getting a script error relating to Chrome when I'm using Firefox.
Made me loose my post. The only site that does this is the MS 'super' tech site .
Anyway ... (looks like I lost your thread in the shuffle) -
"The main suggestion here is to change the registry so that windows no longer has timeout detection on your graphics card. I am somewhat skeptical that this will solve my problem because"
I went over TDR a bit before but didn't mention the relationship to graphics lag.
MS set a 2 sec lag before TDR is initiated. While this sounds like a long time I believe a 2 sec lag may not always manifest as a visual lag on screen for anything like that long a time.
2 sec may be OK for general use, but it is a big FAIL for gamers. TDR has caused untold gamer angst.
- I reckon the best registry fix is not to disable TDR, as TDR can still protect the system (theoretically),
but to set a longer time. TDR and BSOD are closely related so while it may not help in this instance,
using a longer time just may help.
I've been using 5 sec for several years (but MS have recommended 8sec in recent times).
I have noticed a time or three when I thought the longer time has stopped a game having a TDR crash
because I could actually see a brief hang before the game moves on.
Open regedit then -
Navigate to -
H_KEY_LOCAL_MACHINE \ System \ CurrentControlSet \ Control \ Graphics Drivers.
Right click on the open field and click on New / DWORD (32bit) Value,
Then name it: TdrDelay -> double click it -> Set the value to 5.
I've only had a couple of TDR since starting with Win7 and using the 5sec timer.
With those games I found that lowering the games resolution one notch stopped the TDR.
This was with Skyrim and Crysis 2.
With Crysis 2 the gpu use dropped (from memory) from 99% to about 97%.
What exactly do you mean by "Post Beeps"?
Power on self test -
Those are the error beeps that happen if something is wrong when you boot into Windows .
These beeps will come between power on the machine and Windows loading.
There is the normal beep, but there are also error code beeps which include short and long beeps
in combination or just one long beep (memory problem if I remember correctly - I usually have to look
it up when something goes wrong ;D )
Sometimes Windows will still load, but with the gpu the card will not function properly, if at all,
but you will hear the beep code before Windows loads.
When there is a Post beep error relating to the gpu it's usually because the card is not fully seated,
or there is a speck of dust in the slot. In this instance the card may function until it is under load.
btw - With Speccy you can post a report to a 'unique' URL that the program creates when you use the
option 'Publish Snapshot'. You just copy and paste the URL to your post.
- I'd thought Speccy showed +12V as well, but apparently not.