# Framework Laptop 16 Ryzen 7040 BIOS 4.04 Release STABLE

**URL:** <https://community.frame.work/t/framework-laptop-16-ryzen-7040-bios-4-04-release-stable/81740>\
**Category:** Framework Laptop 16\
**Tags:** bios, bios-announcement, framework-laptop-16-amd-7040, framework-laptop-16-amd-ai-300, graphics-module-nvidia-5070, graphics-module-amd-rx7700s\
**Created:** [April 10, 2026, 7:04am UTC](https://community.frame.work/t/framework-laptop-16-ryzen-7040-bios-4-04-release-stable/81740 "2026-04-10T07:04:14Z")\
**Posts on this page:** 1\
**Showing post:** 38

<div class="post-metadata">

**Author:** ![Guillaume\_C](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/guillaume_c/32/39715_2.png) [@Guillaume\_C](https://community.frame.work/u/Guillaume_C)\
**Post date:** [May 20, 2026, 11:15pm UTC](https://community.frame.work/t/framework-laptop-16-ryzen-7040-bios-4-04-release-stable/81740/38 "2026-05-20T23:15:31Z")

</div>

Well, i already have more info, and a repro for the 545(/544)MHz bug.

It seems to be due to a race condition between consecutive calls of `\_SB_.PCI0.GPP0.M241(1)`, the matching EC PMF handler, and `\_SB_.PCI0.GPP0.M241(0)`.

The easiest way to trigger it is:  
`# echo '\_SB_.PCI0.GPP0.M241 0x01' >/proc/acpi/call; cat /proc/acpi/call; sleep 0.1; echo '\_SB_.PCI0.GPP0.M241 0x00' >/proc/acpi/call; cat /proc/acpi/call`

It still is probabilistic, so it won’t always happen (and also sometimes it locks the freq to 1400 MHz instead), but it happens roughly 60% of the time, which is a great step towards identifying the underlying cause.

---

_[View the full topic](https://community.frame.work/t/framework-laptop-16-ryzen-7040-bios-4-04-release-stable/81740)._