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.
Ah, FW13 here, so just a single fan.
This describes the design of the Intel CPUs. I have not seen the problem people are describing. This message is just be describing the design of the Intel CPU.
There is a bit of a complex pattern of events before the CPU will throttle like this.
Something too hot == H
OK temp again == O
CPU throttling == T
HTOHTOHTOHTOTOTOTOTOTOTOTOT
I.e. the CPU will behave as one would expect, too hot, throttle, OK temp again.
But, if this cycle repeats too often and close together, the CPU will just Throttle for a long period.
The challenge of course is finding out what component is getting too hot.
So, if one records temperatures over a long period, one should see the cycles of HTO until eventually the CPU stays (as per its design) in T for longer.
This is probably why FW support were asking for temperature data to be collected over time before it happens, as opposed to only collecting data after it happens.
2 Likes
Why are we left on our own to figure this out? FW dropped the ball on their design, and I have to deal with a computer that barely functions that I paid thousands for?
When is the recall happening?
1 Like
Contact support for assistance. They are best equipped to help resolve the issue(s).
No context was given. Not sure how anyone in the community could advise a course of action.
Support couldn’t solve it. (after literal months of back and forth and jumping through hoops).
Support refused a mainboard upgrade.
I want an official stance on the fact I was sold e-waste.
1 Like
Not sure why you would be entitled to a mainboard upgrade instead of a repair or replacement. That in and of itself sounds suspicious (and somewhat demanding)
If you want something official it will not be on the forums unless you want official user opinions. Put it up for sale and move on to something that has the level of support you want. Sorry you had a less than stellar experience.
The forum is end users who are invested in seeing the product succeed and offer their guidance and knowledge.
3 Likes
I’m still having this issue where the CPU gets completely stuck at 400 MHz. This time, I waited over 24 hours, but without surprise, it didn’t recover on its own. I had to use the disconnect battery trick in the BIOS to get it back to normal. Is there really no proper solution for this?
Luckily, I don’t use this laptop as a workstation, just Firefox, with quite a lot of tabs though. I’ve already replaced the thermal paste to help cooling and avoid throttling, but it still happens about once a month. I’m not convinced the cooling design is very effective.
It’s a shame, because I really appreciate the modular design, repairability, and the overall philosophy behind the Framework 13. But with problems like this, my next laptop will most likely be from a different brand. Although I could consider a motherboard upgrade if there’s a solid improvement in the latest versions.
Edit: Oh WOW. 12th Gen Intel Core BIOS 3.17 Release Stable
6. Fixed high temperature causes continuous CPU throttling to 400Mhz.
Thanks! I updated. If you do not hear back from me, it means the problem has been resolved 
2 Likes
I have BIOS 3.17 but still regularly experience the Intel 12th Gen. going into “limp mode” and throttling down until reboot without any apparent cause. 
I’m not sure if we’re experiencing exactly the same issue or if it’s something different.
In my case, when CPU gets too hot, it gets downclocked to 400MHz. This is a hardware level throttle, not controlled by the OS. Once the temperature goes down, after some time, it usually recovers its normal speed by itself. But sometimes, it gets stuck at 400 MHz and won’t unlock no matter what I do. Even rebooting doesn’t help, and the only way to reset it is by disconnecting the battery from the BIOS.
I haven’t had the chance to stress my CPU enough yet to see if the latest BIOS update actually fixes this problem for me.
I haven’t logged if there is an overtemperature event beforehand, but I too experience sudden and seemingly permanent drops down to 400MHz, which so far only went away when I shutdown, leave the laptop off for half a minute or so without charger, then do a cold start. Some of these steps might be unnecessary however, I haven’t tried to boil them down to the minimal reproducible procedure. Although so far I have not needed to disconnect the battery via the BIOS.
Oh yeah, that’s definitely strange. I have a widget to monitor temperature, but honestly, just from the fan noise alone, I know jet engine getting ready for takeoff 
Do you also hear the fan ramping up when this happens, or feel really hot when you put your hand under the laptop?
I never considered the laptop to be exceptionally quiet, and while resting on a table the underside always gets quite warm to the touch, but it indeed seems to ramp up the fan when the issue occurs. However the CPU temp then hovers around 60 degC while the throttling is persisting, so if there is a temp limit being hit and assuming the fan is controlled by the embedded controller to counteract this, then it is either some other sensor, or maybe just a bug?
Uhm, when mine gets downclocked to 400 MHz, the fan is usually full speed and the back of laptop is close to fry an egg. I stop everything to reduce CPU load and settles around 55–60 °C. Most of the time (~80%) it recovers normal speeds after about 10 minutes or so, otherwise, it just gets stuck.
But it’s a bit odd you were never able to come back to normal speed and always need to powerdown for 30 minutes. Have you reached out to Framework support, maybe they could help diagnose the issue ?
I will keep an eye on it.
Maybe I have to give it more time to recover on it’s own, but the first time I diagnosed the issue the device had already been slow for several days.