Is it possible to overclock a 2500k with all power saving features on?

[2is]

I don't think my cpu downclocks without power saving features enabled. I might be living in the past tho 😵

The question is what does that have to do with vdroop? You're saying it's related but have not shown why or how. Vdroop is not downclocking.

 

[richaron]

The question is what does that have to do with vdroop? You're saying it's related but have not shown why or how. Vdroop is not downclocking.

AFAIK basic power saving features downclock the speed [f] of the CPU. I hope you understand the basics of speed [f], load, & power draw of a silicon chip (because I'm too lazy & ill-informed to elaborate).

Imagine the power requirements of:
- a downclocked 800Mhz CPU at idle
- an overclocked 4Ghz CPU under load

Now guess how a motherboard & PSU might have problems supplying an order of magnitude more power instantly (results = Vdroop).

 

[Meghan54]

AFAIK basic power saving features downclock the speed [f] of the CPU. I hope you understand the basics of speed [f], load, & power draw of a silicon chip (because I'm too lazy & ill-informed to elaborate).

Imagine the power requirements of:
- a downclocked 800Mhz CPU at idle
- an overclocked 4Ghz CPU under load

Now guess how a motherboard & PSU might have problems supplying an order of magnitude more power instantly (results = Vdroop).

You still have not described vdroop.

And that last statement.....about supplying power instantly.....that's what your mb and ps are designed to do! That's why capacitors are included in both, to provide the instant power required while the ps catches up.

 

[poohbear]

at the end of the day sandy bridge is super power efficient, so even it its overclocked to 4.4ghz on 1.35 24/7 when its idle it can't be drawing THAT much power?

 

[Elfear]

I didn't use llc for 4.4Ghz but I did use offset voltage. But the signs were pretty clear: crashes in games that couldn't be helped with increasing vcore, disabled c3/c6 and crashes were gone. I didn't try fixed vcore but it seems to me both situations have downsides so I settled for 4.3GHz.


Temps fluctuate a bit for me as well, but not 10c, more like 5. Check taskman to see what's actually going on. Might be perfectly normal though. What's certainly not good for power consumption is disabling all power saving features. I'm convinced having eist and c1e enabled won't cause any trouble at all.

I had the same experience. Mining at 4.8GHz (cpu activity at 10-30%) would result in a random BSOD every so often even though the cpu was stable while Priming. Finally disabled C3/C6 and no more BSODs. It's like the voltage couldn't adjust quickly enough for the different levels of activity. At least that's my uneducated guess.

 

[coffeejunkee]

To dig up old thread & educate the nubs...

Yes it does. My main experience with power saving features is downclocking the cpu while idle. Then if I instantly smash all cores @ high clock rate, it's the Vdroop which messes with my chi (it would be fine @ same settings without f & load changes).

To say Vdroop has nothing to do with it is silly.

Great, nub education is always good.

Turn off powersave features. Use fixed vcore. Experience same vdroop...

at the end of the day sandy bridge is super power efficient, so even it its overclocked to 4.4ghz on 1.35 24/7 when its idle it can't be drawing THAT much power?

Well, turn everything off and use fixed vcore and it will add something like 30-40W depending on overclock. Basically for nothing, so why disable if not necessary?

 

[richaron]

Great, nub education is always good.

Turn off powersave features. Use fixed vcore. Experience same vdroop...

You have successfully proven Vdroop is not solely confined to downclocking situations :thumbsup:

 

[2is]

AFAIK basic power saving features downclock the speed [f] of the CPU. I hope you understand the basics of speed [f], load, & power draw of a silicon chip (because I'm too lazy & ill-informed to elaborate).

Imagine the power requirements of:
- a downclocked 800Mhz CPU at idle
- an overclocked 4Ghz CPU under load

Now guess how a motherboard & PSU might have problems supplying an order of magnitude more power instantly (results = Vdroop).

As mentioned, that's exactly what the mobo is designed to do. vdrrop isn't limited to low load situations, in fact, it ONLY happens during load. The lower voltage levels at lower loads/speeds is not vdroop. Vdroop is a physical phenomenon. Its a combination of voltage, current and resistance that cause it. The voltage drops you're talking about are related to speedstep NOT vdroop.

 

[richaron]

As mentioned, that's exactly what the mobo is designed to do. vdrrop isn't limited to low load situations, in fact, it ONLY happens during load. The lower voltage levels at lower loads/speeds is not vdroop. Vdroop is a physical phenomenon. Its a combination of voltage, current and resistance that cause it. The voltage drops you're talking about are related to speedstep NOT vdroop.

I gave a scenario where supplied voltage is compromised because of power saving features, & where it may be the straw that broke the camels back, I have seen the results myself (i.e. a CPU fails with power saving features downclocking where it might not otherwise). I didn't say Vdroop was limited to downclocking, & I agree it's a physical phenomenon (moot point; are your really suprised with a physical situation?).

 

[coffeejunkee]

You have successfully proven Vdroop is not solely confined to downclocking situations :thumbsup:

No, I have proven that powersaving features and vdroop have nothing to do with each other, because you will see exactly the same vdroop with powersaving features enabled or not. Which is what I said in the first place, but you said that was 'silly'.

As for your cpu being unstable, what I think you actually mean is when using dynamic instead of fixed vcore. I myself experience nothing like that, dynamic vcore is just as stable as fixed vcore in my case. Maybe I should go beyond 4.6GHz to notice something similar, but I doubt it.

 

[richaron]

No, I have proven that powersaving features and vdroop have nothing to do with each other, because you will see exactly the same vdroop with powersaving features enabled or not. Which is what I said in the first place, but you said that was 'silly'.

As for your cpu being unstable, what I think you actually mean is when using dynamic instead of fixed vcore. I myself experience nothing like that, dynamic vcore is just as stable as fixed vcore in my case. Maybe I should go beyond 4.6GHz to notice something similar, but I doubt it.

You haven't proven anything. Watching the readout of some program is only very loosley related to what is going on in your motherboard/cpu. If you think there is no power difference between a downclocked cpu & stock/overclocked (at idle) then I'll stand by my "silly" claim.

I set all my voltages manually.

I'll leave this convo with this: Vdroop is related to the differential of power draw by the CPU (idle vs load). A higher overclock increases the power requirements (& hence the V differential), a downclocked CPU reduces the power draw (hence also increases the V differential). So power saving features effect overclocking/stability potential.

 

[birthdaymonkey]

i5 2500K @4.6 here. P8Z77-V Pro, vcore offset mode (manual) -0.02, medium LLC. This results in a CPU-Z value of 1.29-1.31v under load and 0.98v idle.

I've been 100% stable (Prime, IBT, gaming, daily use) with no power saving features disabled and no other voltages tweaked.

 

[coffeejunkee]

You haven't proven anything. Watching the readout of some program is only very loosley related to what is going on in your motherboard/cpu. If you think there is no power difference between a downclocked cpu & stock/overclocked (at idle) then I'll stand by my "silly" claim.

I set all my voltages manually.

I'll leave this convo with this: Vdroop is related to the differential of power draw by the CPU (idle vs load). A higher overclock increases the power requirements (& hence the V differential), a downclocked CPU reduces the power draw (hence also increases the V differential). So power saving features effect overclocking/stability potential.

I don't think that. What I said is that a certain frequency you will see the same amount of vdroop with C1E/EIST/C-states enabled as with those features disabled, regardless of using fixed or dynamic vcore. So no, I don't see any relation at all.

Some people seem to think vdroop means lower vcore during idle, but that's not the case at all and that's why I commented, since this is a topic about cpu powersaving during idle, which involves lowering vcore.

Anyway, this is all offtopic because it has been shown by many here that you can overclock fine with all settings enabled, as it was with basically all cpu's before. I've never bought the whole 'disable eist or your cpu will be unstable' rambling, mostly because I never had any issues having it enabled, and this was with P4, C2D and Lynnfield. But like I said as well, I had to disable C3/C6 when going above 4.3. If your cpu works fine with those enabled, great. If you're wondering why you have weird crashes, that might be the problem.

 

[2is]

I gave a scenario where supplied voltage is compromised because of power saving features, & where it may be the straw that broke the camels back, I have seen the results myself (i.e. a CPU fails with power saving features downclocking where it might not otherwise). I didn't say Vdroop was limited to downclocking, & I agree it's a physical phenomenon (moot point; are your really suprised with a physical situation?).

I'm not sure what you're saying I don't think you are either. The voltage decrease you're referring to is not vdroop. Period. Nor is it related to vdroop.

 

[2is]

Double post