I’ve just started turning off my PC when I’m done with it because a mouse farting on the mouse will wake it up. Also if I do manage to get it to sleep it wakes itself up every few hours to check for updates.
This has literally been a problem since Windows ever came into being. I remember long nights of wrestling with this garbage on Jurassic versions of Windows.
Check the BIOS/firmware, there are different sleep states for Windows and Linux that can be configured. Some just refuse to sleep properly. I had a Dell laptop that would sleep and then wake up when I closed the lid and then stay awake.
This article is a wall of text spreading fake info. The sleep states work fine in windows if you have any idea how it works. And this has been the case for at least 8 years.
If you have any issue go into cmd type powercfg -requests and windows will tell you what is keeping it awake.
And doubling down if you really want your pc to wake if its off and you slap your keyboard just tweak your bios wake options and done.
Isn’t that a Lenovo model? I noticed they weren’t mentioned in the article and wondered if that was on purpose or just an oversight. My cheap IdeaPad also sleeps fine…but it also has an AMD cpu.
I dunno why I individually responded to people when I should’ve just done this.
It’s because one of your peripherals is set to wake state. You can google how to figure that out.
I turned my mouse and keyboard off from this. The mouse will wake it even if you move it. So f that. Keyboard. Some. Keyboards will wake just by having an active transmission (so manually turn it off every time - no thanks)
Now I manually have to touch my power button to wake.
My macbook wakes up whenever I get up in the middle of the night to pee. This is without me touching the mouse or the keyboard or even the desk they’re sitting on. This bothers me.
MacBook: “Oh, hey chickenlady… I see your up. Yeah, I couldn’t sleep either. Why don’t you come over here and spend some time in my soft white glow. We can just surf the web and consume for hours.”
This is an issue, but it’s not the issue. The issue is windows modern standby, trying to make users PCs always on like smartphones. Except the processors don’t support the same low power states as smartphones processors, and can be triggered by software like windows update to turn on even when disconnected from power and without functioning ventilation.
It’s because one of your peripherals is set to wake state. You can google how to figure that out.
Sometimes that’s a firmware issue. ASUS screwed up the ACPI DSDT for my 2021 G15 by leaving the sleep capabilities off of one of the NVMe slots - every time you’d tell the machine to sleep it would try, but because one of the NVMe slots wasn’t capable the machine would then immediately rewake. I had to decompile the damned thing, patch it and load my patched table as an in memory override every single boot.
This is true for S3 sleep, but that’s not the issue here. S0 sleep or Modern Standby just doesn’t put the computer to sleep. Windows manages device power states instead of the BIOS, and it usually doesn’t work out so well.
Overheating and battery drain caused by Modern Standby happen on laptops that are closed with nothing plugged in.
The “allow device to wake up computer” is already set to “off” in mouse, keyboard and other USB devices, together with any bios settings related to wake up. Yet still, at least once a week my computer is on in the morning, after i set it to Hibernate the night before. Sometimes it even power cycles straight away after i tried to turn it of. Same today, when i was was out of the house for a few hours, and it decided to magically turn itself on, run windows update and restart. I have to power it down and turn of the the power on the power-strip each night. My work laptop has the same issue, except it does not care about the power strip switch and discharges the battery overnight instead!
I actually like suspend to RAM. Makes my laptop usable after sleep a bit faster. But absolutely not on Windows because then my fans are still spinning after minutes like many have reported. But I was simply able to disable that with a registry tweak and it’s now going to regular ACPI S3 when I close the lid. Is my Framework Laptop 13 (i5-1240P) an uncommon exception?
Yes depending on the sleep state. Also some power is going to ram to keep it alive. I think for framework it’s in the realm of 5% an hour or something like that.
I usually go the hibernation route.
Desktops I sleep to ram, laptops I hibernate to the SSD.
Try to put my PC to sleep? 1 of 3 things happens: it either goes to sleep normally, it goes to sleep but wakes itself up 2 seconds later, or the PC actually just shuts down. Try to shut down my PC? 1 of 2 things happens: it either shuts down, or it restarts.
The only way for me to keep my desktop off all night is for me to switch off the power supply or unplug it, sleep, hibernate, flat out turning it off, all result in a bright ass screen waking me up at 2am
There was a video from LTT not too long ago where they contacted MS about the issue. It’s supposedly due to device manufacturers not implementing the spec properly so they ended up giving up on it.
I had the same problem with my work-issued Thinkpad. No overheating, but frequently pulling the laptop out of the bag and finding battery dead. Solution I found was to bind the power-button to “hibernate”, and just using that any time I knew I was going to be putting it away into my bag.
One problem I ran into writing my first Windows Store application like 10 years ago was that Windows Store seemed to have no interest in mobile-style security where you request permissions one-at-a-time and only the ones you need - the intended workflow was that you either requested no secure privs and let your app be “untrusted”, or you made your app “trusted” and requested all the privs. This was actively recommended by MS.
Of course, this means “wake from sleep” would be something that every app would have permission to do accidentally, even if they didn’t want to.
Yep, while my Extreme Gen 4 has a BIOS toggle, my work-issued T14 Gen 3 does not so I had to get IT to come in and enable hibernate. Prior to that it seemed like it had less battery life sleeping than awake. (ex: fully charged and confirmed that the power light is flashing before flight - few hours later it’s 100% dead.)
I managed to fiddle around with my work Dell laptop and disable that nonsense. I think it was called “modern standby”. I don’t understand why this isn’t considered a fire hazard. It was terrifying to leave my laptop in my backpack until I figured out the fix.
LTT had a great video on that. Basically Windows has a bug which sometimes prevents this sleep mode from working correctly and that nukes battery life. Microsoft has promised a fix, but apparently it’s not resolved still. In theory it should work exactly the same as Power Nap. It sometimes does, but sometimes - not so much.
P.S. Power Nap used to be buggy as well, but Apple fixed it years ago.
Thanks for the details! When Power Nap was new I didn’t have a Mac that could use it. I think it used newer Intel tech than what my Mac had at the time IIRC.
Really depends on your devices use case. That isn’t my daily driver and the trade off of not having a dead laptop is worth it for my needs of this device.
Add comment