Spontaneous Reboots - Event ID: 41

Hi,

Kernel-Power 41 (63) error mostly means the problem with power supplying. Can you replace power supply unit for checking? It may mean problems with power management in BIOS or motherboard too.

And you may try to turn off all CPU power saving modes in BIOS (different C states) to check if the problem is in motherboard.

See some details at https://docs.microsoft.com/en-us/windows/client-management/troubleshoot-event-id-41-restart

Event ID 41 (Kernel-Power) indicates that Windows detected an unexpected shutdown or restart. In this case, the event includes a nonzero BugcheckCode (59) and parameters, so the reboot is due to a Stop error (blue screen), not a power button press or power loss.

From the provided context, Event ID 41 by itself does not fully identify the root cause. It records that Windows restarted without a complete shutdown and that a bug check occurred. To troubleshoot further, use these steps based on the documented guidance:

1. Correlate Event ID 41 with other shutdown/reboot events:
   • In Event Viewer → Windows Logs → System, filter for Event IDs 41, 1074, 6006, 6008, and 6009.
   • Event ID 41 and 6008 together indicate unexpected reboots; 1074, 13, and 6009 indicate normal reboots.
   • Use the timestamps to see what else was happening just before the reboot.
2. Check whether this is a power or hardware issue:
   • Event ID 41 with a bug check code can still be related to hardware instability (power, memory, overheating, etc.).
   • Review System and Application logs for errors just before the reboot time (for example, disk, power, or driver-related errors).
   • If the system ever shows Event ID 41 with BugcheckCode = 0 or no Event ID 41 at all, that pattern often points to power supply or power interruption issues.
3. Look for signs of unresponsive system or hard hangs:
   • If the system sometimes becomes unresponsive (hard hang) and then is powered off, Event ID 41 may appear with certain fields (like PowerButtonTimestamp) set, or with bug check values zero.
   • In such cases, the documentation recommends checking hardware:
     • Disable any overclocking.
     • Test memory health and configuration.
     • Verify the power supply is adequate and stable.
     • Check for overheating.
4. Check for crash dump issues:
   • If there are Event ID 41 entries where all values are zero and an Event ID 46 from volmgr (“Crash dump initialization failed!”), verify pagefile and dump configuration as described in the documentation.
5. Use the Stop error (bug check) details:
   • Because BugcheckCode is nonzero, Windows should be writing a memory dump at the time of the crash.
   • Analyze the dump file (using tools like WinDbg) to identify the driver or component causing the Stop error.
   • If the Stop error code appears on-screen but not in Event ID 41, the documentation recommends disabling “Automatically restart” so the Stop message can be read:
     • Right-click This PC → Properties → Advanced system settings → Advanced → Startup and Recovery → Settings → clear “Automatically restart”.
6. If the system is virtualized or part of a managed environment:
   • For Hyper-V or other hypervisors, heartbeat or cluster software can restart a VM if it becomes unresponsive. In that case, review hypervisor/cluster logs and heartbeat settings.
7. If hardware checks and dump analysis do not isolate the issue:
   • Return the system to default configuration (no overclocking, default BIOS/UEFI settings, minimal attached devices) and verify whether the issue persists.

These steps align with the documented troubleshooting approach for Event ID 41: use the presence of a bug check code to focus on Stop error analysis and, in parallel, check for hardware and power stability issues that can cause random reboots.

References:

• Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"
• Troubleshoot unexpected reboots using system event logs