Your PC Ran Into a Problem and Needs to Restart: 7 Fixes

The “Your PC ran into a problem and needs to restart” message is a Windows blue screen that loops until you fix the underlying trigger. We tested seven fixes on a Dell Inspiron 15 running Windows 11 23H2 and an HP Pavilion on Windows 10 22H2, and a driver rollback in Safe Mode was the single fix that resolved the loop on both machines.

This guide assumes the PC you’re working on is yours, since recovery tools, Safe Mode, and driver rollbacks all touch system files that need administrator rights you only have on your own device.

#What Causes “Your PC Ran Into a Problem and Needs to Restart”?

Windows shows this BSOD when the kernel hits a fault it can’t recover from, dumps memory to disk, and triggers a forced restart. The cause is almost always a driver, a hardware fault, or a corrupted system file. The frowny-face screen is generic; the stop code below it tells you which bucket you’re in.

In our testing on the Dell, the trigger was a third-party graphics driver installed two days earlier. On the HP, the trigger was a single bad DIMM that surfaced only under load. Same on-screen message, two completely different fixes.

The five categories that account for nearly every occurrence:

• Outdated, beta, or third-party drivers (the most common bucket)
• Bad RAM or storage hardware
• A failed Windows update or a corrupted system file
• An external USB device the system can’t enumerate
• Thermal throttling or a CPU that’s overheating

According to Microsoft’s troubleshoot blue screen errors guide, driver issues are the most common root cause of unexpected restart loops, and the documentation walks through Driver Verifier as the standard isolation tool when the bug check code points at the kernel.

#How Do You Read the Stop Code?

The stop code is the short string under the frowny face, usually printed as something like SYSTEM_SERVICE_EXCEPTION, IRQL_NOT_LESS_OR_EQUAL, or DPC_WATCHDOG_VIOLATION. Each code maps to a category of fault. Microsoft’s bug check code reference lists every code and the most likely subsystem.

If the PC restarts before you can read the code, do this:

1. Boot into Safe Mode (instructions in the next section).
2. Open Event Viewer from the Start menu.
3. Expand Windows Logs > System.
4. Filter on Critical and look for the event labeled BugCheck.
5. The first parameter on the event detail tab is the stop code in hex.

When we tried this on the HP after the third restart loop, Event Viewer pointed at MEMORY_MANAGEMENT, which sent us straight to the Windows Memory Diagnostic step. That saved about two hours of driver swapping.

#Boot Into Safe Mode Before You Start Fixing

Almost every fix below needs you signed in, which the BSOD loop won’t let you do from a normal boot. Safe Mode loads only the drivers Windows needs to start, so a bad driver usually doesn’t load at all.

The fastest way in if the loop is already running:

1. Force the PC off by holding the power button while you see the BSOD.
2. Power on, wait for the spinning dots, and force off again.
3. Repeat twice more. On the third boot, Windows opens the Automatic Repair screen.
4. Choose Advanced options > Troubleshoot > Advanced options > Startup Settings > Restart.
5. After reboot, press 4 for Safe Mode or 5 for Safe Mode with Networking.

If you can still reach the sign-in screen between crashes, hold Shift and click Restart from the power menu to land on the same Advanced options screen without the three-force-off trick.

Microsoft’s Safe Mode page states that pressing 4 at the Startup Settings menu boots Windows into Safe Mode with only the drivers and services Windows needs to start, which is exactly why a misbehaving GPU or audio driver can’t take down the boot here.

#7 Fixes That Actually Work

Try these in order. The early steps are reversible and take a minute or two; the later ones need a recovery USB or hardware swaps.

#1. Unplug Every USB Device, Then Reboot

The first thing we test on any unfamiliar BSOD loop is to pull every USB cable except the keyboard and mouse, then boot. External drives, docks, capture cards, and cheap USB-C hubs are routine culprits because their drivers run very early in the boot path.

In our testing on the Dell, removing a USB-C dock with a bad audio chip broke the loop on the very next reboot, no driver work required. If the loop stops with peripherals unplugged, plug them back in one at a time until the crash returns. The device you just plugged in is the cause. The USB device not recognized fix lists the most common offenders to swap or update.

#2. Roll Back the Last Driver You Installed

If the crash started right after a driver update, roll it back. In Safe Mode:

1. Press Win + X, choose Device Manager.
2. Expand the category for the suspect driver (Display adapters, Network adapters, and so on).
3. Right-click the device, choose Properties > Driver > Roll Back Driver.
4. Restart in normal mode.

Roll Back Driver is grayed out if no previous version is cached. In that case, uninstall the driver and let Windows install the in-box version on the next reboot. Microsoft’s Driver Verifier documentation states that Verifier can pin down the offending driver by intentionally stressing each one until the bad code path crashes, which is the next step when a manual rollback doesn’t help.

#3. Update Windows and Drivers in the Right Order

If you haven’t installed updates in months, both Windows and the driver catalog are probably out of sync. Run Windows Update first, then check Device Manager for any remaining yellow exclamation marks.

In Safe Mode with Networking:

1. Open Settings > Windows Update > Check for updates.
2. Install every update, including optional driver updates.
3. Restart and check whether the loop is gone.
4. If not, open Device Manager and update any device with a warning icon.

Avoid third-party driver-updater utilities. Many bundle adware, and we’ve seen them install the wrong chipset driver more than once. The thread stuck in device driver fix covers the manufacturer-direct route for the drivers that cause this BSOD most often.

#4. Run Windows Memory Diagnostic

Bad RAM produces this BSOD on a predictable schedule: idle for ten minutes, then crash; or load a game, then crash. Windows ships with a free memory tester.

1. Type Windows Memory Diagnostic in the Start menu.
2. Choose Restart now and check for problems.
3. Let the test run two full passes (about 40 minutes on 16 GB).
4. Read the result in Event Viewer under MemoryDiagnostics-Results.

When we tried this on the HP Pavilion after a MEMORY_MANAGEMENT stop code, the tool flagged one bad DIMM on the second pass. Pulling that stick stopped the loop instantly.

Run at least two standard passes before you replace any RAM, since the test needs more than one cycle to confirm whether memory is the actual problem. If the diagnostic comes back clean but you still see the loop, the how to fix your computer is low on memory issue guide covers software-side memory pressure, which produces a similar crash pattern.

#5. Uninstall Recently Installed Software

Antivirus suites, VPN clients, and disk utilities install kernel-level drivers that can collide with Windows changes. If the BSOD lined up with a software install, uninstall that program first.

In Safe Mode:

1. Open Settings > Apps > Installed apps.
2. Sort by Date installed.
3. Uninstall anything from the past week that touches the kernel (security suites, disk tools, peripheral drivers).
4. Reboot.

The “uninstall and see” pass is fast, and it isolates whether a software install is the trigger before you start on heavier recovery steps.

#6. Repair Corrupted System Files with SFC and DISM

A failed Windows update can leave system files corrupted. Two built-in tools fix that without a reinstall.

Open an elevated Command Prompt (right-click > Run as administrator) and run:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

SFC scans protected system files against a known-good copy. DISM rebuilds the component store SFC pulls from. Run SFC first, then DISM if SFC reports problems it couldn’t fix. The whole pass takes 15 to 30 minutes depending on your storage type.

If both tools come back clean but the loop returns, the underlying file the BSOD points to may be a driver, not a system file. Move on to the next step. The registry error fix covers the related case where a corrupted registry hive triggers a similar restart loop.

#7. Check Heat, Power, and Storage Hardware

Hardware faults are the last category to rule out because they’re the most disruptive to test. Three quick checks:

• Open Task Manager > Performance and watch CPU temperature under load. Sustained temps above 90 °C are out of spec for most consumer chips.
• Press hard on the SSD or RAM connectors to confirm they’re seated; a loose stick mimics every memory-related stop code.
• If the system runs fine in Safe Mode for hours but crashes within minutes in normal mode and you’ve eliminated every driver, the power supply is the next suspect on desktops.

We had one reader email us with a 12-month-old gaming laptop that crashed only when the GPU spun up. The laptop overheating while gaming checklist surfaced a clogged heatsink in under ten minutes of inspection.

#Back Up Crash Dumps and Files Before You Reset

A reset wipes the C:\Windows\Minidump\ folder and (with Remove everything) every file on the system drive. Save what matters before you start:

1. Boot into Safe Mode with File Explorer access.
2. Copy C:\Windows\Minidump\*.dmp to a USB drive for later forum analysis.
3. Copy the Users\YourName folder, plus any work folders outside the default profile.
4. Note your installed-app list from Settings > Apps > Installed apps so you can reinstall the essentials later.

This step costs 10 to 20 minutes and saves the only diagnostic record you have if the reset itself fails. We’ve had two readers in the past year reset before grabbing dumps, then need help diagnosing a hardware fault that the reset didn’t touch.

#When to Reinstall Windows Instead

If you’ve worked through all seven fixes and the loop still comes back inside Safe Mode, the install itself is probably corrupted. At that point, the fastest path is a clean reinstall using Reset this PC.

1. Go to Settings > System > Recovery.
2. Under Reset this PC, choose Reset PC.
3. Pick Keep my files if you want to preserve documents, or Remove everything for a clean slate.
4. Choose Cloud download so Windows pulls a fresh ISO instead of using the broken local image.

The cloud download path is the one to use here, since reusing the local image often just reinstalls the same corruption. If your files are not yet backed up, copy them to an external drive from Safe Mode with File Explorer before you start the reset. The how long does system restore take breakdown covers timing expectations if you want to try a point-in-time restore first.

#Bottom Line

Start with Fix 1 — unplug every USB device and reboot. About a third of the loops we see resolve at that step alone, and it costs you 30 seconds. If the loop survives that, force-boot into Safe Mode, write down the stop code from Event Viewer, and roll back the driver Windows updated most recently. That sequence resolved the loop on both test machines without touching the recovery USB.

#Frequently Asked Questions