 Since Upgrade to 24H2 - How to Troubleshoot.webp)
Windows 11 users who upgraded to version 24H2 may experience unexpected system crashes accompanied by a Bug Check or Dark Screen of Death (DSOD). These crashes can cause Windows to restart unexpectedly and may display a stop code that provides clues about the underlying problem.
This guide explains what causes a Bug Check in Windows 11 and covers the troubleshooting steps that can identify and resolve 24H2 crash issues.
Disclaimer: We are an independent technical support resource and are not affiliated with, endorsed by, or sponsored by Microsoft.
Understanding Bug Check (DSOD) in Windows 11
A Bug Check happens when Windows encounters a critical error it can’t recover from, forcing the system to crash and reboot. The error screen usually shows a stop code, which can offer real clues about the actual cause — it’s worth noting down before you start troubleshooting.
Some users experience repeated crashes specifically after upgrading to 24H2. If your computer is crashing or restarting frequently, work through the steps below in order.
Here’s how to troubleshoot and fix Windows 11 24H2 DSOD:
1
Check for Windows updates
Make sure your computer has the latest updates installed — Microsoft often releases patches for known 24H2 issues shortly after they’re reported. Open Settings (Win + I) → Windows Update → Check for updates.
2
Update or roll back drivers
Outdated or incompatible drivers are a common cause of crashes after a major Windows update, especially graphics and network drivers. Open Device Manager (Win + X → Device Manager), expand Display adapters, Network adapters, and other key components, right-click each device, and select Update driver. If crashes started right after updating a specific driver, go to Properties → Driver → Roll Back Driver instead.
3
Run Windows Memory Diagnostic
Faulty RAM can trigger Bug Checks. Press Win + R, type mdsched.exe, and press Enter, then choose “Restart now and check for problems” to scan your memory for errors.
4
Check storage for errors
Disk errors can also cause system instability. Open Command Prompt as administrator and run chkdsk /f /r, then restart your computer to let it complete the scan and repair any issues found.
5
Roll back to the previous Windows version
If none of the above resolves the crashes, rolling back is usually the best temporary fix while the underlying cause gets sorted out. Go to Settings → Recovery → Go back to the previous version of Windows 11 (this option is only available for a limited time after upgrading).
If Crashes Continue
If you’ve checked for updates, updated or rolled back drivers, run the Windows Memory Diagnostic, checked your storage for errors, and the crashes still continue, note the exact stop code shown on the Bug Check screen — it narrows down the cause considerably. You can also find it afterward in Event Viewer (search for Event Viewer in the Start menu, then check Windows Logs → System for a Critical or Error event around the time of the crash).
At this stage, consider whether the problem started right after installing a specific app, driver, or peripheral — removing or updating that item is often the fastest path to a fix. If the system remains unstable after all of the above, a repair install or clean install of Windows 11 may be necessary, after backing up your important files first.
If you’d like help identifying your specific stop code or walking through these steps, chat with our support team.
FAQ
What is a Dark Screen of Death (DSOD) in Windows 11?
It’s a crash where the screen goes black or dark instead of showing the familiar blue error screen, usually accompanied by a Bug Check that forces Windows to restart. It’s commonly linked to driver or display-related issues, especially after a major update like 24H2.
Why do Bug Check crashes happen after updating to 24H2?
Major feature updates like 24H2 can expose compatibility issues with existing drivers, especially graphics and network drivers, or surface underlying hardware problems that weren’t triggered by the previous version.
Where do I find the stop code after a crash?
It’s shown on the crash screen itself, or afterward in Event Viewer under Windows Logs → System, listed as a Critical or Error event around the time Windows restarted.
Should I roll back to the previous Windows version?
Rolling back is a reasonable temporary fix if crashes started right after upgrading to 24H2 and other steps haven’t resolved them. It’s only available for a limited time after the upgrade, so act quickly if you want that option.
Tags: Bug Check, Dark Screen of Death, DSOD, Fix Windows Errors, System Stability, Troubleshooting, Windows 11, Windows 11 24H2, Windows Crashes
