Why is my CPU Downclocking?

[Soggyhead]

So I have a Intel Pentium G3258 and I was wondering if there is any good reason why my CPU is downclocking when coming out of sleep mode? I only have it overclocked in the bios, so no software is involved.

 

[flibberdipper]

Do you have performance mode or whatever it's called in the power options part of the control panel enabled?

[DimasRMDO]

When your computer is idling, the CPU will automatically downclock itself so it's normal. You can disable C-State if you don't want your CPU to downclock when it's idling.

[theelitegamer]

When your computer is idling, the CPU will automatically downclock itself so it's normal. You can disable C-State if you don't want your CPU to downclock when it's idling.

What he said.

 

Or go to PowerSettings and go to CPU and change the settings. 

[DimasRMDO]

If you want to disable C-State (if you're using MSI motherboard) go to the BIOS > OC > CPU Features > C-State (disable it).

[Soggyhead]

Power saving? When it isn't used it'll underclock and downvolt to save power

So all power saving options are off, they are all set to performance mode in windows power options.

If you want to disable C-State (if you're using MSI motherboard) go to the BIOS > OC > CPU Features > C-State (disable it).

So i have an Asrock mobo but i'll go check out those options anyways.

Alright i rebooted and found the C-state options in the CPU configuration in the advanced tab on my Asrock board if anybody with this same problems wants to know.

After putting it in sleep mode and bringing it back out it was still downclocked, but i'll probably mess around with more of the sleep states in the bios.

Still downclocked, anymore ideas?

[Django]

Haswell can run full speed when active without any noticeable down clocking with C-States enabled.

Sounds like a BIOS bug, is there a BIOS update you can try.

[Soggyhead]

Haswell can run full speed when active without any noticeable down clocking with C-States enabled. Sounds like a BIOS bug, is there a BIOS update you can try.

It seems you were right, after going back on a version of the bios it was fixed. It would make sense because the version of the bios i had, had a power saver function embedded in it. So thx

[PepperBurst]

It's not a problem, I have the same CPU clocked at 4.2 GHz on a stock cooler, CPUs downclock themselves automatically when not under load but clocks itself higher depending on your current load. It really isn't a feature you'd want to remove as it saves power when the CPU doesn't really need to work hard (Like, sleeping or idling).

[Blackie Sheen]

So all power saving options are off, they are all set to performance mode in windows power options.

I really dont understand why you would want your cpu to work at its max frequency when at idle. The is no real benefit to it since it will promptly push itself to its rated speed at soon as it receives significan enough load

[Django]

I really dont understand why you would want your cpu to work at its max frequency when at idle.

 

With C-states when idle the processor core clock(s) stop with C-state C1, with higher C-states such as C6 the cores are power gated off. Down clocking is advantageous for power saving on CPU's that are older than about 10 years or where C-States have been disabled, otherwise not much use IMO. I'd much rather have my Haswell operating at maximum frequency when active and get the job done quicker so it can return to the better C-State power savings.

[Soggyhead]

I really dont understand why you would want your cpu to work at its max frequency when at idle. The is no real benefit to it since it will promptly push itself to its rated speed at soon as it receives significan enough load

Thats the thing my computer is really never at idle, im either gaming, or i want it in sleep mode. So that when i come out of sleep mode it's still overclocked. Otherwise i would have to restart every time or turn off my computer all the way, but thats just personal preference.

[Django]

Here's an example of a simple single threaded application on Haswell quad that does some work every couple of seconds with clock set for max performance (no down clocking) and C-States enabled except for C1E.

Averaging only 2% of CPU time it has plenty of time to make use of power savings with C-States and according to HWiNFO64 uses an average of 7.4W.

 

 

If we force down clocking and run the same application it takes longer to complete.

Now having to use 9.4% of overall CPU time to get the same job done as CPU is running slower there is less time to make use of idle C-States. Average power is now 7.9W, using more power than having clocks forced to maximum when the CPU is active.

 

Running the same application again while allowing it naturally clock up and down with load.

Very similar to the maximum clocks but with a bit of added latency as can be seen with the average CPU time being 3%.