I had Opus debug my laptop restarts. It pulled down windebug and pointed out the two drivers that were causing a problem.
One of them was an HDMI audio driver, which wasn't completely a surprise given I connect to a KVM and I imagine something was weird about the connection (and I don't listen to audio through my monitor anyway)
The other was the realtek/intel driver for audio as well? (updated those) Never have had a problem again. Felt pretty good. Windows laptops are pretty awful about coming out of power save, but works like a champ now.
I had a compaq laptop which worked fine until I got a dock, updated windows and after that, XP would only work properly while docked. The dock had a lot more devices, and obviously drivers were causing problems. But corporate had locked down the machine and I had to live with it until I was upgraded to a Thinkpad.
I’m all for convenience but not intentionally writing hours of work to disk before closing the lid (which you already know can be janky) is wild to me.
Thank you thank you thank you. Op and Diallo. I traced it to event 1033 but could not make head way any further. I ended up just disabling sleep entirely which did not help my electric bill when I could not shut down! Edit this worked on my desktop for further context.
I question the wisdom of "Modern Standby." When I put my laptop in sleep mode, I want it to sleep. I don't want it to be using the network, checking for updates, fetching email, etc. It can do all of those things when I wake it up.
All of the hotbagging nonsense where a laptop cooks itself in a bag seems to be caused by Windows trying to be clever and deciding there's some really important stuff it needs to do, so it wakes up the machine, does a bunch of stuff, and doesn't get back to sleep.
Windows, you're not as clever as you think you are. None of this work is urgent. Just stay asleep until I wake you up. Seriously, just don't.
The ultimate solution would be a fixed MT7922 driver, but try as I might, I haven't been able to find one online.
Perhaps it's time to ask an LLM of your choice to make one.
The marketing tries to tell us that we're on the brink of AGI, but still in 2026 putting a random laptop reliably to sleep remains an open problem.
I had Opus debug my laptop restarts. It pulled down windebug and pointed out the two drivers that were causing a problem.
One of them was an HDMI audio driver, which wasn't completely a surprise given I connect to a KVM and I imagine something was weird about the connection (and I don't listen to audio through my monitor anyway)
The other was the realtek/intel driver for audio as well? (updated those) Never have had a problem again. Felt pretty good. Windows laptops are pretty awful about coming out of power save, but works like a champ now.
I had a compaq laptop which worked fine until I got a dock, updated windows and after that, XP would only work properly while docked. The dock had a lot more devices, and obviously drivers were causing problems. But corporate had locked down the machine and I had to live with it until I was upgraded to a Thinkpad.
I’m all for convenience but not intentionally writing hours of work to disk before closing the lid (which you already know can be janky) is wild to me.
I think this is more about workspace state, not saving working data to disk.
Thank you thank you thank you. Op and Diallo. I traced it to event 1033 but could not make head way any further. I ended up just disabling sleep entirely which did not help my electric bill when I could not shut down! Edit this worked on my desktop for further context.
I swear most laptop sleep problems relate to wifi powersaving :(
(I also thought S0ix was supposed to fix all of this ...)
Fucking hell!
40+ years of laptop computing and sleep is still a problem !!!
I question the wisdom of "Modern Standby." When I put my laptop in sleep mode, I want it to sleep. I don't want it to be using the network, checking for updates, fetching email, etc. It can do all of those things when I wake it up.
All of the hotbagging nonsense where a laptop cooks itself in a bag seems to be caused by Windows trying to be clever and deciding there's some really important stuff it needs to do, so it wakes up the machine, does a bunch of stuff, and doesn't get back to sleep.
Windows, you're not as clever as you think you are. None of this work is urgent. Just stay asleep until I wake you up. Seriously, just don't.