System returning from sleep three seconds after entering - why?

Page 1 of 2 12 LastLast

  1. Posts : 208
    Windows 10
       #1

    System returning from sleep three seconds after entering - why?


    In the past month month, my computer, running 2004, has stopped its normal overnight behavior of entering sleep three hours after I restart it, then staying asleep until I wake in the morning, with waking from sleep on its own three seconds after entering sleep.

    You can see this below from the event viewer:

    System returning from sleep three seconds after entering - why?-image.png

    The event above it, 107 (102), has the system resuming from sleep three seconds later.

    Actually, before the event shown from 10/9, it hadn't entered sleep since 10/6, when it remained in sleep for three seconds.

    And a look at the event log - which I swear used to go back more than a year but now only goes back three weeks - shows that if the system ever entered sleep during that time - most days it did - it would wake in three seconds, and then when I touched the computer (clicked or jiggled the mouse) hours later, Event ID 1, power troubleshooter, would say the computer has returned from a low power state.

    Is this normal? I am 100% sure the computer would sleep - not sleep and wake, then return from a low-power state - at one time. How do I get the computer to actually sleep again, until I wake it hours later?
      My Computer

  2. Macboatmaster's Avatar
    Posts : 994
    10, 8.1 and 7 all Professional versions, and Linux Mint
       #2

    Please try = admin cmd prompt and type or copy and paste
    powercfg -lastwake

    that may tell us what actually woke it

    Also please try
    powercfg -waketimers
    and
    powercfg /requests

    If all of those get you no where then try this one please
    powercfg/SYSTEMSLEEPDIAGNOSTICS
    Generates a diagnostic report of system sleep transitions.
    That should respond with a report has been gerated and is stored at
    C:\Windows\system32\system-sleep-diagnostics.html.
    If you then go to windows - system 32
    open it scroll down to the s entries you should see the html file -system sleep diagnostics HTML file with the browser icon on which it will open - just click it
    When you open it - it may well give you more details of what woke the system

    In respect of the missing event items - MAYBE the upgrade to 2004
      My Computer

  3. Crizal's Avatar
    Posts : 1,565
    Windows 10 Home 64bit
       #3

    Just worth asking -- do you have any Optional Windows Updates showing up and not installed? Specifically, optional previews of cumulative or net framework updates. If you do, please see the following link starting with post #90. A number of people who haven't installed the optionals have the sleep issue and your time frame matches. If you don't have optionals that are listed and not installed, then do follow Macboatmaster's advice.

    KB4571744 Cumulative Update Windows 10 v2004 build 19041.488 - Sept. 3
      My Computer

  4. FreeBooter's Avatar
    Posts : 4,053
    Windows 10 Pro 64-bit
       #4

    Execute powercfg /lastwake command to identify the event or device that is responsible for the last waking process. Once the results are shown, check the “Instance Path:” to see where it originated from (the USB or PCI port for instance) and look under “Type:” for the nature of the cause, typically a device or a wake timer.

    Execute powercfg /devicedisablewake “Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)” command to disable wake for the device.

    If above command wont work, head into your device manager by holding down the Windows-key + R and enter “devmgmt.msc”. In the device manager, search for the the device in question, right-click it and select “Properties”. Then simply switch to the “Power Management” tab and uncheck the box for “Allow this device to wake the computer”.
      My Computer


  5. Posts : 208
    Windows 10
    Thread Starter
       #5

    Macboatmaster said:
    Please try = admin cmd prompt and type or copy and paste
    powercfg -lastwake

    that may tell us what actually woke it

    Also please try
    powercfg -waketimers
    and
    powercfg /requests

    If all of those get you no where then try this one please
    powercfg/SYSTEMSLEEPDIAGNOSTICS
    Generates a diagnostic report of system sleep transitions.
    That should respond with a report has been gerated and is stored at
    C:\Windows\system32\system-sleep-diagnostics.html.
    If you then go to windows - system 32
    open it scroll down to the s entries you should see the html file -system sleep diagnostics HTML file with the browser icon on which it will open - just click it
    When you open it - it may well give you more details of what woke the system

    In respect of the missing event items - MAYBE the upgrade to 2004
    Below is the command prompt with the results of the queries you mentioned:

    System returning from sleep three seconds after entering - why?-image.png

    So, not a lot of substance there.

    The system sleep diagnostics report also does not seem to show much. I tried to attach it but can't attach html.
      My Computer

  6. steve108's Avatar
    Posts : 12,620
    19041.1052 - 2004/20H1 Home x64
       #6
      My Computer


  7. Posts : 208
    Windows 10
    Thread Starter
       #7

    FreeBooter said:
    Execute powercfg /lastwake command to identify the event or device that is responsible for the last waking process. Once the results are shown, check the “Instance Path:” to see where it originated from (the USB or PCI port for instance) and look under “Type:” for the nature of the cause, typically a device or a wake timer.

    Execute powercfg /devicedisablewake “Intel(R) USB 3.0 eXtensible Host Controller - 1.0 (Microsoft)” command to disable wake for the device.

    If above command wont work, head into your device manager by holding down the Windows-key + R and enter “devmgmt.msc”. In the device manager, search for the the device in question, right-click it and select “Properties”. Then simply switch to the “Power Management” tab and uncheck the box for “Allow this device to wake the computer”.
    Unfortunately, there are no lastwakes shown when I run that command.

    And the Host Controller is not allowed to wake the computer:

    System returning from sleep three seconds after entering - why?-image.png
      My Computer

  8. Try3's Avatar
    Posts : 8,371
    Windows 10 Home x64 Version 21H1 Build 19043.1052
       #8

    asus2016 said:
    You can see this below from the event viewer:
    System returning from sleep three seconds after entering - why?-image.png
    The event above it, 107 (102), has the system resuming from sleep three seconds later.
    I think EventID 107 gives false information. I have just added it to my Event viewer, Custom view definition and it makes no sense at all to me.
    System returning from sleep three seconds after entering - why?-event-viewer-sleep-wake-timings-test.png
    19:02:22 - I pressed the power button to sleep the computer, and it slept until -
    19:03:11 - I pressed the power button to wake the computer.

    I suggest that you just monitor these -
    System returning from sleep three seconds after entering - why?-definition.png
    - and even EventID 131 might not be useful in your case as it just gives a running count of resumes since the last boot.

    I think you need to review your fault investigation notes [and your posts] and remove anything you had concluded from EventID 107.
    - In your posts, you can just select anything that is now not a valid statement and click on the S icon to overscore it then just add an explanatory note at the bottom about having discounted some conclusions.

    I also suggest that you go to the Asus support site, reinstall the display driver in case it is corrupt and check for any updated Bios.
    Even if you have the latest version, it might have become corrupt and there is no diagnostic test so reinstallation is the only way of addressing this potential cause of the problem.
    In Windows 7, Windows Help suggested this as one of the standard measures when there was a sleep-related problem.
    I cannot say that that the display adapter is definitely the cause of your problem, merely that it is a possibility that needs to be confirmed / eliminated.
    Using Device manager to check for driver updates is not sufficient. It just looks for version numbers-dates not driver integrity.


    Best of luck,
    Denis
      My Computer

  9. Macboatmaster's Avatar
    Posts : 994
    10, 8.1 and 7 all Professional versions, and Linux Mint
       #9

    The powerconfig request
    MoUsoCoreWorker.exe is although one may not recognise it easily - windows updates, does that show on the html and does it fit with the times
    update session orchestrator

    Please see this
    PC will not sleep - related to last Win10 update?

    You may find if you install all offered updates and before sleeping check again for updates that the problem is solved
      My Computer


  10. Posts : 208
    Windows 10
    Thread Starter
       #10

    This appears to have solved the problem. FIX: We Could Not Complete The Install Because An Update Service Was Shutting Down (similar but not exactly the same) was also helpful.

    I did two quick tests. In one I used the power > sleep from the start menu to force the computer into sleeping. In the other, I changed the sleep timeout from three hours to two minutes, so it would automatically sleep within a short timeframe.

    In both of those cases, the event viewer later indicated that the system resumed from sleep in 1-3 seconds. However, the computer fan was silent while I waited for a few minutes. Then jiggling the mouse did not wake the computer. It would remain in whatever state it was (I'll call it sleep, though this might technically be wrong), until I pressed on a keyboard key. Guessing that clicking the mouse would have revived the computer as well.

    If it conforms to this behavior in the morning, I'll mark the problem as solved.
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 21:50.
Find Us




Windows 10 Forums