Manual Overclocking And TurboV EVO
We used the overclock settings from our P8Z68 Deluxe firmware description to set Intel’s Core i7-2600K to 4.73 GHz at 1.35 V. Actual settings include a 1.335 V CPU core with “Extreme” Load-Line Calibration at a 47x multiplier and 100.5 MHz BCLK.
Asus’ class-leading memory overclocking capability allowed us to simultaneously use our memory’s XMP-2200 values to reach DDR3-2145.
Asus TurboV EVO requires one reboot to enable live ratio changes from Windows. A few of the firmware’s clock and voltage settings are repeated here, though the software’s maximum overclock came up around 100 MHz short of what we were able to demonstrate using the firmware to dial in our desired settings.
Changes to the CPU core voltage showed up in both CPU-Z and Asus Probe II, but were not reflected in the TurboV EVO menu. This might be because we set the board's BIOS to fixed (rather than offset) mode. We believe the relatively large delta in overclocking capability between software and firmware settings is most likely due to differences in “Load-Line Calibration” between automatic (software) and manual (firmware) adjustment methods.
Current page: Manual Overclocking And TurboV EVOPrev Page Asus OC Tuner Next Page Gigabyte Smart QuickBoost
Stay on the Cutting Edge
Join the experts who read Tom's Hardware for the inside track on enthusiast PC tech news — and have for over 25 years. We'll send breaking news and in-depth reviews of CPUs, GPUs, AI, maker hardware and more straight to your inbox.
auto overclocking is not a good think IMO, its asking for trouble. How many RMA's do motherboard & CPU companies want when this doesnt work properly?Reply
I have a Asrock z68 Pro 3 MB, and after trying out auto overclocking the system only worked stable until 4,3 Ghz (core i7 2600k). I had to do manual settings to make my CPU stable @ 4,5 GhzReply
I don't like anything assuming anything.Reply
Automatic overclock blows for 2 reasons.Reply
1) It either is super conservative and therefore useless for any enthusiast.
2) It is insanely over-aggressive because it doesn't bother testing stability for more than a few minutes (if at all). So you end up with it thinking a 50% overclock is "stable" when it totally isn't.
When I tested the Gigabyte utility to overclock the only area I found problems in was the peak core voltage, I soon noticed the CPU idle temps were way too high.Reply
Turned out that with all other settings as chosen by the utility the peak core could be set to its lowest value in the BIOS and still be perfectly stable. So is it just ramping up the voltage to be on the safe side?
Isn't changing the default BCLK frequency supposed to be dangerous? Why do so many sites seem to promote changing it?Reply
ASRock's auto OC'ing on the P67 Extreme6 is excellent with my 2500K. I achieved a 4.8 GHz OC, a 4.6, 4.4, 4.2 & 4.0 with the auto settings. The voltage stayed under 1.36 on all of these OC settings.Reply
I have downclocked my system to base settings on both the CPU and GPU because the wear on the system with OC'ing. None of the games I play, nor any of the other apps need a OC to perform well, so why place additional stress on the components when it is merely for bragging rights?
When I played with manual OC'ing I found, like this article, that there was only a marginal gain from auto settings. Plus ther is the additional risk of screwing the pooch entirely and bricking the CPU or mobo by overvolting.
Unless you are a real pro and are not risk adverse, I'd recommend that you stick with auto OC'ing, and for this, ASRock has proven to be the best.
@Chesteracorgi, you don't need to be a pro to OC your CPU. They have guides on Overclocking every CPU around, very easily and effectively.Reply
I feel that Toms should have done some stability testing on their manual and automatic OCed Processors. They might have and just not posted their results. I am in the camp where I feel that if you can't take the hour or two to figure it all out you probably shouldn't be Overclocking. If we had a larger sample of Proccessors we have no idea how many would turn out badly.
It looks like a good tool to start off your own OC because it's probably gonna be in the ballpark, but on it's own it leaves much to be desired.
Question... Was the same CPU used in all tests? If so, it seems untrue to say that "CPU's" shouldn't have more than 'n' voltage when the Mobo's are presenting different internal loads, right? You stated that manually you can get 4.67 GHz at 1.35 V on board 'x'. If the CPU is consistnat in all tests, 1.35V should ba ample force to get 4.67 on ANY Motherboard with that CPU right?... but you couldn't. My point being different mobo's require more "push" there by making it harder for me to fault autoOC programs for cranking up voltage past "comfy" limits when, for all we know, they are taking into account higher internal loads. There is a variable missing someplace. Like 1.375v is risky on type "A" mobos but type "B" mobos can go to 1.4V. I don't know.. am I making any sense here? It just seems some piece of the puzzle is missing....Reply
just wondering i7 series 900 apply the same rule?? less than 1.4v safe, more is a certain death??Reply