BSOD on resume from sleep

Community Support
,
1

I’m having issues with my Framework 13 AMD. I frequently put my laptop to sleep by pressing the power button, and then wake it later by pressing the power button and using the fingerprint functionality. Sometimes on resuming from sleep, it freezes for a few seconds and then has a Blue Screen of Death. This happens about once a day when I am using my laptop regularly, sometimes more. This has been going on for months. (My first record of this happening is January 27.)

Specs:
Framework Laptop 13 DIY Edition - AMD Ryzen 7 7840U
Crucial 64GB (2x32GB) DDR5 RAM 5600MHz CT2K32G56C46S5
WD_BLACK 4TB SN850X NVMe
Windows 11 Home

In mid March I reinstalled Windows 11 and the only drivers I installed were the Framework driver bundle (and Windows update). The issue has happened both before and after I reinstalled Windows.
I have run memtest overnight and that passed. I have had BSODs on BIOS 3.05, 3.07, and 3.08 beta.

I have seen stop codes of CRITICAL_PROCESS_DIED, SYSTEM_SERVICE_EXCEPTION, and 0xc000021a (Fatal System Error). The blue screens never progress past 0% and no information is collected!

What should my next steps be here to debug this?
I think I have another SSD that I could test with but I’d have to pull that out of another computer.

2

Hi,

I have been having these too. In 3 months, i have had 2 blue screens and 3 black screens of death.

Frameworks is by far the worst laptop I have ever had. (Previously used Dell and Lenovo without any issues)

What seems to have settled things down for me was to do a MemTest which didn’t result in anything, but then I re-seated the RAM module and these issues seem to have gone away.

Certainly the fan running constantly has stopped after i re-seated the ram.

Hope this helps.

3

Hi there,

Owner from a Framework 13 Ryzen 5 7640U system.

Yeah ever since this BIOS update, I’ve had the same issue. I’ll often get these issues where Windows acts like I took the SSD out for a bit, then BSOD, reboot, and it’s okay again.

Hopefully Framework release a patch?

4

I attempted to test with my alternate SSD, however that SSD was bad and I was not able to test with it.

I did install the v2.04 beta driver bundle, and I still got a BSOD. (Framework Laptop 16 AMD Ryzen™ 7040 Series Driver Bundle v2.04 2025_04_02 Release BETA)

I have reached out to Framework support.

5

I have the same issue even before the BIOS update. I couldn’t figure out why so I reinstalled microwin and got the BIOS update on the same day. The issue is less frequent but albeit still present. Sometimes when I open the laptop from sleep, it would BSOD and stay in this BSOD loop for several boots until the window recovery wizard shows up.

PXL_20250407_165955797
PXL_20250407_1659557971920×2550 256 KB

Edit: my windows install is broken, constant bsod, can’t restore, can’t repair with another installation media, rerolling updates also didnt work.

6

Update: I reinstalled Windows, and things were back to normal, but as soon as I applied the latest Windows update, it broke the computer again.

7

This is the response I got from Framework Support:

Hello David,

Welcome to Framework Support. We apologize for the delayed response. Due to a high volume of inquiries, our response times are currently longer than usual.

Would you mind answering a few questions so we can get started and decide what to do next?

  • What events led up to the issue? Were any hardware modifications, changes, or software updates made to your device before the problem occurred?
  • Before the issue arose, were you using a docking station, hub, third-party charger, or an external GPU? If so, please provide the specifications of those components.
  • Could you please confirm if you can follow our instructions​ on installing the operating system?​
  • Were you able to install the latest BIOS version and driver bundle​ and get all Windows updates, including optional updates, after installing the operating system?

For troubleshooting purposes, please set the BIOS to its default settings. To enter the BIOS, tap the F2 key before the Framework logo appears on the screen. Once in the BIOS, press the F9 key to load Optimal Defaults. Finally, press the F10 key to exit and save the changes.

If this doesn’t help, please try the following:

If no success, please open up a command prompt and type the “powercfg /a” command

If the Standby S0 network status is connected, kindly enter the following commands in the command prompt.

  • POWERCFG -SETDCVALUEINDEX SCHEME_CURRENT SUB_NONE CONNECTIVITYINSTANDBY 0
  • POWERCFG -SETACVALUEINDEX SCHEME_CURRENT SUB_NONE CONNECTIVITYINSTANDBY 0

Monitor if the issue persists or not

alt image
alt image578×411 81.9 KB

Let us know how it goes.
Thank you.

Regards,
Framework Support

8

And my response:

Framework Support,

  • What events led up to the issue? Were any hardware modifications, changes, or software updates made to your device before the problem occurred?

I have not made any hardware changes to my system. I have been running the same Memory, SSD, and WiFi card since I first set up the computer.

I regularly install Windows Updates, however I’m not aware of what specific updates were installed around the time this started.

  • Before the issue arose, were you using a docking station, hub, third-party charger, or an external GPU? If so, please provide the specifications of those components.

No, I’m not using any dock, hub, or external GPU. I regularly use the Anker USB C Nano II 65W Charger. However I have reproduced this issue without any charger or peripherals attached.

Using the WD Dashboard I have seen that the firmware version for my SSD is 624361WD, and that no updates are available.

  • Could you please confirm if you can follow our instructions on installing the operating system?

Ok yes, last night I followed the instructions and did a clean install of Windows 11.

I currently have BIOS version 3.08 installed, and I can not downgrade to 3.07. However back when I did have BIOS 3.07 installed the issue did happen on that version.

After I did the clean install of Windows last night, I installed the driver bundle you link and installed all Windows updates, including optional updates.

I ran the POWERCFG commands and verified that “powercfg /a” reports “Standby (S0 Low Power Idle) Network Disconnected”.

The only other thing I did was set up the fingerprint sensor, I did not install any other programs or drivers.

After I did all this, with nothing attached to the computer and with no programs running, I proceeded to repeatedly lock and unlock the computer with the fingerprint sensor. After about 30 unlocks, while unlocking the computer, the system froze for a few seconds at the “Hello” lock screen, it then showed the desktop for a few seconds. After that the Blue Screen of Death appeared. (See attached for image.)

I waited 30 minutes however the blue screen did not change and the percentage did not increase beyond 0%.

I just want to mention that I received my computer on January 29, 2024. I’m not sure exactly when this issue started but the first evidence I have of this issue is from January 27, 2025. So in theory this should be covered under the 1 year warranty.

-David “Ren”

PXL_20250415_145007708_2
PXL_20250415_145007708_21920×1442 99.5 KB

9

Got the following from Framework Support:

Hi David,

Thank you for the update.

Could you please check/verify/confirm/do the following:

  • For documentation purposes, please send us a screenshot capturing the Windows installation date.
  1. Press Windows + X keys, select Command Prompt(Admin)
  2. Type systeminfo and hit Enter.
  3. Scroll a bit above in the list it shows Original Windows install Date.
  • As you mentioned in your Community post, you attempted to use another SSD; however, it appears that the drive was faulty and you weren’t able to test it successfully. Have you also tried using another RAM?
  • At this point, could you please try running MemTest86 to check whether both RAM modules are functioning properly? Once you’ve completed the test, kindly share the results with us.
  • Check the SSD for errors using CHKDSK.
  • Check for corrupted system files in Windows using sfc /scannow.
  • Could you please send us the Event Viewer logs for further investigation? Below are the steps on collecting the logs.
  1. Press the Windows key + R on your keyboard to open the run window
  2. In the run dialog box, type in eventvwr and click OK
  3. In the Event Viewer window, expand the Windows Logs menu
  4. Under the Windows Logs menu, right-click on System and choose Save All Events As
  5. Save the file as eventviewer.evtx

Looking forward to your response.
Regards,
Framework Support

I reproduced the BSOD with each ram stick individually and ran memtest on both sticks of ram and each stick of ram individually. I replied back with all of their requested information.

Looking at the logs I remember that when installing the framework driver bundle the screen went black and the system remained on, but the display did not come back and I had to forcibly reboot it. After that it worked normally. (other than the BSODs)

10

Did the exact same thing when it came to SSD replacements. BSODs continued to occur.

11

From Framework Support:

Hi David,

Thank you for the thoughtful update.

Please try performing a mainboard reset and let us know if it changes the behavior. Once completed, we can proceed with escalating the case if needed.

Here are the steps:

  1. Disconnect all Expansion Cards, charger, RAM, SSD, Input Cover, and Main Battery.
  2. Press and hold the power button for 20 seconds.
  3. Leave everything disconnected for 15 minutes to allow the mainboard to fully power-drain.
  4. After 15 minutes, reconnect the Main Battery, SSD, and charger.
  5. Install a single stick of RAM in Channel 0 only (leave Channel 1 empty).
  6. Slowly press the chassis open switch 10 times — press and hold for 2 seconds each time, then release. Wait for the red LED blink on the mainboard before the next press.
  7. Press the SW1 button on the mainboard to boot the system. You may use a screwdriver to press it.
  8. This process will also reset the BIOS settings to default.
    ​

Please refer to the photo below for guidance on the switches.

alt image
alt image1139×401 644 KB

​

Thank you for your patience, and we look forward to hearing back from you.

Regards,
Framework Support

I did the reset, reproduced the BSOD, and replied.

12

Framework Support:

Hi David,

Thank you for getting back to us.

Lastly, kindly send us a clear and close picture of the entire mainboard with and without the black plastic shrouds showing all its components on the sides for inspection and documentation purposes. See the image below for reference with the black plastic shrouds removed.

alt image
alt image898×606 465 KB

We look forward to your response. Thank
Regards,
Framework Support

I sent them a photo of the mainboard.

I’m not sure if I should keep updating this thread but maybe it’s useful to someone? Anyway it sounds like Framework Support is close to some sort of resolution.

1 Like
13

Just want to post I’ve been having the same problems with my Framework 13 AMD 7040 DIY on Windows (32 GiB RAM, BIOS 3.05).

I very recently upgraded to 24H2 and have been seeing the Wake → Freeze → Crash (automatic reboot) within 30 seconds → Reboot problem.

Before the update, it seemed the graphics driver would occassionally reset (Wake → Freeze → Black screen flash with cursor → Normal operation) especially after wake which almost always recovered without a reboot.

Apart from that, the laptop would also randomly freeze after seemingly heavy GPU use (see: Random hard freezes fw13 amd7840u win11 - #493 by _ce), but that might be another issue.

14

Thanks a lot for all the details, I have exactly the same problem on my Framework 13 AMD 7040 that I purchased at the beginning of this year. Can you let us know if they reach out to you with a solution ?

15

Hi David,

Thank you for keeping in touch and providing continuous updates. We appreciate your patience and cooperation in addressing your concern about your Framework laptop.

Can we try to do a memory shuffle and see if you can gain stability after these procedures? While also doing this, could you please take photos of the memory slots, highlighting their pins for documentation and review? Try removing your sticks of RAM and then just taking one of them and installing it into Slot 0 and seeing if the issue persists. Then, try the same with the other stick of RAM. What I mean by this is that you only place one stick into Channel 0, and then try to boot, then remove that stick and move it to Channel 1, and then try to boot, then remove that stick and then try the other stick in Channel 0, etc., etc. Finally, perform the shuffle, placing both sticks in and trying to boot.

For reference: https://guides.frame.work/Guide/Memory+Replacement+Guide/94?lang=en​

DRAM 1 on channel 0
DRAM 1 on channel 1
Remove the DRAM 1
Install DRAM 2 on channel 0
DRAM 2 on channel 1
Now put back the DRAM 1 on channel 0, DRAM 2 on channel 1, and swap the RAMs (DRAM 2 on channel 0, DRAM 1 on channel 1)

Thank you for your patience. We are looking forward to your response.
Regards,
Framework Support

My response:

Framework Support,

See attached for photos of the memory pins.

As I mentioned in my email on April 18, I have already tested the laptop with only DRAM 1 on channel 0, and only DRAM 2 on channel 0. I was able to reproduce the BSOD in both configurations. I also ran memtest86 in both configurations which passed.

Please keep in mind this issue is intermittent, and it can take me 30 minutes to hours to reproduce a BSOD. The system can boot fine, the BSODs happen occasionally when resuming from sleep.

I have continued on and reproduced BSODs with only DRAM 1 on channel 1, and only DRAM 2 on channel 1.

Afterwards I put both modules in the system.

-David “Ren”

16

Hi David,

Thank you for your detailed update and for providing the photos of the memory pins. We appreciate your effort in testing different RAM configurations and sharing your observations about the intermittent BSODs on your Framework Laptop.

To troubleshoot the issue further, can you please do the following?

  1. Please try disabling the Fast Startup as it can sometimes cause issues when resuming from sleep, especially with certain hardware configurations. Disabling it may reduce the likelihood of BSODs. Here’s how:
    Go to Control Panel > Power Options > Choose what the power buttons do> Click Change settings that are currently unavailable.>Uncheck Turn on fast startup and save the changes.

  2. Please enter safe mode and see if the issue is present there. Safe mode starts Windows in a basic state, using a limited set of files and drivers. To go to Safe mode, Press Windows + R, type msconfig and press Enter> go to the Boot tab and check Safe boot> Select Minimal and click Okay> Restart your laptop and test if the issue persists. To exit Safe mode, uncheck Safe Boot and restart.

By disabling Fast Startup, we’re eliminating a potential conflict in how the system handles sleep and resume operations. Testing in Safe Mode allows us to isolate the issue by ruling out driver or software-related conflicts.

Thank you for your patience and cooperation. We are looking forward to your response.
Regards,
Framework Support

Framework Support,

  1. I have disabled Fast Startup. I don’t believe this will affect anything because I’m not shutting the computer down and the computer is not in a hibernate state when the issue happens. The BSODs happen when resuming from sleep. I can confirm the computer is only in a sleep state and not a hibernate state because it only takes a second to resume rather than the 5+ seconds it takes to resume from a hibernate. I have reproduced a BSOD when resuming from sleep using the fingerprint scanner with Fast Startup disabled.

  2. I booted into safe mode to test the issue. In safe mode, sleep is unavailable and pressing the power button causes the system to hibernate. Additionally the fingerprint scanner is unavailable and when resuming I need to enter my password. So I believe it is impossible to recreate the BSOD in safe mode because so far it has only happened on resuming from sleep when using the fingerprint scanner. Regardless I did test hibernating and waking the computer 100 times and I did not experience a BSOD.

The other thing I tested was only locking the computer (not going to sleep), and then unlocking the computer with the fingerprint scanner. So far this has not caused a BSOD.

I also tested sleeping and resuming the computer with no fingerprint or PIN set up, and so far this has not yet produced a BSOD. I think this is very unlikely to cause a BSOD because when the computer does freeze up and crash, it is always on the Windows “Hello” screen. The “Hello” screen is specifically related to using the fingerprint reader.

Both of these tests are inconclusive because the BSODs are so intermittent.

-David “Ren”

17

Hi David,

Thanks for your response. We’ve escalated your ticket for review and we will be back to you soon.

Please note that due to higher than normal contact volumes, Framework support may be slower to respond.

Your case is in queue and we appreciate your patience.

Hi David,

Thanks for your patience.

For further review of this issue, can you please send us a sleep study report of your laptop?

You may follow this guide​.
​
We are looking forward for your response. Thank you.
Regards,
Framework Support

Framework Support,

See attached for the sleep study.

I have spent a lot of time sleeping and resuming the computer in order to test this issue.

Crashes have happened at the following times:

4/15 7:50 AM PT (both DRAM)
4/16 9:45 PM PT (#1 DRAM in ch 0)
4/17 11:54 AM PT (#2 DRAM in ch 0)
4/18 10:59 AM PT (after mainboard reset, one DRAM only)
4/22 12:56 PM PT (#2 DRAM in ch 1)
4/22 6:12 PM PT (#1 DRAM in ch 1)
4/24 8:16 AM PT (both DRAM, fast startup disabled)

-David “Ren”

18

Can you submit a bug report to AMD directly.

https://www.amd.com/en/resources/support-articles/faqs/AMDBRT.html

This helps them gather all the relevant system information you are running.

19

Sure, I have gone ahead and submitted a bug report to AMD.

20

Thanks for keeping us updated. One thing id like to add since you mentioned the fingerprint login causing bsods, ever since I removed ít and used only the pin number to login, I haven’t noticed any bsod.