Hey everyone,
Wondering if anyone has run into this before. My Framework 13 with the Ryzen AI 9 HX 370 will randomly freeze while I’m doing homework or just normal stuff. No input response at all (mouse/keyboard stop working), then after maybe 5–10 seconds it just shuts off completely.
Only recent change I made was swapping in a new Wi-Fi card – the Intel AX210.
Has anyone experienced anything similar? Could it be the card, a driver issue, or something else entirely? Not sure what to try next.
Appreciate any help.
I would check that your NVME and RAM are both situated well and were not bumped during your wifi card swap out.
…and memtest the hell out of modules.
I have the 13 Ryzen AI 300; my computer has also been freezing recently with no input response, but has not been shutting down. I have to hold the power button down to turn off, then back on. Wish I had a fix for you but at least wanted to share you aren’t the only one having issues. Disappointing given these are not cheap computers. I have been disappointed with support so far.
vaio
August 26, 2025, 9:44am
5
Same here. Ryzen AI 5 340 model with the latest BIOS and drivers (no modifications to stock hardware, got it as pre-built). Just freezes randomly and if you wait long enough, it reboots on its own. Very disappointing and happens multiple times a day sometimes.
James3
August 26, 2025, 10:17am
6
Is this symptom similar to:
opened 01:24PM - 02 Feb 25 UTC
bug
Laptop 16 AMD Ryzen 7040
## 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
### 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.
or
opened 04:53PM - 24 Mar 25 UTC
Laptop 16 AMD Ryzen 7040
3.05
Linux
## 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
### 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
This has only happened to me once so far.
The symptoms are:
Power plugged in.
Playing a video.
Laptop hangs, screen freezes, laptop plays audio in a short loop.
Wait 20 seconds, no automatic reboot.
Wait 60 seconds, still no reboot.
Force reboot by pressing the power button for 10 seconds.
No logs are stored, so no crash log is available.
No pstore crash log output.
No useful S5_RESET_STATUS, because I had to manually long press the power button to reset it.
EC port80 output runs over the 4096 log limit I had so no useful output captured their either.
I think that while it was in the "hang" state, it was still outputting port 80 output (keeps repeating the pattern):
Log index, Port 80 Value, Port 80 Value in ASCII or a decoded value.
"00005324","e825f022",".%.."
"00005325","e825f028",".%.("
"00005326","e825f90e",".%.."
"00005327","e825f90d",".%.."
"00005328","e825f90e",".%.."
"00005329","e825f90d",".%.."
"0000532a","e825f022",".%.."
...
Those are all values it also outputs when the laptop is running fine.
Long press of power button to power off gives:
"000054af","00001001","(S3->S0)"
## 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 and does not self-reboot.
Note: I generally have the power plugged in most of the time. For all the FTH I have seen, the power was plugged in at the time.
## Expected behavior
It should not randomly freeze then hang. (FTH)
## Screenshots
N/A
## Operating System (please complete the following information):
- OS/Distribution: Linux/Ubuntu
- Version: 24.04
- Linux Kernel Version: `uname -a` 6.13.7 <- Mainline compiled kernel.
## Additional context
Add any other context about the problem here.
If so, please add more details to those issues.
If you are able to reproduce it more often, then you might be able to help narrow down the problem a bit.
Please add detail like which Linux kernel etc, which BIOS version etc.