Framework Laptop 16 Ryzen 7040 BIOS 3.07 Release BETA

[Quin_Chou]

Highlights

1. Added Framework’s dbx key and updated the default CA of Windows Secure Boot.
2. Fixed an issue where hardware encryption on OPAL drives could cause a missing boot drive on subsequent reboots.
3. Fixed the issue where the CPU was stuck at 545MHz after the system resumed from sleep.
4. Fixed battery drain issues occurring with the Balanced Power Profile.
5. Introduced Battery Charge Limiting status functionality.
6. Introduced the Framework EC device.

Note:

1. Once you update to 3.07, you can only downgrade to the previous version.
2. Install the latest driver bundle 2.05 or newer with BIOS 3.07. Although the Framework EC device will show a yellow bang without it, the system’s functionality remains unaffected.

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

After the beta release, we will monitor community feedback, and publish this release to our stable release channel after approximately one week if no major issues are reported.

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.

Battery Extender functionality

With the high energy density on the 61Wh battery, leaving it at 100% state of charge for an extended period of time can shorten the lifetime of the battery. To prevent this, we have added a new feature that automatically limits the maximum state of charge if the system is left plugged into power for more than 5 days. The timer is reset after the system is disconnected from a power adapter for more than 30 minutes.

Battery Extender Duration	Battery State of Charge
0-5< Days	99% → 100%
5-7 Days	90% → 95%
>7+ Days	85% → 87%

This functionality also reduces cycling of the battery by allowing the battery to discharge by several percent before charging again. Note that in addition to this automatic setting, you can also manually set a lower charge limit on your battery in BIOS to further preserve battery longevity.

This feature can be disabled or enabled in the BIOS Advanced menu.

Battery Extender: This option is enabled by default. If disabled, the system will always keep the battery fully charged.

Battery Extender Trigger: This option sets the number of days that must pass before the battery state of charge is reduced automatically to extend the battery life.

Battery Extender Reset: This option sets the number of minutes that the system is running on battery before the extender is reset, causing the system to charge to 100% when attached to power again.

Battery Charge Limit Functionality

This release modifies the battery charge limit functionality to add a 5% float range. This allows us to reduce the number of microcycles on the battery when the CPU turbos.
Previously to the change in 3.05, the battery would be held at the target state of charge, so if a large power draw happened for a short time, such as when the CPU turbos, the battery would drain slightly and then charge again.
Introduced in this version, the battery will not start to charge until the battery has dropped 5% below the charge limit.

As an example, if the user sets the battery charge limit to 80%, the battery will maintain a state of charge between 80% and 75%. And will not charge up to 80% until it has discharged to 75% while the system is on.

If this is activated while the battery state of charge is above the limit, the battery will discharge without drawing power from the adapter until the upper limit is reached.

Downloads

Windows

Download Link	SHA256
Framework_Laptop_16_Amd_Ryzen7040_BIOS_3.07.exe	0E3457E774226EC459F8BFD93B1D716FA1FDF1F0607FF65B09F810991DE8B773

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

Updating via LVFS is available in the testing channel during the beta period.

You can enable updates from testing by running

fwupdmgr enable-remote lvfs-testing

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_3.07_EFI.zip	6241F5EDF3D3DB347FCF9A5E9CD08438EFBFE49A51EEC5579F59EF2278EA0FC2

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
CVE-2024-21925	Improper input validation within the AmdPspP2CmboxV2 driver may allow a privileged attacker to overwrite SMRAM	8.2
CVE-2024-0179	SMM Callout vulnerability within the AmdCpmDisplayFeatureSMM driver could allow locally authenticated attackers to overwrite SMRAM	8.2
CVE-2025-4275	A vulnerability in the digital signature verification process does not properly validate variable attributes which allows an attacker to bypass signature verification by creating a non-authenticated NVRAM variable.	7.8
CVE-2025-2884	TCG TPM2.0 Reference implementation’s CryptHmacSign helper function is vulnerable to Out-of-Bounds read due to the lack of validation the signature scheme with the signature key’s algorithm.	6.6
CVE-2024-36347	Improper signature verification in AMD CPU ROM microcode patch loader may allow an attacker with local administrator privilege	6.4
CVE-2024-49200	An issue was discovered in AcpiS3SaveDxe and ChipsetSvcDxe in Insyde InsydeH2O with kernel 5.2 though 5.7. A potential DXE memory corruption vulnerability has been identified.	6.4
CVE-2024-36350	A transient execution vulnerability in some AMD processors may allow an attacker to infer data from previous stores	5.6
CVE-2024-36357	A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D cache	5.6
CVE-2024-36348	A transient execution vulnerability in some AMD processors may allow a user process to infer the control registers speculatively	3.8
CVE-2024-36349	A transient execution vulnerability in some AMD processors may allow a user process to infer TSC_AUX	3.8

Enhancements

1. Updated to AMD PI 1.2.0.0c.
2. Added Framework’s dbx key and updated the default CA of Windows Secure Boot to Microsoft UEFI CA 2023.
3. Introduced Battery Charge Limiting status functionality to support Windows Smart Charging feature.
4. Introduced the Framework EC device to enable the Framework tool on Windows. Linux already supports the tool.

Fixes

1. Fixed an issue where hardware encryption on OPAL drives could cause a missing boot drive on subsequent reboots.
2. Fixed battery drain issues occurring with the Balanced Power Profile.
3. Fixed the issue where the CPU was stuck at 545MHz after the system resumed from sleep.
4. Fixed “Force Power for Input Modules” setting was not working.
5. Security Fixed - CVE-2024-36348, CVE-2024-36349, CVE-2024-36350, CVE-2024-36357, CVE-2024-36347, CVE-2024-0179, CVE-2024-21925, CVE-2024-49200, CVE-2025-2884, CVE-2025-4275.

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	3.07	Updated
EC	ec_307_03829d	Updated
PD	0.0.1E	Same
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.
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.

[jared_kidd]

Awesome. Just want to confirm before I waste my time upgrading…. This 3.07 is different than the “alpha” 3.07 that was floating around a couple weeks ago, correct? I just want to confirm the terrible issues that alpha version was causing have been resolved (or attempted to) for this beta 3.07?

Also,

@Quin_Chou

Once you update to 3.07, you can only downgrade to the previous version.

Do you mean I can go back to 3.05 if this one is still broken in some way?

[jared_kidd]

Dang, the md5 is the same between this “beta” and the terribly broken “alpha” from a couple weeks back.

Serious question for Framework: Why are you releasing a confirmed broken bios for everyone to use? Also, why is it so painfully hard for you to get us a working bios update?

[tacsist]

Cannot say for 240w chargers, but the erratic GPU clocks have remained with 140w chargers. Seems that it might be slightly better than previously, I do not get as drastic of hitching and sound corruption as before (still unplayable though). It seems to coincide with CPU usage, so if the game is more CPU heavy, the worse are the dGPU clocks jumps.

[TheLPeink]

Con confirm stutterness with 140W BASUES.

I know it’s not easy, but se really need true third party chargers compatibility…

[James3]

The notes in the original post above refer to “61Wh battery”.

Is that a typo, or can you use a 61Wh battery with the FW16 ?

[alderonmatt]

Thanks for trying to release a bios update, but the quality of these is just so terrible. Please make sure you have a test plan that you execute for all the bios updates to test all the combos of these things. Don’t rely on the community to find everything.

I have been using a different laptop because the quality of the firmware is so bad with so many issues.

[sinatosk]

After trying BIOS 3.05, 3.06 and now 3.07

At one point I thought I wasn’t experiencing the FTH issue anymore because I thought they were bugs in Linux ( they were and they got fixed ) but I was wrong, it’s still happening ( I don’t know yet for 3.07 )

and the FTR issue is too still happening

from this point, I’m starting to have loss of words and I’m getting sick and tired of sounding like a verbose parrot here

[the9thdude]

I noticed that there’s a keyboard firmware update being pushed alongside the 3.07b update. Is this the fabled keyboard wake fix?

[jared_kidd]

You are mistaken. There is no keyboard update:

No update in the downloadable files either. They did say they were going to release keyboard/sleep updates but they have not yet.

[the9thdude]

Oh, I guess I just got a little excited The wait continues…

[knipp30]

@Quin_Chou

On 3.07, in the bios, it is not possible to change the device boot order. I can view the boot order, but the options are greyed out and cannot be changed. (NVM the bios changed the boot prio to auto, this works now)

Using the 240w charger, the stuttering is much more reserved, but I still observe battery drain when gaming (balanced mode, Fedora) and when it wants to charge, said stuttering continues.

Not sure if its the F43 update, or the 3.07 bios change, but I also noticed a decent drop in Cinebench scores since doing the bios update. I was getting about 15,700, now I see about 14,700. Not thermal throttling, as my highest core sits at about 95 degrees during the test.

[Quin_Chou]

We’ve confirmed that the 240W adapter is now compatible with the BIOS 4.00 candidate for the Framework Laptop 16 (Ryzen 7040 with AMD 7700/NV 5070). However, since the 3.06 beta, we’ve updated the EC to correct the power settings when system is connected with 240W, so the PROHOT event is caused by the current monitor IC in specific condition.

This update includes a fix that prevents a PROHOT event caused by the current monitor IC. The issue is now reliably reproducible, and we have a solution. This fix is included in the BIOS 4.00 candidate, which is on track for internal alpha release this week. We plan to release the beta and stable versions in the next two weeks. We will not be releasing a new BIOS 3.08 version for this fix, as the release schedule for 4.00 is very similar. This will be listed as a known issue in the 3.07 stable release until the 4.00 stable version is available.

[Richard_Ullger]

Hi,

Is PROHOT another event or are you referring to PROCHOT_CPU and PROCHOT_GPU and does this also fix it for the FW 180w charger?

I can reliably reproduce in 3.05.

1. Boot up on battery power.
2. Log into DE, in my case XFCE on Arch
3. Run amdgpu_top. Change the device to dGPU. Throttle status is clear. Throttle status doesn’t display for iGPU.
4. Connect the FW 180w charger. In my case USB-C in port 1.
5. Throttle status immediately shows PROCHOT_CPU and PROCHOT_GPU although no throttling is evident and temperatures are below 40°c.

Battery extender is turned off, battery limit is set to 80%.

[TheLPeink]

Amazing! If you need people to test out 4.00 with the Delta 240W, Baseus 140W and Framework 180W I’m willing to put my FW16 to good use

[jared_kidd]

Thank you for confirming I am not the only one experiencing this. I reported it over here and further above in that thread.

@Quin_Chou unfortunately dismissed the issue.

[Nate_Hanna]

Ditto this. I’m not up to date on the jargon, but I’ve experienced the 545MHz bug after unplugging and plugging back in with the 180w adapter since BIOS 3.05. Does this beta or potentially the 4.00 release address that?

[jared_kidd]

@Richard_Ullger is not referring to the 545MHz issue at all. They are talking about the PROCHOT flags getting triggered when connecting the 180W charger, which has been an issue for a long time, at least back to 3.05.

This 3.07 version apparently does “fix” the 545MHz issue, but I personally have not left it installed long enough to tell if it really fixes it, or just brought it back to the frequency that it occurred on 3.05, which was less frequent. 3.07 causes other issues, particularly for those with the 7700s graphics installed, in that it throttles down to 1000-1400MHz any time power state is changed on the 7700s. This is even more unacceptable for my usage (games), so I am sticking on 3.05 until they fix all these issues, if ever.

[Quin_Chou]

We have also verified this with the 180W configuration using the BIOS 4.00 candidate. Based on your information, I will inform the validation team to test it thoroughly before release.

[Abilio_Costa]

Does this also fix the issue where the CPU throttles down to 1GHz during high loads? amdgpu_top shows “EDC_CPU” throttling when that happens.
It usually also happens after resuming from sleep on battery.