- Joined
- Mar 16, 2017
- Messages
- 2,098 (0.75/day)
- Location
- Tanagra
| System Name | Budget Box |
|---|---|
| Processor | Xeon E5-2667v2 |
| Motherboard | ASUS P9X79 Pro |
| Cooling | Some cheap tower cooler, I dunno |
| Memory | 32GB 1866-DDR3 ECC |
| Video Card(s) | XFX RX 5600XT |
| Storage | WD NVME 1GB |
| Display(s) | ASUS Pro Art 27" |
| Case | Antec P7 Neo |
lol Trucks are users too!Only 3+ decades? Well I won't hold your obvious youth and lack of experience against you!This is ESPECIALLY so since I pretty much have to totally agree with you. If there's been one general category of persistent problems, almost since the OS first took over the duty from HW, it is with sleep/standby/hibernate modes.
That said, the vast majority of causes for Windows failing to go to sleep (or waking up for no apparent reason), is due to some connected hardware device - most commonly via USB, but sometimes by the NIC.
When the problem is constant and caused by a corrupt driver, becoming proficient with the powercfg command to determine which driver is a must. But sadly, too often the problem is intermittent. This (I believe) is not due to a corrupt driver, but rather a corrupt setting that, for whatever reason, suddenly becomes "stuck". And the only way to resolve that is by a "cold" boot. By "cold", I mean to shutdown the computer AND unplug from the wall (or flip the PSU's master power switch) for about 15 seconds. This removes all traces of the ATX Form Factor's required +5Vsb "standby" voltage from all points on the motherboard, allowing the "cold" boot to reset/correct the offending setting. So after 15 seconds, restore power and boot, cross fingers and toes and hopefully the computer will sleep as expected, until that setting becomes corrupt again.
BTW, at a former place of work, we used to be plagued by computers constantly waking up for no apparent reason. Then one day a coworker was looking out the window and noticed one of those huge double dump gravel trucks go by and suddenly several of our computers woke up. It was the subtle vibrations shaking the building and computer desks wiggling the mice just enough to wake up the computers. Then we noticed the occasional heavy foot-fall, a passing train, or an EC-135 launching in our direction would wake them too. So we got into the habit of flipping the mice on their backs when done using the computer. It worked.
Another pro for Linux, at least on my install, is that mouse movement and clicks don’t wake the machine. Only a keystroke will wake it, which is much harder to trigger accidentally (unless you have mischievous cats). macOS behaves the same way, though a mouse click will wake, too. Windows consistently struggles with power management, Linux and macOS handle them really well.
