Clock stuck at .39Ghz

Putting this here too…

Hi there, don’t know if anybody else tried this, but I may have found a workaround to keep this problem from happening:
The only caveats are that it keeps the CPU from using the full speed available, but it keeps the laptop stable, and if you update the BIOS it resets the settings, so make sure to keep an eye on that.
If you go into BIOS and set CPU to Max-Non Turbo Performance and Disable Intel SpeedStep, SpeedShift and Turbo Boost Max, then it should keep the problem from happening.
This is with a Intel 11 i5, 16gb RAM and Windows 11, but it also fixed the problem on a Intel 12 i5 as well.
Hope this helps somebody!

Same experience, linking to my previous reply for visibility. I have tried everything - there is a major issue here, whether it be in power delivery in firmware or elsewhere.

Edit: nevermind :frowning: after another half hour or so, one of the core temperatures spiked to 100C, and now all cores are stuck throttled down to 400MHz again.

Thought I’d follow up here as well: after going through a ton of troubleshooting steps, Framework Support finally sent me a new mainboard, and that seems to have solved this issue (Excessive CPU thermal(?) throttling on 12th-gen - #12 by kelnos for details).

Hi everyone!

I own a Framework Laptop 13 DIY edition

my laptop’s CPU (12th gen Intelcore i7 - 1260p) has been stuck at 0,4 GHZ. I understand that this might be a BIOS issue, however i haven’t change any, nor there’s a resent update for them.

I would like to learn how to reset this particular bios settings or which setting I have to change.

regards,
Gabriel

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. :frowning: