Random hard freezes fw13 amd7840u win11

Hi guys,

like others, I haven’t had a single freeze since the update !

About the battery life I feel it has shortened a bit but I don’t have concrete proof about it…
Moreover, if I leave my fw and it goes on standby, I have to restart it because the screen won’t wake up. Finally, since the update, I can’t change the lightning (from the settings and the buttons).

Compared to the freezes, these issues are nothing but if someone knows how to fix those problems I’d be so grateful.

Thanks in advance !

Still got a BSOD after installing the Beta. So, the situation may be improved, but not fully solved. Or it is another problem for me. “Unfortunately”, it happens not very often to me, so it is very difficult to pin it down e.g. to extension cards. RAM is original and “just” 8GB, so nothing special here …

I think there are indeed multiple root causes out there for the BSODs. For example, if I set the PCIe Power Savings for Link Management on battery to Maximum (which is the default Windows setting), I get BSODs pretty regularly…

I created a user account for this forum so that I can chime in and say, that I am affected too. The number of users affected and not posting online is probably quite high.

I did the usual

  • Installed the Framework chipset driver package
  • Installed all windows updates
  • Installed latest AMD GPU driver
  • Ran memtest for multiple nights without issue

Still seeing BSOD.

Next I looked at the minidumped and with google’s help I was able to link the crashes to the AMD Audio driver. I disabled the AMD audio device in the Windows 11 device manager, and sure enough, the BSOD were gone for 3 months now. It’s not very nice as a solution, but I was happy to get it under control somehow.

Since the BSODs are under control for me right now, I’ll wait until the BIOS update leaves the beta stage and then give it a try: Framework 13 AMD Ryzen 7040 BIOS 3.03b BETA - #32 by TheWiFiNerds

I have not had a freeze in the 12 days since I’ve installed the update. That being said, I’ve had to reboot for updates and things so it hasn’t been running for 12 days straight. But I’m personally cautiously optimistic at this point.

Hello,
I’m encountering frequent system freezes, typically twice a month.
How can I resolve this issue? I’m not exerting high CPU usage or running multiple software applications simultaneously.

What BIOS and drivers are you using?

Bios: 3.03
Driver: 10/24/23

Is it a BSOD or just a driver-related freeze? If it’s the first one, you can try the 3.03b BIOS. If it’s a second one, that’s more complicated but you could try using the AMD-provided drivers and seeing how that goes.

It occurs when the display shows a normal screen but fails to recognize any keyboard or mouse inputs. Could you advise me on which AMD driver I should use?

You can grab the installer from here: https://www.amd.com/en/support/apu/amd-ryzen-processors/amd-ryzen-7-processors-radeon-graphics/amd-ryzen-7-7840u. It’ll automatically grab the right drivers.

1 Like

Just sharing my experience here, FW13 AMD 7840U. I was running Debian 12, had a lot of freezes and crashes. Installed 3.03b which made the system a lot more stable. Today I had 3 freezes within 15 minutes while using my Thunderbolt/USB-C dock. Last crash actually corrupted my hard drive, presumably because I was using LUKS full disk encryption. My whole installation is corrupted now.

I’ll try installing Windows 10, see if that makes it more stable. But this is really bad and I hope this will be fixed very soon.

Did you happen to have secure boot enabled w/ Debian? Just curious. I had a lot of issues w/ Debian & Ubuntu, various versions and kernels; and switched to Arch and the beta firmware and my issues seemed to all melt away. Main difference I could see is disabling secure boot (which I plan to re-enable), and enabling the AMD microcode patches after installing Arch.

Secure boot works nice, but you have to register the key + password.
using KDE Neon (Ubuntu LTS 22.04.x + latest plasma) and have no issues.

welcome to the club for me it corrupted the whole bios of the motherboard

Following up, received a replacement device via support and have been using it for a bit over a week under workloads that have previously triggered the BSODs. It is running

  • Windows 11 Pro latest available (non-insider)
  • Framework drivers
  • Bios 3.03 (I have not put 3.03b on this device yet since the device is stable)

Device is 7840U, 32gb of ram (framework) and 1tb drive.

I would suggest if you are seeing this issue at all, that you should be working with support for help.

I’ve noticed the same for touchpad use, though whether the laptop is plugged in or not doesn’t seem to affect it.

My Framework always freezes for ~30 seconds prior to the BSOD and it’s always while I’m scrolling on the touchpad. This issue has never occurred while using an external Bluetooth mouse.

Having freezes as well on Windows 11 and an AMD7840U. Weirdly enough, it started happening about two or three weeks ago. I never encountered issues before.

The trackpad freezes, then the entire computer freezes, and then I either restart it manually or get a watchdog violation BSOD.

A little follow up from my side too: I used to have the same freezes as most people in this thread, installed the BIOS beta as soon as it was released and haven’t had any since then!

However, I also notice that every now and then the mouse halts for a second when using the trackpad (as if there still is an issue with it, just that it does not cause a BSOD anymore). The reliability history has improved a lot (with much less critical events) but I keep getting Windows hardware errors and indications that Microsoft WWA Host has stopped working. I was wondering, is anyone else observing the same?

1 Like

Personally, I have not experienced a BSOD since the beta update. That being said, the trackpad does go a little crazy (usually once a day).

I also encountered 2 hardware errors too. The first one: LKD_0x141_Tdr:6_IMAGE_amdkmdag.sys-PF:1-SCH seems to be related to graphics drivers that couldn’t access a virtual memory allocation. The second one: LKD_0x1D4_COMMAND_TIMEOUT_0x5_UcmUcsiAcpiClient_UcmUcsiCx!UcmUcsiCx::GenerateUcsiFailureDump seems to be related to some USB-C controller stuff.
Disclaimer: The assumptions about the causes are from an LLM.