Hey Matt, thanks for the quick response 
Yep, sometime around 6.13.7, one of those upgrades seemed to solve my Triple Fault issue. I have not had this problem since. I am currently running linux 6.14.10-arch1-1, core/linux-firmware 20250508.788aadc8-2, and core/amd-ucode 20250508.788aadc8-2.
However, I got tagged in this post the other day. I asked if they could check the S5_RESET_STATUS so we can be sure if itâs FTR or Triple Fault but they havenât replied. I am guessing it is Sync Flood because of the version of Linux (6.14.9) they are running. I havenât seen anybody overtly reporting the Triple Fault 0x00800800 yet, but the Ryzen AI 300 series boards are confirmed to be experiencing the Sync Flood 0x08000800.
I appreciate the attention on this. This Sync Flood issue is particularly nasty because it seems to affect any and all boards on any and all distros/kernels. This thread, as well as the others replied in, and the GitHub issues all have these reports. It seems like itâs hardware/firmware related. I fear that if it is not root caused by Framework engineering, whatever AMD board is released next will also have this issue. Iâd suggest this thread be read and watched as the main Sync Flood thread.
Thereâs a lot of good info from people debugging here, as mentioned by sydney in the other thread: FW16 Freeze then Reboot (FTR) S5_RESET_STATUS = 0x08000800 <- Sync Flood. ¡ Issue #41 ¡ FrameworkComputer/SoftwareFirmwareIssueTracker ¡ GitHub
This thread is about the Triple Fault, which seems to be resolved, but I wonât be certain until I get to 6.15 and use it for a few weeks.