Event Viewer Critical

Hello,

Today while looking through i Event Viewer, which i snoop around in periodically, i noticed 2 Critical Notices related to the kernel-power and was wondering if i should be concerned and perhaps someone can provide me some insight as to what exactly these faults are ? and if i can take any corrective action to remedy them? Any input is appreciated. Here is a breakdown of the critical errors.

1) The first critical error reads:

"The system has rebooted without cleanly shutting down first. This error is because the system stopped responding and the hardware watchdog triggered a reset."

LOG NAME: System
SOURCE: Kernel Power
EVENT ID: 142
TASK CATEGORY: (173)
LEVEL CRITICAL
KEY WORDS: (70368744177664), (2)

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>142</EventID>
<Version>0</Version>
<Level>1</Level>
<Task>173</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2017-03-28T20:49:08.107192200Z" />
<EventRecordID>37605</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Moyer</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="ResetReasonMask">0</Data>
</EventData>
</Event>


2) And the second critical error reads:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 3/28/2017 4:49:08 PM
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (70368744177664),(2)
User: SYSTEM
Computer: Moyer

Description:

The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
<EventID>41</EventID>
<Version>4</Version>
<Level>1</Level>
<Task>63</Task>
<Opcode>0</Opcode>
<Keywords>0x8000400000000002</Keywords>
<TimeCreated SystemTime="2017-03-28T20:49:08.098846500Z" />
<EventRecordID>37604</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="8" />
<Channel>System</Channel>
<Computer>Moyer</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="BugcheckCode">0</Data>
<Data Name="BugcheckParameter1">0x0</Data>
<Data Name="BugcheckParameter2">0x0</Data>
<Data Name="BugcheckParameter3">0x0</Data>
<Data Name="BugcheckParameter4">0x0</Data>
<Data Name="SleepInProgress">5</Data>
<Data Name="PowerButtonTimestamp">131352077255704496</Data>
<Data Name="BootAppStatus">0</Data>
<Data Name="Checkpoint">0</Data>
<Data Name="ConnectedStandbyInProgress">false</Data>
<Data Name="SystemSleepTransitionsToOn">1</Data>
<Data Name="CsEntryScenarioInstanceId">0</Data>
</EventData>
</Event>

 

Was the Power Button pressed and held instead of tapped to bring the computer out of sleep/hibernation?

 

I'm not really sure? It may have been. If so, would it result in this situation? The critical error instance?

 

Yes, because the machine wasn't shut down properly. Windows needs time to "sort things out" before it shuts down. Pressing and holding the power button causes a hard shut down which in a few instances can also cause file corruption.

 

Hey, thanks for your wisdom mdonah.....i appreciated it!