Originally Posted by Sprkd1
How is this different from my GTX 560 Ti 448 Cores downclocking itself at the desktop and then running at "real clocks" during games?
Have a look at this screenshot (again
) and you'll discover Kepler OC'ing works very differently from your card.
Notice how the AB OSD shows my card running at 1337MHz? Now, look at GPU-Z ... do you see 1337MHz anywhere on the front? Nope, you don't. The highest core clock number you see is the current Boost Value, which is 1207MHz. The additional OC is 'dynamic overclocking' that Kepler does. I call this magical +130MHz discrepancy the 'Kepler Boost' value for my card. Every individual sample has it's own Kepler Boost value (although they're in steps of 13MHz, ranging from 0 to 235 based on reports on these boards), and this represents the MHz amount above the listed 'Boost' value (the one in GPU-Z) that your card will actually run at when under load. Fermi has no such dynamic overclocking ... your 3d clock is what you set it to, period.
Notice also that overclocking in Precision X no longer involves setting a specific clock like it does on your card, but rather, it involves an 'offset' value (+148 in my case here) instead.Edited by brettjv - 6/28/12 at 11:27am