Registry GURU needed, apply within

OldBuzzard · May 27, 2008, 11:51 PM

Gentlemen (and Grace)

I would like to add a couple of registry entries, that will help get a handle on the ongoing TDR problem in Vista.

MS has a page showing some Reg tweaks, but I'm not savvy enough to actually make those entries.

Would someone that has the knowledge please make up a .reg file that I can use to add them to my Registry?

The MS page is here: http://www.microsoft.com/whdc/device...m_timeout.mspx

Now, I have more than one OS installed, so if I bugger up the one I put the reg tweaks in, I've lost nothing. My Vista 64 OS is a "throw away" one, so even if what I get makes the OS unusuable, I won't be stressed.

Grace · May 28, 2008, 01:05 PM

I could make those entries for you tonight, but the MS page is showing all of the options you could set, not something specific. Can you describe the problem exactly or what you'd like to do?

OldBuzzard · May 28, 2008, 04:55 PM

Grace,

I'd like to try two things.

1. Turn off TRD all together, which appears to be this one:
•TdrLevel: REG_DWORD. The initial level of recovery. The possible values are:
•TdrLevelOff (0). – Detection disabled

2. Give the GPU just a bit more time to respond before the TRD is issued. I think this one does that:
TdrDelay: REG_DWORD. The number of seconds that the GPU is allowed to delay the preempt request from the scheduler. This is effectively the timeout threshold. The default value is 2.

I'm working on the theory that with all the possible hardware combinations there are, that Vista is too aggressive in issuing the error. I think that for some combinations, the various tolerences combine to make Vista think that an error has occured when it's just a matter of the proper data not getting there fast enough.

Grace · May 29, 2008, 08:10 PM

I made an .reg file for you, here it is:

TRD Test.zip

It will turn TRD off completely but will also increase the TRD delay time to 20 seconds (in case the kill entry doesn't work).

OldBuzzard · May 31, 2008, 05:41 PM

Thank you dear

I tried to send a little rep your way, but not sure if it worked or not

It said something to the efect that I couldn't give rep 2x in the same thread

I've installed, and played with the settings some...you can see results in the "Big Sticky"

Grace · May 31, 2008, 08:09 PM

Quote:

Originally Posted by OldBuzzard

It said something to the efect that I couldn't give rep 2x in the same thread

Of course it does; it worked the first time.

You're welcome.

May 27, 2008, 11:51 PM	#1
OldBuzzard DH's oldest Geek Join Date: May 2003 Location: Oberlin, OH Posts: 2,783 Rep Power: 145 System Specs	Registry GURU needed, apply within Gentlemen (and Grace) I would like to add a couple of registry entries, that will help get a handle on the ongoing TDR problem in Vista. MS has a page showing some Reg tweaks, but I'm not savvy enough to actually make those entries. Would someone that has the knowledge please make up a .reg file that I can use to add them to my Registry? The MS page is here: http://www.microsoft.com/whdc/device...m_timeout.mspx Now, I have more than one OS installed, so if I bugger up the one I put the reg tweaks in, I've lost nothing. My Vista 64 OS is a "throw away" one, so even if what I get makes the OS unusuable, I won't be stressed. __________________ When looking for a reason as to why things go wrong, never rule out sheer STUPIDITY

May 28, 2008, 04:55 PM	Thread Starter #3
OldBuzzard DH's oldest Geek Join Date: May 2003 Location: Oberlin, OH Posts: 2,783 Rep Power: 145 System Specs	Grace, I'd like to try two things. 1. Turn off TRD all together, which appears to be this one: •TdrLevel: REG_DWORD. The initial level of recovery. The possible values are: •TdrLevelOff (0). – Detection disabled 2. Give the GPU just a bit more time to respond before the TRD is issued. I think this one does that: TdrDelay: REG_DWORD. The number of seconds that the GPU is allowed to delay the preempt request from the scheduler. This is effectively the timeout threshold. The default value is 2. I'm working on the theory that with all the possible hardware combinations there are, that Vista is too aggressive in issuing the error. I think that for some combinations, the various tolerences combine to make Vista think that an error has occured when it's just a matter of the proper data not getting there fast enough. __________________ When looking for a reason as to why things go wrong, never rule out sheer STUPIDITY

May 31, 2008, 05:41 PM	Thread Starter #5
OldBuzzard DH's oldest Geek Join Date: May 2003 Location: Oberlin, OH Posts: 2,783 Rep Power: 145 System Specs	Thank you dear I tried to send a little rep your way, but not sure if it worked or not It said something to the efect that I couldn't give rep 2x in the same thread I've installed, and played with the settings some...you can see results in the "Big Sticky" __________________ When looking for a reason as to why things go wrong, never rule out sheer STUPIDITY

May 28, 2008, 01:05 PM	#2
Grace HH's Tomboy Join Date: Nov 2005 Location: Anywhere but in my house! Posts: 776 Rep Power: 56	I could make those entries for you tonight, but the MS page is showing all of the options you could set, not something specific. Can you describe the problem exactly or what you'd like to do?

May 29, 2008, 08:10 PM	#4
Grace HH's Tomboy Join Date: Nov 2005 Location: Anywhere but in my house! Posts: 776 Rep Power: 56	I made an .reg file for you, here it is: TRD Test.zip It will turn TRD off completely but will also increase the TRD delay time to 20 seconds (in case the kill entry doesn't work).