CPU is restricted to 400MHz and thermal warnings are active though temperatures aren't exceeding limits.
CPU is restricted to 400MHz and thermal warnings are active though temperatures aren't exceeding limits.
It seems your Asus Flow X13 is experiencing thermal throttling without any obvious external issues. The HWinfo64 data shows throttling flags are active in both HTC and PROCHOT EXT, yet no unusual sensor readings stand out. It might be a software issue or something not immediately visible getting hot. The last time this occurred was after leaving the power cable unplugged during cleaning, but this time it wasn’t the case—manually enabling fans resolved it. This is the first time it’s happened consistently, so I’m unsure what to try next. I’ve adjusted performance settings, switched power sources, and even forced fan operation, but nothing has changed. If it’s software-related, wiping and reinstalling might help. If hardware is involved, isolating the cooling system could be necessary. I’m considering a repair soon, but I’m worried about the cooling setup not reaching its intended temperature.
A basic way to resolve the problem is to install Throttlestop and turn off PROCHOT. Check if this resolves the issue, and if it does, you likely have something sending incorrect data. I've encountered this with my X270 using a third-party battery. Disabling PROCHOT is necessary to use the PC correctly.
Throttle stop is exclusive to Intel, yet I've experimented with Ryzen controllers that can't modify these settings. I'm hesitant about turning off a protective feature just to start with.
From what I understand, turning off PROCHOT doesn't shut down all thermal monitoring completely—it just affects certain features. Also, a short pause will let you see if the problem is with PROCHOT or something else. If you're stuck at 400Mhz after disabling it, it means PROCHOT isn't the root cause.
No mobile chip software seems available on the AMD side, unfortunately. I haven’t located anything since most options are found for desktop CPUs.
Updating the BIOS resolved the problem (it wasn’t a fresh update, even though it should have been). I should have done this earlier, but I’m hoping it’s not a cause for worry.