Common BSOD messages and causes
The infamous Microsoft “Blue Screen Of Death”, or BSOD, can of course have many causes, some of which can be fixed up with a reboot. Other BSOD errors may signify a more serious issue related to Drivers, memory or other factors.
Listed below are a few of the most common Error messages that accompany a BSOD, together with explanations of what they may mean.
The error messages take the form of an 8-character hexidecimal code (the last eight characters in the ‘STOP’ message code).
STOP: 0×0000000A
IRQL_NOT_LESS_OR_EQUAL
Indicates that a kernel-mode process or driver attempted to access a memory location it did not have permission to access, or a memory location that exists at a kernel interrupt request level (IRQL) that was too high (a kernel-mode process can only access other processes that have an IRQL that’s equal to or lower than its own).
STOP: 0×0000001E
KMODE_EXCEPTION_NOT_HANDLED
The Windows XP kernel detected an illegal or unknown processor instruction. The problems that cause this error can be either software or hardware related and result from invalid memory and access violations, which are intercepted by the Windows default error handler if error-handling routines are not present in the code itself.
STOP: 0×00000024
NTFS_FILE_SYSTEM
Indicates that a problem occurred within Ntfs.sys, the driver file that allows the system to read and write to drives formatted with the NTFS file system. (A similar Stop message, 0×00000023, exists for the file allocation table [FAT16 or FAT32)] file systems).
STOP: 0×00000050
PAGE_FAULT_IN_NONPAGED_AREA
The requested data was not in memory. The system generates an exception error when using a reference to an invalid system memory address. Defective memory (including main memory, L2 RAM cache, video RAM) or incompatible software may cause this error.
STOP: 0×0000007B
INACCESSIBLE_BOOT_DEVICE
Windows XP has lost access to the system partition or boot volume during the startup process. Incorrect device drivers typically cause this error although it can also indicate a possible virus infection.
STOP: 0×0000007F
UNEXPECTED_KERNEL_MODE_TRAP
A hardware problem e.g. resulting from mismatched or defective memory, a malfunctioning CPU, or a fan failure that’s causing overheating.
STOP: 0×0000009F
DRIVER_POWER_STATE_FAILURE
Indicates that a driver is in an inconsistent or invalid power state. This error typically occurs during events that involve power state transitions, such as shutting down or moving in or out of standby or hibernate mode.
STOP: 0×000000D1
DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system attempted to access pageable memory using a kernel process IRQL that was too high. Typical cause is a bad device driver (one that uses improper addresses) although it can also be caused by faulty or mismatched RAM or a damaged pagefile.
STOP: 0×000000EA
THREAD_STUCK_IN_DEVICE_DRIVER
A device driver problem is causing the system to pause indefinitely. Typically, this problem is caused by a display driver waiting for the video hardware to enter an idle state. This might point to a hardware problem with the video adapter or a faulty video driver.
STOP: 0xC0000218
UNKNOWN_HARD_ERROR
A required registry hive file could not be loaded. The file may be corrupt or missing. The registry file may have been corrupted due to hard disk corruption or some other hardware problem. A driver may have corrupted the registry data while loading into memory or the memory where the registry is loading may have a parity error.
STOP: 0xC0000221
STATUS_IMAGE_CHECKSUM_MISMATCH
Driver, system file, or disk corruption problems (such as a damaged paging file). Faulty memory hardware can also cause this message to appear.
Simple Machines Forum (SMF) is a free, professional grade software package that allows you to set up your own online community within minutes.