Nov 01 2021 04:45 PM
Nov 01 2021 04:45 PM
Windows 11 build 22000.282 (Release)
All drivers on the system updated to the most recent Windows 11 supporting drivers.
CPU's that I tested this with: Ryzen 7 5800X and Ryzen 9 5900X.
X570 AORUS XTREME (rev. 1.0) BIOS updated to F35d.
Power saver plan set to minimum processor state is set to 99% and maximum processor state to 100%.
Tried the same with Balanced and Power Efficiency mode.
CPU doesn't throttle down nor stays at stock frequency (none turbo) when idle, this leads to increase power consumption/temperatures.
CPUZ, HWMonitor and other tools do show that it randomly hits stock frequency for some milliseconds and then goes straight back to maximum boost frequency.
Been swapping back and forward between Windows 11 and Windows 10, on Windows 10 this works without issues.
Reported this issue via Insider Feedback back in August and on the Insider forum in September.
Re: BUG: Windows 11 Power saver plan - Microsoft Tech Community
Right now I'm running my CPU at stock frequency to avoid my CPU being stuck at boost frequency.
Is this bug going to be addressed and fixet?
Nov 05 2021 08:27 AM - edited Nov 05 2021 08:28 AM
I got a new M.2 drive this week and went for a fresh install.
The power plans work closer to how they did in Windows 11 now, I still had to set PBO down to 65W values to get the same idle and load behaviour though.
So to get the same with PPT 105, TDC 70, EDC 95 on Windows 10 I had to drop to PPT 76, TDC 60, EDC 90 on Windows 11.
Needless to say that this also decreases performance.
CPU is sitting on 34-35C while typing here right now.
So one conclussion is that upgrading from Windows 10 to Windows 11 breaks either the power plans or the CPU scheduler.
Although there is still the issue of having to lower the TDP to get the same behaviour and temperatures as with Windows 10.
Dec 21 2021 10:09 AM - edited Dec 21 2021 10:16 AM
Nopes, it still doesn't work like it did on Windows 10 21H1.
Seems Microsoft completely ignores the issue, someone in the US should adress this to the ECAA, since that would be the only way I currently can think of that would force MS to react.