All 3 sound like symptoms of some sort of firmware problem. If you’re able to reproduce you should report it to framework.
I’m having the same problem for my Framework 13" that was delivered in Sep 2024.
Framework Laptop 13 DIY Edition (AMD Ryzen™ 7040 Series)
System: AMD Ryzen™ 5 7640U - 2.8k Display
Depending on the apps I use, I’m having daily complete lockups on Windows 11 with latest BIOS and drivers when using some graphics intensive apps including Microsoft Powerpoint, Adobe Photoshop. The lockups mostly if not always seem to happen when doing sudden intensive tasks but not during sustained heavy tasks, specifically saving a (large) file or copy pasting (large pictures) seem to trigger a lockup.
System freezes completely without any chance to recover, display stays on. After a minute or so, the system will automatically reboot. The system event log doesn’t contain any entries and there is no BSOD to be seen.
I’ve already removed the HDMI extension and disabled the PCIe idle setting in the BIOS to make sure this is not related to either of those.
A post was split to a new topic: Touchpad gestures
I’ve been having random power cuts and restarts the past 2 months and they’re super random. However I’ve narrowed it down to iGPU memory usage mostly. And all issues started appearing after FW replaced my 7840U mainboard under warranty. My old one was manufactured in 2023, my new one - in 2024.
I’m using the Crucial 96GB DDR5 kit at 5600MHz and it worked flawlessly with the old motherboard.
I’ve also tested multiple OS - Windows 11 Pro, ArchLinux, Fedora 40 and 41 (Gnome and KDE), Gentoo, NixOS. All of them experience a complete power off and reboot of the machine randomly. When I set the iGPU memory to Gaming in the BIOS, the crashes happen more frequently.
And now with the most recent Linux kernel 6.12 the issue also happens super frequently. I ran a few memtests (except the super slow ones) and everything was fine. I also reseated the RAM a couple of times - still the same thing.
And now that I’m reading about everyone else’s issues, I’m both happy and sad I’m not the only one.
I really hope a firmware or software update can fix the issue and not another mainboard replacement.
Update:
The second module had dirty connectors (idk how that happened). After cleaning it, the laptop booted without issues. I’ll now test it for a few days and see if it crashes. If not, I’ll test with both modules again and hope everything will be fine.
I can’t edit my comment so I’m replying instead.
After digging deeper and testing the RAM again, it might be because of a faulty module. I started testing the modules on by one in each slot. The first module worked perfect in both slots. Then, after inserting the second module in the first slot, the system doesn’t boot and I get a POST code - 11000101 → 0xC5 → Restore system configuration stage 1
I have no idea what it actually means, but the system won’t boot even after more than 30 minutes left in this state.
I’ve contacted Crucial and will be waiting for a response next week. So most probably not Framework’s fault.
The laptop is also stable with the single working module - I haven’t had any crashes or freezes.
Last update:
It seems the issue only occurs when I have both memory sticks inserted. If only one stick is slotted in any of the slots the system is stable, but I get way less FPS in games. When both sticks are present, I get decent FPS, but the laptop shuts down in less than 5 minutes from launching the game.
I created a support ticket a month or more ago and still haven’t received a response so I might create a new one.
But both sticks run flawlessly on their own, MemTest86+ passes with flying colors. Even both sticks pass all MemTest86+ tests, but fail in real-world scenarios.
I’m now certain it’s a mainboard issue.
Still seeing occassional crashes again, though due to different daily use of my laptop in the last month (mostly coding, compiling, I’m guessing not so heavy GPU stuff) its been about a month since the last crash.
I’ve noticed that my last crash in Nov as well as the last 2 crashes actually created a minidump indicating a DPC_WATCHDOG_VIOLATION. That doesn’t tell much but it does indicate a hanging driver for whatever reason.
The last 2 minidump seemed to involve winhvr.sys (WSL was running both times) but the Nov dump involved mmcss.sys. I’ve been adviced to “RAM shuffle” my RAM modules, which I’ll try in any case.
For what its worth: memory configuration is “Kingston DDR5 SODIMM FURY Impact 2x16GB 5600”, SSD is “WD Black SN770 1TB M.2 SSD”, driver is the latest pack from Framework (Unified AMD Ryzen 7040 Series Driver Bundle 2024-10-02), BIOS is 3.05 and Link State Power Management in advanced power options is set to Off.