PC Restarts Randomly? Fix Guide

A computer that randomly restarts is usually reacting to one of five things: unstable power, overheating, unstable RAM or overclocking, a driver/update crash that reboots before the blue-screen message is visible, or malware/unwanted software that added a bad driver, miner, scheduled task, or startup component. The safest path is to capture evidence first: check Event Viewer for Kernel-Power Event ID 41, disable automatic restart on system failure, note whether the reboot happens under load or while idle, then test power, temperature, memory, drivers, storage, and malware signs in that order.

If the PC restarts with no warning, do not keep forcing games, benchmarks, or heavy GPU tasks until temperatures and power delivery are safe. Repeated hard restarts can corrupt files, damage active downloads, and make a failing drive worse. If the reboot started after a fake update, cracked installer, unknown optimizer, browser redirect, or security alert, keep malware in the checklist instead of treating it as an afterthought.

Quick check: match the symptom to the likely cause

Use this restart triage map as the short version of the guide: Event ID 41 tells you Windows saw an unclean restart, then the last useful clue decides whether to test power, heat, RAM, drivers, or malware signs first.

Before you change hardware, capture the restart evidence

Windows often hides the useful error because it is configured to restart automatically after a system failure. Temporarily turn that off so the next crash can show a stop code instead of rebooting too fast to read.

1. Press Win + R, type sysdm.cpl, and press Enter.
2. Open Advanced -> Startup and Recovery -> Settings.
3. Under System failure, clear Automatically restart, then click OK.
4. After the next crash, write down the stop code, driver name, or exact message.

Then open Event Viewer -> Windows Logs -> System. A critical Kernel-Power, Event ID 41 entry confirms that Windows detected an unclean restart, but it does not prove the root cause by itself. Look at the warnings and errors immediately before the Event 41 entry: WHEA-Logger often points to hardware, BugCheck points to a Windows stop error, Display driver errors point to GPU/driver problems, and User32 Event ID 1074 usually means a planned restart.

What the Event Viewer clue means

1. Check power delivery and the PSU

Sudden restarts with no blue screen often mean the PC briefly lost stable power. This can come from the power supply unit, a loose cable, an overloaded power strip, a weak laptop charger, or a motherboard connector that was not fully seated after a build or upgrade.

• Plug the PC directly into a known-good wall outlet for a test. Skip cheap extension cords and overloaded strips.
• Reseat the 24-pin motherboard cable, CPU power cable, GPU PCIe power cables, and the power cable going into the PSU.
• If the restart happens only under GPU/CPU load, compare the PSU wattage and age against the actual CPU/GPU combination.
• For laptops, test with the original charger, then on battery only if the battery is safe and removable in normal use.
• Stop and use a repair shop if you smell burning, see arcing, hear crackling, or find swollen capacitors.

Do not open a PSU casing. The capacitors inside can remain dangerous after shutdown.

2. Rule out overheating

Modern CPUs and GPUs protect themselves by throttling or shutting down when temperatures cross safe limits. A desktop with dust-clogged heatsinks, a laptop with blocked vents, dried thermal paste, or a failed fan can restart suddenly during games, video export, virtual machines, or even browser workloads.

Check temperatures while the computer is idle and again under the workload that usually triggers the restart. If temperatures climb rapidly, clean dust from vents and heatsinks, confirm all fans spin, improve airflow around the case, and remove aggressive overclocking profiles. Laptops should be tested on a hard flat surface, not on bedding or fabric.

3. Test RAM, XMP/EXPO, and overclocking

Unstable memory can look like random Windows restarts, browser crashes, corrupted downloads, game crashes, or a reboot with no useful message. This is common after enabling XMP/EXPO, mixing RAM kits, moving a PC, or updating BIOS defaults.

1. Turn off CPU/GPU overclocking and return BIOS power settings to default.
2. Temporarily disable XMP/EXPO and test the PC at standard memory speed.
3. Reseat RAM sticks and use the motherboard manual’s recommended slots.
4. Run Windows Memory Diagnostic or a longer memory test if restarts continue.
5. If the PC has multiple RAM sticks, test one stick at a time only if you are comfortable working inside the case.

If disabling XMP/EXPO stops the restarts, the memory kit may still be healthy; it may simply need a lower speed, newer BIOS, or adjusted voltage/timings from the motherboard vendor’s compatibility list.

4. Check drivers, Windows Update, and recent changes

If restarts began after a driver, BIOS update, GPU utility, antivirus change, or Windows feature update, treat the timing as evidence. Look in Settings -> Windows Update -> Update history, and compare the install date with the first restart.

Use these checks in order:

1. Install pending Windows and driver updates if the PC is stable long enough.
2. Roll back a recently updated GPU, chipset, storage, or network driver from Device Manager if the timing matches.
3. Uninstall the newest optional driver/update only when the restart started immediately after it.
4. Boot into Safe Mode. If the problem disappears there, suspect a third-party driver, startup app, security product conflict, or service.
5. Use a clean boot to isolate startup software before reinstalling Windows.

5. Repair system files and check storage

Corrupted system files and failing storage can trigger restarts, especially after repeated hard shutdowns. Open Command Prompt or Windows Terminal as administrator and run:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
chkdsk C: /scan

If Windows reports disk errors, back up important files before running repair commands that require a reboot. A drive that repeatedly disconnects, clicks, disappears from BIOS, or shows growing SMART errors should be treated as a hardware problem, not just a Windows problem.

6. Scan for malware and unwanted startup persistence

Malware is not the most common cause of instant power-style restarts, but it is relevant when the reboot comes with browser redirects, unknown scheduled tasks, strange PowerShell windows, new startup entries, fake update prompts, security alerts, or high CPU/GPU load after an unknown download. Some unwanted programs install unstable drivers, miners, proxy settings, browser extensions, or startup persistence that can make the system crash under load or reboot after cleanup.

1. Disconnect from suspicious sites and stop using cracked installers, fake driver updaters, or unknown “optimizer” tools.
2. Open Task Manager -> Startup apps and disable unfamiliar entries while you investigate.
3. Check Task Scheduler for recently created tasks with random names, PowerShell commands, or files in AppData, Temp, or browser profile folders.
4. Run a full security scan before deleting random files manually. Removing only the visible process may leave a loader, scheduled task, service, browser change, or bundled module that recreates the symptom.
5. After cleanup, change passwords only from a clean device if you found an infostealer, browser password theft, suspicious account activity, or an executable that ran from a game/mod/crack download.

Gridinsoft Anti-Malware is useful in this lane because it checks detections, hidden files, startup entries, scheduled tasks, bundled apps, browser changes, and persistence together instead of asking you to guess which leftover is safe to delete.

Related Gridinsoft guides can help when the restart is only one symptom of a broader infection: PowerShell outbound connection blocked, fake Chrome update terminal popups, and infostealer cleanup after downloading a game or mod.

If the computer is stuck in a restart loop

If the PC cannot stay on long enough for normal troubleshooting, enter the Windows Recovery Environment. From the sign-in screen or Start menu, hold Shift while choosing Restart. If Windows cannot boot normally, interrupt startup three times to reach recovery options, then try Startup Repair, System Restore, Uninstall Updates, or Startup Settings -> Safe Mode.

Before using Reset this PC, save important files if the drive is still readable. A reset can fix Windows corruption, but it will not repair a failing PSU, overheating GPU, unstable RAM, or dying SSD.

Best troubleshooting order

1. Back up important files if the PC stays on long enough.
2. Disable automatic restart so the next crash can show a stop code.
3. Check Event Viewer and Reliability Monitor for the last event before the restart.
4. Test wall power, cables, PSU behavior, laptop charger, and battery.
5. Check CPU/GPU temperatures and clean dust or blocked vents.
6. Undo overclocking and test RAM without XMP/EXPO.
7. Review Windows Update, drivers, Safe Mode, and clean boot behavior.
8. Run SFC, DISM, CHKDSK, and a malware scan.
9. If hardware signs remain, stop guessing and test with known-good parts or a repair shop.

FAQ

References

1. Microsoft Learn. “Advanced troubleshooting for Event ID 41: The system has rebooted without cleanly shutting down first.” Microsoft, updated 2026, accessed June 20, 2026. https://learn.microsoft.com/en-us/troubleshoot/windows-client/performance/event-id-41-restart
2. Microsoft Support. “Troubleshooting Windows unexpected restarts and stop code errors.” Microsoft, accessed June 20, 2026. https://support.microsoft.com/en-gb/windows/resolving-blue-screen-errors-in-windows-60b01860-58f2-be66-7516-5c45a66ae3c6
3. Microsoft Support. “Recovery options in Windows.” Microsoft, accessed June 20, 2026. https://support.microsoft.com/en-us/windows/recovery-options-in-windows-31ce2444-7de3-818c-d626-e3b5a3024da5