Very similar problem for me. 2x 16gb crucial ram. Tried removing 1 stick and i haven’t got a crash since. Tried again with 2 and it crashed within 30mins.
Basically only when gaming btw. Really annoying because of dataloss and with 1 stick the performance is meh
Update from end of last week: Support was concerned that all four of my chargers/docks may have issues/incompatibilities and suggested trying the Framework charger.
I’ve firmly reminded them that the crashing occurs on battery power too (just takes a lot longer) so it’s not related to chargers or USB devices.
Hopefully they’ll finally agree to a replacement mainboard, I’m pretty sure I’ve exhausted all practical options to isolate the problem on my end.
I have seen this symptom once on a FW16 amd.
I have not been able to reproduce it a second time.
Like you. The syslog has no entries at the time of the crash.
No MCE errors after the reboot.
I was using the ethernet port card. Wifi was disabled to the time.
My support ticket has been reviewed and they’ve agreed it seems most probable that my mainboard has a fault. It’s now with the RMA team, hopefully this process doesn’t take too long so I can use my new laptop again
This might be an EC firmware bug that only happens after the EC has been on for a while.
One way to reset the EC is to power off the laptop and leave it overnight.
That is powered off, not standby,sleep or hibernated.
It should then take longer before the issue returns, if it is an EC firmware problem.
EDIT: The laptop also needs to be unplugged from the PSU. If the laptop is plugged into a PSU, it will not reset the EC.
The EC can cause these symptoms.
To find out if the EC crashed, you can use the command “ectool panicinfo”.
If it has an entry in there, the EC crashed, causing the reboot / unexpected power off.
To reset the EC.
Remove the PSU and power off the laptop.
After the Power button LED goes off, the EC will reset 40 seconds later. So, leave it off for 1-2 mins, then power on.
After the EC reset, “ectool panicinfo” should be empty, until the next crash.
So, I would be interested to see if there is any ectool panicinfo output.
An example of the output is:
ectool panicinfo
Saved panic data:
=== PROCESS EXCEPTION: 00 ====== xPSR: 61000000 ===
r0 :00000000 r1 :200c738c r2 :00000000 r3 :00000000
r4 :100a6328 r5 :200c738c r6 :00000000 r7 :00000001
r8 :00000001 r9 :100afb49 r10:100a7180 r11:00000000
r12:100ad781 sp :200c7338 lr :1008b551 pc :1009f2da
Sorry I didn’t see this in time James, typing this back on my FW 13 with the replacement mainboard fitted
I really hope the new mainboard doesn’t have the same issue. I will report back if I have trouble, noting it took 2-3 weeks before I started to get the crashing issue on my original hardware.
Edit: Also just recording that the replacement mainboard’s box had been already been opened (seal was broken). I assume it was just from extra testing before being sent out
I’ve swapped my 2x 32GB 5200MHz for my 1x 32GB 5600MHz and have not had a crash since (several hours of running)
I ruled out the expansion slots as the crashing happened with no expansion cards fitted. Any sort of charger/power connect and the constant crashing returned. To answer your question though, I’m connected to an Alogic USB-C dock and using DP Alt Mode.
Expansion bay? I don’t think I have one on the FW13?
Not specific to an app, as I’ve had the crash occur many times during my system boot up. But often more likely to crash when I execute a heavish task (e.g. open Firefox, running go test, nixos-rebuild, etc)
I’m running NixOS stable currently, kernel v6.11.2 … have tried a few different kernels and also had the crashing on Fedora v40 Live USB.
If the crashing returns I’ll try ectool console and let you know.
Have had a few days of full-time use at home and the office with no crashing on 5600 MHz RAM. Odd that the new mainboard crashes with 5200MHz but not 5600MHz; both sticks were definitely crashing my original mainboard.