0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Unexpected exception in kernel mode or interrupt request line that prevents kernel correct operating has happened. The reason may also be in interrupt that lead to instant death in form of double fault. The first number in the error code is interrupt number (8 = double fault). In order to learn more about this type of interrupt please refer to the x86 family manual. In other words, this error occurs when processor commits error that the kernel is not able to resolve. Most frequently this error is caused by storage device bad blocks and less frequently by processor acceleration. Try to cancel synchronous data transmission in BIOS.
0x00000080: NMI_HARDWARE_FAILURE
This is the kernel initialization error. HAL must present all specific information required and offer to contact equipment supplier for technical support.
0x0000008B: MBR_CHECKSUM_MISMATCH
This error occurs during the booting process, when MBR control total computed by the system does not coincide with the one calculated by the boot loader. Usuallyitmeansviruseffect. First boot with the help of boot CD and then scan boot sector with antivirus software.
0x0000008E: PAGE_FAULT_IN_NON_PAGED_AREA
This error is caused by RAM memory units incompatibility or corruption. Check RAM memory and replace defective memory units.
0x0000008F: PP0_INITIALIZATION_FAILED
This error occurs during zero phase of Plug and Play manager initialization process in kernel mode. Check the equipment and system disk.
0x00000090: PP1_INITIALIZATION_FAILED
This error occurs during the primary phase of Plug and Play manager initialization process in kernel mode. By this moment system files, driver and register have been already initialized. Checktheequipmentandsystemdisk.
0x00000092: UP_DRIVER_ON_MP_SYSTEM
This error happens when uniprocessor driver is being loaded in system with more than one active processor.
0x00000093: INVALID_KERNEL_HANDLE
This error occurs when kernel code or other operating system critical components try to shut down the descriptor that is not valid.
0x00000096: INVALID_WORK_QUEUE_ITEM
The problem is caused by incorrect device driver.
0x00000097: BOUND_IMAGE_UNSUPPORTED
The problem is caused by incorrect device driver.
0x00000098: END_OF_NT_EVALUATION_PERIOD
Trial period of Windows demo version has run out.
0x00000099: INVALID_REGION_OR_SEGMENT
ExInitializeRegion or ExInterlockedExtendRegion were requested with incorrect parameters selection.
0x0000009A: SYSTEM_LICENSE_VIOLATION
Software license agreement has been violated. This may be caused by attempt to change system type product or Windows demo version trial period.
0x0000009B: UDFS_FILE_SYSTEM
This error is caused by read or record operation fault while using UDFS (User-defined file system) data carrier. This fault may originate from the file system corruption or disk bad sectors. It may also result from the software changing dick structure, for instance, an encryption program.
0x0000009C: MACHINE_CHECK_EXCEPTION
This is a fatal error Machine Check Exception. The error is related to incorrect equipment configuration, processor acceleration, RAM memory units’ unstable performance, system components overheating or power supply unit unstable operation.
0x0000009F: DRIVER_POWER_STATE_FAILURE
Driver energy consumption is discordant or inadmissible. Usually it happens because of power failure, while rebooting, sleep mode quit etc. You should replace faulty driver or remove the software that controls file system (antivirus software, encryption programs etc.).
0x000000A5: ACPI_BIOS_ERROR
This error is caused by permanent failure of ACPI BIOS. This problem cannot be resolved on operating system level. The detailed analysis is required.
0x000000B4: VIDEO_DRIVER_INIT_FAILURE
Windows operating system didn't manage to load video card driver. The problem is related to video card drivers or hardware conflict happened. Reboot in safe mode and install the standard video card driver.
0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
Driver tried to write data on ROM device where this operation is impossible. The problem is basically related to installation of a bad driver, service or firmware. Replacethedriver.
0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Driver has written some data in inadmissible storage section. Replace the driver.
0x000000C2: BAD_POOL_CALLER
System kernel or driver produced an incorrect memory reference instruction. This error is basically caused by bad driver or faulty software. Replace the driver.
0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
Driver check program has detected fatal error in STOP-error generation module. Cover parameters are parameters transmitted to KeBugCheckEx and displayed on a blue screen. Replace the driver.
0x000000C5: DRIVER_CORRUPTED_EXPOOL
There was an attempt to call high level IRQL process from inadmissible memory area. This error is mostly caused by the drivers which corrupted system pool. Replacethedriver.
0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
Driver has made an attempt to call disposed memory pool. Replace the driver.
0x000000C7: TIMER_OR_DPC_INVALID
Kernel timer or Delayed Procedure Call (DPC) appears in forbidden memory block. This error occurs when the driver didn’t manage to shut down kernel timer or Delayed Procedure Call (DPC) before its roll-out from memory. Replace the driver.
0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
This message is produced by some of driver check managers. Replace the driver.
0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
This error is similar to STOP-error 0x00000076. The only difference between these two is that the present error is detected while kernel tracing. The error means that the driver or input-output manager cannot open locked pages after input-output procedure execution. Pay attention to the application-oriented driver name displayed in STOP-error window. Replace the driver.
0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
Thedrivercannotcancelsystemcomponentspendingoperations. This error usually occurs as a result of installation of bad drivers or service components. Replacethedriver.
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system tried to call page memory using kernel process through the high level IRQL. The bad driver is the most common reason of this problem. It also may be caused by corrupted RAM memory or faulty swap-file.


Sections
Categories
Calendar