Hello fpers
I read a thread a few months back about someone having a problem overclocking their 2500k/2600k where the frequency would jump back and fourth.
I am having the same problem and can't seem to figure it out or find the thread.
My motherboard control panel reads 4.5 ghz for my overclock but when I fire up cpu-z it goes from 4.5 x10 to 1.6 x16 and it goes back and fourth...
It's called speed step, it's normal.
The CPU throttles down when not under load to save power.
[QUOTE=Ins4ne;34005137]Hello fpers
I read a thread a few months back about someone having a problem overclocking their 2500k/2600k where the frequency would jump back and fourth.
I am having the same problem and can't seem to figure it out or find the thread.
My motherboard control panel reads 4.5 ghz for my overclock but when I fire up cpu-z it goes from 4.5 x10 to 1.6 x16 and it goes back and fourth...[/QUOTE]
You can change this in the BIOS mate, so that it stays the same continuously, would you like me too share this with you?
I'd advise against it, unless you want the CPU to run at maximum power consumption (which can be as high as 150W in some situations) and be a furnace.
It slows down when you don't need the speed, saves power, heat, noise. And once you do need power it scales back up quickly
Well the thing is there is no consistency. When I am under load it'll switch between them whenever. Same thing when I am idling, it'll just decide to switch back and forth.
I'm not sure about the 2600k, but on my i5-750 I found that C1E was turning my clock speed down too quickly, before applications were done utilizing a higher clock. I disabled C1E and noticed a small performance gain, while leaving Speedstep enabled. Windows will automatically set the clock speed using Speedstep when it decides to, or you can change the clock indirectly by changing advanced power options minimum and maximum processor power levels. You can see the multiplier change with CPU-Z when you change the minimum power state.
Sorry, you need to Log In to post a reply to this thread.