My DIY edition running Win10 is getting stuck clocked at .39Ghz. This happens even when plugged in. After a reboot it runs at full speed for a minute or two, then reverts to .39Ghz. [image] I’m following the instructions on this thread and this did not fix it.

[image] Iann_C: Have you tried kernel 5.18 ? It brings a lot of improvements for 12th gen. Like 20% efficiency even on high loads. That would be 5.19, I guess

@cowpod Two adjustments you can make on Throttlestop that potentially could be a temporary fix until framework comes with a bios fix… The problem seems to be when it throttles to some critical temperature, it goes to 400 mhz and doesn’t know how to come back up again. You could maybe use throttlestop to decrease the temperature at which it throttles 2-3C so it never gets too hot, though if the bug could happen anytime it throttles, this might cause the bug to happen more frequently. Another potential solution may be to lower the turbo ratios down incrementally to decrease the spiky nature of turbo and or set PL1 and PL2 time to infinity and cap the TDP value to a wattage that it will never reach a thermal limit and start throttling. You can maybe start at 28W and increase or decrease the TDP to maximize wattage while never throttling.

Have you tried kernel 5.18 ? Yes, I’m running Debian testing, which is on 5.18 now. I’ve also tried 5.19 (in experimental), but that caused unusable mouse pointer jerkiness and stuttering.

I’m getting stuck on 0.39 Ghz with both linux and windows 10 on the alderlake laptop. I just started up the laptop today and it was slow, even in the BIOS. It doesn’t make any difference if it’s on battery or plugged in, it’s still stuck at 0.39 ghz edit: hmm, disabling the battery through the BIOS seems to have fixed this… edit 2: This is weird… it seems like the disconnect battery option only applies for the next reboot (it isn’t saved like the rest of the BIOS settings). Anyways, I think what happened was that I set the “disconnect battery” option, then on the next boot I disconnected the power to see if disconnecting the battery would cause it to fail to boot. It seems like it tried to boot, but ran out of power and shut off again. This seems to have reset something internally and fixed my problem in the process, so I will leave this here for anyone else who happens to stumble on this issue: My steps were to set the “disconnect battery” option in the bios, then disconnect the power and try to turn it on again. It should try to boot without power and then fail. After that, it should work.

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. [image] [RESPONDED] 12th gen - excessive CPU throttling on Linux - Can't get above 46c and pegs to 400mhz under load Linux For those interested, I had and still have the same issue. Updated the BIOS to the alpha version, re-pasted with PTM7950, double checked the pad locations for the VRMs, the whole nine-yards. I received a replacement mainboard after months of troubleshooting and the thing idles around 80C and will still clock-throttle down to 400 MHz even at 60C. Then it will constantly jump to 100C and trigger PROCHOT again. I repeated the same procedures that I did with the original board, at my own expense ag…

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.

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.

Clock stuck at .39Ghz

Community Support

Asa_Kaczynski April 13, 2023, 1:04am 216

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.

Topic		Replies	Views
[RESPONDED] CPU gets stuck at 0.2 GHz Linux	125	47054	January 7, 2025
Framework Laptop 16 Ryzen 7040 BIOS 3.06 Release BETA -Held Framework Laptop 16 bios-announcement , framework-laptop-16-amd-7040	158	9391	September 27, 2025
Framework 400MHz issue Framework Laptop 13 intel-12th , laptop-13-chassis	74	1849	September 8, 2026
Framework Laptop 13 - 12th Gen Intel Core BIOS 3.19 Release STABLE Framework Laptop 13 intel-12th , bios-announcement	54	3706	May 25, 2026
CPU sometimes gets stuck in some sort of low power mode Linux nixos	77	3151	September 26, 2026

Clock stuck at .39Ghz

Related topics