“Your PC ran into a problem and needs to restart” is the message Windows 11 shows on every blue screen — it’s the friendly face of a crash, and it deliberately hides the technical details. The actual diagnosis lives in the small print at the bottom: the stop code (like SYSTEM_SERVICE_EXCEPTION) and sometimes a failing driver name. Everything useful is in that small print; the big message is just decoration.

So the fix for “your PC ran into a problem” is a two-stage process: first capture the real error, then fix that error. This guide covers both stages — how to see the hidden details, the most common stop codes behind this message, and the fix order for each. Think of it as the front door to our blue screen troubleshooting hub , which routes each specific stop code to its dedicated fix.

Why this happens

  • It’s a generic wrapper, not a specific error: This message appears for all ~300 Windows stop codes. The cause is whatever the hidden stop code says — driver bug, bad RAM, failing drive, corrupt files.
  • Automatic restart hides the details: By default Windows reboots seconds after showing this screen, so most people never see the stop code underneath.
  • The most common underlying causes: Buggy drivers (graphics, network, storage), failing RAM, Windows Update conflicts, corrupted system files, and overheating — the usual blue screen suspects.
  • It can appear once or in loops: A one-off crash after a driver update is minor; the same message on every boot indicates a boot-level failure needing recovery-environment repairs.
  • The QR code isn’t very helpful: The blue screen includes a QR code linking to a generic Microsoft support page. It rarely identifies your specific problem — the stop code does.
  • Dump files capture what the screen doesn’t: Even if the screen flashes past, C:\Windows\Minidump holds the technical details of every crash.

How to fix it

Work through these in order — capture the real error first, then fix it.

Fix 1: Disable automatic restart so you can read the error

Stop the screen from vanishing before you’ve read it.

  1. Press Windows + R, type sysdm.cpl, press Enter.
  2. Advanced tab > Settings under Startup and Recovery.
  3. Untick Automatically restart and click OK.
  4. The next crash will hold on the blue screen. Photograph it — the stop code at the bottom is your diagnosis.

If Windows won’t stay booted long enough: force the recovery environment (interrupt boot three times), go to Troubleshoot > Advanced options > Startup Settings > Restart, and press 9 to disable auto-restart for that boot. Our full auto-restart guide covers every method.

Fix 2: Find the stop code after the fact

If the crash already happened and the screen is gone:

  1. Open Event Viewer (Windows + X) > Windows Logs > System.
  2. Look for Error entries from source BugCheck around the crash time — the event text includes the stop code (e.g., 0x0000001a) and sometimes the failing driver.
  3. Alternatively, check C:\Windows\Minidump for the latest .dmp and analyze it with WinDbg (!analyze -v) — the definitive method.
  4. Write down the stop code. Everything from here depends on it. Microsoft’s own blue screen troubleshooting reference is a useful companion if you want the official take.

Fix 3: Match the stop code to its fix

The most common stop codes behind this message and their first moves:

  1. MEMORY_MANAGEMENT or FAULTY_HARDWARE_CORRUPTED_PAGE → test RAM (mdsched.exe, then MemTest86).
  2. IRQL_NOT_LESS_OR_EQUAL or DRIVER_IRQL_NOT_LESS_OR_EQUAL → update or roll back the named driver (usually network or graphics).
  3. SYSTEM_SERVICE_EXCEPTION or SYSTEM_THREAD_EXCEPTION_NOT_HANDLED → identify the driver from the dump, update it cleanly.
  4. INACCESSIBLE_BOOT_DEVICE → check BIOS storage mode (RAID vs AHCI) and the Intel RST driver.
  5. CRITICAL_PROCESS_DIED → run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth; check the drive.
  6. DPC_WATCHDOG_VIOLATION → update SSD firmware and storage drivers.

Fix 4: Undo what changed recently

Most crashes follow a change — find it and reverse it.

  1. Settings > Windows Update > Update history — did a Windows or driver update land just before crashes started? Uninstall it (Uninstall updates) or roll back the driver (Device Manager > Properties > Driver tab > Roll Back Driver).
  2. Settings > Apps > Installed apps sorted by date — uninstall anything new (especially VPNs, third-party antivirus, “optimizers”).
  3. Did you change BIOS settings or install new hardware? Revert.

Fix 5: Run the standard repair pass

When the cause is unclear, this fixes the common software corruption:

  1. Open Terminal (Admin) via Windows + X.
  2. Run sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth, then sfc /scannow again.
  3. Run chkdsk C: /f and restart if prompted.
  4. Safe, non-destructive, and resolves a solid minority of mystery crashes outright.

Fix 6: Boot into Safe Mode and observe

Safe Mode loads minimal drivers — if crashes stop there, it’s a driver or startup program.

  1. Shift + Restart from the power menu > Troubleshoot > Advanced options > Startup Settings > Restart > press 4.
  2. If stable in Safe Mode: update drivers (graphics, network, chipset) from your laptop manufacturer’s site, and clean-boot (msconfig) to find conflicting startup software.
  3. If it crashes in Safe Mode too: suspect hardware (RAM, drive, overheating) or core Windows corruption.

Fix 7: Test hardware if software fixes fail

The remaining suspects when software comes back clean:

  1. RAM: mdsched.exe quick test, then MemTest86 (two+ passes) for certainty.
  2. Drive: manufacturer’s health tool (Samsung Magician, WD Dashboard, Crucial Storage Executive) + chkdsk C: /f /r.
  3. Heat: HWiNFO during the crash-triggering workload — sustained 95°C+ on a laptop CPU suggests cooling failure.
  4. Back up before hardware testing — if the drive is the problem, every boot risks more damage.

Closing

“Your PC ran into a problem” is Windows being polite instead of useful — but the fix process is the same as for any blue screen once you look past the friendly message. Disable the auto-restart, capture the stop code, and follow it to the specific fix; that’s the entire method, and it works because the stop code is the one honest part of the screen. If this message appears on every boot rather than randomly, skip the driver hunting and go straight to recovery-environment repairs — a boot loop is a different problem wearing the same message. Either way, the dump files in C:\Windows\Minidump are your backstop: they remember what the screen didn’t stay still long enough to show.

Frequently asked questions

What does 'Your PC ran into a problem' mean?
It’s the generic blue screen message Windows 11 shows for every crash. The real information is the stop code shown underneath (like MEMORY_MANAGEMENT) — that’s what identifies the cause. The friendly message itself tells you nothing.
How do I find the actual error behind this message?
Read the stop code at the bottom of the blue screen before it restarts (or disable automatic restart so it stays visible). After rebooting, check Event Viewer > Windows Logs > System for BugCheck entries, or analyze the minidump in C:\Windows\Minidump with WinDbg.
Will my files be okay?
Almost always yes. This message accompanies every blue screen regardless of cause, and most causes (drivers, updates, settings) don’t threaten data. The exceptions — failing drive or RAM — are why you should back up before troubleshooting.
What if it shows this message on every boot?
That’s a boot loop, not a random crash. Boot into the recovery environment (interrupt boot three times), then work through startup repair, BCD rebuild, and update rollback — our automatic repair loop guide covers that sequence.