Why Does My PC Keep Restarting Randomly?

When a PC restarts out of nowhere, it’s more than an annoyance. You can lose unsaved work, corrupt files, and end up stuck in a loop that breaks updates or games. The upside is that “random” restarts rarely stay random once you collect a few clues.

This article walks you through a clean diagnosis path for Windows desktops and laptops. You’ll start with checks that take minutes, then move into deeper tests that narrow the fault to a driver, a setting, or a piece of hardware.

Restart Clues You Can Grab Right Away

Before changing anything, note three things. They point you toward the right fix faster than any generic checklist.

• What did the screen do? Blue screen with text, black screen with instant reboot, or a freeze first.
• What were you doing? Gaming, video calls, idle desktop, waking from sleep, copying files.
• What changed recently? Driver update, Windows update, new RAM, new GPU, BIOS change, new USB device.

If you can, write down the clock time of the last reboot. You’ll use it to line up the System log entries.

Why Does My PC Keep Restarting Randomly? Start With These Checks

Do these in order. After each step, use the PC as you normally would until you either hit another restart or you gain confidence the issue is gone.

Show The Crash Instead Of Auto-Rebooting

Windows can be set to reboot right after a crash. That hides the blue screen and makes the restart feel “out of the blue.” Turn off auto-restart so you can see the stop code and any driver name.

1. Open Settings and search for Advanced system settings.
2. Under Startup and Recovery, select Settings.
3. Uncheck Automatically restart.

If you later hit a blue screen, take a photo of the stop code. Microsoft’s official stop code guidance lists the same starting move and the next actions to try. Microsoft Learn stop code troubleshooting is a good baseline reference.

Check Event Viewer For Unclean Shutdown Markers

Even when Windows reboots fast, it often logs what happened. Event Viewer is your quickest “what just happened?” tool.

1. Right-click Start, open Event Viewer.
2. Go to Windows Logs → System.
3. Filter the log for Kernel-Power.

Event ID 41 is a common one during surprise restarts. Microsoft explains what its fields mean and why a “bug check code” of zero can point to a power interruption or a crash that didn’t finish writing data. Microsoft Learn on Event ID 41 restart cases is worth a read so you know what you’re looking at.

Back Off Overclocks And Memory Profiles For A Test

If you’ve enabled XMP/EXPO, tuned the CPU, or pushed a GPU overclock, return to stock for a day. Marginal stability often shows up as sudden reboots long before you see clear errors.

Do The “Boring” Cable And Outlet Checks

• Reseat the 24-pin motherboard power plug and the CPU 8-pin (or 4+4) plug.
• Reseat the GPU and its PCIe power plugs.
• Test a different wall outlet and skip cheap power strips for one evening.
• Unplug extra USB devices for a test: hubs, capture cards, external drives.

A half-seated connector can mimic a failing PSU. This quick reset clears that out.

What The Restart Style Usually Means

Try to sort your restarts into one of these buckets. Each bucket narrows the list.

Blue Screen Then Reboot

This is a Windows crash. Common causes include drivers, unstable RAM, storage faults, and kernel-level tools like some anti-cheat or monitoring apps. If a driver name shows on the blue screen, start there.

Black Screen And Instant Reboot

This often points to power delivery or a thermal safety shutdown. A PSU can dip under load for a split second and the PC simply restarts. Overheating can also trigger a hard shutdown that looks like a quick reboot.

Freeze First, Then Reboot

Hard locks can be RAM instability, GPU driver hangs, or storage timeouts. Logs plus one-at-a-time stress testing is the fastest way to separate them.

Software Triggers That Can Feel Like Hardware

Software is still a top cause of random restarts, especially after updates. The goal here is to remove variables cleanly.

Display Driver Trouble

GPU drivers sit deep in the system. If restarts began after a display driver update, treat that update as a lead.

• Roll back the display driver in Device Manager for a quick test.
• If that helps, do a clean driver install so you’re not stacking new files on old ones.

NVIDIA publishes a step-by-step clean install checklist that covers removing the old driver and reinstalling a fresh package. NVIDIA clean driver install steps works as a simple playbook even when your install didn’t fail.

Third-Party Tuning And Overlay Apps

RGB suites, fan apps, overlay recorders, and “boost” tools can hook into drivers and services. If you’ve got several running at startup, cut back for a week. Keep the ones you trust and remove the rest, one at a time, until stability returns.

Fast Startup And Sleep Edge Cases

Fast Startup mixes shutdown with hibernation. On some systems, that hybrid state can stack small glitches until a restart happens at a bad moment. Try a true power cycle: shut down, unplug for 30 seconds, then boot. If that improves things, turn off Fast Startup for a while and compare behavior.

System File Damage And Disk Errors

When system files are damaged, crashes can show up in random places. Use built-in tools first.

• Run sfc /scannow in an elevated Command Prompt.
• Then run DISM /Online /Cleanup-Image /RestoreHealth.

If restarts happen during big installs or large file copies, storage can be involved. Check for a loose SATA cable, a flaky external drive, or an NVMe that isn’t seated fully.

Hardware Faults That Commonly Cause Surprise Restarts

If software checks don’t change the behavior, shift to hardware. These checks don’t need special equipment.

Power Supply And Power Delivery

A PSU that can’t hold steady output during spikes can reboot the system with no warning. If restarts line up with gaming or GPU-heavy work, power delivery jumps near the top of the list.

• Use separate PCIe power cables to the GPU when your PSU has that option, not a single daisy-chained lead.
• Skip adapters that split one connector into two PCIe plugs.
• If Event ID 41 shows no bug check data, treat power and thermals as the first branch to test.

Thermal Shutdowns

Heat-driven restarts often follow a pattern: heavy load, fans ramp, then the system drops. Clean dust from filters and heatsinks, confirm fans spin freely, and check that the CPU cooler is mounted tight. On laptops, test on a hard surface with clear airflow.

RAM Errors

RAM faults can pass casual use and then crash at random. Start with the built-in Windows Memory Diagnostic, then move to one-stick testing if you still crash.

Microsoft’s guide shows how to run the memory test and where to find results after reboot. Windows Memory Diagnostic steps gives the exact flow. If errors appear, test one module at a time and swap slots to rule out a bad slot.

GPU Instability

A GPU can crash from heat, driver trouble, unstable power, or a factory overclock that’s marginal in your case. A fast test is to lower the GPU power limit or reduce the clock slightly and see if reboots stop during the same workload.

BIOS Settings

If restarts began after BIOS changes, load BIOS defaults and retest. If that fixes it, reapply your settings one by one until the fault returns. That pinpoints the setting that pushed the system over the edge.

A Diagnostic Order That Keeps Tests Clean

Random restarts get messy when you change ten things at once. Use this order. It keeps each test meaningful.

Step 1: Set A Stable Baseline

• Stock CPU and RAM settings in BIOS.
• Auto-restart after system error turned off.
• Startup apps trimmed to the ones you trust.

Step 2: Confirm If Windows Thinks It Crashed

Use the System log around the restart time. Planned restarts often show Event ID 1074. Unclean shutdown markers often show Event ID 41 or Event ID 6008. That split steers your next move.

Step 3: Stress One Part At A Time

• CPU-heavy load triggers reboot: check CPU cooling, BIOS settings, VRM airflow.
• GPU-heavy load triggers reboot: check PSU, GPU power cables, GPU temps, driver state.
• Only mixed load triggers reboot: suspect PSU transient response or case airflow limits.

Step 4: Check Memory In Layers

Run Windows Memory Diagnostic first. If it’s clean but the PC still restarts, test one stick at a time. Swap slots too. This is slow, but it turns “random” into a clear pass/fail.

Step 5: Decide On A Part Swap

When power is the leading suspect, the strongest test is swapping in a known-good PSU. When RAM is the lead, one-stick testing gives the answer. When neither changes anything, the motherboard and CPU become the main suspects.

Fixes That Tend To Stick Once You’ve Found The Cause

After you narrow the culprit, pick the matching fix and keep the rest of the system stable while you confirm the result.

Power Fixes

If the PSU is old, under-sized, or from a weak brand, swapping it is often the clean fix. On modular PSUs, never mix cables across models. Use only the exact cable set for that unit.

Thermal Fixes

Dust-cleaning and a proper cooler mount solve a lot of “it only restarts when I play” cases. If your case has poor intake airflow, test with the side panel off for ten minutes under load. If stability improves, airflow is part of the problem.

Driver Fixes

When a clean driver install stops the reboots, keep the system lean. Fewer overlays, fewer tuning tools, fewer “helper” apps. Stability loves boring setups.

Memory Fixes

If XMP/EXPO triggers restarts, drop the memory speed one step or run stock settings. It’s better to lose a small slice of performance than to lose work to surprise reboots.

When To Stop And Get Hands-On Repair Help

• You see heat damage, melting, or smell burning at a connector.
• The PC restarts even while sitting in BIOS with no OS loaded.
• Restarts began right after a liquid spill.
• You tested with known-good PSU and RAM and it still restarts.

At that stage, the fastest path is bench testing with spare parts. The aim stays the same: isolate the failing part without risking other components.

Send us your feedbackTell us what you thought about this post

Name * Email *

Your comment *

Quick check — what is …? *

Send feedback