S0 sleep should never have invented, what a mess created by Microsoft and Intel!
If this is causing the unexpected shutdowns, I’m not sure, I tend to think not.
This is mainly causing power drains and incidental (yes also unexpected) shutdowns, not structural (what I expect). In my case the laptop is always connected to power, in house use only, and the symptoms described by Linus, are happening when switching from power to battery. But this may cover some of the experienced symptoms from others, again, what a mess created by MS en Intel. Framework does support the S3 mode, good to know.
2 Likes
Hi All - I just received my new Gen 12 Framework laptop this week, installed Windows 11 and promptly started running into this issue. I’ve opened a support case with Framework to see where the troubleshooting goes. Wish me luck!
4 Likes
Hi and welcome to the forum.
If you are using Windows sleep will automatically go to hibernate when the battery goes low, i.e. switch off.
Did you read the above 91 posts 
etc.
EDIT
Your profile says you have been reading for 7 minutes so maybe you saw soemthing relevant ??
Good luck! Hoping for the best 
1 Like
Ok, here might be a hacky way of getting around this issue for now.
Also, I think this has been hashed enough, but this is NOT a hibernate issue. This also shouldn’t be a power drain issue, since multiple people (myself included) have seen this issue when the laptop has been plugged in. The symptom can be found by looking in Event Viewer, and there should be an event that looks like “The previous system shutdown at on was unexpected.” Like so:
If you go back in the event viewer to the specified time and date, you’ll find some event that’s like “Process C:\Windows\System32\WUDFHost.exe (process ID:1424) reset policy scheme from {381b4222-f694-41f0-9685-ff5bb260df2e} to {381b4222-f694-41f0-9685-ff5bb260df2e}”
And I’ll get getting hundreds of these events.
So, what I did was go into Task Manager, add the PID column to the tasks to figure out what process is causing that event, and manually killed the process. This pops up an event that shows that the driver’s angry, since it got killed:
Event text: “The device Intel(R) Innovation Platform Framework Processor Participant (location PCI bus 0, device 4, function 0) is offline due to a user-mode driver crash. Windows will attempt to restart the device 5 more times. Please contact the device manufacturer for more information about this problem.”
My emphasis in bold. If you kill the process, it’ll just automatically restart itself. BUT, if you notice the name and PCI bus ID, you can go into Device Manager, find it under “System Devices”, and manually uninstall the device/remove the driver.
I did that, and now I have a yellow-bang’d device (see below), but I haven’t had issues the past two nights.
Probably a bit heavy-handed, and not sure what the long-term implications are for performance/stability/etc, but if you’re desperate, this might work for you. Just make sure you do a system restore point/backups/all the general precautions with messing with stuff you’re unsure of. Hopefully this also provides a hint to what’s been causing us grief as well.
3 Likes
I’ve disabled Hybrid Modern Sleep (S0 Sleep), since S3 sleep is supported by the 12th Gen Framework laptop. This will increase the amount of time it takes to wake up the laptop from sleep, but at least I won’t lose all my work and open programs. I know this is not ideal, and I’m really hoping Framework comes up with a solution to this issue so we can enjoy the instant wake up from sleep.
This requires editing the registry as noted here, then reboot the laptop: High Battery Drain During Suspend (Windows edition) - #175 by Xiaoling_He
2 Likes
My understanding is that this is a fix that will need to come from Microsoft, not the PC manufacturers.
4 Likes
I was also seeing this, but figured since it was info level logging I figured this was just Windows being Windows.
Glad to read that both @jeffwmo and @freddy were able to come up with solutions. Good troubleshooting both of you!
It’s odd to me that this is an issue at all, since the problem is coming from an Intel device which should be fully supported by MicroSoft. But perhaps there is some configuration Windows isn’t used to seeing.
I wonder if other people experiencing this issue would see the same event text following Jeff’s fix as he did?
I have been struggling with this same issue. After seeing the recent LTT video about modern standby and reading through this tread, I am first trying the registry edit like @freddy shared recently. I have just done the change, so I’ll report back in a day or two if it seems to work or not for me.
3 Likes
Yeah, I’m hitting shutdowns during sleep again, so while my post may have been interesting, it doesn’t ultimately solve this behavior it looks like. Probably best to stick with the S3 workaround until the modern standby mode behaves better.
2 Likes
I am having this problem too with a relatively new 12th gen and it happens with or without power and sometimes even when I just choose restart from within windows. It closes out windows, turns off screen - and then somewhere in there the screen never turns back on even though the power button shows on. It is not consistent but it is common enough that it is super frustrating to the family member who is using the laptop as their main device.
I have no good info to add to this thread, but thank you all for hopefully helping come up with the push or info for a resolution.
1 Like
It’s only been about 1.5 days since my last post, but so far the change to S3 sleep is working perfectly (well, the first time it hibernated, but that was because of a power management setting that I could easily change).
I know S3 sleep may be slightly slower than modern standby, but it sleeps without any of the issues we’ve all experienced, so I definitely recommend it.
2 Likes
Two days ago, I replaced the mainboard (no small task and it truly is a DIY laptop, briljantly build) en I reverted all settings back to S0 deep sleep.
It has survived two nights now, so it looks promising, and may look like hardware related on some mainboards (it looks like my old mainboard reacts differently compared to the new one).
Disabling S0 using the regkey mentioned in LTT and above, also made a stable system.
I’ll keep posting my experiences.
2 Likes
Love to hear it!
1 Like
I’ve completed my troubleshooting with Framework Support. Based on all the testing over the last week, they have concluded my laptop is experiencing a software issue. The issue happens when a power cable is connected to the laptop, regardless of expansion cards being installed or not. For the time being, I’m sticking with S3 sleep. Here was their last bit of feedback after asking if this was being looked at with an eye towards finding a resolution:
“We are currently aware of these issues with the Intel CPU and are currently working to improve or fix them with our configurations. We may have to announce any fixes in the future but are unable to provide an estimated time frame as this is not an internal hardware issue by Framework. This is a known issue with the Intel CPU in relation to power management in Windows.”
5 Likes
Good to hear they are aware and its software related. Hopefully with the next bios update we get a fix.
And three unexpected shutdowns later, I can confirm it didn’t help replacing the mainboard. I got a bonus that FN Lock is no longer possible to activate (really annoying: help!), and I’m now switching back to hibernate and disabling S0.
3 Likes
Adding a reply for emphasis, since this fixed the issue for me as well. No need to disable S0 sleep.
My issue went from 100% daily power loss to zero issues now for well over a month with the steps I listed out above.
2 Likes