Endless restarts often come from bad drivers, faulty updates, heat, or power issues—use Safe Mode, updates, and hardware checks to stop the loop.
When a desktop or laptop keeps bouncing back to a reboot screen, you lose work right away. The good news: most restart loops trace back to predictable triggers. This guide walks you through fast checks, proven fixes, and a clean order of steps that stop the cycle without guesswork.
PC Keeps Rebooting: Root Causes And Quick Wins
Start with patterns. Note when the restart happens: during boot, right after login, while gaming, or under any heavy load. That timing points you to the likely source.
Common causes include a broken driver, a half-installed update, storage errors, heat throttling, a weak power unit, or a short from a loose cable. A quick action can narrow it fast: boot into Safe Mode, roll back the last change, or watch system temps.
Use this quick map to match the symptom with a likely cause and a first move:
| Symptom | Likely Cause | First Move |
|---|---|---|
| Boot loop before login | Broken update or driver | Safe Mode; uninstall update or driver |
| Restart under load | Heat or power sag | Clean cooling; test temps; test PSU |
| Restart on wake | Driver or sleep state bug | Update BIOS and drivers; change power plan |
| Random restarts idle | Power plan or wake timer | Disable wake timers; check scheduled tasks |
| Blue screen then reboot | Driver or system file | Turn off auto restart; run DISM and SFC |
| USB attached triggers reboot | Faulty device or hub | Remove all peripherals; add back one by one |
Immediate Actions Before Deep Fixes
Back up what you can. If the system stays up for two to three minutes, copy current work to an external drive or a cloud folder. If the loop is instant, use another PC and a USB stick to create a recovery drive so you can pull files later.
Next, check two toggles that mask the real error. Disable automatic restart on crash so you can read the stop code, and enable boot logging. Seeing a stop code or the last loaded driver trims hours from trial and error.
Windows Steps That Stop Restart Loops
Use a stable path. Enter Safe Mode, remove the last app or driver you installed, and see if normal boot returns. If the restart began right after Patch Tuesday, uninstall the latest quality update and pause new updates until the root cause is clear.
If system files are damaged, repair the image and the protected files from a Command Prompt with admin rights. Run DISM to service the component store, then run SFC to verify and repair protected files. When these finish clean, many restart loops end on the next boot. DISM and SFC repair steps explains the exact commands and order.
Check Event Viewer for the first critical event around the time of each restart. Kernel-Power 41 usually points to an abrupt power loss, while a driver crash leaves a trace under System or Application logs. Match the event time with what you were doing to confirm the lead.
Turn off automatic restart on system failure temporarily. This leaves the stop code on screen so you can capture it and search the exact text later. Turn the setting back on once you finish repair so unattended servers can self-recover.
Update device drivers from the vendor, not random driver packs. Start with chipset, storage, graphics, and network. If a specific vendor driver started the loop, roll back to the prior release or use the inbox driver until a fixed build lands.
If the restart loop began during a feature update or after a preview patch, step back to the previous build, or remove the preview. Wait for the stable release notes to confirm the fix before trying again.
Mac Steps To Stop Repeat Restarts
On a Mac, repeated reboots often point to a kernel panic, a buggy extension, or a failing peripheral. Start in safe mode, remove third-party kernel extensions and login items, and install the latest updates. Test with only Apple-made peripherals attached to rule out a bad device. See Apple’s kernel panic guide for safe mode and update steps.
If you see a report that names a specific app or extension, remove it and reboot. If safe mode is stable but normal mode is not, the issue is almost always third-party code. When the Mac restarts during sleep or wake, reset NVRAM and run a hardware test.
Heat And Power Checks
Thermal spikes and weak power rails are classic restart triggers. Dust in a laptop vent or a desktop cooler raises temps under load, and a tired battery or an aging power supply sags when the GPU or CPU draws a surge.
Clean fans and heat sinks, replace dry thermal paste on older desktops, and make sure every power lead snaps in tight. Watch CPU and GPU temps while running a light stress test. If temps climb past safe ranges and the system resets, fix cooling before chasing drivers.
For desktops, swap in a known-good power supply if you can. For laptops, try with the charger only and with the battery only to isolate which half trips the reset.
When To Suspect Malware Or Storage Errors
Malware can wedge a restart cycle by tampering with services or drivers. Run an offline scan from Windows Security or a trusted rescue disk. Remove suspicious startup items and scheduled tasks.
Storage errors can trigger reboots during heavy disk activity. Check SMART data, run CHKDSK on the system volume, and flip to another SATA or NVMe cable if you have one. If the drive shows reallocated sectors or pending sectors, clone it before deeper tests.
Step-By-Step Repair Checklist
Here’s a practical order that works for both Windows and macOS. Work top to bottom; stop when the loop ends.
| Tool | What It Checks | Command Or Path |
|---|---|---|
| DISM and SFC | Windows image and protected files | dism /online /cleanup-image /restorehealth; sfc /scannow |
| Event Viewer | Crash and driver logs | eventvwr.msc; Windows Logs > System |
| Apple Safe Mode | Third-party extensions and caches | Hold Shift on boot; then App Store updates |
Prevention Tips That Stick
Keep a restore point or a Time Machine snapshot before major changes. Update firmware and drivers on a steady cadence. Leave 20–30% free space on the system drive so updates and logs have room. Use a dust filter, keep vents clear, and avoid running high-load tasks on soft surfaces that block airflow.
Keep a small toolkit ready: a USB installer for your OS, a spare SATA or NVMe cable, a can of air, isopropyl wipes, and a thumb drive with your key drivers. When trouble strikes, you can move from theory to action in minutes.
Still Stuck? What To Back Up Before A Reset
If none of the steps work, protect your data, reset, and rebuild clean. Back up the user profile, browser data, password vaults, email archives, game saves, and any license files. After a reset, add apps in batches, testing between each set to catch the culprit fast if the loop returns.
Safe Mode Paths That Work
On Windows, hold Shift while clicking Restart, then choose Troubleshoot > Advanced options > Startup Settings and press the number for Safe Mode with or without networking. If the restart loop blocks that route, interrupt boot three times to trigger Automatic Repair, then choose Advanced options and reach the same menu.
Roll Back Updates And Drivers
From Apps > Installed apps, sort by install date and remove the last items you added. In Device Manager, open Display adapters, Network adapters, and Storage controllers, select the device, and pick Roll Back Driver when available. If a display driver started the loop, use the vendor’s clean-up tool before installing a stable build.
Repair With Commands
Open an elevated Command Prompt. Run:
1) dism /online /cleanup-image /restorehealth
2) sfc /scannow
Reboot after both complete. If SFC finds issues it cannot fix, run DISM again, then SFC once more.
Event Viewer In One Minute
Open Event Viewer and filter the System log by Critical and Error. Note the time and the source, such as Kernel-Power, BugCheck, or a driver name. Double-click an event to read the details, then search for that exact text along with your device model.
Disable Automatic Restart Temporarily
Open System > Advanced system settings > Startup and Recovery. Clear the box for Automatic restart. Leave it off while you test so the stop code stays on screen long enough to grab a photo.
Memory And Disk Tests
Run Windows Memory Diagnostic and let it cycle at least once. For disks, run chkdsk c: /scan first; if it flags problems, schedule chkdsk c: /f for the next boot. On NVMe drives, a firmware update from the vendor can fix power-state errors that look like random resets.
BIOS And Firmware Cleanup
Update the BIOS or UEFI to the latest stable build from your motherboard or laptop maker. Reset to defaults, then set only what you need. Disable fast startup while you test. If your board supports it, switch from a beta firmware to a proven release.
macOS Safe Steps
Shut down, then press the power button and hold it until you see Loading startup options on Apple silicon. Pick your disk, hold Shift, and click Continue in Safe Mode. On Intel models, press and hold Shift right after the chime until you see the login screen. In safe mode, remove login items, test without third-party launch agents, and install system updates.
Peripherals And Extensions
Unplug docks, hubs, and adapters. Test with a basic wired keyboard and mouse only. Remove legacy kernel extensions from /Library/Extensions that came with old hardware or uninstall the matching app. If a crash report names a kext, that file is your first target.
Apple Diagnostics And Reinstall
Run Apple Diagnostics by holding D on Intel or pressing and holding the power button until Options appears on Apple silicon, then pick Diagnostics. If hardware passes and the Mac still cycles, reinstall macOS over the top of your data. This refreshes system files without touching documents.
Backup And Recovery Ready
Keep a recent image or Time Machine backup, a second admin account, plus a thumb drive with network and storage drivers. That combo cuts downtime during a reset.
When A Reset Makes Sense
If you still hit the loop after repairs and hardware checks, a clean install saves time. Export browser bookmarks and passwords, back up email PST or mailbox files, and deactivate licensed apps that tie to hardware IDs. After the reset, install drivers, run updates, and then bring apps back in small groups with a quick reboot between each set. If the loop returns right after one group, you just found your culprit.
Recent Driver And Update Quirks
Some restart loops come from sound or graphics packages tied to new releases. Audio stacks like Intel SST or display stacks from major GPU vendors have shipped builds that crash under certain power states. If your system started looping right after a feature update or a driver push, pause updates, install the vendor’s previous stable package, and wait for a fixed build. Laptop makers often ship tuned drivers that lag behind the chip vendor release; those tuned builds can be steadier on portable models.
What Not To Do
Do not run random “driver updater” tools, registry cleaners, or BIOS betas while the system is unstable. Change one thing at a time and test between each change.