Windows 10: 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.

:)

 

Limited Wi-Fi access

I recently downloaded the Windows 10 preview build 10130, and logged in to the computer. As soon as I logged in, I tried to connect to the internet, but it keeps on saying "limited" I tried reconnecting and disabling the adapter and turning off Fire wall,
but it didn't work... Help please? I'm using an ASUS X551 with a 2.16GHz Intel Celeton CPU N2830 with 4GB ram. Type: 64-bit

 

Lost in transition from insider to RTM

I'm in 10130 and logged with my Outlook account.

 

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

 

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".

 

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.

 

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.

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.

 

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?

 

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[/quote] 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}[/quote] 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.[/quote] 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}[/quote] 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}[/quote] After 2 hours it restarts on its own again.

 

Then you probably need to go through your power plan options, and check the settings, also under advanced settings>settings currently not available

 

Okay, I have disabled any action to be done once a critical battery level is hit (my pulled out when it's plugged in anyway), and turned off the password upon wake-up. I will check tomorrow if anything changes. Thanks!

 

You're welcome, let me know how it turns out*Smile.