Fix “Your PC Ran Into a Problem” Restart Loop

“Your PC Ran Into a Problem and Needs to Restart” means Windows has crashed with a stop error and cannot finish starting. Record the stop code, disconnect unnecessary devices, and use Windows Recovery Environment to try Startup Repair, Safe Mode, update removal, or System Restore before considering a reset. Back up important files first when possible, and investigate failing RAM, storage, overheating, or other hardware if recovery tools do not fix the loop.

What to do when the PC keeps restarting before Windows loads

You may see the blue-screen message for only a moment before the computer restarts. If Windows reaches the sign-in screen, write down the stop code and any named file, such as CRITICAL_PROCESS_DIED, INACCESSIBLE_BOOT_DEVICE, or ntfs.sys. These clues can point to a driver, damaged system files, storage trouble, or another cause.

Your PC ran into a problem and needs to restart. We're just collecting some error info, and then we'll restart for you.

The message appears when Windows encounters a stop error during startup or normal operation. Let the computer restart once. If it returns to the same screen, unplug nonessential USB devices such as external drives, printers, webcams, docking stations, and USB hubs. Leave the keyboard, mouse, monitor, and power connected. A faulty peripheral or removable drive can interfere with startup.

Use Windows Recovery Environment (WinRE) instead of repeatedly holding the power button down. Windows often opens WinRE automatically after several failed starts. If it does not, turn the PC on and, when the Windows logo or manufacturer logo appears, hold the power button until it turns off. Repeat this interruption only as needed for Windows to show Preparing Automatic Repair or Choose an option. Once recovery appears, stop forcing shutdowns.

From the recovery screen, select Advanced options. If you can reach the sign-in screen but Windows crashes before the desktop, hold Shift while selecting Restart, then choose Troubleshoot and Advanced options. You may be asked for an administrator password. If BitLocker is enabled, some recovery actions will require its recovery key.

If the PC never reaches WinRE, use the manufacturer’s recovery key or boot-menu key and select a Windows installation or recovery USB. Create that USB from another working Windows PC using Microsoft’s official installation media, then choose Repair your computer rather than installing immediately. Check the BIOS or UEFI boot order and confirm that the internal drive is detected. Do not change storage-controller modes casually; changing AHCI, RAID, or similar settings can create another boot failure.

Which fix applies when the loop started after an update, driver, app, or hardware change

These steps apply to supported Windows 10 and Windows 11 installations, although menu names can vary by build and manufacturer. Recovery actions normally require an administrator account. A restart is expected after most fixes, and you should back up important files before making changes whenever Windows starts long enough to let you do so.

Before opening a repair tool, note the stop code, the date the loop began, and anything that changed immediately beforehand. Also disconnect nonessential peripherals. If Windows starts even briefly, copy important files to another drive or cloud storage. Do not format the disk or reset Windows while files exist only on that PC.

The table is a starting point, not a diagnosis:

If the drive is encrypted with BitLocker, find the recovery key from another device through the Microsoft account or organization that manages the PC before starting recovery work. The key is a long numerical code; your normal Windows password is not a substitute.

Recovery tools can change system files, drivers, updates, or settings, so keep the backup step ahead of anything that could affect the drive. System Restore does not normally remove personal documents, but it can remove programs, drivers, and updates installed after the selected restore point.

How to break the loop without deleting your files

Work through these options in order. They are arranged from generally reversible to more involved. Open each tool from Troubleshoot > Advanced options in WinRE unless a step says otherwise.

Try Startup Repair first

Startup Repair checks common problems that prevent Windows from loading, including damaged boot configuration data and some startup files. It does not intentionally delete personal files.

1. Select Startup Repair.
2. Choose your Windows account and enter its password if prompted.
3. Let the scan finish and restart when asked.

Expected result: Windows reaches the sign-in screen or desktop without returning to the blue-screen loop. If Startup Repair says it could not repair your PC, return to Advanced options and try Safe Mode or System Restore. That result does not prove the hardware is bad; it means this automated repair did not resolve the startup problem.

Start Windows in Safe Mode

Safe Mode loads Windows with a limited set of drivers and services. If it works, a recently installed driver, service, or application becomes more likely than a basic boot failure.

1. Select Startup Settings.
2. Select Restart.
3. Press 4 or F4 for Safe Mode, or 5 or F5 for Safe Mode with Networking.
4. Sign in and remove the most recent app or driver if the problem began after one was installed.

For a driver, open Device Manager, expand the relevant category, right-click the device, and choose Properties > Driver. Use Roll Back Driver when available. Otherwise choose Uninstall Device, restart normally, and allow Windows to reinstall a compatible driver. Focus first on graphics, storage, chipset, and antivirus-related drivers.

Expected result: Windows starts normally after the change. If Safe Mode also crashes, or the same stop code appears there, continue with update removal, System Restore, and offline checks rather than repeatedly attempting normal startup.

Remove a recent Windows update

From WinRE, select Uninstall Updates, then try Uninstall latest quality update. This usually removes a recent small Windows update while leaving personal files in place. If the loop began immediately after a major version upgrade and the option is offered, Uninstall latest feature update may be relevant, but it can be unavailable after the rollback period.

Expected result: Windows starts after the update is removed. If the uninstall fails, use System Restore or Safe Mode. Do not remove updates at random; a security update may have addressed a real vulnerability, so reinstall it later only after confirming that Windows and the affected driver are stable.

Use System Restore

Select System Restore in Advanced options and choose a restore point from before the loop began. System Restore changes Windows system files, drivers, registry settings, and installed programs, but normally leaves personal files such as documents and photos alone. Review the affected programs list before confirming.

Expected result: Windows starts with the earlier configuration. If no restore points exist, the restore fails, or the loop remains, move to offline system checks.

Run offline system checks

From Advanced options, open Command Prompt. The Windows drive may not be C: in recovery. Find it by checking which volume contains the Windows folder.

dir C:\Windows
dir D:\Windows
dir E:\Windows

Use the letter that shows the Windows folder in the following commands. Replace C: if recovery assigned a different letter.

chkdsk C: /scan
sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

chkdsk checks the file system and sfc checks protected Windows files against the offline installation. The scan may take time, especially on a hard disk. Expected results include a message that no integrity violations were found or that corrupted files were repaired. If the disk check reports unreadable sectors, repeated errors, or cannot complete, treat that as a possible storage failure and back up data before more repairs.

If the loop began after an interrupted update, you can also try the Deployment Image Servicing and Management repair from a normal administrator Command Prompt after Windows starts. Avoid guessing at advanced boot commands or deleting boot files; an incorrect offline command can make recovery harder.

How to confirm Windows is stable again

After a repair, choose Continue in WinRE or select Restart. Let Windows start normally without reconnecting every peripheral at once. Sign in, use the PC normally, and restart it again to check whether it remains stable.

Open Reliability Monitor from the Start menu by searching for View reliability history. Look for red failure markers on the date of the crash and open them to see the application, Windows failure, or hardware error recorded. In Device Manager, look for warning icons and inspect recently changed devices. A driver that appears normal in Device Manager can still be involved, so compare its installation date with the beginning of the loop.

If Windows is stable, create a current backup and then install pending Windows updates one group at a time. Obtain hardware drivers from the computer or component manufacturer rather than using random driver-download sites. Restart after a significant driver or update so you can identify a change if the crash returns.

If the stop code returns, test memory and storage. Run Windows Memory Diagnostic by searching for it in Start, choosing Restart now and check for problems, and reviewing the result after Windows starts. For a more thorough memory test, use the diagnostic tool recommended by the computer or memory manufacturer. If it reports errors, test modules individually only if you are comfortable opening the PC and following its service instructions.

For storage, review the result of chkdsk, check the drive’s health with the manufacturer’s diagnostic utility, and pay attention to slow startup, missing files, clicking noises from a hard disk, or repeated disk-related stop codes. Hardware tests should be run after backing up important files where possible.

If the PC becomes unusually hot, shuts off under load, or shows different stop codes on different starts, include overheating and other hardware faults in the investigation rather than treating the problem as a Windows-only failure.

When the loop points to failing hardware or requires a reset

A software repair is less likely to be enough when the computer crashes in Safe Mode, reports memory errors, logs disk failures, becomes unusually hot, shuts off under load, or fails to recognize its boot drive. Different stop codes on different starts also raise concern about hardware. A new component that immediately caused the loop is another strong clue.

Power the PC off, disconnect it from mains power, and return it to the previous hardware configuration if you can do so safely. For a laptop or a device under warranty, use the manufacturer’s service process rather than opening it.

If WinRE tools fail, back up files before attempting more invasive work. You can remove the drive and connect it to another computer with a suitable adapter, boot from a trusted Windows installation or recovery USB, or ask a repair service to copy the data. BitLocker-encrypted data cannot be read without the recovery key. If the PC belongs to an employer or school, its administrator may control the key and recovery options.

If the computer never reaches WinRE, try the manufacturer’s recovery key or boot-menu key and select a Windows installation or recovery USB. Create that USB from another working Windows PC using Microsoft’s official installation media, then choose Repair your computer rather than installing immediately. Check the BIOS or UEFI boot order and confirm that the internal drive is detected. Do not change storage-controller modes casually; changing AHCI, RAID, or similar settings can create another boot failure.

Reset this PC can remove applications and, depending on the option you choose, personal files. Before using it, copy files elsewhere, record required license information, and make sure you have the BitLocker recovery key.

Use Reset this PC only after recovery tools, Safe Mode, update removal, System Restore, and hardware checks have either failed or shown that the Windows installation is beyond practical repair. Keep my files is less destructive than Remove everything, but it still removes installed programs and settings, and it is not a substitute for a backup. If reset fails, the drive may be damaged or the installation media may be faulty; arrange professional repair or replace the failing component instead of repeating the reset.

Conclusion

Start with WinRE and the least disruptive repair that matches the timing of the crash. If Windows becomes stable, back up your files and reintroduce updates, drivers, and peripherals carefully. If recovery tools fail or diagnostics report memory, storage, heat, or other hardware problems, protect the data first and arrange repair or a clean reinstall rather than forcing more restarts.

Frequently Asked Questions

Will Startup Repair delete my files?

Startup Repair is designed to repair startup problems without deleting personal files. Back up important data first when possible, because an underlying drive failure can make any recovery operation risky.

What if I do not know my BitLocker recovery key?

From another device, check the Microsoft account associated with the PC or contact the organization that manages it. If the device is managed by work or school, an administrator may have stored the key. Without the key, encrypted files may not be recoverable through WinRE.

Can a bad driver cause this restart loop?

Yes. Graphics, storage, chipset, and security-software drivers can trigger repeated stop errors. Start Safe Mode, which loads a smaller set of drivers, then roll back or uninstall the recent driver if Windows remains stable there.