# Framework instability with 0x08000800 fabric flood **URL:** \ **Category:** Linux\ **Tags:** ubuntu\ **Created:** [April 21, 2026, 6:35pm UTC](https://community.frame.work/t/framework-instability-with-0x08000800-fabric-flood/81955 "2026-04-21T18:35:50Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Andrew\_Meadows](https://avatars.discourse-cdn.com/v4/letter/a/b19c9b/32.png) [@Andrew\_Meadows](https://community.frame.work/u/Andrew_Meadows)\ **Post date:** [April 21, 2026, 6:35pm UTC](https://community.frame.work/t/framework-instability-with-0x08000800-fabric-flood/81955/1 "2026-04-21T18:35:50Z")
Which Linux distro are you using? Ubuntu Which release version? 24.04.4 LTS Which kernel are you using? 6.17.0-20-generic Which BIOS version are you using? 3.0.3 - 3.0.4 has an AMD bug that causes freezes. Which Framework Desktop model are you using? (AMD Ryzen™ AI Max 300 Series) AMD Ryzen AI Max+ 395 w/ 128GB RAM * * * Continue to get crashes. With 3.0.4 I would get a GPU freeze-up. Downgrading to 3.0.3 worked for a while until in the middle of a long-ish video conference the system froze and restarted. `last -x` confirmed the crash. It wasn’t a reboot. Confirmed reset reason was fabric flood: `sudo dmesg | grep -iE 'whea|machine check|hardware error|corrected error' ` `[2.203806] x86/amd: Previous system reset reason [0x08000800]: an uncorrected caused a data fabric sync flood event` Sniffing around, I see I’m not the only one with this problem. Absolutely ZERO bios changes have been made at this point. Had some fan issues, bought some headphones. That’s the gist of it. Trying to work. Just work. And this machine seems exceptionally unstable at this point. Does anyone know if this issue is being investigated for inclusion in 3.0.5? Any advance bios settings that can be done to prevent this from happening. Spending a lot of money on a pretty paper-weight isn’t what I had in mind. ---
**Author:** ![Angel\_Campoverde](https://avatars.discourse-cdn.com/v4/letter/a/e495f1/32.png) [@Angel\_Campoverde](https://community.frame.work/u/Angel_Campoverde)\ **Post date:** [April 27, 2026, 1:38pm UTC](https://community.frame.work/t/framework-instability-with-0x08000800-fabric-flood/81955/2 "2026-04-27T13:38:03Z")
> Sniffing around, I see I’m not the only one with this problem. Yeah, I am having problems like this too. For me it restarts once a day or sometimes 3-4 times a day. It becomes unusable a times. I also have an AMD GPU in linux, almalinux. ---
**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\ **Post date:** [April 27, 2026, 1:43pm UTC](https://community.frame.work/t/framework-instability-with-0x08000800-fabric-flood/81955/3 "2026-04-27T13:43:05Z")
Probably a good place to start is here: > > > \## Device Information > > \### System Model or SKU > \[\] Framework Laptop 16 (AMD Ryz…en™ 7040 Series) > No dGPU. > > \### BIOS VERSION > 3.0.5 > > Windows: > N/A > > Linux: > Open a terminal and run the following command > \`\`\`sudo dmidecode --string bios-version\`\`\` > 03.05 > > \### DIY Edition information > Memory: Manufacture and SKU > Kingston Fury Impact: Part Number: KF556S40-32 > 2x making 64GB total. > Storage: Manufacture and SKU > Model Number: WD\_BLACK SN850X 1000GB > Firmware Version: 620361WD > Wifi: Network controller: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter > > \### Port/Peripheral information > 1. USB-C card, nothing plugged in. > 2. Empty > 3. Empty > 4. Empty > 5. USB-C card, FW16 PSU plugged in. > 6. USB-A card, nothing plugged in. > > \### Standalone Operation > Are you running your mainboard as a standalone device. Is standalone mode enabled in the BIOS? > \- \[\] No > > \## Describe the bug > S5\_RESET\_STATUS = 0x08000800 \<- Sync Flood. > > Occasionally, about once a month I get a random crash/freeze then about 20 seconds later a reboot. > There is some details in this community thread: > https://community.frame.work/t/frwk16-random-crash-then-reboots/62411/31 > > This issue is only for "Freeze then Reboot" issues. Not "Freeze then power off". > > > \## Steps To Reproduce > Steps to reproduce the behavior: > 1. Start from a powered off laptop. > 2. Power on laptop > 4. Wait a random amount of time. Play videos, netflix, youtube etc. > 5. System freezes for about 20 seconds and then reboots itself. > > Note: I generally have the power plugged in most of the time. For all the FTR I have seen, the power was plugged in at the time. The PSU used is the FW provided one that comes with the FW16. > Note: The FW16 was not under high load. the cpu fans were not audibly running. I.e. I could not hear them above the netflix / youtube video playing. > > \## Expected behavior > It should not randomly freeze then reboot. (FTR) > > \## Screenshots > N/A > > \## Operating System (please complete the following information): > - OS/Distribution: Linux/Ubuntu > - Version: 24.04 > \- Linux Kernel Version: \`uname -a\` 6.12.7 \<- Mainline compiled kernel. > > \## Additional context > Add any other context about the problem here. The comments about AER in that thread a good place to start. ---
**Author:** ![Andrew\_Meadows](https://avatars.discourse-cdn.com/v4/letter/a/b19c9b/32.png) [@Andrew\_Meadows](https://community.frame.work/u/Andrew_Meadows)\ **Post date:** [April 27, 2026, 9:38pm UTC](https://community.frame.work/t/framework-instability-with-0x08000800-fabric-flood/81955/4 "2026-04-27T21:38:03Z")
I appreciate the tip, James, but that thread is for a version of BIOS that does not exist for the laptop AND is a different AMD architecture. So can you help me understand what you believe is the “relevant” portion of that AER issue but cause the thread also covers at least 14 months of feedback. Thanks. ---
**Author:** ![James3](https://avatars.discourse-cdn.com/v4/letter/j/b5e925/32.png) [@James3](https://community.frame.work/u/James3)\ **Post date:** [April 27, 2026, 9:42pm UTC](https://community.frame.work/t/framework-instability-with-0x08000800-fabric-flood/81955/5 "2026-04-27T21:42:42Z")
Try adding this to your kernel boot parameters: `pcie_ports=native pcie_ecrc=on` And see if you get any AER errors in the logs. If you do get some, it will tell you which pcie device might be causing the sync-flood. The AER is only one possible cause of the sync-flood, but worth a try. ---
**Author:** ![Andrew\_Meadows](https://avatars.discourse-cdn.com/v4/letter/a/b19c9b/32.png) [@Andrew\_Meadows](https://community.frame.work/u/Andrew_Meadows)\ **Post date:** [April 28, 2026, 1:17pm UTC](https://community.frame.work/t/framework-instability-with-0x08000800-fabric-flood/81955/6 "2026-04-28T13:17:14Z")
Thanks, James. I will add to those to GRUB and see where we get. Sincerely appreciate you pulling that up out of that lengthy thread.