Hey there, did you use the search?
We’ve had this one posted before several times.
1 Like
I’ve been having this issue off an on for a few months. It seemed to resolve itself once automatically after leaving the laptop off for an entire weekend.
Since the issue started again for a second time I was unable to resolve the problem / find a workaround until this thread. There is one comment that mentions they removed the HDMI port from their framework laptop and it resolved the issue. I just wanted to leave a comment saying that doing so instantly resolved my problem as well.
Lucky! Removing all expansion cards doesn’t fix it for me, even…
I got the same problem on 13th gen intel.
I’m playing APEX and have high cpu usage, after some time(e.g. 10 min). It will go to 400Mhz for a long time. I only have this problem for some days. But it occurs every day.
Same problem here and the support is just writing:
When you disable Intel SpeedStep the issue stops.
Can’t believe I get such incompetent support. Thougt Framework would be different
1 Like
Same issue, support wrote me this message: https://twitter.com/Batchputz/status/1786098638462287875/photo/1
Can’t believe it. I am shocked by this behavior
This still happens to me from time to time, usually after being plugged in for days. I find that unplugging and running on battery for a while and then rebooting and running on battery for a while solve the issue.
Hey Steffen, looks like our support team sent you an incorrect response, we apologize for this experience, it should be fixed now.
OMG. Thanks for battery trick, finally CPU clock can be adjusted again to full speed.
I’ve wasted hours trying to understand what was going wrong with my laptop, stuck at 400Mhz for no reason. It was barely usable…
I have 12th gen Intel and BIOS 3.06. I see there is a 3.08 update but ChangeLog doesn’t really mention this issue as fixed. Could we get an official answer from @Framework ? Thanks.
I’m on the 3.08 BIOS and it definitely is not fixed. I don’t believe it was intended to be.
Ah. Thank you! Hopefully they’ll find a solution at some point…
It’s interesting to see this problem happening on Framework AMD. The early Steam Decks had what appears to be this same issue. They would permanently clock down to cpu@400mhz and gpu@200mhz. People just had to RMA them until the fix was found.
Valve eventually fixed it with a firmware update (assumed bios) that resolved it:
Firmware 116
- Fixed a rare issue that would set the processor TDP limit too low causing CPU and GPU frequencies to be stuck at 400 MHz and 200 MHz respectively.
At this point I’m loosely convinced it’s a problem with the embedded controller’s firmware. Since that is / can be CPU chipset agnostic, it’s not surprising that this bug could affect CPU/GPU from more than one vendor.
It is caused by BD PROCHOT. On 13th Intel FW13, I didn’t find any way to cancel it.
Right. I’ve been tailing EC logs, and I see where it gets a thermal-high alert, then throttles. But then the temperature drops (almost immediately), but there are no log messages printed about the temp dropping or the EC unthrottling. So either there’s a bug in the EC firmware, or an issue the sensors feeding the EC information in that they don’t notify on temperature changes properly when temps are going down.
Sadly the stopped responding to the case. I guess I have to return the framework laptop and go back to Lenovo. 
Yeah, I haven’t heard back in a while either. Unfortunately I’m out of both the return and warranty periods.
Is this “BD PROCHOT” ?
There are two different PROCHOT.
- PROCHOT - Core CPU hitting limit
- BD PROCHOT - A temp sensor elsewhere on the motherboard triggering the PROCHOT state.
We would need FW Engineering to tell us where the BD PROCHOT sensor actually is?
Its times like this where users having the schematics would help a lot. 
Summary, this is not a CPU getting too hot issue, its something else thinking its getting too hot, but we don’t yet know what that something else is.
What are the fan speeds when this problem is happening?
Maybe one of the fans is not working, or a VRM is getting to hot.
Is this “BD PROCHOT” ?
There are two different PROCHOT.
No idea, is there a way for me to tell based on the EC log output?
this is not a CPU getting too hot issue, its something else thinking its getting too hot, but we don’t yet know what that something else is.
This is a good theory and seems likely, since, as I’ve noted, my CPU core temperatures are normal for some time before the throttling stops.
Would all these other sensors be reported to userspace? If so, then I’m not sure if this is it, as all temperatures are shown to be low enough. (Non “Core#” sensors I can see are “PackageId0,0”, “Iwlwifi_1,0”, “Composite,0”, “Sensor1,0”, and “Sensor2,0”.
AFAICT, “PackageId0,0” is a part of the CPU, “Iwlwifi_1,0” is (obviously) the wifi card, and the final three are related to the NVMe card.
framework_tool --thermal also gives me a look at:
F75303_Local: 46 C
F75303_CPU: 50 C
F75303_DDR: 48 C
Battery: 36 C
PECI: 49 C
F57397_VCCGT: 45 C
Fan Speed: 3079 RPM
What are the fan speeds when this problem is happening?
Not sure, but I’ll try to remember to check the next time this happens. They’re always at their loudest, though, so I expect they’re running at full tilt.
Maybe one of the fans is not working
Isn’t there just one fan? So if I hear a fan, that should be it.
FW13 - one fan
FW16 - two fans.