I have been out of the game for a while but have recently decided to build a very, very budget system.
Don't laugh....
CPU - G620
VID - 6770 DDR5 1GB
Ram -8gb Kingston value
Board - ASUS P8H61-M LE/USB3
Ok.... Once you have stopped laughing. I did say budget!
Now for the story.
When I saw most components running around 20c I decided to turn things up a little. Yep! Old habits die hard. The Sapphire VID over-clocked easily with the overdrive utility so no problems there. I then had a go at the CPU. I ran the BIOS autotune and gained an extra 100Mhz at a base frequency of 103Mhz.
Once I was in windows I ran up the TurboV EVO utility. I ran the auto tune from windows and ended up with the same 103Mhz base clock setting. I then manualy adjusted the base clock to 107 and CPU voltage 1.21 and supprisingly the settings took leaving me with a 2.8 Ghz CPU. I tested quite a few runs of 3D mark and a few games and everything seemed stable and still reasonably cool. Happy with my efforts I saved the overclocked profile in TurboV. 3Dmark gained a subtle improvement with the jump from 2.7Ghz to 2.8Ghz and reports the CPU as a G620 @ 28xx Mhz. I wish I had a web link but apparently my display driver is not WHQL.
Now for the weird bit.
If I soft reset the system the 107Mhz settings stick and everything is good. If I do a cold reset then the system will revert back to 103Mhz BCLK.
After the cold reset I attempted to apply the saved 107Mhz profile and windows froze. I then tried the same settings directly in the BIOS and the system froze. Somewhat perplexed, I discovered the only way to get the previous 107Mhz settings to run was to run an auto tune from windows again and then apply the 107 BCLK settings. Once again the system runs very well and stably at just over 2.8Ghz. This is somewhat annoying as I have to do this each time the system is powered off if I want to use the higher settings.
Does anyone have any idea what might be going on? From everything I have read, I should not be able to run a 107Mhz BCLK on this system anyway. So, why does it appear to work and why does it only work after an autotune has been run from TurboV?
Don't laugh....
CPU - G620
VID - 6770 DDR5 1GB
Ram -8gb Kingston value
Board - ASUS P8H61-M LE/USB3
Ok.... Once you have stopped laughing. I did say budget!
Now for the story.
When I saw most components running around 20c I decided to turn things up a little. Yep! Old habits die hard. The Sapphire VID over-clocked easily with the overdrive utility so no problems there. I then had a go at the CPU. I ran the BIOS autotune and gained an extra 100Mhz at a base frequency of 103Mhz.
Once I was in windows I ran up the TurboV EVO utility. I ran the auto tune from windows and ended up with the same 103Mhz base clock setting. I then manualy adjusted the base clock to 107 and CPU voltage 1.21 and supprisingly the settings took leaving me with a 2.8 Ghz CPU. I tested quite a few runs of 3D mark and a few games and everything seemed stable and still reasonably cool. Happy with my efforts I saved the overclocked profile in TurboV. 3Dmark gained a subtle improvement with the jump from 2.7Ghz to 2.8Ghz and reports the CPU as a G620 @ 28xx Mhz. I wish I had a web link but apparently my display driver is not WHQL.
Now for the weird bit.
If I soft reset the system the 107Mhz settings stick and everything is good. If I do a cold reset then the system will revert back to 103Mhz BCLK.
After the cold reset I attempted to apply the saved 107Mhz profile and windows froze. I then tried the same settings directly in the BIOS and the system froze. Somewhat perplexed, I discovered the only way to get the previous 107Mhz settings to run was to run an auto tune from windows again and then apply the 107 BCLK settings. Once again the system runs very well and stably at just over 2.8Ghz. This is somewhat annoying as I have to do this each time the system is powered off if I want to use the higher settings.
Does anyone have any idea what might be going on? From everything I have read, I should not be able to run a 107Mhz BCLK on this system anyway. So, why does it appear to work and why does it only work after an autotune has been run from TurboV?