Framework Laptop 16 Ryzen 7040 BIOS 4.05 Release STABLE

Framework Laptop 16
, , , ,
1

This BIOS version has been officially promoted from Beta to Stable. If you already updated to this version during the Beta phase, no further action is required—your firmware is identical to the final release.

Updating from 3.0x

Update sequence for AMD Ryzen™ 7040 Series Mainboard and the NVIDIA® GeForce RTX™ 5070 Graphics Module:

  1. If you are planning to use your Keyboard (1st Gen), RGB Macropad (1st Gen), or Numpad (1st Gen), you’ll first need to update your keyboard firmware using this link.
  2. Update your Framework Laptop 16 (AMD Ryzen 7040 Series) BIOS to the latest by following the instructions on this link.
  3. Replace the Graphics Module using this guide: Expansion Bay Module Swap.
  4. Update your driver bundle using this link.

Highlights

  1. Updated AMD AGESA to PhoenixPI-FP8-FP7_1.2.0.0f
  2. Updated input module app to 0.3.16.
  3. Update G-Sync VK key for NVIDIA 5070 12G Graphic Module.
  4. Fixed an issue that unexpected 35W CPU power limit when AMD dGPU is in BOCO mode.
  5. Security Fixes - CVE-2024-36343, CVE-2024-36345, CVE-2025-54502.

Note:

  • The BIOS version 4.0x is a mandatory requirement to support the NVIDIA® GeForce RTX™ 5070.
  • Once you update to version 4.05, the only compatible downgrade path is to BIOS 3.05 or any newer version (this restriction applies only if you are using UMA graphics or the AMD RX7700).
  • We’ve changed the keyboard standby/lid-close behavior to suspend the input device when the lid is closed, preventing unintended waking. Before updating your laptop to the latest from 3.0x, you’ll need to update Keyboard/Numpad/MacroPad firmware to 0.3.1, following the instructions here. If you already performed this and are on 4.0x there is no need to update again.
  • This release includes support for NVIDIA® GeForce RTX™ 5070, which also needs Driver Bundle 3.02 or newer. The BIOS version 4.0x is a mandatory requirement to support the NVIDIA® GeForce RTX™ 5070.

You can check your current BIOS version following the steps here to determine if you are on the latest release.

Subscribing to release notifications

If you want to subscribe to new release notifications you can now opt in through this link to receive an email when we release a new BIOS or driver update for your Framework Laptop.

Downloads

Windows

Download Link SHA256
Framework_Laptop_16_Amd_Ryzen7040_BIOS_4.05.exe 1D2CDB356F3140A44581262ED958D20D777BA575D4E0CBC85C198A635C817A48

|

Instructions for Windows Installer:

  1. Run the .exe.
  2. Click yes to reboot.
  3. Wait for the firmware progress bar to complete, and then the system will reboot.
  4. If you are updating a system in standalone mode, please pay careful attention to the standalone update process below.

Please note that you must update with a charger attached.

Linux/LVFS

Please note that you must update with a charger attached, then run:

fwupdmgr refresh --force

then

fwupdmgr get-updates

then

fwupdmgr update

Please note that you must update with a charger attached.

LVFS may not update if the battery is 100% charged. LVFS uses the battery status to determine if it is safe to apply updates. However if our battery is at 100% and the charger is off, we set the battery charging status to false. In this case you can discharge your battery a few percent, then plug in AC again and run fwupdmgr update.

Linux/Other/UEFI Shell update

Download Link SHA256
Framework_Laptop_16_Amd_Ryzen7040_BIOS_4.05_EFI.zip FE161F4894D565A3ACE3E7D9640AEAAAE872DB440DC17D39B3A3A4EAA53DBA93

Note that if you use the EFI shell update with Windows, you should suspend Bitlocker if enabled before updating using the EFI updater.

Instructions for EFI shell update:

  1. Extract contents of zip folder to a FAT32 formatted USB drive. Cleanly unmount the drive before physically removing it, otherwise the BIOS update may not function correctly.
  2. Attach a charger to your device while updating.
  3. Boot your system while pressing F12 and boot from the thumb drive.
  4. Let startup.nsh run automatically.
  5. Follow the instructions to install the update.

Security Fixes

Module Name Vulnerability Score (CVSS 3.x)
CVE-2024-36343 Improper input validation in the System Management Mode (SMM) communications buffer could allow a privileged attacker to perform an out of bounds read or write to a limited section of the Top of Memory Segment (TSEG) memory region, potentially resulting in loss of confidentiality or integrity. N/A
CVE-2024-36345 Improper input validation in the AMD OverDrive (AOD) System Management Mode (SMM) module could allow a privileged attacker to perform an out-of-bounds read, potentially resulting in loss of confidentiality. N/A
CVE-2025-54502 Incorrect use of boot service in the AMD Platform Configuration Blob (APCB) SMM driver could allow a privileged attacker with local access (Ring 0) to achieve privilege escalation potentially resulting in arbitrary code execution. N/A

Enhancements

  1. Updated AMD AGESA to PhoenixPI-FP8-FP7_1.2.0.0f
  2. Updated input module app to 0.3.16.
  3. Update G-Sync VK key for NVIDIA 5070 12G Graphic Module.

Fixes

  1. Fixed an issue that unexpected 35W CPU power limit when AMD dGPU is in BOCO mode.

Component Versions

This BIOS update is a bundle of updates to multiple embedded components in the system.

Not all of them use the same version number.

BIOS 4.05 Updated
EC ec_405_2246d58 Updated
PD 0.0.21 Same
NVIDIA® GeForce RTX™ 5070 PD 0.0.22 Same
AMD PI 1.2.0.0f Updated

Reporting Issues

To report issues we have created a public issue tracker on github. Issues · FrameworkComputer/SoftwareFirmwareIssueTracker · GitHub We hope that this is a better way to track issues with community involvement moving forward as we have found it difficult to both gather relevant information about issues people are reporting on the forums, and track the issues through their lifecycle in a transparent way.
If you do experience an issue with the update that is related to your system firmware, please post as complete a description as you can, including relevant system information, and external peripherals. Please note that we do not currently have a SLA for responding to issues on github, but we will be reviewing them through the bios release process, and will review them for future updates as well.

If you have an issue regarding hardware, broken devices, returns, etc, this is not the place, please contact support.

Known Issues

  1. Type-c connection may be unstable with some Apple phones.
  2. Cannot negotiate charging for certain portable EPR power banks.
  3. If a device is plugged into an expansion card slot during the update, all USB3/DP functionality will be lost until the device is removed and reinstalled, or the system is fully shut down and powered on again. (Power off, unplug the charger, wait 90 seconds, and then power on again to recover). This issue has an occasional failure rate.
  4. Intermittent CPU frequency lock at 545MHz following S3/Modern Standby resume.
2 Likes
Framework 16 BIOS Update LFKN6.04.01 bricked my laptop
2

is it 1.2.0.0e or 1.2.0.0.f?
if user does not have dedicated GPU is there any reason to update to the latest bios form 4.04?

3

This is confusing, as this behavior change is not new in 4.05, it was introduced in 4.00 or 4.01. Users like me who already have the 4.0x series installed are not getting new lid-closed behavior by upgrading to 4.05.

4

That’s why the heading of the update section says “Updating from 3.0x”…There are probably still some on the 3.x bios series.

That said, I don’t see what was “fixed” in this version. What do we need to test and verify? There are at least 3 major bugs I can think of off the top of my head. But I doubt all of these were fixed.

5

based on previous release it looks like:

  • some changed in EC to handle 35w power limit in BOCO
  • AMD AGESA updated from 1.2.0.0e to PhoenixPI-FP8-FP7_1.2.0.0f
  • CVE-2025-62626
  • CVE-20225-54514
6

Does this bios fix the recent change that locked the RX7700s to 100w and nothing higher/lower (used to be able to OC to 120w)

7

Sorry about that, the correct version is actually 1.2.0.0f (just fixed it in the forum).

The G-Sync VK key for the new GPU model enables native G-Sync support without the watermark. I still suggest upgrading to this version since the new AMD PI packs security patches and fixes the AMD dGPU power limit bug.

1 Like
8

I’ll sync with the team on whether to update the string to avoid confusion. For context, the message remains because users still running 3.xx need to follow these instructions to upgrade to the latest version and enable support for the new module.

9

No, we will investigate this further. 4.05 was actually finalized two weeks ago.

1 Like
10

When will the EC changes show up in GitHub - FrameworkComputer/EmbeddedController at fwk-tulip-29169 · GitHub?

11

While updating to this version today I got a graphical glitch and now the laptop is not starting. This is my support ticket ENCJ8S4D.

12

I’ve got some bad news. Updated from 4.0.4 and plugged in my 240w brick. Booted up and not long after, my power connection started connecting and disconnecting over and over. I find this odd because 4.0.4 and 4.0.5 use the same PD software, so it could have been happening over time, but I tried switching ports, both back ports don’t work. The back left port just bounces over and over back and back right doesn’t respond to anything. Tried a smaller power brick, same issue. Tried BIOS “remove battery” function to no avail, tried unplugging and even removing battery for 5 min, nope. Plugged back in and I noticed I could smell something faint, like burnt electronics. Started hunting down the smell and found it a suspected location behind the rear left USB port. Pulled the board to check… yep. QT140 on back of the board near primary charging port didn’t survive.

IMG_4693
IMG_46931920×2560 796 KB

2 Likes
13

I pulled out a spare Framework 16 motherboard I got from a mystery box a while ago, and on my board QT140 is the same components as QT139: a small SMD component labeled NQ. Googling that SMD component marker points to several zener diodes and transient voltage suppressors, which makes sense if this popped because of overvoltage or something similar. You might get away with just replacing that component if you can get the detailed specs for a replacement.

EDIT: Found a datasheet that looks relevant: https://services.taiwansemi.com/storage/resources/datasheet/SMBJ%20SERIES_R2104.pdf
In this datasheet, NQ is listed as a voltage suppressor with part number SMBJ75.

14

So after assessing the situation support is sending me replacement motherboard.

1 Like
15

Well, that’s concerning.

16

Now the big question … what was the cause?

And regarding this bios version, the 544MHz bug is still very much there. Still triggers every day if my laptop is on 24/7. After 2+ years now, I’m really starting to wonder if this bug is a design flaw and un-fixable.

2 Likes
17

I will make a bet that it is fixable. there was comment added recently in github issue, that they have found root cause and looking for volunteer to test new bios.

18

Yes, I was one who requested that test bios and am running it at this moment. And yes, my laptop got locked down to 544MHz today as always. They have not identified nor fixed it yet.

For context, my laptop is left on all day most days. It has systemd timers set up to change the battery charge limit to 70% in the morning, and then back to 100% at 5pm in preparation for evening gaming or roaming around. It seems to happen when the charge limit is set back to 100% but I have not been around to do an in-depth test.

19

I was looking for an update on that. I don’t have this issue, but to me it’s a great litmus test if the BIOS is worth updating.

20

I find it crazy that I STILL suffer from this 0.5 Ghz bug and Framework can’t seem to fix it.