Kernel-Power Event ID 41 error, System has rebooted without cleanly shutting down

Windows Kernel Event ID 41 is a common error to find on out in the Event Viewer on Windows 10/8/7 and Windows Server. Microsoft recently published an article about ways to fix those issues.

The system has rebooted without cleanly shutting down first


The system has rebooted without cleanly shutting down first

Symptoms are your computer restarts, and a critical error message is logged in the event log:

Log Name: System
Source: Microsoft-Windows-Kernel-Power
Event ID: 41
Level: Critical
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.

Why does system Generates Kernel-Power Event ID 41 error?

The kernel power Event ID: 41 error is generated under different scenarios where the computer is shut down or restarts unexpectedly. When the computer that is running Windows is started, a check is performed to determine whether the computer was cleanly shut down. If the computer was not shut down correctly, a Kernel-Power Event 41 message is generated. In the following three scenarios, an Event 41 may be generated

How to Fix Windows Kernel Event ID 41? Or how to find the root cause of it?

In this article, Microsoft has mentioned three different scenarios of why this happens and how to fix it.

Scenario 1:

The computer restarted, and there is a Stop error BugCheckCode in the event data

Scenario 2:

Shut down the computer by pressing and holding the power button

Scenario 3:

The system randomly restarts and no Stop error BugcheckCode is listed, or the computer is completely unresponsive (hard hang)

For further details on how to fix it review this support document from Microsoft visit KB2028504.

Posted by on , in Category Windows with Tags
Shyam aka “Captain Jack” is a Microsoft MVP alumnus and a Windows Enthusiast with an interest in Advanced Windows troubleshooting. Suggestions made and opinions expressed by him here are his personal one's and not of his current employers. He blogs at