Windows closes all my programs overnight when screen is locked

This is my first post here, I have searched and searched all over Google and have not been able to find one other case of someone having this issue.
Even though I have a laptop it tends to be my desktop and stays at home 99% of the time plugged in and running. It is set to never sleep and never hibernate while plugged in, to do nothing whenever the screen is closed, and I have Windows Update automatic restart blocked. But whenever I have programs open such as web pages I'm not done looking at, stuff downloading, something in the house still using files off its hard drive over the network, an unsaved text file I used as a note pad for the day, etc. and I lock it and come back more than say... four hours later (typically this happens overnight) to log back in I find that I'm actually logging in fresh, everything is lost. Yet I look in the task manager and the up time is well over a week, so it didn't restart, I'm not sure if I'm even being logged off but everything has to start back up when I log back in like I am. The WiFi searches and reconnects, the battery symbol takes a few seconds to (I guess) connect to the battery info, Avast and some other task bar apps load back too, desktop icons take the usual few seconds to appear and load, but nothing I was using before comes back. Compared to when I usually unlock it and it's just like uncovering a picture, all is there instantly the way I left it.
Though it wasn't for this issue I even reinstalled the OS a few weeks ago and it didn't change it and this is the only computer I've had that has this problem. My old Asus netbook that was treated the same way for over a year never did this, and my girlfriends MacBook with Windows installed that is almost always running never does this. Can anyone at least give me some pointers of where to look in the event viewer? I've been aware of its existence but have never needed to use it.

nommy the first said:

Hello Herqulees and welcome to the SevenForums,

Do you have a screensaver enabled? If so, please check the following;

1. Click on the .
2. In the Search programs and files box, type "Personalization", and click on the first entry under Control Panel.
3. A new window will pop-up. In the right bottom corner, click on Screen Saver, another window will pop-up.
4. Is the box next to On resume, display logon screen checked?
   If so, please uncheck the box and restart your computer afterwards.

Also, does this problem occur on other accounts?
If not, please try to recreate the problem on another account. If it still doesn't occur please report back, as your user profile might be corrupted and we will need to fix it.


Good luck and keep us posted,
Nommy

Nope I don't use screen savers, I think they're a waste of processing power. I'm the only user of the computer so only one account, unless theirs a hidden admin account like Windows XP, never used safe mode so dunno if that's still there. I would prefer to try other ideas first as I don't want to make another user account and have to kinda start over with setting up programs like a new computer again just to delete it a few days later and who knows how much junk that would leave in the registry, plus I don't think anything is corrupt since it's done this before and after I reinstalled Windows. Seeing as I have always had the OEM Windows 7 of this laptop installed, from when I bought it to what I reinstalled, and this is the only Windows 7 computer of mine to do this, and this laptop has a lot of proprietary power saving features that Windows does not control, I am suspecting it is something Acer changed in the OS or something they have installed that is doing this.
Is why I was wondering where in the Event Viewer I could see account log ins and outs and possibly what requested the log in/out?

From 2013-07-27 at about 9pm to 07-28 at about 9am the computer was left unattended and locked (Windows Key + L), it was left in a rush so I can't remember what all was running but I know I had some stuff open, but when I returned and unlocked it everything was gone. Looking through the event viewer for suspicious stuff here are a few things I've found from newest to oldest;

Code:

--------------------------------------------------

Log Name:      Application
Source:        Microsoft-Windows-ApplicationExperienceInfrastructure
Date:          7/28/2013 8:51:29 AM
Event ID:      1
Task Category: None
Level:         Warning
Keywords:      
User:          Michael-Laptop\Michael ********
Computer:      Michael-Laptop
Description:
The application (Acer Updater, from vendor Acer Incorporated) has the following problem: Acer Updater has a known compatibility issue with this version of Windows. For an update that is compatible with this version of Windows, contact Acer Incorporated.

--------------------------------------------------

Log Name:      Application
Source:        Microsoft-Windows-ApplicationExperienceInfrastructure
Date:          7/28/2013 8:50:28 AM
Event ID:      1
Task Category: None
Level:         Warning
Keywords:      
User:          Michael-Laptop\Michael ********
Computer:      Michael-Laptop
Description:
The application (Acer Updater, from vendor Acer Incorporated) has the following problem: Acer Updater has a known compatibility issue with this version of Windows. For an update that is compatible with this version of Windows, contact Acer Incorporated.

--------------------------------------------------

Log Name:      Application
Source:        Microsoft-Windows-Winlogon
Date:          7/28/2013 8:50:25 AM
Event ID:      6000
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Michael-Laptop
Description:
The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.

--------------------------------------------------

Log Name:      Application
Source:        gupdate
Date:          7/28/2013 8:14:01 AM
Event ID:      0
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Michael-Laptop
Description:
The description for Event ID 0 from source gupdate cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Service stopped

--------------------------------------------------

Log Name:      Application
Source:        gupdate
Date:          7/28/2013 8:14:00 AM
Event ID:      0
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Michael-Laptop
Description:
The description for Event ID 0 from source gupdate cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Service started

--------------------------------------------------

Log Name:      Application
Source:        Microsoft-Windows-Winlogon
Date:          7/28/2013 3:27:07 AM
Event ID:      6000
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Michael-Laptop
Description:
The winlogon notification subscriber <SessionEnv> was unavailable to handle a notification event.

--------------------------------------------------

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          7/28/2013 3:27:07 AM
Event ID:      4647
Task Category: Logoff
Level:         Information
Keywords:      Audit Success
User:          N/A
Computer:      Michael-Laptop
Description:
User initiated logoff:

Subject:
	Security ID:		Michael-Laptop\Michael ********
	Account Name:		Michael ********
	Account Domain:		Michael-Laptop
	Logon ID:		0x73e9b49

This event is generated when a logoff is initiated. No further user-initiated activity can occur. This event can be interpreted as a logoff event.

--------------------------------------------------

Log Name:      Application
Source:        Desktop Window Manager
Date:          7/28/2013 3:27:06 AM
Event ID:      9009
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Michael-Laptop
Description:
The Desktop Window Manager has exited with code (0x40010004)

--------------------------------------------------

Log Name:      Application
Source:        gupdate
Date:          7/28/2013 3:14:01 AM
Event ID:      0
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Michael-Laptop
Description:
The description for Event ID 0 from source gupdate cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Service stopped

--------------------------------------------------

Log Name:      Application
Source:        gupdate
Date:          7/28/2013 3:14:00 AM
Event ID:      0
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Michael-Laptop
Description:
The description for Event ID 0 from source gupdate cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

Service started

--------------------------------------------------

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          7/28/2013 3:05:22 AM
Event ID:      4634
Task Category: Logoff
Level:         Information
Keywords:      Audit Success
User:          N/A
Computer:      Michael-Laptop
Description:
An account was logged off.

Subject:
	Security ID:		Michael-Laptop\Michael ********
	Account Name:		Michael ********
	Account Domain:		Michael-Laptop
	Logon ID:		0xd2ac806

Logon Type:			7

This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer.

--------------------------------------------------

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          7/28/2013 3:05:22 AM
Event ID:      4634
Task Category: Logoff
Level:         Information
Keywords:      Audit Success
User:          N/A
Computer:      Michael-Laptop
Description:
An account was logged off.

Subject:
	Security ID:		Michael-Laptop\Michael ********
	Account Name:		Michael ********
	Account Domain:		Michael-Laptop
	Logon ID:		0xd2ac814

Logon Type:			7

This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer.

--------------------------------------------------

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          7/28/2013 3:05:22 AM
Event ID:      4672
Task Category: Special Logon
Level:         Information
Keywords:      Audit Success
User:          N/A
Computer:      Michael-Laptop
Description:
Special privileges assigned to new logon.

Subject:
	Security ID:		Michael-Laptop\Michael ********
	Account Name:		Michael ********
	Account Domain:		Michael-Laptop
	Logon ID:		0xd2ac806

Privileges:		SeSecurityPrivilege
			SeTakeOwnershipPrivilege
			SeLoadDriverPrivilege
			SeBackupPrivilege
			SeRestorePrivilege
			SeDebugPrivilege
			SeSystemEnvironmentPrivilege
			SeImpersonatePrivilege

--------------------------------------------------

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          7/28/2013 3:05:22 AM
Event ID:      4624
Task Category: Logon
Level:         Information
Keywords:      Audit Success
User:          N/A
Computer:      Michael-Laptop
Description:
An account was successfully logged on.

Subject:
	Security ID:		SYSTEM
	Account Name:		MICHAEL-LAPTOP$
	Account Domain:		WORKGROUP
	Logon ID:		0x3e7

Logon Type:			7

New Logon:
	Security ID:		Michael-Laptop\Michael ********
	Account Name:		Michael ********
	Account Domain:		Michael-Laptop
	Logon ID:		0xd2ac814
	Logon GUID:		{00000000-0000-0000-0000-000000000000}

Process Information:
	Process ID:		0x1d64
	Process Name:		C:\Windows\System32\winlogon.exe

Network Information:
	Workstation Name:	MICHAEL-LAPTOP
	Source Network Address:	127.0.0.1
	Source Port:		0

Detailed Authentication Information:
	Logon Process:		User32 
	Authentication Package:	Negotiate
	Transited Services:	-
	Package Name (NTLM only):	-
	Key Length:		0

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
	- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
	- Transited services indicate which intermediate services have participated in this logon request.
	- Package name indicates which sub-protocol was used among the NTLM protocols.
	- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

--------------------------------------------------

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          7/28/2013 3:05:22 AM
Event ID:      4624
Task Category: Logon
Level:         Information
Keywords:      Audit Success
User:          N/A
Computer:      Michael-Laptop
Description:
An account was successfully logged on.

Subject:
	Security ID:		SYSTEM
	Account Name:		MICHAEL-LAPTOP$
	Account Domain:		WORKGROUP
	Logon ID:		0x3e7

Logon Type:			7

New Logon:
	Security ID:		Michael-Laptop\Michael ********
	Account Name:		Michael ********
	Account Domain:		Michael-Laptop
	Logon ID:		0xd2ac806
	Logon GUID:		{00000000-0000-0000-0000-000000000000}

Process Information:
	Process ID:		0x1d64
	Process Name:		C:\Windows\System32\winlogon.exe

Network Information:
	Workstation Name:	MICHAEL-LAPTOP
	Source Network Address:	127.0.0.1
	Source Port:		0

Detailed Authentication Information:
	Logon Process:		User32 
	Authentication Package:	Negotiate
	Transited Services:	-
	Package Name (NTLM only):	-
	Key Length:		0

This event is generated when a logon session is created. It is generated on the computer that was accessed.

The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).

The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.

The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
	- Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
	- Transited services indicate which intermediate services have participated in this logon request.
	- Package name indicates which sub-protocol was used among the NTLM protocols.
	- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.

--------------------------------------------------

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          7/28/2013 3:05:22 AM
Event ID:      4648
Task Category: Logon
Level:         Information
Keywords:      Audit Success
User:          N/A
Computer:      Michael-Laptop
Description:
A logon was attempted using explicit credentials.

Subject:
	Security ID:		SYSTEM
	Account Name:		MICHAEL-LAPTOP$
	Account Domain:		WORKGROUP
	Logon ID:		0x3e7
	Logon GUID:		{00000000-0000-0000-0000-000000000000}

Account Whose Credentials Were Used:
	Account Name:		Michael ********
	Account Domain:		Michael-Laptop
	Logon GUID:		{00000000-0000-0000-0000-000000000000}

Target Server:
	Target Server Name:	localhost
	Additional Information:	localhost

Process Information:
	Process ID:		0x1d64
	Process Name:		C:\Windows\System32\winlogon.exe

Network Information:
	Network Address:	127.0.0.1
	Port:			0

This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials.  This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command.

To not have a half-page long post I wrapped everything with code tags, but it may make some stuff hard to read. At 3:05:22am multiple events show I was logged in and "special privileges" were applied to my account. Then before even a second could go by I was logged out. Then at 3:14:00 - 3:14:01am Google Update was doing something undefined and at 3:27:06am the DWM exited with 0x40010004. Finally at 3:27:07am it says I logged my account off when according to previous events I was already logged off and I wasn't even home, and at the same time an error I'm not sure about appears.

Layback Bear said:

Why not just save your work and shut down the laptop when not in use.
Laptop are noted for not handling heat well. Any thing in auto update or scheduling might be causing this problem.

My computer is always doing something, I just use a laptop instead of a desktop because they're more efficient power-wise. As far as heat that has not been an issue. When just idling for network usage or web browsing all temps stay below 115F, under heavy use (compressing large backups) maybe it'll hit 150F.

nommy the first said:

It's currently 4AM here, so I'll have a look at the report first thing tomorrow:)


Nommy

Alright, thank you