Framework Laptop 16 BIOS v4.02 and Driver v3.01 Releases (AMD Ryzen™ 7040 Series) STABLE

[Quin_Chou]

Update sequence for AMD Ryzen™ 7040 Series Mainboard:

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. If you are upgrading to the NVIDIA® GeForce RTX™ 5070, replace the Graphics Module using this guide: Expansion Bay Module Swap.

4. Update your driver bundle using this link.

This release includes two major updates:

1. 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 BIOS 4.02, you’ll need to update Keyboard/Numpad/MacroPad firmware to 0.3.1, following the instructions here.
2. This release includes support for NVIDIA® GeForce RTX™ 5070, which also needs Driver Bundle 3.01 or newer.

Highlights

1. Added support for the NVIDIA® GeForce RTX™ 5070.

• Added support for NVIDIA G-SYNC (requires a 2nd Gen Display Kit).
• Added support for the NVIDIA Advanced Optimus feature (requires a 2nd Gen Display Kit).

2. Updated the power table to support NVIDIA® GeForce RTX™ 5070.
3. Updated the standalone detection user interface (UI).
4. Updated the Framework Input Module application version check for Keyboard Firmware.
5. Updated the PD firmware to 0x22 for NVIDIA® GeForce RTX™ 5070.
6. Updated the USB Type-c UCSI version from 1.x to 2.0 standard.
7. Fixed the issue causing PROCHOT to occur when the system is under heavy load.
8. Fixed an issue where the CPU became locked at 0.55 GHz during Furmark and CPU burn stress tests.
9. Fixed an issue where the screen would flash when switching between two EPR adapters.
10. Fixed an issue where the overcurrent protection event was triggered when the AC adapter was switched between adapters.
11. Fixed an issue where the BIOS update process could run on the wrong platform, resulting in the system being bricked.
12. Fixed an issue where the Supervisor Password incorrectly displayed “Not Installed” after the user had successfully set the password.
13. Fixed an issue where the system always displayed an “invalid supervisor password” error when the user set TPM to Hidden and set the supervisor password within the same BIOS session.
14. Fixed an issue where the Wooting 80HE Keyboard did not function while in the BIOS.
15. Fixed an issue where the system would flash a black screen during DDS.

Note:

• This BIOS version is a mandatory requirement to support the NVIDIA® GeForce RTX™ 5070.
• Once you update to version 4.02, 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).

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.02.exe	A2768875EDA8BC4E0803DBA4F31027F95CFA8D5FE7F0B82D0C9AB6BAE97FCA74

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.02_EFI.zip	5403E1F2E1610E3CCD5B373B9816EA6529268652D511B96BE7EAF5F866E8CEA9

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

N/A

Enhancements

1. Added support for the NVIDIA® GeForce RTX™ 5070.

• Enabled NVIDIA G-SYNC (requires a 2nd Gen Display kit).
• Added support for the NVIDIA Advanced Optimus feature (requires a 2nd Gen Display kit).

2. Updated the GPU PD firmware to 0x22 for NVIDIA® GeForce RTX™ 5070.
3. Updated the power table to support NVIDIA® GeForce RTX™ 5070.
4. Updated the standalone detection user interface (UI).
5. Updated the Framework Input Module application version check for Keyboard Firmware.
6. Updated the USB Type-c UCSI version from 1.x to 2.0 standard.

Fixes

1. Fixed the issue causing PROCHOT to occur when the system was under heavy load.
2. Fixed an issue where the CPU became locked at 0.55 GHz during Furmark and CPU burn stress tests.
3. Fixed an issue where the screen would flash when switching between two EPR adapters.
4. Fixed an issue where the overcurrent protection event was triggered when the AC adapter was switched between adapters.
5. Fixed an issue where the BIOS update process could run on the wrong platform, resulting in the system being bricked.
6. Fixed an issue where the Supervisor Password incorrectly displayed “Not Installed” after the user had successfully set the password.
7. Fixed an issue where the system always displayed an “invalid supervisor password” error when the user set TPM to Hidden and set the supervisor password within the same BIOS session.
8. Fixed an issue where the Wooting 80HE Keyboard did not function while in the BIOS.
9. Fixed an issue where the system would flash a black screen during DDS.

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.02	Updated
EC	ec_402_c8091da	Updated
PD	0.0.21	Same
NVIDIA® GeForce RTX™ 5070 PD	0.0.22	Updated
AMD PI	1.2.0.0c	Same

Reporting Issues

To report issues we have created a public issue tracker on github. GitHub · Where software is built 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. Some power banks do not follow USB-C 3.1 EPR entry timing which is the root cause of this issue.
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.

Windows Driver Bundle

The version number has jumped to 3.01 because this new bundle now includes drivers for both the AMD and NVIDIA-based Graphics Modules for Framework Laptop 16.

Windows 24H2/25H2

Download Link	SHA256
Framework_Laptop_16_AMD_Ryzen_7040_driver_bundle_W11_v3.01_2025_11_12.exe	7A5A753FA2896C430F32411B5F242248FB323785EC26F0B91A44FB35E8E4A2B0

Driver Bundle Components

Driver	Version	Updated
AMD Chipset Driver	7.06.02.123	Updated
AMD Graphics Driver	25.10.2 (v32.0.22021.1009)	Updated
NVIDIA Graphic Driver	581.80 (v32.0.15.8180)	Added
NVIDIA App	11.0.5.420	Added
NVIDIA Control Panel	8.1.968.0	Added
Realtek Audio Driver	6.0.9859.1	Updated
Realtek Audio Console	1.53.374.0	Same
RZ616 WiFi Driver	3.4.0.1335	Updated
RZ616 Bluetooth Driver	1.1043.0.555	Updated
Goodix Fingerprint Driver	3.12804.1.270	Same
Camera Ext	10.0.22000.10002	Added
Realtek MEP Driver	10.0.22000.10003	Updated
AMD MEP Driver	32.1.0.0	Same
Microsoft MEP Driver	1.0.42.0	Same
Framework EC Driver	0.0.0.6	Same
Realtek Ethernet	11013_20_07272023_08042023	Same
SD Card Reader	v4_5_10_201	Same
2nd Gen uSD Card Reader	v4_5_10_202	Same
Monitor Driver	1.0.0.0	Same

[Xavier_Jiang]

Amazing work to see this kind of substantial rollout of BIOS features.

But I have a question: Will my old firmware keyboard continue to work? Or will they just become unresponsive until I re-flash the firmware?

[wojciech_migas]

it works, but you will get warning at boot that you should update keyboard firmware. you can skip firmware update, but to skip that warning you have to press power button to continue boot.

AFAIK without keyboard firmware update, it may happen that keyboard will wake up laptop from sleep when lid is closed

[Filip]

Is the EmbeddedController repo updated with the latest changes to the EC firmware present in this release? Wondering as I have some custom patch I apply to my EC firmware. I do not see any mention of the nvidia module in the EC repo so I’m wondering if the changes are present.

[Filip]

And that’s a no, I installed the BIOS and replaced the RW EC Firmware but it is always switching to RO. Guess I’ll be downgrading back to 03.07 until the repository is updated.

[OVER_CL0CK]

@Quin_Chou Can you guys have a running list of each “stable” version of the bios versions listed on the page? Every time there is an update you guys only have the newest one, but for some folks who are needing to roll back, the download is no longer a simple link option.

[jared_kidd]

@Quin_Chou

• Fixed the issue causing PROCHOT to occur when the system is under heavy load.
• Fixed an issue where the overcurrent protection event was triggered when the AC adapter was switched between adapters.

I applied this 4.02 version and am very disappointed to report the above were not fixed. My simple steps at the bottom of my post here still cause throttling. In fact, when I did it, it seems my cpu was throttled at a max of 10w. Running “stress-ng -c16” will only get the following frequencies:

PROCHOT still triggered when connecting or disconnecting the 180w psu:

this is pathetic:

[igimenezblb]

Was apprehensive of the 4.01 update but I bit the bullet on this one. I updated keyboard firmware, updated BIOS (was on 3.07) and updated drivers but I skipped out on the MEP drivers. Running Windows 11 25H2, all smooth sailing. I even got my highest Cinebench R23 score yet (14921). I do keep the smart charge feature on 85% and keep the laptop plugged in all the time. Haven’t had any weird behavior.

[Justin_Y]

My initial impressions of this beta update were good, but unfortunately fell apart pretty quickly once I started trying to use the dGPU. I think I am seeing the same type of throttling problems others are seeing, but symptoms were super weird. I am in Windows, with the driver bundle from this thread installed.

When plugged in to the 180w FW adapter, the CPU kept bouncing down to < 1ghz and then back up. I didn’t really pay too much attention to what exact speed it was, but it kept dropping and rebounding every few seconds while plugged in. This did NOT happen using the 65W Asus ROG Ally power adapter, nor did it happen while I was not plugged in.

Here’s what I was doing -
-streaming a youtube video in firefox
-opened steam & forza horizon 5 on battery power
-waited for fh5 to finish “optimising”
-plugged in

At this point I noticed the audio from youtube crackling (I didn’t have the stream in focus.) I doubt the specific game has anything to do with this; when FH5 started though the AMD software flipped the mux from apu to gpu. I plugged in after this happened. EDIT: Lastly will add that I have some monitor software that shows the AC plugged in status on the led matrix and while this was happening I noticed this was flipping back and forth (on and off) almost exactly in line with the drops to low cpu speeds.

I hope this helps track down the issue. I rolled back to 3.0.7 for now.

[knipp30]

Are you at 100% when seeing this? I did your steps and can’t repro. No prochot, no throttling, nothing.

[SepticFuddy]

Did this behavior start only after the update or was it an issue before? If the latter, what BIOS were you on before? Are you using FW drivers or from the chipset’s website?

[Xavier_Jiang]

No B160UAK01.5 support, unfortunate.

Keyboard blocking while lid is off is very nice to have. Seem to work flawless. Touchpad still works, but thats unimportant.

[Justin_Y]

only after updating to 4.0.2. I installed the keyboard update, then the bios and finally the drivers. It wasn’t a problem for me on 3.0.7 though I know others here have had issues with that version too.

[TechPriestNhyk]

I just wanted to come in and say that I accidentally upgraded to this BIOS version, and then experienced the 544mhz bug for the first time while playing Minecraft. This was a fresh boot, and the device was never suspended/asleep. I downgraded back to 3.05.

System:

Ryzen 7 7840HS

RX 7700s

Fedora 42

[jared_kidd]

Here is something I noticed, and it goes with my earlier tests, the 35w cpu power limit is only in effect when the dGPU is powered off.

If I am taxing the cpu (compiling a linux kernel, for example), it will still be capped at 35w.

I can launch something simple that turns on the dGPU, such as “DRI_PRIME=1 glxgears” to lift the power cap on the cpu.

As soon as I close the dGPU using program (glxgears in this example), the dGPU will sleep 3 seconds later and then the 35w cpu cap is back in place.

Here is a simple test (with FW 180w psu connected):

1. Launch an amdgpu_top session to monitor, making sure to choose the 780m (do not use s-tui because it will hold the dGPU awake once it is woken up).
2. Launch a cpu stress “stress-ng -c16”. Power cap should still be 35w, which you can see in amdgpu_top.
3. Now launch glxgears on the dGPU. On my arch system this gets it in the right place: DRI_PRIME=1 glxgears
4. watch the 35w power limit shown in amdgpu_top jump up to high 50s/low 60s.
5. Close glxgears and the cpu power will again limit back to 35w a few seconds later.

Again, this is easily repeatable.

EDIT: I just finished testing the above steps on Fedora 43, and confirmed the issue there as well. Though, oddly, the limit was 24w instead of the 35w I get on Arch Linux. I tested 3 times on Fedora with the same result each time, even after a reboot. This confirms it is not an OS issue.

[TechPriestNhyk]

One thing that may be related is that I’ve noticed (emperically) that the dGPU and CPU seem to share a common power budget in the driver. For instance, if I use ryzenadj with the dGPU installed, it’ seems to actually set the total budget for the dGPU and CPU rather than just the CPU. I orginally found this when I wanted to set CPU limits to limit fan noise… but found that it was not feasible due to it’s impact on dGPU.

[TheLPeink]

True! Power budget is shared.

You can experiment using this unofficial tool.

It’s great! You can monitor temps, set up fan curves and adjust total TDP. All for free. The guy is a dragon.

[FlyingTypeTrainer]

I had an experience similar to my last attempt at updating from 3.07 to 4.01.

Ryzen 7840 with the 7700S.

I started the 4.02 update andI had my power plugged into port 4 and after the update completed it stopped functioning for charging while port 1, the unused port, was working. I ran the update again with power plugged into port 1 and after that both ports are functioning normally. I will update with any weirdness if I see it.

[CAM-Gerlach]

The “update sequence” section and others here and on the Framework main site states multiple times that the keyboard firmware needs to be updated before updating the BIOS. However, the linked keyboard firmware page states:

BIOS requirement:

• Framework Laptop 16 AMD Ryzen™ 7040 Series - BIOS 4.01 or later

Given that 4.01 was pulled (at least to Beta status) due to a critical issue, do we really need to install that beta BIOS prior to installing the keyboard driver (which is in turn required for the keyboard to work after installing BIOS 4.02)? Or can that requirement be ignored and the sequence above followed without actually breaking things in practice? Thanks!

[jared_kidd]

@CAM-Gerlach

The “update sequence” section and others here and on the Framework main site states multiple times that the keyboard firmware needs to be updated before updating the BIOS.

If you perform an update using the recommended firmware tools, the keyboard firmware is updated first, and the bios update is staged for reboot. In the end, it does not matter which is updated “first”, just that you update both.

The keyboard is not going to “break” if you don’t update it. It just wont resolve the wake-while-lid-closed issue the update resolves.