Skip to content

Event ID 41: The system has rebooted without cleanly shutting down first

Windows Event ID Lookup: What Windows event IDs mean: 4625, 4624, 4740, 6008, 41, 7045, 1102 and 3,000 more, with Windows' own message text, the fields and what to check.

Look up a Windows event ID from Event Viewer, a SIEM alert or a log export: what it means, the fields it records, and what to check. Many IDs are used by more than one source (event 41 is both a Kernel-Power crash and a boot error), so every definition is shown, the one people usually mean first. The message text is Windows' own, read from the event providers of Windows 10.0.26200.0, 2026-10-28; the notes are ours, based on Microsoft's security auditing reference.

Try: 4625, 4624, 4740, 6008, 41, 1074, 7045, 1102, 4104, 1149

The system has rebooted without cleanly shutting down first.

Event 41
Kernel-Power
System log
Critical

The system restarted without shutting down cleanly first: power loss, a crash, a hang or a forced power-off.

What to check: BugcheckCode non-zero means a blue screen (decimal; convert to hex, e.g. 126 = 0x7E). Zero usually means the power was cut or the machine was reset while hung.

Related: 6008, 1001

Message and fields (as Event Viewer shows them)
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Windows failed to load with error status

Event 41
Kernel-Boot
System log
Error
Message and fields (as Event Viewer shows them)
Windows failed to load with error status ….

An update was downloaded.

Event 41
WindowsUpdateClient
System log
Information
Message and fields (as Event Viewer shows them)
An update was downloaded.

The time service has been configured to use one or more input providers, however, none of the input providers are still running.

Event 41
Time-Service
System log
Warning
Message and fields (as Event Viewer shows them)
The time service has been configured to use one or more input providers, however, none of the input providers are still running. The time service has no source of accurate time.

Begin session arbitration:

Event 41
TerminalServices-LocalSessionManager
TerminalServices-LocalSessionManager/Operational log
Information
Message and fields (as Event Viewer shows them)
Begin session arbitration:

User: …
Session ID: …