Clock stuck at .39Ghz

Does this thread describe a different problem to the undermentioned?

This is still an issue in 2026. Is there an explanation from staff? A remedy even? Despite the 100s of posts and users experiencing this, i’m yet to see anyone in the organisation comment on the matter.

I have a 12th Gen Intel(R) Core™ i7-1260P. It was stuck at 10% of max frequency or CPU min MHz (400). I had it plugged in for days, and went through many suspend.

I plugged off the power and all expansion cards (2 USB C, 1 USB A and one HDMI). Let it off for 2 minutes, turned it on without expansion cards. It went back to normal. I plugged in all the cards, and it is still performing good.

If the system will lag again I will try to report.

Yeah. This bug has hung around but, for whatever reason, only affects some people and not others.

Here’s some threads for reference:

https://community.frame.work/t/framework-laptop-13-intel-12th-gen-stuck-on-400-mhz-or-not/72185

https://community.frame.work/t/laptop-running-at-400mhz-390mhz/23741

https://community.frame.work/t/processors-fixed-at-400-mhz-as-of-a-few-days-ago-for-no-apparent-reason/62141

And here’s a post from user @mahe who came up with a workaround to the issue:

https://community.frame.work/t/framework-laptop-13-12th-gen-intel-core-bios-3-19-release-stable/75567/40