The CPU isn't reaching its full clock speed.
The CPU isn't reaching its full clock speed.
People often ask why a laptop is pushed to run at boost clock, but most don’t realize these machines are built for short bursts. Laptops like the T14 handle high performance only briefly—usually just a few seconds—before needing to cool down. It’s surprising how they manage such power for so little time.
When all of the C states are disabled, the maximum turbo multiplier is limited to 41. That is the problem. In ThrottleStop, check the C States - AC box, select Off and press Apply. Do the same thing again but this time select On and press Apply. This resets some of the Windows C states settings. Is there any C state activity now? If not, it is possible there was a BIOS update that disabled the C states. This is a cheesy way some manufacturers use to block access to the higher 47 multiplier when lightly loaded. It is a really bad idea because it creates a lot of extra heat when all of the low power C states are disabled. There is nothing wrong with trying to get a CPU to run at its Intel rated speed. Turbo Boost is a feature of almost all Intel CPUs. There is no reason for Turbo Boost to be disabled.
Accessing the Windows Power Settings allows you to attempt the Restore plan defaults feature, which can help reset the current power plan. You might also consider changing to another available plan. It seems the C settings were turned off during a BIOS update, so you could try reinstalling an earlier BIOS version. Keep in mind there are potential risks involved when updating to older BIOS versions, so proceed with caution. The C settings likely had a toggle enabled when turbo boost previously exceeded the 41 multiplier.
the laptop operates efficiently up to 30W before it starts throttling, but now the reduced clock speed is the main reason it only hits that power limit during emulation, not when using the cooling pad.
Linux experiences the same problem at up to 4.1ghz. I've tested both Linux Mint (XFCE) and Fedora (GNOME).
Set up cpupower and execute "sudo cpupower idle-set -d n" with n ranging from 9 to 0 each run. Observe any adjustments in CPU clock speed. Use "sudo cpupower idle-set -D n" to silence C-state reporting or "sudo cpupower idle-set -E" to activate them. Consider installing i7z for clock monitoring, though it may misreport states. Also, try "sudo intel_gpu_tools" and run "sudo intel_gpu_top" to view power consumption. Verify if firmware (UEFI) was updated; revert if necessary.
distro runs Fedora (Gnome) after Mint faced a self-destruction scenario