Computer is only kinda sleeping?

[quixoticduck]

Hi. My PC was working fine until recently when I had to update to Windows 10 (from W7). I'm fairly sure this is not a hardware issue because of this.

 

Now, when tell it to go to sleep the fans sound the same as when it's on, and my keyboard stays lit up, but the monitor goes blank. It seems to be half asleep for a while and then after a little while (30ish mins?) I realise the monitor has come back on. If I try to wake it up while it is still 'asleep' then it comes back on pretty much instantly, unlike it did when it was W7. Also, the Windows menu (that I clicked open previously to tell it to sleep) is open when it wakes. To me it doesn't really seem like it's going to sleep properly at all? Is this normal W10 behaviour?

 

I've tried enabling and disabling hibernation. When I go to a cmd window and type power "cfg -lastwake"  it says "Wake History Count - 0"

 

I've always been able to fix issues with Windows waking itself up in the past but this is the first time I've been confused whether it's even asleep in the first place so it's more confusing to fix.

 

I mentioned it to a tech support guy at my work (it's my home PC though) and he said Windows 10 sleep is different and not supposed to work as Windows 7's did... I just don't know.  I was thinking of doing a fresh install of Windows (not that I really want to put time aside for this) to fix this, but based on what he's said my PC isn't even working incorrectly? But it definitely *feels* like it is to me.
 

Thanks for any info.

[Bombastinator]

The deal is there’s a bunch of different sleep states (laptops) and not all hardware configurations support all of them.  Got to find out which sleep states your pieces of hardware can support.

[quixoticduck]

On 2/16/2020 at 3:47 AM, Bombastinator said:

The deal is there’s a bunch of different sleep states (laptops) and not all hardware configurations support all of them.  Got to find out which sleep states your pieces of hardware can support.

Sorry for the late reply, I thought I'd not had any responses. That sounds pretty complicated compared to Windows 7  I'm using the same hardware, sleep always worked fine until Windows 10. I've tried plugging my keyboard into another W10 computer and the keyboard lights go off when it goes to sleep and the fans run down so something's definitely wrong with mine. I've taken your advice and looked into sleep states, and typed something into a cmd window to discover:

powercfg -a
The following sleep states are available on this system:
    Standby (S3)
    Hibernate
    Hybrid Sleep
    Fast Startup

The following sleep states are not available on this system:
    Standby (S1)
        The system firmware does not support this standby state.

    Standby (S2)
        The system firmware does not support this standby state.

    Standby (S0 Low Power Idle)
        The system firmware does not support this standby state.

so I guess I have to set my computer to use the correct one--I don't understand why it wouldn't do this automatically if it knows what is supported... and why not just stick with whatever W7 used and make the others opt in for people upgrading

[Bombastinator]

It looks to my uneducated eye like microsoft is doing a lot of very quiet very undocumented fundamental updating to win10 and they might be missing stuff.  I don’t know if it was them or AMD that made my good monitor completely inoperable.

[quixoticduck]

I've found this post and it seems identical to my situation: https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware-winpc/intel-usb-30-extensible-host-controller-waking/06db1dab-0fbb-4b0e-93be-3f05e16396f1 so hopefully this will help me fix it. Although people on the thread don't seem to have had their problem solved. If I disable the driver then my mouse, keyboard, everything stops working until I restart the computer and the driver is enabled again. It's weird.