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.
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.
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.
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.
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.
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.
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.
- In the Event Viewer, look at the left panel and click Windows Logs category.
- Under Windows Logs , click on System. System logs carry detailed records of your system’s operations, including Microsoft stop code occurrences.
- In the top right, find Filter Current Log.
- In the dialogue box, check the boxes with the tags Critical and Error . Then, click OK .
- 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.