brettjv

Good call, Mike.

First thing I usually do with a new card is find out all the possible straps within a couple hundred MHz above my stock speeds (using the sliders/rivatuner graphs, I slowly increase/apply changes, one at a time, just to see which discreet clocks the graphs tell me the card is able to run at), and then jot them all down, so I'll always know what they are. This concept of straps applies not just to shaders, but to all three clocks, just so you know. Once you start watching the RT graph application, you'll start to understand what we mean by 'straps', if you don't already.

This is always helpful later, when I actually go to do the stability tests, I won't accidentally test the same 'step' (aka the same actual speed, as opposed to what the slider says, which is really just an approximation) twice.

Other than that, though (and it's just 'how I do it', not what's right or wrong ) your instructions sound great man!

Oh, and BTW ... yeah, ATITool pretty much always will give you the idea that your card is stable at higher clocks than it really is. Try running a few Crysis benches, and a couple runs of 3dMark06, if you wanna really check to see if you're stable...

__________________
3dMark06: 26,490
http://service.futuremark.com/compare?3dm06=11655839

WaLshy11

hmm so I have to increase the shader by 54mhz each time?
What about core clock and memory clock? Are they fine to increase a little bit instead of a massive jump?