Anyone ever have issues with processors changing P-states?

[pantsaregood]

Just upgraded from an i5-2500K at 4.4 GHz to an i7-7820X at 4.8 GHz. All benchmarks show that the processor is considerably more powerful than my 2500K.

The issue? Every day use seems sluggish. I've narrowed the problem down to the processor spending almost all of its time at 1.2 GHz - even up to ~15% utilization. My 2500K was quick to boost up to 4.4 GHz from 1.6 GHz, but my 7820X just sits there until a massive load gets dropped on it.

Disabling energy efficient features (C-states, EIST, Speedshift) locks the CPU to 4.8 GHz and makes the issue go away, but it also causes my idle power consumption to almost double.

Anyone ever dealt with an issue like this? I'd rather not have to keep an instance of Prime95 running on a single thread to make my computer feel "snappy."

 

[Bouowmx]

I use ThrottleStop to set SpeedShift Energy-Performance Preference (EPP): range 0-255. Set to a low value so that less load is needed for processor to increase frequency.

 

[pantsaregood]

I use ThrottleStop to set SpeedShift Energy-Performance Preference (EPP): range 0-255. Set to a low value so that less load is needed for processor to increase frequency.

I'll have to try this out. I found some hidden power management settings in Windows that have the same effect, but they don't function when Speed Shift is enabled.

The default threshold for changing P-states in Windows 10 was 90% utilization. That perfectly explains why benchmarks made my CPU look like a monster but normal use felt slower than my 2500K.

EDIT: No luck with ThrottleStop. My PC hard locks within seconds of the program starting. Guess I'll have to just use EIST for now.

 

[Dufus]

If you disable Speed Step in the BIOS and use C-States C3/C6 then you should hopefully get good power savings and fast clocks.

 

[coercitiv]

Disabling energy efficient features (C-states, EIST, Speedshift) locks the CPU to 4.8 GHz and makes the issue go away, but it also causes my idle power consumption to almost double.

Normally Speedshift should address this situation, but for some reason it's not working as intended in your case (or not working at all).

I would advise you to increase minimum frequency through power management and keep C-states enabled. You can go as far as forcing 4.8Ghz all the time, as long as C-states are enabled your power usage will drop when cores are idle.

To change min frequency in Windows either choose the High Performance Profile or go to Control Pannel > Power Options > Change Plan Settings > Change advanced power settings > Processor power management > Minimum Processor state and increase that value from 5% to 50% or higher.

PS: i hope you're not using the Power Saver power plan, use either Balanced or High Performance.

 

[pantsaregood]

Normally Speedshift should address this situation, but for some reason it's not working as intended in your case (or not working at all).

I would advise you to increase minimum frequency through power management and keep C-states enabled. You can go as far as forcing 4.8Ghz all the time, as long as C-states are enabled your power usage will drop when cores are idle.

To change min frequency in Windows either choose the High Performance Profile or go to Control Pannel > Power Options > Change Plan Settings > Change advanced power settings > Processor power management > Minimum Processor state and increase that value from 5% to 50% or higher.

PS: i hope you're not using the Power Saver power plan, use either Balanced of High Performance.

Unfortunately, it appears that Speed Shift was not working as intended.

As of right now, C-states and EIST are enabled. I was able to unhide a setting in Power Options called "Processor performance increase threshold" through some registry modification. This was set at 90% (meaning 90% utilization) by default. Lowering it to 5% causes immediate clock increases. Lowering it to 0% forces every core to run at 4.8 GHz at all times. This appears to have resolved the issue.

When Speed Shift is enabled, this setting is ignored. My motherboard (ASRock X299 OC Formula) has three Speed Shift settings - Native (OS controlled), Native (No Legacy Support), and Out of Band (CPU/motherboard autonomous control). I don't recall if Out of Band causes the same issue, but Native ignored the performance increase threshold entirely.