System remains at minimal processing frequency indefinitely.
System remains at minimal processing frequency indefinitely.
Hi, I have an hp 14-fq1040ca laptop and the processor has been stuck on the lowest speed (400 MHz) for about a week now. The problem started when I installed a windows update last week and I had a very low battery percentage (although that may not have had anything to do with it). I've tried restarting, updating the BIOS, changing power management settings, unplugging and plugging back in both the battery pack and fan (they both work fine), and just leaving it plugged in for a day. I think it may have something to do with how much power the cpu is getting (as it doesn't seem to be thermal throttling), though I am not very familiar with how that works / how I would fix it. Included is a screenshot from a hardware monitoring tool. Please help
Indicates overheating concerns on the motherboard, possibly due to poor cooling or sensor issues. It may result from excessive heat in the VRM system or faulty readings. Ryzen Master can help disable bd prochot, but acting without understanding the root cause risks further damage.
Essentially, you should replace the motherboard or look for a method to lower your CPU's temperature.
I’d likely run the standard diagnostics—either a fresh OS installation or testing Linux via a USB drive. Considering the schedule, it might actually point to a failing power supply unit or a bad battery management system. It’s also worth checking if the system still limits performance when using low battery levels.
Checking the thermal paste is important too, along with verifying that all fans and pumps on your CPU cooler or radiator are functioning properly. I ran into a problem where a fan stopped working, and there were overheating issues and blue screens before it, possibly due to poor thermal paste.
The image indicates the CPU is currently idle, which is normal when downclocking. Stressing the CPU in this situation is typical. Could you capture another picture while applying some pressure? Regarding the issue, it seems resolved after a fix, though I recall the first-gen Ryzen (2xxx models) had a sleep-related bug that sometimes led to stuck states at low clocks—seems like plugging it back would resolve it. It doesn’t appear to match your scenario.