How to Troubleshoot and Fix Stop Code Errors (BSOD) on Windows 11: The Complete Guide

Encountering a stop code error—commonly known as the Blue Screen of Death (BSOD)—on Windows 11 can be an unnerving experience for anyone, whether you’re a tech-savvy veteran or just somebody trying to use their computer for daily tasks. Although these errors may seem intimidating, they are actually like a warning signal from your operating system: something has gone seriously wrong, and Windows cannot continue safely. But before you panic, you should know that in most cases, blue screen crashes are fixable—with a methodical approach, patience, and the right information.

This in-depth guide unpacks everything you need to know about tackling stop code errors on Windows 11, from understanding what a BSOD actually means, to advanced troubleshooting techniques, memory dump analysis, and the specifics of each error type. Whether your error is a one-time glitch or your PC is stuck in an endless cycle of crashes, here you will find actionable steps, using updated advice from official Microsoft documentation, leading tech brands, and real user reports.

What Is a Stop Code Error (BSOD) in Windows 11?

When Windows 11 encounters a condition that could harm the system or its data, it will halt operations and display a Blue Screen of Death (BSOD), also called a stop code error. This safety mechanism prevents your machine from causing further damage, whether due to a malware attack, hardware failure, problematic drivers, or system file corruption.

The blue screen itself features a hex-based error code—like 0x00000050—alongside a ‘stop code’ (usually some technical-sounding uppercase phrase, such as PAGE_FAULT_IN_NONPAGED_AREA). Since Windows 8, blue screens frequently include a QR code that, when scanned, takes you directly to a Microsoft support page related to the error.

Although the blue color has remained iconic, there have been times (notably in Windows preview builds) where the color switched to green to distinguish Insider preview crashes—hence the Green Screen of Death (GSOD).

Common Causes of BSOD/Stop Code Errors in Windows 11

Stop code errors can erupt from almost anywhere in your system stack, but an in-depth analysis from Microsoft and leading manufacturers reveals a pattern:

• Faulty third-party drivers – Around 70% of stop code errors trace back to non-Microsoft or third-party drivers. These can include graphics, network, storage, or peripheral drivers that have become obsolete, corrupt, or simply have bugs.
• Hardware failures – Think faulty RAM, deteriorating SSDs, overheating CPUs, or even loose cables. Microsoft estimates that approximately 10% of BSODs are hardware-induced.
• Microsoft code and updates – 5% of errors are related to Windows code itself, including problematic updates or rare OS glitches.
• Unknown/undetermined – In about 15% of cases, the system memory is too damaged at the time of the crash to provide a clear cause.

Other common triggers include: malware or compromised boot sectors, registry errors, low disk space, application conflicts, manual overclocking, and also power surges or abrupt shutdowns.

Identifying Your BSOD Stop Code and Error Message

Every time a blue screen appears, pay special attention to:

• Stop Code (e.g., CRITICAL_PROCESS_DIED, KMODE_EXCEPTION_NOT_HANDLED, MEMORY_MANAGEMENT)
• Error Code (e.g., 0x000000EF, 0x0000001E, 0x0000001A)
• QR Code (scan with your smartphone for a direct support link)

Keeping a note of your specific stop code is crucial, as it narrows down the troubleshooting path significantly. For example, DRIVER_IRQL_NOT_LESS_OR_EQUAL almost always indicates driver misbehavior, while INACCESSIBLE_BOOT_DEVICE points to fundamental issues with the disk or the storage controller.

For a deeper analysis, your PC also generates a memory dump file during each crash, stored in %SystemRoot%\MEMORY.DMP or %SystemRoot%\Minidump. Advanced users or support technicians can use WinDbg to dive deep into these files.

Most Frequent BSOD Stop Codes and Their Meanings

Below is a rundown of the stop codes Windows 11 users most frequently encounter—and what each one really means:

• PAGE_FAULT_IN_NONPAGED_AREA (0x00000050): Windows tried to access an unavailable memory page. Common in faulty RAM or corrupt NTFS volumes.
• IRQL_NOT_LESS_OR_EQUAL (0x0000000A): A driver tried to access memory at too high an interrupt request level. Frequent with poorly programmed or outdated drivers, or faulty RAM.
• KMODE_EXCEPTION_NOT_HANDLED (0x0000001E): A kernel-mode program threw an unhandled exception. Most likely cause: a malfunctioning driver or service.
• CRITICAL_PROCESS_DIED (0x000000EF): A critical Windows process terminated unexpectedly. A serious indicator that can point to a system problem, disk failure, or malware.
• MEMORY_MANAGEMENT (0x0000001A): The memory manager detected corruption. Probably failed RAM or corrupt system files.
• SYSTEM_SERVICE_EXCEPTION (0x0000003B/0xC000021A): Exception in a system service. Could be due to driver conflicts, file corruption, or errors in Windows updates.
• DRIVER_IRQL_NOT_LESS_OR_EQUAL (0x000000D1): A driver made an incorrect memory reference. A sign of incompatible or faulty drivers.
• VIDEO_TDR_FAILURE (0x00000116), VIDEO_ENGINE_TIMEOUT_DETECTED, or VIDEO_TDR_TIMEOUT_DETECTED (0x00000141/0x00000117): Issues related to GPU or display drivers, especially regarding interface timeouts.
• INACCESSIBLE_BOOT_DEVICE (0x0000007B): Windows cannot access the startup disk. Frequent in conflicts with storage drivers or severe disk corruption.
• BAD_POOL_HEADER (0x00000019): Corrupt pool memory. Due to bad drivers, faulty RAM, or rare software errors.
• SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (0x0000007E): Unhandled system thread exception. Usually associated with outdated drivers.
• WHEA_UNCORRECTABLE_ERROR (0x00000124): Hardware error reported by the WHEA architecture. Severe—possible deteriorating CPU, RAM, or other component.
• UNMOUNTABLE_BOOT_VOLUME (0x000000ED): Windows cannot mount the boot drive. Common in disk corruption or changes in storage controller configuration.
• DPC_WATCHDOG_VIOLATION (0x00000133): The DPC Watchdog detected errors. Often related to faulty drivers, especially in storage devices.

If the error codes change with each crash, suspect hardware instability or multiple driver conflicts. This indicates that the system has a more serious underlying problem.

Immediate Actions to Take After a Blue Screen in Windows 11

If a blue screen appears, act immediately by following these steps:

• Allow the crash process to finish – If you see a percentage, let Windows collect diagnostic data before forcing a restart.
• Note the stop code, error code, and any file or QR code displayed.
• Try restarting – Many times, an isolated crash is resolved with a restart, especially if it occurred during a heavy update or driver installation.
• If you cannot access Windows, note if the crash repeats under the same condition (for example, in safe mode or normal mode, at the login screen, etc.).

Troubleshooting Stop Code Errors Step-by-Step

1. Disconnect external devices

Disconnect everything except the keyboard and mouse—external hard drives, printers, webcams, etc. Even a faulty peripheral can block Windows from starting or trigger a blue screen. Restart with only the essentials and, if you get into Windows, reconnect hardware one by one to detect which one is causing the problem.

2. Perform a complete hard reset

Completely turn off your machine—hold down the power button until it shuts off. Remove the power cable (and the battery on laptops if it’s removable), then hold down the power button for 20 seconds to discharge residual electricity. Reconnect and restart. This can fix transient errors or stuck devices, especially after a power surge or a failed update.

3. Access Safe Mode

If Windows freezes at every startup, try booting into Safe Mode. This loads a minimal set of drivers and programs, often bypassing the cause of the BSOD:

• During startup, force-stop your computer three times when you see the Windows logo (hold down the power button in the middle of the process). Next time, Windows will enter the automatic repair screen.
• Select Troubleshoot > Advanced options > Startup Settings, and then Restart.
• In the options, press 4 for Safe Mode, or 5 for Safe Mode with Networking.

If your computer works stably in Safe Mode, the problem likely stems from third-party drivers or software, not hardware.

4. System Restore – Return to a functional state

If you have System Restore enabled, you can use a previous point to return to an earlier state before the problematic software installation or update.

1. Go to Settings > System > Recovery (or from the Windows Recovery Environment via Troubleshoot > Advanced options > System Restore if you cannot start normally).
2. Follow the prompts to select a restoration point and go back.

This process does not affect your personal files, but it uninstalls apps or drivers added since the restore point was created.

5. Diagnosis with memory dump analysis

If you have technical knowledge or support, analyze the MEMORY.DMP or minidump files located in %SystemRoot%\MEMORY.DMP or %SystemRoot%\Minidump. Use WinDbg (available from the Microsoft Store) to open these files and run the command !analyze -v, which provides a detailed breakdown of the root cause of the crash, frequently including the responsible driver or system process.

If you are not technical, seek help on official Microsoft forums or with a trusted technician, providing the stop code and relevant context.

6. Run System File Checker (SFC) and DISM

Corrupt system files are a classic cause of recurring blue screens. Use SFC and DISM to scan for and repair corruption in Windows:

• Open Command Prompt as Administrator
• Type sfc /scannow and press Enter
• If SFC cannot repair some files, run the following DISM commands one by one:
  • DISM /Online /Cleanup-Image /CheckHealth
  • DISM /Online /Cleanup-Image /ScanHealth
  • DISM /Online /Cleanup-Image /RestoreHealth

These commands require an internet connection, as Windows can download clean files from Microsoft servers. When finished, restart your system.

7. Update drivers, BIOS, and firmware

Most BSODs are linked to outdated or malfunctioning drivers. Keep graphics, network, storage, and chipset drivers updated, as well as the BIOS/UEFI:

• Use manufacturer tools like Dell SupportAssist or download drivers directly from your equipment or motherboard manufacturer’s website.
• To update the BIOS, carefully follow the manufacturer’s instructions; a BIOS update can fix compatibility issues but carries risks.
• Always restart after updating drivers or firmware.

8. Ensure free disk space

Windows needs at least 10-15% free space, especially on the drive where it is installed (usually C:). If your disk is full, system files can become corrupted or updates can fail, contributing to blue screens. Clean up unnecessary files using tools like Disk Cleanup or Storage Sense.

9. Scan for malware

Viruses and rootkits can compromise critical system processes or the MBR, causing blue screens. Use Microsoft Safety Scanner or another trusted tool that includes MBR checks.

10. Clean Boot to isolate problems

A ‘clean boot’ starts Windows with only essential services and programs, helping identify which third-party component is causing the failure.

1. Type msconfig in the search bar and select System Configuration.
2. On the Services tab, check Hide all Microsoft services, and then Disable all.
3. Switch to the Startup tab and click Open Task Manager. Disable all non-Microsoft programs.
4. Restart and see if the problem persists. If it disappears, enable services and programs in groups to find the culprit.

11. Hardware Diagnostics

Blue screens sometimes stem from physical hardware failures not detectable during normal use. Run your manufacturer’s diagnostic tests; for example, on Dell, pressing F12 during boot accesses their diagnostic suite. For other brands, check the manufacturer’s website.

Common components under review: RAM, hard drives/SSDs, CPUs, and GPUs.

12. Reset BIOS/UEFI to default values

Incorrect settings in BIOS or UEFI—such as overclocking, storage modes, or specific timings—can cause stop code errors. To reset:

1. Restart and repeatedly press F2 (or another key according to your brand) to enter BIOS/UEFI.
2. Look for the option to ‘Load Defaults’, ‘Restore Settings’, or similar, and save changes.

This step helps especially with errors like INACCESSIBLE_BOOT_DEVICE, which can be caused by changes in controller configuration.

13. Repair Windows startup files

If Windows doesn’t boot, use the built-in Startup Repair.

1. Interrupt the boot process three times at the Windows logo to access the recovery environment, or use a Windows 11 installation USB.
2. Select Troubleshoot > Advanced options > Startup Repair.
3. Follow the on-screen instructions to start the automatic repair.

If you have BitLocker active, be prepared to provide the recovery key, which you may have in your Microsoft account under ‘Devices’.

14. Use SupportAssist OS Recovery (for specific brands)

Some brands include system recovery tools, like SupportAssist on Dell, which can repair Windows and recover data when it won’t start normally.

1. Restart and press F12 at startup to access the boot menu.
2. Select SupportAssist OS Recovery.
3. Choose ‘Repair’, follow the instructions, and monitor the process.

This tool can detect hardware failures, update drivers, and repair startup errors in an automated mode.

15. Factory reset as a last resort

If all the previous steps fail and blue screens persist, you can reset Windows 11 to its factory state.

1. Go to Settings > System > Recovery.
2. Select Reset this PC and follow the instructions to keep your files or remove everything and clean the drive.

A full reset will erase everything on the system, so remember to back up your important files first.

Advanced Troubleshooting: Memory Dump Analysis and Debugging Tools

For stubborn or mysterious stop errors, analyzing memory dumps is essential. Here’s how to use advanced debugging tools:

Enabling and Locating Memory Dumps

1. Search for View advanced system settings and enter.
2. On the Advanced tab, open Settings under Startup and Recovery.
3. Under Write debugging information, select the desired type of dump (mini, kernel, or complete).
4. Larger volumes are created in %SystemRoot%\MEMORY.DMP; smaller ones in %SystemRoot%\Minidump.

Use the DumpChk tool to verify the validity of the volumes, and for deep analysis, download the Windows SDK and select ‘Debugging Tools for Windows’ (WinDbg). Load your dump file and run !analyze -v to get a detailed breakdown, including problematic drivers or DLLs. Basic interpretation consists of identifying which driver or module caused the failure and focusing on updating or removing it.

[related url=”https://www.ikkaro.net/what-is-a-real-time-operating-system-rtos/”]

Using Driver Verifier

Driver Verifier is a powerful tool that can reveal problematic drivers, but use it with caution, as it can intentionally introduce crashes to detect errors:

• Start by typing verifier in Windows search and follow the prompts to select drivers (start with non-Microsoft ones).
• If the system fails to boot, enter Safe Mode and reset the configuration.

This method is especially useful in cases of recurring blue screens related to drivers.

Special Case Stop Codes and Their Solutions

INACCESSIBLE_BOOT_DEVICE (0x0000007B)

This error indicates that Windows lost access to the startup disk or found a poor controller configuration. These commonly occur due to:

• Changing the storage controller mode (RAID vs. AHCI vs. IDE) in BIOS/UEFI
• Disk failure, loose cables, or damaged boot sectors

To solve:

1. Enter BIOS (F2 or DEL) at startup.
2. Locate the SATA configuration—change it from ‘RAID On’ to ‘AHCI’, or vice versa, and save changes.
3. If it doesn’t work, restore default values or consider a full reinstall if storage configuration errors persist.

Specific tips for frequent stop codes

• PAGE_FAULT_IN_NONPAGED_AREA: Run chkdsk /f /r from the command line and perform memory diagnostics (type mdsched.exe in search).
• SYSTEM_SERVICE_EXCEPTION: Use sfc /scannow and DISM. If you suspect a faulty update, try uninstalling it in ‘Update History’.
• KMODE_EXCEPTION_NOT_HANDLED: Boot into Safe Mode, open Device Manager, and uninstall or disable recent or problematic drivers or devices.

Preventing Future Stop Code Errors and BSODs

Keep Everything Up-to-Date

One of the most effective ways to avoid blue screens is to keep everything updated: Windows, drivers, BIOS/UEFI, and main applications. Updates contain compatibility improvements and critical fixes that often do not appear in change notes.

Watch for Recent Changes

If stop codes start after a recent installation (whether utility or driver), uninstall it immediately. Use ‘Apps & features’ or Device Manager to remove recent drivers.

Manage Startup Programs and Clean Boot

Reduce what loads at startup. Fewer automatic programs and services make it easier to identify what caused the problem. Use the Startup tab in Task Manager to disable non-essential software.

Proactively Monitor Hardware Health

Even new equipment can have faulty RAM or disks that passed the initial test. Run periodic diagnostics with manufacturer tools and monitor system temperatures to detect overheating, a frequent trigger for BSODs.

Understand What Doesn’t Work

Reinstall Windows only as a last resort, after exhausting other targeted solutions. Reinstallation erases settings, applications, and data if you haven’t made backups. Prioritize specific solutions like rolling back updates or using System Restore first.

Managing Software Conflicts

The Windows 11 ecosystem can present unexpected conflicts, for example, between security software or recent drivers. Uninstall apps or drivers added just before the first BSOD and keep in mind that Windows updates can also be a cause. Use a clean boot process to isolate the problem in stages, enabling services and programs in small groups.

Once the conflict is identified, update or remove the problematic components.

When to Seek Help: Community and Professional Support

If you have exhausted all troubleshooting techniques and your PC remains in a blue screen cycle, it is time to seek specialized help. The Microsoft Community forums (answers.microsoft.com) and manufacturer support portals are valuable resources. Provide as many details as possible: hardware, recent changes, specific codes, and the moments when the problem occurs.

Attaching minidump files or analyses from tools like WinDbg speeds up the diagnostic process.

FAQ: Common Questions About BSODs and Stop Code Errors

• Can a BSOD damage my hardware? The blue screen itself is just a warning, but if it indicates overheating, failed components, or an unstable power source, those causes can put your hardware at risk if not addressed.
• What’s the difference between a BSOD and a system freeze? The BSOD shows a blue screen with an error and usually forces a restart, while freezes leave the system stuck or unresponsive without a visible message. Both can have similar roots, but freezes do not automatically generate useful diagnostic information.
• Should I disable automatic restart after a BSOD? Yes, this can be done in Control Panel > System > Advanced system settings > Startup and Recovery. Removing the ‘Automatically restart’ option allows you to see the error on the screen and facilitates diagnosis.
• Can overheating cause blue screens? Absolutely. Ensure your equipment is free of dust, well-ventilated, and that fans and cooling solutions are working correctly.
• Can a recent Windows update cause BSOD errors? Yes. If a stop code arises after an update, try uninstalling it or taking advantage of system restoration.
• How do I perform a clean install? After backing up important files, create a Windows 11 installation USB from the Microsoft website and follow the instructions to format and reinstall, removing all previous data and settings.

Final Thoughts

Receiving a blue screen on Windows 11 can be frustrating, but it is rarely an unsolvable situation. If you understand what each code means and follow an orderly diagnostic process, you can resolve even stubborn failures, from simple restarts, driver recovery, hardware inspection, to full resets or reinstalls. Keeping up with updates, regularly checking the health of your components, and noting crash codes makes it easier to identify and eliminate the root cause of these failures.

With this knowledge, you will be better prepared to turn the dreaded blue screen into a solvable problem and convert inconveniences into opportunities for learning and improvement on your computer.