| Error Message | Details |
| APC_INDEX_MISMATCH | This BSOD error contains the bug check value of 0x00000001. It means there is a mismatch in the APC state index. “Some Windows users reported that this error occurred while printing PDF files, working on Excel, and opening AutoCad.” - Source |
| IRQL_NOT_GREATER_OR_EQUAL | This blue screen of death Windows 10 error appears with a stop code 0x00000009. It usually occurs due to faulty graphics card drivers, invalid registries, or corrupted system files. |
| IRQL_NOT_LESS_OR_EQUAL | This BSOD error appears with a bug check value of 0x0000000A. It means the Windows or a Kernel-mode driver accessed the paged memory at Dispatch_Level or above. “Users reported that their system started crashing with IRQL_NOT_LESS_OR_EQUAL error when the system was idle. Also, it made the system completely unbootable when they tried to run a system update to fix the issue.” - Source |
| KMODE_EXCEPTION_NOT_HANDLED | This BSOD error code shows up a value of 0x0000001E. It may cause system to restart unexpectedly or not boot at all. “Users reported that this error occurred at the initial stage of booting system. Even enabling the Safe Mode doesn’t help.” - Source |
| DEVICE_QUEUE_NOT_BUSY | This BSOD error is quite uncommon and appears with the bug check value of 0x00000002. |
| INVALID_AFFINITY_SET | This BSOD appears with a bug check value of 0x00000003. It may occur majorly due to hardware problems. |
| INVALID_DATA_ACCESS_TRAP | This BSOD error indicates an incorrect data access trap. It appears with a bug check value of 0x00000004. “Some users reported that they found difficulty in upgrading to the latest version of Windows due to this error.”- Source |
| IRQL_NOT_DISPATCH_LEVEL | This error comes up with a bug check value of 0x00000008. |
| NO_EXCEPTION_HANDLING_SUPPORT | This BSOD error appears with a stop code 0x0000000B. It may occur due to faulty device drivers. Sometimes, it is difficult to figure out the cause behind such errors, as reported by some Windows users.- Source |
| MAXIMUM_WAIT_OBJECTS_EXCEEDED | This BSOD error has a bug check value of 0x0000000C. The error shows that the current thread exceeded the permitted number of wait objects. It may occur due to improper use of KeWaitForMultipleObjects or FsRtlCancellableWaitForMultipleObjects. |
| MUTEX_LEVEL_NUMBER_VIOLATION | This BSOD error appears with a stop code 0x0000000D. |
| NO_USER_MODE_CONTEXT | This error has a bug check value of 0x0000000E. It appears when the control returns from the initial thread procedure to start a system thread. |
| SPIN_LOCK_ALREADY_OWNED | When you encounter this BSOD error, it indicates that a request for a spin lock had been initiated when the spin lock was already owned. It appears with a stop code 0x0000000F. |
| THREAD_NOT_MUTEX_OWNER | It comes with a bug check value of 0x00000011. “As users reported, corrupted RAM may cause this error.” - Source |
| WORKER_THREAD_RETURNED _WHILE_ATTACHED_TO_SILO | This BSOD bug check has a value of 0x0000019A. This error occurs when a worker thread is attached to a silo and does not detach before returning. |
| TRAP_CAUSE_UNKNOWN | It indicates that an unknown exception has occurred. This error appears with stop code 0x00000012. |
| CID_HANDLE_DELETION | This error shows a blue screen and appears with a bug check value of 0x00000017. |
| REFERENCE_BY_POINTER | It shows a stop code - 0x00000018 and indicates that an object's reference count is illegal for the current state of the thing. |
| BAD_POOL_HEADER | This bug check has a value of 0x00000019. It indicates a corrupted pool header. Different parameters of this error show other causes of this error. |
| MEMORY_MANAGEMENT | It appears with a stop code 0x0000001A. This error means that a severe memory management error has occurred. |
| PFN_REFERENCE_COUNT | This BSOD error has a value of 0x0000001C. |
| KERNEL_APC_PENDING_DURING_EXIT | This BSOD error appears with a stop code - 0x00000020. It indicates that an asynchronous procedure call (APC) was still pending when a thread exited. Users reported that they encountered this error upon signing out or shutting down their system. - Source Some users reported that they encountered this error with their entirely new Windows systems. – Source |
| QUOTA_UNDERFLOW | It usually appears with a stop code - 0x00000021. It specifies that a quota charge has been mishandled by returning more quota to a particular block as compared to the previous charge. Some users reported that they experienced this error after installing Windows 10 Home edition. - Source |
| FAT_FILE_SYSTEM | When this error occurs, it indicates that there is a problem with the FAT file system. It appears with a stop code - 0x00000023. It may make your system stuck at a booting loop, as reported by some users. - Source |
| NTFS_FILE_SYSTEM | This BSOD bug check has a value of 0x00000024. It appears when there is a problem with NTFS.sys, a driver file that helps the system to read/write to NTFS hard drives. |
| CDFS_FILE_SYSTEM | This error appears when a problem occurs in the CD file system. You may see this error with a stop code - 0x00000026. |
| Stop Code: 0x00000024 | It may also contain different stop codes, including 0X00000024 (0X0000000000190494, 0xFFFFFA800471DA70, 0XFFFFFFFFC0000102, 0X0000000000000000). |
| CORRUPT_ACCESS_TOKEN | The error appears with a stop code - 0x00000028. |
| INCONSISTENT_IRP | It indicates an IRP was found to contain conflicting information. It has a value of 0x0000002A. This error means some fields of the IRP were inconsistent with the remaining state of the IRP. |
| PANIC_STACK_SWITCH | This BSOD error shows up with a value of 0x0000002B. It specifies that a kernel-mode stack was overrun. |
| DATA_BUS_ERROR | When you see this error, it means there is a parity error in the system memory. It shows up with the value of 0x0000002E. It may be caused by a hardware issue, such as configuration issue, defective hardware, or incompatible hardware. |
| SET_OF_INVALID_CONTEXT | This error means a stack pointer in a trap frame had an invalid value. It has a value of 0x00000030. “It occurs when some routine attempts to set the stack pointer in the trap frame to a lower value than the current stack pointer value.” – Source |
| PHASE0_INITIALIZATION_FAILED | It has a stop code - 0x00000031. This error indicates a failed system initialization. |
| UNEXPECTED_INITIALIZATION_CALL | This BSOD error appears with code 0x00000033. |
| BAD SYSTEM CONFIG INFO | It occurs when there is a problem with the registry. This bug check has a value of 0x00000074. |
| NO_MORE_IRP_STACK_LOCATIONS | This BSOD occurs when the IoCallDriver packet has no more stack locations remaining. It has a value of 0x00000035. |
| DEVICE_REFERENCE_COUNT_NOT_ZERO | This BSOD has a value of 0x00000036. It shows that a driver attempted to delete a device object that still had a positive reference count. |
| FLOPPY_INTERNAL_ERROR | It appears less frequently and contains a value of 0x00000037. |
| SERIAL_DRIVER_INTERNAL | This BSOD error is not common. |
| SYSTEM_EXIT_OWNED_MUTEX | This error shows a stop code 0x00000039. It indicates that the worker routine returned without releasing the mutex object that it owned. |
| SYSTEM_UNWIND_PREVIOUS_USER | This BSOD error contains the value of 0x0000003A. |
| BSOD SYSTEM SERVICE EXCEPTION | This BSOD error has a value of 0x0000003B. It designates that an exception happened while executing a routine that transitions from non-privileged code to privileged code. |
| MULTIPROCESSOR_CONFIGURATION _NOT_SUPPORTED | This error appears with a stop code - 0x0000003E. It shows that the system has multiple processors but they are asymmetric in relation to one another. |
| NO_MORE_SYSTEM_PTES | This blue screen error is the result of a system that has performed too many I/O actions. It has resulted in fragmented system page table entries (PTE). It appears with a stop code 0x0000003F. |
| TARGET_MDL_TOO_SMALL | This BSOD error appears with a stop code 0x00000040. It indicates that a driver has improperly used IoBuildPartialMdl. It is majorly a driver bug. You may encounter this error while browsing the internet, updating your system, or installing a Windows update. - Source |
| MUST_SUCCEED_POOL_EMPTY | With an error value of 0x00000041, this BSOD error indicates that a kernel-mode thread has requested too much must-succeed pool. You can try to replace or rewrite the driver to fix this issue. – Source |
| ATDISK_DRIVER_INTERNAL | This error appears with a bug check value of 0x00000042. |
| NO_SUCH_PARTITION | This BSOD error contains the value of 0x00000043. |
| MULTIPLE_IRP_COMPLETE_REQUESTS | This blue screen error shows up with a value of 0x00000044. It specifies that a driver has tried to request an IRP be completed that is already complete. Sometimes, even installing the latest driver won’t help fix the error, making it a tough bug to fix. – Source |
| INSUFFICIENT_SYSTEM_MAP_REGS | It is an uncommon bug check that has a value of 0x00000045. |
| DEREF_UNKNOWN_LOGON_SESSION | This BSOD error appears with a value of 0x00000046. |
| REF_UNKNOWN_LOGON_SESSION | It occurs less frequently and contains a value of 0x00000047. |
| CANCEL_STATE_IN_COMPLETED_IRP | It is a common BSOD error that designates an I/O request packet (IRP) was completed and then was subsequently canceled. It comes with a value of 0x00000048. |
| PAGE_FAULT_WITH_INTERRUPTS_OFF | This error appears with a bug check value of 0x00000049. |
| IRQL_GT_ZERO_AT_SYSTEM_SERVICE | This BSOD error appears with a value of 0x0000004A. This error indicates a thread returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL. |
| STREAMS_INTERNAL_ERROR | This blue screen error appears with a value of 0x0000004B. |
| FATAL_UNHANDLED_HARD_ERROR | This error shows up with a value of 0x0000004C. |
| NO_PAGES_AVAILABLE | This error indicates that there are no free pages available to continue operations. It possesses a value of 0x0000004D. |
| PFN_LIST_CORRUPT | This BSOD error has a value of 0x0000004E. It shows that the page frame number (PFN) list is corrupted. This error may occur on your system quite frequently. - Source |
| KERNEL_DATA_INPAGE_ERROR | This BSOD error consists of a value of 0x0000004F. |
| PAGE_FAULT_IN_NONPAGED_AREA | This BSOD error appears with a value of 0x00000050. It indicates that invalid system memory has been referenced. |
| REGISTRY_ERROR | This BSOD error indicates that a severe registry error has occurred. It shows up with a stop code 0x00000051. |
| MAILSLOT_FILE_SYSTEM | This error shows up with a stop code 0x00000052. |
| NO_BOOT_DEVICE | The error shows up a value of 0x00000053. |
| LM_SERVER_INTERNAL_ERROR | This BSOD error occurs with a value of 0x00000054. |
| DATA_COHERENCY_EXCEPTION | This blue screen error appears with a value of 0x00000055. |
| INSTRUCTION_COHERENCY_EXCEPTION | It appears with a stop code 0x00000056. |
| XNS_INTERNAL_ERROR | A less common error that has a value of 0x00000057. |
| FTDISK_INTERNAL_ERROR | If the system is booted from the wrong copy of a mirrored partition, then you may encounter this error. It appears with a bug check value of 0x00000058. |
| PINBALL_FILE_SYSTEM | This BSOD error indicates that a problem occurred in the Pinball file system and appears with a value of 0x00000059. |
| CRITICAL_SERVICE_FAILED | This error shows up with stop code 0x0000005A. |
| SET_ENV_VAR_FAILED | The error appears with a value of 0x0000005B. |
| 0x0000005C | This BSOD error usually occurs due to device driver or hardware issues. |
| UNSUPPORTED_PROCESSOR | This blue screen of death Windows 10 error contains the value 0x0000005D. It designates that the computer is attempting to run Windows on an unsupported processor. |
| OBJECT_INITIALIZATION_FAILED | This BSOD error possesses a value of 0x0000005E. |
| SECURITY_INITIALIZATION_FAILED | This blue screen error displays with a stop code 0x0000005F. |
| SYMBOLIC_INITIALIZATION_FAILED | This blue screen error consists of a stop code 0x00000064. |
| MEMORY1_INITIALIZATION_FAILED | This BSOD error appears with a stop code 0x00000065. |
| CACHE_INITIALIZATION_FAILED | This BSOD error shows up with a stop code 0x00000066. |
| CONFIG_INITIALIZATION_FAILED | When the registry configuration fails, you may encounter this error with a stop code - 0x00000067. |
| IO1_INITIALIZATION_FAILED | This blue screen error designates that the initialization of the I/O system failed for some reason. It has a value of 0x00000069. |
| LPC_INITIALIZATION_FAILED | This blue screen of death error consists of a value of 0x0000006A. |
| PROCESS1_INITIALIZATION_FAILED | This BSOD error contains a value of 0x0000006B. It means that the initialization of the Microsoft Windows operating system has failed. |
| REFMON_INITIALIZATION_FAILED | It consists of a value of 0x0000006C. |
| SESSION1_INITIALIZATION_FAILED | When the initialization of the Microsoft Windows operating system fails, you may encounter this BSOD error with a stop code 0x0000006D. |
| SESSION3_INITIALIZATION_FAILED | With a value of 0x0000006F, this bug check specifies the initialization of the Microsoft Windows operating system. |
| SESSION4_INITIALIZATION_FAILED | This blue screen error appears with a stop code 0x00000070. It designates that the initialization of the Microsoft Windows operating system has failed. |
| 0x00000071 | This BSOD error shows that the initialization of the Microsoft Windows operating system has failed. |
| 0x00000072 | This BSOD error is generally caused by irregular Windows registry entries or incorrect system settings. |
| CONFIG_LIST_FAILED | This BSOD error shows up with a stop code 0x00000073 and indicates that one of the top-level registry keys, also known as core system hives, cannot be linked in the registry tree. |
| CANNOT_WRITE_CONFIGURATION | This BSOD error shows up with a stop code 0x00000075. When you see this error, it means that the SYSTEM registry hive file cannot be converted to a mapped file. It usually occurs if the system is out of the pool and the Windows operating system cannot reopen the hive.- Source |
| PROCESS_HAS_LOCKED_PAGES | This error shows you the value of 0x00000076. It indicates that a driver has failed to release locked pages after an I/O operation or that it attempted to unlock pages that were already opened. This error may occur while loading/playing video games or even watching YouTube. - Source |
| KERNEL_STACK_INPAGE_ERROR | When the requested page of kernel data from the paging file could not be read into memory, it appears with a value of 0x00000077. It may also appear with other stop codes - 0x00000077 (0x00000001, 0x00000000, 0x00000000, 0xF79DFD24). However, finding the cause of it may seem quite tricky. - Source |
| PHASE0_EXCEPTION | This BSOD error appears with a value of 0x00000078. |
| MISMATCHED_HAL | With a stop code 0x00000079, this BSOD specifies that the HAL (Hardware Abstraction Layer) revision level or configuration does not match the kernel or the computer. |
| INACCESSIBLE_BOOT_DEVICE | This BSOD on Windows 10 occurs with a value of 0x0000007B. It specifies that the Microsoft Windows operating system has lost access to the system partition during startup. |
| BUGCODE_NDIS_DRIVER | This BSOD appears with a value of 0x0000007C, indicating that a problem occurred with an NDIS driver. |
| INSTALL_MORE_MEMORY | This BSOD appears with a value of 0x0000007D. It indicates that there is not enough memory to start the Microsoft Windows operating system. |
| SYSTEM_THREAD_EXCEPTION_NOT_HANDLED | This BSOD error means that a system thread generated an exception that the error handler did not catch. It appears with a value of 0x0000007E. |
| UNEXPECTED_KERNEL_MODE_TRAP | It shows up with a bug check value of 0x0000007F. It designates that the Intel CPU generated a trap and the kernel failed to catch this trap. It usually occurs after installing faulty or mismatched hardware (memory). – Source |
| NMI_HARDWARE_FAILURE | It contains a bug check value of 0x00000080 and occurs due to malfunctioning hardware. This error may also occur when a Non-Maskable Interrupt (NMI) is triggered. - Source |
| SPIN_LOCK_INIT_FAILURE | This BSOD error appears with a value of 0x00000081. |
| DFS_FILE_SYSTEM | The blue screen error with a value of 0x00000082. |
| SETUP_FAILURE | This BSOD indicates a fatal error occurred during setup. This bug check has a value of 0x00000085. |
| MBR_CHECKSUM_MISMATCH | This BSOD error means that a mismatch has occurred in the MBR checksum. It appears with a value of 0x0000008B. |
| KERNEL_MODE_EXCEPTION_NOT_HANDLED | This BSOD bug check has a value of 0x0000008E. It indicates a kernel-mode application generated an exception that the error handler did not catch. |
| PP0_INITIALIZATION_FAILED | This bug check appears with a value of 0x0000008F. This BSOD error shows that the Plug and Play (PnP) manager could not be initialized. |
| UP_DRIVER_ON_MP_SYSTEM | This BSOD has a value of 0x00000092. It specifies that a uniprocessor-only driver has been loaded on a multiprocessor system. |
| INVALID_KERNEL_HANDLE | This BSOD error shows that an invalid or protected handle was passed to NtClose. It appears with a value of 0x00000093. |
| KERNEL_STACK_LOCKED_AT_EXIT | This BSOD error indicates that a thread exited while its kernel stack was marked as not swappable. It contains a value of 0x00000094. |
| INVALID_WORK_QUEUE_ITEM | This BSOD error appears with a value of 0x00000096. It indicates that a queue entry was removed that contained a NULL pointer. This error may appear on your system periodically without even showing any warning. – Source |
| Srttrail.txt | This blue screen of death error may show up due to multiple reasons. It may appear out of nowhere on your first startup, after installing a program, or while browsing the internet. - Source |
| END_OF_NT_EVALUATION_PERIOD | This error appears with the stop code 0x00000098. It indicates that the trial period for the Microsoft Windows operating system has ended. |
| INVALID_REGION_OR_SEGMENT | Containing the value of 0x00000099, this BSOD error specifies that ExInitializeRegion or ExInterlockedExtendRegion was called with an invalid set of parameters. |
| SYSTEM_LICENSE_VIOLATION | This BSOD error indicates that the software license agreement has been violated. It shows up with a value of 0x0000009A. |
| UDFS_FILE_SYSTEM | This BSOD error appears with a stop code 0x0000009B. It designates that a problem occurred in the UDF file system. |
| MACHINE_CHECK_EXCEPTION | This bug check has a value of 0x0000009C. It indicates a fatal machine check exception has occurred. |
| USER_MODE_HEALTH_MONITOR | This BSOD error has a stop code 0x0000009E, which means that one or more critical user-mode components failed to satisfy a health check. |
| DRIVER_POWER_STATE_FAILURE | With a value of 0x0000009F, this blue screen error indicates that the driver is in an inconsistent or invalid power state. |
| INTERNAL_POWER_ERROR | This BSOD bug check indicates that the power policy manager experienced a fatal error. It appears with a stop code 0x000000A0. |
| PCI_BUS_DRIVER_INTERNAL | With a value of 0x000000A1, this BSOD error means that the PCI Bus Driver detected inconsistency problems in its internal structures and could not continue. |
| MEMORY_IMAGE_CORRUPT | It may show up with a value of 0x000000A2 and shows corruption in the image of an executable file in memory. |
| ACPI_DRIVER_INTERNAL | With a value of 0x000000A3, this BSOD on Windows 10 shows that the ACPI driver detected an internal inconsistency. |
| CNSS_FILE_SYSTEM_FILTER | This BSOD error shows up with a stop code 0x000000A4 and indicates that a problem has occurred in the CNSS file system filter. |
| ACPI_BIOS_ERROR | With a value of 0x000000A5, this BSOD error indicates that the computer's Advanced Configuration and Power Interface (ACPI) BIOS is not fully compliant with the ACPI specification. |
| BAD_EXHANDLE | This BSOD error has a value of 0x000000A7. It designates that the kernel-mode handle table detected an inconsistent handle table entry state. |
| SESSION_HAS_VALID_POOL_ON_EXIT | This error contains a stop code 0x000000AB and indicates that a session unload occurred while a session driver still held memory. |
| HAL_MEMORY_ALLOCATION | This error appears with a stop code 0x000000AC and indicates that the hardware abstraction layer (HAL) could not obtain sufficient memory. |
| VIDEO_DRIVER_DEBUG_REPORT_REQUEST | It shows that the video port created a non-fatal minidump on behalf of the video driver during run time. This error appears with a stop code 0x000000AD. |
| VIDEO_DRIVER_INIT_FAILURE | This BSOD shows up with a stop code 0x000000B4 and designates that Windows could not enter graphics mode. |
| ATTEMPTED_SWITCH_FROM_DPC | This BSOD has a value of 0x000000B8 and indicates that an illegal operation was attempted by a delayed procedure call (DPC) routine. |
| DPC Watchdog Violation Error | This bug check has a value of 0x00000133 that indicates the DPC watchdog has been executed. The reasons could be DPC watchdog detected a single long-running deferred procedure call (DPC) or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above. You may encounter this error after upgrading to Windows 10. - Source |
| SESSION_HAS_VALID_VIEWS_ON_EXIT | This BSOD error appears with a stop code 0x000000BA. It specifies that a session driver still had mapped views when the session unloaded. |
| BAD POOL HEADER | This BSOD error indicates a corrupted pool header. It has a value of 0x00000019. This error means that there is a problem with Windows memory allocation. – Source |
| NETWORK_BOOT_DUPLICATE_ADDRESS | This bug check indicates that a duplicate IP address has been assigned to the machine while booting off a network. It contains a value of 0x000000BC. |
| ATTEMPTED_WRITE_TO_READONLY_MEMORY | This BSOD error shows up with a stop code - 0x000000BE. This bug check appears when a driver attempts to write to a read-only memory segment. |
| MUTEX_ALREADY_OWNED | This blue screen error appears with a stop code 0x000000BF. It indicates that a thread attempted to acquire ownership of a mutex it already owned. |
| SPECIAL_POOL_DETECTED _MEMORY_CORRUPTION | This bug check appears with a stop code - 0x000000C1. It specifies that the driver wrote to an invalid section of the special pool. |
| BAD_POOL_CALLER | This bug check has a value of 0x000000C2. When you get this error, it means that there is a thread making the bad pool request. You may encounter this error randomly appearing on your system, crashing it, or sometimes only freezing it. -Source |
| DRIVER_VERIFIER_DETECTED_VIOLATION | This bug check is a general STOP code for fatal errors found by Driver Verifier. This error appears with a value of 0x000000C4. |
| DRIVER_CORRUPTED_EXPOOL | This BSOD error possesses the value of 0x000000C5 and designates that the system attempted to access invalid memory at a process IRQL that was too high. |
| DRIVER_CAUGHT_MODIFYING_FREED_POOL | This BSOD occurs when the driver attempts to access a freed memory pool. It appears with a bug check value of 0x000000C6. |
| TIMER_OR_DPC_INVALID | This BSOD has a value of 0x000000C7. This blue screen error occurs when a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted. |
| IRQL_UNEXPECTED_VALUE | This error indicates the processor's IRQL is not what it should be at this time. This BSOD has a value of 0x000000C8. It may usually occur due to a problematic device driver. – Source |
| Boot Error - 0xc0000001 | This blue screen of death on Windows 10 error indicates that there might be some issues with the booting device or some booting files are corrupted. The error may also occur due to corrupted boot sector of your system. - Source |
| PNP_DETECTED_FATAL_ERROR | It means that the Plug and Play Manager encountered a severe error, probably due to a problematic Plug and Play driver. This error has a value of 0x000000CA. |
| DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS | This BSOD error appears with a value of 0x000000CB. When you see this error, it means that a driver or the I/O manager failed to release locked pages after an I/O operation. |
| PAGE_FAULT_IN_FREED_SPECIAL_POOL | When the system has referenced memory that was earlier freed, you may experience this BSOD error with a stop code 0x000000CC. |
| PAGE_FAULT_BEYOND_END_OF_ALLOCATION | When the system accessed memory beyond the end of a driver's pool allocation, it resulted in this error with a stop code - 0x000000CD. |
| DRIVER_UNLOADED_WITHOUT_ CANCELLING_PENDING_OPERATIONS | This BSOD error indicates that there is a driver who failed to cancel pending operations before unloading. It has a value of 0x000000CE. This error may occur due to dump_WppRecorder.sys. - Source |
| TERMINAL_SERVER_DRIVER_ MADE_INCORRECT_MEMORY_REFERENCE | When a driver incorrectly ports to the terminal server, this bug check may occur with a value of 0x000000CF. |
| DRIVER_CORRUPTED_MMPOOL | When the system attempts to access invalid memory at a process IRQL that was too high, this BSOD error with a stop code 0x000000D0 may appear. |
| DRIVER_IRQL_NOT_LESS_OR_EQUAL | With a stop code 0x000000D1, this error occurs when a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. |
| BUGCODE_ID_DRIVER | This error appears with a value of 0x000000D2. This BSOD shows that a problem has occurred with an NDIS driver. |
| DRIVER_PORTION_MUST_BE_NONPAGED | This BSOD error appears with a stop code 0x000000D3 and indicates that the system attempted to access pageable memory at a process IRQL that was too high. |
| SYSTEM_SCAN_AT_RAISED_IRQL_ CAUGHT_IMPROPER_DRIVER_UNLOAD | This blue screen error means that a driver did not cancel pending operations before unloading. It shows up with a value of 0x000000D4. |
| DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL | This error appears with a stop code 0x000000D5 and indicates that a driver has referenced memory that was earlier freed. |
| DRIVER_PAGE_FAULT_BEYOND _END_OF_ALLOCATION | This BSOD error specifies the driver has accessed memory beyond the end of its pool allocation. It consists of a value of 0x000000D6. |
| DRIVER_UNMAPPING_INVALID_VIEW | This BSOD error shows that a driver is trying to unmap an address that was not mapped. It comes with the stop code - 0x000000D7. |
| DRIVER_USED_EXCESSIVE_PTES | This BSOD error appears with 0x000000D8. When this error shows up, it means that there are no more system page table entries (PTE) remaining. |
| LOCKED_PAGES_TRACKER_CORRUPTION | This blue screen of death error may appear with a stop code 0x000000D9. It Indicates that the internal locked-page tracking structures have been corrupted. |
| SYSTEM_PTE_MISUSE | This BSOD appears with a stop code 0x000000DA, indicating that a page table entry (PTE) routine has been used improperly. This error may also occur when trying to install Windows 10 from a bootable flash drive. - Source |
| DRIVER_CORRUPTED_SYSPTES | This BSOD error has a value of 0x000000DB, which means that an attempt was made to touch memory at an invalid IRQL, probably due to corruption of system PTEs. |
| DRIVER_INVALID_STACK_ACCESS | This BSOD error appears with the stop code 0x000000DC and indicates that a driver accessed a stack address below the stack pointer of the stack's thread. |
| POOL_CORRUPTION_IN_FILE_AREA | This blue screen error has a value of 0x000000DE. When this message appears, it means that a driver has corrupted pool memory used to hold pages destined for disk. |
| IMPERSONATING_WORKER_THREAD | When a work item doesn’t disable impersonation before it is completed, this blue screen occurs with a value of 0x000000DF. |
| ACPI_BIOS_FATAL_ERROR | This BSOD error indicates the faulty components of your system. It has a value of 0x000000E0. The BIOS is showing that there is no alternative but to issue a bug check. |
| WORKER_THREAD_RETURNED_AT_BAD_IRQL | When a worker thread is completed and returned with IRQL >= DISPATCH_LEVEL, this blue screen error occurs with a stop code 0x000000E1. |
| MANUALLY_INITIATED_CRASH | When a user deliberately initiated a crash dump from either the kernel debugger or the keyboard, this blue screen error appears with a value of 0x000000E2. |
| RESOURCE_NOT_OWNED | This BSOD means that a thread tried to release a resource it did not own. It shows up with error code 0x000000E3. |
| WORKER_INVALID | This blue screen bug check has a value of 0x000000E4. This error designates that memory that should not contain an executive work item does include such an item or that a currently active work item was queued. This error usually occurs due to a driver freeing memory which still contains an executive work item |
| DRIVER_VERIFIER_DMA_VIOLATION | It is for all Driver Verifier DMA Verification violations. It has a value of 0x000000E6. |
| INVALID_FLOATING_POINT_STATE | This BSOD appears with a stop code 0x000000E7. It specifies a thread's saved floating-point state is invalid. |
| INVALID_CANCEL_OF_FILE_OPEN | It appears with a value of 0x000000E8. It indicates that an invalid file object was passed to IoCancelFileOpen. |
| ACTIVE_EX_WORKER_THREAD_TERMINATION | This BSOD error code has a value of 0x000000E9. It shows that an active executive worker thread is being terminated. |
| DIRTY_MAPPED_PAGES_CONGESTION | It has a value of 0x000000EB. It specifies that there are no free pages available to continue operations. Any file system or filter driver in the stack may be at fault. |
| SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT | With the value of 0x000000EC, this error specifies a session unload that occurred while a session driver still held memory. |
| UNMOUNTABLE_BOOT_VOLUME | With a value of 0x000000ED, this error means that the I/O subsystem attempted to mount the boot volume, and it failed. |
| BSOD CRITICAL PROCESS DIED | This BSOD error comes with a value of 0x000000EF and shows that a critical system process died. It may occur when the state of the process is corrupted or otherwise is damaged. |
| SCSI_VERIFIER_DETECTED_VIOLATION | This BSOD error is for all Driver Verifier SCSI Verification violations and appears with a value of 0x000000F1. |
| DISORDERLY_SHUTDOWN | This BSOD shows up with a value of 0x000000F3. It means that Windows was unable to shut down due to lack of memory. It occurs when there are no free pages available to continue operations. |
| CRITICAL_OBJECT_TERMINATION | This BSOD error specifies that a process or thread crucial to system operation has unexpectedly exited or been terminated. This error appears with a value of 0x000000F4. When processes and threads necessary for system operation get removed for any reason, the system can no longer function and result in this blue screen of death error. |
| FLTMGR_FILE_SYSTEM | When an unrecoverable failure occurs in the Filter Manager, the system appears with a blue screen and a stop "FLTMGR_FILE_SYSTEM" with a code 0x000000F5. |
| PCI_VERIFIER_DETECTED_VIOLATION | This bug check has a value of 0x000000F6. This BSOD shows that an error occurred in the BIOS or another device verified by the PCI driver. Reasons behind this error could include a faulty PCI driver or BIOS being verified. |
| DRIVER_OVERRAN_STACK_BUFFER | This BSOD error has a value of 0x000000F7. It means that a driver has overrun a stack-based buffer. |
| RAMDISK_BOOT_INITIALIZATION_FAILED | When an initialization failure occurs while attempting to boot from the RAM disk, you may encounter this BSOD error on your screen with a value of 0x000000F8. |
| DRIVER_RETURNED_STATUS _REPARSE_FOR_VOLUME | This bug check has a value of 0x000000F9. When you encounter this BSOD on Windows 10, it indicates that a driver returned STATUS_REPARSE to an IRP_MJ_CREATE request with no trailing names. |
| HTTP_DRIVER_CORRUPTED | With a value of 0x000000FA, this BSOD error shows that an HTTP kernel driver (Http.sys) has reached a corrupted state and cannot recover. |
| ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY | It shows that an attempt was made to execute non-executable memory. It appears with a value of 0x000000FC. |
| DIRTY_NOWRITE_PAGES_CONGESTION | This BSOD error has the value of 0x000000FD. It specifies that there are no free pages available to continue basic system operations. |
| BUGCODE_USB_DRIVER | This BSOD error contains a value of 0x000000FE. It indicates that an error has occurred in a Universal Serial Bus (USB) driver. Users have reported that laptop crashes many times randomly with this issue. - Source |
| RESERVE_QUEUE_OVERFLOW | This BSOD error indicates an attempt to insert a new item into a reserve queue caused the queue to overflow. This contains error code 0x000000FF. |
| LOADER_BLOCK_MISMATCH | This BSOD contains error code 0x00000100. It indicates that either the loader block is invalid or does not match the system being loaded. |
| CLOCK_WATCHDOG_TIMEOUT | With a value of 0x00000101, this BSOD indicates that an expected clock interrupt on a secondary processor in a multi-processor system was not received within the allocated interval. |
| MUP_FILE_SYSTEM | This BSOD error possesses a value of 0x00000103. When multiple UNC providers (MUP) encounter invalid or unexpected data, they show that an MUP cannot channel a remote file system request to a network redirector, the Universal Naming Convention (UNC) provider. |
| AGP_INVALID_ACCESS | This BSOD error has a value of 0x00000104. It specifies that the GPU wrote to a range of Accelerated Graphics Port (AGP) memory that had not previously been committed. |
| AGP_GART_CORRUPTION | This BSOD error indicates corrupted Graphics Aperture Remapping Table (GART) and appears with a value of 0x00000105. |
| AGP_ILLEGALLY_REPROGRAMMED | This blue screen of death error indicates that an unauthorized agent has reprogrammed the AGP (Accelerated Graphics Port) hardware. It possesses a value of 0x00000106. |
| THIRD_PARTY_FILE_SYSTEM_FAILURE | This error shows up with a stop code 0x00000108. It specifies that an unrecoverable problem has occurred in a third-party file system or file system filter. |
| CRITICAL_STRUCTURE_CORRUPTION | This BSOD error has a value of 0x00000109. It occurs when the kernel has detected critical kernel code or data corruption. |
| APP_TAGGING_INITIALIZATION_FAILED | This BSOD error has a bug check value of 0x0000010A. |
| FSRTL_EXTRA_CREATE_ PARAMETER_VIOLATION | It contains a value of 0x0000010C and indicates that a violation was detected in the File system Run-time library (FsRtl) Extra Create Parameter (ECP) package. |
| WDF_VIOLATION | It comes with a value of 0x0000010D. This BSOD specifies that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver. |
| VIDEO_MEMORY_MANAGEMENT_INTERNAL | This BSOD error has a value of 0x0000010E. It designates that the video memory manager has encountered a condition that it is unable to recover from. |
| RESOURCE_MANAGER_ EXCEPTION_NOT_HANDLED | This BSOD error designates that the kernel transaction manager detected that a kernel-mode resource manager had raised an exception in response to a direct call-back. As a result, the resource manager is in an unexpected and unrecoverable state. The bug check value of this error code is 0x0000010F. |
| RECURSIVE_NMI | This BSOD error has a stop code 0x00000111 which indicates that a non-maskable-interrupt (NMI) occurred while a previous NMI is in progress. |
| MSRPC_STATE_VIOLATION | This error shows that Msrpc.sys driver has initiated a STOP code. It contains a value of 0x00000112. |
| VIDEO_DXGKRNL_FATAL_ERROR | It contains a bug check value of 0x00000113 and indicates that the dxg kernel has detected a violation. |
| VIDEO_SHADOW_DRIVER_FATAL_ERROR | With a stop code 0x00000114, this blue screen error means that the shadow driver has detected a violation. |
| AGP_INTERNAL | This blue screen error indicates that the accelerated graphics port (AGP) driver has detected a violation. It has a value of 0x00000115. |
| VIDEO_TDR_ERROR | This bug check has a value of 0x00000116. It indicates that an attempt to reset the display driver and recover from a timeout failed. |
| VIDEO_TDR_TIMEOUT_DETECTED | This BSOD error indicates that the display driver failed to respond in a timely fashion. It comes with a value of 0x00000117. |
| VIDEO_SCHEDULER_INTERNAL_ERROR | This BSOD error shows up with a stop code 0x00000119 that means that the video scheduler has detected a fatal violation. It may show a black screen at first, and when you reboot, it may convert into a blue screen error. – Source |
| EM_INITIALIZATION_FAILURE | This BSOD error appears with a stop code 0x0000011A. |
| ATTEMPTED_WRITE_TO_CM_ PROTECTED_STORAGE | It shows that an attempt was made to write to the read-only protected storage of the configuration manager. It has a value of 0x0000011C. |
| EVENT_TRACING_FATAL_ERROR | It occurs when the Event Tracing subsystem has encountered an unexpected fatal error. This error has a value of 0x0000011D. It may even occur on the first startup of your system. - Source |
| RTKVHD64.sys | This BSOD error has a bug check value of 0×0000003B. It may occur while playing video games or due to a faulty Realtek audio driver. |
| WHEA_INTERNAL_ERROR | This bug check has a value of 0x00000122. It may occur when there is corruption in the Windows Hardware Error Architecture (WHEA). In some cases, the error occurred after updating the system. - Source |
| WHEA_UNCORRECTABLE_ERROR | This error indicates a fatal hardware error. It consists of a value of 0x00000124. It uses the error data that is provided by the WHEA (Windows Hardware Error Architecture). |
| PAGE_NOT_ZERO | This BSOD specifies that a page that should have been filled with zeros was not. It has a value of 0x00000127 and usually occurs due to hardware error or a privileged component of the OS modified a page after freeing it. |
| FAULTY_HARDWARE_CORRUPTED_PAGE | It indicates that the Windows memory manager detected corruption, which could have been caused by a component accessing memory using physical addressing. It occurs with a stop code - 0x0000012B. |
| SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M | This BSOD error specifies that a system thread generated an exception which the error handler did not catch. It appears with a bug check value of 0x1000007E. This error also usually occurs while playing both offline and online games. - Source |
| UNEXPECTED_KERNEL_MODE_TRAP_M | When the Intel CPU generates a trap and the kernel fails to catch this trap, you may encounter this error with a bug check value of 0x0000007F. The error may cause your system to crash frequently. – Source |
| KERNEL_MODE_EXCEPTION_NOT_HANDLED_M | It shows that a kernel-mode program generated an exception which the error handler did not catch. It shows a stop code - 0x1000008E. |
| THREAD_STUCK_IN_DEVICE_DRIVER_M | This BSOD error shows a stop code 0x100000EA. It means that a thread in a device driver is endlessly spinning. Users have reported that they encountered this issue while playing intense graphic games. - Source |
| STATUS_CANNOT_LOAD_REGISTRY_FILE | It appears when the registry file could not be loaded correctly. It shows a value of 0xC0000218. As per the users, the PCs even become unresponsive or freeze out after installing Windows 10 update. - Source |
| STATUS_SYSTEM_PROCESS_TERMINATED | This BSOD error may occur with different stop codes - oxc00000104d8, 0x000104D8, 0xc0000034, and 0xc000021a. Users reported that they tried to perform a clean install but the system doesn’t even recognize the USB installation media due to this error. - Source |
| STATUS_IMAGE_CHECKSUM_MISMATCH | It specifies that there is corruption in a driver or a system DLL. It has a value of 0xC0000221. “Users reported that this error may also make your system stuck at an automatic repair loop.” - Source |
| Boot Selection Failed Because A Required Device Is Inaccessible | This BSOD error appears with a value of 0xc000000f. |
| MANUALLY_INITIATED_CRASH1 | It appears with a stop code - 0xDEADDEAD. It appeared when a manually initiated crash |
About The Author
Mansi Verma 
A seasoned technology writer and tech enthusiast with keen interest for everything in technology.
5 min read
5 min read
5 min read
