# Framework Laptop 13 Ryzen 7040 BIOS 3.20 Release STABLE **URL:** \ **Category:** Framework Laptop 13\ **Tags:** laptop-13-chassis, laptop-13-pro-chassis, bios, bios-announcement, amd-7040\ **Created:** [June 30, 2026, 2:10am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283 "2026-06-30T02:10:49Z")\ **Posts on this page:** 20\ **Page:** 2
**Author:** ![NineLives](https://avatars.discourse-cdn.com/v4/letter/n/cdc98d/32.png) [@NineLives](https://community.frame.work/u/NineLives)\ **Post date:** [July 14, 2026, 4:45pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/21 "2026-07-14T16:45:56Z")
I’m not on the latest BIOS yet, but I can confirm this behavior in my standalone 7840U. Installing the RTC battery available from the Framework marketplace resolves the issue. ---
**Author:** ![Richard\_Lee1](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@Richard\_Lee1](https://community.frame.work/u/Richard_Lee1)\ **Post date:** [July 14, 2026, 7:12pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/22 "2026-07-14T19:12:18Z")
Thank you for that confirmation. The thing is, it’s able to remember everything else through complete power loss. It remembers that I disabled TPM. It remembers my max battery charge level. And so on. Why can’t it remember the simple Auto/Game setting for the UMA? ---
**Author:** ![DataBase](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/database/32/48360_2.png) [@DataBase](https://community.frame.work/u/DataBase)\ **Post date:** [July 15, 2026, 12:14am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/23 "2026-07-15T00:14:21Z")
Have you reported it here: > **[Issues · FrameworkComputer/SoftwareFirmwareIssueTracker](https://github.com/FrameworkComputer/SoftwareFirmwareIssueTracker/issues)** > > Public Issue Tracker for Firmware Issues related to Framework Products - Issues · FrameworkComputer/SoftwareFirmwareIssueTracker ---
**Author:** ![Mathias](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@Mathias](https://community.frame.work/u/Mathias)\ **Post date:** [July 15, 2026, 8:20am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/24 "2026-07-15T08:20:29Z")
Someone with a bricked device should also report the issue on GitHub, otherwise this may not get the needed attention. ---
**Author:** ![Richard\_Lee1](https://avatars.discourse-cdn.com/v4/letter/r/5e9695/32.png) [@Richard\_Lee1](https://community.frame.work/u/Richard_Lee1)\ **Post date:** [July 15, 2026, 3:42pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/25 "2026-07-15T15:42:39Z")
Just reported it. > > > \## Device Information > > \### System Model or SKU > > Please select one of the followi…ng > > \- \[\] Framework Laptop 12 (13th Gen Intel® Core™) > \- \[\] Framework Laptop 13 (11th Gen Intel® Core™) > \- \[\] Framework Laptop 13 (12th Gen Intel® Core™) > \- \[\] Framework Laptop 13 (13th Gen Intel® Core™) > \- \[x\] Framework Laptop 13 (AMD Ryzen™ 7040 Series) > \- \[\] Framework Laptop 13 (AMD Ryzen™ AI 300 Series) > \- \[\] Framework Laptop 13 (Intel® Core™ Ultra Series 1) > \- \[\] Framework Laptop 16 (AMD Ryzen™ 7040 Series) > \- \[\] Framework Laptop 16 (AMD Ryzen™ AI 300 Series) > \- \[\] Framework Desktop (AMD Ryzen™ AI 300 PRO Series) > > \### BIOS VERSION > All versions so far, to 03.20 > > \### DIY Edition information > Memory: Crucial CT2K16G56C46S5 > Storage: SK Hynix Gold P31 2TB > > \### Port/Peripheral information > Nothing plugged in, other than 4 pass-through Type-C cards. > > \### Standalone Operation (Laptop Only) > Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS? > \- \[\] Yes > \- \[x\] No > > \## Describe the bug > With BIOS -\> Advanced -\> iGPU Memory set to "Gaming," full loss of power (Battery Disconnect & power disconnect) causes it to get reset to "Auto." > > NineLives in the Framework Community also confirmed that the same thing happens in Standalone Mode without the optional RTC battery. > > \## Steps To Reproduce > Steps to reproduce the behavior: > 1. Connect to an external power. > 2. Enter BIOS Setup. > 3. Configure Advanced -\> iGPU Memory to "Gaming." > 4. Go to Advanced -\> Battery disconnect and select YES. > 5. Follow through, so the Laptop shuts off. > 6. Disconnect external power. > 7. To confirm that the battery disconnect took effect, press the power button and make sure nothing happens. > 8. Reconnect external power. > 9. Enter BIOS Setup again. > 10. Advanced -\> iGPU Memory setting should have reverted to "Auto." > > \## Expected behavior > Firmware is able to remember everything else through complete power loss, so it should be able to remember the iGPU Memory setting of "Gaming" as well. > > \## Operating System (please complete the following information): > \- OS not involved. ---
**Author:** ![fish\_177](https://avatars.discourse-cdn.com/v4/letter/f/a4c791/32.png) [@fish\_177](https://community.frame.work/u/fish_177)\ **Post date:** [July 17, 2026, 10:31pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/26 "2026-07-17T22:31:05Z")
Updated 7840U board from 3.17 → 3.20 via lvfs on f44 with no problems, just took awhile. ---
**Author:** ![David\_Henry](https://avatars.discourse-cdn.com/v4/letter/d/e19b73/32.png) [@David\_Henry](https://community.frame.work/u/David_Henry)\ **Post date:** [July 19, 2026, 8:16pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/27 "2026-07-19T20:16:46Z")
Updated 7840U board from 3.18 → 3.20 via lvfs and… it get stuck at two blue dots 😥 I can now follow the [BIOS update stuck](https://community.frame.work/t/bios-update-stuck/83416) thread… ---
**Author:** ![Charlie\_6](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/charlie_6/32/22087_2.png) [@Charlie\_6](https://community.frame.work/u/Charlie_6)\ **Post date:** [July 21, 2026, 8:30am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/28 "2026-07-21T08:30:42Z")
> [@Richard\_Lee1](#): > > BIOS remembers everything else, even through battery disconnect, so why can’t it remember the iGPU UMA setting? Did you have the RTC coin cell installed. If not, the iGPU UMA setting reset could be the result of memory training. ---
**Author:** ![David\_Henry](https://avatars.discourse-cdn.com/v4/letter/d/e19b73/32.png) [@David\_Henry](https://community.frame.work/u/David_Henry)\ **Post date:** [July 22, 2026, 8:15pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/29 "2026-07-22T20:15:41Z")
Ok I successfully fixed it myself thanks to the following community guide: > [@Success in recovering from bad BIOS upgrade - Framework 13 AMD 7040](https://community.frame.work/t/success-in-recovering-from-bad-bios-upgrade-framework-13-amd-7040/66598/50): > > Really great topic, saved my motherboard after a BIOS upgrade failure! (3.18 → 3.20) I followed your steps (bought the same stuff for ~32€, used the same tricks with ceramic coasters - first time I used them in ten years sweat_smile, same commands) and it worked! Some notes: I also did four ROM reads and got one failure (the second read). The pogo was stable. Reading the ROM takes 4m40s. I extracted the 3.20 BIOS from the UEFI capsule b… ---
**Author:** ![HHPC\_IT](https://avatars.discourse-cdn.com/v4/letter/h/ecb155/32.png) [@HHPC\_IT](https://community.frame.work/u/HHPC_IT)\ **Post date:** [July 24, 2026, 12:32am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/30 "2026-07-24T00:32:06Z")
This just happened to us when upgrading from BIOS 3.18 (one of the few, most remained on 3.17) to 3.20. We’ve already updated 10 machines without issue, but number 11 locked up during the BIOS update and now the laptop is bricked. ---
**Author:** ![Mathias](https://avatars.discourse-cdn.com/v4/letter/m/bbe5ce/32.png) [@Mathias](https://community.frame.work/u/Mathias)\ **Post date:** [July 24, 2026, 6:23am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/31 "2026-07-24T06:23:17Z")
What do we know about the bricking? Does it only occur while upgrading from 3.18? My Laptop 13 at work is still on 3.17, and my private one is on 3.19, and I’m afraid to upgrade to 3.20. ---
**Author:** ![Charlie\_6](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/charlie_6/32/22087_2.png) [@Charlie\_6](https://community.frame.work/u/Charlie_6)\ **Post date:** [July 24, 2026, 8:11am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/32 "2026-07-24T08:11:28Z")
I upgraded from 3.16 to 3.20, no problem during the process. Either the bricking rate is higher from 3.18, or it’s irrelevant of version as most computers were 3.18 before flashing 3.20 ---
**Author:** ![yuip](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/yuip/32/15742_2.png) [@yuip](https://community.frame.work/u/yuip)\ **Post date:** [August 1, 2026, 4:31pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/33 "2026-08-01T16:31:35Z")
So I’m holding upgrading to this version given the issues some people have had bricking their laptops, which I think never occurred before. Do we know if this is happening only on laptops with Linux or it has nothing to do with the OS? ---
**Author:** ![Omair](https://avatars.discourse-cdn.com/v4/letter/o/898d66/32.png) [@Omair](https://community.frame.work/u/Omair)\ **Post date:** [August 2, 2026, 9:48am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/34 "2026-08-02T09:48:28Z")
went straight from 3.19B ( because i was not going to have my laptop not connect to my KVM for my convinience) to 3.20, no issues whatso ever ( although i did not have any USB connected to the laptop when i initiated the upgrade. ---
**Author:** ![CKC](https://avatars.discourse-cdn.com/v4/letter/c/5fc32e/32.png) [@CKC](https://community.frame.work/u/CKC)\ **Post date:** [August 4, 2026, 10:49am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/35 "2026-08-04T10:49:50Z")
Reading this thread, I think i’ll skip this version since I’m out of warranty 🙁. Who knows what would happen if i decide to roll the dice. ---
**Author:** ![Rei](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/rei/32/13593_2.png) [@Rei](https://community.frame.work/u/Rei)\ **Post date:** [August 4, 2026, 6:24pm UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/36 "2026-08-04T18:24:17Z")
Does anyone relate to this issue? [Framework 13 AMD 7840U freeze on Linux kernel 7.0.0 and 7.0.1](https://community.frame.work/t/framework-13-amd-7840u-freeze-on-linux-kernel-7-0-0-and-7-0-1/82167) I notice it happens occasionally, unexpectedly on my system these days 🫤 kernel 7.0.11 ---
**Author:** ![goldenspinach](https://avatars.discourse-cdn.com/v4/letter/g/f1d935/32.png) [@goldenspinach](https://community.frame.work/u/goldenspinach)\ **Post date:** [August 6, 2026, 10:48am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/37 "2026-08-06T10:48:42Z")
This is an absolutely insane situation. Given all the random bricking, nobody should be upgrading to BIOS 3.20. Framework should immediately withdraw BIOS 3.20 from circulation and revert to 3.18 as the latest stable release. BIOS 3.20 should be treated as radioactive material. On top of that, refusing to replace out-of-warranty bricked mainboards because of a faulty BIOS is very poor form. If you’re providing BIOS updates for your own hardware, you’re setting up a perfectly reasonable expectation that the BIOS upgrade is guaranteed to work on that hardware. Otherwise there is really no point in providing BIOS upgrades. Reading the " [BIOS update stuck](https://community.frame.work/t/bios-update-stuck/83416) " thread is essentially a horror story. Users should not resort to hardware hacking to fix a fault caused by Framework. No reputable company would allow this dumpster fire to continue. CC [Matt\_Hartley](https://community.frame.work/u/matt_hartley) ---
**Author:** ![Richard\_Tango-Lowy](https://avatars.discourse-cdn.com/v4/letter/r/67e7ee/32.png) [@Richard\_Tango-Lowy](https://community.frame.work/u/Richard_Tango-Lowy)\ **Post date:** [August 7, 2026, 3:50am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/38 "2026-08-07T03:50:46Z")
> Does anyone relate to this issue? [Framework 13 AMD 7840U freeze on Linux kernel 7.0.0 and 7.0.1](https://community.frame.work/t/framework-13-amd-7840u-freeze-on-linux-kernel-7-0-0-and-7-0-1/82167) I had this problem on 7.0.0 and 7.0.1, but not since. Now on 7.1.6 and no problems. ---
**Author:** ![Engstrom](https://avatars.discourse-cdn.com/v4/letter/e/ad7895/32.png) [@Engstrom](https://community.frame.work/u/Engstrom)\ **Post date:** [August 8, 2026, 8:57am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/39 "2026-08-08T08:57:11Z")
I contacted support regarding bricked out of warranty mainboards caused by Framework’s bios, and received this response: _“If your device is out of warranty, we will still review the case, but coverage for replacement or repair cannot be guaranteed.”_ This essentially means you’re on your own if a BIOS update fails. @Quin_Chou Would it not be appropriated to clearly state in the first post that if you update your computer with this official STABLE BIOS and it bricks your device, Framework will not cover the repair? Also, if I understand points 1 and 2 in the changelog correctly, I need 3.20 to upgrade my non-Pro laptop with Pro components. Does this mean my two year old laptop is now effectively EOL? How does this align with Framwork’s mission statement? ---
**Author:** ![inffy](https://sea1.discourse-cdn.com/flex001/user_avatar/community.frame.work/inffy/32/39079_2.png) [@inffy](https://community.frame.work/u/inffy)\ **Post date:** [August 8, 2026, 9:15am UTC](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283/40 "2026-08-08T09:15:33Z")
Updated through LVFS and no issues seen. Well I avtually already updated in the beta period [Previous page](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283.md?page=1) [Next page](https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-20-release-stable/83283.md?page=3)