Windows 11 Keeps Restarting on Its Own? How to Find Out Why

Windows 11 Keeps Restarting on Its Own? How to Find Out Why

You’re in the middle of something and the screen just goes black for a second, then you’re back at the lock screen — no warning, no blue screen you had time to read, just a PC that decided to restart itself. It happens once and you shrug it off. Then it happens again a day or two later.

An uninvited restart almost always has a specific cause, even when it feels completely random — Windows itself, a driver, or the hardware underneath it is reacting to something specific, it’s just not something you’re seeing happen in the moment. The trick is finding the record it left behind rather than trying to catch it live.

Quick explanation: this guide covers confirming it’s actually an unexpected restart rather than a scheduled one, overheating as a built-in protective shutdown, power settings and a failing power supply on desktops, a driver crashing so fast the blue screen flashes and reboots before you can read it, testing your RAM for instability, and telling a genuinely random restart apart from Windows Update quietly restarting on its own schedule.

For the full feature list and usage details, you can also visit the Fixyfier Documentation.

Quick Answer

A PC that restarts without warning almost always logs Event ID 41 in the System event log the moment it happens, which confirms it wasn’t a clean, intentional shutdown. From there, the most common causes are overheating (Windows restarting itself as a safety measure), a crashing driver whose blue screen flashes by too fast to read because “Automatically restart” is turned on, and unstable RAM. On a desktop, a failing power supply is also worth ruling out. Less dramatically, it’s sometimes just Windows Update restarting on its own overnight schedule rather than anything actually being wrong.

Confirm It Was Actually an Unexpected Restart

Before chasing hardware or drivers, it’s worth confirming Windows agrees something went wrong — a genuinely unexpected restart isn’t a silent event as far as Windows is concerned, even though it feels that way from your side of the screen.
Every time Windows starts up after a shutdown that wasn’t clean, it logs Event ID 41 from the Kernel-Power provider in the System event log, with a timestamp for exactly when it happened. Finding one of these lined up with when your PC restarted is the confirmation that this wasn’t a scheduled reboot or something you triggered and forgot about.
Get-WinEvent -FilterHashtable @{LogName='System'; ProviderName='Microsoft-Windows-Kernel-Power'; ID=41} -MaxEvents 5
Fixyfier’s Log Report Generators section includes a System Event Logs tool that pulls together kernel and system-level diagnostics like this one in a single place, without needing to build the event filter yourself first.

Overheating Can Trigger a Protective Restart

Windows can force a restart as a safety measure when a component — usually the CPU or GPU — reaches a temperature the firmware considers unsafe to keep running at. This is by design, not a bug, and it tends to line up with demanding tasks: gaming, video export, or anything else that pushes the hardware hard for an extended stretch.
The pattern to look for is restarts that cluster around demanding activity rather than happening at random moments while the PC is mostly idle. Dust buildup in a laptop’s vents, old thermal paste, or a fan that’s stopped spinning as effectively as it used to are the usual underlying causes, and a basic cleaning or a fresh coat of thermal paste resolves this more often than people expect.
If the pattern doesn’t line up with heavy use at all — restarts happening just as easily while the PC is sitting idle on a desktop — overheating is a less likely explanation, and it’s worth moving on to the driver and memory checks below instead.

Power Settings, Sleep, and a Failing Power Supply

A restart that happens specifically around sleep or wake — going to sleep and then restarting instead of waking normally, or restarting shortly after you resume from sleep — usually points at a power management setting rather than a hardware fault. Fast Startup and USB selective suspend are common culprits, since both change how the system handles power state transitions.
On a desktop, it’s also worth considering the power supply itself, particularly if the restarts happen more under load — launching a game, plugging in a second monitor, or connecting a power-hungry USB device. An aging or undersized PSU that’s struggling to keep up with a sudden draw is a genuinely common cause of restarts that otherwise look completely random.
Fixyfier’s Security & Privacy section includes a Restore Default Power Plans option, which is a fast way to rule out a drifted or corrupted power configuration as the cause before assuming it’s a hardware problem.

A Driver Crash, With the Blue Screen Set to Restart Automatically

What looks like a completely silent restart is very often a blue screen you simply never got to see. Windows has a system failure setting called “Automatically restart” that’s on by default, and it restarts the PC the instant a crash happens rather than leaving the stop code on screen for you to read.
Turning that setting off — under System Properties > Advanced > Startup and Recovery Settings, unchecking “Automatically restart” — won’t prevent the crash, but it will let the next one actually show you the stop code instead of restarting past it, which turns a mystery restart into a specific, diagnosable crash the same way a readable blue screen would be.
Fixyfier’s Administrative Tools section puts Device Manager a click away, useful for updating or rolling back whichever driver the crash dump ends up pointing to once you can actually read the stop code.
NordVPN
One Thing Worth Knowing

Researching a Restart Problem From a Device That Isn't the One Restarting

A PC that keeps restarting on its own isn't one you can leave open in a browser tab while you dig through fixes, so there's a good chance you're reading this from a phone, a work laptop, or someone else's computer instead — often on whatever network happens to be available. NordVPN keeps that research session encrypted no matter which device or connection you end up using to get through it.

Protect This Session

Ruling Out Unstable Memory

Bad or unstable RAM is one of the more common underlying causes of restarts that seem to have no pattern at all — no correlation with heat, no correlation with sleep, nothing obviously in common between one restart and the next. Memory errors can corrupt data the system depends on to keep running, and a hard restart is often how that ends up surfacing.
Windows includes a built-in memory diagnostic that runs a series of tests against your RAM on the next restart and reports back whether it found anything. It takes a few minutes and needs the PC to restart to run, but it’s a genuinely useful way to either confirm or rule out memory as the cause before spending more time elsewhere.
Fixyfier’s Memory & Graphics Diagnostics section includes a Memory Diagnostic Utility shortcut that launches this same built-in test directly, without needing to search for it through Windows Settings first.

Ruling Out a Scheduled Windows Update Restart

Before assuming something’s actually wrong, it’s worth checking whether this is Windows Update quietly doing exactly what it’s designed to do. Windows can restart on its own overnight, or shortly after you’ve been away from the keyboard for a while, to finish installing an update it’s already downloaded — and if you weren’t watching, that can look identical to a random crash-restart.
Checking your update history for an install that lines up with when the restart happened is the fastest way to rule this in or out. If it matches, this isn’t the same problem as an unexpected Event ID 41 restart at all — it’s Windows doing routine maintenance on a schedule you didn’t consciously set.
If it turns out to be Windows Update itself misbehaving — stuck, failing, or repeatedly re-installing the same update — rather than just restarting to finish a normal install, that’s covered in more depth in a dedicated guide on Windows Update stuck downloading or installing.

Frequently Asked Questions

Is a random restart the same thing as a blue screen crash?

Often, yes — it’s just a blue screen you didn’t get to see. Windows’ default setting restarts the PC the instant a crash happens rather than leaving the stop code visible, so what feels like a silent, unexplained restart is frequently the exact same underlying crash a blue screen article would cover, just hidden by that setting.

Could this be a sign my hard drive or SSD is failing?

It’s possible but less common than overheating, a driver crash, or unstable RAM. A failing drive tends to come with other warning signs too — slow file access, files that won’t open, or error messages when copying data — so it’s worth checking the drive’s health if restarts are showing up alongside symptoms like those, rather than assuming it’s the drive on restarts alone.

Why does my desktop restart under load but my laptop restarts at random moments?

That difference is a useful clue rather than a coincidence. A desktop restarting specifically under load points more toward the power supply or overheating, since both are tied to how hard the hardware is working. A laptop restarting with no obvious pattern points more toward a driver crash or unstable memory, since those aren’t necessarily tied to how much you’re actually asking the hardware to do.

Let Fixyfier Help You Track Down What’s Behind the Restarts

Fixyfier’s Log Report Generators section puts System Event Logs a click away for confirming what actually happened, its Administrative Tools section includes a Device Manager shortcut for the driver side of things, and its Memory & Graphics Diagnostics section includes a Memory Diagnostic Utility shortcut — together, enough to confirm what’s actually going on before you start replacing hardware on a guess.
Get Fixyfier from the Microsoft Store