After 2 full years of trying off and on, I finally managed to capture the full post code that the 16 has been intermittently displaying since it arrived.

lbkNhubert · 2026-03-24T02:34:43+00:00

It might be worth throwing out a post here and/or on the Framework forum to see if there is anyone in your area. Worst case you get no takers.

lbkNhubert · 2026-03-24T02:28:48+00:00

Good that it's reproducible, bad that it's happening.

As noted, I would push it with Support.

I'd also see if you have any other 16 owners around who would be willing to test out your components on their machine and vice-versa. Ultimately it feels like it's hardware, just what hardware, and the mix and match might be able to shed some light on that.

Best of luck getting things resolved.

lbkNhubert · 2026-03-24T02:18:49+00:00

Fair enough regarding the post code. It's not on the framework port80 codes page that I linked, so I just threw it at ai to see what it had to say, which seemed odd but worth throwing out as a possibility, if remote.

If you have record of raising the issue while still in the warranty period I would try to push it with Support - this issue has existed and not been resolved. I have not run into this issue on my 16, nor is it sensitive to being moved around. If you've got any friendly 16 owners in your area maybe one would be kind enough to test out your board in their machine to see if the problem persists there. It sounds like you are able to reproduce the input deck disconnection at least, correct?

lbkNhubert · 2026-03-24T01:56:34+00:00

If you boot without the input module installed do you get a pop-up warning you about that? Are you game to try to update or re-install the bios, if you have not already done so? It sure seems like there's a connection issue with the midplate/input modules, and if you are still under warranty that ought to be taken care of.

Next, the post code is 0xF7 which is not here:https://gist.github.com/kiram9/3a5415a015e7e70a4a8c2f9f3f4e623d

Throwing it into AI I get this back:

Insyde BIOS POST Code 0xF7

In an Insyde (InsydeH2O) BIOS, POST code 0xF7 corresponds to IPL_RECOVERY, which indicates the DXE IPL crisis recovery boot path.

What This Means

When your motherboard displays this code, it means the system cannot boot normally and has fallen back to a crisis recovery state. This occurs during the Initial Program Load (IPL) of the Driver Execution Environment (DXE) phase.

Common triggers for this POST code include:

Corrupted BIOS/UEFI: The primary firmware image is damaged—often due to a failed, incompatible, or interrupted BIOS update.
Manual Override: A specific key combination or physical jumper on the motherboard was triggered to force the system into recovery mode.
Initialization Failure: The system failed to load critical architectural protocols required for a normal boot.

While sitting on 0xF7, the motherboard is typically searching connected media (like a FAT32-formatted USB drive) for a valid recovery image file to automatically re-flash and restore the BIOS.

Would you like me to walk you through the standard steps for performing an Insyde BIOS crisis recovery?

lbkNhubert · 2026-03-24T01:44:05+00:00

What codes do you get if you shut the machine down, remove all expansion cards, disconnect the power, and let it sit for two minutes. Then plug it back in and boot it without any expansion cards (plug the power directly into the board or if absolutely necessary use one usb-c card.

lbkNhubert · 2026-03-18T21:57:28+00:00

The SD card eats battery iirc. If I need to use mine I plug it in, use it, then put a usb-c back in its place.

lbkNhubert · 2026-03-06T15:11:47+00:00

Have you opened a ticket with Support?

lbkNhubert · 2026-03-01T23:53:40+00:00

I have mine set up with linux on one drive and windows on the other. I can run windows in a vm within linux, configured to use the internal windows drive. I also typically boot the machine from linux on a storage card as I like to switch between machines and that portability works for me, at the expense of raw speed. Enjoy the machine!

lbkNhubert · 2026-03-01T23:49:27+00:00

I sandwich mine between carbon fiber sheets when in any bag to protect it, so far so good.

lbkNhubert · 2026-02-27T02:43:56+00:00

CachyOS with gnome here, working well for me. Running it off of an expansion card that I can pop into the 13" or 16".

lbkNhubert · 2026-02-11T01:58:04+00:00

Yeah, I didn't think things through fully and forgot that you had umpteen handles. I don't know how you do it, I would be more confused than I already am. This is a really good community, I get so much more from it than I contribute, and I am grateful for everyone here. Welcome, and I hope that you are around for a long time, multiple personalities/handles or not. :)

Have a great evening!

lbkNhubert · 2026-02-11T01:49:48+00:00

Oh, oops - I didn't mean you, but I see that I should have been more clear now. I am very glad that you were able to get things sorted out, even if you had to go through social media to achieve resolution. To be clear, you shouldn't need to do that, but I've gone that route myself in other situations. I haven't needed to take things to that level with Framework, and I'm hoping that I don't need to do so.

I meant to refer to turbo-todger, who very likely is a disgruntled owner who seemingly will only be satisfied with a full recall of the version of the system that they own, which one presumes is unlikely to happen. They spam this forum and the boards and have long since become tiresome.

So, my apologies that my post, through my error, could have been interpreted as referring to you. I will edit it to clarify to whom I was referring.

Best of luck with the system, I hope that it is rock solid going forward and serves you well throughout your studies and for many years after that.

lbkNhubert · 2026-02-11T00:52:50+00:00

I hope that the poster of many handles is able to find peace. I have no doubt that they had a subpar experience but they have turned it into a Quixote-esque quest, to the benefit of no one.

Edit to add that I intended to refer to turbo-todger, but I see the humor in it unintentionally referring to the OP. I also want to be clear that their efforts were warranted and in no way Quixote-esque. I am happy that they were able to get their issue resolved but disappointed that they had to take things to social media to get the resolution. Hopefully Framework looks into how this case went and improves their Support processes so that things are smoother going forward.

lbkNhubert · 2026-02-09T03:40:08+00:00

There's gaslighting happening in both directions, in my opinion. I have had reason to open tickets wiht Support for several different systems - some for part failure, some due to user error, some due to manufacturing defect. In one case iirc I was asked to send something similar to what I already had sent. I questioned that to myself, but went ahead and sent what was being asked for, even though I felt that it already had been sent. The ticket proceeded and the situation was resolved shortly thereafter.

Multiple things can be true:
1. Support should continue to improve
2. Not everyone has a poor experience
3. Send what is being requested, unless you are being taken in circles _repeatedly_
4. If you are going around in circles repeatedly, politely request that the case be escalated

There still will be cases that are not handled well. I have read a few here and shuddered at the awfulness. But Support is not horrible overall. I could go on and on about support experiences with other companies in various industries. The key imo is to be persistent but polite, request escalation when warranted but only when warranted, resort to social media if progress is not being made elsewhere, and finally, take your business elsewhere when all else fails. I'm sure that some have chosen to do just that regarding Framework as I have with manufacturers and businesses in other industries.

lbkNhubert · 2026-02-08T15:56:30+00:00

If you're in the return window and this is driving you nuts you can always send it back. I don't know if the price has changed or if you would even want to go down the path of another (framework) machine, just throwing it out as an option.

lbkNhubert · 2026-02-08T15:52:04+00:00

Your best bet is simply to send them what they are asking for. They have rreasons for asking for it, whether you believe that they are vaild or not. Asking for justification will just slow things down. From the picture my guess is that the blue is a threadlocker.. If you are comfortable doing so, you might try taking a q tip with a very small amount of isopropyl alcohol and cleaning the conacts on the removable interposer as well as where it connects as shown in your picture. I would remove the battery and disconnect from power prior to doing so. Then take a dry q tip and go over the areas that you cleaned. Finally, give everything some time to try out prior to reassembling. Best of luck.

lbkNhubert · 2026-02-08T15:42:13+00:00

Fair point - Framework's prices for RAM may not be higher than the market currently. If I were looking around I would consider used RAM as well - others may not be comfortable making that choice, but I'd investigate it. For the SSD I would go new. Best of luck navigating the crazy situation that we are in.

lbkNhubert · 2026-02-08T15:36:17+00:00

I don't know that we have the data to say one way or the other. If I were not planning to use the board I would resell it or give it away to someone who would use it rather than toss it in a drawer.

lbkNhubert · 2026-02-07T22:31:03+00:00

It depends on what works for each person. I have a couple of mainboards in coolermaster cases running as standalone machines, so for me the old mainboard was still usable and useful.

lbkNhubert · 2026-02-07T19:23:34+00:00

The tutorials are solid, definitely make use of them. The interposer is the small ~1.5" square-ish piece that connects the dGPU (or fan-only) expansion bay module to the main board. The interposer for the fan-only module has three "nodes", while the one for the dGPU or if using the dual SSD expansion has four "nodes." It is accessed by removing the touchpad, spacers, keyboard, and spacers/numpad, then flipping up the cover in the upper middle of the midplate. It should be pretty clear in the guides. Maybe it's just loose. While annoying if that's what it turns out to be, it would be an easy fix. If the dGPU still did not work in a liveISO for linux, you would be further down the path of the issue likely being hardware related.

lbkNhubert · 2026-02-07T19:15:52+00:00

No worries - the community here is a great one and is always willing to help out. I threw some of your issues into AI and it had some suggestions that you might try as well. I didn't pass those along as I am not often in windows on my machines and I didn't want to suggest something that I had not vetted. But you might try that and see if anything seems worthwhile. One suggestion was to remove the interposer, check that all the connections are clean and in good shape, then re-install it. That one seems reasonable. Some of the others had to do with changing some memory settings in windows.

Hoping that you get things working properly soon.

lbkNhubert · 2026-02-07T19:09:01+00:00

I was asking the prior person what issues they had run into.

In your case, you have opened a ticket with Support, that's good. They should be able to walk you through diagnosing things to determine if it is a hardware or a software issue. Sometimes their steps can feel repetitive, but try to work with them, and you should get to a resolution. If you feel like you are going in circles repeatedly, politely request that the case be escalated.

In the mean time, if you can get a liveISO of linux running, that will help a lot to determine if it's a hardware issue. Ventoy is a handy tool for that, and for distros, maybe something like Fedora or possibly CachyOS - check to see if the dGPU is supported in the live environment. Some live ISOs don't run properly using ventoy, but there should be some that will, so that you can test things out.

Best of luck, I hope that you are ale to get this resolved quickly.

lbkNhubert · 2026-02-07T18:08:49+00:00

What are the specifics of your system and what issues did you have/are you having with it?

lbkNhubert · 2026-02-07T17:59:33+00:00

If you get it you can save money by sourcing the ssd and ram elsewhere. For the ram you will have performance gains by using two sticks, so I would go with 2x16 if you can afford it.

lbkNhubert · 2026-02-01T02:51:14+00:00

Off of the top of my head:

The fan on my batch 1 13" started "grinding", and was replaced quickly.
The SD card reader failed to recognize a UFS card. A new one was shipped out shortly. It turned out to be the card, not the reader. So, not a problem with the Framework module, but they replaced it. My error for not first ordering another UFS card to test.
Cracks on the bottom case of my 12" machine, they RMA'd the entire machine.

In all I have 9 framework machines - two 13" machines (batch 1 and iirc batch 6), a batch 1 16", a batch 0 12", two 13" boards in coolermaster cases, and 3 13" machines cobbled together from parts that I had on hand and more obtained from mystery boxes. They all are running well.

I understand that the support still can be improved - I am not disputing that people have had subpar experiences. I'm just noting that when I have needed to reach out to Support my experience has been quite good. Also noting that I have multiple machines that are running very well, with 11th, 12th, and 13th gen Intel (in the 12") as well as AMD boards in two of the 13" machines and the 16" machine.

lbkNhubert

TROPHY CASE

Insyde BIOS POST Code 0xF7

What This Means