The adjustment of the multiplier has no impact.
The adjustment of the multiplier has no impact.
Hi,
I'm just starting out with Overclocking and after reading an Ivy Bridge guide, I'm struggling to understand what I'm doing incorrectly and why my settings aren't working as expected.
What I've tried so far: Turbo Boost is enabled, so that's not the issue. I changed the power plan in Windows to Balanced, switched to offset mode with +005%, and set the multiplier to Manual, which seems to disable Turboboost for some reason.
Using Asus AI Suite to overclock with TurboV EVO, Digi, and Power Control works fine at a multiplier bump of 41. However, my Vcore voltage drops to 1.321, and temperatures reach around 70°C. I'm hoping to see if adjusting BIOS settings can improve the results.
Details: i5-3570k, Asus P8Z77-V, Corsair H100i GTX, G-skill Ripjaws 8GB (1600Mhz), Cl9, Corsair HX-650W Pro Modular PSU.
My UEFI BIOS settings show 1600MHz because I'm on the Balanced power plan during high performance mode; with my own plan it's 3400Mhz stock.
Apologies for the low quality, I couldn't find a USB stick for screenshots.
Thanks in advance.
kYmo :
no improvement detected by CPUZ. I tested various power plans in Windows and ran Prime95 for stress testing; it still reports a strange 3.5Ghz reading. Also, when I set the multiplier to 41 with EIST and Turbo off, it re-enables automatically unless I revert the BIOS back to defaults. The first step I recommended was clearing the CMOS. Not just restoring defaults, but completely wiping all BIOS changes at a hardware level. This avoids conflicts from forgotten or random settings. Check your CPU-Z screenshot—look for the line saying "Multiplier x 16.0 (16-35)". Why 35? The maximum stock clock speed is actually 34. If there was some advanced turbo activation, it should show 16-38 instead.
What do you mean by not taking effect?
Turbo Boost should be turned off when you change the multiplier.
Since the CPU speed remains at the stock multiplier, and I thought online that Intel Turbo Boost needs to be enabled for any changes to work, are you correct in thinking I was mistaken?
According to what I understand, there are two main approaches for overclocking Intel processors. The first involves pushing the CPU to its limits by disabling all power-saving features and voltage controls, maintaining a steady voltage, adapting for VDroop or using LLC, and running it nonstop at full capacity. This method is typically used for AMD CPUs as well, for beginners, and for extreme cooling setups where stable performance is crucial. The second approach uses a turbo boost that activates only after the system reaches a certain threshold, allowing you to apply your overclock manually. I’m not sure which guide you followed, but I recommend keeping the CPU voltage at auto unless you need precise adjustments. Use offset mode for fine-tuning and avoid changing settings blindly—it can harm both you and your machine. Here’s what I suggest: clear CMOS, disable EIST, Intel Speedstep, Turbo Boost, and C states; set Load Line Calibration to a more aggressive setting; apply all multiplier changes directly to the CPU Ratio field; adjust voltage only in offset mode if needed; turn off XMP until stability is achieved; and proceed slowly, as this process requires time.
Amtsseung:
According to what I understand, there are two main approaches for overclocking Intel processors. The first involves pushing the CPU to its absolute limits by disabling all power-saving settings and voltage controls, maintaining a steady voltage, adapting for VDroop or using LLC, and continuously running it at full capacity. This technique is typically used for AMD CPUs as well, for beginners, and for extreme cooling setups where stability is crucial. The second approach uses a turbo boost that activates only when the turbo feature is triggered, allowing the CPU to reach its maximum speed after the boost kicks in. This method seems more suitable for advanced users who want better control over stability.
I’m not certain which guide you were using, but I’d keep the CPU voltage set to auto. If you need precise tweaks, consider using offset mode. For testing stability, adjust the Load Line Calibration settings slightly before manually changing any voltage. Leave the CPUID maximum unchanged.
TBH, I’d suggest starting with the first method if you’re new to overclocking. It’s simpler and avoids many complications. Changing settings without understanding them can harm your CPU or computer. Here’s what I recommend:
1.) Reset CMOS.
2.) Turn off EIST, Intel Speedstep, Turbo Boost, and C states.
3.) Adjust the CPU Load Line Calibration to a more aggressive setting (medium or above).
4.) Apply all changes directly to the CPU multiplier field, not Turbo Ratio.
5.) Make voltage adjustments only in offset mode if needed.
6.) Disable XMP until you achieve a stable overclock. XMP can interfere with settings.
7.) Be patient—this process requires time and practice.
Thanks for your reply! I also tried LLC on Medium initially but switched to regular mode to check the issue, and I had C states disabled besides the first one. The guide I followed is what I used:
http:// (sorry if linking isn’t allowed)
That’s the kind of overclock I aimed for, which activates only when turbo kicks in for power savings at idle. I don’t see the need to keep the voltage high all the time or have the CPU always at 100%.
Also, when offset mode is enabled, manual Vcore adjustments aren’t possible—it’s grayed out. Is this normal?
I’ll try the methods you suggested and follow up with results.
KYmo:
Thank you for your reply!
I initially used an LLC on Medium to test first, but switched to a regular setup to check if that was the issue. I also disabled the C states except the first one. Here’s the guide I followed:
http://
(sorry if linking isn’t allowed)
That matches what I was aiming for—just to see if it triggered the overclock only when turbo activated for power efficiency during idle. I thought keeping the Vcore high all the time and having the CPU at 100% with an OC would waste the processor sooner.
Also, when offset mode is enabled, I can’t manually adjust the Vcore—it’s grayed out. Is this typical?
I’ll try the methods you suggested and follow up with my results.
I assume linking is acceptable if it fits your situation and gives useful details. Keep the LLC on Medium; your voltages at idle look reasonable, so I think a slight boost would help.
You didn’t stick to the guide. It recommended adjusting the core multiplier, not the turbo multiplier.
Turbo overclocks are quite tricky. First, understand how turbo functions: its peak speed depends on all four cores under load, not just one or two. The voltages and timing of turbo activity matter a lot. I’d suggest researching Intel’s turbo behavior before relying on it.
Still, turbo can be useful—just ensure you increase the core multiplier too. Leaving C-states and EIST on, turning off turbo, and setting your desired multiplier in the CPU core ratio box should give better results. The CPU will idle normally with power savings active, then ramp up to the target speed once under load.
You can only adjust voltage in offset or manual mode—both aren’t available at the same time. When offset is on, manual entry is disabled. To avoid BIOS corruption, method B isn’t allowed if method A is enabled, and vice versa. So manual settings are hidden when offset is active.
Also, keep in mind that leaving power-saving features on while using manual voltage can be problematic. It forces a constant voltage, which defeats the purpose of saving power. For example, if your CPU runs at 0.8GHz at 1.3V while idle and then jumps to 4.1GHz at full load at the same voltage, no savings are achieved.
KYmo:
Thank you for your reply!
I initially used an LLC on Medium to test first, but switched to regular to check if that was the issue. I also disabled the C states except the first one. I followed this guide:
http://
(sorry if linking isn't allowed)
That’s the kind of overclocking I aimed for—only to activate when turbo kicks in for better power efficiency during idle, since keeping the Vcore high all the time could damage the CPU sooner.
Also, when offset mode is enabled, I can’t manually adjust the Vcore—it’s grayed out. Is this typical?
I’ll try the methods you suggested and follow up with my results.
I think linking should be fine if it fits your situation and gives useful details. Keep the LLC on Medium; your voltages at idle look reasonable, so I expect a slight boost under load.
You didn’t follow the guide exactly. It recommended adjusting the core multiplier, not the turbo multiplier.
Turbo overclocks are quite tricky. First, understand how turbo functions: the speed it achieves when all four cores are under stress isn’t the same as when only one or two are stressed, nor does it reflect the actual voltages and timing. I’d suggest researching Intel’s turbo behavior to grasp its true impact.
It’s possible to increase speed without boosting turbo, but you’ll need to raise the core multiplier too. Leaving power-saving features on is acceptable, though it won’t yield a stable overclock. If you keep C-states and EIST enabled, turn off turbo and set your desired multiplier in the CPU core ratio box—this should give better results. The CPU will still idle normally with power savings active, but under load it will reach the target speeds you specify in BIOS.
Changing the turbo multiplier while leaving the core multiplier unchanged will only push it to 4.1GHz when two cores are turboing (which rarely happens), and it will stay at 3.7GHz under full load—explaining why you didn’t notice any improvement.
You can adjust voltage only in offset or manual mode, not both. Enabling power-saving features disables manual voltage changes to protect the BIOS. It’s generally not advisable to force constant voltage if you want savings; instead, rely on proper overclock settings.
Imagine your CPU idling at 0.8GHz at 1.3V, then ramping up to 4.1GHz at the same voltage—no savings occurred. Offset mode adjusts the entire voltage range by a set amount, whether in percentages or millivolts.
amtseung :
kYmo :
Thanks for the response!
I did have LLC on Medium to start with but put it to regular to see if that was the cause, also i had the c states disabled besides the first one. This is the guide i followed
http://
(sorry if linking is disallowed)
Yeah that is the type of overclock i was going for only to kick in when turbo kicks in for the power savings at idle as i don't see the point in having the vcore high all the time and cpu at 100% state with an OC i think that would just burn the cpu out sooner.
Oh and when i have offset mode enabled i can't set the Vcore manually it's greyed out... is this normal?
I will try the methods you suggested and get back to you with the results
I would imagine linking is allowed, if it's appropriate to what you're describing and provides valuable context.
Leave the LLC on Medium then. Your voltages don't look too swell at idle, so imagining what they'd be under load, I think it'd like a nice little extra kick in the behind.
You didn't follow the guide. The guide said to adjust core multiplier, not turbo multiplier.
Turbo overclocks are an extremely finicky thing. First of all, you have to know how turbo works: The speed it reaches when all 4 cores are under load is not the speed it reaches when only 1-2 cores are under load, let alone the voltages and durations of the turbo-ness. I suggest you do some reading on how intel turbo actually works, and what it actually accomplishes.
There's nothing wrong with making turbo run faster though, you just won't actually see much benefit without also increasing the core multiplier as well. There's also nothing wrong with leaving all the power savings features on. You just won't have as high of a stable overclock. If you leave C-states and EIST on, disable turbo, and enter your desired multiplier value into the CPU core ratio box instead, I think that's the desired effect you're looking for. The CPU will still idle properly since the power savings are enabled, but once you place the CPU under load, it'll kick into high gear and hit the clock speeds you entered in bios. If you change the turbo multiplier and leave the core multiplier alone, it'll only reach 4.1ghz when it turbos on 2 cores only (which is like, never), and will still sit at 3.7ghz under full load, which is why you saw absolutely no change.
You can only change voltage on offset mode, or manual mode. You can't do both. To prevent corrupting the bios, it doesn't let you change via method B if method A is enabled, and vice versa. And so, manual entry is greyed out if offset mode is enabled. And just as a heads up, if you're leaving your power savings stuff enabled, manual voltage is usually a very, very bad idea, since it forces a constant voltage, the opposite of saving power Imagine your CPU idling at 0.8ghz at 1.3V, and running full load at 4.1ghz at 1.3V, no power was saved. Offset mode, well, offsets the entire range of voltages by the given amount whether it's a value of percentages or millivolts.
So i tried everything you suggested...
still no change according to CPUZ and i tried the different power plans in windows and ran Prime95 for stress testing and it shows at 3.5Ghz strangely enough? also when i set the multiplier to 41 with EIST and Turbo disabled it re-enables then automatically unless i restore the bios to default?
i've played around with quite a few things you suggested, i even input 1.35Vcore manually instead of using offset to see if that might work but nada
🙁
.
I'm at an end i really don't know why this isn't working i think it's going to be some stupid setting i've missed...
I'm going to try and set a smaller bump in the multiplier see if that helps...
KYmo shared their observations and troubleshooting steps. They noted no changes in CPUZ and found the stress test results odd at 3.5Ghz, especially with certain power plans and settings. They mentioned clearing CMOS thoroughly, not just restoring defaults, to avoid conflicts from forgotten changes. They pointed out confusion about the multiplier values displayed and suggested checking the BIOS settings. They emphasized keeping EIST and Speedstep enabled, and advised against mixing on/off states. Additionally, they reminded to keep XMP disabled for stability.