This is my config:
Intel® Core™ i5-1135G7
16GB (1 x 16GB) DDR4-3200
500GB - WD_BLACK™ SN850 NVMe™
At various times the laptop just bluescreens with this message:
Default Boot Drive Missing or Boot Failed.
Insert Recovery Media and Hit any key
Then Select “Boot Manager’ to choose a new Boot Device or to Boot Recovery Media”
This happens both when the laptop is opened on my desk and when the lid is closed. To recover all I do is hit the power button and it just powers back on.
Does this happen when your laptop is already booted and you just leave it powerd on for some time. Or if you close the lid or go into standby? Looking at this forum (and discord) there seem to be a lot of s0ix standby related issues that can manifest in ways like these. It might be something else of course too
It happens when the laptop is already booted and goes into sleep mode.
Microsoft is currently pushing a new standby mode called s0ix or “modern standby”. This new standby mode requires many components in your laptop to support certain standby modes and wake up calls. As an example a lot of sata ssds don’t support those standards which is most likely the reason why framework said that sata ssds arn’t supported (they might work if they support DevSlp and HIPM). Even with compatible devices there can still be a few issues from time to time. Typical symptoms are:
- Screen goes black but power consumption does not go down
- System goes to sleep but will not be able to wake up anymore (require hard shutdown)
- System wakes up successfully but your SATA drive might not be accessible
- System might randomly wake up during sleep or crash, pushing up power consumption even higher
There are lots of posts in this forum with similar issues. Your problems sounds kinda similar to these with you drive loosing connection after initiating standby. A few things that can solve this is to make sure all of your drivers are up to date and update your bios to the newest version.
If the problem still continues it is possible to replace s0ix or “modern standby” with the old “s3” standby mode. With a quick google search you can find guides on how to do this. I know on windows you can do this by changing a few registry settings. I can only recommend this as an temporary fix though since the old “s3” standby mode might cause issues with drivers that are optimised for the s0ix standby mode. If you do this you should make an backup just in case. Maybe i’m also wrong and the issue lies somewhere else. The framework team might also know better ways to fix this at this point
Thanks for the thorough answer. I looked up your advice and think you are correct about the problem. At this point I’m not going to modify the registry and see what the support team says. I send them a trouble ticket earlier today.
I was having this same issue, and @_Asic was very helpful in pointing me in the right direction, and the answer ended up being very simple. For anyone else who comes across this issue, the article I used to fix this is:
It’s a simple fix, don’t be scared of using the registry editor.
You can use the command
powercfg /a in the command prompt to see if s3 is supported, at the top it will say:
The following sleep states are available on this system:
Along with other options. If that’s missing, edit your registry like so:
Enter the 32-bit DWORD value
PlatformAoAcOverride and set it to
Hope this helps others, thanks Asic for getting me to the answer; and as he said, backup your system before doing this just in case if you’ve got files you don’t want to lose.
I’ve actually had Framework tech support help me fix this problem. The drivers for the SSD needed to be updated and once that happened everything worked correctly. It seems that Western Digital is having problems with some of their drives and FW had me send them the serial number of my drive.
a little late to comment here maybe. I had the same problem when I first got my framework and it did crash when it was sleeping time to time. I also had to update ssd for myself, but I used a Crucial p5 instead of a wd.