# Framework Laptop 16 occasionally stuck at 0.55GHz even on latest BIOS

**URL:** <https://community.frame.work/t/framework-laptop-16-occasionally-stuck-at-0-55ghz-even-on-latest-bios/85125>\
**Category:** Community Support\
**Tags:** framework-laptop-16-amd-7040, other-issues\
**Created:** [September 27, 2026, 7:30pm UTC](https://community.frame.work/t/framework-laptop-16-occasionally-stuck-at-0-55ghz-even-on-latest-bios/85125 "2026-09-27T19:30:51Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![dmx0987654321](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/dmx0987654321/32/21947_2.png) [@dmx0987654321](https://community.frame.work/u/dmx0987654321)\
**Post date:** [September 27, 2026, 7:30pm UTC](https://community.frame.work/t/framework-laptop-16-occasionally-stuck-at-0-55ghz-even-on-latest-bios/85125/1 "2026-09-27T19:30:52Z")

</div>

Sometimes when I’m using my laptop normally, the processor gets stuck at 0.55GHz for 1-5 minutes and the system becomes sluggish as a result. I’ve deduced the following:

- Restarting fixes it temporarily
- Plugging/unplugging power adapter (or anything else) does not change it, and it can occur with or without power
- It does not seem correlated to running games or other demanding applications, it can happen when running nothing but a browser
- Unlike prior posts with this problem, it does not seem connected to sleep mode, as it can occur following a restart

My system is as follows:

- Windows 11 25H2
- Framework Laptop 16 (AMD Ryzen 7 7840HS, RX 7700S installed)
- BIOS version 04.05

 ![20260927_160036(1)](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/4/1/41fec4efdc86175203cc730383618b6c0ded7755.jpeg)

(Apologies for the photo, the system was too sluggish to screenshot)

---

<div class="post-metadata">

**Author:** ![pkunk](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@pkunk](https://community.frame.work/u/pkunk)\
**Post date:** [September 28, 2026, 3:57am UTC](https://community.frame.work/t/framework-laptop-16-occasionally-stuck-at-0-55ghz-even-on-latest-bios/85125/2 "2026-09-28T03:57:45Z")

</div>

This has been an issue for a while now on the Framework Laptop 16. It likely has has multiple issues and have been slowly resolved but others still keep cropping up like a bad game of whack-a-mole.

File a ticket with support so they know there are more issues related to this ongoing. It has gotten better but something else keeps leaving the system stuck in this state which is not normal.

---

<div class="post-metadata">

**Author:** ![ZzyzZ](https://avatars.discourse-cdn.com/v4/letter/z/9de0a6/32.png) [@ZzyzZ](https://community.frame.work/u/ZzyzZ)\
**Post date:** [September 28, 2026, 6:27am UTC](https://community.frame.work/t/framework-laptop-16-occasionally-stuck-at-0-55ghz-even-on-latest-bios/85125/3 "2026-09-28T06:27:30Z")

</div>

There are other laptop with historic precedence, I still have no idea what caused it but my ASUS TUF with a 4800H back in 2018 had this issue for a while a few years back. Stuck at 0.37 GHz and unusable.

Idk how it was fixed, it happened as suddenly as it is resolved. If you search around online there are still residuals of people asking for a fix [Reddit](https://www.reddit.com/r/AMDLaptops/comments/urexkf/4800h_stuck_in_377mhz/)

I didn’t update firmware, didn’t reinstall OS. I just remember I tried a bunch of things and miracally it just stopped happening after plaguing me for a good few months.

Ik this is not entirely relevant to FW but probably look around and see if it’s a broader problem.

---

<div class="post-metadata">

**Author:** ![wojciech\_migas](https://avatars.discourse-cdn.com/v4/letter/w/35a633/32.png) [@wojciech\_migas](https://community.frame.work/u/wojciech_migas)\
**Post date:** [September 28, 2026, 8:11am UTC](https://community.frame.work/t/framework-laptop-16-occasionally-stuck-at-0-55ghz-even-on-latest-bios/85125/4 "2026-09-28T08:11:53Z")

</div>

> [@dmx0987654321](#):
>
> - on 04.05

please reach out to @Quin_Chou if I good remember he was sharing beta bios over github which should solve this issue. [CPU frequency stuck at low values after suspend/resume on firmware 3.06 · Issue #91 · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub](https://github.com/FrameworkComputer/SoftwareFirmwareIssueTracker/issues/91#issuecomment-5076673996)

---

<div class="post-metadata">

**Author:** ![dmx0987654321](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/dmx0987654321/32/21947_2.png) [@dmx0987654321](https://community.frame.work/u/dmx0987654321)\
**Post date:** [September 28, 2026, 9:07pm UTC](https://community.frame.work/t/framework-laptop-16-occasionally-stuck-at-0-55ghz-even-on-latest-bios/85125/5 "2026-09-28T21:07:01Z")

</div>

Thanks for your suggestions. @wojciech_migas I’ve let him know on Github, we’ll see if anything comes of it.

---

<div class="post-metadata">

**Author:** ![dmx0987654321](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/dmx0987654321/32/21947_2.png) [@dmx0987654321](https://community.frame.work/u/dmx0987654321)\
**Post date:** [October 1, 2026, 10:06pm UTC](https://community.frame.work/t/framework-laptop-16-occasionally-stuck-at-0-55ghz-even-on-latest-bios/85125/6 "2026-10-01T22:06:17Z")

</div>

Keeps happening so I took system logs of it happening a few times with HWInfo, then reached out to support with the data. As luck would have it, Microsoft saw fit to release 26H2 48 hours ago, so I have further testing to do, but I’ll update this post if it stops happening.

Edit - Nope, still happens:

 ![image](https://us1.discourse-cdn.com/flex001/uploads/framework3/original/3X/d/e/de5facf694ec3df6ab20bc90cd02e0a7d58478de.png)

---

<div class="post-metadata">

**Author:** ![dmx0987654321](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/dmx0987654321/32/21947_2.png) [@dmx0987654321](https://community.frame.work/u/dmx0987654321)\
**Post date:** [October 10, 2026, 8:21pm UTC](https://community.frame.work/t/framework-laptop-16-occasionally-stuck-at-0-55ghz-even-on-latest-bios/85125/7 "2026-10-10T20:21:50Z")

</div>

Reset my mainboard and tried a few other things to no avail. Support suggested I do the liquid metal replacement on my Batch 1 CPU, but I’m not going to go that far just yet because it doesn’t seem likely that this would fix it. I’ll try a different operating system and see if that changes anything.

---

<div class="post-metadata">

**Author:** ![pkunk](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@pkunk](https://community.frame.work/u/pkunk)\
**Post date:** [October 11, 2026, 3:05am UTC](https://community.frame.work/t/framework-laptop-16-occasionally-stuck-at-0-55ghz-even-on-latest-bios/85125/8 "2026-10-11T03:05:23Z")

</div>

Probably not going to fix the speed limitation like you said unless it is truly being driven by a thermal spike because over time the liquid metal had a tendency to pump out and not provide the same effective heat transfer to the heat sink.

Not a bad suggestion really. If it still is a BIOS issue then the gain will be that the future potential thermal issues would be eliminated with the known issues from the liquid metal design that was in the first generation models. It had the potential to be good just some characteristics that were not fully understood with implementation that was deployed.
