HankiWhy does my Windows PC randomly restart?
Kernel-Power Event ID 41 records an unclean shutdown; it does not identify the cause. Start with the time of the restart, what you were doing and any accompanying error or dump information.
Collect the Windows evidence
- Write down whether you saw a stop-code screen, an instant power loss, or a frozen PC that you restarted yourself. Include the time and whether the machine was idle, gaming or waking from sleep.
- Open Event Viewer and inspect Windows Logs → System around that time. Open Kernel-Power 41 and read its Details, including any bugcheck information.
- Check nearby events instead of treating the most dramatic entry as the explanation. Save relevant events and keep their timestamps and time zone with your notes.
Microsoft’s Event ID 41 guidance distinguishes stop errors, forced power-button shutdowns and cases where error values are zero. A zero bugcheck value does not, by itself, prove a faulty power supply.
Choose the next question
| What you observed | What to investigate next |
|---|---|
| Stop code or a saved crash dump | Record the exact code and preserve the dump before changing drivers. |
| Freeze followed by holding the power button | Describe the freeze. The forced shutdown is a separate event. |
| Restart after a recent change | List the changed hardware, drivers, firmware or settings and their dates. |
| No usable dump | Check whether dump creation was configured and whether Windows reported a write failure. |
These are investigation prompts, not diagnoses. A timestamp correlation is a lead to test. Avoid changing several settings together: you lose the ability to tell which change affected the problem.
Organize the evidence with Hanki Diagnose
In Diagnose, choose the guided check My PC restarted by itself or showed a blue screen. Each step explains why it matters and opens the right tool: Recent Event Logs for unexpected restarts, blue screens and disk or hardware errors from the last seven days, the Crash timeline for what happened just before, and Dump analysis when Windows saved a crash dump. A read-only Fix my PC scan adds storage, device, Windows file and security checks in one pass.
Hanki summarizes what it found in plain language and keeps the raw evidence one click away. It can group evidence and help you review it; the timeline does not establish a root cause.
Prepare a report containing the symptom, reproduction steps, relevant times and exact error text. Use the Assistant’s Prepare / redact step to remove private information before you share it. Do not post a raw memory dump publicly: it can contain application data and secrets.
Make the next attempt useful
Keep a short log: date, workload, observed failure, one change made, and what happened afterward. “No restart in one short test” is weaker evidence than repeated tests under the conditions that previously failed.
If dump creation is failing, continue with the pagefile guide. Preserve important files before investigating an unstable machine.
Questions about Why does my Windows PC randomly restart?
Does Kernel-Power Event ID 41 identify the cause of a restart?
No. It records that Windows detected an unclean shutdown. Check nearby events, the bugcheck details and any saved dump before forming a hypothesis.
What if Windows did not save a crash dump?
Record what you observed and check dump settings or write-failure events. A missing dump does not prove a power-supply or other hardware fault.
Why should I change one thing at a time?
A short log of the workload, timestamps, one change and the outcome makes it easier to distinguish a useful fix from a coincidental quiet period.