Windows 10 sleep not working

[Idkwhattodowithmylife]

I have a windows 10 pc that when I put it into sleep mode it just turns back on after about five minutes. 
 

 

also I am going to sleep so I won’t reply for 12-16 hours

[Dukesilver27-]

Some devices probably is still active, which is considered user input by windows. Try checking all your usb devices.

[SorryBella]

58 minutes ago, Idkwhattodowithmylife said:

also I am going to sleep so I won’t reply for 12-16 hours

You couldve sent this 12-16 hours later. @Dukesilver27- would be it in this one, check your mouse and keyboard in particular, my RVM has a scratched lens that causes sensor drift every few minutes so my PC refuses to sleep a lot.

[GoodBytes]

Windows can tell you what device has awaken your system from sleep:

 

Open the command Prompt as admin, and type and execute:

powercfg /lastwake

 

Typically, the culprits are one of more:

• Wake On Magic Packet feature from Wireless and Ethernet. Disable them under the "Advanced" tab of the device properties panel under the Device Management panel.
   
• Wake On Pattern Match feature from Wireless and Ethernet. Disable them under the "Advanced" tab of the device properties panel under the Device Management panel.
   
• Wireless and Ethernet activity by the router. Disable the Wireless card or/and Ethernet from waking up the system under Device Manager. Double click on the mouse to open its property panel, and go under Power Management tab. Then uncheck "Allow this device to wake the computer."
   
• Mouse which moves a fraction of mm due to vibration or its own cable pulling or pushing the mouse. Disable your mouse from waking up the system under Device Manager. Double click on the mouse to open its property panel, and go under Power Management tab. Then uncheck "Allow this device to wake the computer."

 

 

[Idkwhattodowithmylife]

19 hours ago, GoodBytes said:

Windows can tell you what device has awaken your system from sleep:

 

Open the command Prompt as admin, and type and execute:

powercfg /lastwake

 

Typically, the culprits are one of more:

• Wake On Magic Packet feature from Wireless and Ethernet. Disable them under the "Advanced" tab of the device properties panel under the Device Management panel.
   
• Wake On Pattern Match feature from Wireless and Ethernet. Disable them under the "Advanced" tab of the device properties panel under the Device Management panel.
   
• Wireless and Ethernet activity by the router. Disable the Wireless card or/and Ethernet from waking up the system under Device Manager. Double click on the mouse to open its property panel, and go under Power Management tab. Then uncheck "Allow this device to wake the computer."
   
• Mouse which moves a fraction of mm due to vibration or its own cable pulling or pushing the mouse. Disable your mouse from waking up the system under Device Manager. Double click on the mouse to open its property panel, and go under Power Management tab. Then uncheck "Allow this device to wake the computer."

 

 

 

the report said this and i dont know what it means:

Wake History Count - 1
Wake History [0]
  Wake Source Count - 1
  Wake Source [0]
    Type: Device
    Instance Path: PCI\VEN_8086&DEV_8C31&SUBSYS_18E7103C&REV_04\3&11583659&0&A0
    Friendly Name: Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
    Description: USB xHCI Compliant Host Controller
    Manufacturer: Generic USB xHCI Host Controller
 

[GoodBytes]

32 minutes ago, Idkwhattodowithmylife said:

the report said this and i dont know what it means:

Wake History Count - 1
Wake History [0]
  Wake Source Count - 1
  Wake Source [0]
    Type: Device
    Instance Path: PCI\VEN_8086&DEV_8C31&SUBSYS_18E7103C&REV_04\3&11583659&0&A0
    Friendly Name: Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)
    Description: USB xHCI Compliant Host Controller
    Manufacturer: Generic USB xHCI Host Controller
 

It points to your Intel USB Controller.

In other words, the call to wake up the system has been done by it. Windows could not identify down the chain which device is responsible.

 

But you can investigate yourself via Device Manager to get an idea of the possible devices.

Open Device Manager, then go to View > "Device by Connection Type".

You'll see something like this:

 

You can go by name. Instance Path tell you that it is PCI device (which makes sense), so it should be under "ACPI x64-based PC" then under "Microsoft ACPI-Compliant System", then under "PCI Express Root Complex" (which contain all PCIe devices), and look under each "PCI Express Root Port" for "Intel(R) USB 3.0 eXtensible Host Controller" (which is the "Friendly Name" of the USB Controller described in the /lastwake command you executed. Then just have a look at what is connected under it, and it can be any of these devices.

 

Hope this helps.

[Idkwhattodowithmylife]

thanks! i found out that it was my case fans for some reason??