How to fix critical error 41

Question

Computer has unexpected shutdown causing critical error event 41. How is this fixed?

Answer 1

Hi ,

If it is a laptop or desktop, if possible, could you provide the laptop model or your desktop configuration?

Access the c:\windows\minidump folder, copy the files to your desktop, then upload them to OneDrive or Google Drive and post the link here for analysis.

Thanks

Answer 2

Event ID 41 (Kernel-Power) does not point to a single software bug that can be “fixed”; it is a symptom that Windows detected the previous shutdown was not clean. The resolution is to identify and correct the underlying cause of the unexpected shutdown or restart.

Use these steps based on the scenarios in the event data and other logs:

1. Check if Event ID 41 contains a BugcheckCode
   • Open Event Viewer → Windows Logs → System → find the Kernel-Power, Event ID 41 entry.
   • In the event details, look at BugcheckCode:
     • If BugcheckCode is non‑zero, the system restarted because of a Stop error (blue screen).
       1. Convert the decimal BugcheckCode to hexadecimal (for example, 159 → 0x0000009F) using Calculator in Programmer mode.
       2. Use that hex code with:
          • Advanced troubleshooting for Stop error or blue screen error issue
          • Bug Check Code Reference
       3. Fix the specific driver, hardware, or configuration problem indicated by that bug check.
2. If the restart was caused by holding the power button
   • If PowerButtonTimestamp in Event ID 41 is non‑zero, Windows detected that the power button was held down to force a shutdown.
   • This is not a software error; it is a forced power‑off. To avoid future Event 41 entries:
     • Only shut down via Start → Shut down/Restart.
     • Use forced power‑off only when the system is completely unresponsive.
3. If BugcheckCode and PowerButtonTimestamp are zero (Scenario 3)
   • This usually indicates a hardware or power issue, or that Windows could not write error codes or a dump file.
   • Perform the following checks:
     1. Disable overclocking
        • In firmware/BIOS, return CPU, RAM, and GPU to default (non‑overclocked) settings and test if random restarts stop.
     2. Check memory (RAM)
        • Run a memory checker and verify all modules run at the same speed and are correctly configured.
     3. Check the power supply
        • Ensure the PSU wattage is sufficient for CPU, GPU, drives, and peripherals.
        • For desktops, consider power outages, loose power cables, or a failing PSU.
        • For laptops, check for a failing or loose battery or AC adapter.
        • If power loss is suspected, consider using an uninterruptible power supply (UPS).
     4. Check for overheating
        • Inspect fans, heatsinks, and internal temperatures.
        • Clean dust and ensure proper airflow.
     5. Check virtualization/cluster heartbeat
        • If this is a Hyper‑V VM (non‑clustered), the Hyper‑V heartbeat feature on the host can restart an unresponsive VM.
        • In a Hyper‑V cluster, the “Enable heartbeat monitoring for the virtual machine” option or cluster health monitoring can restart VMs.
        • In VMware, similar heartbeat or third‑party clustering can trigger restarts.
     6. Review related events
        • Use Event ID 6008 (“The previous system shutdown was unexpected”) to find the shutdown time.
        • Around that time, review Application and System logs for disk, power, driver, or hardware errors.
4. If Event ID 46 (volmgr) appears: “Crash dump initialization failed!”
   • When Event ID 41 has all values as 0 and there is a volmgr Event ID 46, the system could not initialize the crash dump (often due to pagefile configuration).
   • Check pagefile settings and ensure a valid pagefile exists on a local disk so Windows can write memory dumps and bugcheck information.
5. Improve diagnostics for future occurrences
   • Ensure a dump file is configured (default is pagefile‑based) so that future Stop errors can be captured.
   • Optionally disable automatic restart on system failure so the blue screen and bugcheck code remain visible:
     1. Right‑click My Computer → Properties → Advanced system settings → Advanced.
     2. Under Startup and Recovery, select Settings.
     3. Clear “Automatically restart.”
6. About “fixing” Event ID 41 itself
   • Event ID 41 is a record of an abnormal/dirty shutdown, not a root cause.
   • After correcting the underlying hardware, power, or Stop‑error cause, future shutdowns should be clean and Event ID 41 should no longer appear.
   • The registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Reliability tracks dirty shutdown counts; clearing its values (DirtyShutdown, LastAliveStamp, TimeStampInterval) only affects tracking and the Shutdown Event Tracker prompt, not the underlying issue.

In summary, fixing Event ID 41 means:

• Determine whether the cause is a Stop error, forced power‑off, or power/hardware instability.
• Use bugcheck codes, volmgr Event ID 46, and surrounding Application/System events to identify the failing component.
• Correct the hardware, driver, or configuration problem so that Windows can shut down cleanly.

---

References:

• Advanced troubleshooting for Event ID 41: "The system has rebooted without cleanly shutting down first"