The Intel 10700k is limited by its base clock speed.
The Intel 10700k is limited by its base clock speed.
The CPU utilization image displays full load. @Derminian Can you share screenshots of the FIVR and TPL interfaces? There could be a hint there. Also run Limit Reasons while the CPU is busy and observe any red indicators that suggest throttling. Close HWiNFO when using Limit Reasons. Take a closer look at the TPL window. Verify the Speed Shift setting and confirm Speed Shift Max matches the recommended value. Inspect the MMIO Lock box in the upper-right corner of the TPL window. Restore IntelPPM to its default setting.
@unclewebb Thank you for the response, I have attached the photos you asked for. The FIVR and TPL screenshots are on idle. Under the limits section under a Prime 95 stress test I see no red. The SpeedShift was already checked but I did check and apply the MIMO lock box. Unfortunately it still is capping out at 3.8Ghz.
The BIOS or Windows 11 might not be configuring your CPU properly. ThrottleStop could resolve the issue, but you’ll need to turn off Windows 11’s Virtualization-Based Security. It requires direct access to CPU registers, which isn’t possible when VBS and memory integrity protection are active. After disabling these protections, restart and remove the ThrottleStop.INI file. This file can become damaged if you run ThrottleStop with VBS or integrity enabled. The core problem is that your CPU turbo settings are capped at 38, restricting performance to around 3800 MHz during stress tests. You may need to adjust these values in ThrottleStop and possibly disable VBS first. Using ThrottleStop with VBS usually breaks most FIVR configurations. It’s unclear whether the BIOS or Windows 11 is at fault. If you can’t fix it in the BIOS, disabling VBS before running ThrottleStop is your best chance to restore normal operation. Any changes in the BIOS require deleting the ThrottleStop.INI file afterward so ThrottleStop can apply updates without relying on old settings. This situation is common—many users face similar challenges after upgrading.
I just wanted to express my gratitude for your assistance. You managed to resolve an issue that had been challenging for two days in a matter of minutes. I already had core isolation turned off, but HyperV was still installed after switching from Windows 10 to Windows 11. After reviewing the steps mentioned, I disabled the features and confirmed VBS wasn’t running. I noticed my CPU was already turboing at 4.7Ghz across all cores. By chance, I upgraded to Windows 11 about three months prior. I created a system image just in case things went wrong, but it wasn’t necessary. Everything seemed to run smoothly without any noticeable slowdowns in gaming or other tasks. Overall, I’m satisfied with the upgrade. I didn’t perceive significant improvements beyond what Windows 11 offers, just enjoyed testing it out. I’m indifferent about the change overall. But as you said, many overlook such issues—especially if I hadn’t been watching overclocking videos that day and decided to check my performance and stress test. I even monitored the monitor in the PSU window for CPU speed and temperatures. I didn’t really focus much on the CPU clock before. Thanks again for your support!