Windows 10 10130 logging off on inactivity?

Page 1 of 2 12 LastLast

  1. Posts : 15
    Windows 10
       #1

    Windows 10 10130 logging off on inactivity?


    So I recently updated from 10074 to 10030(switched from slow to fast) and my routine would be to use the laptop until midnight and not turn it off when I hit the sack. When I go back to it, it's already in the lock screen, logged off. It's not in that sleep state where you login and everything was saved. This one totally logs the system off, as if you had just restarted the system.

    Any ideas? I don't have screen saver turned on, nor sleep turned on in my power settings. This has happened twice already.
      My Computer


  2. Posts : 605
    Windows 10
       #2

    Could it have blue screen while you were away and rebooted itself? Is your system stable?
      My Computer


  3. Posts : 4,131
    Windows 3.1 to Windows 11
       #3

    adjust your screen saver - lock screen comes on after screen saver
    if you want lock screen to display - do not turn off display (power setting)
    do not sleep (power settings)
      My Computer


  4. Posts : 605
    Windows 10
       #4

    Kyhi said:
    adjust your screen saver - lock screen comes on after screen saver
    if you want lock screen to display - do not turn off display (power setting)
    do not sleep (power settings)
    "It's not in that sleep state where you login and everything was saved. This one totally logs the system off, as if you had just restarted the system".
      My Computer


  5. Posts : 17,661
    Windows 10 Pro
       #5

    Check the Windows Update history. Do the dates when updates have been installed correlate with those two times you have found the computer restarted? If so, it might be an automatic restart after the updates.
      My Computer


  6. Posts : 15
    Windows 10
    Thread Starter
       #6

    fracking4oil said:
    Could it have blue screen while you were away and rebooted itself? Is your system stable?
    The only time I've had blue screens is when I max out the memory usage. ie: Playing GTA V and an application opens itself, It would BSoD. But other than that, it's okay. The system wasn't under heavy load during those 2 days.
    Kari said:
    Check the Windows Update history. Do the dates when updates have been installed correlate with those two times you have found the computer restarted? If so, it might be an automatic restart after the updates.
    I'm quite certain it wasn't an update, though I could be mistaken too. Usually when an update is done and it restarts, a notification is left afterwards stating that updates were installed. Both instances did not give me a notification after so I can't really tell if an update happened or not. Also my update history only contains Windows Defender updates, which usually don't require a restart.

    I will see if the system restarts again when I hit the sack.
      My Computer


  7. Posts : 27,162
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #7

    You can check the in Event Viewer under shutdown times what happened:
    Windows 7: Shut Down - View Details of Last Shutdown of Computer
      My Computers


  8. Posts : 15
    Windows 10
    Thread Starter
       #8

    Cliff S said:
    You can check the in Event Viewer under shutdown times what happened:
    Windows 7: Shut Down - View Details of Last Shutdown of Computer
    Thanks, I found 6 of them, 2 of which correlate with my 2 instances. The other 4 are accounted for (blue screens, improper shutdown). Is there anyway to find out what's causing them?
      My Computer


  9. Posts : 27,162
    Win11 Pro, Win10 Pro N, Win10 Home, Windows 8.1 Pro, Ubuntu
       #9

    See if there is any info in details or general tab.
    Attachment 20834
      My Computers


  10. Posts : 15
    Windows 10
    Thread Starter
       #10

    Cliff S said:
    See if there is any info in details or general tab.
    Attachment 20834
    Okay, I may have found a culprit. It appears before Kernel-General and Kernel-Boot (both of which tell me that the system had just booted up). The source is called UserPowerModeService.
    The first one restart had these:
    Code:
    Process C:\Windows\SysWOW64\powercfg.exe (process ID:4564) reset policy scheme from {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c} to {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c
    and another one after it
    Code:
    Process C:\Windows\SysWOW64\powercfg.exe (process ID:8768) reset policy scheme from {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c} to {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}
    Though the first restart didn't occur right after the those events. After 4 hours, the system seems to have booted up on its own with
    Code:
    The operating system started at system time ‎2015‎-‎06‎-‎04T19:45:41.495126700Z.
    The second restart had these before it:
    Code:
    Process C:\Windows\SysWOW64\powercfg.exe (process ID:8388) reset policy scheme from {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c} to {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}
    then
    Code:
    Process C:\Windows\SysWOW64\powercfg.exe (process ID:908) reset policy scheme from {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c} to {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}
    After 2 hours it restarts on its own again.
      My Computer


 

  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 11:16.
Find Us




Windows 10 Forums