[SOLVED] Windows Power Options no longer changing cpu speed.

Klaz49

Reputable
Sep 26, 2019
60
0
4,540
Ill try to keep this as short as possible.

Before I would use the windows power options to either:
  1. Have my pc in "Power saving" mode, which slowed the CPU down to like 2Ghz. Used this when I wasnt gaming, or when going to bed.
  2. Have my pc in "AMD High Performance". This put my cpu around 3.8-4.2Ghz depending on how much usage the cpu was getting.

However now changing to any of these profiles in windows are not doing anything. My cpu is constantly staying at 3.8ghz no matter what.

I have AI Suite 3, and Ryzen Master installed. They were both installed before when I still was able to change my power options.
I have tried closing (and pruning in task manager) both programs. That doesnt help. the cpu is still staying at the same speed.

What can I do? I just wanna go back to being able to change my power modes at will.
 
Solution
changing to any of these profiles in windows are not doing anything. My cpu is constantly staying at 3.8ghz
i have had issues like this before with Windows 10 where the power plans seemed to quit functioning in the same way.
over the years i've experienced it a few times.
to correct the issue i would create a custom profile and they would usually work fine.

the last time i experienced it more recently this didn't help either though.
it turned out to be an issue with my BIOS and C-States not working properly with my CPU.
resetting to optimized defaults and re-entering my personal custom options in the BIOS reset it back to normal again.
then the CPU would follow the power plan CPU % rates with no problem.
i wouldn't expect a...
changing to any of these profiles in windows are not doing anything. My cpu is constantly staying at 3.8ghz
i have had issues like this before with Windows 10 where the power plans seemed to quit functioning in the same way.
over the years i've experienced it a few times.
to correct the issue i would create a custom profile and they would usually work fine.

the last time i experienced it more recently this didn't help either though.
it turned out to be an issue with my BIOS and C-States not working properly with my CPU.
resetting to optimized defaults and re-entering my personal custom options in the BIOS reset it back to normal again.
then the CPU would follow the power plan CPU % rates with no problem.
i wouldn't expect a manual CPU % to be tied to C-States but somehow it was overriding the plans' settings.
 
Solution
i have had issues like this before with Windows 10 where the power plans seemed to quit functioning in the same way.
over the years i've experienced it a few times.
to correct the issue i would create a custom profile and they would usually work fine.

the last time i experienced it more recently this didn't help either though.
it turned out to be an issue with my BIOS and C-States not working properly with my CPU.
resetting to optimized defaults and re-entering my personal custom options in the BIOS reset it back to normal again.
then the CPU would follow the power plan CPU % rates with no problem.
i wouldn't expect a manual CPU % to be tied to C-States but somehow it was overriding the plans' settings.
I dont think creating a manual plan will work, as I feel there is more to the changing of the cpu done by windows then by the settings listed.
For example, before I was trying to change how the "power saving mode" limited cpu use, but after looking at both advanced profiles in Windows Power plan settings (Power save/High performance), they both stated min/max CPU usage was 100%, Even tho obviously my CPU clock speeds were changing.
 
I dont think creating a manual plan will work
and you wouldn't try because..?
Windows Power plan settings (Power save/High performance), they both stated min/max CPU usage was 100%, Even tho obviously my CPU clock speeds were changing.
then either someone/something edited the 'Power saver' plan or you have a deeper corruption in the OS.
all Windows OS have default Power saver settings; 'Processor power management' > 'Minimum processor state' > Setting: 5%.

some motherboard control software or other 3rd party system/gaming optimization software is known to cause issues like this.
if you have anything like it installed, uninstall.
AI Suite III doesn't affect these types of settings unless you choose one of their optimization or AI overclock options. if you have, just disable the option.
never allowed Ryzen Master to run on any systems i've worked with so couldn't tell you if they have similar built-in options.

and it's always possible that it's just a corruption in Windows, it's reported regularly.
if you have a Restore point from before you noticed the issue revert.
if not, it may take a fresh install to correct any issue causing it.
 
Last edited:
what do you mean by, "didn't work"?
any manually created Power Plan failed to initialize?
or any manually input settings failed to take place?

if your Power Plans were working, i don't get the "didn't work" statement.
I tried to manually create a power plan, and edit existing ones in the past, when the power plans were working for me. however no matter what I changed it had no effect on my cpu speed.
I tried again earlier this morning and still nothing. Even if i put the limit on the cpu at max50% its still just staying at 3.8ghz.
 
tried again earlier this morning and still nothing. Even if i put the limit on the cpu at max50% its still just staying at 3.8ghz.

some motherboard control software or other 3rd party system/gaming optimization software is known to cause issues like this.
if you have anything like it installed, uninstall.
AI Suite III doesn't affect these types of settings unless you choose one of their optimization or AI overclock options. if you have, just disable the option.
never allowed Ryzen Master to run on any systems i've worked with so couldn't tell you if they have similar built-in options.

and it's always possible that it's just a corruption in Windows, it's reported regularly.
if you have a Restore point from before you noticed the issue revert.
if not, it may take a fresh install to correct any issue causing it.