| TABLE 1: Kernel Mode Error Conditions | |
| 0X0000000A | |
| IRQL_NOT_LESS_OR_EQUAL | |
| A process attempted to access pageable memory at a process internal request level (IRQL) that was too high. A process can access only objects that have priorities (IRQL) equal to or lower than its own. A device driver using improper addresses usually is the cause of this error. | |
| 0X00000019 | BAD_POOL_HEADER |
| This error, also called Invalid Pool Header, can appear for several reasons. You can find the cause by debugging the system. | |
| 0X0000001E | KMODE_EXCEPTION_NOT_HANDLED |
| This error is a very common bug check. Usually the exception address (the second parameter) pinpoints the driver or function that caused the problem. Always note this address and the link date of the driver or image that contains this address. | |
| 0X00000024 | NTFS_FILE_SYSTEM |
| All file system bug checks have encoded the source file and the line within the source file that generated the bug check in their first ULONG (unsigned long value). The upper 16 bits identify the file; the lower 16 bits identify the source line in the file where the bug check occurred. | |
| 0X00000051 | REGISTRY_ERROR |
| Something has gone terribly wrong with the Registry. It might have received an I/O error while attempting to read one of its files as a result of a hardware problem or file system corruption. | |
| 0X00000077 | KERNEL_STACK_INPAGE_ERROR |
| The system could not read in the requested page of kernel data. A bad block in a paging file or a disk controller error might be the cause. If the error is a result of a paging error, AUTOCHK will attempt to map out the bad block when you restart the system. The second parameter identifies the cause of the error: | |
| 0XC000009A | |
| signifies a lack of nonpaged pool resources. | |
| 0XC000009C and 0XC000016A | |
| both signify a bad block on the drive. | |
| 0XC0000185 | |
| signifies improper termination of a SCSI device, bad SCSI cabling, or two devices attempting to use the same IRQ. | |
| 0X0000007A | KERNEL_DATA_INPAGE_ ERROR |
| See 00000077, KERNEL_STACK_INPAGE_ERROR | |
| 0X0000007B | INACCESSIBLE_BOOT_DEVICE |
| The system cannot access the boot device. Often, this message signifies a disk controller configuration problem or an error in accessing the hard disk. Another possible cause is that, during initialization of the I/O system, the driver for the boot device failed to initialize the boot device (device not available, SCSI error). Another possibility is that the file system could not recognize the data on the boot device. The message also might mean that a virus has infected the boot sector. | |
| 0X0000007F | UNEXPECTED_KERNEL_MODE_TRAP |
| A trap that the kernel doesn't have permission to have or catch occurred in privileged processor (kernel) mode. The message may signify a computer RAM problem (mismatched SIMMs), a BIOS problem, or corrupted file system drivers. The first number in the bug check is the number of the trap. Consult an Intel x86 Family manual for the trap codes. | |
| 0X00000080 | NMI_HARDWARE_FAILURE |
| A hardware error has occurred, in which HAL reports the information that it can identify and directs the user to call the hardware vendor. | |
If the stop code identifies a problemsuch as a 0X0000007B INACCESSIBLE_BOOT_DEVICE errorthat you can resolve locally, correct the problem (e.g., remember to turn on the external hard disk drive) and then restart the computer to verify the resolution. If you can't resolve the error easily, you might be able to use a kernel debugger to isolate the problem.