Windows 11 restarts randomly: how to fix it

Quick answer: A random restart means Windows did not shut down on its own terms. Start by opening Event Viewer and looking for Kernel-Power Event ID 41, 1074 and 6008 in the System log: 1074 points to a planned restart such as an update, while 41 with a bug check code points to a blue screen crash. Turn off Automatically restart so the next crash stays on screen with its stop code. If the log shows no code at all, Microsoft points to hardware: power, overheating, overclocking and memory.

Applies to: Windows 11 desktops and laptops that reboot without warning, during use or while idle (most steps also work in Windows 10). If you see a blue screen with a stop code before each restart, our guide to the “Your PC ran into a problem” screen goes deeper into specific stop codes.

Match what you see to a cause

Microsoft’s Event ID 41 article says an unexpected shutdown can come from a power interruption or a Stop error, and that the event by itself may not explain what happened. What you notice around each restart narrows it down.

What you seePossible causeGo to
Restarts overnight or when you step awayWindows Update installing and restartingFixes 1 and 3
Blue screen flashes, then the PC rebootsStop error from a driver, device or softwareFixes 2 and 7
Instant power-off and reboot, no blue screenPower supply, battery or power cutFix 4
Restarts under load, such as gaming or video exportHeat, overclocking or an undersized power supplyFixes 4, 5 and 6
Started after new RAM, a GPU or other hardwareNew device, its driver or its power drawFixes 6 and 7
Keyboard and screen freeze first, then a restartHard hang, possibly hardwareFixes 5 and 6
Nothing obvious, still restartsDamaged system files or a bad recent changeFixes 8 and 9

Fix 1: Check which event Windows logged

As general guidance, Windows writes entries to the System log when it shuts down or restarts, so the log may tell you whether the restart was planned or not. To open it:

  1. Press Windows + X and select Event Viewer.
  2. In the left pane, open Windows Logs > System.
  3. Select Filter Current Log in the right pane, type 41,1074,6006,6008 in the event ID box and select OK.
  4. Look at the entries closest to the time of the restart.

Microsoft’s Event ID 41 troubleshooting article explains what each ID means:

  • 1074: an app or a user started the shutdown or restart, for example from the Start menu or through a program. The entry names the process and the user, which is how an update restart shows up.
  • 6006: Windows was turned off cleanly.
  • 6008: the last shutdown was unexpected. Its time is a good anchor for what to check next.
  • 41 (Kernel-Power, level Critical): Windows started again without a clean shutdown first. It is logged at the next startup.

Open the Event ID 41 entry and look at the Details tab. According to Microsoft, a nonzero BugcheckCode means a Stop error caused the restart; a nonzero PowerButtonTimestamp means someone held the power button; and zeros everywhere, or no Event 41 at all, mean Windows could not record a cause, which Microsoft links to power and hardware problems.

Microsoft also says that if every value in Event 41 is zero, look for Event ID 46 from volmgr reporting that crash dump initialization failed. In that case Windows could not write the crash data, and Microsoft suggests checking the page file setup, since the default dump file is the page file.

As general guidance, Windows also includes Reliability Monitor, which may be easier to read than Event Viewer. Search the Start menu for reliability history and open it; days with a crash or a shutdown problem are marked on a timeline, and selecting one may show the related event.

Fix 2: Turn off automatic restart to see the stop code

As general guidance, Windows is often set to restart right after a Stop error, so the blue screen can vanish before you read it. Microsoft’s article says to clear the restart option if you see a stop code that Event 41 does not include. In Windows 11:

  1. Press Windows + R, type sysdm.cpl and select OK (on many PCs you can also reach it from Settings > System > About > Advanced system settings).
  2. On the Advanced tab, under Startup and Recovery, select Settings.
  3. Clear Automatically restart and select OK.

The next crash will now stay on screen. Note the stop code, such as PAGE_FAULT_IN_NONPAGED_AREA, and any file name shown with it. Microsoft’s support page on unexpected restarts says this code and module name help identify the cause. The trade-off: the PC no longer reboots on its own after a crash, so turn the option back on when you are done.

Event 41 stores the bug check code as a decimal number, while many references list it in hexadecimal. Microsoft’s conversion method uses the Windows Calculator in Programmer mode: with Dec selected, type the number, then select Hex. Its example is 159, which becomes 0x9F, written in full as 0x0000009F. Search for that code, or see our guide to the blue screen restart message.

Fix 3: Rule out Windows Update restarts

If Event 1074 sits right before each restart and names an update process, the reboot was planned by Windows rather than caused by a fault. As general guidance, you can steer when that happens:

  1. Open Settings > Windows Update > Advanced options.
  2. Set Active hours to the hours you normally use the PC, or let Windows adjust them automatically. Windows is designed to avoid restarting for updates inside that window.
  3. Turn on the option that notifies you when a restart is needed, if your version offers it, so you get a warning first.

Option names may vary between Windows 11 versions. On a work or school PC, your organization may control these settings and the restart schedule.

Fix 4: Check the power supply and battery

When Event 41 shows a bug check code of zero, or no Event 41 appears, Microsoft says this may point to a power problem: the PC lost power before it could record anything. The conditions it lists:

  • On a laptop, the battery was removed or ran flat.
  • On a desktop, the plug came out or there was a power cut.
  • The power supply is faulty or too weak for the hardware in the PC.

Microsoft notes that more memory, a newer processor, extra drives or external devices can draw more power than the existing supply can deliver steadily. If outages or brownouts caused the restarts, it suggests an uninterruptible power supply (UPS).

As general guidance, also try a different wall outlet without a power strip, reseat the power cables, and on a laptop test with the original charger. A desktop that restarts only under heavy load is a candidate for a power supply check by a technician.

Fix 5: Check for overheating

Microsoft’s hardware checklist includes looking at internal temperatures for overheating parts. As general guidance, many PCs protect themselves by switching off when the processor or graphics card gets too hot, which looks like a sudden restart.

  • Clean dust from vents and fans, and make sure the fans spin.
  • Keep a laptop on a hard, flat surface so air can reach the intake.
  • Watch temperatures with the manufacturer’s utility or the motherboard’s firmware screen while the PC is under load.

Our laptop overheating guide covers cooling and power settings step by step.

Fix 6: Undo overclocking and test the memory

Microsoft recommends disabling overclocking and confirming the problem still happens at standard speeds. As general guidance, that may include CPU, GPU and memory overclocks, and memory profiles such as XMP or EXPO set in the firmware. Put them back to default, then use the PC as usual for a while.

Microsoft also suggests checking memory health and configuration, and making sure all memory modules run at the same speed and are set up correctly. As general guidance, the built-in tool is Windows Memory Diagnostic: press Windows + R, type mdsched.exe and choose to restart and check now. Save your work first, because the PC restarts straight away. If you recently added RAM, testing with only the original modules is another quick check.

Fix 7: Remove new hardware and check drivers

Microsoft’s support page on unexpected restarts says a hardware device, its driver or software can cause them. Its basic steps start with these:

  1. Remove any hardware you added just before the restarts began, then see whether they stop.
  2. Start the PC in Safe Mode, which loads fewer drivers. As general guidance, if it stays up there, a driver or startup app is the stronger suspect. See how to boot into Safe Mode.
  3. Open Device Manager and look for devices with a warning icon. Update, disable or uninstall them, as the page suggests.

As general guidance, graphics, chipset, storage and network drivers are worth updating from the PC or device maker. Our guide on how to update drivers in Windows 11 explains where to get them and when a rollback makes more sense. If the restarts began after a driver update, rolling back that driver is the faster test.

Fix 8: Free up space, update and repair Windows

The same Microsoft page suggests keeping 10% to 15% of the system drive free and installing the latest updates through Windows Update, which can include fixes for stability problems.

If the restarts continue, damaged system files may play a part. As general guidance, open Terminal (Admin) and run these commands one at a time:

  1. DISM /Online /Cleanup-Image /RestoreHealth
  2. sfc /scannow

As general guidance, DISM repairs the Windows image files that SFC may rely on, so it usually runs first and needs an internet connection. See how to run sfc /scannow and read the results for what each result means.

Fix 9: Roll back with System Restore

The last basic step on Microsoft’s list is to restore Windows from a restore point or another recovery option. As general guidance, System Restore undoes recent system changes such as drivers and updates, and only helps if a restore point exists from before the restarts began.

Warning: apps and drivers installed after the chosen restore point may be removed. Back up important files before you start.

  1. Search the Start menu for Create a restore point and open it. As general guidance, the exact button names may vary slightly between versions.
  2. Select System Restore, then Next.
  3. Pick a point dated before the problem and select Scan for affected programs to see what changes.
  4. Confirm and let the PC restart.

Microsoft’s Event 41 article ends its hardware checklist with one more idea: if nothing isolates the problem, return the system to its default configuration and see whether the restarts continue. If they do, even after a clean start, the manufacturer’s hardware diagnostics or a repair shop are the next step.

Official sources

How we write our guides: read our editorial policy.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *