“Your PC Ran Into a Problem” on Windows 11 24H2? Fix It Fast

“Your PC ran into a problem and needs to restart.” If you’ve used Windows 11 for any length of time, you’ve met this screen — the polite, sad-faced announcement that your laptop just crashed. Since the 24H2 update, a lot of people are meeting it more often than they’d like, because 24H2 changed enough under the hood to upset drivers that were perfectly happy before.

Here’s the reassuring part: this screen is a symptom, not a diagnosis, and the path from symptom to fix is well-trodden. The stop code at the bottom tells you what’s wrong, and this guide shows you how to read it and what to do about the most common causes on 24H2. For the full technical deep-dive, our Windows 11 blue screen fix guide covers every major stop code.

Why this happens

  • A driver conflicts with 24H2’s kernel changes. The update reworked memory management, power sequencing, and driver interfaces — older drivers can crash under the new rules.
  • Windows Update delivered a buggy driver. 24H2’s rollout included new driver versions for common hardware; some had bugs that only appear on specific laptop models.
  • Memory problems surfaced. 24H2’s stricter memory handling exposes marginal RAM that previous builds tolerated silently.
  • Corrupted system files. An interrupted or partial 24H2 install leaves mismatched components that crash under load.
  • Overheating under new power behavior. Changed CPU power management can push thermals higher on some laptops, and heat causes exactly these crashes.
  • Third-party software hooks broke. Antivirus filters, VPN clients, and system utilities that hook the kernel may not be 24H2-ready.

How to fix it

Work through these in order. The goal is to go from “crashing” to “stable,” then identify the specific cause.

Fix 1: Capture the stop code

You can’t fix what you can’t see — so make the screen stay put.

  1. The next time it crashes, photograph the screen with your phone, making sure the stop code (all caps with underscores) and any “What failed” filename are legible.
  2. To keep the screen visible in future, disable auto-restart: Win + R, type sysdm.cpl, Advanced tab, Settings under Startup and Recovery, uncheck Automatically restart.
  3. Confirm dumps are being saved: in the same dialog, Write debugging information should be Automatic memory dump.
  4. With the code in hand, you can look up the specific fix — many are covered in our IRQL fix guide and related articles.

Fix 2: Boot into Safe Mode to stabilize

Safe Mode loads only essential drivers — if crashes stop there, a third-party driver is guilty.

  1. Force two interrupted boots to reach Recovery, then Troubleshoot > Advanced options > Startup Settings > Restart and press 4.
  2. Use the laptop in Safe Mode for a while. Stable here = driver or startup software problem.
  3. Still crashing in Safe Mode? That points to hardware (RAM, drive, thermals) or core system corruption — skip to Fixes 6 and 7.
  4. In Safe Mode you can also uninstall the most recent update via Settings > Windows Update > Update history > Uninstall updates.

Fix 3: Update the big three drivers

Graphics, Wi-Fi, and chipset drivers cause the majority of 24H2 crashes.

  1. Open Device Manager (Win + X > Device Manager).
  2. Update Display adapters, Network adapters, and the chipset/System devices entries: right-click each, Update driver > Search automatically for drivers.
  3. Then go to your laptop maker’s support site for the tested versions — Dell , HP , Lenovo — and install their 24H2-era releases.
  4. Intel Wi-Fi/Bluetooth users can also use Intel’s Driver & Support Assistant tool for the latest wireless drivers.

Fix 4: Roll back the driver that 24H2 installed

If crashes started the day 24H2 arrived, undo its driver changes.

  1. Go to Settings > Windows Update > Update history > Driver updates and note what 24H2 delivered.
  2. In Device Manager, open each listed device’s Properties > Driver tab and click Roll Back Driver where available.
  3. Reboot and test for a day. Stability confirms the new driver was the problem.
  4. To stop Windows re-installing the bad driver, use Microsoft’s “Show or hide updates” troubleshooter to hide that specific driver version.

Fix 5: Repair system files

A damaged 24H2 install needs its components verified.

  1. Open an elevated Terminal (Win + X > Terminal (Admin)).
  2. Run sfc /scannow and wait for completion.
  3. Then run DISM /Online /Cleanup-Image /RestoreHealth to repair the component store.
  4. Reboot and monitor. If SFC reports corruption it couldn’t fix even after DISM, consider an in-place repair install using Microsoft’s official Windows 11 installation media — it refreshes Windows while keeping files and apps.

Fix 6: Test memory and thermals

Rule out the hardware causes that 24H2’s stricter handling exposes.

  1. Run Windows Memory Diagnostic: Win + R, type mdsched.exe, Restart now and check for problems. Check results in Event Viewer > Windows Logs > System afterward.
  2. Monitor temperatures with HWMonitor during normal use — sustained CPU/GPU temps above 90°C warrant cleaning the vents and fans.
  3. Run chkdsk C: /f from an elevated Command Prompt (reboot to let it scan) to rule out file-system damage from crash-time disk writes.
  4. Memory-specific stop codes have their own playbook — see our memory management BSOD guide .

Fix 7: Uninstall the 24H2 update as a last resort

If nothing stabilizes the system, step back from 24H2 while Microsoft refines it.

  1. Go to Settings > Windows Update > Update history > Uninstall updates (or Troubleshoot > Advanced options > Uninstall Updates > Uninstall the latest feature update from Recovery).
  2. After rolling back, Pause updates for several weeks.
  3. Before retrying 24H2 later, update your BIOS and all drivers from your laptop maker’s site — most 24H2 crash waves trace to outdated firmware meeting the new build.
  4. Microsoft tracks known 24H2 issues in its Windows support documentation — check there for your specific stop code before reinstalling the update.

Closing

“Your PC ran into a problem” is Windows being honest: something went wrong, it told you, and it restarted to protect itself. On 24H2, that something is usually a driver caught off-guard by the update. Capture the stop code, refresh or roll back the driver, verify the system files — and the sad face becomes a rare sight again instead of a regular visitor.

Frequently asked questions

What does 'Your PC ran into a problem and needs to restart' mean?
It’s the friendly face of a blue screen (bugcheck). Windows hit a fatal error it couldn’t recover from, collected diagnostic info, and restarted. The small stop code at the bottom — like MEMORY_MANAGEMENT or DRIVER_IRQL_NOT_LESS_OR_EQUAL — identifies the specific failure and points to the fix.
Why does it happen repeatedly on Windows 11 24H2?
Recurring crashes after the 24H2 update usually mean a driver that worked under 23H2 conflicts with 24H2’s changed kernel or power management. Graphics, Wi-Fi, and storage drivers are the top offenders. Updating or rolling back the driver that 24H2 installed breaks the cycle.
Will the automatic restart damage my files?
No. The restart itself doesn’t touch your files — Windows just reboots. The underlying crash also rarely damages data, though you can lose unsaved work in open apps. If crashes happen during disk writes, running chkdsk afterward is a sensible precaution.
How do I stop the screen from disappearing before I can read it?
Disable automatic restart: press Win + R, type sysdm.cpl, go to the Advanced tab, click Settings under Startup and Recovery, and uncheck Automatically restart. The blue screen will then stay visible until you restart manually, giving you time to photograph the stop code.