Windows stop codes list

STOP Code
Cause of the Blue Screen

0x00000001
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.

0x00000002
This BSOD is uncommon. BSOD error code 0x00000002 may also show «DEVICE_QUEUE_NOT_BUSY» on the same blue screen.

0x00000003
This BSOD is uncommon. BSOD error code 0x00000003 may also show «INVALID_AFFINITY_SET» on the same blue screen.

0x00000004
This BSOD is uncommon. BSOD error code 0x00000004 may also show «INVALID_DATA_ACCESS_TRAP» on the same blue screen.

0x00000005
This BSOD is uncommon. BSOD error code 0x00000005 may also show «INVALID_PROCESS_ATTACH_ATTEMPT» on the same blue screen.

0x00000006
This BSOD is uncommon. BSOD error code 0x00000006 may also show «INVALID_PROCESS_DETACH_ATTEMPT» on the same blue screen.

0x00000007
This BSOD is uncommon. BSOD error code 0x00000007 may also show «INVALID_SOFTWARE_INTERRUPT» on the same blue screen.

0x00000008
This BSOD is uncommon. BSOD error code 0x00000008 may also show «IRQL_NOT_DISPATCH_LEVEL» on the same blue screen.

0x00000009
This BSOD is uncommon. BSOD error code 0x00000009 may also show «IRQL_NOT_GREATER_OR_EQUAL» on the same blue screen.

0x0000000A
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.

0x0000000B
This BSOD is uncommon. BSOD error code 0x0000000B may also show «NO_EXCEPTION_HANDLING_SUPPORT» on the same blue screen.

0x0000000C
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.

0x0000000D
This BSOD is uncommon. BSOD error code 0x0000000D may also show «MUTEX_LEVEL_NUMBER_VIOLATION» on the same blue screen.

0x0000000E
This BSOD is uncommon. BSOD error code 0x0000000E may also show «NO_USER_MODE_CONTEXT» on the same blue screen.

0x0000000F
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.

0x00000010
This BSOD is uncommon. BSOD error code 0x00000010 may also show «SPIN_LOCK_NOT_OWNED» on the same blue screen.

0x00000011
This BSOD is uncommon. BSOD error code 0x00000011 may also show «THREAD_NOT_MUTEX_OWNER» on the same blue screen.

0x00000012
This BSOD means that an unknown exception has occurred. BSOD error code 0x00000012 may also show «TRAP_CAUSE_UNKNOWN» on the same blue screen.

0x00000013
This BSOD is uncommon. BSOD error code 0x00000013 may also show «EMPTY_THREAD_REAPER_LIST» on the same blue screen.

0x00000014
This BSOD is uncommon. BSOD error code 0x00000014 may also show «CREATE_DELETE_LOCK_NOT_LOCKED» on the same blue screen.

0x00000015
This BSOD is uncommon. BSOD error code 0x00000015 may also show «LAST_CHANCE_CALLED_FROM_KMODE» on the same blue screen.

0x00000016
This BSOD is uncommon. BSOD error code 0x00000016 may also show «CID_HANDLE_CREATION» on the same blue screen.

0x00000017
This BSOD is uncommon. BSOD error code 0x00000017 may also show «CID_HANDLE_DELETION» on the same blue screen.

0x00000018
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.

0x00000019
This BSOD means that a pool header is corrupt. BSOD error code 0x00000019 may also show «BAD_POOL_HEADER» on the same blue screen.

0x0000001A
This BSOD means that a severe memory management error occurred. BSOD error code 0x0000001A may also show «MEMORY_MANAGEMENT» on the same blue screen.

0x0000001B
This BSOD is uncommon. BSOD error code 0x0000001B may also show «PFN_SHARE_COUNT» on the same blue screen.

0x0000001C
This BSOD is uncommon. BSOD error code 0x0000001C may also show «PFN_REFERENCE_COUNT» on the same blue screen.

0x0000001D
This BSOD is uncommon. BSOD error code 0x0000001D may also show «NO_SPIN_LOCK_AVAILABLE» on the same blue screen.

0x0000001E
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.

0x0000001F
This BSOD is uncommon. BSOD error code 0x0000001F may also show «SHARED_RESOURCE_CONV_ERROR» on the same blue screen.

0x00000020
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.

0x00000021
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.

0x00000022
This BSOD is uncommon. BSOD error code 0x00000022 may also show «FILE_SYSTEM» on the same blue screen.

0x00000023
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.

0x00000024
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.

0x00000025
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.

0x00000026
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.

0x00000027
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.

0x00000028
This BSOD is uncommon. BSOD error code 0x00000028 may also show «CORRUPT_ACCESS_TOKEN» on the same blue screen.

0x00000029
This BSOD is uncommon. BSOD error code 0x00000029 may also show «SECURITY_SYSTEM» on the same blue screen.

0x0000002A
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.

0x0000002B
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.

0x0000002C
This BSOD is uncommon. BSOD error code 0x0000002C may also show «PORT_DRIVER_INTERNAL» on the same blue screen.

0x0000002D
This BSOD is uncommon. BSOD error code 0x0000002D may also show «SCSI_DISK_DRIVER_INTERNAL» on the same blue screen.

0x0000002E
This BSOD means that a parity error in system memory has been detected. BSOD error code 0x0000002E may also show «DATA_BUS_ERROR» on the same blue screen.

0x0000002F
This BSOD is uncommon. BSOD error code 0x0000002F may also show «INSTRUCTION_BUS_ERROR» on the same blue screen.

0x00000030
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.

0x00000031
This BSOD means that system initialization failed. BSOD error code 0x00000031 may also show «PHASE0_INITIALIZATION_FAILED» on the same blue screen.

0x00000032
This BSOD means that system initialization failed. BSOD error code 0x00000032 may also show «PHASE1_INITIALIZATION_FAILED» on the same blue screen.

0x00000033
This BSOD is uncommon. BSOD error code 0x00000033 may also show «UNEXPECTED_INITIALIZATION_CALL» on the same blue screen.

0x00000034
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.

0x00000035
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.

0x00000036
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.

0x00000037
This BSOD is uncommon. BSOD error code 0x00000037 may also show «FLOPPY_INTERNAL_ERROR» on the same blue screen.

0x00000038
This BSOD is uncommon. BSOD error code 0x00000038 may also show «SERIAL_DRIVER_INTERNAL» on the same blue screen.

0x00000039
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.

0x0000003A
This BSOD is uncommon. BSOD error code 0x0000003A may also show «SYSTEM_UNWIND_PREVIOUS_USER» on the same blue screen.

0x0000003B
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.

0x0000003C
This BSOD is uncommon. BSOD error code 0x0000003C may also show «INTERRUPT_UNWIND_ATTEMPTED» on the same blue screen.

0x0000003D
This BSOD is uncommon. BSOD error code 0x0000003D may also show «INTERRUPT_EXCEPTION_NOT_HANDLED» on the same blue screen.

0x0000003E
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.

0x0000003F
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.

0x00000040
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.

0x00000041
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.

0x00000042
This BSOD is uncommon. BSOD error code 0x00000042 may also show «ATDISK_DRIVER_INTERNAL» on the same blue screen.

0x00000043
This BSOD is uncommon. BSOD error code 0x00000043 may also show «NO_SUCH_PARTITION» on the same blue screen.

0x00000044
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.

0x00000045
This BSOD is uncommon. BSOD error code 0x00000045 may also show «INSUFFICIENT_SYSTEM_MAP_REGS» on the same blue screen.

0x00000046
This BSOD is uncommon. BSOD error code 0x00000046 may also show «DEREF_UNKNOWN_LOGON_SESSION» on the same blue screen.

0x00000047
This BSOD is uncommon. BSOD error code 0x00000047 may also show «REF_UNKNOWN_LOGON_SESSION» on the same blue screen.

0x00000048
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.

0x00000049
This BSOD is uncommon. BSOD error code 0x00000049 may also show «PAGE_FAULT_WITH_INTERRUPTS_OFF» on the same blue screen.

0x0000004A
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.

0x0000004B
This BSOD is uncommon. BSOD error code 0x0000004B may also show «STREAMS_INTERNAL_ERROR» on the same blue screen.

0x0000004C
This BSOD is uncommon. BSOD error code 0x0000004C may also show «FATAL_UNHANDLED_HARD_ERROR» on the same blue screen.

0x0000004D
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.

0x0000004E
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.

0x0000004F
This BSOD is uncommon. BSOD error code 0x0000004F may also show «NDIS_INTERNAL_ERROR» on the same blue screen.

0x00000050
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
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
This BSOD is uncommon. BSOD error code 0x00000052 may also show «MAILSLOT_FILE_SYSTEM» on the same blue screen.

0x00000053
This BSOD is uncommon. BSOD error code 0x00000053 may also show «NO_BOOT_DEVICE» on the same blue screen.

0x00000054
This BSOD is uncommon. BSOD error code 0x00000054 may also show «LM_SERVER_INTERNAL_ERROR» on the same blue screen.

0x00000055
This BSOD is uncommon. BSOD error code 0x00000055 may also show «DATA_COHERENCY_EXCEPTION» on the same blue screen.

0x00000056
This BSOD is uncommon. BSOD error code 0x00000056 may also show «INSTRUCTION_COHERENCY_EXCEPTION» on the same blue screen.

0x00000057
This BSOD is uncommon. BSOD error code 0x00000057 may also show «XNS_INTERNAL_ERROR» on the same blue screen.

0x00000058
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
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
This BSOD is uncommon. BSOD error code 0x0000005A may also show «CRITICAL_SERVICE_FAILED» on the same blue screen.

0x0000005B
This BSOD is uncommon. BSOD error code 0x0000005B may also show «SET_ENV_VAR_FAILED» on the same blue screen.

0x0000005C
This BSOD is uncommon. BSOD error code 0x0000005C may also show «HAL_INITIALIZATION_FAILED» on the same blue screen.

0x0000005D
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
This BSOD is uncommon. BSOD error code 0x0000005E may also show «OBJECT_INITIALIZATION_FAILED» on the same blue screen.

0x0000005F
This BSOD is uncommon. BSOD error code 0x0000005F may also show «SECURITY_INITIALIZATION_FAILED» on the same blue screen.

0x00000060
This BSOD is uncommon. BSOD error code 0x00000060 may also show «PROCESS_INITIALIZATION_FAILED» on the same blue screen.

0x00000061
This BSOD is uncommon. BSOD error code 0x00000061 may also show «HAL1_INITIALIZATION_FAILED» on the same blue screen.

0x00000062
This BSOD is uncommon. BSOD error code 0x00000062 may also show «OBJECT1_INITIALIZATION_FAILED» on the same blue screen.

0x00000063
This BSOD is uncommon. BSOD error code 0x00000063 may also show «SECURITY1_INITIALIZATION_FAILED» on the same blue screen.

0x00000064
This BSOD is uncommon. BSOD error code 0x00000064 may also show «SYMBOLIC_INITIALIZATION_FAILED» on the same blue screen.

0x00000065
This BSOD is uncommon. BSOD error code 0x00000065 may also show «MEMORY1_INITIALIZATION_FAILED» on the same blue screen.

0x00000066
This BSOD is uncommon. BSOD error code 0x00000066 may also show «CACHE_INITIALIZATION_FAILED» on the same blue screen.

0x00000067
This BSOD means that the registry configuration failed. BSOD error code 0x00000067 may also show «CONFIG_INITIALIZATION_FAILED» on the same blue screen.

0x00000068
This BSOD is uncommon. BSOD error code 0x00000068 may also show «FILE_INITIALIZATION_FAILED» on the same blue screen.

0x00000069
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
This BSOD is uncommon. BSOD error code 0x0000006A may also show «LPC_INITIALIZATION_FAILED» on the same blue screen.

0x0000006B
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
This BSOD is uncommon. BSOD error code 0x0000006C may also show «REFMON_INITIALIZATION_FAILED» on the same blue screen.

0x0000006D
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
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
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
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
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
This BSOD is uncommon. BSOD error code 0x00000072 may also show «ASSIGN_DRIVE_LETTERS_FAILED» on the same blue screen.

0x00000073
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
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
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
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
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
This BSOD is uncommon. BSOD error code 0x00000078 may also show «PHASE0_EXCEPTION» on the same blue screen.

0x00000079
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
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
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
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
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
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
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
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
This BSOD is uncommon. BSOD error code 0x00000081 may also show «SPIN_LOCK_INIT_FAILURE» on the same blue screen.

0x00000082
This BSOD is uncommon. BSOD error code 0x00000082 may also show «DFS_FILE_SYSTEM» on the same blue screen.

0x00000085
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
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
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
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
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.

0x00000092
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
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
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.

0x00000096
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
This BSOD is uncommon. BSOD error code 0x00000097 may also show «BOUND_IMAGE_UNSUPPORTED» on the same blue screen.

0x00000098
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
This BSOD is uncommon. BSOD error code 0x000000B9 may also show «CHIPSET_DETECTED_ERROR» on the same blue screen.

0x000000BA
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
This BSOD is uncommon. BSOD error code 0x0000010A may also show «APP_TAGGING_INITIALIZATION_FAILED» on the same blue screen.

0x0000010C
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
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
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
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
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
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
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
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
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
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
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
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
This BSOD is uncommon. BSOD error code 0x0000011A may also show «EM_INITIALIZATION_FAILURE» on the same blue screen.

0x0000011B
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
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
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
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
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
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
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
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
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.

0x1000007E
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
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
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
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
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
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
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.

0xC0000225
This BSOD means that Windows is unable to find the correct system files to initiate booting. BSOD error code 0xC0000225 may also show another message on the same blue screen, like «Boot selection failed because a required device is inaccessible.» or «A required device isn’t connected or can’t be accessed.»

0xDEADDEAD
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!)

What does a stop code look like? What are common Windows stop code errors? How to find and fix Windows stopcode on your Windows 11/10/8/7 PC? In this post, MiniTool shows you the detailed answers to these questions and let’s continue reading.

What Is Windows Stopcode

Sometimes your PC suddenly crashes and the safest thing the PC can do is to stop everything and then restart.  When this occurs, you can see a blue screen error and stop code on the computer screen. The Windows stopcode error contains some handy information.

What does a stop code look like? A Windows stop code, also called a bug check or bug check code, is a unique number that identifies a specific stop error (Blue Screen of Death – BSOD). The Windows stopcode is displayed in the hexadecimal format that starts with 0x, followed by an eight-character string.

Windows stopcode can also be written in a shorthand form, for example, 0xc000021a – called 0x21a. You see all the zeros after the x are removed.

All the Windows 11/10 stop codes are different from each other and every one refers to a unique Windows error that instructs you on how to assist in fixing the malfunction. Most stop codes are related to device drivers, RAM, and other hardware or software issues.

Common Windows Stop Code Errors

As mentioned above, each Windows stopcode indicates a stop error. In Windows, there are many stop codes and let’s see some common ones.

Windows Stopcode Stop Error Explanation
0x0000001A MEMORY_MANAGEMENT a severe error with system memory management
0x0000003B SYSTEM_SERVICE_EXCEPTION an exception happened while executing a routine that transitions from non-privileged code to privileged code
0x000000EF CRITICAL_PROCESS_DIED a critical system process died
0x000000ED UNMOUNTABLE_BOOT_VOLUME the I/O subsystem attempted to mount the boot volume and failed
0x0000012B FAULTY_HARDWARE_CORRUPTED_PAGE a hardware memory error
0x0000007B INACCESSIBLE_BOOT_DEVICE OS fails to access the system partition during startup
0x00000074 BAD_SYSTEM_CONFIG_INFO an error in the registry
0x00000019 BAD_POOL_HEADER a pool header is corrupt
0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH a driver or a system DLL has been corrupted
0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED it happens when a critical process (winlogon.exe or csrss.exe) fails
0x0000009A SYSTEM_LICENSE_VIOLATION the software license agreement has been violated

This table only lists some common Windows stopcode errors and if you want to know a complete list, see this guide from Lifewire – List of Blue Screen Error Codes (from stop 0x1 to STOP 0xC0000225). If you are using a Windows 10/11 PC, you can refer to our related post – Your PC Ran into a Problem and Needs to Restart to find some common stop errors.

How to Find Windows Stopcode

When your PC crashes, a Windows stop code may appear on the blue screen. Sometimes you cannot notice the error message and the Windows stopcode. So how to find the code once your computer reboots? One of the easiest ways is to use BlueScreenView that is from NirSoft.

It can scan your desktop or laptop for the minidump files created during blue screen of death crashes and show all the information regarding crashes in a table. Besides, you can view details of the device drivers loaded during the crash and easily find the problematic driver that could lead to a breakdown.

See how to find Windows stopcode in Windows 11/10/8/7:

Step 1: Visit the official website of BlueScreenView and download this software. Then, use the installer to install this tool on your PC.

Step 2: Launch BlueScreenView and check the listed Windows stopcode errors. You can sort through the errors so as to find the most recent BSOD.

BlueScreenView Windows 10

In addition, you can check Windows stopcode via Windows Event Viewer.

Step 1: Type event viewer to the search box and right-click on it to select Run as administrator.

Step 2: Go to Windows Logs > System to see system-related logs.

Step 3: Click Filter Current Log and check the box of Critical & Error. Then, click OK.

check Windows stopcode via Event Viewer

Step 4: Find the item that shows BugCheck in the Source tab and then check the General and Details section to find the Windows stopcode.

How to Fix Windows Stopcode Errors Windows 11/10/8/7

After knowing so much information about Windows stop codes, if you suffer from a blue screen error along with a stop code, how can you fix it?

Sometimes the blue screen also shows you a message to ask you to contact www.windows.com/stopcode. This link brings you to a page on resolving blue screen errors in Windows. For a specific stop error, the fixes are a bit different but some common basic troubleshooting tips can help a lot. Now, let’s go to see some you can try.

Back up Your Important Files (Suggestion)

Sometimes blue screen errors keep appearing randomly and may bring severe results – your files lose after a stop error. So, if you meet a frustrated Windows stopcode in Windows 11/10/8/7, we strongly suggest that you should create a backup for your important files at once.

To do this thing, running a piece of professional backup software is a good choice. In Windows, the inbuilt utility – Backup and Restore can help a lot in data backup. But it has a limitation – it doesn’t allow us to select individual files to back up but choose folders. Besides, this tool is not flexible and you often suffer from a failed backup.

To back up your files well, using the third-party PC backup software like MiniTool ShadowMaker is a good choice. This tool supports file backup, disk backup, partition backup and system backup. To automatically back up your data, you can configure a schedule plan. Also, you can make incremental backups and differential backups with this tool.

Importantly, MiniTool ShadowMaker allows you to create a bootable USB drive so that you can back up your computer in case of system crashes. Now, get its trial edition via the following button and then start a data backup in case of Windows stopcode.

MiniTool ShadowMaker TrialClick to Download100%Clean & Safe

Step 1: Connect an external drive to your PC and run MiniTool ShadowMaker Trial Edition to enter its main interface.

Step 2: Tap on Backup > SOURCE > Folders and Files, then open your computer to find and select the items you need to back up and click OK.

Step 3: Choose an external drive to save the backup image.

Step 4: Tap on Back Up Now to execute the file backup.

back up data with MiniTool ShadowMaker

Tips:

If your PC fails to boot to the desktop after a Windows stopcode error appears, you can run MiniTool ShadowMaker Bootable Edition to perform a file backup. See this related post — How to Back up Data without Booting Windows? Easy Ways Are Here to see what you should do.

Next, start Windows stopcode fixes. Note that the following fixes are done in the Windows desktop version. If your machine fails to boot, you can perform these troubleshooting tips in Safe Mode. Don’t know how to enter this mode? Follow the guide – How to Start/Boot Windows 11 in Safe Mode? (7 Ways) and choose a proper way.

Restart Your Computer

Restarting your laptop or desktop is the easiest and simplest thing that you can try to solve a Windows stop error. Sometimes a reboot can do the trick. Just press and hold the power button for 10 seconds to turn off the PC.

Then, disconnect all the external devices including external hard disks, USB flash drives, printers, webcams, and SD cards.  If you are using a laptop, disconnect the AC adapter or power cable and remove the battery. Wait a while, put the battery back and power on the machine, then connect your devices to the PC and see if BSOD errors happen.

If this way is ineffective, try other ways to address stop codes in Windows 11/10/8/7.

Run SFC & DISM and CHKDSK

In many cases, the Windows stopcode error may be caused by corrupted system files, some file system errors and hard disk errors. You can try to fix the corruption or these errors by using the Windows system utilities – SFC, DISM and CHKDSK.

SFC, short for System File Checker, helps to scan the entire operating system for the system files. If it detects corrupted files in the system, it can replace the corruption.  How to run an SFC scan for fixing broken system files? See the steps.

Step 1: Press Win + R, type cmd into the textbox and press Ctrl + Shift + Enter to run Command Prompt with admin rights. If prompted by the UAC window, click Yes.

Step 2: Type sfc /scannow and press Enter. Then, this tool starts the scan process.

Tips:

Sometimes the SFC tool gets stuck during the scan. To find solutions, you can refer to our previous post — Windows 10 SFC /Scannow Stuck at 4/5/30/40/73, etc.? Try 7 Ways.

Usually, we also run a DISM scan using the Deployment Image Servicing and Management tool to fix Windows bad images in addition to SFC. In the CMD window, run the command – DISM /Online /Cleanup-Image /RestoreHealth.

DISM scan

Next, run the CHKDSK scan to check and repair file system errors and hard drive errors that may lead to a stop code in Windows 11/10/8/7. In the CMD window with admin rights, run the command – chkdsk x: /f /r. Replace x with the letter of your drive.

Update Windows

When Windows stopcode errors happen on your PC, you can try to update the operating system. This is because Windows updates may include bug fixes and patches for some known issues besides security updates. If you are using Windows 10/11 PC, follow these instructions to keep Windows up-to-date.

In Windows 10, go to Settings > Update & Security > Windows Update, and then check for available updates. If some are found, download and install them. In Windows 11, go to Settings > Windows Update to update Windows to the latest version.

Uninstall Incompatible Updates, Apps or Drivers

Sometimes a recently-installed Windows update, app or driver can cause a Windows stopcode error on the blue screen. To fix BSOD in Windows 11/10, go to uninstall them.

To uninstall an update in Windows 10, go to Settings > Update & Security > Windows Update > View update history > Uninstall updates. In Windows 11, go to Settings > Windows Update > Update history > Uninstall updates. Next, choose the recent update and click Uninstall.

uninstall Windows 10 updates

To uninstall a driver or app, go to Control Panel > Uninstall a program under Programs (viewed by Category), choose the target item and click Uninstall.

Perform a System Restore

If you have a restore point created before Windows stopcode errors happen, you can use that point to bring the Windows system to a previous good state. System Restore is a good option to undo some changes to revert your PC to an earlier state.

Step 1: Type create a restore point into the search box and open the System Properties window.

Step 2: Tap on System Restore.

Step 3: After choosing a restore point based on the created time, click Next > Finish.

system restore

These are the common Windows 11/10 stopcode fixes that you can try. In addition to these workarounds, you can try some other ways. And you should search for the specific stop code error online and find out the detailed solutions.

Final Words

That’s all the basic information about Windows stopcode including what it looks like, some common Windows stop codes, how to find and fix Windows stop errors on your PC. Blue screen of death is a royal pain for many users over the decades. Hopefully, this guide here can help you better understand the blue screen errors.

Table of contents

  • What Is a Windows Blue Screen of Death?
  • What Causes the Blue Screen of Death?
  • Different Microsoft Stop Codes and What They Mean
  • How to Check Causes of Windows BSOD
    • Method 1: Using the Event Viewer to check stop codes
    • Method 2: Using the Reliability Monitor to identify issues
    • Method 3: Analyzing dump files
  • How to Fix BSOD Stop Code Errors on Windows 11/10
    • Fix 1: Restart your computer
    • Fix 2: Disconnect unnecessary devices
    • Fix 3: Boot in Safe Mode
    • Fix 4: Update Windows
    • Fix 5: Scan for malware
    • Fix 6: Uninstall any updates, apps, or drivers that are incompatible or recently installed
    • Fix 7: Check your computer’s RAM using the Windows Memory Diagnostic tool
    • Fix 8: Run SFC, DISM, and CHKDSK utilities
    • Fix 9: Perform a system restore
    • Fix 10: Reinstall Windows as a last resort
  • Windows Stop Codes: Explained
  • FAQ

This guide walks you through the various stop codes, what they mean, and their causes.

You have probably heard recent news stories about the thousands of Windows PCs booting up with a blue screen of death , disrupting the operation of supermarkets, banks, airlines, and many other businesses worldwide. Even though it wasn’t Microsoft’s fault, it shows how problematic BSODs can be. 

Data loss, system instability, and serious work disruption are some of the issues that can result from BSODs. Fortunately, BSOD errors usually come with a W indows stop co de, which can help you identify the problem and resolve it before it gets worse. 

I’ll walk you through everything important you need to know about stop codes and how to use them to resolve various BSODs issues. 

Let’s begin.

What Is a Windows Blue Screen of Death?

BSODs (blue screen of death), or STOP codes, alert users about critical system failures that force Windows to crash. They appear on blue backgrounds (hence the name) and typically do not linger for long before the system restarts.
Every Windows blue screen may look similar, but each error displays a message with the name of the affected file and a code (called a bug check value) to explain the cause of the problem. The operating system saves a dump (.dmp) file with more details about the crash on your system before rebooting.
Earlier BSOD errors threw a lot of vague information and code at users, which left most of us even more confused. But since Windows 8, Microsoft has scaled back the texts and tried to make the screen less scary and more helpful.
Stop code interfaces now contain QR codes, stop code descriptions that you can look up on Microsoft’s website, and sad smiley faces.

The code usually starts with “0x” followed by eight characters, like “0xc000021a.” Sometimes, these codes may come in a shorter way by removing the zeros, so “0xc000021a” becomes “0x21a.”
Regardless of how the code appears, each Windows stop code has its own special meaning and points to a specific problem with your computer.

What Causes the Blue Screen of Death?

I mentioned that Windows saves a dump file before rebooting. Reading and interpreting these .dmp files can help explain the causes of the BSOD error. Going through the Windows Event Viewer is another way to find the specific cause of the problem.

Still, the following underlying issues should come to mind whenever Windows displays a blue screen:

  • Device driver issues

Device drivers act as go-betweens for Windows and your hardware. BSODs show up when these drivers are out-of-date, corrupt, or missing.  

  • Faulty hardware

Some stop codes advise you to check recently installed hardware devices because blue screens of death on Windows 10 and Windows 11 are generally connected to hardware issues. A recently installed device or an older component might be malfunctioning and triggering the error. They include your RAM, hard drive, and peripherals.

  • Missing and damaged system files

System files control critical Windows processes, from boot operations to shutdowns. If any of these files are missing or corrupt, Windows will experience a fatal failure that will cause the blue screen error.

  • Malware

Malicious programs can corrupt or delete system files and drivers to trigger BSOD errors.

  • Overheating

Windows usually displays blue screens and shuts down when system temperature reaches dangerous levels. I got used to blue screens when I put my gaming laptop under load and it generated too much heat. The solution was employing effective cooling measures. Your overheating issue could be due to a poor cooling system, your computer activity, or unsafe overclocking .


📌Further reading: Ultimate Guide: How to Stop a Laptop from Overheating


Different Microsoft Stop Codes and What They Mean

The first step to fixing a blue screen of death issue is to understand the stop code you are seeing and the potential cause of the error. Different stop codes warn you about different things and have different severity levels. The following is a list of some of the Windows stop codes and what they mean:

Windows stop code Stop code error Explanation Causes
0x0000001A MEMORY_MANAGEMENT A severe error with system memory management Faulty RAM, corrupted system files, or outdated drivers
0x000000D1 DRIVER_IRQL_NOT_LESS_OR_EQUAL A driver attempted to access an invalid memory address Faulty drivers, incompatible hardware, or antivirus conflicts
0xC0000005 ACCESS_VIOLATION The system encountered an access violation, typically due to memory issues Faulty RAM, corrupted drivers, incompatible software, or malware infection
0x0000003B SYSTEM_SERVICE_EXCEPTION An exception occurred while executing a privileged code routine Outdated drivers, corrupted system files, or incompatible software
0x00000023 FAT_FILE_SYSTEM Indicates an issue with the FAT file system used by the storage device Corrupted or damaged hard drive, or failure to load virtual memory
0x000000EF CRITICAL_PROCESS_DIED A critical system process terminated unexpectedly Corrupted system files, malware, or hardware failure
0x00000051 REGISTRY_ERROR Indicates a severe issue with the Windows registry Corrupted registry files, faulty hardware, or insufficient system resources
0x0000002E DATA_BUS_ERROR A parity error occurred in system memory Faulty hardware, especially RAM, or hardware conflict issues
0x000000ED UNMOUNTABLE_BOOT_VOLUME The system failed to mount the boot volume Damaged hard drive, corrupted boot files, or incorrect BIOS settings
0x00000119 VIDEO_SCHEDULER_INTERNAL_ERROR A video scheduler detected a fatal error in the graphics processing Outdated or corrupted graphics drivers, faulty graphics card, or hardware acceleration issues
0x00000139 KERNEL_SECURITY_CHECK_FAILURE A Windows stop code error that indicates a failure in the kernel security check Corrupted system files, incompatible drivers, or memory issues
0x0000012B FAULTY_HARDWARE_CORRUPTED_PAGE A hardware memory error detected Faulty RAM or hardware-related issues
Windows stop code Stop code error Explanation Causes
0x0000007B INACCESSIBLE_BOOT_DEVICE OS cannot access the system partition during startup Missing or corrupted boot files, incorrect BIOS settings, or hard drive failure
0x00000074 BAD_SYSTEM_CONFIG_INFO An error in the system registry Corrupted registry, incompatible hardware, or failed Windows updates
0x00000050 PAGE_FAULT_IN_NONPAGED_AREA The system attempted to access a non-existent or restricted memory area Faulty RAM, corrupted system files, or incompatible software or drivers
0x00000019 BAD_POOL_HEADER A memory pool header is corrupt Faulty drivers, malware, or corrupted system files
0x0000009C MACHINE_CHECK_EXCEPTION (MCE) Indicates a hardware error detected by the processor Overheating, hardware failure (such as CPU, RAM, or motherboard), or power supply issues
0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH A driver or system DLL has a mismatched checksum Corrupted system files or faulty hardware
0x0000007A KERNEL_DATA_INPAGE_ERROR The system couldn’t read data from the paging file into memory Faulty hard drive, corrupted memory, or loose/damaged drive connection
0xC000021A STATUS_SYSTEM_PROCESS_TERMINATED A critical process (like winlogon.exe or csrss.exe) failed Corrupted system files or third-party software conflicts
0x00000133 DPC_WATCHDOG_VIOLATION The system detected a prolonged Deferred Procedure Call (DPC) Outdated drivers, storage issues, or device firmware problems
0x0000009A SYSTEM_LICENSE_VIOLATION The software license agreement was violated Software license issues or OS-related restrictions
0x8007025D INSTALLATION_ERROR A Windowsstop error code indicating that the installation process encountered an issue Corrupted installation files, USB issues, or hardware incompatibility
0x80070091 SYSTEM_RESTORE_ERROR A Windowsstop code error indicating that System Restore encountered an issue while attempting to restore your system to a previous state Corrupted file system, antivirus conflicts, or disk space issues
0x80000003 BREAKPOINT_REACHED A breakpoint was reached during debugging Software debugging pause or outdated drivers

How to Check Causes of Windows BSOD

Method Ease of use When to use What it helps you see
Event Viewer Medium Use when you need detailed logs of system errors and stop codes Provides precise error codes and detailed event logs for troubleshooting
Reliability Monitor Easy Best for users looking for a user-friendly summary of recent system issues Shows an overview of system stability, crashes, and failures
Dump file analysis Complex Use this for deep analysis and understanding complex errors Reveals in-depth crash data, including driver or memory-related issues

Method 1: Using the Event Viewer to check stop codes

While Wi ndows stop code s can be helpful, they often don’t provide a complete picture. To truly understand the causes of the BSOD, you need to dig a bit deeper. This is where the Event Viewer comes in. 

It’s a built-in log viewer that records everything under your system’s hood. Event Viewer is your first stop when deciphering what causes the BSOD. Follow these steps to check stop codes: 

  • Press the Windows key to open the Start menu, type  “Event Viewer,”  and select it.

Search for Event Viewer and select it

  • In the Event Viewer, look at the left panel and click  Windows Logs  category.

Click Windows Logs

  • Under  Windows Logs , click on  System.  System logs carry detailed records of your system’s operations, including Microsoft stop code occurrences.

Under  <i>Windows Logs </i>, click on  <i>System </i>» src=»https://www.auslogics.com/en/articles/wp-content/uploads/2024/11/Screenshot-2024-11-12-163427.png»></p>
<div class= Картинка с сайта: www.auslogics.com

  • In the top right, find Filter Current Log.

Find Filter Current Log

  • In the dialogue box, check the boxes with the tags  Critical and Error . Then, click  OK .

Check the boxes with the tags  <i>Critical  </i>and <i> Error </i>» src=»https://www.auslogics.com/en/articles/wp-content/uploads/2024/11/Screenshot-2024-11-12-170538.png»></p>
<div class= Картинка с сайта: www.auslogics.com

  • Look through the items on your screen and observe if there are any items labeled BugCheck  in the  Source  tab. Any item like this is the error you are looking for. Click on it to see the stop error code.

In Event Viewer, look for items labeled  <i>BugCheck </i> in the  <i>Source </i> tab » src=»https://www.auslogics.com/en/articles/wp-content/uploads/2024/11/Screenshot-2024-11-12-171014.png»></p>
<div class= Картинка с сайта: www.auslogics.com

Method 2: Using the Reliability Monitor to identify issues

The Reliability Monitor provides a clear view of your system’s stability, making it easier to troubleshoot issues that may lead to a BSOD. It logs critical events, including memory, hard disk, application, and operating system failures, which are common causes of BSOD errors.

Additionally, it tracks significant system changes, like new software installations or updates, that could impact stability. This can help you identify patterns or recent changes that may be linked to the BSOD error and take specific actions to correct it.

Compared with the Event Viewer, the Reliability Monitor is more user-friendly, providing a clear visual timeline of system stability. The Event Viewer typically gives you a more detailed, technical view of the problem, and this can be overwhelming due to the sheer volume of entries.

How to access the Reliability Monitor

  • Type “Reliability Monitor” into the search bar in your Start menu.

View reliability history

  • Once you click the application, you will see a graph showing the stability index of your system over time.

Review your computer's reliability and problem history

  • On the horizontal axis, you have dates. On the vertical axis, you will see numbers 1, 5, and 10. Those numbers indicate how stable your computer was on the dates displayed. Usually, the higher the number, the better. For the computer above, we can tell its most stable day was on the 11th of November. 
  • For a more detailed view, you can change from days to weeks. This gives you more details from previous weeks instead of just the week in view.

Review your computer's reliability and problem history> View by Days/Weeks» src=»https://www.auslogics.com/en/articles/wp-content/uploads/2024/11/Screenshot-2024-11-12-210845.png»></p>
<div class= Картинка с сайта: www.auslogics.com

Identifying critical events in the Reliability Monitor

Below the graph is a list of errors. Each error on the Reliability Monitor timeline has an icon that denotes its type. Here, you’re primarily looking for critical events or instances that have led to the BSOD.

These events provide key insights into what can cause a blue screen. Examining them closely can lead to identifying the Windows stop code responsible for your woes.

Method 3: Analyzing dump files

Even with tools like the Event Viewer and the Reliability Monitor, the causes of the error can sometimes remain elusive. This is where dump files come in. They can provide a deeper understanding of the Windows blue screen of death you’re facing.

Dump files are essentially snapshots of your system at the moment of the crash. They contain detailed information about your system’s actions when encountering the blue screen of death in Windows 10 and 11.

How to generate dump files

Before you analyze the dump files, you need to generate them first. Here’s how to do it: 

  • Go to Windows Explorer (Windows + E), right-click on  This PC , and select  Properties .

Go to This PC and select Properties

  • Click on  Advanced system settings .

Click Advanced system settings

  • Under  Startup and Recovery , click  Settings .
  • Ensure  Write an event to the system log  is checked in the new window. Choose the dump file type you want under  Write debugging information .
  • Click  OK  and then  Apply .

After a BSOD occurs, you can locate these dump files in the  C:\Windows\Minidump  folder.

Analyzing dump files using WinDbg

The simplest and easiest way to read the dump files is to use WinDbg. Microsoft developed this tool, so you have nothing to worry about. 

To use it, follow these steps:

  • Download the WinDbg tool from Microsoft’s website and install it.
  • Open WinDbg and click  File , then  Open Crash Dump.
  • Navigate to  C:\Windows\Minidump  and open the dump file.
  • Once the file is open, type  “!analyze -v”  in the command line at the bottom of the WinDbg window and press Enter.
  • Wait while WinDbg analyzes the file. It will then display the Windows stop code and other information about what caused the crash.

Navigating dump files might feel like a complicated task. However, these files contain the key to understanding the  Windows 11/10 stop codes  and the root of the Windows blue screens of death. With the information you gather, you’ll be better prepared to solve and prevent further BSOD occurrences.

Download Auslogics BoostSpeed

Your one-stop PC maintenance and optimization tool, this program will clean, speed up, repair and tweak your system to ensure maximum speed and efficiency.

How to Fix BSOD Stop Code Errors on Windows 11/10

Now that you found the Windows stop codes, what is the next thing to do? The answer to that will depend on the severity of the problem you are facing.

The following are general solutions that should work for most problems. Think of them as first-aid solutions. However, you should know that every stop code error has a unique solution, like you saw in the table above.

The blue screen of death error you are seeing is likely an indication that you are dealing with a big issue. If you are not careful, it might result in a total loss of your files. To avoid that, it’s better to back up your files before going any further.  

Backing up your files will not fix the blue screen error you are experiencing. However, it gives you enough time to save your documents before you lose any of your files.   

For a quick backup of essential files, you can simply connect an external drive and copy your files there.

Fix 1: Restart your computer

Even though the BSOD looks like a big issue, simple fixes like restarting your computer might solve the problem. A computer restart acts like a complete refresh button for your system, addressing various technical hiccups in one simple action. 

Simply press the power button of your computer for about 10 seconds until it shuts down. Once it is off, you can turn it on again and see if the problem is resolved.

You might want to disconnect all external devices from your computer before you do the restart. This will help you isolate whether the BSOD error is being caused by a faulty peripheral device or corrupted driver. Sometimes, these components can conflict with system operations and can introduce instability that triggers system crashes.

Fix 2: Disconnect unnecessary devices

If you started seeing the error after connecting a plug-and-play external device, consider walking your way back. Some peripheral components could cause critical conflicts that trigger the BSOD.

Disconnect your mouse, external webcam, and even external monitors one after the other and try running your computer each time.

Fix 3: Boot in Safe Mode

If your PC keeps blue screenin g whenever you try to start Windows, boot your system into Safe Mode to apply the fixes that follow. These steps will show you what to do:

Note

Booting into Safe Mode helps resolve BSOD issues by starting Windows with only essential drivers and services, preventing faulty software, drivers, or malware from interfering. If the system runs fine in Safe Mode, it indicates that a third-party app or driver is likely causing the BSOD.

In Safe Mode, you can apply the following fixes: uninstall problematic updates, remove conflicting software, update drivers, and run diagnostic tools like SFC and DISM to repair system files.

  • Press and hold your power button to shut down your system.
  • Turn on your computer, but once your PC manufacturer’s logo flashes and Windows starts to boot, press and hold the power button to force your system to shut down again. Repeat this step two to three times until the Preparing Automatic Repair message appears.

Repeat this step two to three times until the <i>Preparing Automatic Repair</i> message appears» src=»https://www.auslogics.com/en/articles/wp-content/uploads/2024/07/unnamed-127.png»></p>
<div class= Картинка с сайта: www.auslogics.com

Click the  <i>Advanced options </i> button when the <em>Automatic Repair</em> screen appears » src=»https://www.auslogics.com/en/articles/wp-content/uploads/2024/07/unnamed-128.png»></p>
<div class= Картинка с сайта: www.auslogics.com

<strong>Click  <i>Troubleshoot  </i>when you see the  <i>Choose an option </i> interface </strong>» src=»https://www.auslogics.com/en/articles/wp-content/uploads/2024/07/unnamed-129.png»></p>
<div class= Картинка с сайта: www.auslogics.com

Under  <i>Troubleshoot </i>, click  <i>Advanced options </i>, then click on  <i>Startup Settings </i>» src=»https://www.auslogics.com/en/articles/wp-content/uploads/2024/07/unnamed-130.png»></p>
<div class= Картинка с сайта: www.auslogics.com

Click the  <i>Restart  </i>button once you get to the next screen » src=»https://www.auslogics.com/en/articles/wp-content/uploads/2024/07/unnamed-131.png»></p>
<div class= Картинка с сайта: www.auslogics.com

Startup settings Safe Mode

Fix 4: Update Windows

If the problem was from a bad update from Windows, there is a huge possibility that Windows is already working to fix the issue. Therefore, updating your OS in such cases will likely fix the problem.

To do that, simply check for available Windows updates , and if there are any available, download and install them.

Fix 5: Scan for malware

Viruses and malware can also cause BSOD issues. Some of these malicious software can delete or corrupt critical system files, making it difficult for Windows to boot properly.

If you are dealing with malware, this is probably the beginning of many other problems. To be safe, consider scanning your PC with a trusted malware tool . Run a full scan of your computer and promptly delete any malware you find in the process.

Ensure your malware detection tool is up to date. If you search with an outdated tool, it might miss newer viruses, malware, or threats that could be causing your blue screen of death errors. This is important because cyber security threats evolve constantly as new malware variants are created daily.

Fix 6: Uninstall any updates, apps, or drivers that are incompatible or recently installed

BSOD errors may appear due to apps, drivers, or even Windows updates that may be incompatible. If you recently installed an app, a driver, or updated Windows before you saw the BSOD error, this might be the cause of the problem.

Try uninstalling these applications to see if that resolves the problem.

If it’s a Windows update that causes the error, roll it back with these steps:

  1. Press Win + I to open Settings. In Settings, go to Update & Security > Windows Update .
  2. Click View update history > Uninstall updates . Windows will take you to Control Panel.
  3. In the Control Panel window, select the most recent update (or the one causing the error) and click Uninstall .
  4. Follow the prompts to complete uninstallation and restart your PC.

Fix 7: Check your computer’s RAM using the Windows Memory Diagnostic tool

Issues with your computer’s RAM can lead to the BSOD. If that is the case, you can run the Windows Memory Diagnostic tool to identify and potentially fix the issue. 

Remember that the tool will run after your computer restarts and give you its results. The results are usually stored in the Event Viewer, just in case you need them again.

Fix 8: Run SFC, DISM, and CHKDSK utilities

When you see Windows stop code errors, you could be dealing with corrupted system files or disk errors. 

You can fix some of these issues by running Windows’ built-in system repair utilities like the SFC, DISM, and CHKDSK .

These powerful tools can scan for, detect, and repair corrupted files and disk errors that might be triggering these stop codes. 

To run these tools, open the Command Prompt with administrative privileges and execute the following commands: 

Enter the scannow command

DISM /Online /Cleanup-Image /RestoreHealth

Enter the chkdsk command

Run these commands one after the other and, if possible, back up your data before proceeding.

Fix 9: Perform a system restore

If the problem persists, restore Windows to a previous version when it was working well. The process only tries to fix Windows by restoring it to a saved restore point and may roll back your operating system settings and application files but will not affect your personal data. 

Remember that the restore point you want to use should be from a time when your PC was not showing the error. If you choose a restore point that was saved after you started experiencing the BSOD, you may be restoring the problem instead of fixing it.

If you have not saved a restore point on Windows, you may not be able to use this option. That said, Windows usually creates a restore point after an update. So, check if you have any restore points.

To perform a system restore:

Type Create a restore point

Click System Restore

Restore system files and settings

Restore your computer to the state it was in before a selected event

If you are not sure what to pick, you can select Scan for affected programs . Windows will give you a list of the files that may be affected by the restore point and possible issues that may be fixed in the process.

Fix 10: Reinstall Windows as a last resort

If you have tried everything above and nothing worked, you should consider reinstalling Windows. Sadly, this process will remove all your installed programs and system settings, essentially giving you a clean slate.

However, it is a good way to ensure that your system returns to a stable, error-free state by removing any deep-rooted problems that might be causing the recurring blue screen errors.


📌Here’s a detailed guide to help you: How to Factory Reset a Computer Running Windows 10/11


Windows Stop Codes: Explained

We hope that you have found a solution from the above steps. However, it does not end there. Once you’ve resolved the Windows stop code error, it’s essential to take proactive steps to prevent the BSOD from recurring.

One of the best things to do is keep a regular system maintenance schedule. This will help keep your computer running smoothly. To avoid stress, you can use third-party tools like Auslogics BoostSpeed or similar software to optimize and manage your system. 

Also, keep your machine updated, perform regular scans, and monitor your system performance. All of these steps will go a long way in preventing future errors.

By the way, we would like to hear from you! Drop a comment below and let us know how this guide helped you or if you have any additional questions!

FAQ

Yes, hardware issues can absolutely cause the dreaded Windows stop code errors. Hardware problems such as faulty RAM, failing hard drives, overheating CPUs, or issues with other components can trigger various Windows 10 stop code errors, as well as Windows 11.

You can check the system event logs. Go to the Event Viewer, then navigate to Windows Logs > System. Look for any error or warning entries around the time the stop code error occurred, as these may provide clues about the root cause. You can also try uninstalling or rolling back any recent driver or software updates to see if that resolves the issue.

Yes, memory-related problems can trigger BSOD errors.

Windows restarts by default when it encounters a BSOD event. Restarting often fixes the problem, especially when the underlying cause is temporary.

You can find out the causes of BSOD events by checking the dump file saved to your hard drive or going through the Event Viewer.

By performing regular maintenance, keeping your operating system and drivers up to date, avoiding overheating, and eliminating malware.

Источник

 S.NO Name  Explanation Code
1 APC_INDEX_MISMATCH This BSOD appears on exit from a system call and it is an outcome of internal error in kernel. 0x00000001
2 DEVICE_QUEUE_NOT_BUSY This is an uncommon Blue screen error harmful to devices. 0x00000002
3 INVALID_AFFINITY_SET Rare bugcheck and doesn’t appear commonly. 0x00000003
4 INVALID_DATA_ACCESS_TRAP Again an occasionally occurring error that indicates an incorrect data access trap. 0x00000004
5 INVALID_PROCESS_ATTACH_ATTEMPT This BSOD commonly appears when a driver requests the KeAttachProcess function and the thread is attached to a different process. 0x00000005
6 INVALID_PROCESS_DETACH_ATTEMPT The BSOD appears after calling KeStackAttachProcess routine and afterward KeUnstackDetachProcess. The process is necessary for the driver’s implementation of callback function PLOAD_IMAGE_NOTIFY_ROUTINE. 0x00000006
7 INVALID_SOFTWARE_INTERRUPT Infrequent occurring bugcheck. 0x00000007
8 IRQL_NOT_DISPATCH_LEVEL Rare Blue Screen 0x00000008
9 IRQL_NOT_GREATER_OR_EQUAL “” 0x00000009
10 IRQL_NOT_LESS_OR_EQUAL Error message implies Windows or a kernel-mode driver accessed paged memory at an invalid address while at an IRQL. 0x0000000A
11 NO_EXCEPTION_HANDLING_SUPPORT Rare bugcheck 0x0000000B
12 MAXIMUM_WAIT_OBJECTS_EXCEEDED This BSOD is the consequent of improper use of FsRtlCancellableWaitForMultipleObjects or KeWaitForMultipleObjects. 0x0000000C
13 MUTEX_LEVEL_NUMBER_VIOLATION Seldom occurs 0x0000000D
14 NO_USER_MODE_CONTEXT Appears when a control returns from the initial thread procedure during starting a system thread 0x0000000E
15 SPIN_LOCK_ALREADY_OWNED Result of a recursive request for a spin lock or comparable function. 0x0000000F
16 SPIN_LOCK_NOT_OWNED Occurs occasionally 0x00000010
17 THREAD_NOT_MUTEX_OWNER “” 0x00000011
18 TRAP_CAUSE_UNKNOWN Unknown exception 0x00000012
19 EMPTY_THREAD_REAPER_LIST Sporadically occurs 0x00000013
20 CREATE_DELETE_LOCK_NOT_LOCKED Rare bugcheck 0x00000014
21 LAST_CHANCE_CALLED_FROM_KMODE “” 0x00000015
22 CID_HANDLE_CREATION “” 0x00000016
23 CID_HANDLE_DELETION “” 0x00000017
24 REFERENCE_BY_POINTER Consequences of reference count of an object which is illegal for the present state of the object. 0x00000018
25 BAD_POOL_HEADER Corrupt pool header at the time of current request generates this issue. 0x00000019
26 MEMORY_MANAGEMENT Different flaws in memory management cause this BSOD. 0x0000001A
27 PFN_SHARE_COUNT Doesn’t occur in Windows 10 currently 0x0000001B
28 PFN_REFERENCE_COUNT Appears very infrequently. 0x0000001C
29 NO_SPIN_LOCK_AVAILABLE “” 0x0000001D
30 KMODE_EXCEPTION_NOT_HANDLED Faulty Services or driver causes a kernel mode program to create an exception. Error handler fails to catch this exception. 0x0000001E
31 SHARED_RESOURCE_CONV_ERROR Rare Blue Screen Error 0x0000001F
32 KERNEL_APC_PENDING_DURING_EXIT BSoD occurs when an asynchronous procedure call was remaining in pending state when a thread exited. 0x00000020
33 QUOTA_UNDERFLOW This Stop error appears after quota charges are mishandled by returning more quota. This occurs to a particular block that was previously charged. 0x00000021
34 FILE_SYSTEM Infrequent bugcheck 0x00000022
35 FAT_FILE_SYSTEM BSoD happens because of corruption in FAT file system mostly due to Bad sectors or blocks in disk. 0x00000023
36 NTFS_FILE_SYSTEM Driver file ntfs.sys messes that allow the system to write and read to NTFS drives generate this flaw. 0x00000024
37 NPFS_FILE_SYSTEM Issues in NPFM File System lead to this Blue Screen. 0x00000025
38 CDFS_FILE_SYSTEM Corruption in CDFS File System causes this stop error mostly because of Bad sector in disk. 0x00000026
39 RDR_FILE_SYSTEM Depletion of nonpaged pool memory leads to issues in SMB redirector file system that finally results in this error. 0x00000027
40 CORRUPT_ACCESS_TOKEN Seldom occurring bugcheck 0x00000028
41 SECURITY_SYSTEM “” 0x00000029
42 INCONSISTENT_IRP Inconsistent  I/O request packets are the main reason behind this issue. 0x0000002A
43 PANIC_STACK_SWITCH kernel-mode driver using more stack space is the prime cause of this stop code. 0x0000002B
44 PORT_DRIVER_INTERNAL Rare stop error 0x0000002C
45 SCSI_DISK_DRIVER_INTERNAL “” 0x0000002D
46 DATA_BUS_ERROR Mainly occurs because of memory issues or configuration. 0x0000002E
47 INSTRUCTION_BUS_ERROR Rare Stop code 0x0000002F
48 SET_OF_INVALID_CONTEXT Stack pointer in a trap frame having an invalid value leads to this problem 0x00000030
49 PHASE0_INITIALIZATION_FAILED In this situation, System initialization fails at a very early stage. 0x00000031
50 PHASE1_INITIALIZATION_FAILED “” 0x00000032
51 UNEXPECTED_INITIALIZATION_CALL Scanty bugcheck 0x00000033
52 CACHE_MANAGER Depletion of nonpaged pool memory causes issues with file system’s cache manager that ends up with this error. 0x00000034
53 NO_MORE_IRP_STACK_LOCATIONS This BSOD appears due to IoCallDriver packet that has no more stack locations remnant in the packet. 0x00000035
54 DEVICE_REFERENCE_COUNT_NOT_ZERO Driver tried to remove a device object still the reference count didn’t become 0. 0x00000036
55 FLOPPY_INTERNAL_ERROR Infrequent error 0x00000037
56 SERIAL_DRIVER_INTERNAL “” 0x00000038
57 SYSTEM_EXIT_OWNED_MUTEX The worker routine returned back without freeing the mutex object that it owned. 0x00000039
58 SYSTEM_UNWIND_PREVIOUS_USER Seldom occurring error 0x0000003A
59 SYSTEM_SERVICE_EXCEPTION Appears when executing code has an exception and thread system thread is under this value. 0x0000003B
60 INTERRUPT_UNWIND_ATTEMPTED Rare stop code 0x0000003C
61 INTERRUPT_EXCEPTION_NOT_HANDLED “” 0x0000003D
62 MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED System contains more than one processor, but they are not symmetric to each other. 0x0000003E
63 NO_MORE_SYSTEM_PTES Page table entries in fragmented state have been generated because of too many I/O actions. 0x0000003F
64 TARGET_MDL_TOO_SMALL target MDL too large to map the whole range of addresses requested by a driver. 0x00000040
65 MUST_SUCCEED_POOL_EMPTY This Blue Screen appears because must-succeed pool couldn’t fulfill the requests of Kernel-mode thread. 0x00000041
66 ATDISK_DRIVER_INTERNAL Infrequent issue 0x00000042
67 NO_SUCH_PARTITION “” 0x00000043
68 MULTIPLE_IRP_COMPLETE_REQUESTS Driver has tried to request an I/O request packet be completed that is already complete. 0x00000044
69 INSUFFICIENT_SYSTEM_MAP_REGS Rare problem 0x00000045
70 DEREF_UNKNOWN_LOGON_SESSION “” 0x00000046
71 REF_UNKNOWN_LOGON_SESSION “” 0x00000047
72 CANCEL_STATE_IN_COMPLETED_IRP  BSoD occurs because an IRP was completed, and then was hereinafter canceled. 0x00000048
73 PAGE_FAULT_WITH_INTERRUPTS_OFF exceptional issue 0x00000049
74 IRQL_GT_ZERO_AT_SYSTEM_SERVICE Stop code appears because of the Thread that is returning back from a system call to user mode whereas its IRQL is higher than PASSIVE_LEVEL. 0x0000004A
75 STREAMS_INTERNAL_ERROR Infrequent Blue Screen 0x0000004B
76 FATAL_UNHANDLED_HARD_ERROR “” 0x0000004C
77 NO_PAGES_AVAILABLE The error occurs when free pages are unavailable to continue operations. 0x0000004D
78 PFN_LIST_CORRUPT Shows up when page frame number list becomes corrupted. 0x0000004E
79 NDIS_INTERNAL_ERROR Rare problem 0x0000004F
80 PAGE_FAULT_IN_NONPAGED_AREA Occurs when system references invalid memory. 0x00000050
81 REGISTRY_ERROR Indicates that registry is damaged and malfunctioning. 0x00000051
82 MAILSLOT_FILE_SYSTEM Infrequent problem 0x00000052
83 NO_BOOT_DEVICE “” 0x00000053
84 LM_SERVER_INTERNAL_ERROR “” 0x00000054
85 DATA_COHERENCY_EXCEPTION “” 0x00000055
86 INSTRUCTION_COHERENCY_EXCEPTION “” 0x00000056
87 XNS_INTERNAL_ERROR “” 0x00000057
88 FTDISK_INTERNAL_ERROR Error appears after system is booted from the incorrect copy of a mirrored partition. 0x00000058
89 PINBALL_FILE_SYSTEM nonpaged pool memory, when got depleted may lead to a Pinball file system. 0x00000059
90 CRITICAL_SERVICE_FAILED Infrequent error 0x0000005A
91 SET_ENV_VAR_FAILED “” 0x0000005B
92 HAL_INITIALIZATION_FAILED Failed HAL initialization leads to throwing BSOD issue 0x0000005C
93 UNSUPPORTED_PROCESSOR When machine tries to run run an unsupported processor this Blue screen appears. 0x0000005D
94 OBJECT_INITIALIZATION_FAILED Rarely occurs 0x0000005E
95 SECURITY_INITIALIZATION_FAILED “” 0x0000005F
96 PROCESS_INITIALIZATION_FAILED “” 0x00000060
97 HAL1_INITIALIZATION_FAILED “” 0x00000061
98 OBJECT1_INITIALIZATION_FAILED “” 0x00000062
99 SECURITY1_INITIALIZATION_FAILED “” 0x00000063
100 SYMBOLIC_INITIALIZATION_FAILED “” 0x00000064
101 MEMORY1_INITIALIZATION_FAILED “” 0x00000065
102 CACHE_INITIALIZATION_FAILED “” 0x00000066
103 CONFIG_INITIALIZATION_FAILED When Registry configuration gets failed the stop code appears. 0x00000067
104 FILE_INITIALIZATION_FAILED Infrequent Blue Screen 0x00000068
105 IO1_INITIALIZATION_FAILED initialization of the I/O system failed leads this stop code to appear. 0x00000069
106 LPC_INITIALIZATION_FAILED Seldom occurring Blue screen 0x0000006A
107 PROCESS1_INITIALIZATION_FAILED Initialization of the OS failed causes this stop code. 0x0000006B
108 REFMON_INITIALIZATION_FAILED Occasionally occurs 0x0000006C
109 SESSION1_INITIALIZATION_FAILED Windows OS Initialization failure leads to throw this BSOD. 0x0000006D
110 SESSION2_INITIALIZATION_FAILED “” 0x0000006E
111 SESSION3_INITIALIZATION_FAILED “” 0x0000006F
112 SESSION4_INITIALIZATION_FAILED “” 0x00000070
113 SESSION5_INITIALIZATION_FAILED “” 0x00000071
114 ASSIGN_DRIVE_LETTERS_FAILED Rare issue 0x00000072
115 CONFIG_LIST_FAILED When Core registry hives are unable to link the registry tree this error appears. 0x00000073
116 BAD_SYSTEM_CONFIG_INFO Corruption in registry is the main cause of this blue screen. 0x00000074
117 CANNOT_WRITE_CONFIGURATION When registry hive file fails to be converted to a mapped file this BSoD shows up. 0x00000075
118 PROCESS_HAS_LOCKED_PAGES Device Driver tries to unlock pages that are previously unlocked or locked and fails to do so throwing the error. 0x00000076
119 KERNEL_STACK_INPAGE_ERROR Memory fails to read requested page of kernel data coming from the paging file and throws BSOD. 0x00000077
120 PHASE0_EXCEPTION An unexpected crash during HAL initialization causes this issue. 0x00000078
121 MISMATCHED_HAL The prime cause of this error is Hardware Abstraction Layer revision level or configuration that fails to match that of the computer or kernel. 0x00000079
122 KERNEL_DATA_INPAGE_ERROR Memory finds itself unable to read the requested page of kernel data. 0x0000007A
123 INACCESSIBLE_BOOT_DEVICE Windows OS cannot access the system partition while starting up. 0x0000007B
124 BUGCODE_NDIS_DRIVER Windows identifies a defect in Networking driver. 0x0000007C
125 INSTALL_MORE_MEMORY Lack of memory to start Windows. 0x0000007D
126 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED Error handler cannot trace out an exception caused by thread. 0x0000007E
127 UNEXPECTED_KERNEL_MODE_TRAP Intel CPU gives rise to a trap and kernel becomes unable to catch this. 0x0000007F
128 NMI_HARDWARE_FAILURE A malfunction is progressing into hardware. 0x00000080
129 SPIN_LOCK_INIT_FAILURE Infrequent issue 0x00000081
130 DFS_FILE_SYSTEM “” 0x00000082
131 SETUP_FAILURE fatal error occurred during setup. 0x00000085
132 MBR_CHECKSUM_MISMATCH This stop code appears when mismatch happens in the MBR checksum 0x0000008B
133 KERNEL_MODE_EXCEPTION_NOT_HANDLED The error handler fails to identify exception created by kernel-mode application. 0x0000008E
134 PP0_INITIALIZATION_FAILED Error appears when Plug and Play manager is not able to be initialized. 0x0000008F
135 PP1_INITIALIZATION_FAILED “” 0x00000090
136 UP_DRIVER_ON_MP_SYSTEM Windows is running on multiprocessor however driver is assembled to work on only one. 0x00000092
137 INVALID_KERNEL_HANDLE BSoD generated when Kernel code attempted to end protected or invalid handle. 0x00000093
138 KERNEL_STACK_LOCKED_AT_EXIT Blue screen occurs with this stop code because thread exits while its kernel stack is specified as not swappable 0x00000094
139 INVALID_WORK_QUEUE_ITEM BSoD appears when queue entry is deleted that includes a NULL pointer. 0x00000096
140 BOUND_IMAGE_UNSUPPORTED Occasional problem 0x00000097
141 END_OF_NT_EVALUATION_PERIOD Appears when trial period of Windows comes to end. 0x00000098
142 INVALID_REGION_OR_SEGMENT Blue screen crops up when ExInterlockedExtendRegion or ExInitializeRegion is called with an invalid set of parameters. 0x00000099
143 SYSTEM_LICENSE_VIOLATION Violation of license agreement leads to shape up this BSoD error. 0x0000009A
144 UDFS_FILE_SYSTEM Damage in UDF File System produces this issue. 0x0000009B
145 MACHINE_CHECK_EXCEPTION When fatal machine check exception eventuates this error appears. 0x0000009C
146 USER_MODE_HEALTH_MONITOR The Components of critical user-mode are unable to fulfill a health check 0x0000009E
147 DRIVER_POWER_STATE_FAILURE BSoD shows up when a driver remains in an invalid or inconsistent power state. 0x0000009F
148 INTERNAL_POWER_ERROR Occurs due to power policy manager that encounters a fatal error. 0x000000A0
149 PCI_BUS_DRIVER_INTERNAL PCI Bus driver identifies inconsistency difficulties in its internal structures and fails to continue. 0x000000A1
150 MEMORY_IMAGE_CORRUPT Damage in the image of an executable file living in memory leads to this problem. 0x000000A2
151 ACPI_DRIVER_INTERNAL This mess up occurs because ACPI driver enucleates an internal inconsistency. 0x000000A3
152 CNSS_FILE_SYSTEM_FILTER Reason for the problem is damage to CNSS file system filter. 0x000000A4
153 ACPI_BIOS_ERROR Advanced Configuration and Power Interface BIOS is not perfectly acquiescent with the ACPI specification. 0x000000A5
154 BAD_EXHANDLE The flaw occurs due to “kernel-mode handle table” that identifies an inconsistent entry state. 0x000000A7
155 SESSION_HAS_VALID_POOL_ON_EXIT During this bug situation, session device driver doesn’t release its pool allocations prior to a session unload. 0x000000AB
156 HAL_MEMORY_ALLOCATION Hardware abstraction layer fails to find enough amount of non-paged memory pool for a critical requirement. 0x000000AC
157 VIDEO_DRIVER_DEBUG_REPORT_REQUEST Video port generates a minidump to satisfy the driver’s request. 0x000000AD
158 BGI_DETECTED_VIOLATION Rare bugcheck 0x000000B1
159 VIDEO_DRIVER_INIT_FAILURE Windows cannot access graphics mode. 0x000000B4
160 ATTEMPTED_SWITCH_FROM_DPC DPC tried an illegitimate operation. 0x000000B8
161 CHIPSET_DETECTED_ERROR Infrequent error 0x000000B9
162 SESSION_HAS_VALID_VIEWS_ON_EXIT A session driver mapped views cannot be unmapped before session unloaded. 0x000000BA
163 NETWORK_BOOT_INITIALIZATION_FAILED Windows is unsuccessful to boot off a network. 0x000000BB
164 NETWORK_BOOT_DUPLICATE_ADDRESS Issue occurs when an extra identical IP address is assigned to the pc while booting off a network. 0x000000BC
165 INVALID_HIBERNATED_STATE Memory image created by hibernation is not compatible with the previous hardware configuration. 0x000000BD
166 ATTEMPTED_WRITE_TO_READONLY_MEMORY The issue appears when driver tries to write read only file. 0x000000BE
167 MUTEX_ALREADY_OWNED Shape up when thread tries to acquire ownership of a mutex it owns so far. 0x000000BF
168 SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION Occurs when driver writes to an invalid area of the special pool 0x000000C1
169 BAD_POOL_CALLER A thread requests invalid pools. 0x000000C2
170 DRIVER_VERIFIER_DETECTED_VIOLATION Malfunctioning of driver verifier gives rise to this code. 0x000000C4
171 DRIVER_CORRUPTED_EXPOOL This BSoD appears when system tries to approach invalid memory at a process IRQL that is extremely high. 0x000000C5
172 DRIVER_CAUGHT_MODIFYING_FREED_POOL Driver tries to access a released memory pool. 0x000000C6
173 TIMER_OR_DPC_INVALID The BSOD appears when DPC or kernel timer remains somewhere in memory where it is not permitted. 0x000000C7
174 IRQL_UNEXPECTED_VALUE IRQL of processor has not the value what it should be currently. 0x000000C8
175 DRIVER_VERIFIER_IOMANAGER_VIOLATION I/O violation by driver verifier throws this issue. 0x000000C9
176 PNP_DETECTED_FATAL_ERROR BSOD prompts when Plug and Play Manager confront a severe error. 0x000000CA
177 DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS I/O manager or driver is unsuccessful to free locked pages subsequent to an operation. 0x000000CB
178 PAGE_FAULT_IN_FREED_SPECIAL_POOL System has referenced memory which was previously released. 0x000000CC
179 PAGE_FAULT_BEYOND_END_OF_ALLOCATION The BSOD prompts when system accesses memory beyond the end of some driver’s pool allocation. 0x000000CD
180 DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS The issue takes place when driver fails to terminate pending operations prior to unloading. 0x000000CE
181 TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE Driver, incorrectly ported to the terminal server cause this problem. 0x000000CF
182 DRIVER_CORRUPTED_MMPOOL The issue occurs because system tries to access invalid memory at a process IRQL that is extremely high. 0x000000D0
183 DRIVER_IRQL_NOT_LESS_OR_EQUAL Kernel-mode driver attempted to access pageable memory while the process IRQL was too high. 0x000000D1
184 BUGCODE_ID_DRIVER Issue running in an NDIS driver 0x000000D2
185 DRIVER_PORTION_MUST_BE_NONPAGED System attempted to access pageable memory at a process IRQL that was too high. 0x000000D3
186 SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD Driver doesn’t close pending operations previous to unloading. 0x000000D4
187 DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL Driver has referenced memory which was earlier freed. 0x000000D5
188 DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION Issue appears when driver accesses memory further away than the end of its pool allocation. 0x000000D6
189 DRIVER_UNMAPPING_INVALID_VIEW Driver is attempting to unmap mapped address. 0x000000D7
190 DRIVER_USED_EXCESSIVE_PTES Page table entries are not available further. 0x000000D8
191 LOCKED_PAGES_TRACKER_CORRUPTION BSOD occurs because of damage in internal locked-page tracking structures. 0x000000D9
192 SYSTEM_PTE_MISUSE BSoD shows up because of Page table entry routine which has been used in an improper method. 0x000000DA
193 DRIVER_CORRUPTED_SYSPTES Driver tries to access memory at an invalid IRQL, possibly because of damage in system Page table entries. 0x000000DB
194 DRIVER_INVALID_STACK_ACCESS Driver accessed a stack address that resides under the stack pointer of the thread. 0x000000DC
195 POOL_CORRUPTION_IN_FILE_AREA Driver has malfunctioning pool memory that is used for holding pages designated for disk. 0x000000DE
196 IMPERSONATING_WORKER_THREAD Work item did not disable impersonation before it completed. 0x000000DF
197 ACPI_BIOS_FATAL_ERROR Any component is faulty 0x000000E0
198 WORKER_THREAD_RETURNED_AT_BAD_IRQL A worker thread completed and returned with IRQL => DISPATCH_LEVEL. 0x000000E1
199 MANUALLY_INITIATED_CRASH This Blue screen appears when a user purposely initiates a crash dump from either keyboard or kernel debugger. 0x000000E2
200 RESOURCE_NOT_OWNED Occurs after a thread tries to free a resource it didn’t own. 0x000000E3
201 WORKER_INVALID Issue is commonly the result of the memory which driver releases but it still contains an executive work item. 0x000000E4
202 DRIVER_VERIFIER_DMA_VIOLATION Refers to entire Driver Verifier DMA Verification violations. 0x000000E6
203 INVALID_FLOATING_POINT_STATE Floating-point state stored by a thread is invalid. 0x000000E7
204 INVALID_CANCEL_OF_FILE_OPEN Invalid file object was passed to IoCancelFileOpen 0x000000E8
205 ACTIVE_EX_WORKER_
THREAD_TERMINATION
Blue Screen shows up because of termination of an active executive worker thread. 0x000000E9
206 THREAD_STUCK_IN_DEVICE_DRIVER Thread in a driver is everlastingly spinning. 0x000000EA
207 DIRTY_MAPPED_PAGES_CONGESTION Blue screen appears when free pages are unavailable to further continue operations. 0x000000EB
208 SESSION_HAS_VALID_
SPECIAL_POOL_ON_EXIT
A session driver holds memory but session unload occurs. 0x000000EC
209 UNMOUNTABLE_BOOT_VOLUME BSOD appears because input and output subsystem tries to mount the boot volume and it fails. 0x000000ED
210 CRITICAL_PROCESS_DIED Occurs when critical system process died. 0x000000EF
211 STORAGE_MINIPORT_ERROR The prime cause is the storage Miniport driver that fails to satisfy a SRB request. 0x000000F0
212 SCSI_VERIFIER_DETECTED_VIOLATION The Blue Screen of Death refers to entire Driver Verifier SCSI Verification violations. 0x000000F1
213 HARDWARE_INTERRUPT_STORM Occurrence of this BSOD is because of the kernel that discovers an interrupt storm. 0x000000F2
214 DISORDERLY_SHUTDOWN Windows fails to shut down because of short of memory. 0x000000F3
215 CRITICAL_OBJECT_TERMINATION A process or thread crucial to system operation has unexpectedly exited or been terminated. 0x000000F4
216 FLTMGR_FILE_SYSTEM Blue Screen of Death appears due to the Filter Manager which encountered unrecoverable failure. 0x000000F5
217 PCI_VERIFIER_DETECTED_VIOLATION PCI driver is verifying an error in BIOS or another device. 0x000000F6
218 DRIVER_OVERRAN_STACK_BUFFER A driver has overrun a stack-based buffer. 0x000000F7
219 RAMDISK_BOOT_INITIALIZATION_FAILED When RAM disk is used to boot an initialization failure takes place. 0x000000F8
220 DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN A device driver returned “STATUS_REPARSE” to an IRP_MJ_CREATE request without trailing names. 0x000000F9
221 HTTP_DRIVER_CORRUPTED Http.sys has come to a corrupted state and unable to recover. 0x000000FA
222 ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY The Blue Screen of Death bug shows up when trying to execute a non-executable memory. 0x000000FC
223 DIRTY_NOWRITE_PAGES_CONGESTION BSOD occurs due to unable to continue basic system operations because of unavailability of free pages. 0x000000FD
224 BUGCODE_USB_DRIVER USB driver encounters error. 0x000000FE
225 RESERVE_QUEUE_OVERFLOW The issue appears due to overflow of Queue because of inserting a new item into a reserve queue. 0x000000FF
226 LOADER_BLOCK_MISMATCH Reason for this problem is either the loader block is invalid, or it does not match the system that is being loaded. 0x00000100
227 CLOCK_WATCHDOG_TIMEOUT Secondary processor experience an expected clock interrupt. This occurs in a multi-processor system that doesn’t receive under allocated interval. 0x00000101
228 DPC_WATCHDOG_TIMEOUT Blue screen of death appears because Deferred Procedure Call watchdog routine isn’t executed in allocated time interval. 0x00000102
229 MUP_FILE_SYSTEM Reason of the BSOD is Multiple UNC provider that has experienced invalid or unexpected data. 0x00000103
230 AGP_INVALID_ACCESS Graphic Processing Unit writes to a range of AGP memory that had not earlier been committed. 0x00000104
231 AGP_GART_CORRUPTION Blue screen appears because GART is corrupt. 0x00000105
232 AGP_ILLEGALLY_REPROGRAMMED An unauthorized agent has re-programmed AGP hardware. 0x00000106
233 THIRD_PARTY_FILE_SYSTEM_FAILURE File system filter or 3rd party file system encounter an unrecoverable issue. 0x00000108
234 CRITICAL_STRUCTURE_CORRUPTION Kernel has identified critical kernel code or data corruption. 0x00000109
235 APP_TAGGING_INITIALIZATION_FAILED “” 0x0000010A
236 FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION Blue Screen occurs when a violation is detected in the FsRtl ECP package. 0x0000010C
237 WDF_VIOLATION KMDF identify that Windows find an error in a framework-based driver. 0x0000010D
238 VIDEO_MEMORY_MANAGEMENT_INTERNAL In this Blue screen condition, video memory manager is unable to recover. 0x0000010E
239 RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED BSod refers to the unrecoverable state of resource manager. 0x0000010F
240 RECURSIVE_NMI A non-maskable-interrupt happens while a previous NMI was going on. 0x00000111
241 MSRPC_STATE_VIOLATION In this issue, Msrpc.sys driver has started a bug check. 0x00000112
242 VIDEO_DXGKRNL_FATAL_ERROR Infrequent error 0x00000113
243 VIDEO_SHADOW_DRIVER_FATAL_ERROR “” 0x00000114
244 AGP_INTERNAL “” 0x00000115
245 VIDEO_TDR_FAILURE When trying to reset display driver furthermore recover from a timeout fails and prompts BSoD. 0x00000116
246 VIDEO_TDR_TIMEOUT_DETECTED Graphics driver is unable to respond in a timely method. 0x00000117
247 VIDEO_SCHEDULER_INTERNAL_ERROR BSoD prompts because video scheduler has encountered a fatal violation. 0x00000119
248 EM_INITIALIZATION_FAILURE Rare bugcheck 0x0000011A
249 DRIVER_RETURNED_HOLDING_CANCEL_LOCK A driver has returned from a cancel routine that holds the global cancel lock. 0x0000011B
250 ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE The issue occurs when configuration manager read-only protected storage is written. 0x0000011C
251 EVENT_TRACING_FATAL_ERROR Blue Screen of Death appears because of the Event Tracing sub-system that has experienced an unexpected fatal error. 0x0000011D
252 TOO_MANY_RECURSIVE_FAULTS A file system has produced lots of recursive faults under low resource conditions that cannot be handled. 0x0000011E
253 INVALID_DRIVER_HANDLE Somebody has stopped the initial handle for a driver between inserting the driver object and referencing the handle. 0x0000011F
254 BITLOCKER_FATAL_ERROR BSoD occurs because BitLocker drive encryption encountered an issue that it cannot recover from. 0x00000120
255 DRIVER_VIOLATION Driver has caused a violation. 0x00000121
256 WHEA_INTERNAL_ERROR An internal issue takes place in the Windows Hardware Error Architecture. 0x00000122
257 CRYPTO_SELF_TEST_FAILURE Cryptographic subsystem failed a mandatory algorithm self-test during bootstrap. 0x00000123
258 WHEA_UNCORRECTABLE_ERROR A fatal error in hardware has occurred. 0x00000124
259 NMR_INVALID_STATE NMR has found an invalid state. 0x00000125
260 NETIO_INVALID_POOL_CALLER An invalid pool request has been made to netio managed memory pool, e.g. FSB and MDL. 0x00000126
261 PAGE_NOT_ZERO Blue Screen of Death appears when a page isn’t filled with 0 but it should be. 0x00000127
262 WORKER_THREAD_RETURNED_WITH_BAD_IO_PRIORITY A worker threads IOPriority was incorrectly changed by the called worker routine. 0x00000128
263 WORKER_THREAD_RETURNED_WITH_BAD_PAGING_IO_PRIORITY A worker threads Paging IOPriority was wrongly modified by the called worker routine. 0x00000129
264 MUI_NO_VALID_SYSTEM_LANGUAGE BSOD stop code occurs when Windows doesn’t notice installed, licensed language packs for the default UI language. 0x0000012A
265 FAULTY_HARDWARE_CORRUPTED_PAGE A damage in memory manager caused by a component that accesses memory through physical addressing. 0x0000012B
266 EXFAT_FILE_SYSTEM exFAT file system encountered an issue. 0x0000012C
267 VOLSNAP_OVERLAPPED_TABLE_ACCESS Volsnap attempted to access a common table from two different threads which may result in table corruption and eventually corrupt the table. 0x0000012D
268 INVALID_MDL_RANGE This is typically a driver bug. 0x0000012E
269 VHD_BOOT_INITIALIZATION_FAILED Blue Screen of death appear because of initialization failure that take place while trying to boot from a VHD. 0x0000012F
270 DYNAMIC_ADD_PROCESSOR_MISMATCH Occurs when new processor is incompatible with the current configuration 0x00000130
271 INVALID_EXTENDED_PROCESSOR_STATE Appears when restoring or saving extended processor state. 0x00000131
272 RESOURCE_OWNER_POINTER_INVALID BSoD refers to supply of invalid resource owner pointer. 0x00000132
273 DPC_WATCHDOG_VIOLATION When faulty driver code doesn’t perform its work within the allotted time frame 0x00000133
274 DRIVE_EXTENDER Drive extender component has encountered a serious internal error that stops continued operation. 0x00000134
275 REGISTRY_FILTER_DRIVER_EXCEPTION Blue Screen of death appears because of an unhandled exception in a registry filtering driver. 0x00000135
276 VHD_BOOT_HOST_VOLUME_NOT_ENOUGH_SPACE When trying to boot via VHD an initialization failure occurs. 0x00000136
277 WIN32K_HANDLE_MANAGER win32k/ntuser handle manager encounters a fatal error. 0x00000137
278 GPIO_CONTROLLER_DRIVER_ERROR BSoD occurs when GPIO class extension driver experienced a fatal error. 0x00000138
279 KERNEL_SECURITY_CHECK_FAILURE Kernel has identifies the damage in a critical data structure. 0x00000139
280 KERNEL_MODE_HEAP_CORRUPTION Kernel mode heap manager identifies damage in a heap. 0x0000013A
281 PASSIVE_INTERRUPT_ERROR Kernel has encountered problems with passive-level interrupt. 0x0000013B
282 INVALID_IO_BOOST_STATE BSoD occurs when a thread exits with an invalid Input or output boost state. 0x0000013C
283 CRITICAL_INITIALIZATION_FAILURE Blue Screen of Death prompts when early kernel initialization has failed. 0x0000013D
284 STORAGE_DEVICE_ABNORMALITY_DETECTED This mess up happens when storage driver stack experiences proportion of responsiveness violations surpassing the threshold, or other failures to respond. 0x00000140
285 VIDEO_ENGINE_TIMEOUT_DETECTED Either of the display engines is unable to respond in timely method. 0x00000141
286 VIDEO_TDR_APPLICATION_BLOCKED Display hardware cannot be accessed by an app. 0x00000142
287 PROCESSOR_DRIVER_INTERNAL Appears when PPM driver experiences a fatal error. 0x00000143
288 BUGCODE_USB3_DRIVER Occurs due to damage in USB 3 driver. 0x00000144
289 SECURE_BOOT_VIOLATION A necessary operation not being performed or invalid policy leads to prevent the starting of secure Boot policy enforcement. 0x00000145
290 ABNORMAL_RESET_DETECTED The issue appears when Windows undergo an abnormal reset 0x00000147
291 REFS_FILE_SYSTEM A file system error has occurred. 0x00000149
292 KERNEL_WMI_INTERNAL Blue Screen of death appears because a fatal error occurs in internal kernel WMI subsystem. 0x0000014A
293 SOC_SUBSYSTEM_FAILURE System on Chip subsystems experienced an unrecoverable issue. 0x0000014B
294 FATAL_ABNORMAL_RESET_ERROR System has abnormally reset. 0x0000014C
295 EXCEPTION_SCOPE_INVALID Appears because System encounters internal inconsistency in exception dispatching 0x0000014D
296 SOC_CRITICAL_DEVICE_REMOVED A critical System on a Chip device has been unexpectedly failed or removed. 0x0000014E
297 PDC_WATCHDOG_TIMEOUT A system cannot return from standby because component is unable to respond within the allocated time period. 0x0000014F
298 TCPIP_AOAC_NIC_ACTIVE_REFERENCE_LEAK Until the send queue is fully drained NIC active reference should isn’t freed. 0x00000150
299 UNSUPPORTED_INSTRUCTION_MODE Prompts when you try to execute code via an unsupported processor instruction mode. 0x00000151
300 INVALID_PUSH_LOCK_FLAGS flags supplied to one of push lock APIs were invalid. 0x00000152
301 KERNEL_LOCK_ENTRY_LEAKED_ON_THREAD_TERMINATION Before a thread releases entire AutoBoost lock entries it is terminated. 0x00000153
302 UNEXPECTED_STORE_EXCEPTION Unexpected exception occurs in store component. 0x00000154
303 OS_DATA_TAMPERING Rare bugcheck 0x00000155
304 WINSOCK_DETECTED_HUNG_CLOSESOCKET_LIVEDUMP Blue screen appears after Winsock encounters a hung transport endpoint close request. 0x00000156
305 KERNEL_THREAD_PRIORITY_FLOOR_VIOLATION BSoD occurs when on the priority floor of a particular thread an illegal operation is attempted. 0x00000157
306 ILLEGAL_IOMMU_PAGE_FAULT Blue Screen of Death appears because IOMMU has delivered a page fault packet for an invalid ASID. 0x00000158
307 HAL_ILLEGAL_IOMMU_PAGE_FAULT IOMMU vendor has delivered a page fault against an ASID that was in the process of being freed. 0x00000159
308 SDBUS_INTERNAL_ERROR SD-attached device encountered unrecoverable hardware failure. 0x0000015A
309 WORKER_THREAD_RETURNED_WITH_SYSTEM_PAGE_PRIORITY_ACTIVE Blue screen occurs when called worker routine leaks worker thread’s system page priority 0x0000015B
310 PDC_WATCHDOG_TIMEOUT_LIVEDUMP BSOD occurs because a system component becomes unable to respond within the allocated time period and prevents from exiting or entering standby. 0x0000015C
311 SOC_SUBSYSTEM_FAILURE_LIVEDUMP SoC subsystem encountered a critical fault and captured a live kernel dump. 0x0000015D
312 BUGCODE_NDIS_DRIVER_LIVE_DUMP NDIS has captured a live kernel dump. 0x0000015E
313 CONNECTED_STANDBY_WATCHDOG_TIMEOUT_LIVEDUMP Blue Screen appears because an issue prompts in connected standby watchdog timeout. 0x0000015F
314 WIN32K_ATOMIC_CHECK_FAILURE Win32k function has violated an ATOMICCHECK. 0x00000160
315 LIVE_SYSTEM_DUMP Blue Screen occurs because the system administrator requested the collection of a live system memory dump. 0x00000161
316 KERNEL_AUTO_BOOST_INVALID_LOCK_RELEASE A thread that doesn’t own a lock has freed the lock tracked by AutoBoost. 0x00000162
317 WORKER_THREAD_TEST_CONDITION Kernel worker threads raised a failure. 0x00000163
318 WIN32K_CRITICAL_FAILURE Win32k has encountered a critical failure. 0x00000164
319 CLUSTER_CSV_STATUS_IO_TIMEOUT_LIVEDUMP  SMB client on the non-coordinating node complains that an IO on coordinating node is taking too long and fails all IOs with STATUS_IO_TIMEOUT. 0x00000165
320 CLUSTER_RESOURCE_CALL_TIMEOUT_LIVEDUMP BSOD occurs after Cluster Resource call takes more time than configured timeout. 0x00000166
321 CLUSTER_CSV_SNAPSHOT_DEVICE_INFO_TIMEOUT_LIVEDUMP Cluster Service call to the volume snap to query snapshot information took too long. 0x00000167
322 CLUSTER_CSV_STATE_TRANSITION_TIMEOUT_LIVEDUMP Blue screen throws up because Cluster Shared Volume state transition takes too long. 0x00000168
323 CLUSTER_CSV_VOLUME_ARRIVAL_LIVEDUMP CSV Manager was asked to create a new volume device object, and it has not reached in time. 0x00000169
324 CLUSTER_CSV_VOLUME_REMOVAL_LIVEDUMP Blue Screen occurs because a CSV Manager volume removal request has timed out. 0x0000016A
325 CLUSTER_CSV_CLUSTER_WATCHDOG_LIVEDUMP Cluster service user mode watchdog identified that a thread is not progressing for a long. 0x0000016B
326 INVALID_RUNDOWN_
PROTECTION_FLAGS
The reason of this Blue Screen error is the flags supplied to one of the rundown protection APIs which were invalid. 0x0000016C
327 INVALID_SLOT_ALLOCATOR_FLAGS flags supplied to one of the slot allocation API were invalid. 0x0000016D
328 ERESOURCE_INVALID_RELEASE target thread pointer supplied to ExReleaseResourceForThreadLite was invalid. 0x0000016E
329 CLUSTER_CSV_STATE_TRANSITION_INTERVAL_TIMEOUT_LIVEDUMP CSV next state transition request has not reached. 0x0000016F
330 CRYPTO_LIBRARY_INTERNAL_ERROR Blue Screen throws up when internal error in the crypto libraries occurs. 0x00000170
331 CLUSTER_CSV_CLUSSVC_DISCONNECT_WATCHDOG Cluster disconnect is not making forward progress. 0x00000171
332 COREMSGCALL_INTERNAL_ERROR CoreMessageCall encountered an unrecoverable error. 0x00000173
333 COREMSG_INTERNAL_ERROR Blue Screen appears when CoreMessaging detects an unrecoverable error. 0x00000174
334 PREVIOUS_FATAL_ABNORMAL_RESET_ERROR System has abnormally reset Windows phone or unrecoverable error occurred. 0x00000175
335 ELAM_DRIVER_DETECTED_FATAL_ERROR Early Launch Antimalware driver detected a fatal error. 0x00000178
336 CLUSTER_CLUSPORT_STATUS_IO_TIMEOUT_LIVEDUMP SMB client on the initiator node complains that an IO to a target node is taking too long and fails all IOs with STATUS_IO_TIMEOUT. 0x00000179
337 PROFILER_CONFIGURATION_ILLEGAL Rare bugcheck 0x0000017B
338 PDC_LOCK_WATCHDOG_LIVEDUMP BSoD prompts up when thread has been holding PDC lock too long. 0x0000017C
339 PDC_UNEXPECTED_
REVOCATION_LIVEDUMP
System unexpectedly revokes activator. 0x0000017D
340 MICROCODE_REVISION_MISMATCH Either one or multiple processors in the configuration have loaded inconsistent microcode. 0x0000017E
341 VIDEO_DWMINIT_TIMEOUT_FALLBACK_BDD Video fell back to Behavior-Driven Development rather than using the IHV driver. 0x00000187
342 CLUSTER_CSVFS_LIVEDUMP CSV File System initiated this livedump to help debug an inconsistent state. 0x00000188
343 BAD_OBJECT_HEADER Occurs because of damage in OBJECT_HEADER. 0x00000189
344 SECURE_KERNEL_ERROR Secure kernel confronts a fatal error. 0x0000018B
345 HYPERGUARD_VIOLATION Blue Screen throws up because kernel has identified critical kernel or code data have been corrupted. 0x0000018C
346 SECURE_FAULT_UNHANDLED Secure fault originated by the secure kernel could not be handled. 0x0000018D
347 KERNEL_PARTITION_
REFERENCE_VIOLATION
Issue takes place because a partition was improperly dereferenced. 0x0000018E
348 WIN32K_CRITICAL_FAILURE_LIVEDUMP Win32k has encountered a critical failure. 0x00000190
349 PF_DETECTED_CORRUPTION Rare bugcheck 0x00000191
350 KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL A lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or above. 0x00000192
351 VIDEO_DXGKRNL_LIVEDUMP dxgkrnl causes a livedump. 0x00000193
352 SMB_SERVER_LIVEDUMP BSOD prompts when SMB server encounters an issue and has captures a kernel dump to gather debug information. 0x00000195
353 LOADER_ROLLBACK_DETECTED OS loader edition doesn’t match the OS. 0x00000196
354 WIN32K_SECURITY_FAILURE WIN32K experiences security failure. 0x00000197
355 UFX_LIVEDUMP UFX livedump occurred. 0x00000198
356 KERNEL_STORAGE_SLOT_IN_USE Blue Screen of Death appears since storage slot fails to be released because there is an object using it. 0x00000199
357 WORKER_THREAD_RETURNED_WHILE_ATTACHED_TO_SILO “A worker thread attached to a silo and did not detach before returning”. 0x0000019A
358 TTM_FATAL_ERROR BSOD occurs when Terminal topology manager (TTM) encountered a fatal error. 0x0000019B
359 WIN32K_POWER_
WATCHDOG_TIMEOUT
Win32k didn’t turn on the monitor in a timely method. 0x0000019C
360 CLUSTER_SVHDX_LIVEDUMP SVHDX initiated this livedump to help debug an inconsistent state. 0x0000019D
361 TTM_WATCHDOG_TIMEOUT Terminal topology manager (TTM) identified that some device specific operations did not compete with the configured timeouts . 0x000001A0
362 CALL_HAS_NOT_RETURNED_WATCHDOG_TIMEOUT_LIVEDUMP A call has not returned within the timeout period. 0x000001A3
363 DRIPS_SW_HW_DIVERGENCE_LIVEDUMP Rare bugcheck 0x000001A4
364 USB_DRIPS_BLOCKER_SURPRISE_REMOVAL_LIVEDUMP A USB device will be surprisingly removed seeing that it is blocking DRIPS. 0x000001A5
365 BLUETOOTH_ERROR_RECOVERY_LIVEDUMP bthport.sys has tried to recover and reset the radio from an irremediable internal condition. 0x000001A6
366 SMB_REDIRECTOR_LIVEDUMP SMB redirector has identified an issue and has gathered a kernel dump to collect debug information. 0x000001A7
367 VIDEO_DXGKRNL_BLACK_SCREEN_LIVEDUMP A user initiated DXGKRNL livedump for the scenarios of black screen. 0x000001A8
368 VIDEO_MINIPORT_FAILED_LIVEDUMP Rare bugcheck 0x000001B0
369 DRIVER_VERIFIER_DETECTED_VIOLATION_LIVEDUMP A driver trying to damage the system has been detected. 0x000001C4
370 IO_THREADPOOL_DEADLOCK_LIVEDUMP A kernel mode thread pool experienced a deadlock condition. 0x000001C5
371 FAST_ERESOURCE_
PRECONDITION_VIOLATION
A current thread is carrying out an invalid call to a fast resource routine. 0x000001C6
372 STORE_DATA_STRUCTURE_CORRUPTION The store component identified a malfunction in its data structures. 0x000001C7
373 MANUALLY_INITIATED_POWER_BUTTON_HOLD BSOD appears when a user holds power button for a specified time 0x000001C8
374 USER_MODE_HEALTH_MONITOR_LIVEDUMP Blue Screen of Death appears when a critical user mode component is unable to fulfill a health check. 0x000001C9
375 SYNTHETIC_WATCHDOG_TIMEOUT System freezes and not processing timer ticks. 0x000001CA
376 INVALID_SILO_DETACH A thread cannot detach from a silo prior to exiting. 0x000001CB
377 EXRESOURCE_TIMEOUT_LIVEDUMP A deadlock situation or heavy contention which can lead to performance problems. 0x000001CC
378 INVALID_CALLBACK_STACK_ADDRESS BSOD occurs because the callback stack seems to be a user mode address which is illegitimate. 0x000001CD
379 INVALID_KERNEL_STACK_ADDRESS In the middle of context switch, an invalid initial kernel stack address was encountered. 0x000001CE
380 HARDWARE_WATCHDOG_TIMEOUT System freezes and is not processing timer ticks. 0x000001CF
381 CPI_FIRMWARE_WATCHDOG_TIMEOUT ACPI driver was not able to perform a task in expected allotted time. 0x000001D0
382 TELEMETRY_ASSERTS_LIVEDUMP Issue throws up when a Telemetry Assert verification fails. 0x000001D1
383 WORKER_THREAD_INVALID_STATE The problem refers to the invalid state of an executive worker thread. 0x000001D2
384 WFP_INVALID_OPERATION A Filtering Platform callout carries out an invalid operation. 0x000001D3
385 UCMUCSI_LIVEDUMP An UcmUcsi class extension has experienced an error. 0x000001D4
386 DRIVER_PNP_WATCHDOG A driver is not able to perform a PnP operation under a specific time. 0x000001D5
387 WORKER_THREAD_RETURNED_WITH_NON_DEFAULT_WORKLOAD_CLASS A worker thread modified its workload class and didn’t revert it prior to returning. 0x000001D6
388 EFS_FATAL_ERROR An Encrypting File System error situation has occurred such that cannot be handled without data loss or data corruption. 0x000001D7
389 UCMUCSI_FAILURE UCSI class extension has experienced an issue. 0x000001D8
390 HAL_IOMMU_INTERNAL_ERROR HAL IOMMU library encountered an internal error issue. 0x000001D9
391 IPI_WATCHDOG_TIMEOUT Blue screen of death prompts when a processor gets stuck in an IPI loop for more than the allowed time. 0x000001DB
392 DMA_COMMON_BUFFER_VECTOR_ERROR A driver has put the DMA vectored common buffer APIs to wrong use. 0x000001DC
393 XBOX_ERACTRL_CS_TIMEOUT BSOD throws up because eractrl.sys driver fails to transition the Xbox console to or from standby after an extended time. 0x00000356
394 BC_BLUETOOTH_VERIFIER_FAULT A driver has caused a violation. 0x00000BFE
395 BC_BTHMINI_VERIFIER_FAULT Bluetooth miniport extensible driver verifier has caught a violation. 0x00000BFF
396 HYPERVISOR_ERROR Issue prompts because hypervisor has experienced a fatal error. 0x00020001
397 SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M Similar to SYSTEM_THREAD_EXCEPTION_NOT_HANDLED 0x1000007E
398 UNEXPECTED_KERNEL_MODE_TRAP_M Similar to UNEXPECTED_KERNEL_MODE_TRAP 0x1000007F
399 KERNEL_MODE_EXCEPTION_NOT_HANDLED_M Similar to KERNEL_MODE_EXCEPTION_NOT_HANDLED 0x1000008E
400 THREAD_STUCK_IN_DEVICE_DRIVER_M Similar to THREAD_STUCK_IN_DEVICE_DRIVER 0x100000EA
401 THREAD_TERMINATE_HELD_MUTEX Blue Screen of Death throws up because a driver obtained a mutex on a thread that exited before it could be freed. 0x4000008A
402 STATUS_CANNOT_LOAD_REGISTRY_FILE As the code says registry file could not be loaded. 0xC0000218
403 WINLOGON_FATAL_ERROR BSOD appears when Winlogon process is unexpectedly closed. 0xC000021A
404 STATUS_IMAGE_CHECKSUM_MISMATCH A system DLL or driver has been damaged. 0xC0000221
405 MANUALLY_INITIATED_CRASH1 Blue Screen of Death prompts when a User intentionally initiated a crash dump using keyboard or kernel debugger. 0xDEADDEAD

Источник

Понравилась статья? Поделить с друзьями:
0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии
  • Система не обнаружила msvcr100 dll windows 10 как исправить
  • Как проверить не устарела ли версия windows
  • File bcd error code 0xc0000098 windows 10
  • Windows 11 tpm fix
  • Ksecpkg sys windows 10 синий экран