• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

6800 GT overclocking weirdness

icebird0

Junior Member
I'm using the 66.93 drivers. I've overclocked both 2D and 3D to Ultra speeds (400/1100) using Coolbits. When playing games the system will sometimes pause for a few seconds and the core clock will revert to 350. After exiting the game the core will return to 400 (as captured by RivaTuner).

Anyone else had this problem and/or have any idea why this is happening? Should I mod the bios to 400/1100 so that it doesn't even know about the 350 default?
 
Sounds to me like perhaps there is an instability problem with the higher speeds. When running it through the various 3dmark tests do you notice any artifacting?
 
Its probably a heat problem and is underclocking to keep from frying or something. Its probably not good to mod the bios because you might damage it
 
Other than this random auto-downclocking I haven't had any other stability problems and haven't noticed any artifacts in 3dmark05 or games. I wouldn't think that it's a heat problem either because the core only gets up to the high 60s under load (including when it auto-downclocks).

It occured to me that I have this problem most often when playing the new Medal of Honor Pacific Assault MP demo. Is it possible that a particular game could be sending instructions to the card that ultimately cause it to reset the core clock to the bios default? MOHPA doesn't appear to be the, uh, most elegantly coded game. 😉

I played for a few hours today and didn't see this problem at all. It seems to occur only once or twice every few days. If it gets any worse I'll probably look into using OmniExtremeEdit FX to modify the default core and memory clocks in the bios rom before flashing it. I would hope that would solve the problem. 😀
 
Back
Top