A Blue Screen of Death (BSOD) will occur when Windows is experiencing a serious problem. Windows will display a blue screen with an error code on the screen.
The error code on the screen is very useful information on the cause of the failure to further identify the problem.
BSOD can occur on all Windows operating systems starting from Windows 95 to Windows 11. In Windows 11 the BSOD screen is not blue but black.
Here, Bardimin summarizes various sources of error codes from the BSOD and their explanations.
| Code | Message | Description |
| 0x00000001 | APC_INDEX_MISMATCH | This BSOD means that there has been a mismatch in the APC state index. BSOD error code 0x00000001 may also show “APC_INDEX_MISMATCH” on the same blue screen. APC_INDEX_MISMATCH – internal kernel error. It occurs at the completion of the system call. Error 0x00000001 occurs when the file system driver has a mismatched sequence of system calls to start or finish a protected or critical section. For example, each call must be KeEnterCriticalRegion corresponding call KeLeaveCriticalRegion. |
| 0x00000002 | DEVICE_QUEUE_NOT_BUSY | This BSOD is uncommon. BSOD error code 0x00000002 may also show “DEVICE_QUEUE_NOT_BUSY” on the same blue screen. A rare error may be caused, both by hardware and software. The highest probability of an error is a failure of the printer driver or an error signature key. Any operating system family of Windows NT from Microsoft can cause Stop 0x00000002. Including Windows 8, Windows 7, Windows Vista, Windows XP and Windows 2000. As with any other error blue screen of death, you cannot complete the operation because the system immediately restarts or if it is linked with the settings, restart the user expects. |
| 0x00000003 | INVALID_AFFINITY_SET | This BSOD is uncommon. BSOD error code 0x00000003 may also show “INVALID_AFFINITY_SET” on the same blue screen. Most likely this error can be seen when installing the printer. Any operating system can cause Stop 0x00000003. it was present Windows 2000 and it is fixed in the latest updates of windows. |
| 0x00000004 | INVALID_DATA_ACCESS_TRAP | This BSOD is uncommon. BSOD error code 0x00000004 may also show “INVALID_DATA_ACCESS_TRAP” on the same blue screen. This problem occurs in Windows XP SP2 and Windows Server 2003 when you install some antivirus and firewall programs. To resolve this problem in Windows XP SP2, you must download and install the updates. It also indicates an unacceptable interruption of access to the data. This error occurs if your operating system drivers are outdated. |
| 0x00000005 | INVALID_PROCESS_ATTACH_ATTEMPT | This BSOD is uncommon. BSOD error code 0x00000005 may also show “INVALID_PROCESS_ATTACH_ATTEMPT” on the same blue screen. This error indicates that the flow has been attached to the process in a situation where it is not allowed. For example, this error could occur if caused KeAttachProcess, when the flow has been attached to the process (which is not allowed), or if the flow is returned from the certain function calls in the attached state (that is not valid). It occurs when a coding error in the Http.sys file, which in turn causes damage to the stack. |
| 0x00000006 | INVALID_PROCESS_DETACH_ATTEMPT | This BSOD is uncommon. BSOD error code 0x00000006 may also show “INVALID_PROCESS_DETACH_ATTEMPT” on the same blue screen. A rare error indicates a problem with a mutex or APC. BSoD may occur if Windows incorrectly queues function asynchronous procedure call (APC) nucleus, also known as a completion routine. |
| 0x00000007 | INVALID_SOFTWARE_INTERRUPT | This BSOD is uncommon. BSOD error code 0x00000007 may also show “INVALID_SOFTWARE_INTERRUPT” on the same blue screen. It indicates the level is not within the software range. In the present version of windows, they tried to fix it but despite all this, it still exists under the latest Windows. Usually, it occurs due to a hardware controller or a damaged or defective/incompatible software. Technically, this error means that the kernel mode process or driver attempted to access a memory location which is not allowed. |
| 0x00000008 | IRQL_NOT_DISPATCH_LEVEL | This BSOD is uncommon. BSOD error code 0x00000008 may also show “IRQL_NOT_DISPATCH_LEVEL” on the same blue screen. The blue screen of death 0x00000008 indicates an attempt to remove the device at a non-dispatch level. |
| 0x00000009 | IRQL_NOT_GREATER_OR_EQUAL | This BSOD is uncommon. BSOD error code 0x00000009 may also show “IRQL_NOT_GREATER_OR_EQUAL” on the same blue screen. IRQL_NOT_GREATER_OR_EQUAL error occurs when memory access occurs at too high IRQL. Typically, this error indicates IRQL value is less than desired when a driver uses an incorrect memory address. Other possible causes of this error include an incompatible device driver, a general hardware problem, or incompatible software. |
| 0x0000000A | IRQL_NOT_LESS_OR_EQUAL | This BSOD means that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. BSOD error code 0x0000000A may also show “IRQL_NOT_LESS_OR_EQUAL” on the same blue screen. Stop 0x0000000A occurs when entering sleep mode. This occurs because Diskdump.sys driver incorrectly sets the I/O size to 0. When the system enters hibernation mode, Diskdump.sys driver is responsible for writing the memory content in the Hiberfil.sys file. If the storage device that contains Hiberfil.sys file busy, when the device receives an I/O request from Diskdump.sys driver, it tries to send the I/O request later. However, Diskdump.sys driver incorrectly sets the I/O size to 0 when resends the request. Therefore, the system accesses the invalid memory address and you get an error message. |
| 0x0000000B | NO_EXCEPTION_HANDLING_SUPPORT | This BSOD is uncommon. BSOD error code 0x0000000B may also show “NO_EXCEPTION_HANDLING_SUPPORT” on the same blue screen. A blue screen of 0x0000000B indicates that exception handling was not supported. |
| 0x0000000C | MAXIMUM_WAIT_OBJECTS_EXCEEDED | This BSOD means that the current thread exceeded the permitted number of wait objects. BSOD error code 0x0000000C may also show “MAXIMUM_WAIT_OBJECTS_EXCEEDED” on the same blue screen. Error MAXIMUM_WAIT_OBJECTS_EXCEEDED exist due to improper use of KeWaitForMultipleObjects or FsRtlCancellableWaitForMultipleObjects. The caller may pass a pointer to the buffer parameter WaitBlockArray the routine. The system will use this buffer to track waiting objects. If the buffer is provided, the count parameter may not exceed MAXIMUM_WAIT_OBJECTS. If the buffer is not provided, the count parameter may exceed THREAD_WAIT_OBJECTS. If the count value exceeds the allowable value, this error occurs. |
| 0x0000000D | MUTEX_LEVEL_NUMBER_VIOLATION | This BSOD is uncommon. BSOD error code 0x0000000D may also show “MUTEX_LEVEL_NUMBER_VIOLATION” on the same blue screen. It indicates an attempt to acquire the mutex at a lower level. This often happened after CPU overhead or lack of RAM, so make sure that your system does not have any virus and check your memories via test utilities. |
| 0x0000000E | NO_USER_MODE_CONTEXT | This BSOD is uncommon. BSOD error code 0x0000000E may also show “NO_USER_MODE_CONTEXT” on the same blue screen. When the computer connects and then disconnects from a remote access session to your computer with Microsoft Windows 2000 operating system, the computer may unexpectedly stop responding, and you may receive BSoD NO_USER_MODE_CONTEXT. |
| 0x0000000F | SPIN_LOCK_ALREADY_OWNED | This BSOD means that a request for a spin lock has been initiated when the spin lock was already owned. BSOD error code 0x0000000F may also show “SPIN_LOCK_ALREADY_OWNED” on the same blue screen. Typically, this error is caused by a recursive query on the spin-lock. For example, when spin-lock was obtained, stream and then the same thread calls a function that is also trying to get a spin-lock. A second attempt to get a spin-lock is not locked, because it would lead to a deadlock. If calls are made by more than one processor, one processor will be blocked until the other processor releases the lock. This error can also occur without explicit recursion when all flows and all spin-locks are assigned IRQL. IRQL spin-lock is always greater than or equal to the DPC, but this is not taken into account for the flows. However, IRQL stream which comprises spin-lock must maintain greater than or equal to the value IRQL spin-lock. When reducing the flow IRQL below IRQL spin-lock, which stream contains, allows another thread executed by the processor. This new stream can try to get the same spin-lock. Make sure you do not get the lock recursively. And, for streams that contain spin-lock, make sure that you do not reduce the flow IRQL to the level below IRQL spin-lock, which it contains. |
| 0x00000010 | SPIN_LOCK_NOT_OWNED | This BSOD is uncommon. BSOD error code 0x00000010 may also show “SPIN_LOCK_NOT_OWNED” on the same blue screen. 0x00000010 indicates an attempt to free his own spin-lock. It may be caused by an improperly installed device, a device driver that conflicts with Windows, or an obsolete device driver. You can visit FixBit which provides the latest version of drivers. It also offers auto driver update service so that you can have a hassle-free installation. If a file name is specified, update the target device. If this does not fix the problem, uninstall all recently-installed devices cleanly, reinstall them with FixBit, and update your Windows. |
| 0x00000011 | THREAD_NOT_MUTEX_OWNER | This BSOD is uncommon. BSOD error code 0x00000011 may also show “THREAD_NOT_MUTEX_OWNER” on the same blue screen. 0x00000011 indicates an attempt to liberate the improper flow of the mutex. Uninstalling the latest installed software to find the problem. Check and verify that your newly added hardware is compatible with your Windows, and download the latest drivers by visiting the FixBit site. |
| 0x00000012 | TRAP_CAUSE_UNKNOWN | This BSOD means that an unknown exception has occurred. BSOD error code 0x00000012 may also show “TRAP_CAUSE_UNKNOWN” on the same blue screen. 0x00000012 indicates that there was an unknown exception. This error usually occurs on computers running Windows 2000 with a Sound Blaster and sound card integrated software Live for that sound. The problem is solved by removing the software for this zvukovuhi. It is a rare error of TRAP_CAUSE_UNKNOWN parameters which includes: The sudden interruption The unknown exception of floating-point |
| 0x00000013 | EMPTY_THREAD_REAPER_LIST | This BSOD is uncommon. BSOD error code 0x00000013 may also show “EMPTY_THREAD_REAPER_LIST” on the same blue screen. 0x00000013 indicates that the stream list is damaged. Uninstall the recently installed software and Make sure your newly added hardware is compatible with your Windows, and download the latest drivers available directly from your hardware manufacturer’s site. |
| 0x00000014 | CREATE_DELETE_LOCK_NOT_LOCKED | This BSOD is uncommon. BSOD error code 0x00000014 may also show “CREATE_DELETE_LOCK_NOT_LOCKED” on the same blue screen. 0x00000014 is extremely rare. This error is caused by wrong hardware or inappropriate device driver issues. |
| 0x00000015 | LAST_CHANCE_CALLED_FROM_KMODE | This BSOD is uncommon. BSOD error code 0x00000015 may also show “LAST_CHANCE_CALLED_FROM_KMODE” on the same blue screen. 0x00000015 indicates that the latter is a random exception service was launched in kernel mode. This error means that the installed device is not ready and you don’t have a vital service running on your computer. |
| 0x00000016 | CID_HANDLE_CREATION | This BSOD is uncommon. BSOD error code 0x00000016 may also show “CID_HANDLE_CREATION” on the same blue screen. 0x00000016 indicates that a failure occurred when creating a descriptor to represent a client ID. This error can occur if you uninstall a browser so make sure you uninstall it completely through the utility to avoid this error. |
| 0x00000017 | CID_HANDLE_DELETION | This BSOD is uncommon. BSOD error code 0x00000017 may also show “CID_HANDLE_DELETION” on the same blue screen. This error indicates that a failure occurred when deleting the descriptor to represent a client ID. This error code is commonly used to identify the error caused by the hardware driver vendors. The warning messages may slow down PC performance and system freezes startup/shutdown which can be quite annoying if not timely fixed. |
| 0x00000018 | REFERENCE_BY_POINTER | This BSOD means that the reference count of an object is illegal for the current state of the object. BSOD error code 0x00000018 may also show “REFERENCE_BY_POINTER” on the same blue screen. The reference count for the object is invalid for the current state of the object. Every time a driver uses a pointer to an object, it calls the subroutine core to increase the object’s reference count by one. When the driver terminates with a pointer, the driver calls another subroutine core to reduce the reference counter by one. Drivers must call subroutines that increase (link), and decrease (dereferencing) reference count. This error occurs when non-compliance of the values of the reference count of the object. As a rule, the inconsistency caused by the driver, which reduces the reference count of an object too many times by performing additional challenges that dereference the object. 0x00000018 error can occur at zero reference count, while still have open handles to the object. |
| 0x00000019 | BAD_POOL_HEADER | This BSOD means that a pool header is corrupt. BSOD error code 0x00000019 may also show “BAD_POOL_HEADER” on the same blue screen. The pool here is the address space of memory. This error particularly indicates if a computer crashes and suddenly loses contact with one of the memory card or one of the hard drives where there is a paging pool file. |
| 0x0000001A | MEMORY_MANAGEMENT | This BSOD means that a severe memory management error occurred. BSOD error code 0x0000001A may also show “MEMORY_MANAGEMENT” on the same blue screen. This error is usually related to the NTFS file system. Also, if this occurs during the installation of Windows, you should check the features of the system components, including the amount of RAM and free space on your hard disk. |
| 0x0000001B | PFN_SHARE_COUNT | This BSOD is uncommon. BSOD error code 0x0000001B may also show “PFN_SHARE_COUNT” on the same blue screen. 0x0000001B indicates that the PFN database memory management element is damaged count the number of users. It’s a rare error related to your RAM. |
| 0x0000001C | PFN_REFERENCE_COUNT | This BSOD is uncommon. BSOD error code 0x0000001C may also show “PFN_REFERENCE_COUNT” on the same blue screen. 0x0000001C indicates that memory management PFN database element is a corrupt reference count. It means your newly added hardware is not compatible with your Windows, |
| 0x0000001D | NO_SPIN_LOCK_AVAILABLE | This BSOD is uncommon. BSOD error code 0x0000001D may also show “NO_SPIN_LOCK_AVAILABLE” on the same blue screen. 0x0000001D indicates that all the spin locks are not available. A rare error in Windows XP error which occurs when you change the IPX frame type of the current network connection is automatically determined on any other type. |
| 0x0000001E | KMODE_EXCEPTION_NOT_HANDLED | This BSOD means that a kernel-mode program generated an exception which the error handler did not catch. BSOD error code 0x0000001E may also show “KMODE_EXCEPTION_NOT_HANDLED” on the same blue screen. The Windows kernel detected a prohibited transaction or unknown processor instruction. The 0x1E error can be caused by a faulty memory and access violation reasons similar to those that cause Stop 0xA error. |
| 0x0000001F | SHARED_RESOURCE_CONV_ERROR | This BSOD is uncommon. BSOD error code 0x0000001F may also show “SHARED_RESOURCE_CONV_ERROR” on the same blue screen. 0x0000001F indicates conversion problem shared the resource. You can uninstall any newly installed hardware and software to find the problem. Make sure your new hardware is compatible with your Windows, and download the latest drivers by using FixBit site. |
| 0x00000020 | KERNEL_APC_PENDING_DURING_EXIT | This BSOD means that an asynchronous procedure call (APC) was still pending when a thread exited. BSOD error code 0x00000020 may also show “KERNEL_APC_PENDING_DURING_EXIT” on the same blue screen. It indicates that an asynchronous procedure call (APC) was in standby mode upon completion of the thread execution. A key parameter – the number of outages for APC stream. If the number is non-zero, then it will indicate the source of the problem. A number of disconnections APC decreases each time when the driver calls KeEnterCriticalRegion, FsRtlEnterFileSystem, or when the mutex. The number of APC trips is gradually increased whenever the driver calls KeLeaveCriticalRegion, KeReleaseMutex, or FsRtlExitFileSystem. |
| 0x00000021 | QUOTA_UNDERFLOW | This BSOD means that quota charges have been mishandled by returning more quota to a particular block than was previously charged. BSOD error code 0x00000021 may also show “QUOTA_UNDERFLOW” on the same blue screen. This error indicates that the quota was returned to the process, but the process did not use all of the value of the quota. It means the remaining amount of the quota has not been returned. |
| 0x00000022 | FILE_SYSTEM | This BSOD is uncommon. BSOD error code 0x00000022 may also show “FILE_SYSTEM” on the same blue screen. A blue screen of 0x00000022 indicates a file system problem. A possible reason is the depletion of the non-swapped memory pool. During the indexing process, if the amount of available pool of non-pumped memory is very small, another driver requiring a pool of non-pumped memory may also trigger this error. |
| 0x00000023 | FAT_FILE_SYSTEM | This BSOD means that a problem occurred in the FAT file system. BSOD error code 0x00000023 may also show “FAT_FILE_SYSTEM” on the same blue screen. The problem occurs when reading or writing to the FAT16 or FAT32 file system. The cause of the error can be physical damage to the storage device. Other common reasons are: hard drive fragmentation, problems with some software products for RAID arrays, some antivirus programs may also cause this error. To solve the problem, we run ScanDisk ChkDsk or as a first step; then we disable antivirus software, firewall and backup. Also, check the properties of FASTFAT.SYS file, make sure they match the current operating system and service pack version. You must also update the drivers for all storage devices and copy the data to the current version. |
| 0x00000024 | NTFS_FILE_SYSTEM | This BSOD means a problem occurred in ntfs.sys, the driver file that allows the system to read and write to NTFS drives. BSOD error code 0x00000024 may also show “NTFS_FILE_SYSTEM” on the same blue screen. The problem occurs when reading or writing to the NTFS file system. The cause of the error can be physical damage to the storage device. Other common reasons are: hard drive fragmentation, problems with some software products for RAID arrays, some antivirus programs may also cause this error. To solve the problem, we run ScanDisk ChkDsk or as a first step; then we disable antivirus software, firewall and backup. Also, check the properties of FASTFAT.SYS file, make sure they match the current operating system and service pack version. You must also update the drivers with FixBit for all storage devices and copy the data to the current version. |
| 0x00000025 | NPFS_FILE_SYSTEM | This BSOD means that a problem occurred in the NPFS file system. BSOD error code 0x00000025 may also show “NPFS_FILE_SYSTEM” on the same blue screen. One of the possible causes of a blue screen 0x00000025 – damage to the hard disk. File system corruption or bad blocks (sectors) on the disk can cause this error. Damaged SCSI and IDE drivers can also have a negative impact on the ability of the system to read and write to the hard disk, thus causing the error. Another possible reason – the depletion of the pool is not paged memory. During the indexing process, if the amount of available paged pool memory is not very small, the other driver does not require the pool paged memory can also trigger this error. |
| 0x00000026 | CDFS_FILE_SYSTEM | This BSOD means that a problem occurred in the CD file system. BSOD error code 0x00000026 may also show “CDFS_FILE_SYSTEM” on the same blue screen. One of the possible causes of BSoD – damage to the hard disk. Damage to the CDFS file system or bad blocks (sectors) on the disk can cause this error. Damaged SCSI and IDE drivers can also have a negative impact on the ability of the system to read and write to the hard disk, thus causing the error. Another possible reason – the depletion of the pool is not paged memory. During the indexing process, if the amount of available paged pool memory is not very small, the other driver does not require the pool paged memory can also trigger this error. |
| 0x00000027 | RDR_FILE_SYSTEM | This BSOD means that a problem occurred in the SMB redirector file system. BSOD error code 0x00000027 may also show “RDR_FILE_SYSTEM” on the same blue screen. BSoD caused by the depletion of the pool is not paged memory. During the indexing process, if the amount of available paged pool memory is not very small, the other driver does not require the pool paged memory, can trigger this error. This pretty rare error in the system running Windows 2000. Insufficient RAM may be one reason and add an additional bar should solve this problem. |
| 0x00000028 | CORRUPT_ACCESS_TOKEN | This BSOD is uncommon. BSOD error code 0x00000028 may also show “CORRUPT_ACCESS_TOKEN” on the same blue screen. During the indexing process, 0x00000028 indicates that the security system has detected an invalid token. |
| 0x00000029 | SECURITY_SYSTEM | This BSOD is uncommon. BSOD error code 0x00000029 may also show “SECURITY_SYSTEM” on the same blue screen. It indicates an internal security system problem. |
| 0x0000002A | INCONSISTENT_IRP | This BSOD means that an IRP was found to contain inconsistent information. BSOD error code 0x0000002A may also show “INCONSISTENT_IRP” on the same blue screen. BSoD usually occurs when some IRP field was inconsistent with the state of the IRP. An example can be completed IRP, remaining in a device driver queue. This error is not currently used, but there is for debugging purposes. |
| 0x0000002B | PANIC_STACK_SWITCH | This BSOD means that the kernel mode stack was overrun. BSOD error code 0x0000002B may also show “PANIC_STACK_SWITCH” on the same blue screen. This BSoD error could be caused by a kernel-mode driver that uses too much stack space or data corruption in the kernel. |
| 0x0000002C | PORT_DRIVER_INTERNAL | This BSOD is uncommon. BSOD error code 0x0000002C may also show “PORT_DRIVER_INTERNAL” on the same blue screen. It indicates an internal error in the port driver. |
| 0x0000002D | SCSI_DISK_DRIVER_INTERNAL | This BSOD is uncommon. BSOD error code 0x0000002D may also show “SCSI_DISK_DRIVER_INTERNAL” on the same blue screen. 0x0000002D indicates an internal error in a SCSI hard disk and driver. |
| 0x0000002E | DATA_BUS_ERROR | #N/A |
| 0x0000002F | INSTRUCTION_BUS_ERROR | This BSOD is uncommon. BSOD error code 0x0000002F may also show “INSTRUCTION_BUS_ERROR” on the same blue screen. This BSoD 0x0000002F is almost always caused by a problem of hardware – configuration problem, a hardware defect or incompatibility. The most common problems of hardware, that can cause this error is faulty RAM, the cache memory RAM error level 2 (L2), or video memory errors. Hard disk corruption can also cause this error. This error can also be caused when a device driver tries to access an address in 0x8xxxxxxx range that does not exist (in other words, that does not have a physical address mapping). |
| 0x00000030 | SET_OF_INVALID_CONTEXT | This BSOD means that the stack pointer in a trap frame had an invalid value. BSOD error code 0x00000030 may also show “SET_OF_INVALID_CONTEXT” on the same blue screen. Blue Screen of 0x0000002F indicates an error instruction bus. |
| 0x00000031 | PHASE0_INITIALIZATION_FAILED | This BSOD means that system initialization failed. BSOD error code 0x00000031 may also show “PHASE0_INITIALIZATION_FAILED” on the same blue screen. BSoD occurs when some routine attempts to set the pointer to the top of the trap stack frame in a value less than the current value of the stack pointer. |
| 0x00000032 | PHASE1_INITIALIZATION_FAILED | This BSOD means that system initialization failed. BSOD error code 0x00000032 may also show “PHASE1_INITIALIZATION_FAILED” on the same blue screen. At a very early stage of initialization, the system failed. An error caused by device drivers. |
| 0x00000033 | UNEXPECTED_INITIALIZATION_CALL | This BSOD is uncommon. BSOD error code 0x00000033 may also show “UNEXPECTED_INITIALIZATION_CALL” on the same blue screen. 0x00000033 indicates that during the initialization phase has stopped working Windows 2000. Most likely a problem with the device driver. |
| 0x00000034 | CACHE_MANAGER | This BSOD means that a problem occurred in the file system’s cache manager. BSOD error code 0x00000034 may also show “CACHE_MANAGER” on the same blue screen. Depletion paged memory pool does not cause the error. During the indexing process, if the amount of available paged pool memory is not very small, the other driver does not require the pool paged memory, can trigger this error. |
| 0x00000035 | NO_MORE_IRP_STACK_LOCATIONS | This BSOD occurs when the IoCallDriver packet has no more stack locations remaining BSOD error code 0x00000035 may also show “NO_MORE_IRP_STACK_LOCATIONS” on the same blue screen. he emergence of high-level attempt Bsod caused the driver to call the lower-level driver through the interface IoCallDriver filled with the stack area. Because of what the lower level driver has no access to its parameters. This is a fatal mistake, as a high-level driver filled settings for the low-level driver (as required), while in the stack is no space for low-level driver. Also, an error may indicate memory corruption. This error indicates a problem with the controller also may indicate that the RAM is faulty. |
| 0x00000036 | DEVICE_REFERENCE_COUNT_NOT_ZERO | This BSOD means that a driver attempted to delete a device object that still had a positive reference count. BSOD error code 0x00000036 may also show “DEVICE_REFERENCE_COUNT_NOT_ZERO” on the same blue screen. A device driver attempted to remove one of its objects “unit” systems, but the reference count for the object is non-zero. This is a mistake of the device driver request. |
| 0x00000037 | FLOPPY_INTERNAL_ERROR | This BSOD is uncommon. BSOD error code 0x00000037 may also show “FLOPPY_INTERNAL_ERROR” on the same blue screen. 0x00000037 indicates an internal error floppy disk driver. |
| 0x00000038 | SERIAL_DRIVER_INTERNAL | This BSOD is uncommon. BSOD error code 0x00000038 may also show “SERIAL_DRIVER_INTERNAL” on the same blue screen. 0x00000038 indicates an internal serial port driver error. |
| 0x00000039 | SYSTEM_EXIT_OWNED_MUTEX | This BSOD means that the worker routine returned without releasing the mutex object that it owned. BSOD error code 0x00000039 may also show “SYSTEM_EXIT_OWNED_MUTEX” on the same blue screen. 0x00000038 indicates an internal serial port driver error. |
| 0x0000003A | SYSTEM_UNWIND_PREVIOUS_USER | This BSOD is uncommon. BSOD error code 0x0000003A may also show “SYSTEM_UNWIND_PREVIOUS_USER” on the same blue screen. A pretty rare error, the blue screen of death 0x00000039 indicates that an attempt has been made to exit the system service when one or more mutexes are accessing it which means that an attempt has been made to return to user mode through the System Service Manager. |
| 0x0000003B | SYSTEM_SERVICE_EXCEPTION | This BSOD means that an exception happened while executing a routine that transitions from non-privileged code to privileged code. BSOD error code 0x0000003B may also show “SYSTEM_SERVICE_EXCEPTION” on the same blue screen. BSoD 0x0000003B is caused by excessive use of the pool of swappable memory and may appear due to overlapping user-mode graphics drivers and when transferring incorrect data to the kernel code. |
| 0x0000003C | INTERRUPT_UNWIND_ATTEMPTED | This BSOD is uncommon. BSOD error code 0x0000003C may also show “INTERRUPT_UNWIND_ATTEMPTED” on the same blue screen. It is a Windows 2000 test mode error. |
| 0x0000003D | INTERRUPT_EXCEPTION_NOT_HANDLED | This BSOD is uncommon. BSOD error code 0x0000003D may also show “INTERRUPT_EXCEPTION_NOT_HANDLED” on the same blue screen. 0x0000003D blue screen is a test error in Windows 2000. |
| 0x0000003E | MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED | This BSOD means that the system has multiple processors, but they are asymmetric in relation to one another. BSOD error code 0x0000003E may also show “MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED” on the same blue screen. 0x0000003E indicates the presence of several processors in the system, while they are asymmetric with respect to each other. Stop 0x0000003E means a multiprocessor configuration is not supported. For example, not all processors are of the same level or of the same type. |
| 0x0000003F | NO_MORE_SYSTEM_PTES | This BSOD is the result of a system which has performed too many I/O actions. This has resulted in fragmented system page table entries (PTE). BSOD error code 0x0000003F may also show “NO_MORE_SYSTEM_PTES” on the same blue screen. The main reason for the blue screen to appear is that the driver tried to request a large block of virtual memory, but there is no continuous block of sufficient size to satisfy this request. Often video drivers try to capture a huge amount of memory, which simply does not exist. Backup programs can also cause this error. It Indicates one of the following problems: Records page table system (Pte) are deleted or fragmented by the system when a large number of input/output (I / S) is performed A faulty device driver does not work properly with the memory An application as a backup program incorrectly allocates large amounts of memory. Remove all newly installed software (pay special attention to utilities that work with hard drives) and newly installed drivers |
| 0x00000040 | TARGET_MDL_TOO_SMALL | This BSOD means that a driver has improperly used IoBuildPartialMdl BSOD error code 0x00000040 may also show “TARGET_MDL_TOO_SMALL” on the same blue screen. A newly installed hardware and software uninstall is recommended to find the problem. Make sure your newly added hardware is compatible with your Windows and download the latest available drivers directly from the site of your hardware manufacturer. |
| 0x00000041 | MUST_SUCCEED_POOL_EMPTY | This BSOD means that a kernel-mode thread has requested too much must-succeed pool. BSOD error code 0x00000041 may also show “MUST_SUCCEED_POOL_EMPTY” on the same blue screen. In Windows 2000, the must-succeed pool size is very small. Windows XP lacks the ability of drivers to use the must-succeed pool to execute their commands. |
| 0x00000042 | ATDISK_DRIVER_INTERNAL | This BSOD is uncommon. BSOD error code 0x00000042 may also show “ATDISK_DRIVER_INTERNAL” on the same blue screen. This BSOD appears very rarely, the blue screen of death 0x00000042 indicates an internal error in the hard disk and driver. |
| 0x00000043 | NO_SUCH_PARTITION | This BSOD is uncommon. BSOD error code 0x00000043 may also show “NO_SUCH_PARTITION” on the same blue screen. This BSOD appears very rarely, if ever. Reveals a hard disk problem. Scan your computer with an online antivirus and check for viruses. Test your hard drive with the utility available on the manufacturer’s site. |
| 0x00000044 | MULTIPLE_IRP_COMPLETE_REQUESTS | This BSOD means that a driver has tried to requested an IRP be completed that is already complete. BSOD error code 0x00000044 may also show “MULTIPLE_IRP_COMPLETE_REQUESTS” on the same blue screen. Usually, this BSOD is affected by problems with a device driver. To delete or obtain more accurate information follows. The driver called the IoCompleteRequest () function to complete the IRP, but the package has already completed. |
| 0x00000045 | INSUFFICIENT_SYSTEM_MAP_REGS | This BSOD is uncommon. BSOD error code 0x00000045 may also show “INSUFFICIENT_SYSTEM_MAP_REGS” on the same blue screen. 0x00000045 indicates that an attempt was made to allocate more map registers than the adapter. |
| 0x00000046 | DEREF_UNKNOWN_LOGON_SESSION | This BSOD is uncommon. BSOD error code 0x00000046 may also show “DEREF_UNKNOWN_LOGON_SESSION” on the same blue screen. The blue screen of death 0x00000046 indicates the removal of a token that is not part of any login session. |
| 0x00000047 | REF_UNKNOWN_LOGON_SESSION | This BSOD is uncommon. BSOD error code 0x00000047 may also show “REF_UNKNOWN_LOGON_SESSION” on the same blue screen. A blue screen of 0x00000047 indicates that a token has been created that is not part of any login sessions. |
| 0x00000048 | CANCEL_STATE_IN_COMPLETED_IRP | This BSOD means that an I/O request packet (IRP) was completed, and then was subsequently canceled. BSOD error code 0x00000048 may also show “CANCEL_STATE_IN_COMPLETED_IRP” on the same blue screen. If this happens to you after installing a device, check for the latest version of the driver on the internet, directly on the manufacturer’s site. |
| 0x00000049 | PAGE_FAULT_WITH_INTERRUPTS_OFF | This BSOD is uncommon. BSOD error code 0x00000049 may also show “PAGE_FAULT_WITH_INTERRUPTS_OFF” on the same blue screen. A blue screen of 0x00000049 indicates a missing page during the interrupt disable. |
| 0x0000004A | IRQL_GT_ZERO_AT_SYSTEM_SERVICE | This BSOD means that a thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL. BSOD error code 0x0000004A may also show “IRQL_GT_ZERO_AT_SYSTEM_SERVICE” on the same blue screen. The blue screen 0x0000004A indicates that the thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL. |
| 0x0000004B | STREAMS_INTERNAL_ERROR | This BSOD is uncommon. BSOD error code 0x0000004B may also show “STREAMS_INTERNAL_ERROR” on the same blue screen. The 0x0000004B blue screen indicates an internal error in the streaming environment or in the streaming driver. |
| 0x0000004C | FATAL_UNHANDLED_HARD_ERROR | This BSOD is uncommon. BSOD error code 0x0000004C may also show “FATAL_UNHANDLED_HARD_ERROR” on the same blue screen. The blue screen of death 0x0000004C indicates that a fatal serious error occurred before the error handler was available. There are several reasons why this error could occur: the registry data structure file could not be loaded because it is either damaged or not found Winlogon or Windows did not start unexpectedly Driver or system dll is damaged |
| 0x0000004D | NO_PAGES_AVAILABLE | This BSOD means that no free pages are available to continue operations. BSOD error code 0x0000004D may also show “NO_PAGES_AVAILABLE” on the same blue screen. The 0x0000004D blue screen indicates a lack of free space for operations. There are a large number of causes of the Stop 0x0000004D error, but the culprit is always the same – the device driver. |
| 0x0000004E | PFN_LIST_CORRUPT | This BSOD means that the page frame number (PFN) list is corrupted. BSOD error code 0x0000004E may also show “PFN_LIST_CORRUPT” on the same blue screen. This means that the PFN list is damaged. It can be caused by a malfunction of physical memory or driver incorrectly installed. |
| 0x0000004F | NDIS_INTERNAL_ERROR | This BSOD is uncommon. BSOD error code 0x0000004F may also show “NDIS_INTERNAL_ERROR” on the same blue screen. The 0x0000004F blue screen indicates an internal NDIS driver error (Network Driver Interface Specification). This is a very rare error, which indicates an internal error in the shell NDIS (Interface Specification Network Controller) or the NDIS driver. Make sure you have the card driver installed network freshest. |
| 0x00000050 | PAGE_FAULT_IN_NONPAGED_AREA | This BSOD means that invalid system memory has been referenced. BSOD error code 0x00000050 may also show “PAGE_FAULT_IN_NONPAGED_AREA” on the same blue screen. |
| 0x00000051 | REGISTRY_ERROR | This BSOD means that a severe registry error has occurred. BSOD error code 0x00000051 may also show “REGISTRY_ERROR” on the same blue screen. |
| 0x00000052 | MAILSLOT_FILE_SYSTEM | This BSOD is uncommon. BSOD error code 0x00000052 may also show “MAILSLOT_FILE_SYSTEM” on the same blue screen. |
| 0x00000053 | NO_BOOT_DEVICE | This BSOD is uncommon. BSOD error code 0x00000053 may also show “NO_BOOT_DEVICE” on the same blue screen. |
| 0x00000054 | LM_SERVER_INTERNAL_ERROR | This BSOD is uncommon. BSOD error code 0x00000054 may also show “LM_SERVER_INTERNAL_ERROR” on the same blue screen. |
| 0x00000055 | DATA_COHERENCY_EXCEPTION | This BSOD is uncommon. BSOD error code 0x00000055 may also show “DATA_COHERENCY_EXCEPTION” on the same blue screen. |
| 0x00000056 | INSTRUCTION_COHERENCY_EXCEPTION | This BSOD is uncommon. BSOD error code 0x00000056 may also show “INSTRUCTION_COHERENCY_EXCEPTION” on the same blue screen. |
| 0x00000057 | XNS_INTERNAL_ERROR | This BSOD is uncommon. BSOD error code 0x00000057 may also show “XNS_INTERNAL_ERROR” on the same blue screen. |
| 0x00000058 | FTDISK_INTERNAL_ERROR | This BSOD will appear if the system is booted from the wrong copy of a mirrored partition. BSOD error code 0x00000058 may also show “FTDISK_INTERNAL_ERROR” on the same blue screen. |
| 0x00000059 | PINBALL_FILE_SYSTEM | This BSOD means that a problem occurred in the Pinball file system. BSOD error code 0x00000059 may also show “PINBALL_FILE_SYSTEM” on the same blue screen. |
| 0x0000005A | CRITICAL_SERVICE_FAILED | This BSOD is uncommon. BSOD error code 0x0000005A may also show “CRITICAL_SERVICE_FAILED” on the same blue screen. |
| 0x0000005B | SET_ENV_VAR_FAILED | This BSOD is uncommon. BSOD error code 0x0000005B may also show “SET_ENV_VAR_FAILED” on the same blue screen. |
| 0x0000005C | HAL_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x0000005C may also show “HAL_INITIALIZATION_FAILED” on the same blue screen. |
| 0x0000005D | UNSUPPORTED_PROCESSOR | This BSOD means that the computer is attempting to run Windows on an unsupported processor. BSOD error code 0x0000005D may also show “UNSUPPORTED_PROCESSOR” on the same blue screen. |
| 0x0000005E | OBJECT_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x0000005E may also show “OBJECT_INITIALIZATION_FAILED” on the same blue screen. |
| 0x0000005F | SECURITY_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x0000005F may also show “SECURITY_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000060 | PROCESS_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x00000060 may also show “PROCESS_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000061 | HAL1_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x00000061 may also show “HAL1_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000062 | OBJECT1_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x00000062 may also show “OBJECT1_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000063 | SECURITY1_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x00000063 may also show “SECURITY1_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000064 | SYMBOLIC_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x00000064 may also show “SYMBOLIC_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000065 | MEMORY1_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x00000065 may also show “MEMORY1_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000066 | CACHE_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x00000066 may also show “CACHE_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000067 | CONFIG_INITIALIZATION_FAILED | This BSOD means that the registry configuration failed. BSOD error code 0x00000067 may also show “CONFIG_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000068 | FILE_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x00000068 may also show “FILE_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000069 | IO1_INITIALIZATION_FAILED | This BSOD means that the initialization of the I/O system failed for some reason. BSOD error code 0x00000069 may also show “IO1_INITIALIZATION_FAILED” on the same blue screen. |
| 0x0000006A | LPC_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x0000006A may also show “LPC_INITIALIZATION_FAILED” on the same blue screen. |
| 0x0000006B | PROCESS1_INITIALIZATION_FAILED | This BSOD means that the initialization of the Microsoft Windows operating system failed. BSOD error code 0x0000006B may also show “PROCESS1_INITIALIZATION_FAILED” on the same blue screen. |
| 0x0000006C | REFMON_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x0000006C may also show “REFMON_INITIALIZATION_FAILED” on the same blue screen. |
| 0x0000006D | SESSION1_INITIALIZATION_FAILED | This BSOD means that the initialization of the Microsoft Windows operating system failed. BSOD error code 0x0000006D may also show “SESSION1_INITIALIZATION_FAILED” on the same blue screen. |
| 0x0000006E | SESSION2_INITIALIZATION_FAILED | This BSOD means that the initialization of the Microsoft Windows operating system failed. BSOD error code 0x0000006E may also show “SESSION2_INITIALIZATION_FAILED” on the same blue screen. |
| 0x0000006F | SESSION3_INITIALIZATION_FAILED | This BSOD means that the initialization of the Microsoft Windows operating system initialization. BSOD error code 0x0000006F may also show “SESSION3_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000070 | SESSION4_INITIALIZATION_FAILED | This BSOD means that the initialization of the Microsoft Windows operating system failed. BSOD error code 0x00000070 may also show “SESSION4_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000071 | SESSION5_INITIALIZATION_FAILED | This BSOD means that the initialization of the Microsoft Windows operating system failed. BSOD error code 0x00000071 may also show “SESSION5_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000072 | ASSIGN_DRIVE_LETTERS_FAILED | This BSOD is uncommon. BSOD error code 0x00000072 may also show “ASSIGN_DRIVE_LETTERS_FAILED” on the same blue screen. |
| 0x00000073 | CONFIG_LIST_FAILED | This BSOD means that one of the top-level registry keys, also known as core system hives, cannot be linked in the registry tree. BSOD error code 0x00000073 may also show “CONFIG_LIST_FAILED” on the same blue screen. |
| 0x00000074 | BAD_SYSTEM_CONFIG_INFO | This BSOD means that there is an error in the registry. BSOD error code 0x00000074 may also show “BAD_SYSTEM_CONFIG_INFO” on the same blue screen. |
| 0x00000075 | CANNOT_WRITE_CONFIGURATION | This BSOD means that the SYSTEM registry hive file cannot be converted to a mapped file. BSOD error code 0x00000075 may also show “CANNOT_WRITE_CONFIGURATION” on the same blue screen. |
| 0x00000076 | PROCESS_HAS_LOCKED_PAGES | This BSOD means that a driver failed to release locked pages after an I/O operation. BSOD error code 0x00000076 may also show “PROCESS_HAS_LOCKED_PAGES” on the same blue screen. |
| 0x00000077 | KERNEL_STACK_INPAGE_ERROR | This BSOD means that the requested page of kernel data from the paging file could not be read into memory. BSOD error code 0x00000077 may also show “KERNEL_STACK_INPAGE_ERROR” on the same blue screen. |
| 0x00000078 | PHASE0_EXCEPTION | This BSOD is uncommon. BSOD error code 0x00000078 may also show “PHASE0_EXCEPTION” on the same blue screen. |
| 0x00000079 | MISMATCHED_HAL | This BSOD means that the Hardware Abstraction Layer (HAL) revision level or configuration does not match that of the kernel or the computer. BSOD error code 0x00000079 may also show “MISMATCHED_HAL” on the same blue screen. |
| 0x0000007A | KERNEL_DATA_INPAGE_ERROR | This BSOD means that the requested page of kernel data from the paging file could not be read into memory. BSOD error code 0x0000007A may also show “KERNEL_DATA_INPAGE_ERROR” on the same blue screen. |
| 0x0000007B | INACCESSIBLE_BOOT_DEVICE | This BSOD means that the Microsoft Windows operating system has lost access to the system partition during startup. BSOD error code 0x0000007B may also show “INACCESSIBLE_BOOT_DEVICE” on the same blue screen. |
| 0x0000007C | BUGCODE_NDIS_DRIVER | This BSOD means that a problem occurred with an NDIS driver. BSOD error code 0x0000007C may also show “BUGCODE_NDIS_DRIVER” on the same blue screen. |
| 0x0000007D | INSTALL_MORE_MEMORY | This BSOD means that there is not enough memory to start the Microsoft Windows operating system. BSOD error code 0x0000007D may also show “INSTALL_MORE_MEMORY” on the same blue screen. |
| 0x0000007E | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED | This BSOD means that a system thread generated an exception that the error handler did not catch. BSOD error code 0x0000007E may also show “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED” on the same blue screen. |
| 0x0000007F | UNEXPECTED_KERNEL_MODE_TRAP | This BSOD means that the Intel CPU generated a trap and the kernel failed to catch this trap. BSOD error code 0x0000007F may also show “UNEXPECTED_KERNEL_MODE_TRAP” on the same blue screen. |
| 0x00000080 | NMI_HARDWARE_FAILURE | This BSOD means that a hardware malfunction has occurred. BSOD error code 0x00000080 may also show “NMI_HARDWARE_FAILURE” on the same blue screen. |
| 0x00000081 | SPIN_LOCK_INIT_FAILURE | This BSOD is uncommon. BSOD error code 0x00000081 may also show “SPIN_LOCK_INIT_FAILURE” on the same blue screen. |
| 0x00000082 | DFS_FILE_SYSTEM | This BSOD is uncommon. BSOD error code 0x00000082 may also show “DFS_FILE_SYSTEM” on the same blue screen. |
| 0x00000083 | OFS_FILE_SYSTEM | #N/A |
| 0x00000084 | RECOM_DRIVER | #N/A |
| 0x00000085 | SETUP_FAILURE | This BSOD means that a fatal error occurred during setup. BSOD error code 0x00000085 may also show “SETUP_FAILURE” on the same blue screen. |
| 0x0000008B | MBR_CHECKSUM_MISMATCH | This BSOD means that a mismatch has occurred in the MBR checksum. BSOD error code 0x0000008B may also show “MBR_CHECKSUM_MISMATCH” on the same blue screen. |
| 0x0000008E | KERNEL_MODE_EXCEPTION_NOT_HANDLED | This BSOD means that a kernel-mode application generated an exception that the error handler did not catch. BSOD error code 0x0000008E may also show “KERNEL_MODE_EXCEPTION_NOT_HANDLED” on the same blue screen. |
| 0x0000008F | PP0_INITIALIZATION_FAILED | This BSOD means that the Plug and Play (PnP) manager could not be initialized. BSOD error code 0x0000008F may also show “PP0_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000090 | PP1_INITIALIZATION_FAILED | This BSOD means that the Plug and Play (PnP) manager could not be initialized. BSOD error code 0x00000090 may also show “PP1_INITIALIZATION_FAILED” on the same blue screen. |
| 0x00000091 | WIN32K_INIT_OR_RIT_FAILURE | #N/A |
| 0x00000092 | UP_DRIVER_ON_MP_SYSTEM | This BSOD means that a uniprocessor-only driver has been loaded on a multiprocessor system. BSOD error code 0x00000092 may also show “UP_DRIVER_ON_MP_SYSTEM” on the same blue screen. |
| 0x00000093 | INVALID_KERNEL_HANDLE | This BSOD means that an invalid or protected handle was passed to NtClose. BSOD error code 0x00000093 may also show “INVALID_KERNEL_HANDLE” on the same blue screen. |
| 0x00000094 | KERNEL_STACK_LOCKED_AT_EXIT | This BSOD means that a thread exited while its kernel stack was marked as not swappable. BSOD error code 0x00000094 may also show “KERNEL_STACK_LOCKED_AT_EXIT” on the same blue screen. |
| 0x00000095 | PNP_INTERNAL_ERROR | #N/A |
| 0x00000096 | INVALID_WORK_QUEUE_ITEM | This BSOD means that a queue entry was removed that contained a null pointer. BSOD error code 0x00000096 may also show “INVALID_WORK_QUEUE_ITEM” on the same blue screen. |
| 0x00000097 | BOUND_IMAGE_UNSUPPORTED | This BSOD is uncommon. BSOD error code 0x00000097 may also show “BOUND_IMAGE_UNSUPPORTED” on the same blue screen. |
| 0x00000098 | END_OF_NT_EVALUATION_PERIOD | This BSOD means that the trial period for the Microsoft Windows operating system has ended. BSOD error code 0x00000098 may also show “END_OF_NT_EVALUATION_PERIOD” on the same blue screen. |
| 0x00000099 | INVALID_REGION_OR_SEGMENT | This BSOD means that ExInitializeRegion or ExInterlockedExtendRegion was called with an invalid set of parameters. BSOD error code 0x00000099 may also show “INVALID_REGION_OR_SEGMENT” on the same blue screen. |
| 0x0000009A | SYSTEM_LICENSE_VIOLATION | This BSOD means that the software license agreement has been violated. BSOD error code 0x0000009A may also show “SYSTEM_LICENSE_VIOLATION” on the same blue screen. |
| 0x0000009B | UDFS_FILE_SYSTEM | This BSOD means that a problem occurred in the UDF file system. BSOD error code 0x0000009B may also show “UDFS_FILE_SYSTEM” on the same blue screen. |
| 0x0000009C | MACHINE_CHECK_EXCEPTION | This BSOD means that a fatal machine check exception has occurred. BSOD error code 0x0000009C may also show “MACHINE_CHECK_EXCEPTION” on the same blue screen. |
| 0x0000009E | USER_MODE_HEALTH_MONITOR | This BSOD means that one or more critical user-mode components failed to satisfy a health check. BSOD error code 0x0000009E may also show “USER_MODE_HEALTH_MONITOR” on the same blue screen. |
| 0x0000009F | DRIVER_POWER_STATE_FAILURE | This BSOD means that the driver is in an inconsistent or invalid power state. BSOD error code 0x0000009F may also show “DRIVER_POWER_STATE_FAILURE” on the same blue screen. |
| 0x000000A0 | INTERNAL_POWER_ERROR | This BSOD means that the power policy manager experienced a fatal error. BSOD error code 0x000000A0 may also show “INTERNAL_POWER_ERROR” on the same blue screen. |
| 0x000000A1 | PCI_BUS_DRIVER_INTERNAL | This BSOD means that the PCI Bus driver detected inconsistency problems in its internal structures and could not continue. BSOD error code 0x000000A1 may also show “PCI_BUS_DRIVER_INTERNAL” on the same blue screen. |
| 0x000000A2 | MEMORY_IMAGE_CORRUPT | This BSOD means that corruption has been detected in the image of an executable file in memory. BSOD error code 0x000000A2 may also show “MEMORY_IMAGE_CORRUPT” on the same blue screen. |
| 0x000000A3 | ACPI_DRIVER_INTERNAL | This BSOD means that the ACPI driver detected an internal inconsistency. BSOD error code 0x000000A3 may also show “ACPI_DRIVER_INTERNAL” on the same blue screen. |
| 0x000000A4 | CNSS_FILE_SYSTEM_FILTER | This BSOD means that a problem occurred in the CNSS file system filter. BSOD error code 0x000000A4 may also show “CNSS_FILE_SYSTEM_FILTER” on the same blue screen. |
| 0x000000A5 | ACPI_BIOS_ERROR | This BSOD means that the Advanced Configuration and Power Interface (ACPI) BIOS of the computer is not fully compliant with the ACPI specification. BSOD error code 0x000000A5 may also show “ACPI_BIOS_ERROR” on the same blue screen. |
| 0x000000A7 | BAD_EXHANDLE | This BSOD means that the kernel-mode handle table detected an inconsistent handle table entry state. BSOD error code 0x000000A7 may also show “BAD_EXHANDLE” on the same blue screen. |
| 0x000000AB | SESSION_HAS_VALID_POOL_ON_EXIT | This BSOD means that a session unload occurred while a session driver still held memory. BSOD error code 0x000000AB may also show “SESSION_HAS_VALID_POOL_ON_EXIT” on the same blue screen. |
| 0x000000AC | HAL_MEMORY_ALLOCATION | This BSOD means that the hardware abstraction layer (HAL) could not obtain sufficient memory. BSOD error code 0x000000AC may also show “HAL_MEMORY_ALLOCATION” on the same blue screen. |
| 0x000000AD | VIDEO_DRIVER_DEBUG_REPORT_REQUEST | This BSOD means that the video port created a non-fatal minidump on behalf of the video driver during run time. BSOD error code 0x000000AD may also show “VIDEO_DRIVER_DEBUG_REPORT_REQUEST” on the same blue screen. |
| 0x000000B4 | VIDEO_DRIVER_INIT_FAILURE | This BSOD means that Windows was unable to enter graphics mode. BSOD error code 0x000000B4 may also show “VIDEO_DRIVER_INIT_FAILURE” on the same blue screen. |
| 0x000000B8 | ATTEMPTED_SWITCH_FROM_DPC | This BSOD means that an illegal operation was attempted by a delayed procedure call (DPC) routine. BSOD error code 0x000000B8 may also show “ATTEMPTED_SWITCH_FROM_DPC” on the same blue screen. |
| 0x000000B9 | CHIPSET_DETECTED_ERROR | This BSOD is uncommon. BSOD error code 0x000000B9 may also show “CHIPSET_DETECTED_ERROR” on the same blue screen. |
| 0x000000BA | SESSION_HAS_VALID_VIEWS_ON_EXIT | This BSOD means that a session driver still had mapped views when the session unloaded. BSOD error code 0x000000BA may also show “SESSION_HAS_VALID_VIEWS_ON_EXIT” on the same blue screen. |
| 0x000000BB | NETWORK_BOOT_INITIALIZATION_FAILED | This BSOD means that Windows failed to successfully boot off a network. BSOD error code 0x000000BB may also show “NETWORK_BOOT_INITIALIZATION_FAILED” on the same blue screen. |
| 0x000000BC | NETWORK_BOOT_DUPLICATE_ADDRESS | This BSOD means that a duplicate IP address was assigned to this machine while booting off a network. BSOD error code 0x000000BC may also show “NETWORK_BOOT_DUPLICATE_ADDRESS” on the same blue screen. |
| 0x000000BE | ATTEMPTED_WRITE_TO_READONLY_MEMORY | This BSOD will display if a driver attempts to write to a read-only memory segment. BSOD error code 0x000000BE may also show “ATTEMPTED_WRITE_TO_READONLY_MEMORY” on the same blue screen. |
| 0x000000BF | MUTEX_ALREADY_OWNED | This BSOD means that a thread attempted to acquire ownership of a mutex it already owned. BSOD error code 0x000000BF may also show “MUTEX_ALREADY_OWNED” on the same blue screen. |
| 0x000000C1 | SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION | This BSOD means that the driver wrote to an invalid section of the special pool. BSOD error code 0x000000C1 may also show “SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION” on the same blue screen. |
| 0x000000C2 | BAD_POOL_CALLER | This BSOD means that the current thread is making a bad pool request. BSOD error code 0x000000C2 may also show “BAD_POOL_CALLER” on the same blue screen. |
| 0x000000C4 | DRIVER_VERIFIER_DETECTED_VIOLATION | This BSOD is the general STOP code code for fatal errors found by Driver Verifier. BSOD error code 0x000000C4 may also show “DRIVER_VERIFIER_DETECTED_VIOLATION” on the same blue screen. |
| 0x000000C5 | DRIVER_CORRUPTED_EXPOOL | This BSOD means that the system attempted to access invalid memory at a process IRQL that was too high. BSOD error code 0x000000C5 may also show “DRIVER_CORRUPTED_EXPOOL” on the same blue screen. |
| 0x000000C6 | DRIVER_CAUGHT_MODIFYING_FREED_POOL | This BSOD means that the driver attempted to access a freed memory pool. BSOD error code 0x000000C6 may also show “DRIVER_CAUGHT_MODIFYING_FREED_POOL” on the same blue screen. |
| 0x000000C7 | TIMER_OR_DPC_INVALID | This BSOD appears if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted. BSOD error code 0x000000C7 may also show “TIMER_OR_DPC_INVALID” on the same blue screen. |
| 0x000000C8 | IRQL_UNEXPECTED_VALUE | This BSOD means that the processor’s IRQL is not what it should be at this time. BSOD error code 0x000000C8 may also show “IRQL_UNEXPECTED_VALUE” on the same blue screen. |
| 0x000000C9 | DRIVER_VERIFIER_IOMANAGER_VIOLATION | This BSOD is the STOP code code for all Driver Verifier I/O Verification violations. BSOD error code 0x000000C9 may also show “DRIVER_VERIFIER_IOMANAGER_VIOLATION” on the same blue screen. |
| 0x000000CA | PNP_DETECTED_FATAL_ERROR | This BSOD means that the Plug and Play Manager encountered a severe error, probably as a result of a problematic Plug and Play driver. BSOD error code 0x000000CA may also show “PNP_DETECTED_FATAL_ERROR” on the same blue screen. |
| 0x000000CB | DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS | This BSOD means that a driver or the I/O manager failed to release locked pages after an I/O operation. BSOD error code 0x000000CB may also show “DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS” on the same blue screen. |
| 0x000000CC | PAGE_FAULT_IN_FREED_SPECIAL_POOL | This BSOD means that the system has referenced memory which was earlier freed. BSOD error code 0x000000CC may also show “PAGE_FAULT_IN_FREED_SPECIAL_POOL” on the same blue screen. |
| 0x000000CD | PAGE_FAULT_BEYOND_END_OF_ALLOCATION | This BSOD means that the system accessed memory beyond the end of some driver’s pool allocation. BSOD error code 0x000000CD may also show “PAGE_FAULT_BEYOND_END_OF_ALLOCATION” on the same blue screen. |
| 0x000000CE | DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS | This BSOD means that a driver failed to cancel pending operations before unloading. BSOD error code 0x000000CE may also show “DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS” on the same blue screen. |
| 0x000000CF | TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE | This BSOD means that a driver has been incorrectly ported to the terminal server. BSOD error code 0x000000CF may also show “TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE” on the same blue screen. |
| 0x000000D0 | DRIVER_CORRUPTED_MMPOOL | This BSOD means that the system attempted to access invalid memory at a process IRQL that was too high. BSOD error code 0x000000D0 may also show “DRIVER_CORRUPTED_MMPOOL” on the same blue screen. |
| 0x000000D1 | DRIVER_IRQL_NOT_LESS_OR_EQUAL | This BSOD means that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high. BSOD error code 0x000000D1 may also show “DRIVER_IRQL_NOT_LESS_OR_EQUAL” on the same blue screen. |
| 0x000000D2 | BUGCODE_ID_DRIVER | This BSOD means that a problem occurred with an NDIS driver. BSOD error code 0x000000D2 may also show “BUGCODE_ID_DRIVER” on the same blue screen. |
| 0x000000D3 | DRIVER_PORTION_MUST_BE_NONPAGED | This BSOD means that the system attempted to access pageable memory at a process IRQL that was too high. BSOD error code 0x000000D3 may also show “DRIVER_PORTION_MUST_BE_NONPAGED” on the same blue screen. |
| 0x000000D4 | SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD | This BSOD means that a driver did not cancel pending operations before unloading. BSOD error code 0x000000D4 may also show “SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD” on the same blue screen. |
| 0x000000D5 | DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL | This BSOD means that a driver has referenced memory which was earlier freed. BSOD error code 0x000000D5 may also show “DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL” on the same blue screen. |
| 0x000000D6 | DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION | This BSOD means the driver accessed memory beyond the end of its pool allocation. BSOD error code 0x000000D6 may also show “DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION” on the same blue screen. |
| 0x000000D7 | DRIVER_UNMAPPING_INVALID_VIEW | This BSOD means a driver is trying to unmap an address that was not mapped. BSOD error code 0x000000D7 may also show “DRIVER_UNMAPPING_INVALID_VIEW” on the same blue screen. |
| 0x000000D8 | DRIVER_USED_EXCESSIVE_PTES | This BSOD means that there are no more system page table entries (PTE) remaining. BSOD error code 0x000000D8 may also show “DRIVER_USED_EXCESSIVE_PTES” on the same blue screen. |
| 0x000000D9 | LOCKED_PAGES_TRACKER_CORRUPTION | This BSOD means that the internal locked-page tracking structures have been corrupted. BSOD error code 0x000000D9 may also show “LOCKED_PAGES_TRACKER_CORRUPTION” on the same blue screen. |
| 0x000000DA | SYSTEM_PTE_MISUSE | This BSOD means that a page table entry (PTE) routine has been used in an improper way. BSOD error code 0x000000DA may also show “SYSTEM_PTE_MISUSE” on the same blue screen. |
| 0x000000DB | DRIVER_CORRUPTED_SYSPTES | This BSOD means that an attempt was made to touch memory at an invalid IRQL, probably due to corruption of system PTEs. BSOD error code 0x000000DB may also show “DRIVER_CORRUPTED_SYSPTES” on the same blue screen. |
| 0x000000DC | DRIVER_INVALID_STACK_ACCESS | This BSOD means that a driver accessed a stack address that lies below the stack pointer of the stack’s thread. BSOD error code 0x000000DC may also show “DRIVER_INVALID_STACK_ACCESS” on the same blue screen. |
| 0x000000DE | POOL_CORRUPTION_IN_FILE_AREA | This BSOD means that a driver has corrupted pool memory that is used for holding pages destined for disk. BSOD error code 0x000000DE may also show “POOL_CORRUPTION_IN_FILE_AREA” on the same blue screen. |
| 0x000000DF | IMPERSONATING_WORKER_THREAD | This BSOD means that a workitem did not disable impersonation before it completed. BSOD error code 0x000000DF may also show “IMPERSONATING_WORKER_THREAD” on the same blue screen. |
| 0x000000E0 | ACPI_BIOS_FATAL_ERROR | This BSOD means that one of your computer components is faulty. BSOD error code 0x000000E0 may also show “ACPI_BIOS_FATAL_ERROR” on the same blue screen. |
| 0x000000E1 | WORKER_THREAD_RETURNED_AT_BAD_IRQL | This BSOD means that a worker thread completed and returned with IRQL >= DISPATCH_LEVEL. BSOD error code 0x000000E1 may also show “WORKER_THREAD_RETURNED_AT_BAD_IRQL” on the same blue screen. |
| 0x000000E2 | MANUALLY_INITIATED_CRASH | This BSOD means that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard. BSOD error code 0x000000E2 may also show “MANUALLY_INITIATED_CRASH” on the same blue screen. |
| 0x000000E3 | RESOURCE_NOT_OWNED | This BSOD means that a thread tried to release a resource it did not own. BSOD error code 0x000000E3 may also show “RESOURCE_NOT_OWNED” on the same blue screen. |
| 0x000000E4 | WORKER_INVALID | This BSOD means that memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued. BSOD error code 0x000000E4 may also show “WORKER_INVALID” on the same blue screen. |
| 0x000000E6 | DRIVER_VERIFIER_DMA_VIOLATION | This BSOD is the STOP code for all Driver Verifier DMA Verification violations. BSOD error code 0x000000E6 may also show “DRIVER_VERIFIER_DMA_VIOLATION” on the same blue screen. |
| 0x000000E7 | INVALID_FLOATING_POINT_STATE | This BSOD means that a thread’s saved floating-point state is invalid. BSOD error code 0x000000E7 may also show “INVALID_FLOATING_POINT_STATE” on the same blue screen. |
| 0x000000E8 | INVALID_CANCEL_OF_FILE_OPEN | This BSOD means that an invalid file object was passed to IoCancelFileOpen. BSOD error code 0x000000E8 may also show “INVALID_CANCEL_OF_FILE_OPEN” on the same blue screen. |
| 0x000000E9 | ACTIVE_EX_WORKER_THREAD_TERMINATION | This BSOD means that an active executive worker thread is being terminated. BSOD error code 0x000000E9 may also show “ACTIVE_EX_WORKER_THREAD_TERMINATION” on the same blue screen. |
| 0x000000EA | THREAD_STUCK_IN_DEVICE_DRIVER | This BSOD means that a thread in a device driver is endlessly spinning. BSOD error code 0x000000EA may also show “THREAD_STUCK_IN_DEVICE_DRIVER” on the same blue screen. |
| 0x000000EB | DIRTY_MAPPED_PAGES_CONGESTION | This BSOD means that no free pages are available to continue operations. BSOD error code 0x000000EB may also show “DIRTY_MAPPED_PAGES_CONGESTION” on the same blue screen. |
| 0x000000EC | SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT | This BSOD means that a session unload occurred while a session driver still held memory. BSOD error code 0x000000EC may also show “SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT” on the same blue screen. |
| 0x000000ED | UNMOUNTABLE_BOOT_VOLUME | This BSOD means that the I/O subsystem attempted to mount the boot volume and it failed. BSOD error code 0x000000ED may also show “UNMOUNTABLE_BOOT_VOLUME” on the same blue screen. |
| 0x000000EF | CRITICAL_PROCESS_DIED | This BSOD means that a critical system process died. BSOD error code 0x000000EF may also show “CRITICAL_PROCESS_DIED” on the same blue screen. |
| 0x000000F1 | SCSI_VERIFIER_DETECTED_VIOLATION | This BSOD This is the STOP code code for all Driver Verifier SCSI Verification violations. BSOD error code 0x000000F1 may also show “SCSI_VERIFIER_DETECTED_VIOLATION” on the same blue screen. |
| 0x000000F3 | DISORDERLY_SHUTDOWN | This BSOD means that Windows was unable to shut down due to lack of memory. BSOD error code 0x000000F3 may also show “DISORDERLY_SHUTDOWN” on the same blue screen. |
| 0x000000F4 | CRITICAL_OBJECT_TERMINATION | This BSOD means that a process or thread crucial to system operation has unexpectedly exited or been terminated. BSOD error code 0x000000F4 may also show “CRITICAL_OBJECT_TERMINATION” on the same blue screen. |
| 0x000000F5 | FLTMGR_FILE_SYSTEM | This BSOD means that an unrecoverable failure occurred in the Filter Manager. BSOD error code 0x000000F5 may also show “FLTMGR_FILE_SYSTEM” on the same blue screen. |
| 0x000000F6 | PCI_VERIFIER_DETECTED_VIOLATION | This BSOD means that an error occurred in the BIOS or another device being verified by the PCI driver. BSOD error code 0x000000F6 may also show “PCI_VERIFIER_DETECTED_VIOLATION” on the same blue screen. |
| 0x000000F7 | DRIVER_OVERRAN_STACK_BUFFER | This BSOD means that a driver has overrun a stack-based buffer. BSOD error code 0x000000F7 may also show “DRIVER_OVERRAN_STACK_BUFFER” on the same blue screen. |
| 0x000000F8 | RAMDISK_BOOT_INITIALIZATION_FAILED | This BSOD means that an initialization failure occurred while attempting to boot from the RAM disk. BSOD error code 0x000000F8 may also show “RAMDISK_BOOT_INITIALIZATION_FAILED” on the same blue screen. |
| 0x000000F9 | DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN | This BSOD means that a driver returned STATUS_REPARSE to an IRP_MJ_CREATE request with no trailing names. BSOD error code 0x000000F9 may also show “DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN” on the same blue screen. |
| 0x000000FA | HTTP_DRIVER_CORRUPTED | This BSOD means that the HTTP kernel driver (Http.sys) has reached a corrupted state and cannot recover. BSOD error code 0x000000FA may also show “HTTP_DRIVER_CORRUPTED” on the same blue screen. |
| 0x000000FC | ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY | This BSOD means that an attempt was made to execute non-executable memory. BSOD error code 0x000000FC may also show “ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY” on the same blue screen. |
| 0x000000FD | DIRTY_NOWRITE_PAGES_CONGESTION | This BSOD means that there are no free pages available to continue basic system operations. BSOD error code 0x000000FD may also show “DIRTY_NOWRITE_PAGES_CONGESTION” on the same blue screen. |
| 0x000000FE | BUGCODE_USB_DRIVER | This BSOD means that an error has occurred in a Universal Serial Bus (USB) driver. BSOD error code 0x000000FE may also show “BUGCODE_USB_DRIVER” on the same blue screen. |
| 0x000000FF | RESERVE_QUEUE_OVERFLOW | This BSOD means that an attempt was made to insert a new item into a reserve queue, causing the queue to overflow. BSOD error code 0x000000FF may also show “RESERVE_QUEUE_OVERFLOW” on the same blue screen. |
| 0x00000100 | LOADER_BLOCK_MISMATCH | This BSOD means that either the loader block is invalid, or it does not match the system that is being loaded. BSOD error code 0x00000100 may also show “LOADER_BLOCK_MISMATCH” on the same blue screen. |
| 0x00000101 | CLOCK_WATCHDOG_TIMEOUT | This BSOD means that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval. BSOD error code 0x00000101 may also show “CLOCK_WATCHDOG_TIMEOUT” on the same blue screen. |
| 0x00000103 | MUP_FILE_SYSTEM | This BSOD means that the multiple UNC provider (MUP) has encountered invalid or unexpected data. As a result, the MUP cannot channel a remote file system request to a network redirector, the Universal Naming Convention (UNC) provider. BSOD error code 0x00000103 may also show “MUP_FILE_SYSTEM” on the same blue screen. |
| 0x00000104 | AGP_INVALID_ACCESS | This BSOD means that the GPU wrote to a range of Accelerated Graphics Port (AGP) memory that had not previously been committed. BSOD error code 0x00000104 may also show “AGP_INVALID_ACCESS” on the same blue screen. |
| 0x00000105 | AGP_GART_CORRUPTION | This BSOD means that the Graphics Aperture Remapping Table (GART) is corrupt. BSOD error code 0x00000105 may also show “AGP_GART_CORRUPTION” on the same blue screen. |
| 0x00000106 | AGP_ILLEGALLY_REPROGRAMMED | This BSOD means that the Accelerated Graphics Port (AGP) hardware has been reprogrammed by an unauthorized agent. BSOD error code 0x00000106 may also show “AGP_ILLEGALLY_REPROGRAMMED” on the same blue screen. |
| 0x00000108 | THIRD_PARTY_FILE_SYSTEM_FAILURE | This BSOD means that an unrecoverable problem has occurred in a third-party file system or file system filter. BSOD error code 0x00000108 may also show “THIRD_PARTY_FILE_SYSTEM_FAILURE” on the same blue screen. |
| 0x00000109 | CRITICAL_STRUCTURE_CORRUPTION | This BSOD means that the kernel has detected critical kernel code or data corruption. BSOD error code 0x00000109 may also show “CRITICAL_STRUCTURE_CORRUPTION” on the same blue screen. |
| 0x0000010A | APP_TAGGING_INITIALIZATION_FAILED | This BSOD is uncommon. BSOD error code 0x0000010A may also show “APP_TAGGING_INITIALIZATION_FAILED” on the same blue screen. |
| 0x0000010C | FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION | This BSOD means that a violation was detected in the File system Run-time library (FsRtl) Extra Create Parameter (ECP) package. BSOD error code 0x0000010C may also show “FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION” on the same blue screen. |
| 0x0000010D | WDF_VIOLATION | This BSOD means that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver. BSOD error code 0x0000010D may also show “WDF_VIOLATION” on the same blue screen. |
| 0x0000010E | VIDEO_MEMORY_MANAGEMENT_INTERNAL | This BSOD means that the video memory manager has encountered a condition that it is unable to recover from. BSOD error code 0x0000010E may also show “VIDEO_MEMORY_MANAGEMENT_INTERNAL” on the same blue screen. |
| 0x0000010F | RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED | This BSOD means that the kernel transaction manager detected that a kernel-mode resource manager has raised an exception in response to a direct call-back. The resource manager is in an unexpected and unrecoverable state. BSOD error code 0x0000010F may also show “RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED” on the same blue screen. |
| 0x00000111 | RECURSIVE_NMI | This BSOD means that a non-maskable-interrupt (NMI) occurred while a previous NMI was in progress. BSOD error code 0x00000111 may also show “RECURSIVE_NMI” on the same blue screen. |
| 0x00000112 | MSRPC_STATE_VIOLATION | This BSOD means that the Msrpc.sys driver has initiated a STOP code. BSOD error code 0x00000112 may also show “MSRPC_STATE_VIOLATION” on the same blue screen. |
| 0x00000113 | VIDEO_DXGKRNL_FATAL_ERROR | This BSOD means that the dxg kernel has detected a violation. BSOD error code 0x00000113 may also show “VIDEO_DXGKRNL_FATAL_ERROR” on the same blue screen. |
| 0x00000114 | VIDEO_SHADOW_DRIVER_FATAL_ERROR | This BSOD means that the shadow driver has detected a violation. BSOD error code 0x00000114 may also show “VIDEO_SHADOW_DRIVER_FATAL_ERROR” on the same blue screen. |
| 0x00000115 | AGP_INTERNAL | This BSOD means that the accelerated graphics port (AGP) driver has detected a violation. BSOD error code 0x00000115 may also show “AGP_INTERNAL” on the same blue screen. |
| 0x00000116 | VIDEO_TDR_ ERROR | This BSOD means that an attempt to reset the display driver and recover from a timeout failed. BSOD error code 0x00000116 may also show “VIDEO_TDR_ERROR” on the same blue screen. |
| 0x00000117 | VIDEO_TDR_TIMEOUT_DETECTED | This BSOD means that the display driver failed to respond in a timely fashion. BSOD error code 0x00000117 may also show “VIDEO_TDR_TIMEOUT_DETECTED” on the same blue screen. |
| 0x00000119 | VIDEO_SCHEDULER_INTERNAL_ERROR | This BSOD means that the video scheduler has detected a fatal violation. BSOD error code 0x00000119 may also show “VIDEO_SCHEDULER_INTERNAL_ERROR” on the same blue screen. |
| 0x0000011A | EM_INITIALIZATION_FAILURE | This BSOD is uncommon. BSOD error code 0x0000011A may also show “EM_INITIALIZATION_FAILURE” on the same blue screen. |
| 0x0000011B | DRIVER_RETURNED_HOLDING_CANCEL_LOCK | This BSOD means that a driver has returned from a cancel routine that holds the global cancel lock. This causes all later cancellation calls to fail, and results in either a deadlock or another STOP code. BSOD error code 0x0000011B may also show “DRIVER_RETURNED_HOLDING_CANCEL_LOCK” on the same blue screen. |
| 0x0000011C | ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE | This BSOD means that an attempt was made to write to the read-only protected storage of the configuration manager. BSOD error code 0x0000011C may also show “ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE” on the same blue screen. |
| 0x0000011D | EVENT_TRACING_FATAL_ERROR | This BSOD means that the Event Tracing subsystem has encountered an unexpected fatal error. BSOD error code 0x0000011D may also show “EVENT_TRACING_FATAL_ERROR” on the same blue screen. |
| 0x00000121 | DRIVER_VIOLATION | This BSOD means that a driver has caused a violation. BSOD error code 0x00000121 may also show “DRIVER_VIOLATION” on the same blue screen. |
| 0x00000122 | WHEA_INTERNAL_ERROR | This BSOD means that an internal error in the Windows Hardware Error Architecture (WHEA) has occurred. BSOD error code 0x00000122 may also show “WHEA_INTERNAL_ERROR” on the same blue screen. |
| 0x00000124 | WHEA_UNCORRECTABLE_ERROR | This BSOD means that a fatal hardware error has occurred. uses the error data that is provided by the Windows Hardware Error Architecture (WHEA). BSOD error code 0x00000124 may also show “WHEA_UNCORRECTABLE_ERROR” on the same blue screen. |
| 0x00000127 | PAGE_NOT_ZERO | This BSOD means that a page that should have been filled with zeros was not. This might occur because of a hardware error or because a privileged component of the operating system modified a page after freeing it. BSOD error code 0x00000127 may also show “PAGE_NOT_ZERO” on the same blue screen. |
| 0x0000012B | FAULTY_HARDWARE_CORRUPTED_PAGE | This BSOD means that a single-bit error was found in this page. This is a hardware memory error. BSOD error code 0x0000012B may also show “FAULTY_HARDWARE_CORRUPTED_PAGE” on the same blue screen. |
| 0x0000012C | EXFAT_FILE_SYSTEM | This BSOD means that a problem occurred in the Extended File Allocation Table (exFAT) file system. BSOD error code 0x0000012C may also show “EXFAT_FILE_SYSTEM” on the same blue screen. |
| 0x00000133 | DPC_WATCHDOG_VIOLATION | |
| 0x00000138 | GPIO_CONTROLLER_DRIVER_ERROR | |
| 0x00000139 | KERNEL_SECURITY_CHECK_FAILURE | |
| 0x00000144 | BUGCODE_USB3_DRIVER | |
| 0x0000014B | SOC_SUBSYSTEM_FAILURE | |
| 0x1000007E | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M | This BSOD means that a system thread generated an exception which the error handler did not catch. BSOD error code 0x1000007E may also show “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M” on the same blue screen. |
| 0x1000007F | UNEXPECTED_KERNEL_MODE_TRAP_M | This BSOD means that a trap was generated by the Intel CPU and the kernel failed to catch this trap. BSOD error code 0x1000007F may also show “UNEXPECTED_KERNEL_MODE_TRAP_M” on the same blue screen. |
| 0x1000008E | KERNEL_MODE_EXCEPTION_NOT_HANDLED_M | This BSOD means that a kernel-mode program generated an exception which the error handler did not catch. BSOD error code 0x1000008E may also show “KERNEL_MODE_EXCEPTION_NOT_HANDLED_M” on the same blue screen. |
| 0x100000EA | THREAD_STUCK_IN_DEVICE_DRIVER_M | This BSOD means that a thread in a device driver is endlessly spinning. BSOD error code 0x100000EA may also show “THREAD_STUCK_IN_DEVICE_DRIVER_M” on the same blue screen. |
| 0xC0000218 | STATUS_CANNOT_LOAD_REGISTRY_FILE | This BSOD means that a registry file could not be loaded. BSOD error code 0xC0000218 may also show “STATUS_CANNOT_LOAD_REGISTRY_FILE” on the same blue screen. |
| 0xC000021A | STATUS_SYSTEM_PROCESS_TERMINATED | This BSOD means that an error has occurred in a crucial user-mode subsystem. BSOD error code 0xC000021A may also show “STATUS_SYSTEM_PROCESS_TERMINATED” on the same blue screen. |
| 0xC0000221 | STATUS_IMAGE_CHECKSUM_MISMATCH | This BSOD means that a driver or a system DLL has been corrupted. BSOD error code 0xC0000221 may also show “STATUS_IMAGE_CHECKSUM_MISMATCH” on the same blue screen. |
| 0xDEADDEAD | MANUALLY_INITIATED_CRASH1 | This BSOD means that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard. BSOD error code 0xDEADDEAD may also show “MANUALLY_INITIATED_CRASH1” on the same blue screen. (Yes, this means a self-inflicted BSOD!) |
Source: www.lifewire.com, fixbit.com