Computer shutdown/crash out of nowhere

Question

Noticeable events in the event viewer that caught my eye:

"IOMMU fault reporting has been initialized." event ID: 16

"ACPI thermal zone _TZ.TZ00 has been enumerated" event ID: 125

and of course the events where my computer unexpectedly crashes and shutdowns completely
"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 ID: 41

Found a recent thread that might describe my issue (https://learn.microsoft.com/en-us/answers/questions/5739863/crash-while-away-from-computer)
I guess the question number is 5739863

Answer 1

Hello SgtGracious,

Thanks for getting back to me.

I also think that this is a thermal issue, PC temperature can go up to 95-100 Celsius when dealing with heavy workload but go up to 105 is way past the safe threshold. That is also related to event 125, which means the hardware thermal sensor zone is loading threshold for it and might consider force shutdown computer to protect the device.

Usually, this often link to super heavy load to the computer or overclocking. However, if it happens out of nowhere, it's most likely that some hardware might not functioning well (OS and software issue will raise the temperature gradually instead of a large spike). Changing the thermal paste is a great idea, the cooling has already failed, so you should change it even though it might not be the main cause. Also, you should check the other hardware part as well to see if everything is okay. Thank you for your understanding.

Answer 2

Hello SgtGracious,

Welcome to Microsoft Q&A forum.

Before we proceed further, may I know if you have checked the AI assistant suggestion yet? If you did, may I know how it goes?

Additionally, may I know if the crash generates any dump file about it? You can check the by going to C:\Windows\Minidump, if you find it, please upload it to your OneDrive and share it here so I can check for you.

I'm waiting for your reply.

Answer 3

Event ID 41 (Kernel-Power) only tells that Windows detected an unexpected/dirty shutdown when it next booted; it does not by itself identify the root cause.

Use the Event ID 41 data and surrounding events to narrow down the cause:

1. Determine which scenario applies
   • If Event ID 41 includes a nonzero BugcheckCode, the shutdown is due to a Stop error (blue screen). This corresponds to Scenario 1 in the documentation.
   • If Event ID 41 shows a nonzero PowerButtonTimestamp, the restart was triggered by pressing and holding the power button (Scenario 2).
   • If Event ID 41 is missing, or BugcheckCode and PowerButtonTimestamp are both zero, treat it as Scenario 3 (power loss, hard hang, or shutdown too fast for Windows to log details).
2. If there is a BugcheckCode (Scenario 1)
   1. Open Event Viewer → Windows Logs → System → find the Kernel-Power Event ID 41 around the crash time.
   2. In the event details, note BugcheckCode and parameters.
   3. Convert the decimal BugcheckCode to hexadecimal using Calculator in Programmer mode as described:
      • View → Programmer → Dec → enter BugcheckCode → select Hex.
   4. Use the resulting hex code with:
      • “Advanced troubleshooting for Stop error or blue screen error issue”.
      • “Bug Check Code Reference” to look up the specific bugcheck and follow the targeted troubleshooting for that code.
3. If there is no BugcheckCode or it is zero (Scenario 3) When Event ID 41 has BugcheckCode = 0 and/or is missing, Windows could not write error codes before power was lost or the system hung. Typical causes:
   • Power supply issues (desktop unplugged, power outage, underpowered or faulty PSU).
   • Battery removed/drained on a laptop.
   • System hard hang blocking disk writes; then power is cut or power button is held.
   Actions:
   1. Check for physical power issues:
      • For desktops: verify power cable, power strip/UPS, and PSU health.
      • For laptops: check battery and AC adapter; avoid removing power while running.
   2. Check for hard hangs:
      • Next time the system appears frozen, press Caps Lock and see if the keyboard LED toggles. If it does not, the system is likely hard-hung.
      • If forced to power off, expect Event ID 41 with zero codes on next boot.
   3. Review System log around the time of Event ID 41:
      • Look for Event IDs 1001 (bugcheck), 6008 (unexpected shutdown), and any disk, driver, or hardware errors just before the reboot.
      • Use the history of Event IDs 12, 13, 19, 41, 1001, 1074, 6008, 6009, and 7045 to see if the crashes started after a specific driver, firmware, or Windows update.
4. If the restart is from holding the power button (Scenario 2)
   • Event ID 41 will show a nonzero PowerButtonTimestamp.
   • This indicates a manual forced shutdown, usually because the system was unresponsive.
   • Minimize using this method; instead, troubleshoot the underlying hangs (for example, by checking for “hang”, “responding”, or “blank screen” issues as suggested in the Windows Help link in the documentation).
5. Understand the related shutdown events
   • Event ID 1074 (User32): clean shutdown or restart initiated by an application or user (Start menu, Ctrl+Alt+Del, or shutdown.exe). If this is present before a reboot, the restart was intentional.
   • Event ID 6006: Windows was shut down cleanly.
   • Event ID 6008: previous shutdown was unexpected (dirty shutdown).
   • For unexpected reboots caused by bugchecks, you typically see 41 (Kernel-Power), 1001 (WER-SystemErrorReporting), and 6008 (EventLog) together.
6. Additional notes
   • A “dirty shutdown” (power cut, forced power-off) can cause data loss or corruption and lead to boot issues. The system tracks these in the reliability registry keys and in the boot status file (Bootstat.dat), which Windows uses to detect abnormal shutdowns and offer recovery options.
   • The IOMMU and ACPI thermal zone messages by themselves are normal initialization messages; focus on whether Event ID 41 has bugcheck data and what other errors appear immediately before the crash.

If the pattern matches the referenced thread (crashes while idle/away), use the above steps to confirm whether there is a bugcheck code and then follow the bugcheck-specific guidance from the Stop error troubleshooting and Bug Check Code Reference.

---

References:

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