Intel Speedstep - How to (Can I) set a Minimum multiplier and/or Vcore voltage???

euphoria4949

Distinguished
Aug 26, 2012
569
0
19,060
Hello,

So my question is, Is it possible to set a "Minimum" multiplier state with Intel Speedstep enabled, and if so, how???

Reason:
I've been running a really nice overclock for a while now, with speedstep disabled and a manual Vcore, so the CPU is flat out 100% all the time. This has been 100% stable for months, stress tested on AIDA 64 Extreme for around 40+ hours total, hundreds of hours gaming and rendering.. etc.
But, I decided I want to enable speedstep to reduce the clock and voltage when idling as my PC is switched on pretty much 24/7, 365.

Therefore, I enabled speedstep, set the Vcore to offset and got everything sorted perfectly. My 100% load Vcore is exactly the same as when it was set to manual, tested again with AIDA 64 Ex and it's 100% stable.... "At Load". But, very occasionally it becomes unstable at idle. It seems with the multiplier dropping as low as x16, and the VCore down to around 0.850v, some times it's a little too low for the system to handle.

So, with the multiplier ranging from x16< up, and the Vcore from 0.850v<, I would like to know if there is a way to set a minimum multiplier and Vcore, like: x25 and 1.000v for example.
Is this possible, it's not something I've ever tried or looked into before???
I tried setting the Windows power mode to CPU state minimum 25%, also 50%, but that didn't work either :??: And I've tried increasing the LLC, but that doesn't help either.

So any help would be greatly appreciated.
Thanks

P.S. System Specs:

3770K running on an ASUS Z77 Sabertooth Mobo, with Win7 OS.
 
I would've suggested Windows power states, but you've tried that. I'm going to venture a guess that it's not a matter of clockspeed and voltage, though. Try disabling C3, C6 and package C-states (basically, disable all C states except C1E), and disable spread spectrum. See if that fixes things. With Ivy, C-states often caused instability when overclocking.
 

euphoria4949

Distinguished
Aug 26, 2012
569
0
19,060


Thanks for the quick reply.

Sorry, my bad, I should have listed in my OP, that all C-states were already disabled, including C1E actually... I don't even remember disabling that :??:
Also spread spectrum was already disabled too.

I just thought I try something whilst I was back in the BIOS, I reduced the LLC and increased the offset VCore to see if that bumps up the minimum Vcore a tiny bit, but "Hopefully" doesn't effect the load stability.
 
For what it's worth, I'd consider a slightly higher load voltage to be an acceptable tradeoff for the CPU running at lower voltage 99% of the time. Even if you need to increase your offset another 0.025-0.050v, it's probably worth it.
 

euphoria4949

Distinguished
Aug 26, 2012
569
0
19,060


Unfortunately, if I bump up the Maximum Vcore voltage more than 0.010v extra, it becomes unstable under load :( There seems to be a small perfect sweet spot for my overclock, just a tiny lower or higher voltage and it's unstable.
 

euphoria4949

Distinguished
Aug 26, 2012
569
0
19,060


Yeah, I'm totally confused why it's not effecting the multiplier as well.

Mobo limitations, yeah possible, it's a reasonably high Mid range mobo, but not a ROG board.
PSU reaching it's limits, hmmm unlikely. It's a Seasonic X-850w Gold, single rail, with my max power draw from the wall under full system load, everything being stress tested at the same time, is under 600w.
Cooling insufficient, no, I'm running an overkill custom loop, max temps under AIDA 64 barely and rarely even hit 60c.
And I've tried setting the minimum state to everything from 2% to 95%, nothing changes though :??:
 
^ Except most Ivy Bridge CPU/motherboard combos have idle and partial load instability when using offset voltage, regardless of how high the voltage is. OP is certainly welcome to try enabling them, but 90% of Ivy systems I've played with have needed C-states disabled, or to use a fixed voltage when overclocking.

Fixed voltage with C-states enabled is usually not a problem and does offer some power savings, but is generally an inferior solution to offset without C-states. Offset with C-states is best, but it's unlikely to be stable.