Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Win10 Pro not Sleeping - but shutsdown

Status
Not open for further replies.

droodle

Technical User
Nov 10, 2005
75
0
0
AU
putting my Win10 Pro laptop to sleep - it seems to work however when i log in in the morning it has totally shut down - how to trouble shoot this pls ?

Log Name: System
Source: Microsoft-Windows-Kernel-Boot
Date: 2/06/2020 9:01:26 AM
Event ID: 153
Task Category: (62)
Level: Information
Keywords:
User: SYSTEM
Computer: HOSTNAME
Description:
Virtualization-based security (policies: 0) is disabled.
Event Xml:
<Event xmlns=" <System>
<Provider Name="Microsoft-Windows-Kernel-Boot" Guid="{15ca44ff-4d7a-4baa-bba5-0998955e531e}" />
<EventID>153</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>62</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2020-06-01T23:01:26.426101900Z" />
<EventRecordID>15596</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>HOSTNAME</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="Status">0</Data>
<Data Name="EnableDisableReason">0</Data>
<Data Name="VsmPolicy">0</Data>
</EventData>
</Event>

Log Name: System
Source: EventLog
Date: 2/06/2020 9:01:35 AM
Event ID: 6013
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: HOSTNAME
Description:
The system uptime is 9 seconds.
Event Xml:
<Event xmlns=" <System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6013</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-06-01T23:01:35.320558600Z" />
<EventRecordID>15595</EventRecordID>
<Channel>System</Channel>
<Computer>HOSTNAME</Computer>
<Security />
</System>
<EventData>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>
</Data>
<Data>9</Data>
<Data>60</Data>
<Data>-600 AUS Eastern Standard Time</Data>
<Binary>31002E003100000030000000570069006E0064006F00770073002000310030002000500072006F000000310030002E0030002E003100380033003600330020004200750069006C0064002000310038003300360033002000200000004D0075006C0074006900700072006F0063006500730073006F007200200046007200650065000000310038003300360032002E0031003900680031005F00720065006C0065006100730065002E003100390030003300310038002D00310032003000320000003500650032003700370036003700620000004E006F007400200041007600610069006C00610062006C00650000004E006F007400200041007600610069006C00610062006C006500000039000000340000003100360032003600300000003400300039000000450053004B00590000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: EventLog
Date: 2/06/2020 9:01:35 AM
Event ID: 6005
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: HOSTNAME
Description:
The Event log service was started.
Event Xml:
<Event xmlns=" <System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6005</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-06-01T23:01:35.319561200Z" />
<EventRecordID>15594</EventRecordID>
<Channel>System</Channel>
<Computer>HOSTNAME</Computer>
<Security />
</System>
<EventData>
<Binary>E4070600010001001700010023003F010000000000000000</Binary>
</EventData>
</Event>

Log Name: System
Source: EventLog
Date: 2/06/2020 9:01:35 AM
Event ID: 6009
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: HOSTNAME
Description:
Microsoft (R) Windows (R) 10.00. 18363 Multiprocessor Free.
Event Xml:
<Event xmlns=" <System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6009</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-06-01T23:01:35.319561200Z" />
<EventRecordID>15593</EventRecordID>
<Channel>System</Channel>
<Computer>HOSTNAME</Computer>
<Security />
</System>
<EventData>
<Data>10.00.</Data>
<Data>18363</Data>
<Data>
</Data>
<Data>Multiprocessor Free</Data>
<Data>0</Data>
</EventData>
</Event>

Log Name: System
Source: EventLog
Date: 2/06/2020 9:01:35 AM
Event ID: 6008
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: HOSTNAME
Description:
The previous system shutdown at 11:24:28 PM on ‎1/‎06/‎2020 was unexpected.
Event Xml:
<Event xmlns=" <System>
<Provider Name="EventLog" />
<EventID Qualifiers="32768">6008</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-06-01T23:01:35.314392000Z" />
<EventRecordID>15592</EventRecordID>
<Channel>System</Channel>
<Computer>HOSTNAME</Computer>
<Security />
</System>
<EventData>
<Data>11:24:28 PM</Data>
<Data>‎1/‎06/‎2020</Data>
<Data>
</Data>
<Data>
</Data>
<Data>484360</Data>
<Data>
</Data>
<Data>
</Data>
<Binary>E407060001000100170018001C002F02E4070600010001000D0018001C002F02600900003C000000010000006009000001000000B00400000100000006000000</Binary>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-General
Date: 2/06/2020 9:01:26 AM
Event ID: 12
Task Category: (1)
Level: Information
Keywords: (128)
User: SYSTEM
Computer: HOSTNAME
Description:
The operating system started at system time ‎2020‎-‎06‎-‎01T23:01:25.500000000Z.
Event Xml:
<Event xmlns=" <System>
<Provider Name="Microsoft-Windows-Kernel-General" Guid="{a68ca8b7-004f-d7b6-a698-07e2de0f1f5d}" />
<EventID>12</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>1</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000080</Keywords>
<TimeCreated SystemTime="2020-06-01T23:01:26.425990200Z" />
<EventRecordID>15591</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>HOSTNAME</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="MajorVersion">10</Data>
<Data Name="MinorVersion">0</Data>
<Data Name="BuildVersion">18363</Data>
<Data Name="QfeVersion">836</Data>
<Data Name="ServiceVersion">0</Data>
<Data Name="BootMode">0</Data>
<Data Name="StartTime">2020-06-01T23:01:25.500000000Z</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 1/06/2020 11:33:25 PM
Event ID: 10010
Task Category: None
Level: Error
Keywords: Classic
User: HOSTNAME\Andy
Computer: HOSTNAME
Description:
The server microsoft.windowscommunicationsapps_16005.12827.20200.0_x64__8wekyb3d8bbwe!microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca did not register with DCOM within the required timeout.
Event Xml:
<Event xmlns=" <System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="0">10010</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime="2020-06-01T13:33:25.076407700Z" />
<EventRecordID>15590</EventRecordID>
<Correlation ActivityID="{25789be3-d734-4636-96c6-b558d2008ae5}" />
<Execution ProcessID="72" ThreadID="21136" />
<Channel>System</Channel>
<Computer>HOSTNAME</Computer>
<Security UserID="S-1-5-21-2992743614-801305641-276804641-1001" />
</System>
<EventData>
<Data Name="param1">microsoft.windowscommunicationsapps_16005.12827.20200.0_x64__8wekyb3d8bbwe!microsoft.windowslive.calendar.AppXwkn9j84yh1kvnt49k5r8h6y1ecsv09hs.mca</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-DNS-Client
Date: 1/06/2020 11:31:23 PM
Event ID: 1014
Task Category: (1014)
Level: Warning
Keywords: (268435456)
User: NETWORK SERVICE
Computer: HOSTNAME
Description:
Name resolution for the name wpad timed out after none of the configured DNS servers responded.
Event Xml:
<Event xmlns=" <System>
<Provider Name="Microsoft-Windows-DNS-Client" Guid="{1c95126e-7eea-49a9-a3fe-a378b03ddb4d}" />
<EventID>1014</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>1014</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000010000000</Keywords>
<TimeCreated SystemTime="2020-06-01T13:31:23.138906600Z" />
<EventRecordID>15589</EventRecordID>
<Correlation />
<Execution ProcessID="2656" ThreadID="19272" />
<Channel>System</Channel>
<Computer>HOSTNAME</Computer>
<Security UserID="S-1-5-20" />
</System>
<EventData>
<Data Name="QueryName">wpad</Data>
<Data Name="AddressLength">128</Data>
<Data Name="Address">02000000A2FCAC39000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 1/06/2020 11:31:12 PM
Event ID: 42
Task Category: (64)
Level: Information
Keywords: (1024),(4)
User: N/A
Computer: HOSTNAME
Description:
The system is entering sleep.

Sleep Reason: Application API
Event Xml:
<Event xmlns=" <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331c3b3a-2005-44c2-ac5e-77220c37d6b4}" />
<EventID>42</EventID>
<Version>3</Version>
<Level>4</Level>
<Task>64</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000404</Keywords>
<TimeCreated SystemTime="2020-06-01T13:31:12.143717300Z" />
<EventRecordID>15588</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="23340" />
<Channel>System</Channel>
<Computer>HOSTNAME</Computer>
<Security />
</System>
<EventData>
<Data Name="TargetState">4</Data>
<Data Name="EffectiveState">4</Data>
<Data Name="Reason">4</Data>
<Data Name="Flags">0</Data>
<Data Name="TransitionsToOn">16</Data>
</EventData>
</Event>
 
So, you know that when a laptop is sleeping it is still using power and therefore if you leave it UNPLUGGED from AC power, it will eventually exhaust the battery and the laptop will effectively be shut down instead of sleeping. Are you leaving power connected or not?

Also see this for sleep vs. shutdown Link
 
laptop is connected to a dock which always has power.

looked at the article and tried a setting for the Intel Management engine Interface - which incidentally - HP support assistant just installed an update for that component and need to restart

thx.
 
Make sure you have all updates via HP Support Assistant. A BIOS update might make a difference too.
You might also try to turn off Windows 10 Fast Start
I all else fails, you could enable HIBERNATION and use that.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top