How to Read and Fix Windows BSOD Error Codes

The Blue Screen of Death (BSOD) is a critical Windows system state characterized by a complete operational halt and a blue (or black on Windows 11) screen displaying a specific error code. This article provides a comprehensive list of BSOD error codes along with in-depth technical explanations of their causes and contexts, compiled for IT professionals, technicians, and gamers.

The Blue Screen of Death (BSOD) is a protective mechanism of the Windows operating system triggered during a kernel panic or fatal core-level error. This condition forces a total system stop to prevent data corruption or hardware damage. The displayed error code is the primary diagnostic tool for identifying the root cause, which can range from driver conflicts and hardware failures to memory corruption.

While synonymous with a blue screen, the BSOD in Windows 11 is black by default. This visual change does not affect the technical meaning of the provided error code. BSOD can occure across all Windows versions, from Windows 95 to modern systems today, making an understanding of these codes perennially relevant.

Read Also: Understanding and Analyzing Windows Logs and BSOD Files

Accurate diagnosis heavily relies on interpreting the stop code and its additional parameters. Often, errors originate from incompatible kernel-mode drivers, faulty memory (RAM), or storage device issues. Further analysis can utilize tools like the Windows Debugger (WinDbg).

Below is a comprehensive list detailing various BSOD error codes, their associated messages, and brief technical explanations of potential causes. This data is compiled from official Microsoft documentation and trusted technical sources.

Complete List of Blue Screen of Death (BSOD) Error Codes

• 0x00000001 – APC_INDEX_MISMATCH: An inconsistency occured in the Asynchronous Procedure Call (APC) state index. This kernel internal error arises from improper system call sequences for entering or exiting critical sections.
• 0x00000002 – DEVICE_QUEUE_NOT_BUSY: A rare error caused by hardware or software, often related to printer drivers or signature error issues.
• 0x00000003 – INVALID_AFFINITY_SET: Rarely occurs, often seen during printer installation. Indicates a problem with an invalid processor affinity set.
• 0x00000004 – INVALID_DATA_ACCESS_TRAP: Occured in Windows XP SP2 and Windows Server 2003 with certain antivirus and firewall software. Indicates invalid data access interference.
• 0x00000005 – INVALID_PROCESS_ATTACH_ATTEMPT: Indicates an attempt to attach a thread to a process in an unallowed situation. Often caused by coding errors in the Http.sys file.
• 0x00000006 – INVALID_PROCESS_DETACH_ATTEMPT: Indicates a problem with a mutex or APC. Can occur if Windows incorrectly queues an APC function.
• 0x00000007 – INVALID_SOFTWARE_INTERRUPT: Indicates an interrupt level outside the software’s allowed range. Typically due to faulty or incompatible hardware controllers or software.
• 0x00000008 – IRQL_NOT_DISPATCH_LEVEL: Indicates an attempt to delete a device at a non-dispatch level.
• 0x00000009 – IRQL_NOT_GREATER_OR_EQUAL: Occurs when memory access happens at an excessively high IRQL. Indicates a driver using an incorrect memory address.
• 0x0000000A – IRQL_NOT_LESS_OR_EQUAL: A kernel-mode driver accessed pageable memory at DISPATCH_LEVEL or higher. One of the most common BSODs, often related to faulty drivers.
• 0x0000000B – NO_EXCEPTION_HANDLING_SUPPORT: Indicates that exception handling is not supported by the system.
• 0x0000000C – MAXIMUM_WAIT_OBJECTS_EXCEEDED: The current thread exceeded the allowed number of wait objects. Caused by improper use of KeWaitForMultipleObjects.
• 0x0000000D – MUTEX_LEVEL_NUMBER_VIOLATION: An attempt to acquire a mutex at a lower level. Often happens after CPU overhead or insufficient RAM.
• 0x0000000E – NO_USER_MODE_CONTEXT: Occured when a computer was disconnected from a remote session in Windows 2000, causing the system to stop responding.
• 0x0000000F – SPIN_LOCK_ALREADY_OWNED: A request for a spin lock was initiated while the spin lock was already owned. Caused by recursive queries on a spin-lock.
• 0x00000010 – SPIN_LOCK_NOT_OWNED: An attempt to release a spin-lock not owned by the caller. Can be caused by improperly installed devices or conflicting drivers.
• 0x00000011 – THREAD_NOT_MUTEX_OWNER: An attempt to release a thread mutex improperly. Check recently installed software and hardware compatibility.
• 0x00000012 – TRAP_CAUSE_UNKNOWN: An unknown exception has occurred. Often happened on Windows 2000 with Sound Blaster and integrated sound card software.
• 0x00000013 – EMPTY_THREAD_REAPER_LIST: The thread list is corrupted. Uninstall recently installed software and ensure hardware compatibility.
• 0x00000014 – CREATE_DELETE_LOCK_NOT_LOCKED: A very rare error caused by faulty hardware or incompatible device driver issues.
• 0x00000015 – LAST_CHANCE_CALLED_FROM_KMODE: A random exception service was launched in kernel mode. Means an installed device was not ready.
• 0x00000016 – CID_HANDLE_CREATION: Failure while creating a descriptor to represent a client ID. Can occur if a browser is not uninstalled completely.
• 0x00000017 – CID_HANDLE_DELETION: Failure while deleting a descriptor representing a client ID. Typically used to identify errors caused by hardware vendor drivers.
• 0x00000018 – REFERENCE_BY_POINTER: An object’s reference count is illegal for its current state. Caused by a driver decrementing an object’s reference count too often.
• 0x00000019 – BAD_POOL_HEADER: A memory pool header is corrupted. Indicates problems with memory address space, often related to memory cards or hard disks.
• 0x0000001A – MEMORY_MANAGEMENT: A severe memory management error. Usually related to the NTFS file system or issues with RAM and disk space.
• 0x0000001B – PFN_SHARE_COUNT: A Page Frame Number (PFN) database management element is corrupted. A rare error related to RAM.
• 0x0000001C – PFN_REFERENCE_COUNT: A PFN database management element’s reference count is corrupted. Indicates newly added hardware is incompatible.
• 0x0000001D – NO_SPIN_LOCK_AVAILABLE: All spin locks are unavailable. Rarely occured in Windows XP when changing IPX frame type.
• 0x0000001E – KMODE_EXCEPTION_NOT_HANDLED: A kernel-mode program generated an unhandled exception. The kernel detected an illegal processor transaction or instruction.
• 0x0000001F – SHARED_RESOURCE_CONV_ERROR: A shared resource conversion problem. Remove new hardware and software to identify the issue.
• 0x00000020 – KERNEL_APC_PENDING_DURING_EXIT: An Asynchronous Procedure Call (APC) was still pending when a thread exited. Indicates an APC in standby mode after thread execution.
• 0x00000021 – QUOTA_UNDERFLOW: Quota charges were mishandled by returning more quota to a block than previously charged.
• 0x00000022 – FILE_SYSTEM: A file system problem. Likely due to depletion of the nonpaged pool memory during indexing.
• 0x00000023 – FAT_FILE_SYSTEM: A problem with the FAT16 or FAT32 file system. Can be caused by physical storage damage, fragmentation, or software RAID issues.
• 0x00000024 – NTFS_FILE_SYSTEM: A problem in ntfs.sys, the driver file for reading/writing NTFS drives. Similar causes to FAT_FILE_SYSTEM error.
• 0x00000025 – NPFS_FILE_SYSTEM: A problem with the Named Pipe File System (NPFS). Can be caused by hard disk damage or faulty SCSI/IDE drivers.
• 0x00000026 – CDFS_FILE_SYSTEM: A problem with the CD file system. Corruption of the CDFS or bad sectors on the disk.
• 0x00000027 – RDR_FILE_SYSTEM: A problem in the SMB redirector file system. Caused by depletion of the nonpaged memory pool during indexing.
• 0x00000028 – CORRUPT_ACCESS_TOKEN: The security system detected an invalid access token. Occurs during the indexing process.
• 0x00000029 – SECURITY_SYSTEM: An internal security system problem. Indicates a failure within Windows security components.
• 0x0000002A – INCONSISTENT_IRP: An I/O Request Packet (IRP) was found containing inconsistent information. Happens when IRP fields are inconsistent with the IRP’s state.
• 0x0000002B – PANIC_STACK_SWITCH: The kernel-mode stack has been overrun. Caused by a kernel-mode driver using too much stack space or kernel data corruption.
• 0x0000002C – PORT_DRIVER_INTERNAL: An internal error in a port driver. Rarely occurs.
• 0x0000002D – SCSI_DISK_DRIVER_INTERNAL: An internal error in the hard disk and SCSI driver. Indicates issues with storage drivers.
• 0x0000002E – DATA_BUS_ERROR: Information not available in the source data.
• 0x0000002F – INSTRUCTION_BUS_ERROR: Almost always caused by hardware issues: faulty RAM, L2 cache errors, or video memory errors.
• 0x00000030 – SET_OF_INVALID_CONTEXT: The stack pointer in the trap frame has an invalid value.
• 0x00000031 – PHASE0_INITIALIZATION_FAILED: System initialization failed at an early stage. Occurs during routine attempts to set the trap frame stack pointer.
• 0x00000032 – PHASE1_INITIALIZATION_FAILED: System initialization failed. The system failed during early initialization due to a device driver.
• 0x00000033 – UNEXPECTED_INITIALIZATION_CALL: During the initialization phase, Windows 2000 stopped working. Likely a device driver problem.
• 0x00000034 – CACHE_MANAGER: A problem occured in the file system cache manager. Depletion of the paged pool memory can trigger this error.
• 0x00000035 – NO_MORE_IRP_STACK_LOCATIONS: The IoCallDriver packet has no more stack locations available. Can indicate memory corruption or bad RAM.
• 0x00000036 – DEVICE_REFERENCE_COUNT_NOT_ZERO: A driver attempted to delete a device object that still had a positive reference count. A device driver request error.
• 0x00000037 – FLOPPY_INTERNAL_ERROR: Floppy disk driver internal error. Rare in modern systems.
• 0x00000038 – SERIAL_DRIVER_INTERNAL: Serial port driver internal error. Problem with serial communication.
• 0x00000039 – SYSTEM_EXIT_OWNED_MUTEX: A worker routine returned without releasing a mutex it owned.
• 0x0000003A – SYSTEM_UNWIND_PREVIOUS_USER: An attempt to exit a system service while one or more mutexes were accessing it. A rare error.
• 0x0000003B – SYSTEM_SERVICE_EXCEPTION: An exception occurred while executing a routine transitioning from non-privileged to privileged code. Often related to graphics drivers.
• 0x0000003C – INTERRUPT_UNWIND_ATTEMPTED: A Windows 2000 test mode error.
• 0x0000003D – INTERRUPT_EXCEPTION_NOT_HANDLED: A test error in Windows 2000.
• 0x0000003E – MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED: The system has multiple processors, but they are asymmetric to each other. Multiprocessor configuration is not supported.
• 0x0000003F – NO_MORE_SYSTEM_PTES: The system performed excessive I/O, causing System Page Table Entries (PTEs) to become fragmented. Often due to video drivers requesting large memory blocks.
• 0x00000040 – TARGET_MDL_TOO_SMALL: Driver misused IoBuildPartialMdl. Remove new hardware and software to find the problem.
• 0x00000041 – MUST_SUCCEED_POOL_EMPTY: A kernel-mode thread requested too much must-succeed pool. In Windows 2000, this pool size was very small.
• 0x00000042 – ATDISK_DRIVER_INTERNAL: Internal error in the AT hard disk driver. Very rare.
• 0x00000043 – NO_SUCH_PARTITION: Reveals a hard disk problem. Scan with antivirus and check the hard drive with manufacturer utilities.
• 0x00000044 – MULTIPLE_IRP_COMPLETE_REQUESTS: A driver attempted to request completion of an IRP that was already complete. Usually influenced by problems with device drivers.
• 0x00000045 – INSUFFICIENT_SYSTEM_MAP_REGS: An attempt to allocate more map registers than the adaptor. Rarely occurs.
• 0x00000046 – DEREF_UNKNOWN_LOGON_SESSION: Deletion of a token that is not part of any logon session.
• 0x00000047 – REF_UNKNOWN_LOGON_SESSION: A token was created that is not part of any logon session.
• 0x00000048 – CANCEL_STATE_IN_COMPLETED_IRP: An I/O Request Packet (IRP) was completed and then cancelled. Check for the latest driver version on the manufacturer’s site.
• 0x00000049 – PAGE_FAULT_WITH_INTERRUPTS_OFF: A page fault occurred while interrupts were disabled.
• 0x0000004A – IRQL_GT_ZERO_AT_SYSTEM_SERVICE: A thread returned to user mode from a system call while its IRQL was still above PASSIVE_LEVEL.
• 0x0000004B – STREAMS_INTERNAL_ERROR: An internal error in the streaming environment or a streaming driver.
• 0x0000004C – FATAL_UNHANDLED_HARD_ERROR: A fatal serious error occured before an error handler was available. Registry data structure files are corrupt or missing.
• 0x0000004D – NO_PAGES_AVAILABLE: No free pages available to continue operations. The culprit is always a device driver.
• 0x0000004E – PFN_LIST_CORRUPT: The Page Frame Number (PFN) list is corrupted. Caused by physical memory function failure or improperly installed drivers.
• 0x0000004F – NDIS_INTERNAL_ERROR: NDIS (Network Driver Interface Specification) driver internal error. Ensure the latest network card drivers are installed.
• 0x00000050 – PAGE_FAULT_IN_NONPAGED_AREA: Invalid nonpaged system memory was referenced. Commonly related to bad RAM or disk bad sectors.
• 0x00000051 – REGISTRY_ERROR: A severe registry error occurred. The Windows registry database is corrupted or inaccessible.
• 0x00000052 – MAILSLOT_FILE_SYSTEM: A problem with the mailslot file system. Rare in modern systems.
• 0x00000053 – NO_BOOT_DEVICE: The system cannot find a boot device. Check disk connections, BIOS/UEFI configuration, and boot partition integrity.
• 0x00000054 – LM_SERVER_INTERNAL_ERROR: LAN Manager (LM) server internal error. Related to networking and file sharing.
• 0x00000055 – DATA_COHERENCY_EXCEPTION: A data coherency problem on multiprocessor systems. Rarely occurs.
• 0x00000056 – INSTRUCTION_COHERENCY_EXCEPTION: An instruction coherency problem on multiprocessor systems. Rarely occurs.
• 0x00000057 – XNS_INTERNAL_ERROR: Xerox Network Systems (XNS) protocol internal error. Rarely occurs.
• 0x00000058 – FTDISK_INTERNAL_ERROR: The system was booted from the wrong copy of a mirrored partition. Related to fault-tolerant disks.
• 0x00000059 – PINBALL_FILE_SYSTEM: A problem in the Pinball file system. Related to a specialized file system from early Windows NT era.
• 0x0000005A – CRITICAL_SERVICE_FAILED: A critical system service failed to start. Prevents the system from booting completely.
• 0x0000005B – SET_ENV_VAR_FAILED: Failed to set a system environment variable. Rarely occurs.
• 0x0000005C – HAL_INITIALIZATION_FAILED: Hardware Abstraction Layer (HAL) initialization failed. Mismatch between the HAL and the hardware.
• 0x0000005D – UNSUPPORTED_PROCESSOR: The computer attempted to run Windows on an unsupported processor. Occurs when installing the OS on a CPU that is too old or incompatible.
• 0x0000005E – OBJECT_INITIALIZATION_FAILED: System object initialization failed. Rarely occurs.
• 0x0000005F – SECURITY_INITIALIZATION_FAILED: Security subsystem initialization failed. Prevents the system from starting securely.
• 0x00000060 – PROCESS_INITIALIZATION_FAILED: System process initialization failed. Rarely occurs.
• 0x00000061 – HAL1_INITIALIZATION_FAILED: The second phase of HAL initialization failed. Rarely occurs.
• 0x00000062 – OBJECT1_INITIALIZATION_FAILED: The second phase of system object initialization failed. Rarely occurs.
• 0x00000063 – SECURITY1_INITIALIZATION_FAILED: The second phase of security initialization failed. Rarely occurs.
• 0x00000064 – SYMBOLIC_INITIALIZATION_FAILED: Symbolic link initialization failed. Rarely occurs.
• 0x00000065 – MEMORY1_INITIALIZATION_FAILED: Memory manager initialization failed. Rarely occurs.
• 0x00000066 – CACHE_INITIALIZATION_FAILED: Cache manager initialization failed. Rarely occurs.
• 0x00000067 – CONFIG_INITIALIZATION_FAILED: Registry configuration failed. Unable to load or process the system registry hive.
• 0x00000068 – FILE_INITIALIZATION_FAILED: File system initialization failed. Rarely occurs.
• 0x00000069 – IO1_INITIALIZATION_FAILED: I/O system initialization failed for some reason. The I/O subsystem could not start.
• 0x0000006A – LPC_INITIALIZATION_FAILED: Local Procedure Call initialization failed. Rarely occurs.
• 0x0000006B – PROCESS1_INITIALIZATION_FAILED: Windows operating system initialization failed during the process phase. Boot critical process could not start.
• 0x0000006C – REFMON_INITIALIZATION_FAILED: Reference Monitor initialization failed. Rarely occurs.
• 0x0000006D – SESSION1_INITIALIZATION_FAILED: First session initialization failed. Failed to create the initial system session.
• 0x0000006E – SESSION2_INITIALIZATION_FAILED: Second session initialization failed. Failed to create an additional session during boot.
• 0x0000006F – SESSION3_INITIALIZATION_FAILED: Third session initialization failed. Rarely occurs.
• 0x00000070 – SESSION4_INITIALIZATION_FAILED: Fourth session initialization failed. Rarely occurs.
• 0x00000071 – SESSION5_INITIALIZATION_FAILED: Fifth session initialization failed. Rarely occurs.
• 0x00000072 – ASSIGN_DRIVE_LETTERS_FAILED: Failed to assign drive letters to volumes. The system could not map partitions to drive letters.
• 0x00000073 – CONFIG_LIST_FAILED: A top-level registry key could not be linked in the registry tree. Corruption of the SYSTEM registry hive.
• 0x00000074 – BAD_SYSTEM_CONFIG_INFO: There is an error in the registry. The SYSTEM hive file is corrupt or contains invalid configuration.
• 0x00000075 – CANNOT_WRITE_CONFIGURATION: The registry pool SYSTEM file could not be converted to a mapped file. Failed to write boot configuration.
• 0x00000076 – PROCESS_HAS_LOCKED_PAGES: A driver failed to release locked pages after an I/O operation. Memory leak in a kernel driver.
• 0x00000077 – KERNEL_STACK_INPAGE_ERROR: A kernel data page requested from the paging file could not be read into memory. Bad sector in the pagefile or disk failure.
• 0x00000078 – PHASE0_EXCEPTION: An exception occurred during phase 0 of kernel initialization. Rarely occurs.
• 0x00000079 – MISMATCHED_HAL: The Hardware Abstraction Layer (HAL) revision or configuration does not match the kernel or computer. Occurs after a CPU/motherboard upgrade without a clean install.
• 0x0000007A – KERNEL_DATA_INPAGE_ERROR: A kernel data page could not be read from the pagefile. Similar to 0x77, specific to non-stack kernel data.
• 0x0000007B – INACCESSIBLE_BOOT_DEVICE: The system lost access to the system partition during startup. Corrupt disk driver, change in SATA mode (IDE/AHCI/RAID), or disk failure.
• 0x0000007C – BUGCODE_NDIS_DRIVER: A problem with an NDIS (Network Driver Interface Specification) driver. A network driver caused a kernel crash.
• 0x0000007D – INSTALL_MORE_MEMORY: Not enough physical memory to start Windows. RAM not detected or insufficient for boot.
• 0x0000007E – SYSTEM_THREAD_EXCEPTION_NOT_HANDLED: A system thread generated an exception not caught by an error handler. Mirror of 0x1E on a system thread.
• 0x0000007F – UNEXPECTED_KERNEL_MODE_TRAP: The CPU generated a trap that the kernel failed to catch. CPU overheating, overclocking, or hardware failure.
• 0x00000080 – NMI_HARDWARE_FAILURE: A Non-Maskable Interrupt indicates severe hardware failure. Often related to RAM, CPU, or power supply.
• 0x00000081 – SPIN_LOCK_INIT_FAILURE: Failed to initialize a spin lock. Rarely occurs.
• 0x00000082 – DFS_FILE_SYSTEM: A problem with the Distributed File System. Rarely occurs.
• 0x00000083 – OFS_FILE_SYSTEM: Information not available in the source data.
• 0x00000084 – RECOM_DRIVER: Information not available in the source data.
• 0x00000085 – SETUP_FAILURE: A fatal error occurred during Windows Setup. OS installation was interrupted or corrupted.
• 0x0000008B – MBR_CHECKSUM_MISMATCH: Mismatch in the Master Boot Record (MBR) checksum. Virus or malware altering the MBR, or disk corruption.
• 0x0000008E – KERNEL_MODE_EXCEPTION_NOT_HANDLED: A kernel-mode application generated an unhandled exception. Similar to 0x1E and 0x8E.
• 0x0000008F – PP0_INITIALIZATION_FAILED: Plug and Play (PnP) manager could not be initialized. Failed to load a critical PnP driver.
• 0x00000090 – PP1_INITIALIZATION_FAILED: Plug and Play (PnP) manager could not be initialized phase 1. Rarely occurs.
• 0x00000091 – WIN32K_INIT_OR_RIT_FAILURE: Information not available in the source data.
• 0x00000092 – UP_DRIVER_ON_MP_SYSTEM: A uniprocessor-only driver was loaded on a multiprocessor system. An old driver does not support SMP.
• 0x00000093 – INVALID_KERNEL_HANDLE: An invalid or protected handle was passed to NtClose. Corruption of the kernel handle table.
• 0x00000094 – KERNEL_STACK_LOCKED_AT_EXIT: A thread exited while its kernel stack was marked as non-swappable. A driver bug failing to release a stack lock.
• 0x00000095 – PNP_INTERNAL_ERROR: Information not available in the source data.
• 0x00000096 – INVALID_WORK_QUEUE_ITEM: A work queue entry containing a null pointer was removed. A driver work queue bug.
• 0x00000097 – BOUND_IMAGE_UNSUPPORTED: A bound image file is unsupported. Rarely occurs.
• 0x00000098 – END_OF_NT_EVALUATION_PERIOD: The Windows evaluation period has ended. The evaluation system has expired.
• 0x00000099 – INVALID_REGION_OR_SEGMENT: ExInitializeRegion or ExInterlockedExtendRegion was called with invalid parameters. A driver memory bug.
• 0x0000009A – SYSTEM_LICENSE_VIOLATION: A software license agreement has been violated. Invalid or disrupted Windows activation.
• 0x0000009B – UDFS_FILE_SYSTEM: A problem with the Universal Disk Format (UDF) file system. Disk damage or UDF driver issue.
• 0x0000009C – MACHINE_CHECK_EXCEPTION: A fatal machine check exception occurred. Hardware failure of CPU, cache, bus, or motherboard.
• 0x0000009E – USER_MODE_HEALTH_MONITOR: A critical user-mode component failed a health check. Critical user-mode service crash.
• 0x0000009F – DRIVER_POWER_STATE_FAILURE: A driver is in an inconsistent or invalid power state. Failed sleep/hibernate/wake transition.
• 0x000000A0 – INTERNAL_POWER_ERROR: The power policy manager experienced a fatal error. Kernel power manager crash.
• 0x000000A1 – PCI_BUS_DRIVER_INTERNAL: The PCI Bus driver detected an inconsistency in its internal structure. PCI/PCIe configuration problem or hardware issue.
• 0x000000A2 – MEMORY_IMAGE_CORRUPT: Corruption detected in an executable image file in memory. System or driver file corruption in RAM.
• 0x000000A3 – ACPI_DRIVER_INTERNAL: The ACPI driver detected an internal inconsistency. Buggy or incompatible ACPI BIOS.
• 0x000000A4 – CNSS_FILE_SYSTEM_FILTER: A problem with the CNSS file system filter. Rarely occurs.
• 0x000000A5 – ACPI_BIOS_ERROR: The computer’s ACPI BIOS does not fully comply with the specification. ACPI BIOS bug, firmware update needed.
• 0x000000A7 – BAD_EXHANDLE: The kernel-mode handle table detected an inconsistent handle table entry state. Corruption of the extended handle table.
• 0x000000AB – SESSION_HAS_VALID_POOL_ON_EXIT: Session teardown occurred while a session driver still held memory. Memory leak in a session driver.
• 0x000000AC – HAL_MEMORY_ALLOCATION: The Hardware Abstraction Layer (HAL) could not obtain sufficient memory. Insufficient physical memory for HAL operations.
• 0x000000AD – VIDEO_DRIVER_DEBUG_REPORT_REQUEST: The video port created a non-fatal minidump on behalf of the video driver. Debug request from a graphics driver.
• 0x000000B4 – VIDEO_DRIVER_INIT_FAILURE: Windows could not switch to graphics mode. Display driver failed to initialize or VGA hardware is faulty.
• 0x000000B8 – ATTEMPTED_SWITCH_FROM_DPC: An illegal operation was attempted by a Deferred Procedure Call (DPC) routine. A driver attempted a context switch from a DPC.
• 0x000000B9 – CHIPSET_DETECTED_ERROR: The chipset detected an internal error. Motherboard chipset failure.
• 0x000000BA – SESSION_HAS_VALID_VIEWS_ON_EXIT: A session driver still had mapped views when the session was torn down. Memory leak in a session graphics driver.
• 0x000000BB – NETWORK_BOOT_INITIALIZATION_FAILED: Windows failed to boot from the network. PXE boot failure, NIC driver issue, or DHCP configuration problem.
• 0x000000BC – NETWORK_BOOT_DUPLICATE_ADDRESS: A duplicate IP address was assigned to the machine during network boot. IP address conflict in a PXE environment.
• 0x000000BE – ATTEMPTED_WRITE_TO_READONLY_MEMORY: A driver attempted to write to a read-only memory segment. Driver memory access bug.
• 0x000000BF – MUTEX_ALREADY_OWNED: A thread attempted to acquire ownership of a mutex it already owned. Deadlock condition in a driver.
• 0x000000C1 – SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION: A driver wrote to an invalid part of the special pool. Memory corruption detected by Driver Verifier.
• 0x000000C2 – BAD_POOL_CALLER: The current thread made a bad pool request. A driver made an invalid memory allocation request.
• 0x000000C4 – DRIVER_VERIFIER_DETECTED_VIOLATION: A fatal error found by Driver Verifier. A driver violated a kernel rule, often during testing/debugging.
• 0x000000C5 – DRIVER_CORRUPTED_EXPOOL: The system attempted to access invalid memory at too high an IRQL. Corruption of the expanded kernel pool.
• 0x000000C6 – DRIVER_CAUGHT_MODIFYING_FREED_POOL: A driver attempted to access freed pool memory. A use-after-free bug in a driver.
• 0x000000C7 – TIMER_OR_DPC_INVALID: A kernel timer or DPC was found in unauthorized memory. Corruption of timer/DPC structures.
• 0x000000C8 – IRQL_UNEXPECTED_VALUE: The processor’s IRQL was not as it should be. The kernel or a driver changed IRQL incorrectly.
• 0x000000C9 – DRIVER_VERIFIER_IOMANAGER_VIOLATION: A Driver Verifier I/O Verification violation. A driver violated I/O manager rules.
• 0x000000CA – PNP_DETECTED_FATAL_ERROR: The Plug and Play Manager encountered a severe error. A problematic PnP driver or hardware conflict.
• 0x000000CB – DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS: A driver failed to release locked pages after an I/O operation. Similar to 0x76, specific to locked pages.
• 0x000000CC – PAGE_FAULT_IN_FREED_SPECIAL_POOL: The system referenced memory that was previously freed. Use-after-free within a special pool (Driver Verifier).
• 0x000000CD – PAGE_FAULT_BEYOND_END_OF_ALLOCATION: The system accessed memory beyond the end of a pool allocation. Buffer overrun by a driver.
• 0x000000CE – DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS: A driver failed to cancel pending operations before unloading. Unsafe driver unload.
• 0x000000CF – TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE: A driver was improperly ported to a terminal server. Driver incompatible with multi-session.
• 0x000000D0 – DRIVER_CORRUPTED_MMPOOL: The system attempted to access invalid memory at too high an IRQL. Corruption within the paged or nonpaged pool.
• 0x000000D1 – DRIVER_IRQL_NOT_LESS_OR_EQUAL: A kernel-mode driver attempted to access pageable memory at too high an IRQL. One of the most common driver-related BSODs.
• 0x000000D2 – BUGCODE_ID_DRIVER: A problem with an NDIS driver. A specific NDIS driver error.
• 0x000000D3 – DRIVER_PORTION_MUST_BE_NONPAGED: The system attempted to access pageable memory at too high an IRQL. Driver code/data should be nonpaged but was paged.
• 0x000000D4 – SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD: A driver did not cancel pending operations before unloading. Detected during a system scan at high IRQL.
• 0x000000D5 – DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL: A driver referenced memory that was previously freed in the special pool.
• 0x000000D6 – DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION: A driver accessed memory beyond the end of its pool allocation. Driver buffer overrun.
• 0x000000D7 – DRIVER_UNMAPPING_INVALID_VIEW: A driver attempted to unmap an address that was not mapped. Driver memory mapping bug.
• 0x000000D8 – DRIVER_USED_EXCESSIVE_PTES: No more System Page Table Entries (PTEs) are available. A driver used too much mapped memory.
• 0x000000D9 – LOCKED_PAGES_TRACKER_CORRUPTION: The internal locked pages tracker structure is corrupted. Corruption within the locked pages tracker.
• 0x000000DA – SYSTEM_PTE_MISUSE: A Page Table Entry (PTE) routine was misused. Abuse of system PTEs by a driver.
• 0x000000DB – DRIVER_CORRUPTED_SYSPTES: An attempt to touch memory at an invalid IRQL, possibly due to system PTE corruption. Corruption of system PTE tables.
• 0x000000DC – DRIVER_INVALID_STACK_ACCESS: A driver accessed a stack address below the thread’s stack pointer. Stack underrun/overrun by a driver.
• 0x000000DE – POOL_CORRUPTION_IN_FILE_AREA: A driver had corrupted pool memory used to store pages destined for disk. Pool corruption for file cache.
• 0x000000DF – IMPERSONATING_WORKER_THREAD: A work item did not disable impersonation before completing. A driver impersonation bug.
• 0x000000E0 – ACPI_BIOS_FATAL_ERROR: A computer component is damaged. ACPI BIOS fatal failure, BIOS update needed.
• 0x000000E1 – WORKER_THREAD_RETURNED_AT_BAD_IRQL: A worker thread completed and returned with IRQL >= DISPATCH_LEVEL. Worker thread bug.
• 0x000000E2 – MANUALLY_INITIATED_CRASH: The user deliberately initiated a crash dump from the debugger or keyboard. Manual crash (debug).
• 0x000000E3 – RESOURCE_NOT_OWNED: A thread attempted to release a resource it did not own. Driver resource management bug.
• 0x000000E4 – WORKER_INVALID: Memory that should not contain an executive worker item did contain such an item. Work queue corruption.
• 0x000000E6 – DRIVER_VERIFIER_DMA_VIOLATION: A Driver Verifier DMA Verification violation. A driver violated DMA rules.
• 0x000000E7 – INVALID_FLOATING_POINT_STATE: The floating-point state saved in a thread is invalid. FPU state corruption.
• 0x000000E8 – INVALID_CANCEL_OF_FILE_OPEN: An invalid file object was passed to IoCancelFileOpen. File system filter driver bug.
• 0x000000E9 – ACTIVE_EX_WORKER_THREAD_TERMINATION: An active executive worker thread is being terminated. Unexpected termination of an executive worker thread.
• 0x000000EA – THREAD_STUCK_IN_DEVICE_DRIVER: A thread in a device driver is spinning endlessly. Driver infinite loop, often a display driver (TDR).
• 0x000000EB – DIRTY_MAPPED_PAGES_CONGESTION: No free pages are available to continue operations. Out of memory for dirty mapped pages.
• 0x000000EC – SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT: Session teardown occured while a session driver still held special pool memory. Special pool memory leak in a session.
• 0x000000ED – UNMOUNTABLE_BOOT_VOLUME: The I/O subsystem attempted to mount the boot volume and failed. Boot volume file system severely corrupted, often run chkdsk /f.
• 0x000000EF – CRITICAL_PROCESS_DIED: A critical system process died. Processes like csrss.exe or winlogon.exe crashed.
• 0x000000F1 – SCSI_VERIFIER_DETECTED_VIOLATION: A Driver Verifier SCSI Verification violation. A SCSI driver violated rules.
• 0x000000F3 – DISORDERLY_SHUTDOWN: Windows could not shut down due to lack of memory. Out of memory during shutdown.
• 0x000000F4 – CRITICAL_OBJECT_TERMINATION: A process or thread critical to system operation exited or was terminated unexpectedly. Similar to 0xEF, for kernel objects.
• 0x000000F5 – FLTMGR_FILE_SYSTEM: An unrecoverable failure occurred in the Filter Manager. File system filter driver crash (antivirus, backup, encryption).
• 0x000000F6 – PCI_VERIFIER_DETECTED_VIOLATION: An error in the BIOS or other device verified by a PCI driver. PCI hardware or driver violation.
• 0x000000F7 – DRIVER_OVERRAN_STACK_BUFFER: A driver overran a stack-based buffer. Stack buffer overflow in a driver.
• 0x000000F8 – RAMDISK_BOOT_INITIALIZATION_FAILED: An initialization failure occured while attempting to boot from a RAM disk. Windows PE or boot from RAM failure.
• 0x000000F9 – DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN: A driver returned STATUS_REPARSE to an IRP_MJ_CREATE request without an additional name. File system reparse driver bug.
• 0x000000FA – HTTP_DRIVER_CORRUPTED: The kernel HTTP driver (Http.sys) reached a corrupted and unrecoverable state. Corruption within the HTTP kernel driver.
• 0x000000FC – ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY: An attempt to execute non-executable memory. Data Execution Prevention (DEP) violation.
• 0x000000FD – DIRTY_NOWRITE_PAGES_CONGESTION: No free pages are available to continue basic system operations. Out of memory for non-writeable pages.
• 0x000000FE – BUGCODE_USB_DRIVER: An error in a Universal Serial Bus (USB) driver. USB driver crash or USB hardware failure.
• 0x000000FF – RESERVE_QUEUE_OVERFLOW: An attempt to insert a new item into the reserve queue caused the queue to overflow. Kernel reserve queue overflow.
• 0x00000100 – LOADER_BLOCK_MISMATCH: The loader block is invalid or does not match the system being loaded. OS loader corruption.
• 0x00000101 – CLOCK_WATCHDOG_TIMEOUT: The expected clock interrupt on a secondary processor in a multiprocessor system was not received within the allocated interval. CPU hung or unresponsive (multi-processor systems).
• 0x00000103 – MUP_FILE_SYSTEM: The Multiple UNC Provider encountered invalid or unexpected data. Network redirector problem or MUP corruption.
• 0x00000104 – AGP_INVALID_ACCESS: The GPU wrote to an Accelerated Graphics Port (AGP) memory range that was not previously committed. AGP/graphics driver bug.
• 0x00000105 – AGP_GART_CORRUPTION: The Graphics Aperture Remapping Table (GART) is corrupted. AGP GART corruption, often graphics or chipset driver.
• 0x00000106 – AGP_ILLEGALLY_REPROGRAMMED: The Accelerated Graphics Port (AGP) hardware was reprogrammed by an unauthorized agent. Illegal AGP programming.
• 0x00000108 – THIRD_PARTY_FILE_SYSTEM_FAILURE: An unrecoverable problem in a third-party file system or file system filter. Antivirus, encryption, or backup filter crash.
• 0x00000109 – CRITICAL_STRUCTURE_CORRUPTION: The kernel detected critical kernel code or data corruption. Kernel integrity violation, possibly malware rootkit.
• 0x0000010A – APP_TAGGING_INITIALIZATION_FAILED: App Tagging initialization failed. Rarely occurs, related to memory tagging.
• 0x0000010C – FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION: A violation detected in a File System Run-time library (FsRtl) Extra Create Parameter (ECP) package. Filter driver ECP bug.
• 0x0000010D – WDF_VIOLATION: Kernel-Mode Driver Framework (KMDF) detected an error in a framework-based driver. WDF driver violation.
• 0x0000010E – VIDEO_MEMORY_MANAGEMENT_INTERNAL: The video memory manager encountered an unrecoverable condition. Video memory manager crash (dxgmms1.sys).
• 0x0000010F – RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED: The kernel transaction manager detected that a kernel-mode resource manager raised an exception. Kernel Transaction Manager failure.
• 0x00000111 – RECURSIVE_NMI: A Non-Maskable Interrupt (NMI) occurred while a previous NMI was in progress. Hardware NMI storm, often hardware failure.
• 0x00000112 – MSRPC_STATE_VIOLATION: The Msrpc.sys driver initiated a stop code. RPC kernel driver state corruption.
• 0x00000113 – VIDEO_DXGKRNL_FATAL_ERROR: The DirectX Graphics Kernel (dxgkrnl) detected a fatal violation. Critical graphics kernel error.
• 0x00000114 – VIDEO_SHADOW_DRIVER_FATAL_ERROR: A video shadow driver detected a fatal violation. Graphics shadow driver crash.
• 0x00000115 – AGP_INTERNAL: The Accelerated Graphics Port (AGP) driver detected an internal violation. AGP driver internal error.
• 0x00000116 – VIDEO_TDR_ERROR: An attempt to reset the display driver and recover from a timeout failed. Timeout Detection and Recovery failed (display driver hung).
• 0x00000117 – VIDEO_TDR_TIMEOUT_DETECTED: The display driver failed to respond in a timely manner. TDR detected (display driver timeout).
• 0x00000119 – VIDEO_SCHEDULER_INTERNAL_ERROR: The video scheduler detected a fatal violation. Video scheduler error.
• 0x0000011A – EM_INITIALIZATION_FAILURE: Energy Manager initialization failed. Rarely occurs.
• 0x0000011B – DRIVER_RETURNED_HOLDING_CANCEL_LOCK: A driver returned from a cancel routine while holding the global cancel lock. Deadlock condition in cancel logic.
• 0x0000011C – ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE: An attempt to write to read-only storage of the configuration manager. Illegal write to a protected registry hive.
• 0x0000011D – EVENT_TRACING_FATAL_ERROR: The Event Tracing subsystem experienced an unexpected fatal error. Event Tracing for Windows (ETW) crash.
• 0x00000121 – DRIVER_VIOLATION: A driver caused a general violation. General driver violation.
• 0x00000122 – WHEA_INTERNAL_ERROR: An internal error in the Windows Hardware Error Architecture (WHEA). WHEA infrastructure error.
• 0x00000124 – WHEA_UNCORRECTABLE_ERROR: A fatal uncorrectable hardware error occurred. Hardware failure reported by WHEA (CPU, memory, bus).
• 0x00000127 – PAGE_NOT_ZERO: A page that should have been filled with zeros was not. Hardware memory error or the OS modified a page after freeing it.
• 0x0000012B – FAULTY_HARDWARE_CORRUPTED_PAGE: A single-bit error was found on this page. Memory hardware error (bad RAM).
• 0x0000012C – EXFAT_FILE_SYSTEM: A problem with the Extended File Allocation Table (exFAT) file system. exFAT volume damage or driver issue.
• 0x00000133 – DPC_WATCHDOG_VIOLATION: A Deferred Procedure Call (DPC) exceeded the allowed time. A driver DPC ran too long, causing a system hang.
• 0x00000138 – GPIO_CONTROLLER_DRIVER_ERROR: A General Purpose Input/Output (GPIO) controller driver error. Chipset or embedded controller driver error.
• 0x00000139 – KERNEL_SECURITY_CHECK_FAILURE: A kernel security check failed (Stack cookie corruption). Buffer overrun detected by the kernel (/GS protection).
• 0x00000144 – BUGCODE_USB3_DRIVER: A USB 3.0/3.1 driver error. xHCI or USB 3.0 host controller driver crash.
• 0x0000014B – SOC_SUBSYSTEM_FAILURE: A System on Chip (SoC) subsystem failure. For ARM or embedded Windows devices.
• 0x1000007E – SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M: Similar to 0x7E, occurs on systems with different memory configurations.
• 0x1000007F – UNEXPECTED_KERNEL_MODE_TRAP_M: Similar to 0x7F, occurs on systems with different memory configurations.
• 0x1000008E – KERNEL_MODE_EXCEPTION_NOT_HANDLED_M: Similar to 0x8E, occurs on systems with different memory configurations.
• 0x100000EA – THREAD_STUCK_IN_DEVICE_DRIVER_M: Similar to 0xEA, occurs on systems with different memory configurations.
• 0xC0000218 – STATUS_CANNOT_LOAD_REGISTRY_FILE: A registry file could not be loaded. SYSTEM or SOFTWARE hive is corrupt or missing.
• 0xC000021A – STATUS_SYSTEM_PROCESS_TERMINATED: An error in a critical user-mode subsystem (csrss.exe or winlogon.exe).
• 0xC0000221 – STATUS_IMAGE_CHECKSUM_MISMATCH: A driver or system DLL is corrupt (checksum mismatch). System file corrupted or modified.
• 0xDEADDEAD – MANUALLY_INITIATED_CRASH1: The user deliberately initiated a crash dump (manual kernel panic). Debug or “BlueScreen” from the keyboard.

Tip for Professionals and Technicians: When facing recurring BSOD, note the stop code and its parameters. Use the Windows Debugger (WinDbg) to analyze the generated dump file (MEMORY.DMP). Prioritize checking recently updated drivers and run diagnostic memory tests (Windows Memory Diagnostic) along with disk health checks using CHKDSK and SMART tools.

In conclusion, the Blue Screen of Death is not the end of your device, but a valuable diagnostic clue. By understanding BSOD error codes and applying a systematic approach, downtime can be minimized. Always prioritize official information sources like Microsoft documentation and relevant hardware developer forums for specific solutions.

Read Also: Initial Symptoms of a Damaged Starting Hard Disk You Need to Know

Reference Sources:
1. Microsoft. (2023). Bug Check Code Reference. Microsoft Docs.
2. Lifewire. (2023). Blue Screen of Death (BSOD) Meanings. Lifewire.