My CPU frequency is throttled to 200-400 Mhz

Framework Laptop 13 Linux
1

Hello,

I have a persistent problem with my Framework Laptop 13 equipped with an I5-1135G7. The CPU frequency is throttled to 400 MHz, which makes my system extremely slow. The problem disappears temporarily when I reset the BIOS by disconnecting the battery and power cable. But in general, the CPU throttles again a few hours later.

Here are a few points to consider:

- The BIOS is up to date with the latest version.

- There are no temperature-related issues; the temperature is around 50°C.

- The problem persists on both my Archlinux and Fedora systems.

In short, I hope you can help me because, at the moment, my laptop is unusable unless I take it apart and reset the BIOS every morning.

Thank you in advance for your help.

1 Like
2

Reach out to support. There is nothing anyone here can do to help. Most likely caused by PROCHOT (processor hot) signal being sent to throttle the CPU. The cause of this is not really known but support may help. You could also search up the threads about this issue and see if any of the suggestions contained therein are of use to you.

3

Thank you for your response, I have already been able to make a ticket to support, I will share their response with you.

Envoyé à partir de Outlook pour Android

1 Like
4

Same thing here! Let me know if you figure anything out.

Happens to me exactly as you described, on Arch Linux. I figured out I could get it back to normal without disconnecting the battery by turning it off but keeping the power button pressed for like 30 seconds after it turns off. Eventually it restarts and CPU is back to normal. I’m on a 12th gen intel framework 13, processor is i7-1260P.

Really annoying to not be able to play games or do any sort of heavy load that I know the laptop can handle because it throttles itself to an unusable frequency and stays there.

I already tried updating the firmware with the latest updates and I’m still experiencing the issue after fully updating firmware.

6

Applying fresh thermal paste fixed the issue for me.
Still doesn’t make any sense to me that the behavior described in this issue would happen at all. But if anyone is also struggling with this I do recommend applying fresh thermal paste.

In case anyone’s wondering, I used Thermal Grizzly, I think it was the Kryonaut one.