Resolve issues with Win 11 not maintaining CPU OC and power plan settings.
Resolve issues with Win 11 not maintaining CPU OC and power plan settings.
Recently I've faced a problem where my CPU reaches 4.9GHz every time I restart my PC. After rebooting, the overclock reverts back to the standard 3.6GHz, and with any overclock setting, I always choose the -Ultimate Performance power plan. Once restarted, the power plan shifts to -Balanced and the overclock drops to -3.6GHz. It's becoming exhausting to constantly adjust my power settings and keep the CPU at the desired frequency inside BIOS or Intel Extreme tuning for Windows 11. I'm looking for a solution so both settings remain consistent without needing frequent changes. Thank you, Info: 1000w Evga G6 power supply, 32gb G.Skill Trident Royal 3600 16GTRS, MSI MEG Z390 Godlike CPU, Intel i9 9900k. This might be too much info, but I'm trying to get what I need. Edited May 5, 2022 by Darkerowl
It looks like you're dealing with a few technical challenges. First, remove MSI Dragon Center and try selecting the Ultimate power plan via Power Options. After that, restart and check if Windows maintains that setting. If not, consider rebooting entirely. It seems Windows 11 might have a bug affecting performance. For accurate CPU readings, use tools like HWiNFO or CPU-Z instead of HWMonitor. Monitor your processor speeds during these tests. If the issue persists, you may want to enable ThrottleStop 9.4.6 and adjust settings accordingly. Ensure your BIOS is up to date, as outdated firmware can cause similar problems. Keep an eye on turbo limits—some versions disable them by default. Document any changes or screenshots for troubleshooting.
This setup makes sense now. With Windows 11 and the latest BIOS updates for my motherboard, I was seeing incorrect CPU and RAM speeds in all my system apps—reporting a 37MHz clock while the actual speed was only about 1% of normal. After checking everything, I found the MSI MEG Z390 Godlike Mobo model has an option to adjust the OC via a dial on the board or in the BIOS menus. However, the available profiles don’t stay consistent; sometimes they show 4.9 or 50 instead of stable values. I manually changed the settings, but the results weren’t what I expected. After restarting and switching to High Performance power plan, it worked better than the Ultimate plan I usually use. The throttle stop isn’t allowing me to modify the multiplier or other settings. In Intel E.T., my processor cache frequency is listed as 0.04, which seems off. I’m not sure what’s causing this issue, but I’m trying different solutions and hope it resolves.
On Windows 11, for monitoring tools to function properly and access CPU registers, you must turn off virtualization features. Access Windows Features, review enabled items such as Hyper-V, Virtual Machine Platform, Windows Subsystem for Linux, Android Subsystem, Core Isolation, and Memory Integrity, then disable them. Restart your system afterward. Remove the ThrottleStop.INI file, as it may become corrupted by these settings. Avoid using the outdated Intel Extreme Tuning Utility. To modify CPU speed, adjust the Turbo Ratio Limits in the FIVR window. Since your computer uses Speed Shift Technology, the Set Multiplier option is unavailable. ThrottleStop and HWiNFO will align with the reduced speed. Only enable ThrottleStop and provide screenshots of the TPL and FIVR interfaces. Edit – Your image displays an AVX offset ratio of 31; set it to 0 in BIOS. Eliminate XTU.
Consider sharing some images of ThrottleStop now. Is it suitable for keeping your overclock active after a sleep resume cycle? Intel XTU has consistently struggled with this feature, often breaking down over time. Try using the Windows key, Shift key, and S key on your keyboard to capture a screenshot—this should open the sniping tool.
I received the updated version of INTEL E.T. and noticed it’s requesting removal, which I didn’t expect. I planned to share it later—please send the image now and follow the link provided. Windows Core Isolation support info: https://support.microsoft.com/en-us/wind...521df09b78
After disabling that core isolation, the problems disappeared. Now I can observe the correct processor cache speed and see what happens during startup after turning it off and using my basic OC method. It confirmed both the OC settings and my power plan. I’m able to experiment with voltages and enjoy gaming without worrying about losing my progress each night. I’ll restart again to verify it still functions after several cycles. Updating XTU also seemed wise—it alerted me when an update was available, which never happened before. I didn’t realize that help existed. Thank you! Windows 11 has always been tricky for OC; MSI took a long time to release the Win 11 BIOS beta that supports X1 Re-Bar. It’s been quite a journey. Your support means a lot.
Personally, I’d have kept working on this longer since I couldn’t find a fix online. You were a huge help—I never expected someone to notice these issues!
One more thing: I use an HW monitor for years and it’s a simple way to check temperatures during games. After removing MSI Dragon Center, I lost the ability to view my Per Core usage. Do you have any way to restore those stats, or will I need to rely on MSI Dragon Center again?
Someone should create a manual explaining which Windows 11 features need turning off so monitoring tools and XTU function correctly. I’d consider it, but I haven’t installed Windows 11 yet. It’s unclear why disabling Dragon Center affected HWMonitor. You may need to reinstall Dragon Center or HWMonitor. At least now you’re aware that Core isolation—Memory integrity—was probably the cause of many issues. Windows 11 made significant security changes, which is beneficial for most users but challenging for those who prefer deeper customization. Proceed with caution when using XTU; it might still have a problem reapplying offset voltages after a sleep resume. Verify with HWMonitor or HWiNFO to confirm the correct voltage values are applied. Remember that HWMonitor previously had a 2% accuracy issue, so discrepancies between reported and set voltages should be considered.