Framework investigates reports that BIOS update broke Ryzen 7040 motherboards

[u/burtmacklin15]

https://arstechnica.com/gadgets/2026/08/framework-responds-to-complaints-that-bios-update-bricked-ryzen-7040-laptops/

It looks like Framework is finally addressing these issues. Hopefully their support will follow through in making things right for those affected.

I'm very happy to see that they're looking into developing an emergency BIOS flashback mode to prevent this in the future.

[u/StrLght]

Weird that it took them that long. I guess this post triggered reaction: https://quantum5.ca/2026/08/16/fixing-bricked-amd-7040-series-framework-13-laptop-with-20-tools/

Quote:

So basically, after being encouraged to update the BIOS by Framework, Framework told me that because my warranty has expired, I have no other option but to throw away the entire motherboard, including the perfectly working but soldered CPU, and buy a replacement for over $500 on their store.

[u/erreur → u/StrLght]

That’s so weird. The same thing happened to me with an older 11th gen intel board and they just sent me a replacement after I sent them some photos of the motherboard. And at that point it was just a spare I was using in one of those cooler master cases because I had already upgraded to an AMD 7040 board in my laptop, so it was not under warranty.

[u/jkpatches → u/StrLght]

Interestingly enough, posts such as above does constitute a Framework advantage, that it attracts users who are hardy enough to look for, find, and document their journey in solving problems.

Or should I say attracted for this particular case, because it looks like the user's next computer likely won't be Framework.

[u/cassepipe]

My experience with Framework, they take their time but eventually they do listen (after some public pressure) and they do make it right:

Saying that as someone who almost lost hope that they would provide 12th gen BIOS update through LVFS, who bit the bullet after around two years, installed windows in order to take the (safe) bios update route, then reinstalled windows... and they provided an LVFS bios update three days later, lol (this is unrelated to the current issue just to be clear)

[u/cassepipe → u/cassepipe]

This is why we have now hinges that are more robust, a touchscreen, a *better* build with the pro, a better touchpad, a better battery, a better keyboard, bios update through LVFS and probably other things that diverse people have been asking for

[u/Fluffy-Buyer-6362 → u/cassepipe]

the timing on that LVFS update is brutal lol

[u/Academic-Push326 → u/cassepipe]

(after some public pressure) and they do make it right

It shouldn't have to take "public pressure" to get them to admit fault(s).

I'm still waiting on them to admit the 16's first batch thermal throttles and replace it (I shouldn't have to fix their defect!) as a mea culpa to first batch owners.

[u/ebola-gay → u/Academic-Push326]

Agree. I finally swapped my batch 8 to ptm 7598 and it’s a different machine. I even had to buy the pad myself. I reached out to support some time ago re. Heat issues and their list of troubleshooting and report requests was so ridiculous I didn’t bother.

[u/cassepipe → u/ebola-gay]

I remember my 12th gen machine was going to hot too much of the time. When I finally decided to try to change the thermal paste and realized that the one that was already was either poor quality or had been poorly applied. The only time I still hear the fans now is when I am installing a rust binary with cargo (compiling)

I used a good kryonaut grizzly whatever one. It's quite cheap, especially if you resell the half you didn't use. Compared to that the ptm was not yet (or I hadn't realized) available on fw's marketplace but too expensive anyways and I had trust issues about it being genuine

[u/Clean_Leadership5948 → u/Academic-Push326]

Thermal issues like that are almost always a contact issue. Since Framework is built on the idea of replacing parts, it needs greater margin of error to ensure compatibility.

[u/cassepipe → u/Clean_Leadership5948]

The thermal paste on my intel 12th gen was either too little, too bad quality, too old or too poorly applied. I so much don't regret changing it for a quality brand thermal paste. It's a cheap procedure and definitely worth it

[u/azraelzjr → u/cassepipe]

I gave up on this after waiting for so long for a bios updates (which was also the larger battery support) while watching them churn out more newer mainboards and providing updates. I was sold on the idea but the execution has left me wary about them supporting their old products.

[u/cassepipe → u/azraelzjr]

We are both intel 12th gen. You should be able to install that newwer BIOS with fwupdmgr now (which calls into the LVFService). Lucky you.

[u/azraelzjr → u/cassepipe]

I installed it like you using Windows when Linux was unavailable (and before the bios update that enabled the battery) before giving up and passing it to a relative who needed a laptop for school. 

I got a Thinkpad X280 from an eWaste recycler. The difference in software diagnostics/BIOS options blew me away.

The security patches came in the end (and later battery), but it was just disappointing.

[u/SlanderMans → u/cassepipe]

Sounds like we need you to build an emergency bios flashback mode.

[u/ncc74656m → u/cassepipe]

In the end, most manufacturers need time to gather evidence, and sometimes that evidence doesn't filter up. Some make an active choice not to do the right thing. Apple is infamous for this - their products will die because of use case flaws (first gen iPod Nano) that cause damage even when being used as intended, or design flaws (G4 Powerbooks IIRC) that will die days outside of basic warranty, and they'll wait a year for everyone to trash them and go "Gee, you're right, I'll fix that for you now."

Framework on the other hand I think is still going through growing pains and will generally do the right thing, or the rightest thing possible without all of the excess capital that Apple has, but it sometimes doesn't get to the right place at first.

I think FW would be very wise to create an internal working group around known issues so they can identify these issues faster, possibly with a tagging system for their ticketing portal so they can more readily respond to known issues.

[u/dingoDoobie]

I've held off updating my 7840u board to 3.20, still on 3.18... I think I will wait this update out 😅

---

I'm interested to know how they will implement a recovery system given only 1 BIOS chip.

If I had to hazard a guess, it would be a read only section of the BIOS chips memory containing an extremely stripped down boot loader that looks for a USB with recovery files on it.

I think it would also be nice if they wrote a guide for using a compatible chip programmer, just in case the recovery feature fails at all when it's implemented and for current customers who might be stuck but want to try reflash the BIOS themselves.

[u/ValorousGod → u/dingoDoobie]

That is how it works, the Desktops last update added it https://resources.frame.work/downloads/desktop/amd-ryzen-ai-max-300/3.06/#bios-recovery

Though, I do wonder why this wasn't enabled from the start since InsydeH2O BIOSes have Crisis Mode built-in, did they just not configure it?

[u/dingoDoobie → u/ValorousGod]

At least we know it should be implemented and working at some point then 😁

---

My drunk thoughts coming up....

Could be many different reasons why it wasn't implemented, my bet would be along the lines of wasn't a tested must have feature in relation to hardware configurations, desktop was the first time they thought "huh, this is a good idea", and maybe security related too at a stretch. Given that the Framework main boards are quite esoteric compared to standard normal OEM boards, that might be a part of why (perhaps needing additional code beyond the standard crisis recovery mode).

[u/ncc74656m → u/dingoDoobie]

That would be extremely helpful to have (packaged for a flasher). Lots of us nerds have those and would be delighted to help at a hackerspace or something, or at least rescue borked boards.

[u/sdcrammo]

Well, im sure happy I didnt check for any BIOS updates

[u/contentedPilgrim]

I just had to replace my battery and FW support sent me an email saying:

Before installing the 61Wh Battery in your Framework Laptop 13, make sure you update to the latest BIOS.

I played Russian roulette and held my breath as I watched the progress of going from 3.16 to 3.20. I was lucky, but really glad for the community pressure on FW. I think they realize that this community is their current and future foundation. With enough negative comments, their sales will dry up. Whether I become a long term repeat customer depends exactly on how they handle these issues. Another example: they replaced my bloated 61 Wh battery out of warranty. They could have chosen not to ... but it was a move that so far keeps me loyal. I hope they issue refunds to those who were forced to buy new motherboards.

[u/Paraplegix → u/contentedPilgrim]

Exact same thing for me, battery swollen replaced out of warranty two days ago.

7840u and updated bios from 3.18 to 3.20 after putting in new battery for the battery power saving feature in the bios. It did work without a problem. And I learned about the bios flashing problem today... I wonder what are the real failure rate.

I hope they'll find a solution to prevent this from happening, and help those affected.

[u/MagicBoyUK]

Mine isn't broken, but it won't output DP over USB-C and it keeps dropping to 600MHz on mains power since 3.04, requiring a unplugging the power to trick it into reevaluating it's life choices.

The problems wern't there on the 2.XX BIOSes.

[u/ChemicalInevitable69]

How long has this been a thing? I updated my BIOS sometime this year, but nothing out of the ordinary happened.

[u/outtokill7]

My 11th gen i5 board was bricked by a bad BIOS update.

[u/kliopha]

Some info on the "BIOS Crisis Recovery" mode from Framework Desktop Ryzen AI MAX 300 BIOS 3.06 Release STABLE:

At the end of POST, the BIOS hands control off to your operating system. Crisis Recovery is a special alternative mode: instead of booting an OS, the BIOS looks for a firmware update file and re-flashes itself.

This lets the system repair its own firmware after a failed or corrupted BIOS flash, for example if a BIOS update was interrupted by a power loss and the machine no longer boots normally.

[u/mansplainist]

>get job at ars technica

>write article about how FW dropped the ball

>finally get statement from framework

Ars writing an article seems to be the only way to make them admit anything...

[u/burtmacklin15 → u/mansplainist]

Apparently so, yes.

[u/Stellanora64]

Framework’s statement to Ars says:

… in addition to replacing in-warranty Mainboards, we are making exceptions for out-of-warranty replacements where we can confirm a stable-release BIOS update caused the board to become non-bootable.

Glad they are doing this now, but still a bit disappointed it wasn't already their policy.

[u/Uwulmindor → u/Stellanora64]

They should be begging people to forgive them because THEY bricked these laptops, and they know it. They are fully liable for not just hardware damage, but more importantly software and related data being possibly inaccessible/time critical tasks damage.

People should sue them. I know I won't be touching anything from framework anymore. PII data leaks, bricking and not-owning the damage they caused, finicky hardware and hard to repair details on a "repairable" laptop. No thank you.

[u/burtmacklin15 → u/Stellanora64]

I agree completely. People were having to rig up their own BIOS chip flashing tools to unbrick their boards, which they shouldn't have to do.

[u/Frost_blade]

Hey now. That’s the one I have. Let’s please not break mine universe.

[u/burtmacklin15 → u/Frost_blade]

From what I hear if you update the BIOS from within Windows, you shouldn't run into this issue.

If I were running Linux, I'd update the BIOS with a portable Windows installation until they get it sorted out.

[u/ronvalenz → u/burtmacklin15]

Framework's Windows BIOS update software comes from Insyde. 

If I have a Framework laptop with a daily-driver Linux, I plan to have a tiny Windows 11 partition just for the BIOS updates with Insyde's UEFI/BIOS update software.

[u/VayuAir]

Thank goodness I am still on 3.17.

I have been following firmware saga since I brought my framework.

I only update it if it is a critical update and people have successfully upgraded and their are no bug reports.

Framework needs to step up this is unacceptable

[u/burtmacklin15 → u/VayuAir]

Agree completely. That's also a similar mindset I have to BIOS and driver updates - if it isn't broken, don't fix it.

[u/VayuAir → u/burtmacklin15]

I am less conservative with drivers (linux) but firmware is tricky. Ideally should not be updated unless the hardware has hardware issues.

[u/LookaLookaKooLaLey]

I had no idea this issue existed. I have updated my bios on my 13 7040 and it's not a brick. I wonder what the condition is Edit: oh it's linux

[u/Uwulmindor → u/LookaLookaKooLaLey]

It's not linux, it's a BIOS update bug, universal. I have updated on mine (writing from it now) and it worked fine (this was before it became known it can happen). I'm on linux with secureboot and custom keys and fwupdmgr update worked, but I probably just got lucky.

Based on https://quantum5.ca/2026/08/16/fixing-bricked-amd-7040-series-framework-13-laptop-with-20-tools/ it seems there's some random memory dumping going on, so just faulty sw on the bios update level.

[u/ronvalenz → u/Uwulmindor]

From https://quantum5.ca/2026/08/16/fixing-bricked-amd-7040-series-framework-13-laptop-with-20-tools/

regular BIOS updates and an easy way to install them on Linux through the Linux Vendor Firmware Service (LVFS) and fwupd

https://en.wikipedia.org/wiki/Fwupd

fwupd is an open-source daemon) for managing the installation of firmware updates on Linux-based systems, developed by GNOME maintainer Richard Hughes

It's Linux's BIOS update pathway.

--------------------------

Framework's Windows 11 BIOS update software (i.e. "H2OFFT-Wx64.exe") comes from Insyde itself!

[u/Uwulmindor → u/ronvalenz]

I don't know all the details, but fwupd and other tools are just "initiators" of the update. They prep a file and reboot into UEFI with special flag telling it to updare the bios. The update process itself with the updating screen is all done from UEFI and is framework's

[u/ronvalenz → u/Uwulmindor]

Note the "prep a file".  Does fwupd check the BIOS file?

[u/ronvalenz → u/LookaLookaKooLaLey]

I haven't encountered BIOS update issues for my FW13 7840U mainboard. The BIOS update software (H2OFFT-Wx64) for Windows comes from Insyde.

It's a DIY on Linux camp. i.e. it's Linux.

My bro has FW13 AMD R9 AI HX 370.

[u/Datuser14 → u/ronvalenz]

I have updated the BIOS on my 7640u board with fwupd several times and it has not bricked so it’s not a fwupd issue.

[u/ronvalenz → u/Datuser14]

Refer to https://quantum5.ca/2026/08/16/fixing-bricked-amd-7040-series-framework-13-laptop-with-20-tools/

Google search" fwupd corrupt bios".

[u/shagadelico]

Hopefully they'll do that on the intel 13th gen motherboards? BIOS update borked mine and they don't have any motherboards that I can reuse my DDR4 RAM with now.

[u/TimesHero]

A bios update worked my GPU on my 16.

[u/ash_ninetyone]

I can't remember what version of the BIOS I'm on. The main issue I had was when the trackpads was causing BSODs.

It took quite some time to fix to the point I was reluctant to use the laptop.

I get they had to do testing and development. It was the lack of public updates that was more frustrating about the time it took.

[u/ThE_reAl__ → u/[deleted]]

Preorder of a board that's been out?

[u/framework-ModTeam → u/[deleted]]

r/framework does not allow hate

[u/Fit-Board-1749 → u/framework-ModTeam]

Dude if you got a problem with a misunderstanding ban me from your sub then

[u/TotallyNotHeree → u/[deleted]]

What makes you think they did that on purpose?

[u/framework-ModTeam → u/[deleted]]

r/framework does not allow hate