Most Common Blue Screen Errors Message :
0x00000001: APC_INDEX_MISMATCH
0x00000002: DEVICE_QUEUE_NOT_BUSY
0x00000003: INVALID_AFFINITY_SET
0x00000004: INVALID_DATA_ACCESS_TRAP
0x00000005: INVALID_PROCESS_ATTACH_ATTEMPT
0x00000006: INVALID_PROCESS_DETACH_ATTEMPT
0x00000007: INVALID_SOFTWARE_INTERRUPT
0x00000008: IRQL_NOT_DISPATCH_LEVEL
0x00000009: IRQL_NOT_GREATER_OR_EQUAL
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
0x0000000B: NO_EXCEPTION_HANDLING_SUPPORT
0x0000000C: MAXIMUM_WAIT_OBJECTS_EXCEEDED
0x0000000D: MUTEX_LEVEL_NUMBER_VIOLATION
0x0000000E: NO_USER_MODE_CONTEXT
0x0000000F: SPIN_LOCK_ALREADY_OWNED
0x00000010: SPIN_LOCK_NOT_OWNED
0x00000011: THREAD_NOT_MUTEX_OWNER
0x00000012: TRAP_CAUSE_UNKNOWN
0x00000013: EMPTY_THREAD_REAPER_LIST
0x00000014: CREATE_DELETE_LOCK_NOT_LOCKED
0x00000015: LAST_CHANCE_CALLED_FROM_KMODE
0x00000016: CID_HANDLE_CREATION
0x00000017: CID_HANDLE_DELETION
0x00000018: REFERENCE_BY_POINTER
0x00000019: BAD_POOL_HEADER
0x0000001A: MEMORY_MANAGEMENT
0x0000001B: PFN_SHARE_COUNT
0x0000001C: PFN_REFERENCE_COUNT
0x0000001D: NO_SPIN_LOCK_AVAILABLE
0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
0x0000001F: SHARED_RESOURCE_CONV_ERROR
0x00000020: KERNEL_APC_PENDING_DURING_EXIT
0x00000021: QUOTA_UNDERFLOW
0x00000022: FILE_SYSTEM
0x00000023: FAT_FILE_SYSTEM
0x00000024: NTFS_FILE_SYSTEM
0x00000025: NPFS_FILE_SYSTEM
0x00000026: CDFS_FILE_SYSTEM
0x00000028: CORRUPT_ACCESS_TOKEN
0x00000029: SECURITY_SYSTEM
0x0000002A: INCONSISTENT_IRP
0x0000002B: PANIC_STACK_SWITCH
0x0000002C: PORT_DRIVER_INTERNAL
0x0000002D: SCSI_DISK_DRIVER_INTERNAL
0x0000002E: DATA_BUS_ERROR
0x0000002F: INSTRUCTION_BUS_ERROR
0x00000030: SET_OF_INVALID_CONTEXT
0x00000031: PHASE0_INITIALIZATION_FAILED
0x00000032: PHASE1_INITIALIZATION_FAILED
0x00000033: UNEXPECTED_INITIALIZATION_CALL
0x00000034: CACHE_MANAGER
0x00000035: NO_MORE_IRP_STACK_LOCATIONS
0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO 0x00000037: FLOPPY_INTERNAL_ERROR
0x00000038: SERIAL_DRIVER_INTERNAL
0x00000039: SYSTEM_EXIT_OWNED_MUTEX
0x0000003A: SYSTEM_UNWIND_PREVIOUS_USER
0x0000003B: SYSTEM_SERVICE_EXCEPTION
0x0000003C: INTERRUPT_UNWIND_ATTEMPTED
0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED
0x0000003E: MULTIPROCESSOR_CONFIGURATION
_NOT_SUPPORTED
0x0000003F: NO_MORE_SYSTEM_PTES
0x00000040: TARGET_MDL_TOO_SMALL
0x00000041: MUST_SUCCEED_POOL_EMPTY
0x00000042: ATDISK_DRIVER_INTERNAL
0x00000043: NO_SUCH_PARTITION
0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS
0x00000045: INSUFFICIENT_SYSTEM_MAP_REGS
0x00000046: DEREF_UNKNOWN_LOGON_SESSION
0x00000047: REF_UNKNOWN_LOGON_SESSION
0x00000048: CANCEL_STATE_IN_COMPLETED_IRP
0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF
0x0000004A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
0x0000004B: STREAMS_INTERNAL_ERROR
0x0000004C: FATAL_UNHANDLED_HARD_ERROR
0x0000004D: NO_PAGES_AVAILABLE
0x0000004E: PFN_LIST_CORRUPT
0x0000004F: NDIS_INTERNAL_ERROR
0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
0x00000051: REGISTRY_ERROR
0x00000052: MAILSLOT_FILE_SYSTEM
0x00000053: NO_BOOT_DEVICE
0x00000054: LM_SERVER_INTERNAL_ERROR
0x00000055: DATA_COHERENCY_EXCEPTION
0x00000056: INSTRUCTION_COHERENCY_EXCEPTION
0x00000057: XNS_INTERNAL_ERROR
0x00000058: FTDISK_INTERNAL_ERROR
0x00000059: PINBALL_FILE_SYSTEM
0x0000005A: CRITICAL_SERVICE_FAILED
0x0000005B: SET_ENV_VAR_FAILED
0x0000005C: HAL_INITIALIZATION_FAILED
0x0000005D: UNSUPPORTED_PROCESSOR
0x0000005E: OBJECT_INITIALIZATION_FAILED
0x0000005F: SECURITY_INITIALIZATION_FAILED
0x00000060: PROCESS_INITIALIZATION_FAILED
0x00000061: HAL1_INITIALIZATION_FAILED
0x00000062: OBJECT1_INITIALIZATION_FAILED
0x00000063: SECURITY1_INITIALIZATION_FAILED
0x00000064: SYMBOLIC_INITIALIZATION_FAILED
0x00000065: MEMORY1_INITIALIZATION_FAILED
0x00000066: CACHE_INITIALIZATION_FAILED
0x00000067: CONFIG_INITIALIZATION_FAILED
0x00000068: FILE_INITIALIZATION_FAILED
0x00000069: IO1_INITIALIZATION_FAILED
0x0000006A: LPC_INITIALIZATION_FAILED
0x0000006B: PROCESS1_INITIALIZATION_FAILED
0x0000006C: REFMON_INITIALIZATION_FAILED
0x0000006D: SESSION1_INITIALIZATION_FAILED
0x0000006E: SESSION2_INITIALIZATION_FAILED
0x0000006F: SESSION3_INITIALIZATION_FAILED
0x00000070: SESSION4_INITIALIZATION_FAILED
0x00000071: SESSION5_INITIALIZATION_FAILED
0x00000072: ASSIGN_DRIVE_LETTERS_FAILED
0x00000073: CONFIG_LIST_FAILED
0x00000074: BAD_SYSTEM_CONFIG_INFO
0x00000075: CANNOT_WRITE_CONFIGURATION
0x00000076: PROCESS_HAS_LOCKED_PAGES
0x00000077: KERNEL_STACK_INPAGE_ERROR
0x00000078: PHASE0_EXCEPTION
0x00000079: MISMATCHED_HAL
0x0000007A: KERNEL_DATA_INPAGE_ERROR
0x0000007B: INACCESSIBLE_BOOT_DEVICE
0x0000007C: BUGCODE_NDIS_DRIVER
0x0000007D: INSTALL_MORE_MEMORY
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
0x00000080: NMI_HARDWARE_FAILURE
0x00000081: SPIN_LOCK_INIT_FAILURE
0x00000082: DFS_FILE_SYSTEM
0x00000083: OFS_FILE_SYSTEM
0x00000084: RECOM_DRIVER
0x00000085: SETUP_FAILURE
0x00000086: Undetermined
0x00000087: Undetermined
0x00000088: Undetermined
0x00000089: Undetermined
0x0000008A: Undetermined
0x0000008B: MBR_CHECKSUM_MISMATCH
0x0000008D: Undetermined
0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
0x0000008F: PP0_INITIALIZATION_FAILED
0x00000090: PP1_INITIALIZATION_FAILED
0x00000091: WIN32K_INIT_OR_RIT_FAILURE
0x00000092: UP_DRIVER_ON_MP_SYSTEM
0x00000093: INVALID_KERNEL_HANDLE
0x00000094: KERNEL_STACK_LOCKED_AT_EXIT
0x00000095: PNP_INTERNAL_ERROR
0x00000096: INVALID_WORK_QUEUE_ITEM
0x00000097: BOUND_IMAGE_UNSUPPORTED
0x00000098: END_OF_NT_EVALUATION_PERIOD
0x00000099: INVALID_REGION_OR_SEGMENT
0x0000009A: SYSTEM_LICENSE_VIOLATION
0x0000009B: UDFS_FILE_SYSTEM
0x0000009C: MACHINE_CHECK_EXCEPTION
0x0000009D: Undetermined
0x0000009E: Undetermined
0x0000009F: DRIVER_POWER_STATE_FAILURE
0x000000A0: INTERNAL_POWER_ERROR
0x000000A1: PCI_BUS_DRIVER_INTERNAL
0x000000A2: MEMORY_IMAGE_CURRUPT
0x000000A3: ACPI_DRIVER_INTERNAL
0x000000A4: CNSS_FILE_SYSTEM_FILTER
0x000000A5: ACPI_BIOS_ERROR
0x000000A6: Undetermined
0x000000A7: BAD_EXHANDLE
0x000000A8: Undetermined
0x000000A9: Undetermined
0x000000AA: Undetermined
0x000000AB: SESSION_HAS_VALID_POOL_ON_EXIT
0x000000AC: HAL_MEMORY_ALLOCATION
0x000000AD: Undetermined
0x000000AE: Undetermined
0x000000AF: Undetermined
0x000000B0: Undetermined
0x000000B1: Undetermined
0x000000B2: Undetermined
0x000000B3: Undetermined
0x000000B4: VIDEO_DRIVER_INIT_FAILURE
0x000000B5: Undetermined
0x000000B6: Undetermined
0x000000B7: Undetermined
0x000000B8: ATTEMPTED_SWITCH_FROM_DPC
0x000000B9: CHIPSET_DETECTED_ERROR
0x000000BA: SESSION_HAS_VALID_VIEWS_ON_EXIT
0x000000BB: NETWORK_BOOT_INITIALIZATION_FAILED
0x000000BC: NETWORK_BOOT_DUPLICATE_ADDRESS
0x000000BD: Undetermined
0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
0x000000BF: MUTEX_ALREADY_OWNED
0x000000C0: Undetermined
0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 0x000000C2: BAD_POOL_CALLER
0x000000C3: Undetermined
0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
0x000000C5: DRIVER_CORRUPTED_EXPOOL
0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
0x000000C7: TIMER_OR_DPC_INVALID
0x000000C8: IRQL_UNEXPECTED_VALUE
0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
0x000000CA: PNP_DETECTED_FATAL_ERROR
0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
0x000000CC: PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000CD: PAGE_FAULT_BEYOND_END_OF_ALLOCATION
0x000000CE: DRIVER_UNLOADED_WITHOUT_
CANCE LLING_PENDING_OPERATIONS
0x000000CF: TERMINAL_SERVER_DRIVER_MADE_
INCORRECT_MEMORY_REFERENCE
0x000000D0: DRIVER_CORRUPTED_MMPOOL
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x000000D2: BUGCODE_ID_DRIVER
0x000000D3: DRIVER_PORTION_MUST_BE_NONPAGED
0x000000D4: SYSTEM_SCAN_AT_RAISED_IRQL_
CAUGHT_IMPROPER_DRIVER_UNLOAD
0x000000D5: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000D6: DRIVER_PAGE_FAULT_BEYOND_
END_OF_ALLOCATION
0x000000D7: DRIVER_UNMAPPING_INVALID_VIEW
0x000000D8: DRIVER_USED_EXCESSIVE_PTES
0x000000D9: MUTEX_ALREADY_OWNED
0x000000DA: SYSTEM_PTE_MISUSE
0x000000DB: DRIVER_CORRUPTED_SYSPTES
0x000000DC: DRIVER_INVALID_STACK_ACCESS
0x000000DD: Undetermined
0x000000DE: POOL_CORRUPTION_IN_FILE_AREA
0x000000DF: IMPERSONATING_WORKER_THREAD
0x000000E0: ACPI_BIOS_FATAL_ERROR
0x000000E1: WORKER_THREAD_RETURNED_AT_BAD_IRQL
0x000000E2: MANUALLY_INITIATED_CRASH
0x000000E3: RESOURCE_NOT_OWNED
0x000000E4:E5: Undetermined
0x000000E6: DRIVER_VERIFIER_DMA_VIOLATION
0x000000E7: INVALID_FLOATING_POINT_STATE
0x000000E8: INVALID_CANCEL_OF_FILE_OPEN
0x000000E9: ACTIVE_EX_WORKER_THREAD_TERMINATION
0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
0x000000EB: DIRTY_MAPPED_PAGES_CONGESTION
0x000000EC: SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT
0x000000ED: UNMOUNTABLE_BOOT_VOLUME
0x000000EE: Undetermined
0x000000EF: CRITICAL_PROCESS_DIED
0x000000F0: Undetermined
0x000000F1: SCSI_VERIFIER_DETECTED_VIOLATION
0x000000F2: HARDWARE_INTERRUPT_STORM
0x000000F3: DISORDERLY_SHUTDOWN
0x000000F4: CRITICAL_OBJECT_TERMINATION
0x000000F5: Undetermined
0x000000F6: PCI_VERIFIER_DETECTED_VIOLATION
0x000000F7: DRIVER_OVERRAN_STACK_BUFFER
0x000000F8: RAMDISK_BOOT_INITIALIZATION_FAILED
0x000000F9: DRIVER_RETURNED_STATUS_
REPARSE_FOR_VOLUME_OPEN
0x000000FA: Undetermined
0x000000FB: Undetermined
0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
0x000000FD: Undetermined
0x000000FE: BUGCODE_USB_DRIVER
0x000000FF: Undetermined
0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M
0x100000EA: THREAD_STUCK_IN_DEVICE_DRIVER_M
0xC000009A: STATUS_INSUFFICIENT_RESOURCES
0xC0000135: UNABLE_TO_LOCATE_DLL
0xC0000142: DLL Initialization Failure
0xC0000218: UNKNOWN_HARD_ERROR
0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
0xC0000244
0xC000026C
0xDEADDEAD: MANUALLY_INITIATED_CRASH1
This list contains brief the causes of fatal errors for the operating systems Windows 3.51, 4.0, Wndows 2000, Windows XP, Windows Vista. Methods for their removal are described in another article.
0x00000001: APC_INDEX_MISMATCH
Internal Error kernel (kernel). The problem is mostly with problems in drivers
lack of memory or disk space.
0x00000002: DEVICE_QUEUE_NOT_BUSY
0x00000003: INVALID_AFFINITY_SET
0x00000004: INVALID_DATA_ACCESS_TRAP
0x00000005: INVALID_PROCESS_ATTACH_ATTEMPT
0x00000006: INVALID_PROCESS_DETACH_ATTEMPT
0x00000007: INVALID_SOFTWARE_INTERRUPT
0x00000008: IRQL_NOT_DISPATCH_LEVEL
0x00000009: IRQL_NOT_GREATER_OR_EQUAL
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
There was an interference in the virtual memory on the internal process of high-level IRQ.
The most common cause of - the device driver uses an incorrect address.
The error occurs because of bad drivers. Rarely occurs because of malfunction of one of the devices in the system.
Parameters:
1 - the address to which you are wrong treatment
2 - IRQL, which was used to access memory
3 - type of memory access: 0 = read operation, 1 = write operation
4 - address of instruction that has requested access to memory at
0x0000000B: NO_EXCEPTION_HANDLING_SUPPORT
0x0000000C: MAXIMUM_WAIT_OBJECTS_EXCEEDED
0x0000000D: MUTEX_LEVEL_NUMBER_VIOLATION
0x0000000E: NO_USER_MODE_CONTEXT
0x0000000F: SPIN_LOCK_ALREADY_OWNED
0x00000010: SPIN_LOCK_NOT_OWNED
0x00000011: THREAD_NOT_MUTEX_OWNER
0x00000012: TRAP_CAUSE_UNKNOWN
0x00000013: EMPTY_THREAD_REAPER_LIST
0x00000014: CREATE_DELETE_LOCK_NOT_LOCKED
0x00000015: LAST_CHANCE_CALLED_FROM_KMODE
0x00000016: CID_HANDLE_CREATION
0x00000017: CID_HANDLE_DELETION
0x00000018: REFERENCE_BY_POINTER
0x00000019: BAD_POOL_HEADER
0x0000001A: MEMORY_MANAGEMENT
0x0000001B: PFN_SHARE_COUNT
0x0000001C: PFN_REFERENCE_COUNT
0x0000001D NO_SPIN_LOCK_AVAILABLE
0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
This is a very common mistake. Usually excluded address points to the driver or function that caused the stop screen. Always pay attention not only to the specified driver, but also to address itself or an image that contains this error. Usually, this exception code 0x80000003. This error means that the point of interruption or handler is initialized when accessing memory, but the system is booted with / NODEBUG key. This error can not occur too often. If the error appears constantly, make sure that the debugger (debugger) is connected and the system is booted with / DEBUG switch.
On non-Intel systems, if the exception address - 0XBFC0304, an error occurs because the processor cache. If the error occurs permanently please contact the manufacturer of the processor.
As a rule, requires an analysis of the second parameter of the message, which indicates the address of the driver / function that was causing the problem.
Parameters:
1 - Code Exception
2 - address the processing of which failed
3 - Parameter 0 - the exception
4 - Option 1 - the exception
0x0000001F: SHARED_RESOURCE_CONV_ERROR
0x00000020: KERNEL_APC_PENDING_DURING_EXIT
Name of error indicates a damaged / disabled APC counter. If you have this situation, check all file systems are installed on the machine, for example using a rescue package EMRD.
Current IRQL should be zero. If the IRQ is not zero, then a certain order of unloading drivers, when returning to a higher level of IRQ, may cause errors. Try to remember what you did or what applications are closed, what drivers were installed at the time the blue screen. This symptom indicates a serious problem in third-party drivers.
Parameters:
1 - address of APC, at the time of the crash.
2 - Failed thread APC
3 - the current IRQ level
0x00000021: QUOTA_UNDERFLOW
0x00000022: FILE_SYSTEM
0x00000023: FAT_FILE_SYSTEM
Has failed to read or write to the hard disk partition formatted with FAT. Failure may be associated with damage to the file system, or the appearance of bad sectors on the disk. Also, failure may be associated with the software, changing the structure of the disk (encryption programs, etc.).
0x00000024: NTFS_FILE_SYSTEM
Has failed to read or write to the hard disk partition formatted with NTFS. Failure may be associated with damage to the file system, or the appearance of bad sectors on the disk. Also, failure may be associated with the software, changing the structure of the disk (encryption programs, etc.).
0x00000025: NPFS_FILE_SYSTEM
0x00000026: CDFS_FILE_SYSTEM
0x00000027: RDR_FILE_SYSTEM
0x00000028: CORRUPT_ACCESS_TOKEN
0x00000029: SECURITY_SYSTEM
0x0000002A: INCONSISTENT_IRP
I / O Request Packet (IRP) is not functioning, occurs when a field or several fields are incorrect compared to the preserved state of IRP. For example, IRP was already disabled when the driver of a device waiting for the team.
Parameters:
1 - address to which IRP was found in idle mode
0x0000002B: PANIC_STACK_SWITCH
This error occurs when the domain of kernel stack is full. Error occurs when the kernel driver uses too much space in the stack. Possible cause of error may also be damage to the nucleus.
0x0000002C: PORT_DRIVER_INTERNAL
0x0000002D: SCSI_DISK_DRIVER_INTERNAL
0x0000002E: DATA_BUS_ERROR
This STOP-error often occurs due to a failure of memory. This can happen when a driver tries to access a memory address that does not exist.
Parameters:
1 - the virtual memory address that caused the error
2 - physical address of the causes of errors
3 - check the status of the processor (PSR)
4 - Registration instructions error (FIR)
0x0000002F: INSTRUCTION_BUS_ERROR
0x00000030: SET_OF_INVALID_CONTEXT
0x00000031: PHASE0_INITIALIZATION_FAILED
System initialization failed to complete at an early stage (phase 0). Need to examine in more detail the error, as this error code does not say anything practical.
0x00000032: PHASE1_INITIALIZATION_FAILED
System initialization failed to complete at a late stage (Phase 1). Need to examine in more detail the error, as this error code does not say anything practical.
Parameters:
1 - Code-level system, which describes, for whatever reason, the system considers that the initialization is not completed
2 - indicates the location within INIT.C, where the error occurred initializing phase 1
0x00000033: UNEXPECTED_INITIALIZATION_CALL
0x00000034: CACHE_MANAGER
0x00000035: NO_MORE_IRP_STACK_LOCATIONS
Driver high-level driver tried to call low-level interface IoCallDriver (), but the system did not have space in the stack, for this reason that low-level drivers will not reach the required parameters, since it generally has no parameters. This is a fatal situation, since high-level driver believes that the settings for the driver filled the lower level (something he had done to cause low-level drivers). Nevertheless, since there is no free space in the stack was overwritten by the end of the package. This often occurs because of damage to the stack memory. Should be checked for errors and memory drivers.
Parameters:
1 - e IRP
0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO
The device driver was trying to remove from your system one component of a device, but the reference count of this component was not equal to zero - this means that for this component are some outstanding problems (counter indicates the error code, which is why this component can not be unloaded). This is an error calling the driver.
Parameters:
1 - Address object
0x00000037: FLOPPY_INTERNAL_ERROR
0x00000038: SERIAL_DRIVER_INTERNAL
0x00000039: SYSTEM_EXIT_OWNED_MUTEX
0x0000003A: SYSTEM_UNWIND_PREVIOUS_USER
0x0000003B: SYSTEM_SERVICE_EXCEPTION
0x0000003C: INTERRUPT_UNWIND_ATTEMPTED
0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED
0x0000003E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED
Multiprocessor system is not symmetric with respect to each other. For proper symmetry, the processors must be the same type and level. For example, attempts to use a processor-level Pentium and 80486 at the same time, causing havoc. Additionally, on x86 systems, the possibility of floating point calculations must be either on all processors, or no one.
0x0000003F: NO_MORE_SYSTEM_PTES
Not enough RTE (page file entries - access points to the swap file). Usually the cause is a driver that is bad clears the paging file (swap) and it overflows. Also, the cause may be excessive fragmentation of the paging file.
0x00000040: TARGET_MDL_TOO_SMALL
The driver called function IoBuildPartialMdl () and handed him a MDL, to identify the source of the MDL, but the recipient scope MDL is not large enough to display the limits of the desired address. This is a driver error.
0x00000041: MUST_SUCCEED_POOL_EMPTY
Driver sought in place Must Suceed Pool. This feature may not be feasible, since the system does not allocate seats in Must Suceed Pool. Replace or upgrade the faulty driver system.
Parameters:
1 - magnitude of the required request
2 - Number of used pages
3 - the number of requested pages
4 - number of pages available
0x00000042: ATDISK_DRIVER_INTERNAL
0x00000043: NO_SUCH_PARTITION
0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS
The driver asked for the completion of IRP [IoCompleteRequest ()], but the package has already been completed. This error is difficult to detect. Possible cause - the driver tries to complete the same operation several times. A rare cause - 2 different drivers trying to seize the package and complete it. The first usually works, but second to none. Keep track of which driver is made difficult, since traces of the first drivers have been rewritten second.
Parameters:
1 - e IRP
0x00000045: INSUFFICIENT_SYSTEM_MAP_REGS
0x00000046: DEREF_UNKNOWN_LOGON_SESSION
0x00000047: REF_UNKNOWN_LOGON_SESSION
0x00000048: CANCEL_STATE_IN_COMPLETED_IRP
This error indicates that the I / O Request Packet (IRP), which should be completed, the order of cancellation specified in it the same, ie This means that the package in this mode can be canceled. Nevertheless, the package does not include more than the driver, as he had already entered the stage of completion.
Parameters:
1 - e IRP
0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF
Pagination error when accessing memory, and switched off interrupts IRQ. The error description is the same as that of 0x0000000A.
0x0000004A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
0x0000004B: STREAMS_INTERNAL_ERROR
0x0000004C: FATAL_UNHANDLED_HARD_ERROR
Critical unrecognized error. The most likely reasons for this are described in the 0xC0000218, 0xC000022A or 0xC0000221.
0x0000004D: NO_PAGES_AVAILABLE
No more free-paged memory to complete the operation. Check the available disk space. Replace the driver.
Parameters:
1 - number of pages used
2 - number of physical pages on the machine
3 - enhanced the value of pages
4 - Total value of pages
0x0000004E: PFN_LIST_CORRUPT
Reason - Damaged / defective structure of the I / O driver.
Parameters:
1. value 1
2. value ListHead, which damaged
3. number of pages available
4. zero
1. value 2
2. data that can be removed
3. maximum number of physical pages
4. result of the deleted data
0x0000004F: NDIS_INTERNAL_ERROR
0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Occurs when the information requested was not found in memory. The system checks the swap file (page file), but the missing information was identified, it is impossible to write to the swap file (page file).
Parameters:
1. points to an address in memory, which is a mistake
0x00000051: REGISTRY_ERROR
An I / O error with the registry when the system tried to read one of his files, it follows that the error could be caused by hardware problems or damage to the system itself. It can also mean that the error was caused by the update operation, which uses only the security system and this error occurs when resources are running low. If this error occurs, check whether the machine is PDC or BDC, and how many accounts in the database SAM (Security Accounts Manager) is not filled if the appropriate libraries almost to the end.
Parameters:
1. value 1 (indicating where the error occurred)
2. value 2 (indicating where the error occurred)
3. may indicate a library
4. may be a reciprocal code HvCheckHive'a, if a library is damaged
0x00000052: MAILSLOT_FILE_SYSTEM
0x00000053: NO_BOOT_DEVICE
0x00000054: LM_SERVER_INTERNAL_ERROR
0x00000055: DATA_COHERENCY_EXCEPTION
0x00000056: INSTRUCTION_COHERENCY_EXCEPTION
0x00000057: XNS_INTERNAL_ERROR
0x00000058: FTDISK_INTERNAL_ERROR
The system booted from the restored primary partition of the array, causing the library report that the mirror is OK, but actually it is not. These images of libraries in the shadow copy. You need to download it from them.
0x00000059: PINBALL_FILE_SYSTEM
0x0000005A: CRITICAL_SERVICE_FAILED
0x0000005B: SET_ENV_VAR_FAILED
0x0000005C: HAL_INITIALIZATION_FAILED
0x0000005D: HEAP_INITIALIZATION_FAILED
0x0000005E: OBJECT_INITIALIZATION_FAILED
0x0000005F: SECURITY_INITIALIZATION_FAILED
0x00000060: PROCESS_INITIALIZATION_FAILED
0x00000061: HAL1_INITIALIZATION_FAILED
0x00000062: OBJECT1_INITIALIZATION_FAILED
0x00000063: SECURITY1_INITIALIZATION_FAILED
0x00000064: SYMBOLIC_INITIALIZATION_FAILED
0x00000065: MEMORY1_INITIALIZATION_FAILED
0x00000066: CACHE_INITIALIZATION_FAILED
0x00000067: CONFIG_INITIALIZATION_FAILED
Error means that the registry could not allocate the necessary space required for operation of the registry files. This error may never occur, since the process of booking a place is at an early stage startup and registry allocated enough space.
Parameters:
1. five
2. Indicates NTOS \ CONFIG \ CMSYSINI, which failed.
0x00000068: FILE_INITIALIZATION_FAILED
0x00000069: IO1_INITIALIZATION_FAILED
Unable to initialize the input-output for unknown reason. This happens if the installer of the system did not detect the hardware during installation, or a user incorrectly reconfiguring the system.
0x0000006A: LPC_INITIALIZATION_FAILED
0x0000006B: PROCESS1_INITIALIZATION_FAILED
Parameters:
1. According to the code of the process, which found that the system initialization is not successful.
2. According to a place in NTOS \ PS \ PSINIT.C, where the error was discovered.
0x0000006C: REFMON_INITIALIZATION_FAILED
0x0000006D: SESSION1_INITIALIZATION_FAILED
0x0000006E: SESSION2_INITIALIZATION_FAILED
0x0000006F: SESSION3_INITIALIZATION_FAILED
0x00000070: SESSION4_INITIALIZATION_FAILED
0x00000071: SESSION5_INITIALIZATION_FAILED
This code of codes (SESSION1 - SESSION5) indicate the place in NTOS \ INIT \ INIT.C, where the error was made.
Parameters:
1. said session code, which decided that the system initialization is not successful.
0x00000072: ASSIGN_DRIVE_LETTERS_FAILED
0x00000073: CONFIG_LIST_FAILED
Indicates that one of the registry files are corrupted or unreadable. Damaged one of the following registry file: SOFTWARE, SECURITY, SAM (Security Accounts Manager). A possible reason is the lack of disk space, or lack of memory.
0x00000074: BAD_SYSTEM_CONFIG_INFO
This error can occur as a result of the fact that the registry file SYSTEM, downloadable via the component NTLDR, is damaged.
This error may also mean that some required registry keys and their options are not available. Download in LastKnownGood (last known good configuration) may solve this problem. But it is possible that you have to reinstall the system, or use a rescue disk.
0x00000075: CANNOT_WRITE_CONFIGURATION
This error can occur when a hive files (SYSTEM and SYSTEM.ALT) can not be recorded additional data at the time of initialization of the registry at the time of the first phase (when there is access to the filesystem). This error means that the disc has no free space, and an attempt was made to maintain the registry on the device read-only.
0x00000076: PROCESS_HAS_LOCKED_PAGES
This error can occur due to a driver that is not completely unloaded after the I / O operations.
Parameters:
1. address of the process
2. the number of closed pages
3. the number of reserved pages
4. zero
0x00000077: KERNEL_STACK_INPAGE_ERROR
Error reading a page of kernel system. The problem is the bad blocks file, virtual memory or disk controller error (very rarely, the cause may be lack of system resources, but rather, may end reserve physical world memory status c0000009a [STATUS_INSUFFICIENT_RESOURCES]).
If the first and second parameters error code is 0, it means that the location of errors in the kernel is not found. This means that the error was caused by bad hardware.
Status of I / O c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL (STATUS_DISK_OPERATION_FAILED) usually means that the information can not be read because of bad blocks in memory. After the reboot, automatic disk check will attempt to address bad blocks in memory. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and virtual memory located on a SCSI disk, check the connection and operation of SCSI devices.
Parameters:
1. zero
2. zero
3. PTE value at the time of error
4. address error kernel
or
1. status code
2. status code input / output
3. number of virtual memory pages
4. Displacement in the paging file
0x00000078: PHASE0_EXCEPTION
0x00000079: MISMATCHED_HAL
The level of verification HAL and HAL configuration type is not suited to the kernel of the system or machine type. This error is most likely due to the fact that the user has manually edited any NTOSKRNL.EXE or HAL.DLL. Car or on multiprocessor HAL (MP) and yuniprotsessornoe kernel (UP), or vice versa.
0x0000007A: KERNEL_DATA_INPAGE_ERROR
Do not read the requested kernel page. Error caused by a bad block in the memory or disk controller error. See also 0x00000077.
Parameters:
1. Type a frozen lock
2. error status (normally code input / output)
3. the current process (virtual address for lock type 3, or PTE)
4. virtual memory address, which can not be moved to the pagefile
0x0000007B: INACCESSIBLE_BOOT_DEVICE
During the install I / O system, the boot device driver might have failed to initialize the device from which the system tries to load, or the file system that was supposed to read that device, or could not be initialized, or simply did not recognize the information on the device, as file system structure. In the above case, the first argument - the address of the Unicode string data structure that is the ARC name of the device from which the boot was being attempted. In the second case, the first argument - the address of the device object that could not be mounted.
If this error occurred during the initial setup of the system, perhaps the system was installed on the drive or SCSI controller, which it is not supported. Keep in mind that some controllers are supported only by drivers from Windows-Library (WDL), which should be set to custom installation.
This error can also occur after installing a new SCSI adapter or disk controller or after changing the system partition. In this case, on x86 systems, you need to edit BOOT.INI.
Parameters:
1. pointer to the device object or Unicode string string (Unicode string), or ARC name.
0x0000007C: BUGCODE_PSS_MESSAGE
0x0000007D: INSTALL_MORE_MEMORY
Not enough RAM to run the core Windows (requires 5 MB)
Parameters:
1. number of physical pages found
2. lower physical page
3. Top physical page
4. zero
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
The problem with the hardware, driver, or encountered a shortage of free disk space. This error can occur when trying to update Windows XP to Service Pack 2 or Service Pack 3 or Windows Vista when you try to upgrade to Service Pack 1. The reason for the error may be related to hardware drivers. Need to roll back changes to the state at the time of installation of Service Pack, or remove installed updates. To resolve this problem you need to update hardware drivers from the manufacturer.
0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Unexpected exception occurred in kernel mode, or interrupt, in which the kernel does not work. Also cause errors can be interrupted, which led to immediate death in the form of a double error - double fault. The first number in the error code - number of interrupts (8 = double fault). To learn more about what kind of interrupt, refer to the manual of the family Intel x86.
In other words, the error occurs when the processor makes a mistake, which the kernel can not cope. Most often the error occurs because of the bad blocks of RAM, and sometimes due to overclocking.
Try disabling the BIOS function synchronous data transfer.
* 0
Comments (12)
Articles "The description of critical errors: A detailed description and methods of eliminating fatal errors on Windows XP and Vista (Part 2)
Author: admin | June 6, 2009 | Views: 8082
0x00000080: NMI_HARDWARE_FAILURE
Failed to initialize the kernel on this machine. HAL should give all the specific information you have, and prompt the user to refer to your hardware vendor for tech support.
0x00000081: SPIN_LOCK_INIT_FAILURE
0x00000085: SETUP_FAILURE
The error occurs when booting the installer of the system in earlier versions of Windows NT. Text form setup'a no longer use the troubleshooting procedures (bugcheck), in order not to create serious interference during installation. So you never encounter this error. All error checking has been replaced by a more friendly and (where possible) a more informative error messages.
0x0000008B: MBR_CHECKSUM_MISMATCH
The error occurs during the boot process when the checksum is MBR, the calculated system does not match the checksum loader. Usually this means the virus. Scan the boot sector of the anti-virus software pre-loaded with the CD.
KerBugCheckEx options:
1 - The signature of the disk to MBR
2 - checksum MBR, written in osloader
3 - Checksum MBR, recorded in the system
0x0000008E: PAGE_FAULT_IN_NON_PAGED_AREA
Incompatibility or fault blocks of RAM. Prodiagnostiruyte memory and replace faulty memory modules.
0x0000008F: PP0_INITIALIZATION_FAILED
Error occurs during initialization of zero-phase Manager Plug and Play in kernel mode. Check the hardware and the system disk.
0x00000090: PP1_INITIALIZATION_FAILED
Error occurs during the initialization phase of the primary manager of Plug and Play in kernel mode. At this point, initialize system files, drivers and the registry. Check the hardware and the system disk.
0x00000092: UP_DRIVER_ON_MP_SYSTEM
The error occurs when a single processor driver is loaded in a system where there is more than one active processor.
KeBugCheckEx options:
1 - Base address uniprocessor driver
0x00000093: INVALID_KERNEL_HANDLE
Error occurs when the kernel code (kernel code) or other critical components of the OS trying to close a handle that is not valid.
Parameters:
1 - Summoned handle NtClose
2 - 0 means that secure the handle has been closed
1 means not closed correctly handle
0x00000094: KERNEL_STACK_LOCKED_AT_EXIT
This message appears when the thread exists, while its stack is marked as blocked. The problem is caused by hardware drivers.
0x00000096: INVALID_WORK_QUEUE_ITEM
The problem is caused by an incorrect hardware drivers.
0x00000097: BOUND_IMAGE_UNSUPPORTED
The problem is caused by an incorrect hardware drivers.
0x00000098: END_OF_NT_EVALUATION_PERIOD
While working demo version of Windows is finished.
Parameters:
1 - Date of installation (the lower 32-bit)
2 - Date of installation (the upper 32-bits)
3 - Trial period in minutes.
0x00000099: INVALID_REGION_OR_SEGMENT
ExInitializeRegion or ExInterlockedExtendRegion were caused by the wrong set of parameters.
0x0000009A: SYSTEM_LICENSE_VIOLATION
Violation occurred Software License Agreement. This can be either due to attempts to change the type of product system, or attempts to change the term of the trial period, the operating system.
0x0000009B: UDFS_FILE_SYSTEM
Has failed to read or write to the media, with the format UDFS. Failure may be associated with damage to the file system, or the appearance of bad sectors on the disk. Also, failure may be associated with the software, changing the structure of the disk (encryption programs, etc.).
0x0000009C: MACHINE_CHECK_EXCEPTION
Fatal Error Machine Check Exception (testing machine). Error is associated with an incorrect hardware configuration, overclocking the processor, volatile memory unit operation, overheating components, unstable power supply operation.
0x0000009F: DRIVER_POWER_STATE_FAILURE
The driver is in an inconsistent or invalid state energy consumption. This usually happens because of failures in the food, when you reboot, exit from hibernate mode, etc. You should replace the failed driver, or uninstall the software that controls the file system (antivirus software, encryption program
0x000000A0: INTERNAL_POWER_ERROR
0x000000A1: PCI_BUS_DRIVER_INTERNAL
0x000000A2: MEMORY_IMAGE_CURRUPT
0x000000A3: ACPI_DRIVER_INTERNAL
0x000000A4: CNSS_FILE_SYSTEM_FILTER
0x000000A5: ACPI_BIOS_ERROR
The reason for this message, repeated failures in the ACPI BIOS. At the level of the operating system can not solve this problem. Requires detailed analysis.
0x000000A7: BAD_EXHANDLE
0x000000AB: SESSION_HAS_VALID_POOL_ON_EXIT
0x000000AC: HAL_MEMORY_ALLOCATION
0x000000B4: VIDEO_DRIVER_INIT_FAILURE
Windows could not load graphics driver. The problem is mainly related to video drivers, or have a hardware conflict with pay movies. Reboot into safe mode and change the video driver to standard.
0x000000B8: ATTEMPTED_SWITCH_FROM_DPC
0x000000B9: CHIPSET_DETECTED_ERROR
0x000000BA: SESSION_HAS_VALID_VIEWS_ON_EXIT
0x000000BB: NETWORK_BOOT_INITIALIZATION_FAILED
0x000000BC: NETWORK_BOOT_DUPLICATE_ADDRESS
0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
The driver attempted to write data to permanent memory (ROM), where you can not record. The problem is mainly associated with the installation of a bad device driver, service, or firmware. Change the driver.
0x000000BF: MUTEX_ALREADY_OWNED
0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Driver to write data to an invalid section of memory. Change the driver.
0x000000C2: BAD_POOL_CALLER
System kernel or the driver gave the wrong command to access memory. As a rule, a bad driver or software caused this error. Change the driver.
0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
The program checks the driver has detected a fatal error in the module generation STOP-error. The accompanying parameters - parameters that are passed to KeBugCheckEx and displayed on a blue screen. Change the driver.
0x000000C5: DRIVER_CORRUPTED_EXPOOL
An attempt to access invalid memory areas of a process IRQL higher level. This error is almost always due to driver who destroyed the system pool. Change the driver.
0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
The driver tried to access freed pool memory. Change the driver.
0x000000C7: TIMER_OR_DPC_INVALID
Core timer or Delayed Procedure Call (DPC) is present in a prohibited area of memory. This error occurs when the driver was unable to complete the core timer or Delayed Procedure Call (DPC) before shipping it from memory. Change the driver.
0x000000C8: IRQL_UNEXPECTED_VALUE
0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
This is a message from one of the managers check the driver. Change the driver.
0x000000CA: PNP_DETECTED_FATAL_ERROR
0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
Error, similar to the STOP-error 0x00000076. Differs from the latter only by the fact that in this case an error identified in the trace of the kernel. This error indicates that the driver or manager input - output can not open the locked pages after an I - O. Note the name applied to the driver window STOP-error. Change the driver.
0x000000CC: PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000CD: PAGE_FAULT_BEYOND_END_OF_ALLOCATION
0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
The driver can not cancel the hovering state of the system. Error usually occurs after the installation of bad drivers or components of the service. Change the driver.
0x000000CF: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
0x000000D0: DRIVER_CORRUPTED_MMPOOL
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system tried to appeal to the paged memory using a kernel process IRQL a high level. The most common cause - a bad device driver. It can also be caused by a defective RAM or a damaged paging file.
0x000000D2: BUGCODE_ID_DRIVER
0x000000D3: DRIVER_PORTION_MUST_BE_NONPAGED
0x000000D4: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
0x000000D5: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000D6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
0x000000D7: DRIVER_UNMAPPING_INVALID_VIEW
0x000000D8: DRIVER_USED_EXCESSIVE_PTES
Error occurs when the driver requests a large amount of kernel memory.
0x000000D9: MUTEX_ALREADY_OWNED
0x000000DA: SYSTEM_PTE_MISUSE
0x000000DB: DRIVER_CORRUPTED_SYSPTES
0x000000DC: DRIVER_INVALID_STACK_ACCESS
0x000000DE: POOL_CORRUPTION_IN_FILE_AREA
0x000000DF: IMPERSONATING_WORKER_THREAD
0x000000E0: ACPI_BIOS_FATAL_ERROR
0x000000E1: WORKER_THREAD_RETURNED_AT_BAD_IRQL
0x000000E2: MANUALLY_INITIATED_CRASH
0x000000E3: RESOURCE_NOT_OWNED
Various crashes related to the file system, this leads to STOP-error. The problem may be related to the driver NTFS.SYS.
0x000000E4: WORKER_INVALID
0x000000E6: DRIVER_VERIFIER_DMA_VIOLATION
0x000000E7: INVALID_FLOATING_POINT_STATE
0x000000E8: INVALID_CANCEL_OF_FILE_OPEN
0x000000E9: ACTIVE_EX_WORKER_THREAD_TERMINATION
0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
Problematic device driver brought the system to hang. Usually this is caused by the display driver when you try to move the computer into Standby mode. This issue is related to the video card or bad video driver.
0x000000EB: DIRTY_MAPPED_PAGES_CONGESTION
0x000000EC: SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT
0x000000ED: UNMOUNTABLE_BOOT_VOLUME
Failure occurred during the connection startup disk. Error can occur on computers with high-performance disk controllers that have not been correctly configured and installed, or connected to faulty cable. After the usual reboot, the system can resume normal operation as if nothing had happened. Also, this error was not shut down Windows, and failure may be associated with damage to the file system.
0x000000EF: CRITICAL_PROCESS_DIED
0x000000F1: SCSI_VERIFIER_DETECTED_VIOLATION
0x000000F2: HARDWARE_INTERRUPT_STORM
This message appears when the kernel detects a storm interrupts, that is, when caused by the level-interrupt device is not in a position to issue an interrupt request. Usually this is caused by a bad device driver.
0x000000F3: DISORDERLY_SHUTDOWN
Completion of Windows has crashed due to lack of memory. Determine what the program got 'out of memory ", try to discover why virtual memory does not provide the required system resources, and explore, refuses to whether the program (or, sometimes, the driver) to complete its work without the release of the open pages in memory.
0x000000F4: CRITICAL_OBJECT_TERMINATION
0x000000F6: PCI_VERIFIER_DETECTED_VIOLATION
0x000000F7: DRIVER_OVERRAN_STACK_BUFFER
0x000000F8: RAMDISK_BOOT_INITIALIZATION_FAILED
0x000000F9: DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN
0x000000FA: HTTP_DRIVER_CORRUPTED
System driver Http.sys damaged. This component should be restored from the original disk.
0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
You attempted to execute a function in the non-complying memory.
Parameters:
1 - The address from which there was an attempt to perform the function
2 - Contents page table entry (PTE)
0x000000FD: DIRTY_NOWRITE_PAGES_CONGESTION
No free-paged memory to continue the basic system operations.
Parameters:
1 - Total amount requested paged memory
2 - Number of the requested paging memory to the inability to write.
3 -
4 - The status code at the time of the last record in page memory
0x000000FE: BUGCODE_USB_DRIVER
A fatal error occurred in the USB controller and related devices. The problem is usually caused by incorrect operation of USB-controller, or malfunction of USB-connected devices. Unplug all USB-devices from your computer and try to disable the USB-controller in the BIOS. Update the driver USB.
0x000000FF: RESERVE_QUEUE_OVERFLOW
0x00000100: LOADER_BLOCK_MISMATCH
0x00000101: CLOCK_WATCHDOG_TIMEOUT
Indicates that the expected termination of sync on the secondary processor in a multiprocessor system has not been received within a certain interval. This processor is not processing interrupts. Typically, this occurs when the processor is not responding, or went into an infinite loop.
Parameters:
1 - Interval timeout interrupt sync, in nominal clock ticks
2 - nil
3 - Location of the control unit CPU (PRCB) for nereagiruemogo processor
4 - nil
0x00000103: MUP_FILE_SYSTEM
0x00000104: AGP_INVALID_ACCESS
Attempt to write the graphics processor to memory, which has not been set aside for this. Error associated with the video driver or an old version of BIOS.
Parameters:
1 - Displacement (in ULONG) within the pages of AGP to the first data ULONG, whose data is destroyed
2 - nil
3 - nil
4 - nil
0x00000105: AGP_GART_CORRUPTION
Error occurs when damaged Graphics Aperture Remapping Table (GART). Error is caused by malfunctioning driver DMA (direct memory access)
Parameters:
1 - Base address (virtual) in the GART
2 - The offset in the GART, which revealed distortion
3 - The base address (virtual) from the cache GART (copy GART)
4 - nil
0x00000106: AGP_ILLEGALLY_REPROGRAMMED
Error is caused by unsigned or corrupted video driver. Replace the video driver.
Parameters:
1 - Original team
2 - Current team
3 - nil
4 - nil
0x00000108: THIRD_PARTY_FILE_SYSTEM_FAILURE
A fatal error occurred in a third-party file system filter. Error can be caused by antivirus software, defragmentation program, data backup and other third party utilities. Try also to increase the swap file and memory.
0x00000109: CRITICAL_STRUCTURE_CORRUPTION
Core of the system found an incorrect code or data corruption. Systems based on the 64-code protected from this error. The problem could be caused by either a memory or driver of a third party.
0x0000010A: APP_TAGGING_INITIALIZATION_FAILED
0x0000010C: FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION
0x0000010D: WDF_VIOLATION
0x0000010E: VIDEO_MEMORY_MANAGEMENT_INTERNAL
Encountered an internal error video driver. The problem with the video driver.
0x0000010F: RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED
In the Resource Manager kernel mode (kernel-mode resource manager) exception occurred.
0x00000111: RECURSIVE_NMI
0x00000112: MSRPC_STATE_VIOLATION
Msrpc.sys system component during the execution returned an error code. The error code specified in the first parameter.
0x00000113: VIDEO_DXGKRNL_FATAL_ERROR
DirectX Graphics Kernel revealed a critical error.
0x00000114: VIDEO_SHADOW_DRIVER_FATAL_ERROR
Shadow video driver has encountered a critical error.
0x00000115: AGP_INTERNAL
In Video Interface AGP video port driver was detected a critical error.
0x00000116: VIDEO_TDR_ERROR
Reset video driver to time out has not been successfully produced.
0x00000117: VIDEO_TDR_TIMEOUT_DETECTED
0x00000119: VIDEO_SCHEDULER_INTERNAL_ERROR
0x0000011A: EM_INITIALIZATION_FAILURE
0x0000011B: DRIVER_RETURNED_HOLDING_CANCEL_LOCK
0x0000011C: ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE
Attempt was made to record in the area of write-protected configuration manager:
Parameters:
1 - Virtual address write command undertaken
2 - Contents PTE
3 - reserved
4 - reserved
Name of the driver tries to write operations, printed as a Unicode string to display errors.
0x0000011D: EVENT_TRACING_FATAL_ERROR
0x00000121: DRIVER_VIOLATION
The driver produced an access violation in one area of memory.
Parameters:
1 - describes the type of violation
2 - reserved
3 - reserved
Use the kernel debugger and view the call stack to determine the driver's name, which produced an access violation.
0x00000122: WHEA_INTERNAL_ERROR
An internal error occurred in the architecture, error detection hardware Windows (Windows Hardware Error Architecture (WHEA))
0x00000124: WHEA_UNCORRECTABLE_ERROR
An error occurred in the computer's hardware. This error is detected the error detection architecture hardware Windows (Windows Hardware Error Architecture (WHEA))
0x00000127: PAGE_NOT_ZERO
Memory page has not been completely filled with zeroes. This error is due to hardware failure, either because of triggering a privileged operating system component that produced a premature change pages in memory.
Parameters:
1 - The virtual memory address that points to the incorrect page.
2 - Physical page number
3 - nil
4 - nil
0x0000012B: FAULTY_HARDWARE_CORRUPTED_PAGE
Detected single bit error (error of bits) per page of memory. This error is related to hardware memory.
Parameters:
1 - The virtual memory address that points to the incorrect page.
2 - Physical page number
3 - nil
4 - nil
0x0000012C: EXFAT_FILE_SYSTEM
Has failed to read or write in the media section, with the format exFat. Failure may be associated with damage to the file system, or the appearance of bad sectors on the disk. Also, failure may be associated with the software, changing the structure of the disk (encryption programs, etc.). This failure relates to the media, formatted for Windows Vista Service Pack 1.
0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
See 0x0000007E
0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M
0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
See 0x0000008E
0x100000EA: THREAD_STUCK_IN_DEVICE_DRIVER_M
0xC000009A: STATUS_INSUFFICIENT_RESOURCES
System kernel operating system has exhausted all system resources for its work, including the swap file. Check disk for errors. Increase the amount of hard disk and RAM.
0xC0000135: UNABLE TO LOCATE DLL
Windows tried to load the DLL library and got an error code. Possible cause - the file is missing or damaged. It is also possible corrupted registry.
0xC0000142: DLL Initialization Failure
This error was caused by a corrupt system DLL library.
0xC0000218: UNKNOWN_HARD_ERROR
Desired system registry can not load. The file may be corrupted or missing (need a rescue disk or reinstall Windows). Registry files might have been destroyed because of damage to the hard disk. The driver may have destroyed the data of the registry when loading into memory or the memory where the registry has been loaded, has a parity error (turn off the external cache and check RAM).
0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
This occurs when Windows switched to privileged mode and user mode subsystem, such as Winlogon or Runtime Subsystem Client / Server (CSRSS), have caused any crashes, and protection can not be guaranteed. Since Windows XP can not run without Winlogon or CSRSS, this - one of the few situations where the failure-mode service can cause the system to stop responding. This can also happen when the computer is restarted after a system administrator has changed the permissions so that the SYSTEM account no longer had adequate resolution to apply to system files and folders. Error can also be caused by damage to the file user32.dll or incorrect system drivers (. Sys)
0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
the driver is corrupted or the system library has been recognized as damaged. The system does everything in order to verify the integrity of critical system files. Blue screen displays the name of the damaged file. If this happens, boot into any other system or, if none, then reinstall the system. Make sure that the version of the file that has been identified as corrupted, the same as the version of the file in the distribution system and if so, replace it with the disc. Permanent errors with different file names, they say that there are problems with media or with the disk controller, where are these files.
0xC0000244
STOP-error occurs when the audit policy setting activates CrashOnAuditFail
0xC000026C
Usually indicates a problem with a device driver.
0xDEADDEAD: MANUALLY_INITIATED_CRASH1
"It's dead, Jim!" (It's dead, Jim!) STOP-This error indicates that the user deliberately initialized the crash, or from the kernel debugger or the keyboard.
0x0000000F: SPIN_LOCK_ALREADY_OWNED
0x00000010: SPIN_LOCK_NOT_OWNED
0x00000011: THREAD_NOT_MUTEX_OWNER
0x00000012: TRAP_CAUSE_UNKNOWN
0x00000013: EMPTY_THREAD_REAPER_LIST
0x00000014: CREATE_DELETE_LOCK_NOT_LOCKED
0x00000015: LAST_CHANCE_CALLED_FROM_KMODE
0x00000016: CID_HANDLE_CREATION
0x00000017: CID_HANDLE_DELETION
0x00000018: REFERENCE_BY_POINTER
0x00000019: BAD_POOL_HEADER
0x0000001A: MEMORY_MANAGEMENT
0x0000001B: PFN_SHARE_COUNT
0x0000001C: PFN_REFERENCE_COUNT
0x0000001D: NO_SPIN_LOCK_AVAILABLE
0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
0x0000001F: SHARED_RESOURCE_CONV_ERROR
0x00000020: KERNEL_APC_PENDING_DURING_EXIT
0x00000021: QUOTA_UNDERFLOW
0x00000022: FILE_SYSTEM
0x00000023: FAT_FILE_SYSTEM
0x00000024: NTFS_FILE_SYSTEM
0x00000025: NPFS_FILE_SYSTEM
0x00000026: CDFS_FILE_SYSTEM
0x00000028: CORRUPT_ACCESS_TOKEN
0x00000029: SECURITY_SYSTEM
0x0000002A: INCONSISTENT_IRP
0x0000002B: PANIC_STACK_SWITCH
0x0000002C: PORT_DRIVER_INTERNAL
0x0000002D: SCSI_DISK_DRIVER_INTERNAL
0x0000002E: DATA_BUS_ERROR
0x0000002F: INSTRUCTION_BUS_ERROR
0x00000030: SET_OF_INVALID_CONTEXT
0x00000031: PHASE0_INITIALIZATION_FAILED
0x00000032: PHASE1_INITIALIZATION_FAILED
0x00000033: UNEXPECTED_INITIALIZATION_CALL
0x00000034: CACHE_MANAGER
0x00000035: NO_MORE_IRP_STACK_LOCATIONS
0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO 0x00000037: FLOPPY_INTERNAL_ERROR
0x00000038: SERIAL_DRIVER_INTERNAL
0x00000039: SYSTEM_EXIT_OWNED_MUTEX
0x0000003A: SYSTEM_UNWIND_PREVIOUS_USER
0x0000003B: SYSTEM_SERVICE_EXCEPTION
0x0000003C: INTERRUPT_UNWIND_ATTEMPTED
0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED
0x0000003E: MULTIPROCESSOR_CONFIGURATION
_NOT_SUPPORTED
0x0000003F: NO_MORE_SYSTEM_PTES
0x00000040: TARGET_MDL_TOO_SMALL
0x00000041: MUST_SUCCEED_POOL_EMPTY
0x00000042: ATDISK_DRIVER_INTERNAL
0x00000043: NO_SUCH_PARTITION
0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS
0x00000045: INSUFFICIENT_SYSTEM_MAP_REGS
0x00000046: DEREF_UNKNOWN_LOGON_SESSION
0x00000047: REF_UNKNOWN_LOGON_SESSION
0x00000048: CANCEL_STATE_IN_COMPLETED_IRP
0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF
0x0000004A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
0x0000004B: STREAMS_INTERNAL_ERROR
0x0000004C: FATAL_UNHANDLED_HARD_ERROR
0x0000004D: NO_PAGES_AVAILABLE
0x0000004E: PFN_LIST_CORRUPT
0x0000004F: NDIS_INTERNAL_ERROR
0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
0x00000051: REGISTRY_ERROR
0x00000052: MAILSLOT_FILE_SYSTEM
0x00000053: NO_BOOT_DEVICE
0x00000054: LM_SERVER_INTERNAL_ERROR
0x00000055: DATA_COHERENCY_EXCEPTION
0x00000056: INSTRUCTION_COHERENCY_EXCEPTION
0x00000057: XNS_INTERNAL_ERROR
0x00000058: FTDISK_INTERNAL_ERROR
0x00000059: PINBALL_FILE_SYSTEM
0x0000005A: CRITICAL_SERVICE_FAILED
0x0000005B: SET_ENV_VAR_FAILED
0x0000005C: HAL_INITIALIZATION_FAILED
0x0000005D: UNSUPPORTED_PROCESSOR
0x0000005E: OBJECT_INITIALIZATION_FAILED
0x0000005F: SECURITY_INITIALIZATION_FAILED
0x00000060: PROCESS_INITIALIZATION_FAILED
0x00000061: HAL1_INITIALIZATION_FAILED
0x00000062: OBJECT1_INITIALIZATION_FAILED
0x00000063: SECURITY1_INITIALIZATION_FAILED
0x00000064: SYMBOLIC_INITIALIZATION_FAILED
0x00000065: MEMORY1_INITIALIZATION_FAILED
0x00000066: CACHE_INITIALIZATION_FAILED
0x00000067: CONFIG_INITIALIZATION_FAILED
0x00000068: FILE_INITIALIZATION_FAILED
0x00000069: IO1_INITIALIZATION_FAILED
0x0000006A: LPC_INITIALIZATION_FAILED
0x0000006B: PROCESS1_INITIALIZATION_FAILED
0x0000006C: REFMON_INITIALIZATION_FAILED
0x0000006D: SESSION1_INITIALIZATION_FAILED
0x0000006E: SESSION2_INITIALIZATION_FAILED
0x0000006F: SESSION3_INITIALIZATION_FAILED
0x00000070: SESSION4_INITIALIZATION_FAILED
0x00000071: SESSION5_INITIALIZATION_FAILED
0x00000072: ASSIGN_DRIVE_LETTERS_FAILED
0x00000073: CONFIG_LIST_FAILED
0x00000074: BAD_SYSTEM_CONFIG_INFO
0x00000075: CANNOT_WRITE_CONFIGURATION
0x00000076: PROCESS_HAS_LOCKED_PAGES
0x00000077: KERNEL_STACK_INPAGE_ERROR
0x00000078: PHASE0_EXCEPTION
0x00000079: MISMATCHED_HAL
0x0000007A: KERNEL_DATA_INPAGE_ERROR
0x0000007B: INACCESSIBLE_BOOT_DEVICE
0x0000007C: BUGCODE_NDIS_DRIVER
0x0000007D: INSTALL_MORE_MEMORY
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
0x00000080: NMI_HARDWARE_FAILURE
0x00000081: SPIN_LOCK_INIT_FAILURE
0x00000082: DFS_FILE_SYSTEM
0x00000083: OFS_FILE_SYSTEM
0x00000084: RECOM_DRIVER
0x00000085: SETUP_FAILURE
0x00000086: Undetermined
0x00000087: Undetermined
0x00000088: Undetermined
0x00000089: Undetermined
0x0000008A: Undetermined
0x0000008B: MBR_CHECKSUM_MISMATCH
0x0000008D: Undetermined
0x0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED
0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
0x0000008F: PP0_INITIALIZATION_FAILED
0x00000090: PP1_INITIALIZATION_FAILED
0x00000091: WIN32K_INIT_OR_RIT_FAILURE
0x00000092: UP_DRIVER_ON_MP_SYSTEM
0x00000093: INVALID_KERNEL_HANDLE
0x00000094: KERNEL_STACK_LOCKED_AT_EXIT
0x00000095: PNP_INTERNAL_ERROR
0x00000096: INVALID_WORK_QUEUE_ITEM
0x00000097: BOUND_IMAGE_UNSUPPORTED
0x00000098: END_OF_NT_EVALUATION_PERIOD
0x00000099: INVALID_REGION_OR_SEGMENT
0x0000009A: SYSTEM_LICENSE_VIOLATION
0x0000009B: UDFS_FILE_SYSTEM
0x0000009C: MACHINE_CHECK_EXCEPTION
0x0000009D: Undetermined
0x0000009E: Undetermined
0x0000009F: DRIVER_POWER_STATE_FAILURE
0x000000A0: INTERNAL_POWER_ERROR
0x000000A1: PCI_BUS_DRIVER_INTERNAL
0x000000A2: MEMORY_IMAGE_CURRUPT
0x000000A3: ACPI_DRIVER_INTERNAL
0x000000A4: CNSS_FILE_SYSTEM_FILTER
0x000000A5: ACPI_BIOS_ERROR
0x000000A6: Undetermined
0x000000A7: BAD_EXHANDLE
0x000000A8: Undetermined
0x000000A9: Undetermined
0x000000AA: Undetermined
0x000000AB: SESSION_HAS_VALID_POOL_ON_EXIT
0x000000AC: HAL_MEMORY_ALLOCATION
0x000000AD: Undetermined
0x000000AE: Undetermined
0x000000AF: Undetermined
0x000000B0: Undetermined
0x000000B1: Undetermined
0x000000B2: Undetermined
0x000000B3: Undetermined
0x000000B4: VIDEO_DRIVER_INIT_FAILURE
0x000000B5: Undetermined
0x000000B6: Undetermined
0x000000B7: Undetermined
0x000000B8: ATTEMPTED_SWITCH_FROM_DPC
0x000000B9: CHIPSET_DETECTED_ERROR
0x000000BA: SESSION_HAS_VALID_VIEWS_ON_EXIT
0x000000BB: NETWORK_BOOT_INITIALIZATION_FAILED
0x000000BC: NETWORK_BOOT_DUPLICATE_ADDRESS
0x000000BD: Undetermined
0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
0x000000BF: MUTEX_ALREADY_OWNED
0x000000C0: Undetermined
0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION 0x000000C2: BAD_POOL_CALLER
0x000000C3: Undetermined
0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
0x000000C5: DRIVER_CORRUPTED_EXPOOL
0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
0x000000C7: TIMER_OR_DPC_INVALID
0x000000C8: IRQL_UNEXPECTED_VALUE
0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
0x000000CA: PNP_DETECTED_FATAL_ERROR
0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
0x000000CC: PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000CD: PAGE_FAULT_BEYOND_END_OF_ALLOCATION
0x000000CE: DRIVER_UNLOADED_WITHOUT_
CANCE LLING_PENDING_OPERATIONS
0x000000CF: TERMINAL_SERVER_DRIVER_MADE_
INCORRECT_MEMORY_REFERENCE
0x000000D0: DRIVER_CORRUPTED_MMPOOL
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
0x000000D2: BUGCODE_ID_DRIVER
0x000000D3: DRIVER_PORTION_MUST_BE_NONPAGED
0x000000D4: SYSTEM_SCAN_AT_RAISED_IRQL_
CAUGHT_IMPROPER_DRIVER_UNLOAD
0x000000D5: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000D6: DRIVER_PAGE_FAULT_BEYOND_
END_OF_ALLOCATION
0x000000D7: DRIVER_UNMAPPING_INVALID_VIEW
0x000000D8: DRIVER_USED_EXCESSIVE_PTES
0x000000D9: MUTEX_ALREADY_OWNED
0x000000DA: SYSTEM_PTE_MISUSE
0x000000DB: DRIVER_CORRUPTED_SYSPTES
0x000000DC: DRIVER_INVALID_STACK_ACCESS
0x000000DD: Undetermined
0x000000DE: POOL_CORRUPTION_IN_FILE_AREA
0x000000DF: IMPERSONATING_WORKER_THREAD
0x000000E0: ACPI_BIOS_FATAL_ERROR
0x000000E1: WORKER_THREAD_RETURNED_AT_BAD_IRQL
0x000000E2: MANUALLY_INITIATED_CRASH
0x000000E3: RESOURCE_NOT_OWNED
0x000000E4:E5: Undetermined
0x000000E6: DRIVER_VERIFIER_DMA_VIOLATION
0x000000E7: INVALID_FLOATING_POINT_STATE
0x000000E8: INVALID_CANCEL_OF_FILE_OPEN
0x000000E9: ACTIVE_EX_WORKER_THREAD_TERMINATION
0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
0x000000EB: DIRTY_MAPPED_PAGES_CONGESTION
0x000000EC: SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT
0x000000ED: UNMOUNTABLE_BOOT_VOLUME
0x000000EE: Undetermined
0x000000EF: CRITICAL_PROCESS_DIED
0x000000F0: Undetermined
0x000000F1: SCSI_VERIFIER_DETECTED_VIOLATION
0x000000F2: HARDWARE_INTERRUPT_STORM
0x000000F3: DISORDERLY_SHUTDOWN
0x000000F4: CRITICAL_OBJECT_TERMINATION
0x000000F5: Undetermined
0x000000F6: PCI_VERIFIER_DETECTED_VIOLATION
0x000000F7: DRIVER_OVERRAN_STACK_BUFFER
0x000000F8: RAMDISK_BOOT_INITIALIZATION_FAILED
0x000000F9: DRIVER_RETURNED_STATUS_
REPARSE_FOR_VOLUME_OPEN
0x000000FA: Undetermined
0x000000FB: Undetermined
0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
0x000000FD: Undetermined
0x000000FE: BUGCODE_USB_DRIVER
0x000000FF: Undetermined
0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M
0x100000EA: THREAD_STUCK_IN_DEVICE_DRIVER_M
0xC000009A: STATUS_INSUFFICIENT_RESOURCES
0xC0000135: UNABLE_TO_LOCATE_DLL
0xC0000142: DLL Initialization Failure
0xC0000218: UNKNOWN_HARD_ERROR
0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
0xC0000244
0xC000026C
0xDEADDEAD: MANUALLY_INITIATED_CRASH1
This list contains brief the causes of fatal errors for the operating systems Windows 3.51, 4.0, Wndows 2000, Windows XP, Windows Vista. Methods for their removal are described in another article.
0x00000001: APC_INDEX_MISMATCH
Internal Error kernel (kernel). The problem is mostly with problems in drivers
lack of memory or disk space.
0x00000002: DEVICE_QUEUE_NOT_BUSY
0x00000003: INVALID_AFFINITY_SET
0x00000004: INVALID_DATA_ACCESS_TRAP
0x00000005: INVALID_PROCESS_ATTACH_ATTEMPT
0x00000006: INVALID_PROCESS_DETACH_ATTEMPT
0x00000007: INVALID_SOFTWARE_INTERRUPT
0x00000008: IRQL_NOT_DISPATCH_LEVEL
0x00000009: IRQL_NOT_GREATER_OR_EQUAL
0x0000000A: IRQL_NOT_LESS_OR_EQUAL
There was an interference in the virtual memory on the internal process of high-level IRQ.
The most common cause of - the device driver uses an incorrect address.
The error occurs because of bad drivers. Rarely occurs because of malfunction of one of the devices in the system.
Parameters:
1 - the address to which you are wrong treatment
2 - IRQL, which was used to access memory
3 - type of memory access: 0 = read operation, 1 = write operation
4 - address of instruction that has requested access to memory at
0x0000000B: NO_EXCEPTION_HANDLING_SUPPORT
0x0000000C: MAXIMUM_WAIT_OBJECTS_EXCEEDED
0x0000000D: MUTEX_LEVEL_NUMBER_VIOLATION
0x0000000E: NO_USER_MODE_CONTEXT
0x0000000F: SPIN_LOCK_ALREADY_OWNED
0x00000010: SPIN_LOCK_NOT_OWNED
0x00000011: THREAD_NOT_MUTEX_OWNER
0x00000012: TRAP_CAUSE_UNKNOWN
0x00000013: EMPTY_THREAD_REAPER_LIST
0x00000014: CREATE_DELETE_LOCK_NOT_LOCKED
0x00000015: LAST_CHANCE_CALLED_FROM_KMODE
0x00000016: CID_HANDLE_CREATION
0x00000017: CID_HANDLE_DELETION
0x00000018: REFERENCE_BY_POINTER
0x00000019: BAD_POOL_HEADER
0x0000001A: MEMORY_MANAGEMENT
0x0000001B: PFN_SHARE_COUNT
0x0000001C: PFN_REFERENCE_COUNT
0x0000001D NO_SPIN_LOCK_AVAILABLE
0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
This is a very common mistake. Usually excluded address points to the driver or function that caused the stop screen. Always pay attention not only to the specified driver, but also to address itself or an image that contains this error. Usually, this exception code 0x80000003. This error means that the point of interruption or handler is initialized when accessing memory, but the system is booted with / NODEBUG key. This error can not occur too often. If the error appears constantly, make sure that the debugger (debugger) is connected and the system is booted with / DEBUG switch.
On non-Intel systems, if the exception address - 0XBFC0304, an error occurs because the processor cache. If the error occurs permanently please contact the manufacturer of the processor.
As a rule, requires an analysis of the second parameter of the message, which indicates the address of the driver / function that was causing the problem.
Parameters:
1 - Code Exception
2 - address the processing of which failed
3 - Parameter 0 - the exception
4 - Option 1 - the exception
0x0000001F: SHARED_RESOURCE_CONV_ERROR
0x00000020: KERNEL_APC_PENDING_DURING_EXIT
Name of error indicates a damaged / disabled APC counter. If you have this situation, check all file systems are installed on the machine, for example using a rescue package EMRD.
Current IRQL should be zero. If the IRQ is not zero, then a certain order of unloading drivers, when returning to a higher level of IRQ, may cause errors. Try to remember what you did or what applications are closed, what drivers were installed at the time the blue screen. This symptom indicates a serious problem in third-party drivers.
Parameters:
1 - address of APC, at the time of the crash.
2 - Failed thread APC
3 - the current IRQ level
0x00000021: QUOTA_UNDERFLOW
0x00000022: FILE_SYSTEM
0x00000023: FAT_FILE_SYSTEM
Has failed to read or write to the hard disk partition formatted with FAT. Failure may be associated with damage to the file system, or the appearance of bad sectors on the disk. Also, failure may be associated with the software, changing the structure of the disk (encryption programs, etc.).
0x00000024: NTFS_FILE_SYSTEM
Has failed to read or write to the hard disk partition formatted with NTFS. Failure may be associated with damage to the file system, or the appearance of bad sectors on the disk. Also, failure may be associated with the software, changing the structure of the disk (encryption programs, etc.).
0x00000025: NPFS_FILE_SYSTEM
0x00000026: CDFS_FILE_SYSTEM
0x00000027: RDR_FILE_SYSTEM
0x00000028: CORRUPT_ACCESS_TOKEN
0x00000029: SECURITY_SYSTEM
0x0000002A: INCONSISTENT_IRP
I / O Request Packet (IRP) is not functioning, occurs when a field or several fields are incorrect compared to the preserved state of IRP. For example, IRP was already disabled when the driver of a device waiting for the team.
Parameters:
1 - address to which IRP was found in idle mode
0x0000002B: PANIC_STACK_SWITCH
This error occurs when the domain of kernel stack is full. Error occurs when the kernel driver uses too much space in the stack. Possible cause of error may also be damage to the nucleus.
0x0000002C: PORT_DRIVER_INTERNAL
0x0000002D: SCSI_DISK_DRIVER_INTERNAL
0x0000002E: DATA_BUS_ERROR
This STOP-error often occurs due to a failure of memory. This can happen when a driver tries to access a memory address that does not exist.
Parameters:
1 - the virtual memory address that caused the error
2 - physical address of the causes of errors
3 - check the status of the processor (PSR)
4 - Registration instructions error (FIR)
0x0000002F: INSTRUCTION_BUS_ERROR
0x00000030: SET_OF_INVALID_CONTEXT
0x00000031: PHASE0_INITIALIZATION_FAILED
System initialization failed to complete at an early stage (phase 0). Need to examine in more detail the error, as this error code does not say anything practical.
0x00000032: PHASE1_INITIALIZATION_FAILED
System initialization failed to complete at a late stage (Phase 1). Need to examine in more detail the error, as this error code does not say anything practical.
Parameters:
1 - Code-level system, which describes, for whatever reason, the system considers that the initialization is not completed
2 - indicates the location within INIT.C, where the error occurred initializing phase 1
0x00000033: UNEXPECTED_INITIALIZATION_CALL
0x00000034: CACHE_MANAGER
0x00000035: NO_MORE_IRP_STACK_LOCATIONS
Driver high-level driver tried to call low-level interface IoCallDriver (), but the system did not have space in the stack, for this reason that low-level drivers will not reach the required parameters, since it generally has no parameters. This is a fatal situation, since high-level driver believes that the settings for the driver filled the lower level (something he had done to cause low-level drivers). Nevertheless, since there is no free space in the stack was overwritten by the end of the package. This often occurs because of damage to the stack memory. Should be checked for errors and memory drivers.
Parameters:
1 - e IRP
0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO
The device driver was trying to remove from your system one component of a device, but the reference count of this component was not equal to zero - this means that for this component are some outstanding problems (counter indicates the error code, which is why this component can not be unloaded). This is an error calling the driver.
Parameters:
1 - Address object
0x00000037: FLOPPY_INTERNAL_ERROR
0x00000038: SERIAL_DRIVER_INTERNAL
0x00000039: SYSTEM_EXIT_OWNED_MUTEX
0x0000003A: SYSTEM_UNWIND_PREVIOUS_USER
0x0000003B: SYSTEM_SERVICE_EXCEPTION
0x0000003C: INTERRUPT_UNWIND_ATTEMPTED
0x0000003D: INTERRUPT_EXCEPTION_NOT_HANDLED
0x0000003E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED
Multiprocessor system is not symmetric with respect to each other. For proper symmetry, the processors must be the same type and level. For example, attempts to use a processor-level Pentium and 80486 at the same time, causing havoc. Additionally, on x86 systems, the possibility of floating point calculations must be either on all processors, or no one.
0x0000003F: NO_MORE_SYSTEM_PTES
Not enough RTE (page file entries - access points to the swap file). Usually the cause is a driver that is bad clears the paging file (swap) and it overflows. Also, the cause may be excessive fragmentation of the paging file.
0x00000040: TARGET_MDL_TOO_SMALL
The driver called function IoBuildPartialMdl () and handed him a MDL, to identify the source of the MDL, but the recipient scope MDL is not large enough to display the limits of the desired address. This is a driver error.
0x00000041: MUST_SUCCEED_POOL_EMPTY
Driver sought in place Must Suceed Pool. This feature may not be feasible, since the system does not allocate seats in Must Suceed Pool. Replace or upgrade the faulty driver system.
Parameters:
1 - magnitude of the required request
2 - Number of used pages
3 - the number of requested pages
4 - number of pages available
0x00000042: ATDISK_DRIVER_INTERNAL
0x00000043: NO_SUCH_PARTITION
0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS
The driver asked for the completion of IRP [IoCompleteRequest ()], but the package has already been completed. This error is difficult to detect. Possible cause - the driver tries to complete the same operation several times. A rare cause - 2 different drivers trying to seize the package and complete it. The first usually works, but second to none. Keep track of which driver is made difficult, since traces of the first drivers have been rewritten second.
Parameters:
1 - e IRP
0x00000045: INSUFFICIENT_SYSTEM_MAP_REGS
0x00000046: DEREF_UNKNOWN_LOGON_SESSION
0x00000047: REF_UNKNOWN_LOGON_SESSION
0x00000048: CANCEL_STATE_IN_COMPLETED_IRP
This error indicates that the I / O Request Packet (IRP), which should be completed, the order of cancellation specified in it the same, ie This means that the package in this mode can be canceled. Nevertheless, the package does not include more than the driver, as he had already entered the stage of completion.
Parameters:
1 - e IRP
0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF
Pagination error when accessing memory, and switched off interrupts IRQ. The error description is the same as that of 0x0000000A.
0x0000004A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
0x0000004B: STREAMS_INTERNAL_ERROR
0x0000004C: FATAL_UNHANDLED_HARD_ERROR
Critical unrecognized error. The most likely reasons for this are described in the 0xC0000218, 0xC000022A or 0xC0000221.
0x0000004D: NO_PAGES_AVAILABLE
No more free-paged memory to complete the operation. Check the available disk space. Replace the driver.
Parameters:
1 - number of pages used
2 - number of physical pages on the machine
3 - enhanced the value of pages
4 - Total value of pages
0x0000004E: PFN_LIST_CORRUPT
Reason - Damaged / defective structure of the I / O driver.
Parameters:
1. value 1
2. value ListHead, which damaged
3. number of pages available
4. zero
1. value 2
2. data that can be removed
3. maximum number of physical pages
4. result of the deleted data
0x0000004F: NDIS_INTERNAL_ERROR
0x00000050: PAGE_FAULT_IN_NONPAGED_AREA
Occurs when the information requested was not found in memory. The system checks the swap file (page file), but the missing information was identified, it is impossible to write to the swap file (page file).
Parameters:
1. points to an address in memory, which is a mistake
0x00000051: REGISTRY_ERROR
An I / O error with the registry when the system tried to read one of his files, it follows that the error could be caused by hardware problems or damage to the system itself. It can also mean that the error was caused by the update operation, which uses only the security system and this error occurs when resources are running low. If this error occurs, check whether the machine is PDC or BDC, and how many accounts in the database SAM (Security Accounts Manager) is not filled if the appropriate libraries almost to the end.
Parameters:
1. value 1 (indicating where the error occurred)
2. value 2 (indicating where the error occurred)
3. may indicate a library
4. may be a reciprocal code HvCheckHive'a, if a library is damaged
0x00000052: MAILSLOT_FILE_SYSTEM
0x00000053: NO_BOOT_DEVICE
0x00000054: LM_SERVER_INTERNAL_ERROR
0x00000055: DATA_COHERENCY_EXCEPTION
0x00000056: INSTRUCTION_COHERENCY_EXCEPTION
0x00000057: XNS_INTERNAL_ERROR
0x00000058: FTDISK_INTERNAL_ERROR
The system booted from the restored primary partition of the array, causing the library report that the mirror is OK, but actually it is not. These images of libraries in the shadow copy. You need to download it from them.
0x00000059: PINBALL_FILE_SYSTEM
0x0000005A: CRITICAL_SERVICE_FAILED
0x0000005B: SET_ENV_VAR_FAILED
0x0000005C: HAL_INITIALIZATION_FAILED
0x0000005D: HEAP_INITIALIZATION_FAILED
0x0000005E: OBJECT_INITIALIZATION_FAILED
0x0000005F: SECURITY_INITIALIZATION_FAILED
0x00000060: PROCESS_INITIALIZATION_FAILED
0x00000061: HAL1_INITIALIZATION_FAILED
0x00000062: OBJECT1_INITIALIZATION_FAILED
0x00000063: SECURITY1_INITIALIZATION_FAILED
0x00000064: SYMBOLIC_INITIALIZATION_FAILED
0x00000065: MEMORY1_INITIALIZATION_FAILED
0x00000066: CACHE_INITIALIZATION_FAILED
0x00000067: CONFIG_INITIALIZATION_FAILED
Error means that the registry could not allocate the necessary space required for operation of the registry files. This error may never occur, since the process of booking a place is at an early stage startup and registry allocated enough space.
Parameters:
1. five
2. Indicates NTOS \ CONFIG \ CMSYSINI, which failed.
0x00000068: FILE_INITIALIZATION_FAILED
0x00000069: IO1_INITIALIZATION_FAILED
Unable to initialize the input-output for unknown reason. This happens if the installer of the system did not detect the hardware during installation, or a user incorrectly reconfiguring the system.
0x0000006A: LPC_INITIALIZATION_FAILED
0x0000006B: PROCESS1_INITIALIZATION_FAILED
Parameters:
1. According to the code of the process, which found that the system initialization is not successful.
2. According to a place in NTOS \ PS \ PSINIT.C, where the error was discovered.
0x0000006C: REFMON_INITIALIZATION_FAILED
0x0000006D: SESSION1_INITIALIZATION_FAILED
0x0000006E: SESSION2_INITIALIZATION_FAILED
0x0000006F: SESSION3_INITIALIZATION_FAILED
0x00000070: SESSION4_INITIALIZATION_FAILED
0x00000071: SESSION5_INITIALIZATION_FAILED
This code of codes (SESSION1 - SESSION5) indicate the place in NTOS \ INIT \ INIT.C, where the error was made.
Parameters:
1. said session code, which decided that the system initialization is not successful.
0x00000072: ASSIGN_DRIVE_LETTERS_FAILED
0x00000073: CONFIG_LIST_FAILED
Indicates that one of the registry files are corrupted or unreadable. Damaged one of the following registry file: SOFTWARE, SECURITY, SAM (Security Accounts Manager). A possible reason is the lack of disk space, or lack of memory.
0x00000074: BAD_SYSTEM_CONFIG_INFO
This error can occur as a result of the fact that the registry file SYSTEM, downloadable via the component NTLDR, is damaged.
This error may also mean that some required registry keys and their options are not available. Download in LastKnownGood (last known good configuration) may solve this problem. But it is possible that you have to reinstall the system, or use a rescue disk.
0x00000075: CANNOT_WRITE_CONFIGURATION
This error can occur when a hive files (SYSTEM and SYSTEM.ALT) can not be recorded additional data at the time of initialization of the registry at the time of the first phase (when there is access to the filesystem). This error means that the disc has no free space, and an attempt was made to maintain the registry on the device read-only.
0x00000076: PROCESS_HAS_LOCKED_PAGES
This error can occur due to a driver that is not completely unloaded after the I / O operations.
Parameters:
1. address of the process
2. the number of closed pages
3. the number of reserved pages
4. zero
0x00000077: KERNEL_STACK_INPAGE_ERROR
Error reading a page of kernel system. The problem is the bad blocks file, virtual memory or disk controller error (very rarely, the cause may be lack of system resources, but rather, may end reserve physical world memory status c0000009a [STATUS_INSUFFICIENT_RESOURCES]).
If the first and second parameters error code is 0, it means that the location of errors in the kernel is not found. This means that the error was caused by bad hardware.
Status of I / O c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL (STATUS_DISK_OPERATION_FAILED) usually means that the information can not be read because of bad blocks in memory. After the reboot, automatic disk check will attempt to address bad blocks in memory. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and virtual memory located on a SCSI disk, check the connection and operation of SCSI devices.
Parameters:
1. zero
2. zero
3. PTE value at the time of error
4. address error kernel
or
1. status code
2. status code input / output
3. number of virtual memory pages
4. Displacement in the paging file
0x00000078: PHASE0_EXCEPTION
0x00000079: MISMATCHED_HAL
The level of verification HAL and HAL configuration type is not suited to the kernel of the system or machine type. This error is most likely due to the fact that the user has manually edited any NTOSKRNL.EXE or HAL.DLL. Car or on multiprocessor HAL (MP) and yuniprotsessornoe kernel (UP), or vice versa.
0x0000007A: KERNEL_DATA_INPAGE_ERROR
Do not read the requested kernel page. Error caused by a bad block in the memory or disk controller error. See also 0x00000077.
Parameters:
1. Type a frozen lock
2. error status (normally code input / output)
3. the current process (virtual address for lock type 3, or PTE)
4. virtual memory address, which can not be moved to the pagefile
0x0000007B: INACCESSIBLE_BOOT_DEVICE
During the install I / O system, the boot device driver might have failed to initialize the device from which the system tries to load, or the file system that was supposed to read that device, or could not be initialized, or simply did not recognize the information on the device, as file system structure. In the above case, the first argument - the address of the Unicode string data structure that is the ARC name of the device from which the boot was being attempted. In the second case, the first argument - the address of the device object that could not be mounted.
If this error occurred during the initial setup of the system, perhaps the system was installed on the drive or SCSI controller, which it is not supported. Keep in mind that some controllers are supported only by drivers from Windows-Library (WDL), which should be set to custom installation.
This error can also occur after installing a new SCSI adapter or disk controller or after changing the system partition. In this case, on x86 systems, you need to edit BOOT.INI.
Parameters:
1. pointer to the device object or Unicode string string (Unicode string), or ARC name.
0x0000007C: BUGCODE_PSS_MESSAGE
0x0000007D: INSTALL_MORE_MEMORY
Not enough RAM to run the core Windows (requires 5 MB)
Parameters:
1. number of physical pages found
2. lower physical page
3. Top physical page
4. zero
0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
The problem with the hardware, driver, or encountered a shortage of free disk space. This error can occur when trying to update Windows XP to Service Pack 2 or Service Pack 3 or Windows Vista when you try to upgrade to Service Pack 1. The reason for the error may be related to hardware drivers. Need to roll back changes to the state at the time of installation of Service Pack, or remove installed updates. To resolve this problem you need to update hardware drivers from the manufacturer.
0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
Unexpected exception occurred in kernel mode, or interrupt, in which the kernel does not work. Also cause errors can be interrupted, which led to immediate death in the form of a double error - double fault. The first number in the error code - number of interrupts (8 = double fault). To learn more about what kind of interrupt, refer to the manual of the family Intel x86.
In other words, the error occurs when the processor makes a mistake, which the kernel can not cope. Most often the error occurs because of the bad blocks of RAM, and sometimes due to overclocking.
Try disabling the BIOS function synchronous data transfer.
* 0
Comments (12)
Articles "The description of critical errors: A detailed description and methods of eliminating fatal errors on Windows XP and Vista (Part 2)
Author: admin | June 6, 2009 | Views: 8082
0x00000080: NMI_HARDWARE_FAILURE
Failed to initialize the kernel on this machine. HAL should give all the specific information you have, and prompt the user to refer to your hardware vendor for tech support.
0x00000081: SPIN_LOCK_INIT_FAILURE
0x00000085: SETUP_FAILURE
The error occurs when booting the installer of the system in earlier versions of Windows NT. Text form setup'a no longer use the troubleshooting procedures (bugcheck), in order not to create serious interference during installation. So you never encounter this error. All error checking has been replaced by a more friendly and (where possible) a more informative error messages.
0x0000008B: MBR_CHECKSUM_MISMATCH
The error occurs during the boot process when the checksum is MBR, the calculated system does not match the checksum loader. Usually this means the virus. Scan the boot sector of the anti-virus software pre-loaded with the CD.
KerBugCheckEx options:
1 - The signature of the disk to MBR
2 - checksum MBR, written in osloader
3 - Checksum MBR, recorded in the system
0x0000008E: PAGE_FAULT_IN_NON_PAGED_AREA
Incompatibility or fault blocks of RAM. Prodiagnostiruyte memory and replace faulty memory modules.
0x0000008F: PP0_INITIALIZATION_FAILED
Error occurs during initialization of zero-phase Manager Plug and Play in kernel mode. Check the hardware and the system disk.
0x00000090: PP1_INITIALIZATION_FAILED
Error occurs during the initialization phase of the primary manager of Plug and Play in kernel mode. At this point, initialize system files, drivers and the registry. Check the hardware and the system disk.
0x00000092: UP_DRIVER_ON_MP_SYSTEM
The error occurs when a single processor driver is loaded in a system where there is more than one active processor.
KeBugCheckEx options:
1 - Base address uniprocessor driver
0x00000093: INVALID_KERNEL_HANDLE
Error occurs when the kernel code (kernel code) or other critical components of the OS trying to close a handle that is not valid.
Parameters:
1 - Summoned handle NtClose
2 - 0 means that secure the handle has been closed
1 means not closed correctly handle
0x00000094: KERNEL_STACK_LOCKED_AT_EXIT
This message appears when the thread exists, while its stack is marked as blocked. The problem is caused by hardware drivers.
0x00000096: INVALID_WORK_QUEUE_ITEM
The problem is caused by an incorrect hardware drivers.
0x00000097: BOUND_IMAGE_UNSUPPORTED
The problem is caused by an incorrect hardware drivers.
0x00000098: END_OF_NT_EVALUATION_PERIOD
While working demo version of Windows is finished.
Parameters:
1 - Date of installation (the lower 32-bit)
2 - Date of installation (the upper 32-bits)
3 - Trial period in minutes.
0x00000099: INVALID_REGION_OR_SEGMENT
ExInitializeRegion or ExInterlockedExtendRegion were caused by the wrong set of parameters.
0x0000009A: SYSTEM_LICENSE_VIOLATION
Violation occurred Software License Agreement. This can be either due to attempts to change the type of product system, or attempts to change the term of the trial period, the operating system.
0x0000009B: UDFS_FILE_SYSTEM
Has failed to read or write to the media, with the format UDFS. Failure may be associated with damage to the file system, or the appearance of bad sectors on the disk. Also, failure may be associated with the software, changing the structure of the disk (encryption programs, etc.).
0x0000009C: MACHINE_CHECK_EXCEPTION
Fatal Error Machine Check Exception (testing machine). Error is associated with an incorrect hardware configuration, overclocking the processor, volatile memory unit operation, overheating components, unstable power supply operation.
0x0000009F: DRIVER_POWER_STATE_FAILURE
The driver is in an inconsistent or invalid state energy consumption. This usually happens because of failures in the food, when you reboot, exit from hibernate mode, etc. You should replace the failed driver, or uninstall the software that controls the file system (antivirus software, encryption program
0x000000A0: INTERNAL_POWER_ERROR
0x000000A1: PCI_BUS_DRIVER_INTERNAL
0x000000A2: MEMORY_IMAGE_CURRUPT
0x000000A3: ACPI_DRIVER_INTERNAL
0x000000A4: CNSS_FILE_SYSTEM_FILTER
0x000000A5: ACPI_BIOS_ERROR
The reason for this message, repeated failures in the ACPI BIOS. At the level of the operating system can not solve this problem. Requires detailed analysis.
0x000000A7: BAD_EXHANDLE
0x000000AB: SESSION_HAS_VALID_POOL_ON_EXIT
0x000000AC: HAL_MEMORY_ALLOCATION
0x000000B4: VIDEO_DRIVER_INIT_FAILURE
Windows could not load graphics driver. The problem is mainly related to video drivers, or have a hardware conflict with pay movies. Reboot into safe mode and change the video driver to standard.
0x000000B8: ATTEMPTED_SWITCH_FROM_DPC
0x000000B9: CHIPSET_DETECTED_ERROR
0x000000BA: SESSION_HAS_VALID_VIEWS_ON_EXIT
0x000000BB: NETWORK_BOOT_INITIALIZATION_FAILED
0x000000BC: NETWORK_BOOT_DUPLICATE_ADDRESS
0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY
The driver attempted to write data to permanent memory (ROM), where you can not record. The problem is mainly associated with the installation of a bad device driver, service, or firmware. Change the driver.
0x000000BF: MUTEX_ALREADY_OWNED
0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
Driver to write data to an invalid section of memory. Change the driver.
0x000000C2: BAD_POOL_CALLER
System kernel or the driver gave the wrong command to access memory. As a rule, a bad driver or software caused this error. Change the driver.
0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
The program checks the driver has detected a fatal error in the module generation STOP-error. The accompanying parameters - parameters that are passed to KeBugCheckEx and displayed on a blue screen. Change the driver.
0x000000C5: DRIVER_CORRUPTED_EXPOOL
An attempt to access invalid memory areas of a process IRQL higher level. This error is almost always due to driver who destroyed the system pool. Change the driver.
0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
The driver tried to access freed pool memory. Change the driver.
0x000000C7: TIMER_OR_DPC_INVALID
Core timer or Delayed Procedure Call (DPC) is present in a prohibited area of memory. This error occurs when the driver was unable to complete the core timer or Delayed Procedure Call (DPC) before shipping it from memory. Change the driver.
0x000000C8: IRQL_UNEXPECTED_VALUE
0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
This is a message from one of the managers check the driver. Change the driver.
0x000000CA: PNP_DETECTED_FATAL_ERROR
0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
Error, similar to the STOP-error 0x00000076. Differs from the latter only by the fact that in this case an error identified in the trace of the kernel. This error indicates that the driver or manager input - output can not open the locked pages after an I - O. Note the name applied to the driver window STOP-error. Change the driver.
0x000000CC: PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000CD: PAGE_FAULT_BEYOND_END_OF_ALLOCATION
0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
The driver can not cancel the hovering state of the system. Error usually occurs after the installation of bad drivers or components of the service. Change the driver.
0x000000CF: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
0x000000D0: DRIVER_CORRUPTED_MMPOOL
0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
The system tried to appeal to the paged memory using a kernel process IRQL a high level. The most common cause - a bad device driver. It can also be caused by a defective RAM or a damaged paging file.
0x000000D2: BUGCODE_ID_DRIVER
0x000000D3: DRIVER_PORTION_MUST_BE_NONPAGED
0x000000D4: SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD
0x000000D5: DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000D6: DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION
0x000000D7: DRIVER_UNMAPPING_INVALID_VIEW
0x000000D8: DRIVER_USED_EXCESSIVE_PTES
Error occurs when the driver requests a large amount of kernel memory.
0x000000D9: MUTEX_ALREADY_OWNED
0x000000DA: SYSTEM_PTE_MISUSE
0x000000DB: DRIVER_CORRUPTED_SYSPTES
0x000000DC: DRIVER_INVALID_STACK_ACCESS
0x000000DE: POOL_CORRUPTION_IN_FILE_AREA
0x000000DF: IMPERSONATING_WORKER_THREAD
0x000000E0: ACPI_BIOS_FATAL_ERROR
0x000000E1: WORKER_THREAD_RETURNED_AT_BAD_IRQL
0x000000E2: MANUALLY_INITIATED_CRASH
0x000000E3: RESOURCE_NOT_OWNED
Various crashes related to the file system, this leads to STOP-error. The problem may be related to the driver NTFS.SYS.
0x000000E4: WORKER_INVALID
0x000000E6: DRIVER_VERIFIER_DMA_VIOLATION
0x000000E7: INVALID_FLOATING_POINT_STATE
0x000000E8: INVALID_CANCEL_OF_FILE_OPEN
0x000000E9: ACTIVE_EX_WORKER_THREAD_TERMINATION
0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER
Problematic device driver brought the system to hang. Usually this is caused by the display driver when you try to move the computer into Standby mode. This issue is related to the video card or bad video driver.
0x000000EB: DIRTY_MAPPED_PAGES_CONGESTION
0x000000EC: SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT
0x000000ED: UNMOUNTABLE_BOOT_VOLUME
Failure occurred during the connection startup disk. Error can occur on computers with high-performance disk controllers that have not been correctly configured and installed, or connected to faulty cable. After the usual reboot, the system can resume normal operation as if nothing had happened. Also, this error was not shut down Windows, and failure may be associated with damage to the file system.
0x000000EF: CRITICAL_PROCESS_DIED
0x000000F1: SCSI_VERIFIER_DETECTED_VIOLATION
0x000000F2: HARDWARE_INTERRUPT_STORM
This message appears when the kernel detects a storm interrupts, that is, when caused by the level-interrupt device is not in a position to issue an interrupt request. Usually this is caused by a bad device driver.
0x000000F3: DISORDERLY_SHUTDOWN
Completion of Windows has crashed due to lack of memory. Determine what the program got 'out of memory ", try to discover why virtual memory does not provide the required system resources, and explore, refuses to whether the program (or, sometimes, the driver) to complete its work without the release of the open pages in memory.
0x000000F4: CRITICAL_OBJECT_TERMINATION
0x000000F6: PCI_VERIFIER_DETECTED_VIOLATION
0x000000F7: DRIVER_OVERRAN_STACK_BUFFER
0x000000F8: RAMDISK_BOOT_INITIALIZATION_FAILED
0x000000F9: DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN
0x000000FA: HTTP_DRIVER_CORRUPTED
System driver Http.sys damaged. This component should be restored from the original disk.
0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY
You attempted to execute a function in the non-complying memory.
Parameters:
1 - The address from which there was an attempt to perform the function
2 - Contents page table entry (PTE)
0x000000FD: DIRTY_NOWRITE_PAGES_CONGESTION
No free-paged memory to continue the basic system operations.
Parameters:
1 - Total amount requested paged memory
2 - Number of the requested paging memory to the inability to write.
3 -
4 - The status code at the time of the last record in page memory
0x000000FE: BUGCODE_USB_DRIVER
A fatal error occurred in the USB controller and related devices. The problem is usually caused by incorrect operation of USB-controller, or malfunction of USB-connected devices. Unplug all USB-devices from your computer and try to disable the USB-controller in the BIOS. Update the driver USB.
0x000000FF: RESERVE_QUEUE_OVERFLOW
0x00000100: LOADER_BLOCK_MISMATCH
0x00000101: CLOCK_WATCHDOG_TIMEOUT
Indicates that the expected termination of sync on the secondary processor in a multiprocessor system has not been received within a certain interval. This processor is not processing interrupts. Typically, this occurs when the processor is not responding, or went into an infinite loop.
Parameters:
1 - Interval timeout interrupt sync, in nominal clock ticks
2 - nil
3 - Location of the control unit CPU (PRCB) for nereagiruemogo processor
4 - nil
0x00000103: MUP_FILE_SYSTEM
0x00000104: AGP_INVALID_ACCESS
Attempt to write the graphics processor to memory, which has not been set aside for this. Error associated with the video driver or an old version of BIOS.
Parameters:
1 - Displacement (in ULONG) within the pages of AGP to the first data ULONG, whose data is destroyed
2 - nil
3 - nil
4 - nil
0x00000105: AGP_GART_CORRUPTION
Error occurs when damaged Graphics Aperture Remapping Table (GART). Error is caused by malfunctioning driver DMA (direct memory access)
Parameters:
1 - Base address (virtual) in the GART
2 - The offset in the GART, which revealed distortion
3 - The base address (virtual) from the cache GART (copy GART)
4 - nil
0x00000106: AGP_ILLEGALLY_REPROGRAMMED
Error is caused by unsigned or corrupted video driver. Replace the video driver.
Parameters:
1 - Original team
2 - Current team
3 - nil
4 - nil
0x00000108: THIRD_PARTY_FILE_SYSTEM_FAILURE
A fatal error occurred in a third-party file system filter. Error can be caused by antivirus software, defragmentation program, data backup and other third party utilities. Try also to increase the swap file and memory.
0x00000109: CRITICAL_STRUCTURE_CORRUPTION
Core of the system found an incorrect code or data corruption. Systems based on the 64-code protected from this error. The problem could be caused by either a memory or driver of a third party.
0x0000010A: APP_TAGGING_INITIALIZATION_FAILED
0x0000010C: FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION
0x0000010D: WDF_VIOLATION
0x0000010E: VIDEO_MEMORY_MANAGEMENT_INTERNAL
Encountered an internal error video driver. The problem with the video driver.
0x0000010F: RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED
In the Resource Manager kernel mode (kernel-mode resource manager) exception occurred.
0x00000111: RECURSIVE_NMI
0x00000112: MSRPC_STATE_VIOLATION
Msrpc.sys system component during the execution returned an error code. The error code specified in the first parameter.
0x00000113: VIDEO_DXGKRNL_FATAL_ERROR
DirectX Graphics Kernel revealed a critical error.
0x00000114: VIDEO_SHADOW_DRIVER_FATAL_ERROR
Shadow video driver has encountered a critical error.
0x00000115: AGP_INTERNAL
In Video Interface AGP video port driver was detected a critical error.
0x00000116: VIDEO_TDR_ERROR
Reset video driver to time out has not been successfully produced.
0x00000117: VIDEO_TDR_TIMEOUT_DETECTED
0x00000119: VIDEO_SCHEDULER_INTERNAL_ERROR
0x0000011A: EM_INITIALIZATION_FAILURE
0x0000011B: DRIVER_RETURNED_HOLDING_CANCEL_LOCK
0x0000011C: ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE
Attempt was made to record in the area of write-protected configuration manager:
Parameters:
1 - Virtual address write command undertaken
2 - Contents PTE
3 - reserved
4 - reserved
Name of the driver tries to write operations, printed as a Unicode string to display errors.
0x0000011D: EVENT_TRACING_FATAL_ERROR
0x00000121: DRIVER_VIOLATION
The driver produced an access violation in one area of memory.
Parameters:
1 - describes the type of violation
2 - reserved
3 - reserved
Use the kernel debugger and view the call stack to determine the driver's name, which produced an access violation.
0x00000122: WHEA_INTERNAL_ERROR
An internal error occurred in the architecture, error detection hardware Windows (Windows Hardware Error Architecture (WHEA))
0x00000124: WHEA_UNCORRECTABLE_ERROR
An error occurred in the computer's hardware. This error is detected the error detection architecture hardware Windows (Windows Hardware Error Architecture (WHEA))
0x00000127: PAGE_NOT_ZERO
Memory page has not been completely filled with zeroes. This error is due to hardware failure, either because of triggering a privileged operating system component that produced a premature change pages in memory.
Parameters:
1 - The virtual memory address that points to the incorrect page.
2 - Physical page number
3 - nil
4 - nil
0x0000012B: FAULTY_HARDWARE_CORRUPTED_PAGE
Detected single bit error (error of bits) per page of memory. This error is related to hardware memory.
Parameters:
1 - The virtual memory address that points to the incorrect page.
2 - Physical page number
3 - nil
4 - nil
0x0000012C: EXFAT_FILE_SYSTEM
Has failed to read or write in the media section, with the format exFat. Failure may be associated with damage to the file system, or the appearance of bad sectors on the disk. Also, failure may be associated with the software, changing the structure of the disk (encryption programs, etc.). This failure relates to the media, formatted for Windows Vista Service Pack 1.
0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
See 0x0000007E
0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M
0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
See 0x0000008E
0x100000EA: THREAD_STUCK_IN_DEVICE_DRIVER_M
0xC000009A: STATUS_INSUFFICIENT_RESOURCES
System kernel operating system has exhausted all system resources for its work, including the swap file. Check disk for errors. Increase the amount of hard disk and RAM.
0xC0000135: UNABLE TO LOCATE DLL
Windows tried to load the DLL library and got an error code. Possible cause - the file is missing or damaged. It is also possible corrupted registry.
0xC0000142: DLL Initialization Failure
This error was caused by a corrupt system DLL library.
0xC0000218: UNKNOWN_HARD_ERROR
Desired system registry can not load. The file may be corrupted or missing (need a rescue disk or reinstall Windows). Registry files might have been destroyed because of damage to the hard disk. The driver may have destroyed the data of the registry when loading into memory or the memory where the registry has been loaded, has a parity error (turn off the external cache and check RAM).
0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
This occurs when Windows switched to privileged mode and user mode subsystem, such as Winlogon or Runtime Subsystem Client / Server (CSRSS), have caused any crashes, and protection can not be guaranteed. Since Windows XP can not run without Winlogon or CSRSS, this - one of the few situations where the failure-mode service can cause the system to stop responding. This can also happen when the computer is restarted after a system administrator has changed the permissions so that the SYSTEM account no longer had adequate resolution to apply to system files and folders. Error can also be caused by damage to the file user32.dll or incorrect system drivers (. Sys)
0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
the driver is corrupted or the system library has been recognized as damaged. The system does everything in order to verify the integrity of critical system files. Blue screen displays the name of the damaged file. If this happens, boot into any other system or, if none, then reinstall the system. Make sure that the version of the file that has been identified as corrupted, the same as the version of the file in the distribution system and if so, replace it with the disc. Permanent errors with different file names, they say that there are problems with media or with the disk controller, where are these files.
0xC0000244
STOP-error occurs when the audit policy setting activates CrashOnAuditFail
0xC000026C
Usually indicates a problem with a device driver.
0xDEADDEAD: MANUALLY_INITIATED_CRASH1
"It's dead, Jim!" (It's dead, Jim!) STOP-This error indicates that the user deliberately initialized the crash, or from the kernel debugger or the keyboard.
0 comments:
Posting Komentar