Windows 10 Recurring Critical Error Reported in Windows 10 v1909 Event Viewer

  • Thread starter Thread starter Alexander_PH
  • Start date Start date
A

Alexander_PH

From the Windows 10 Event Viewer:

A total of 190 “CRITICAL” errors, all with …

…. identical Event ID of 41;

…. identical Task Category of 63, and;

…. identical 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.”


were recorded from 11:14:55pm 20Feb2020 to 6:55:30am, 23Dec2020.



All the above events were recorded even if the exit from Windows was

done via … Start Menu | Shutdown or Signout | Shutdown.





_____

Questions:

[Q1
] What process in Windows 10 is causing this?

[Q2] What do I need to do to prevent this CRITICAL-ERROR from recurring?




_____

Background:
my long-established home desktop pc shutdown procedure is as follows:

[S1] close the Internet Connection being used (LAN/DSL Modem, or WLAN/Wifi Modem)

[S2] disable the Network Adapter being used via … Network & Sharing Center | Change-Adapter-Settings

[S3] perform Disk Clean-up, including “Clean up System Files”.

[S4] shutdown the home desktop pc via … Start Menu | Shutdown or Signout | Shutdown

.......... Home desktop pc running on Windows 10 Home Single Language v1909, build 18363.1256

.......... last update: KB4592449 on 12Dec2020


Note:I have opted not to connect to the MS Cloud since right at its inception. Warning Messages found

.......... in the Event Viewer (from source: DeviceSetupManager) seem to point to Windows 10 assuming

.......... as its base-case that everybody connects to the MS Cloud.

.......... I hope MS respects each individual’s preferences.






_____

Event Information follows

Log Name: System

Source: Microsoft-Windows-Kernel-Power

Date: 12/23/2020 6:55:30 AM

Event ID: 41

Task Category: (63)

Level: Critical

Keywords: (70368744177664),(2)

User: SYSTEM

Computer: Home-PC1

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>6</Version>

<Level>1</Level>

<Task>63</Task>

<Opcode>0</Opcode>

<Keywords>0x8000400000000002</Keywords>

<TimeCreated SystemTime="2020-12-22T22:55:30.468078600Z" />

<EventRecordID>62132</EventRecordID>

<Correlation />

<Execution ProcessID="4" ThreadID="8" />

<Channel>System</Channel>

<Computer>Home-PC1</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">6</Data>

<Data Name="PowerButtonTimestamp">0</Data>

<Data Name="BootAppStatus">3221225684</Data>

<Data Name="Checkpoint">0</Data>

<Data Name="ConnectedStandbyInProgress">false</Data>

<Data Name="SystemSleepTransitionsToOn">1</Data>

<Data Name="CsEntryScenarioInstanceId">0</Data>

<Data Name="BugcheckInfoFromEFI">false</Data>

<Data Name="CheckpointStatus">0</Data>

</EventData>

</Event>

Continue reading...
 
Back
Top