I’ve actually had a Windows Hardware Error that has straight up led to a sudden shut down, no BSOD, no warning, nothing.
Seems GPU related, I have no insight other than that.
1 Like
Did your mouse cursor slowly experience lags, then completely stop, and the screen turn on with no keyboard or mouse input accepted?
No, not that I noticed at least.
I was just browsing on Firefox, screen went black and instantly went to the boot screen (extremely sudden dirty shut down)
I will say this did happen after I downgraded the AMD Adrenaline Drivers (I did this unwittingly when I installed the new Framework Driver package that was released with the new 3.05 BIOS update). Maybe I need to go back to the newest drivers, IDK. Never saw a crash like this before then.
EDIT: Actually come to think of it, I didn’t have a crash like this on BIOS version 3.03b, this was on BIOS version 3.05, maybe after updating my Adrenaline drivers, I’ll keep an eye out and see if I have any more crashes.
1 Like
I actually think either AMD or MS is to blame for the Freezes and Crashes now. Because BSODs after the 2 BIOS updates are gone but now AMD GPU Driver crashes → amduw23g crash in the event log of windows on my side.
I have the same random crashes on an intel desktop system with amd rdna 3 gpu (7900 xt). These crashes don’t occur on hard load like gaming but when using Teams or GPU acceleration in a browser is used.
But it still makes the framework with amd under windows a dead system for my work environment…
2 Likes
Happened to me twice on my Ryzen 5, the last time I was using chrome, the cursor kinda started lagging and the BSOD followed after a minute or two. Everything froze during that time for a minute or two.
Are you saying it is still happening even with the beta BIOS 3.05? I am going to receive the laptop this week and I will have 30 days to try everything to potentially return it if it is buggy. I would like to know what to try to see if I am also affected by this problem.
1 Like
Not every one has that issue. My Daughter has that device and never had an issue …
For me it still happens after beta bios 3.05
Good Ars Technica article about reliability issues and firmware updates, concentrates more on the Intel-powered ones though: Framework’s software and firmware have been a mess, but it’s working on them | Ars Technica
I have a fully patched Win 11 all AMD desktop with a 5900x and 6700XT. It’s rock solid. Granted I overbuilt it with the goal of it being stable. Seasonic/Noctua/Crucial/etc. My steam deck which has a AMD SOC is also perfectly stable. Granted both of those systems are a generation behind and RDNA2. I wonder if these BSODs are an RDNA3 thing.
I am also thinking it is rdna 3 related. Because Notebooks with AMD APU and the older Vega GPU dont show any instability with Teams or Browser in our company.
Rdna 3 was plagued with a lot of driver side bugs from the beginning (e.g. high idle power consumption).
I can confirm that AMD drivers are not exactly good, but a system being completely frozen or running into BSOD is quite extreme. I used a ThinkPad T14s with AMD Ryzen 7 PRO 7840U for about 3 months with Windows 11, and while I did run into several graphics glitches probably related to PSR, I did not have a single BSOD using the official Lenovo drivers. And I was always hibernating, sometimes even for a few weeks before a proper reboot. But the ThinkPad also has a different screen panel, WLAN module (they use Qualcomm), different touchpad, memory, drive, etc., so perhaps it’s something else at play here.
yes, all the time. 4 times a week I’d say. Then BSOD, usually. Framework 13 AMD Ryzen 5 7640U. 16 Gb Crucial DDR5 5600 So-DIMM, 1 Tb WD black SN850x
I had the BSOD once back in December just days after receiving the FW13.
I updated drivers with AMD and have not had a problem since then think I was one of the lucky ones.
I did not do the recent bios update as it seemed not needed.
Then yesterday out of nowhere it froze. On battery, only using brave
browser nothing connected just a few tabs open and it froze.
I forced shut down, waited a second restarted and all was well.
Then today exactly the same thing happened.
Very strange for it to just start doing it now.
2 Likes
Matthew, I read this whole thread, and I feel like it mostly happens on battery power, after sleeping, while using the trackpad. Perhaps you did exactly that? Notice that these are all correlated, as when on battery power, you are more likely to use the trackpad and put the computer to sleep. The BIOS 3.03b included an updated EC, but the only relevant things in the changelog might be the PMF update rate, where the abbreviation PMF could stand for anything. Judging from the EC source codes, PMF has to do something with the power/thermal limits? No idea how that is related to the BSOD, but since people report that their cursor gradually stops working, I’d assume the EC partially freezes or clogs up the computer, and Windows then decides to kill itself. Would be nice to hear the official explanation from Framework 
It was on battery and I almost exclusively use the trackpad but it was not woken from sleep.
It almost never sleeps because I use it and then shut it down or very rarely I might close the lid which I have set to hibernate but that was not the case in the recent instances of it freezing.
I have updated the bios to 3.05 but left my drivers as is.
Will update if something happens…
So far, so good since updating the bios.
There is one thing I am curious about that happened before the update and has continued after it, occasionally when I start the laptop it takes quite a long time until the framework logo appears and it starts.
Other times it is crazy fast, almost instant.
Any one have any ideas what would cause that?
2 Likes
On BIOS 3.05 and the latest AMD driver pack from Framework, and I’m still BSOD’ing. I could barely get the BIOS and drivers installed because of the frequency of the blue screens. I’ve checked my RAM with memtest86+ and it seems fine. I don’t think I’ve ever crashed or locked up on Arch Linux, that I dual boot on the same drive. This is pretty frustrating.
1 Like
Oh man I feel for you. Also disturbing that on the newer BIOS version it is still happenening. I will go update my BIOS right away so that if I get another BSOD I can report that to Framework and show that the newest drivers and newest BIOS did not help.