- Home
- Logging Guide
- Windows stop code repository
List of stop codes on Windows and their potential causes
In this page
- What is a Windows stop code?
- An exhaustive list of Windows stop codes and why they happen
- How ManageEngine EventLog Analyzer helps you with BSOD analysis for fast and effective troubleshooting in Windows
What is a Windows stop code?
Windows stop codes, often known as bug check codes, are unique identifiers that are represented in hexadecimal format (begins with 0x) and contain information as to what caused the device to crash and stop functioning.
When an error occurs, Windows generates a specific stop code that can be used for troubleshooting. This code is typically displayed on the blue screen and will be in hexadecimal format (e.g., 0x000000EF) or descriptive text (e.g., CRITICAL_PROCESS_DIED).
An exhaustive list of Windows stop codes and why they happen
There are more than 250 stop codes associated with the occurrence of this error. Each error code suggests details as to what caused the device to crash and how it can be used to troubleshoot and resolve BSOD safely.
Below is a complete list of stop codes and their possible causes:
| Stop codes | Message shown | Cause of the error |
|---|---|---|
| 0x00000001 | APC_INDEX_MISMATCH | This error occurs primarily due to a mismatch in the sequence of calls to disable and re-enable asynchronous procedure calls (APCs) within a driver or file system. |
| 0x00000002 | DEVICE_QUEUE_NOT_BUSY | This error occurs when the system attempts to perform an operation on a device that is not currently busy, indicating a potential issue with the device driver or hardware. |
| 0x00000003 | INVALID_AFFINITY_SET | This error is caused by improper allocation of CPU cores to tasks, leading to a system-level conflict during process execution. |
| 0x00000004 | INVALID_DATA_ACCESS_TRAP | This error arises from an incorrect data access attempt by a program or driver, often due to corrupted or incompatible device drivers or system files. |
| 0x00000005 | INVALID_PROCESS_ATTACH_ATTEMPT | This error occurs when a thread attempts to attach to a process in an invalid state, typically due to improper management of process attachment calls in the kernel. |
| 0x00000006 | INVALID_PROCESS_DETACH_ATTEMPT | This error occurs when a thread tries to detach from a process in an invalid state, often due to improper use of kernel functions that manage process attachments. |
| 0x00000007 | INVALID_SOFTWARE_INTERRUPT | This error arises from issues related to device drivers or hardware malfunctions, where the system encounters an unexpected software interrupt. |
| 0x00000008 | IRQL_NOT_DISPATCH_LEVEL | This error occurs when a driver attempts to execute a function at an inappropriate interrupt request level (IRQL) , usually due to improper handling of kernel routines. |
| 0x00000009 | IRQL_NOT_GREATER_OR_EQUAL | This error occurs when a driver or software attempts to access a memory address at an invalid IRQL, often due to faulty or incompatible drivers. |
| 0x0000000A | IRQL_NOT_LESS_OR_EQUAL | This error occurs when a kernel-mode process or driver attempts to access a memory address without the necessary permissions, often due to corrupted or incompatible drivers. |
| 0x0000000B | NO_EXCEPTION_HANDLING_SUPPORT | This error occurs when the Windows operating system encounters a situation where it cannot properly handle exceptions due to missing or corrupt device drivers or system files. |
| 0x0000000C | MAXIMUM_WAIT_OBJECTS_EXCEEDED | This error occurs when a thread exceeds the maximum number of wait objects it can handle, typically due to improper use of the KeWaitForMultipleObjects or FsRtlCancellableWaitForMultipleObjects functions in the kernel. |
| 0x0000000D | MUTEX_LEVEL_NUMBER_VIOLATION | This error occurs when there is a violation in the expected sequence of mutex level operations, typically due to improper synchronization in kernel-mode drivers. |
| 0x0000000E | NO_USER_MODE_CONTEXT | This error occurs when the processor fails to find a valid user mode context while attempting to execute an instruction that requires it, typically due to issues in transitioning from kernel mode to user mode. |
| 0x0000000F | SPIN_LOCK_ALREADY_OWNED | This error occurs when a thread attempts to acquire a spin lock that it already owns, indicating improper synchronization in kernel-mode drivers. |
| 0x00000010 | SPIN_LOCK_NOT_OWNED | This error occurs when a thread attempts to release a spin lock that it does not own, typically due to improper synchronization in kernel-mode drivers. |
| 0x00000011 | THREAD_NOT_MUTEX_OWNER | This error occurs when a thread attempts to release a mutex that it does not own, typically due to improper synchronization in kernel-mode drivers. |
| 0x00000012 | TRAP_CAUSE_UNKNOWN | This error occurs when the system encounters an unknown exception, often due to unexpected interrupts or floating-point exceptions that cannot be identified. |
| 0x00000013 | EMPTY_THREAD_REAPER_LIST | This error occurs when the system's thread reaper attempts to clean up threads but finds no threads available to reap, indicating a potential issue with thread management. |
| 0x00000014 | CREATE_DELETE_LOCK_NOT_LOCKED | This error occurs when a thread attempts to release a create/delete lock that is not currently held, indicating improper synchronization in kernel-mode drivers. |
| 0x00000015 | LAST_CHANCE_CALLED_FROM_KMODE | This error occurs when a kernel-mode process encounters a critical failure that cannot be handled by the system's exception handler, often due to issues like faulty drivers or memory corruption. |
| 0x00000016 | CID_HANDLE_CREATION | This error occurs when the system encounters a failure during the creation of a handle, typically due to issues with kernel-mode drivers or resource management. |
| 0x00000017 | CID_HANDLE_DELETION | This error occurs when the operating system detects a problem related to the deletion of a handle, often due to outdated or incompatible device drivers. |
| 0x00000018 | REFERENCE_BY_POINTER | This error occurs when the reference count of an object is illegal for its current state, often due to improper handling by device drivers that either increment or decrement the reference count incorrectly. |
| 0x00000019 | BAD_POOL_HEADER | This error occurs when the Windows operating system encounters issues with memory allocation, often due to corrupted drivers, faulty RAM, or conflicts with newly installed hardware or software. |
| 0x0000001A | MEMORY_MANAGEMENT | This error occurs due to issues with the system's memory management processes, often caused by faulty RAM or corrupted system files. |
| 0x0000001B | PFN_SHARE_COUNT | This error occurs when the page frame number (PFN) share count is corrupted, typically due to issues with memory management in the system. |
| 0x0000001C | PFN_REFERENCE_COUNT | This error occurs when the reference count for a PFN becomes corrupted, often due to issues with memory management or improper handling by device drivers. |
| 0x0000001D | NO_SPIN_LOCK_AVAILABLE | This error occurs when the system is unable to allocate a spin lock, often due to insufficient resources or improper synchronization in kernel-mode drivers. |
| 0x0000001E | KMODE_EXCEPTION_NOT_HANDLED | This error occurs when a kernel-mode program generates an exception that the error handler fails to catch, often due to faulty device drivers or corrupted system files. |
| 0x0000001F | SHARED_RESOURCE_CONV_ERROR | This error occurs when there are conflicting access attempts to a shared resource by multiple users or processes, often due to improper credential management or multiple connections using different usernames. |
| 0x00000020 | KERNEL_APC_PENDING_DURING_EXIT | This error occurs when an APC is still pending while a thread is exiting, typically due to improper handling by device drivers. |
| 0x00000021 | QUOTA_UNDERFLOW | This error occurs when quota charges are mishandled, typically due to returning more quota to a block than was previously charged, often linked to driver issues or system misconfigurations. |
| 0x00000022 | FILE_SYSTEM | This error occurs when the system encounters a critical issue related to file system integrity, often due to corrupted system files or disk errors. |
| 0x00000023 | FAT_FILE_SYSTEM | This error occurs due to corruption in the File Allocation Table ( FAT), often caused by improper shutdowns, hardware issues, or malware infections. |
| 0x00000024 | NTFS_FILE_SYSTEM | This error occurs when the system encounters critical issues related to the NTFS file system, often due to corrupted system files, disk errors, or malware infections. |
| 0x00000025 | NPFS_FILE_SYSTEM | This error occurs when there are critical issues related to th e Named Pipe File System (NPFS), often due to corruption in the file system or conflicts with network drivers. |
| 0x00000026 | CDFS_FILE_SYSTEM | This error occurs when there are issues related to the CD file system , often caused by disk corruption or bad sectors on the hard drive. |
| 0x00000027 | RDR_FILE_SYSTEM | This error occurs due to issues with the Server Message Block ( SMB) protocol or problems with the non-paged pool memory, often linked to faulty hardware or incompatible drivers. |
| 0x00000028 | CORRUPT_ACCESS_TOKEN | This error occurs when an access token becomes invalid due to corruption during its generation or transmission, often linked to issues such as software bugs or network interruptions. |
| 0x00000029 | SECURITY_SYSTEM | This error occurs when the Windows security subsystem encounters a critical failure, often due to corrupted system files or issues with security settings. |
| 0x0000002A | INCONSISTENT_IRP | This error occurs when the system detects an inconsistency in the handling of I/O request packets (IRPs), often due to issues with device drivers or improper synchronization between drivers. |
| 0x0000002B | PANIC_STACK_SWITCH | This error occurs during a kernel panic when the system attempts to switch to a different stack context but encounters issues, often due to hardware failures or software bugs within the kernel. |
| 0x0000002C | PORT_DRIVER_INTERNAL | This error occurs when there is a failure in the port driver, often due to issues such as memory corruption or improper handling of I/O requests. |
| 0x0000002D | SCSI_DISK_DRIVER_INTERNAL | This error occurs when there is a failure within the SCSI disk driver, often due to issues such as memory corruption or improper handling of I/O requests. |
| 0x0000002E | DATA_BUS_ERROR | This error occurs due to hardware issues such as faulty RAM or corrupted hardware components that disrupt data transmission on the system's data bus. |
| 0x0000002F | INSTRUCTION_BUS_ERROR | This error occurs when the CPU attempts to fetch an instruction from a memory address that is invalid or inaccessible, often due to hardware failures or misconfigured memory settings. |
| 0x00000030 | SET_OF_INVALID_CONTEXT | This error occurs when the stack pointer in a trap frame contains an invalid value, often due to corruption in the context of a thread or process. |
| 0x00000031 | PHASE0_INITIALIZATION_FAILED | This error occurs when the system fails to initialize during the early startup phase, often due to corrupt system files, buggy drivers, or hardware malfunctions. |
| 0x00000032 | PHASE1_INITIALIZATION_FAILED | This error occurs during the system startup process when the initialization phase fails, often due to issues such as corrupted system files, incompatible drivers, or recent hardware changes. |
| 0x00000033 | UNEXPECTED_INITIALIZATION_CALL | This error occurs when a system component or driver calls an initialization routine at an inappropriate time, often due to conflicts between drivers or software components. |
| 0x00000034 | CACHE_MANAGER | This error occurs due to issues with the file system's cache manager, often caused by depletion of non-paged pool memory or corrupted system files. |
| 0x00000035 | NO_MORE_IRP_STACK_LOCATIONS | This error occurs when a higher-level driver attempts to call a lower-level driver but finds that there are no remaining stack locations in the IoCallDriver packet. |
| 0x00000036 | DEVICE_REFERENCE_COUNT_NOT_ZERO | This error occurs when a driver attempts to delete a device object that still has a positive reference count, indicating that there are outstanding references to the device. |
| 0x00000037 | FLOPPY_INTERNAL_ERROR | This error occurs when the system encounters an issue with the floppy disk drive, often due to hardware malfunctions, such as a faulty drive or connection problems. |
| 0x00000038 | SERIAL_DRIVER_INTERNAL | This error occurs when there is a failure within the serial driver, often due to issues such as corrupted drivers or improper initialization routines. |
| 0x00000039 | SYSTEM_EXIT_OWNED_MUTEX | This error occurs when a thread attempts to exit while still holding a mutex, which can lead to resource contention and system instability. |
| 0x0000003A | SYSTEM_UNWIND_PREVIOUS_USER | This error occurs when the system attempts to unwind the stack after a user-mode exception but encounters an inconsistency, often due to issues with exception handling across user and kernel mode. |
| 0x0000003B | SYSTEM_SERVICE_EXCEPTION | This error occurs when an exception is triggered while transitioning from non-privileged to privileged code, often due to memory corruption or accessing invalid pointers. |
| 0x0000003C | INTERRUPT_UNWIND_ATTEMPTED | This error occurs when the system attempts to unwind an interrupt context but encounters an inconsistency, often due to outdated or defective drivers. |
| 0x0000003D | INTERRUPT_EXCEPTION_NOT_HANDLED | This error occurs when the system encounters an unhandled exception during the processing of an interrupt, often due to outdated or corrupted drivers, hardware malfunctions, or incompatible software. |
| 0x0000003E | MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED | This error occurs when the operating system detects multiple processors that are asymmetric or incompatible, often due to mismatched CPU stepping or configurations. |
| 0x0000003F | NO_MORE_SYSTEM_PTES | This error occurs when the system runs out of available page table entries (PTEs) due to excessive memory allocation requests, often caused by a driver that is not releasing resources properly. |
| 0x00000040 | TARGET_MDL_TOO_SMALL | This error occurs when a driver improperly uses the IoBuildPartialMdl function and provides a targe t memory descriptor list (MDL) that is insufficient in size to map the requested range of addresses. |
| 0x00000041 | MUST_SUCCEED_POOL_EMPTY | This error occurs when a kernel-mode thread requests more memory from the must-succeed pool than is available, typically due to excessive memory allocation or leaks in drivers. |
| 0x00000042 | ATDISK_DRIVER_INTERNAL | This error occurs when there is an internal error within the Advanced Technology Attachment Packet Interface (ATAPI) disk driver, often due to issues such as corrupted driver files or conflicts with other hardware components. |
| 0x00000043 | NO_SUCH_PARTITION | This error occurs when the Grand Unified Bootloader (GRUB) cannot find the specified partition, often due to a misconfigured bootloader or deleted partitions in a dual-boot setup. |
| 0x00000044 | MULTIPLE_IRP_COMPLETE_REQUESTS | This error occurs when multiple drivers attempt to complete the same IRP, often due to improper driver management or bugs. |
| 0x00000045 | INSUFFICIENT_SYSTEM_MAP_REGS | This error occurs when the system runs out of available map registers needed for Direct Memory Access ( DMA) operations, typically due to excessive memory allocation requests or insufficient system resources. |
| 0x00000046 | DEREF_UNKNOWN_LOGON_SESSION | This error occurs when the system attempts to dereference a logon session that does not exist, often due to issues with user accounts or corrupted session information. |
| 0x00000047 | REF_UNKNOWN_LOGON_SESSION | This error occurs when the system attempts to reference a logon session that does not exist, often due to improper session management or corruption in user account data. |
| 0x00000048 | CANCEL_STATE_IN_COMPLETED_IRP | This error occurs when a driver attempts to cancel an IRP that has already been completed, which can lead to inconsistencies in resource management. |
| 0x00000049 | PAGE_FAULT_WITH_INTERRUPTS_OFF | This error occurs when the system encounters a page fault while interrupts are disabled, typically due to a driver or kernel-mode code accessing memory that is not currently available. |
| 0x0000004A | IRQL_GT_ZERO_AT_SYSTEM_SERVICE | This error occurs when a thread attempts to return to user mode from a system call while it s IRQL is still above PASSIVE_LEVEL, indicating improper handling of system calls. |
| 0x0000004B | STREAMS_INTERNAL_ERROR | This error occurs when there is an issue within the STREAMS driver framework, often due to improper handling of message processing or resource management in the driver. |
| 0x0000004C | FATAL_UNHANDLED_HARD_ERROR | This error occurs when the system encounters a critical hardware error that it cannot process, often due to issues like faulty hardware components or severe memory corruption. |
| 0x0000004D | NO_PAGES_AVAILABLE | This error occurs when the system runs out of free memory pages, preventing it from fulfilling memory allocation requests. |
| 0x0000004E | PFN_LIST_CORRUPT | This error occurs when the PFN list, which tracks physical memory pages, becomes corrupted, often due to issues like faulty RAM, damaged hard drives, or software conflicts. |
| 0x0000004F | NDIS_INTERNAL_ERROR | This error occurs when there is a critical failure within the Network Driver Interface Specification ( NDIS) framework, often due to corrupted network drivers, hardware conflicts, or memory issues. |
| 0x00000050 | PAGE_FAULT_IN_NONPAGED_AREA | This error occurs when the operating system attempts to access memory that should be permanently resident in RAM but is not available, often due to driver issues, faulty hardware, or corrupted system files. |
| 0x00000051 | REGISTRY_ERROR | This error occurs when there is a critical issue with the Windows Registry, often due to corrupted or missing registry files, hardware problems, or malware infections. |
| 0x00000052 | MAILSLOT_FILE_SYSTEM | This error occurs when there is a critical issue with the mailslot driver, often due to improper handling of interprocess communication or resource management by applications. |
| 0x00000053 | NO_BOOT_DEVICE | This error occurs when the BIOS cannot locate a valid bootable device, often due to incorrect boot order settings, corrupted boot files, or a damaged master boot record ( MBR). |
| 0x00000054 | LM_SERVER_INTERNAL_ERROR | This error occurs when there is a critical issue with the Local Manager (LM) server, often due to misconfigurations in server settings or problems with network connectivity. |
| 0x00000055 | DATA_COHERENCY_EXCEPTION | This error occurs when the system detects inconsistencies in data across different caches or memory locations, often due to improper handling of shared data in multi-core or multi-processor environments. |
| 0x00000056 | INSTRUCTION_COHERENCY_EXCEPTION | This error occurs in multiprocessor systems when there is a failure in maintaining consistency among instruction caches. |
| 0x00000057 | XNS_INTERNAL_ERROR | This error indicates a problem with the XNS (Xerox Network Systems) protocol stack. |
| 0x00000058 | FTDISK_INTERNAL_ERROR | This error occurs when the system is booted from the incorrect copy of a mirrored partition, leading to inconsistencies in the disk management subsystem. |
| 0x00000059 | PINBALL_FILE_SYSTEM | This error indicates a problem within the Pinball file system, often triggered by the depletion of non-paged pool memory. |
| 0x0000005A | CRITICAL_SERVICE_FAILED | This error is primarily caused by issues such as corrupted or missing device drivers and incompatibility with newly installed hardware or software. |
| 0x0000005B | SET_ENV_VAR_FAILED | This error occurs when there is an issue with setting environment variables in the operating system, often due to incorrect syntax or permissions. |
| 0x0000005C | HAL_INITIALIZATION_FAILED | This error usually occurs due to corrupted, outdated, or improperly configured device drivers, which can prevent the hardware abstraction layer (HAL) from initializing correctly. |
| 0x0000005D | UNSUPPORTED_PROCESSOR | This error occurs when Windows detects that the installed processor is not compatible with the operating system, often due to outdated BIOS or microcode that fails to meet the latest system requirements. |
| 0x0000005E | OBJECT_INITIALIZATION_FAILED | This error occurs when an object fails to initialize properly, often due to incorrect parameters or configurations being passed during the creation process. |
| 0x0000005F | SECURITY_INITIALIZATION_FAILED | This error occurs due to issues with the initialization of security components or services within an operating system or application. |
| 0x00000060 | PROCESS_INITIALIZATION_FAILED | This error arises when there is a failure in the initialization of system processes during boot, often due to issues with the Bootcat.cache file or corruption in critical system files like NTDLL.DLL. |
| 0x00000061 | HAL1_INITIALIZATION_FAILED | This error occurs due to issues related to corrupted or outdated drivers, which can prevent the HAL from initializing properly. |
| 0x00000062 | OBJECT1_INITIALIZATION_FAILED | This error is primarily caused by issues related to faulty hardware or incompatible drivers, which can prevent the operating system from properly initializing system objects. |
| 0x00000063 | SECURITY1_INITIALIZATION_FAILED | This error generally occurs due to corrupted system files or incompatible drivers that prevent the security subsystem from initializing properly during the boot process. |
| 0x00000064 | SYMBOLIC_INITIALIZATION_FAILED | This error occurs when the Windows operating system fails to initialize symbolic links due to issues such as corrupted system files or driver conflicts. |
| 0x00000065 | MEMORY1_INITIALIZATION_FAILED | This error occurs when the Windows operating system encounters severe issues with system memory initialization during startup. |
| 0x00000066 | CACHE_INITIALIZATION_FAILED | This error occurs when the system fails to initialize the cache subsystem due to corrupted cache files or issues with the Bootcat.cache file, which can disrupt the boot process. |
| 0x00000067 | CONFIG_INITIALIZATION_FAILED | This error usually arises due to issues with the Boot Configuration Data (BCD) or corrupted system files, which prevent the operating system from properly initializing during startup. |
| 0x00000068 | FILE_INITIALIZATION_FAILED | This error occurs when the operating system encounters issues with initializing file system components, often due to corrupted system files or incompatible drivers. |
| 0x00000069 | IO1_INITIALIZATION_FAILED | This error typically occurs when the operating system fails to initialize the input/output (I/O) system, often due to corrupted system files or driver conflicts. |
| 0x0000006A | LPC_INITIALIZATION_FAILED | This error occurs when the Local Procedure Call (LPC) subsystem fails to initialize due to issues such as corrupted system files or driver conflicts. |
| 0x0000006B | PROCESS1_INITIALIZATION_FAILED | This error occurs due to corrupted system files, such as the Bootcat.cache file or the NTDLL.dll file, which can prevent the operating system from booting properly. |
| 0x0000006C | REFMON_INITIALIZATION_FAILED | This error occurs due to issues with the memory management system or conflicts arising from changes in system settings, such as virtual memory adjustments. |
| 0x0000006D | SESSION1_INITIALIZATION_FAILED | This error arises from memory conflicts or bad sectors on the hard drive, preventing the system from booting successfully. |
| 0x0000006E | SESSION2_INITIALIZATION_FAILED | This error occurs when the Windows operating system fails to initialize a session due to issues such as corrupted system files or incompatible drivers. |
| 0x0000006F | SESSION3_INITIALIZATION_FAILED | This error occurs due to a faulty system file or an interrupted Windows installation process, which prevents the operating system from initializing properly. |
| 0x00000070 | SESSION4_INITIALIZATION_FAILED | This error indicates that the initialization of the Windows operating system failed. |
| 0x00000071 | SESSION5_INITIALIZATION_FAILED | This error occurs due to issues such as corrupted system files, bad sectors on the hard drive, or incompatible drivers that prevent the Windows operating system from initializing properly. |
| 0x00000072 | ASSIGN_DRIVE_LETTERS_FAILED | This error occurs when the Windows operating system is unable to assign drive letters to partitions, often due to corrupted system files or incompatible drivers that prevent proper recognition in disk management . |
| 0x00000073 | CONFIG_LIST_FAILED | This error occurs when the Windows operating system is unable to link a top-level registry key, often due to insufficient disk space or failed memory allocation. |
| 0x00000074 | BAD_SYSTEM_CONFIG_INFO | This error occurs when the Windows operating system encounters issues with the SYSTEM registry hive, often due to corrupted files, incorrect configurations, or problems with the BCD. |
| 0x00000075 | CANNOT_WRITE_CONFIGURATION | This error occurs when the system is unable to write to a configuration file, often due to insufficient permissions or a read-only attribute set on the file. |
| 0x00000076 | PROCESS_HAS_LOCKED_PAGES | This error occurs when a driver fails to release memory pages that it has locked after an I/O operation, or attempts to unlock pages that are already unlocked. |
| 0x00000077 | KERNEL_STACK_INPAGE_ERROR | This error occurs when the operating system fails to read a requested page of kernel data from the paging file into memory, often due to defective storage hardware, failing RAM, or corrupted system files. |
| 0x00000078 | PHASE0_EXCEPTION | This error occurs when an unexpected break is encountered during the HAL initialization, often due to misconfigured boot settings. |
| 0x00000079 | MISMATCHED_HAL | This error occurs when an unexpected break is encountered during the HAL initialization, often due to misconfigured boot settings. |
| 0x0000007A | KERNEL_DATA_INPAGE_ERROR | This error occurs when the operating system fails to read a requested page of kernel data from the paging file into memory, often due to defective storage hardware or failing RAM. |
| 0x0000007B | INACCESSIBLE_BOOT_DEVICE | This error occurs when the Windows operating system cannot access the boot device, often due to a failed or unreadable storage device or corrupted drivers that prevent proper initialization. |
| 0x0000007C | BUGCODE_NDIS_DRIVER | This error indicates a problem with network drivers, often stemming from issues with the NDIS miniport driver. |
| 0x0000007D | INSTALL_MORE_MEMORY | This error arises when the system runs out of available memory resources during an installation or setup process, often due to insufficient RAM or memory allocation limits. |
| 0x0000007E | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED | This error occurs when a system thread generates an exception that the error handler fails to catch, often due to incompatible or corrupted drivers. |
| 0x0000007F | UNEXPECTED_KERNEL_MODE_TRAP | This error occurs when the CPU generates a trap that the Windows kernel fails to catch, often due to hardware failures, particularly with faulty or mismatched memory. |
| 0x00000080 | NMI_HARDWARE_FAILURE | This error occurs when a non-maskable interrupt (NMI) is triggered due to critical hardware issues, such as memory corruption, overheating, or failure of system components. |
| 0x00000081 | SPIN_LOCK_INIT_FAILURE | This error occurs when the initialization of a spin lock fails due to issues such as insufficient memory or incorrect configurations that prevent proper setup. |
| 0x00000082 | DFS_FILE_SYSTEM | This error occurs due to issues with the distributed file system (DFS) configuration, often caused by corrupted system files or incompatible drivers that disrupt the normal operation of the file system. |
| 0x00000083 | OFS_FILE_SYSTEM | This error arises from issues related to the Open File System, often due to corrupted file system structures or disk errors that prevent proper access to files. |
| 0x00000084 | RECOM_DRIVER | This error occurs due to issues with a driver that fails to load correctly, often stemming from corrupted files or incompatible drivers. |
| 0x00000085 | SETUP_FAILURE | This error occurs due to issues such as insufficient memory, corrupted system files, or a failing hard disk that prevent successful setup. |
| 0x0000008B | MBR_CHECKSUM_MISMATCH | This error occurs when the checksum of th e MBR does not match the expected value, often due to corrupted boot sector data or improper modifications during partitioning. |
| 0x0000008E | KERNEL_MODE_EXCEPTION_NOT_HANDLED | This error occurs when a kernel-mode program generates an exception that the error handler fails to catch, often due to faulty device drivers or hardware issues. |
| 0x0000008F | PP0_INITIALIZATION_FAILED | This error occurs during the initialization phase of the Windows operating system, often due to corrupted system files or incompatible drivers that prevent successful startup. |
| 0x00000090 | PP1_INITIALIZATION_FAILED | This error occurs when the plug and play (PnP) manager fails to initialize during the kernel's Phase 1 setup, often due to corrupted system files or incompatible drivers. |
| 0x00000091 | WIN32K_INIT_OR_RIT_FAILURE | This error occurs when the Windows kernel encounters a failure during the initialization of the Win32k subsystem, often due to corrupted system files or incompatible drivers. |
| 0x00000092 | UP_DRIVER_ON_MP_SYSTEM | This error occurs when a uniprocessor-only driver is loaded on a multiprocessor system, indicating a compatibility issue that can lead to instability. |
| 0x00000093 | INVALID_KERNEL_HANDLE | This error occurs when kernel code attempts to close an invalid or protected handle, often due to corrupted drivers or system files that lead to improper memory management. |
| 0x00000094 | KERNEL_STACK_LOCKED_AT_EXIT | This error occurs when a thread exits while its kernel stack is marked as non-swappable, typically due to issues with corrupted drivers or system files that disrupt proper memory management. |
| 0x00000095 | PNP_INTERNAL_ERROR | This error occurs occurs when the PnP manager encounters a critical error, typically due to corrupted drivers or hardware failures that disrupt device recognition. |
| 0x00000096 | INVALID_WORK_QUEUE_ITEM | This error occurs when the system encounters an invalid work queue item, often due to corrupted drivers or hardware issues that disrupt normal processing. |
| 0x00000097 | BOUND_IMAGE_UNSUPPORTED | This error occurs when a bound image format is not supported by the operating system, typically due to incompatible or outdated drivers that fail to recognize the image format. |
| 0x00000098 | END_OF_NT_EVALUATION_PERIOD | This error occurs when the trial period for the Windows operating system has expired, indicating that the evaluation version can no longer be used without activation. |
| 0x00000099 | INVALID_REGION_OR_SEGMENT | This error occurs when the system attempts to initialize a region or segment with invalid parameters, often due to corrupted system files or driver compatibility issues. |
| 0x0000009A | SYSTEM_LICENSE_VIOLATION | This error occurs when the Windows operating system detects a violation of its software license agreement, often due to attempts to alter product licensing or evaluation periods. |
| 0x0000009B | UDFS_FILE_SYSTEM | This error occurs when there is a problem with the Universal Disk Format ( UDF) file system, often due to disk corruption or bad sectors on the storage medium. |
| 0x0000009C | MACHINE_CHECK_EXCEPTION | This error occurs when the Windows operating system detects a serious hardware issue, often related to overheating, faulty components, or driver incompatibilities. |
| 0x0000009E | USER_MODE_HEALTH_MONITOR | This error occurs when critical user-mode components fail to pass a health check, typically due to corrupted drivers, hardware malfunctions, or software conflicts. |
| 0x0000009F | DRIVER_POWER_STATE_FAILURE | This error occurs when a device driver enters an invalid or inconsistent power state, often during transitions to or from sleep mode. |
| 0x000000A0 | INTERNAL_POWER_ERROR | This error occurs when the power policy manager experiences a fatal error, often due to issues such as corrupted system files, outdated drivers, or hardware malfunctions. |
| 0x000000A1 | PCI_BUS_DRIVER_INTERNAL | This error occurs when the Peripheral Component Interconnect (PCI) B us driver detects inconsistencies in its internal structures, preventing it from continuing operation. |
| 0x000000A2 | MEMORY_IMAGE_CORRUPT | This error occurs when the system detects corruption in the memory image, often caused by faulty RAM, hardware issues, or corrupted drivers that disrupt normal memory operations. |
| 0x000000A3 | ACPI_DRIVER_INTERNAL | This error occurs when the Advanced Configuration and Power Interface (ACPI) d river detects a severe internal inconsistency, often due to BIOS errors, corrupted drivers, or incompatibilities with newly installed hardware. |
| 0x000000A4 | CNSS_FILE_SYSTEM_FILTER | This error occurs when there is a problem with the file system filter driver, often related to corrupted drivers or incompatibilities with the installed software. |
| 0x000000A5 | ACPI_BIOS_ERROR | This error occurs when the ACPI BIOS is not fully compliant with the ACPI specification, leading to critical failures in power management and device configuration. |
| 0x000000A7 | BAD_EXHANDLE | This error occurs when the kernel-mode handle table detects an inconsistent handle table entry, indicating a serious issue with handle management in the operating system. |
| 0x000000AB | SESSION_HAS_VALID_POOL_ON_EXIT | This error occurs when a session attempts to exit while still having valid memory pools allocated, indicating improper memory management during session termination. |
| 0x000000AC | HAL_MEMORY_ALLOCATION | This error occurs when the HAL fails to allocate sufficient memory for its operations, often due to insufficient system memory or memory corruption. |
| 0x000000AD | VIDEO_DRIVER_DEBUG_REPORT_REQUEST | This error occurs when the graphics driver encounters a critical issue and requests a debug report, typically due to driver corruption or incompatibility with the operating system. |
| 0x000000B4 | VIDEO_DRIVER_INIT_FAILURE | This error occurs when the system fails to initialize the graphics driver, preventing Windows from entering graphics mode, typically due to missing or corrupted display drivers. |
| 0x000000B8 | ATTEMPTED_SWITCH_FROM_DPC | This error occurs when a Deferred Procedure Call (DPC) routine attempts to perform an illegal operation, such as switching to a lower priority thread while still executing at a hig h IRQL. |
| 0x000000B9 | CHIPSET_DETECTED_ERROR | This error occurs when the system encounters issues related to the chipset drivers, often due to corrupted or incompatible driver installations. |
| 0x000000BA | SESSION_HAS_VALID_VIEWS_ON_EXIT | This error occurs when a session driver fails to unmap its mapped views before the session unloads, indicating a potential bug in system drivers like win32k.sys or video drivers. |
| 0x000000BB | NETWORK_BOOT_INITIALIZATION_FAILED | This error occurs when Windows fails to boot from a network source due to a critical failure during I/O initialization, often related to network configuration issues or driver problems. |
| 0x000000BC | NETWORK_BOOT_DUPLICATE_ADDRESS | This error occurs when multiple devices on the network attempt to use the same IP address, leading to conflicts that prevent successful network booting. |
| 0x000000BE | ATTEMPTED_WRITE_TO_READONLY_MEMORY | This error occurs when a driver or software attempts to write data to a memory segment that is marked as read-only, typically due to faulty or incompatible device drivers. |
| 0x000000BF | MUTEX_ALREADY_OWNED | This error occurs when a thread attempts to acquire a mutex that it already owns, indicating improper management of mutex locks. |
| 0x000000C1 | SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION | This error occurs when the system detects memory corruption within the special pool allocated for drivers, often due to faulty or incompatible device drivers. |
| 0x000000C2 | BAD_POOL_CALLER | This error occurs when a thread in the Windows operating system makes an invalid request to the memory pool, often due to corrupted drivers, memory corruption, or misconfigured system settings. |
| 0x000000C4 | DRIVER_VERIFIER_DETECTED_VIOLATION | This error occurs when the Driver Verifier detects illegal actions or function calls made by device drivers, indicating potential issues with driver integrity or stability. |
| 0x000000C5 | DRIVER_CORRUPTED_EXPOOL | This error occurs when the system detects corruption in the memory pool, typically caused by a faulty or incompatible device driver that improperly manages memory allocations. |
| 0x000000C6 | DRIVER_CAUGHT_MODIFYING_FREED_POOL | This error occurs when a driver attempts to modify memory that has already been freed, indicating improper memory management practices. |
| 0x000000C7 | TIMER_OR_DPC_INVALID | This error occurs when the system detects that a kernel timer or a DPC is improperly located in memory, which is not permitted. |
| 0x000000C8 | IRQL_UNEXPECTED_VALUE | This error occurs when a driver or kernel-mode process uses an invalid IRQL that is not permitted, typically indicating a serious issue with the system's handling of interrupts. |
| 0x000000C9 | DRIVER_VERIFIER_IOMANAGER_VIOLATION | This error occurs when the Driver Verifier detects a violation related to I/O operations, typically due to improper handling of I/O requests by a device driver. |
| 0x000000CA | PNP_DETECTED_FATAL_ERROR | This error occurs when the PnP manager encounters a critical error, typically due to corrupted, missing, or incompatible drivers for PnP devices. |
| 0x000000CB | DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS | This error occurs when a driver fails to properly release memory pages that it previously locked during an I/O operation, indicating a cleanup issue. |
| 0x000000CC | PAGE_FAULT_IN_FREED_SPECIAL_POOL | This error occurs when the system attempts to access memory that has already been freed, indicating a serious issue with memory management, often related to drivers. |
| 0x000000CD | PAGE_FAULT_BEYOND_END_OF_ALLOCATION | This error occurs when a process attempts to access memory beyond the allocated range, indicating a serious issue with memory management. |
| 0x000000CE | DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS | This error occurs when a driver is unloaded from memory while there are still pending operations that have not been completed, indicating a failure in proper resource management. |
| 0x000000CF | TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE | This error occurs when a terminal server driver attempts to access memory incorrectly, often due to faulty or incompatible device drivers. |
| 0x000000D0 | DRIVER_CORRUPTED_MMPOOL | This error occurs when a driver corrupts the memory pool used by the operating system, typically due to faulty or incompatible device drivers. |
| 0x000000D1 | DRIVER_IRQL_NOT_LESS_OR_EQUAL | This error occurs when a kernel-mode driver attempts to access pageable memory at a higher IRQL than it is allowed, indicating a serious memory management issue. |
| 0x000000D2 | BUGCODE_ID_DRIVER | This error occurs when there is a problem with a NDIS driver, often due to corrupted, outdated, or incompatible device drivers. |
| 0x000000D3 | DRIVER_PORTION_MUST_BE_NONPAGED | This error occurs when a driver attempts to access a portion of its code or data that must reside in the non-paged pool but is instead located in pageable memory. |
| 0x000000D4 | SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD | This error occurs when a driver fails to cancel pending operations before being unloaded, leading to memory access violations at an elevated IRQL. |
| 0x000000D5 | DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL | This error occurs when a driver attempts to access memory that has already been freed, indicating improper memory management. |
| 0x000000D6 | DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION | This error occurs when a driver attempts to access memory beyond the allocated range, indicating a bug in the driver's code that may involve buffer overruns or memory corruption. |
| 0x000000D7 | DRIVER_UNMAPPING_INVALID_VIEW | This error occurs when a driver attempts to unmap a virtual address that has not been mapped, indicating a serious issue with memory management. |
| 0x000000D8 | DRIVER_USED_EXCESSIVE_PTES | This error occurs when a driver consumes an excessive number o f PTEs , exceeding the system's available limit, which can lead to memory management issues. |
| 0x000000D9 | LOCKED_PAGES_TRACKER_CORRUPTION | This error occurs when the system detects corruption in the data structures that track locked memory pages, typically due to faulty or improperly written drivers. |
| 0x000000DA | SYSTEM_PTE_MISUSE | This error occurs when a PTE routine is improperly utilized, typically due to corrupted system files or incompatible drivers. |
| 0x000000DB | DRIVER_CORRUPTED_SYSPTES | This error occurs when a driver improperly manipulates system PTEs, leading to memory corruption and instability. |
| 0x000000DC | DRIVER_INVALID_STACK_ACCESS | This error occurs when a driver attempts to access a stack address that lies below the stack pointer of the thread, indicating a serious issue with memory management. |
| 0x000000DE | POOL_CORRUPTION_IN_FILE_AREA | This error occurs when a driver corrupts the pool memory used for file storage, often due to faulty, outdated, or incompatible drivers or software. |
| 0x000000DF | IMPERSONATING_WORKER_THREAD | This error occurs when a worker thread is found to be impersonating a client, leading to security and resource management issues if not handled properly. |
| 0x000000E0 | ACPI_BIOS_FATAL_ERROR | This error occurs when the ACPI BIOS is not compliant with the ACPI specification, often due to outdated or incompatible BIOS firmware. |
| 0x000000E1 | WORKER_THREAD_RETURNED_AT_BAD_IRQL | This error occurs when a worker thread completes and returns at an incorrect IRQL, typically higher than DISPATCH_LEVEL, which violates the operating system's execution rules. |
| 0x000000E2 | MANUALLY_INITIATED_CRASH | This error occurs when a user deliberately triggers a crash dump, typically by using the keyboard shortcut Ctrl + Scroll Lock after enabling the feature in the system's registry. |
| 0x000000E3 | RESOURCE_NOT_OWNED | This error occurs when a thread attempts to release a resource that it does not own, indicating a violation of synchronization rules in the operating system. |
| 0x000000E4 | WORKER_INVALID | This error occurs when the system detects an invalid state in a worker thread, typically due to memory that should not contain an executive work item being improperly accessed or freed. |
| 0x000000E6 | DRIVER_VERIFIER_DMA_VIOLATION | This error occurs when a driver attempts an illegal DMA operation while being monitored by the Driver Verifier, often due to corrupted or incompatible drivers. |
| 0x000000E7 | INVALID_FLOATING_POINT_STATE | This error occurs when a thread's saved floating-point state is found to be invalid during restoration, indicating issues with the context flags or thread ownership. |
| 0x000000E8 | INVALID_CANCEL_OF_FILE_OPEN | This error occurs when a file operation is cancelled improperly, typically due to a conflict in the file handling process or an attempt to cancel an operation that has already completed. |
| 0x000000E9 | ACTIVE_EX_WORKER_THREAD_TERMINATION | This error occurs when an active executive worker thread is unexpectedly terminated, often due to faulty drivers or system resource management issues. |
| 0x000000EA | THREAD_STUCK_IN_DEVICE_DRIVER | This error occurs when a device driver is caught in an infinite loop while waiting for hardware to enter an idle state, indicating a malfunction or bug within the driver. |
| 0x000000EB | DIRTY_MAPPED_PAGES_CONGESTION | This error occurs when the system has too many dirty pages that cannot be written to disk, often due to driver failures in handling memory management properly. |
| 0x000000EC | SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT | This error occurs when a session attempts to exit while still having valid allocations in the special pool, indicating potential memory management issues. |
| 0x000000ED | UNMOUNTABLE_BOOT_VOLUME | This error occurs when the operating system cannot access the boot partition, often due to file system corruption, damaged hard drive sectors, or issues with the MBR. |
| 0x000000EF | CRITICAL_PROCESS_DIED | This error occurs when a critical system process unexpectedly terminates, often due to corrupted system files, driver issues, or hardware malfunctions. |
| 0x000000F1 | SCSI_VERIFIER_DETECTED_VIOLATION | This error occurs when the SCSI verifier detects a violation in the operation of SCSI devices or their drivers, indicating improper handling or communication issues. |
| 0x000000F3 | DISORDERLY_SHUTDOWN | This error occurs when Windows is unable to shut down properly due to a lack of available memory, often caused by applications not terminating or drivers not unloading correctly. |
| 0x000000F4 | CRITICAL_OBJECT_TERMINATION | This error occurs when a crucial process or thread essential for system operation unexpectedly terminates, often due to faulty hardware, corrupted system files, or driver conflicts. |
| 0x000000F5 | FLTMGR_FILE_SYSTEM | This error occurs due to issues with the Filter Manager (fltmgr.sys), which manages file system filter drivers, often caused by corrupted system files, outdated drivers, or hardware malfunctions. |
| 0x000000F6 | PCI_VERIFIER_DETECTED_VIOLATION | This error occurs when the PCI driver detects an error in a device or BIOS being verified, often due to improper handling of PCI device operations. |
| 0x000000F7 | DRIVER_OVERRAN_STACK_BUFFER | This error occurs when a device driver writes more data to a stack-based buffer than it can hold, potentially overwriting critical memory areas and leading to system instability. |
| 0x000000F8 | RAMDISK_BOOT_INITIALIZATION_FAILED | This error occurs when the system fails to initialize the RAM disk during the boot process, often due to corrupted files, incompatible drivers, or insufficient memory allocation. |
| 0x000000F9 | DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN | This error occurs when a driver returns a STATUS_REPARSE response to an IRP_MJ_CREATE request without trailing names, indicating improper handling of reparse points. |
| 0x000000FA | HTTP_DRIVER_CORRUPTED | This error occurs when the HTTP kernel driver (HTTP.sys) enters a corrupted state, often due to corrupted system files, memory issues, or faulty drivers. |
| 0x000000FC | ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY | This error occurs when the system attempts to execute code from a memory region that is marked as non-executable. |
| 0x000000FD | DIRTY_NOWRITE_PAGES_CONGESTION | This error occurs when the system runs out of free memory pages needed for operations, often due to modified non-writable pages not being written out properly. |
| 0x000000FE | BUGCODE_USB_DRIVER | This error typically arises from issues related to outdated or incompatible USB drivers, leading to system instability and crashes. |
| 0x000000FF | RESERVE_QUEUE_OVERFLOW | This error occurs when the system attempts to insert a new item into a reserve queue that has reached its maximum capacity, leading to an overflow condition. |
| 0x00000100 | LOADER_BLOCK_MISMATCH | This error occurs when there is an invalid loader block or a mismatch between the loader block and the system being loaded, which prevents proper booting. |
| 0x00000101 | CLOCK_WATCHDOG_TIMEOUT | This error occurs when a clock interrupt on a secondary processor is not received within the expected time frame, indicating that the processor is unresponsive. |
| 0x00000103 | MUP_FILE_SYSTEM | This error occurs when the Multiple UNC Provider (MUP) encounters invalid or unexpected data, preventing it from processing remote file system requests to a network redirector. |
| 0x00000104 | AGP_INVALID_ACCESS | This error occurs when there is an attempt to access a method or resource that is not permitted in the context of the Accelerated Graphics Port (AGP), often due to changes in method signatures or access modifiers after an upgrade. |
| 0x00000105 | AGP_GART_CORRUPTION | This error typically arises from corruption in the graphics address remapping table (GART), which can occur due to faulty hardware, such as a malfunctioning graphics card or memory issues. |
| 0x00000106 | AGP_ILLEGALLY_REPROGRAMMED | This error occurs when the AGP hardware is reprogrammed by an unauthorized agent, indicating potential tampering or corruption in the graphics driver or system configuration. |
| 0x00000108 | THIRD_PARTY_FILE_SYSTEM_FAILURE | This error occurs when there is an unrecoverable issue in a third-party file system or file system filter, often due to disk corruption or bad sectors on the hard drive. |
| 0x00000109 | CRITICAL_STRUCTURE_CORRUPTION | This error occurs when the Windows kernel detects corruption in critical kernel code or data, which can result from faulty hardware, such as failing RAM, or from drivers that inadvertently modify essential system structures. |
| 0x0000010A | APP_TAGGING_INITIALIZATION_FAILED | This error occurs when the application tagging subsystem fails to initialize properly, often due to issues with system resources or conflicts with existing applications. |
| 0x0000010C | FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION | This error occurs when there is an issue with the allocation or management of extra create parameters (ECPs) in the file system, often due to insufficient resources or corruption in the ECP structures. |
| 0x0000010D | WDF_VIOLATION | This error occurs when the Windows Driver Framework (WDF) detects a critical issue within a framework-based driver, typically due to invalid memory access or resource mismanagement. |
| 0x0000010E | VIDEO_MEMORY_MANAGEMENT_INTERNAL | This error occurs when the video memory manager encounters a critical issue that it cannot recover from, often due to faulty or outdated graphics drivers. |
| 0x0000010F | RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED | This error occurs when the resource manager encounters an unexpected condition that it cannot handle, often due to issues with resource allocation or management in the system. |
| 0x00000111 | RECURSIVE_NMI | This error occurs when a NMI is triggered while another NMI is still being processed, indicating a critical failure in the system management interrupt (SMI) code. |
| 0x00000112 | MSRPC_STATE_VIOLATION | This error occurs when the remote procedure call (RPC) service encounters an unexpected state, often due to asynchronous RPC calls accessing incorrectly reallocated memory addresses. |
| 0x00000113 | VIDEO_DXGKRNL_FATAL_ERROR | This error occurs when the DirectX graphics kernel subsystem detects a critical violation, often due to outdated or incompatible graphics drivers, corrupted system files, or hardware conflicts. |
| 0x00000114 | VIDEO_SHADOW_DRIVER_FATAL_ERROR | This error occurs when the shadow driver detects a critical violation, often due to issues with outdated, corrupt, or buggy graphics drivers. |
| 0x00000115 | AGP_INTERNAL | This error occurs when the Accelerated Graphics Port (AGP) detects a critical issue with the installed video device or driver, often resulting from outdated, corrupted, or incompatible drivers. |
| 0x00000116 | VIDEO_TDR_ ERROR | This error occurs when the graphics driver fails to respond within a designated timeout period, prompting the operating system to attempt a reset that ultimately fails. |
| 0x00000117 | VIDEO_TDR_TIMEOUT_DETECTED | This error occurs when the display driver fails to respond within the expected timeout period, typically due to issues with the graphics driver or hardware. |
| 0x00000119 | VIDEO_SCHEDULER_INTERNAL_ERROR | This error occurs when the video scheduler detects a fatal violation, often due to issues with outdated or incompatible graphics drivers, faulty hardware, or corrupted system files. |
| 0x0000011A | EM_INITIALIZATION_FAILURE | This error typically occurs when the system fails to initialize the Electro-Magnetic Interference (EMI) management subsystem, often due to issues with hardware configuration or compatibility. |
| 0x0000011B | DRIVER_RETURNED_HOLDING_CANCEL_LOCK | This error occurs when a device driver fails to release a cancel lock, which is necessary for managing pending operations in the system. |
| 0x0000011C | ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE | This error occurs when an application tries to write data to a protected storage area managed by the Configuration Manager (CM), which is typically restricted to prevent unauthorized modifications. |
| 0x0000011D | EVENT_TRACING_FATAL_ERROR | This error occurs when the Event Tracing subsystem encounters an unexpected fatal error, often due to corrupt or missing device drivers or system files. |
| 0x00000121 | DRIVER_VIOLATION | This error occurs when a device driver violates the rules set by the operating system, often due to improper handling of memory or resources. |
| 0x00000122 | WHEA_INTERNAL_ERROR | This error occurs when the Windows Hardware Error Architecture (WHEA) encounters a critical internal error, often due to issues with hardware drivers or firmware implementations. |
| 0x00000124 | WHEA_UNCORRECTABLE_ERROR | This error occurs when the WHEA detects a fatal hardware issue that the system cannot recover from, often related to components like the CPU, RAM, or hard drives. |
| 0x00000127 | PAGE_NOT_ZERO | This error occurs when the Windows memory manager detects that a page of memory, expected to be zeroed, contains unexpected data, indicating potential memory corruption. |
| 0x0000012B | FAULTY_HARDWARE_CORRUPTED_PAGE | This error occurs when the Windows memory manager detects corruption in memory that can only be caused by hardware issues, such as defective RAM or improper device driver operations. |
| 0x0000012C | EXFAT_FILE_SYSTEM | This error occurs when the operating system encounters a critical issue with the exFAT file system, often due to corrupted file structures or incompatible hardware. |
| 0x00000133 | DPC_WATCHDOG_VIOLATION | This error occurs when the system's watchdog detects that a DPC has exceeded its allotted time, often due to faulty or outdated device drivers, particularly for SSDs and graphics cards. |
| 0x00000138 | GPIO_CONTROLLER_DRIVER_ERROR | This error occurs when the General Purpose Input/Output (GPIO) class extension driver encounters a fatal error, often due to issues with hardware configuration or driver compatibility. |
| 0x00000139 | KERNEL_SECURITY_CHECK_FAILURE | This error occurs when the Windows kernel detects corruption in critical data structures, often due to faulty drivers, hardware issues, or corrupted system files. |
| 0x00000144 | BUGCODE_USB3_DRIVER | This error occurs when the USB 3.0 driver encounters a critical issue, often due to outdated or corrupted drivers that fail to function properly. |
| 0x0000014B | SOC_SUBSYSTEM_FAILURE | This error indicates an unrecoverable critical fault within a System on a Chip (SoC) subsystem, often due to hardware malfunctions or firmware issues. |
| 0x1000007E | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M | This error occurs when a system thread generates an exception that the error handler cannot catch, often due to issues with incompatible or outdated drivers. |
| 0x1000007F | UNEXPECTED_KERNEL_MODE_TRAP_M | This error occurs when the CPU generates a trap that the kernel cannot catch, often due to hardware failures such as faulty or mismatched memory. |
| 0x1000008E | KERNEL_MODE_EXCEPTION_NOT_HANDLED_M | This error occurs when a kernel-mode application generates an exception that the error handler cannot catch, often due to issues with device drivers or system services. |
| 0x100000EA | THREAD_STUCK_IN_DEVICE_DRIVER_M | This error occurs when a device driver enters an endless loop while waiting for hardware to become idle, often due to issues with the driver itself. |
| 0xC0000218 | STATUS_CANNOT_LOAD_REGISTRY_FILE | This error occurs when the Windows operating system fails to load a necessary registry hive file, typically due to corruption or the file being missing. |
| 0xC000021A | STATUS_SYSTEM_PROCESS_TERMINATED | This error occurs when a critical system process, such as WinLogon or the Client-Server Runtime Subsystem (CSRSS), unexpectedly terminates, often due to corruption or failure to load properly. |
| 0xC0000221 | STATUS_IMAGE_CHECKSUM_MISMATCH | This error occurs when the checksum of a system file, such as a driver or DLL, does not match its expected value, indicating potential corruption. |
| 0xDEADDEAD | MANUALLY_INITIATED_CRASH1 | This error indicates that a manually initiated crash occurred. |
How ManageEngine EventLog Analyzer helps you with BSOD analysis for fast, effective troubleshooting in Windows
ManageEngine EventLog Analyzer is a comprehensive log management solution that monitors, collects, analyzes, and archives logs from your network, including Windows environment. It enables users to gather critical information from various sources, including system logs that record BSOD occurrences.
While the natively available tools help you view and analyze logs for a single system, EventLog Analyzer consolidates logs from multiple Windows systems into a single console.
EventLog Analyzer includes a predefined report specifically designed for BSOD analysis, which captures critical information such as:
- All systems that experienced the BSOD, helping to identify patterns.
- Detailed messages related to bug codes, which are essential for diagnosing the root cause of the crash.
- Exact time at which the stop code error took place.
- In addition to reporting capabilities, EventLog Analyzer enables you to set up real-time alerts for critical Windows systems experiencing BSODs.
