Automatically fix Windows errors:

If your error could not be eliminated automatically (link above), then you can go to the "List of errors"
section in the site menu, and find a detailed description of how to fix your error manually

Why do errors occur in the Windows operating system? The list of reasons is very wide – there can be both incompatibility of computer hardware, and internal, software reasons, such as – lack of drivers for the desired device, software incompatibility with the current version of Windows, etc.

Often, the error can be corrected automatically, simply by running a special utility. But sometimes it also happens that the problem is very individual. On our site we will try to collect solutions to most of these problems that arise when using your device.

Windows error classification

Blue Screen of Death, BSoD – Blue Screen of Death is the name of a critical system error (stop error) message in Microsoft Windows operating systems. Below is a complete list of these errors.


0x00000001: APC_INDEX_MISMATCH

This is an internal kernel error. The error may occur due to a mismatch between KeEnterCricticalRegion and KeLeaveCriticalRegion in the file system.


0x00000002: DEVICE_QUEUE_NOT_BUSY
0x00000003: INVALID_AFFINITY_SET
0x00000004: INVALID_DATA_ACCESS_TRAP


0x00000005: INVALID_PROCESS_ATTACH_ATTEMPT
Stop on Win XP SP2 or Server 2003


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
An attempt was made to affect virtual memory on an internal IRQ process at a level that is too high. If the kernel debugger is available, you can track exactly where the system stuttered.
The most common cause is that the device driver uses an invalid address.
Parameters:
1-address where the erroneous request was made
2-IRQL that was used for accessing memory
3 – access type to storage: 0 = read operation, 1 = write operation
4-address of the instruction that requested memory access at
Note: Keep in mind that this error occurs in 99% due to “curves” drivers. You can find some of them in Windows XP using the utility verifier.exe: Start- & gt; Run- & gt; verifier.exe


0x0000000B: NO_EXCEPTION_HANDLING_SUPPORT
0x0000000C: MAXIMUM_WAIT_OBJECTS_EXCEEDED


0x0000000D: MUTEX_LEVEL_NUMBER_VIOLATION
Try to set mutual exceptions using NTOSEXEXLEVELS.H header file.
You must find the interaction points and determine which ones are trying to access this level in the wrong sequence.
Parameters:
1-the real thread of the interaction level
2 – the level of interaction trying to access


0x0000000E: NO_USER_MODE_CONTEXT
0x0000000F: SPIN_LOCK_ALREADY_OWNED
0x00000010: 0SPIN_LOCK_NOT_OWNED
0x00000011: THREAD_NOT_MUTEX_OWNER


0x00000012: TRAP_CAUSE_UNKNOWN
In General, this error means that the reason for it is not known. In this case, to determine the reason, try to notice what circumstances it occurred: what you were doing or trying to do at the time, what changes occurred in the system, and so on.


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 error. Usually the 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 the address or image containing this error. This is usually the exception code 0x80000003. This error means that a breakpoint or judgment was reached when accessing memory, but the system booted with the / NODEBUG key. This error should not appear too often. If the error persists, make sure that the debugger is enabled and the system is loaded with /DEBUG switch.
On non-Intel systems, if the exception address is 0XBFC0304, the error occurs due to processor caching. If the error persists, contact the manufacturers.
Usually, you need to analyze the second parameter of this message, which indicates the address of the driver/function that caused the problem.
Parameters:
1-exception code
2 – the address at which processing failed
3 – Parameter 0 of the exception
4 – Parameter 1 of the exception


0x0000001F: SHARED_RESOURCE_CONV_ERROR


0x00000020: KERNEL_APC_PENDING_DURING_EXIT
The error name indicates a corrupted / disabled APC counter. If the counter shows a value not equal to zero, then it is the source of the problem. A negative value indicates that the file system called FsRtlEnterFileSystem more times than FsRtlExitFileSystem. A positive value indicates the opposite FsRtlExitFileSystem was due to a greater number of times than FsRtlEnterFileSystem. If you have this situation, check all the file systems installed on the machine. Third-party redirectors are most likely to fail, since they have not been as thoroughly tested as NTFS, FAT, HPFS, and RDR.
The current IRQL must be 0. If not, a specific driver cancellation order may cause the error to occur, returning at a high IRQ level. Always try to notice what you were doing or which apps were closing, which drivers were installed when the blue screen appeared. This symptom indicates a serious problem in third-party drivers.
Parameters:
1 – the address of the APC that was hanging (waiting) at the time of exit.
2 – thread APC disable count
3 is the current IRQ level


0x00000021: QUOTA_UNDERFLOW
0x00000022: FILE_SYSTEM


0x00000023: FAT_FILE_SYSTEM
An error occurred while writing or reading from the system disk on the FAT16 or FAT32 file system. There may be a problem with the disk itself or with the Interrupt Request Packet (IRP) package.
It can also be caused by a large disk fragmentation, a problem with antivirus software, or disk tracking SOFTWARE (drive monitoring).


0x00000024: NTFS_FILE_SYSTEM
Problem with the NTFS file system write and read driver ( NTFS.SYS ). There may be a problem with the disk itself or with the Interrupt Request Packet (IRP) package.
It can also be caused by a large disk fragmentation, a problem with antivirus software, or disk tracking SOFTWARE (drive monitoring).


0x00000025: NPFS_FILE_SYSTEM
0x00000026: CDFS_FILE_SYSTEM
0x00000027: RDR_FILE_SYSTEM
0x00000028: CORRUPT_ACCESS_TOKEN
0x00000029: SECURITY_SYSTEM


0x0000002A: INCONSISTENT_IRP
An IRP was unexpectedly detected on an inconsistent state; this is when a field or multiple fields were incompatible with the preserved IRP state. For example, an IRP that was finished was indicated as still waiting for some device driver’s commands to be executed.
Parameters:
1-address where the IRP was found in an inappropriate state


0x0000002B: PANIC_STACK_SWITCH
This error indicates that the kernel stack area is full. This can occur when the kernel driver uses too much space in the stack area. This can also happen if there is a serious error in the core itself.


0x0000002C: PORT_DRIVER_INTERNAL
0x0000002D: SCSI_DISK_DRIVER_INTERNAL


0x0000002E DATA_BUS_ERROR
This stop is most often caused by an error in the system’s memory. This can also happen when the driver accesses a 0x8xxxxxxx memory address that does not exist.
Parameters:
1 – the address of the virtual memory that caused the error
2-physical address of the error cause
3-processor status register (PSR)
4-error instruction register (FIR)


0x0000002F: INSTRUCTION_BUS_ERROR
0x00000030: SET_OF_INVALID_CONTEXT


0x00000031: PHASE0_INITIALIZATION_FAILED
System initialization failed at an early stage. You need to install the error in more detail, since this code does not tell you anything practical about anything.


0x00000032: PHASE1_INITIALIZATION_FAILED
Parameters:
1 – system status code that describes why the system decided that initialization failed
2-specifies the location inside INIT.C where the phase 1 initialization error occurred


0x00000033: UNEXPECTED_INITIALIZATION_CALL
0x00000034: CACHE_MANAGER


0x00000035: NO_MORE_IRP_STACK_LOCATIONS
The higher-level driver tried to call the lower-level driver via the IoCallDriver () interface, but there was no free space in the stack area, so the lower-level driver will not be able to reach the necessary parameters, since there are no parameters for it at all. This is a disastrous situation, since the top-level driver believes that it has filled in the parameters for the lower-level driver (something it should have done to call the lower-level driver). However, since there is no free space in the stack area for the last driver, the compiler canceled the end of the package. This means that most likely some other memory was corrupted.
Parameters:
1-IRP address


0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO
The device driver tried to delete one of its device objects from the system, but the access count for this object was not equal to 0, meaning that there were still outstanding tasks for this object (the counter indicates the number of reasons why this object cannot be deleted). This is an error calling the driver.
Parameters:
1-address of the 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
A multiprocessor system is not symmetrical with respect to each other. To be symmetrical, processors must be of the same type and level. For example, trying to use a Pentium and 80486 processor will cause an error. In addition, on x86 systems, the ability to calculate fractions must be on both processors or neither.


0x0000003F: NO_MORE_SYSTEM_PTES
Not enough RTE (page file entries). This is usually caused by a driver that does not clean the swap file properly. If the kernel debugger is available, trace where the system stuttered and enter the following command:
!sysptes 3


0x00000040: TARGET_MDL_TOO_SMALL
The driver called The iobuildpartialmdl() function and sent it an MDL to reveal part of the MDL source, but the MDL target is not large enough to display the limits of the required addresses. This is a driver error. The source and target of the MDL, as well as the length of the definition address line, are arguments of the IoBuildPartialMdl () function:
IoBuildPartialMdl( IN PMDL SourceMdl,
IN OUT PMDL TargetMdl,
IN PVOID VirtualAddress,
IN ULONG Length )


0x00000041: MUST_SUCCEED_POOL_EMPTY
If the kernel debugger is available, the VM command shows different values:
Parameters:
1-value of the request that cannot be satisfied
2 – the number of pages that were used from the nonpaged pool.
3 – number of requested pages from the nonpaged pool.
4-number of available pages


0x00000042: ATDISK_DRIVER_INTERNAL
0x00000043: NO_SUCH_PARTITION


0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS
The driver requested completion of IRP [IoCompleteRequest ()], but the package was already completed. This error is difficult to detect. The simplest case is that the driver tries to complete the same operation twice, but this case is very rare. It also happens that two different drivers try to take over the package and terminate it. The first usually works, but the second does not. It is difficult to track which driver caused the crash, since traces of the first driver were rewritten by the second. However, a conflict can be detected by looking at the DeviceObject fields at each stack location.
Parameters:
1-IRP address


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) that should be completed has a specific cancellation order, which means that the packet is in a position that can be canceled in no other way. Although the package itself is no longer related to the driver setting the completion order, since it is already in the completion stage.


0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF
It means exactly what it says: a memory page error with interrupt disabled. Treat this error the same way as 0x0A.


0x0000004A: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
0x0000004B: STREAMS_INTERNAL_ERROR


0x0000004C: FATAL_UNHANDLED_HARD_ERROR
If an error occurs while loading NT, the download is interrupted by a blue screen.
Most common causes:
x218 – a necessary registry of the library could not be loaded. This file may be missing or corrupted. To solve the problem, you will need a rescue boot floppy.
The driver may corrupt the registry key while loading it into memory, or the memory where the key was loaded may not be valid. Especially AST EISA machines with 16M or higher memory must have access to memory above 16M, i.e. in the EISA configuration utility, this parameter must be ENABLED. Otherwise, the file that is loaded into that memory will show-0xffffffff when reading.
x21A-either Winlogon or CSRSS (Windows) suddenly failed. The output code can say more. This is usually c0000005, which indicates that an unsupported exception caused a process to fail. There’s almost nothing you can do here.
x221-indicates that the driver is damaged or the system library was detected as damaged. NT does everything to check the integrity of important system files. The blue screen shows the name of the corrupted file. If this happens, boot into any other system or, if there are none, reinstall/repair the system… Make sure that the version of the file that was corrupted matches the version of the file in the NT distribution, and if so, just replace it from disk. Persistent errors with different file names mean hardware problems in the driver’s I/O path.


0x0000004D: NO_PAGES_AVAILABLE
There is not enough free space to finish the operation. If the kernel debugger is available, print the following commands:
!process 0 7
!vm
dd mmpagingfiles
dd @$p
Parameters:
1 – number of pages used
2-number of physical pages per machine
3 – Extended commit value in pages
4 – Total commit value in pages


0x00000051: REGISTRY_ERROR
Something happened to the registry. If a debugger (kernel debugger) is available, track the error. If it shows you that you are in the system branch (CmpWorker will be present in the list), enter the following commands:
dd CmpRegistryMutex+18 L1
!thread
This will give you the branch and the error location in the registry.
This error can also mean that the registry made an I/O error when trying to read one of its libraries, which means that the error may have been caused by a hardware problem or that the system itself is corrupted. This can also mean that the error is caused by an update operation that is only used by the security system and this is only when resources are running out. If this error occurs, check whether the machine is a PDC or BDC and how many accounts are in the SAM (Account Security Manager) database, whether this can be an echo target, and whether the corresponding libraries are almost full.
Parameters:
1. value 1 (indicates where the error occurred)
2. value 2 (indicates where the error occurred)
3. can point to the library
4. it can be a return code of Hvcheckhive if any 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, so the libraries say the mirror is OK, but it’s not really. Real images of libraries are shaded. You need to make sure that the download is coming from the correct partition.


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
This means that the registry cannot create the space needed to contain registry files. This error should never occur, since the process of creating such a place occurs at an early stage of system loading and therefore there should be enough space to create a pool.
Parameters:
1. 5
2. indicates the NTOSCONFIGCMSYSINI that failed.


0x00000068: FILE_INITIALIZATION_FAILED


0x00000069: IO1_INITIALIZATION_FAILED
Initialization of the I/O system failed for some reason. There is practically no more information. This could happen if the installation made the wrong decision about installing the system, or the user reconfigured the system. Or trying to install an image of one system on a completely different one.


0x0000006A: LPC_INITIALIZATION_FAILED


0x0000006B: PROCESS1_INITIALIZATION_FAILED
Parameters:
1. indicates the status code that decided that NT initialization was not successful.
2. indicates the location in NTOSPSPSINIT.C where the error was detected.


0x0000006C: REFMON_INITIALIZATION_FAILED
0x0000006D: SESSION1_INITIALIZATION_FAILED
0x0000006E: SESSION2_INITIALIZATION_FAILED
0x0000006F: SESSION3_INITIALIZATION_FAILED
0x00000070: SESSION4_INITIALIZATION_FAILED


0x00000071: SESSION5_INITIALIZATION_FAILED
These code codes (SESSION1 – SESSION5) indicate the location in NTOSINITINIT.C where the error was made.
Parameters:
1. specifies the status code that is decided that the initialization of the NT was not successful.


0x00000072: ASSIGN_DRIVE_LETTERS_FAILED


0x00000073: CONFIG_LIST_FAILED
Indicates that one of the system libraries is damaged or unreadable. This library can be either SOFTWARE, SECURITY, or SAM (Account Security Manager).
Parameters:
1. 5
2. 2
3. list of libraries
4. specifies a string (UNICODE_STRING) containing the library name


0x00000074: BAD_SYSTEM_CONFIG_INFO
This error may indicate that the SYSTEM library loaded by OSLOADER/NTLDR is corrupted. However, this is almost impossible, since OSLOADER always checks the libraries after loading and makes sure that they are not damaged.
This error may also mean that some of the required registry keys and their parameters are missing. Loading into LastKnownGood (the Last good configuration) may solve the problem, or you will have to reinstall the system, or use Emergency Repair Disk.


0x00000075: CANNOT_WRITE_CONFIGURATION
This error may occur if the library’s SYSTEM files (SYSTEM and SYSTEM.ALT) cannot accommodate additional information written to the registry libraries between registry initializations and the first phase (when file systems are available). This error usually means that there is not enough free space on the disk, and it can also happen when you try to save the registry on a read-only device.


0x00000076: PROCESS_HAS_LOCKED_PAGES
this error may occur because the driver is not completely cleared from memory after the I / O operation.
Parameters:
1. process address
2. the number of closed pages
3. the number of private pages
4. 0


0x00000077: KERNEL_STACK_INPAGE_ERROR
The requested page of kernel memory could not be read. The reason for the error may be a bad block of the virtual memory file or an error of the disk controller (very rarely, when the reason may be a lack of resources, and more specifically, a reserve of nonpaged pool (unoccupied disk space) with the status c0000009a [STATUS_INSUFFICIENT_RESOURCES]).
If the first and second parameters of the error code are equal to 0, it means that the error location was not found in the kernel. So this error is caused by bad hardware.
The I / O status of c000009c (STATUS_DEVICE_DATA_ERROR) or C000016AL (STATUS_DISK_OPERATION_FAILED) usually means that the information cannot be read due to a bad block in memory. After restarting, the automatic disk check will try to determine the address of the bad block on the disk. If the status is C0000185
(STATUS_IO_DEVICE_ERROR) if the virtual memory is located on a SCSI disk, the disk connection and expiration date must be checked.
Parameters:
1. 0
2. 0
3. PTE value at the time of the error
4. address of the kernel error
1. status code
2. I / O status code
3. the number of page virtual memory
4. additional space in the virtual machine file
More information- & gt;
0x00000078: PHASE0_EXCEPTION


0x00000079: MISMATCHED_HAL
The Hal verification level and Hal configuration type are not appropriate for the system core or machine type. This error is likely caused by the fact that the user has manually updated either NTOSKRNL.EXE either HAL.DLL. On a machine, a multiprocessor HAL (MP) and a uniprocessor core (UP) or Vice versa.
Parameters:
1. type of mismatch (1, 2, or 3):
1. mismatch of PRCB release levels (mismatch of dates). If this is the case, then parameters 2 and 3:

2 – the highest level of y NTOSKRNL.EXE
3 – the highest level of y HAL.DLL

2. version mismatch, in this case parameters 2 and 3:

Version 2 NTOSKRNL.EXE
Version 3 HAL.DLL
versions:0 – 1 – 2 –

3. Micro Channel Architecture (MCA) computers require a specific MCA HAL, in this case parameters 2 and 3:

2-type of machine defined NTDETECT.COM
a value of 2 means that this HAL is made for MCA
3 – type of machines that this HAL supports


0x0000007A: KERNEL_DATA_INPAGE_ERROR
The memory page requested by the kernel cannot be read. The error is caused by a bad block in memory or a disk controller error. See also 0x00000077: KERNEL_STACK_INPAGE_ERROR.
Parameters:
1. type lock key, which hung
2. error status (usually I / O status code)
3. current process (virtual address for lock type 3 or PTE)
4. the address of the virtual memory that cannot be entered in the swap file.


0x0000007B: INACCESSIBLE_BOOT_DEVICE
During the installation of the I / O system, the boot device driver may not have been able to initialize the device that the system was trying to boot from, or the file system that should have read this device either failed to initialize, or simply did not recognize the information on the device as a file system structure. In the case of the originator, the first argument is the address of the unique information structure, which is the ARC name of the device from which the attempt was made to load. In the second case, the first argument is the address of the device object that cannot be mounted.
If this error occurred during the initial installation of the system, it may mean that the system was installed on a disk or SCSI controller that it does not support. Keep in mind that some controllers are only supported by drivers from Windows libraries (WDL), which must be installed by custom installation.
This error can also occur after installing a new SCSI adapter or controller, or after changes to the system partition. In this case, on x86 systems, you need to edit BOOT.INI; on ARC systems, you need to run Setup. For more information on how BOOT.INI should be changed, see the Windows NT Advanced Server “Administrator’s Guide”.
If the argument points to an ARC string name, the format of the first two (this is only in this case) long words will be:
USHORT Length;
USHORT MaximumLength;
PVOID Buffer;
For example, if the first long word contains something like 00800020, where 20 is the length of the Unicode string, and the next long word will contain the buffer address.
If the argument points to a device object, the format of the first word will be:USHORT Type;
This means that the first word contains 0003, where the Type code will always be 0003.
Note:
You can immediately recognize whether the argument points to the ARC name or to the device object, since the Unicode string never contains an odd number of bytes, and the device object will always contain the code type – 3.
Parameters:
1. pointer to the device object or Unicode string, or ARC name.


0x0000007C: BUGCODE_PSS_MESSAGE


0x0000007D: INSTALL_MORE_MEMORY
Not enough memory to load Windows NT (5 MB required).
Parameters:
1. number of physical pages found
2. the lower physical page
3. higher physical page
4. 0


0x4000007E: WINDOWS_NT_BANNER


0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP
This error means that an unexpected interrupt occurred in kernel mode, or the type of interrupt that the kernel does not allow, or a bound trap, or the type of interrupt that causes immediate death (double fault). The first number in the stop code intervals is the interrupt number (8 = double fault). To find out more about this interruption, refer to the Intel x86 family manual.
In General, a bug occurs when the processor makes an error that the kernel can’t handle. Most often occurs due to poor RAM, as well as due to overclocking of the processor.
Try canceling in BIOS-sync negotiation (synchronous data transfer).


0x00000080: NMI_HARDWARE_FAILURE
HAL must provide all specific information and suggest that the user contact their hardware supplier for technical support.support.


0x00000081: SPIN_LOCK_INIT_FAILURE


0x00000085: SETUP_FAILURE
(Note: the setup text form no longer uses bugcheck to get out of serious errors. So you will never encounter 0x85. All bug checks have been replaced with more friendly and (where possible) more informative error messages. However, some error compilers have just been replaced with our bugcheck screens, and the code for these error States is the same as it was. They are listed below.)
1-
0: OEM HAL font-invalid*. fon file format, so the installation could not display the text. This means that vgaxxx.the fon on the CD or floppy is damaged.
1: the video could not be initialized. This error has its own screen and the user is given only 2 options.
This means that the file vga.sys (or another driver, depending on the machine) is damaged, or that this hardware is not supported.
2-what failed:
0: NtCreateFile of devicevideo0
1: IOCTL_VIDEO_QUERY_NUM_AVAIL_MODES
2: IOCTL_VIDEO_QUERY_AVAIL_MODES
3: the Desired video mode is not supported. This means an internal installation error.
4: IOCTL_VIDEO_SET_CURRENT_MODE (video mode cannot be set)
5: IOCTL_VIDEO_MAP_VIDEO_MEMORY
6: IOCTL_VIDEO_LOAD_AND_SET_FONT 3-status code of the NT API call
2: Lack of memory. Now this error uses a friendlier screen, depending on how far the installation has gone.
3: the keyboard Was not initialized. Now 2 different screens are used, depending on the errors that might appear here. This may mean that the disk containing the keyboard drivers (i8042prt.sys or kbdclass.sys) is damaged or the machine has a keyboard that is not supported.
It may also mean that the keyboard layout dll cannot be loaded.
2-what failed:
0: NtCreateFile of deviceKeyboardClass0 .
“The installation did not detect a keyboard connected to your computer.”
1: Unable to load keyboard layout dll.
“The installation cannot load the keyboard layout dll .”
This means that there is no file on the floppy or CD (kbdus.dll for us or other DLLs).
4: the Installation failed to find out the path of the device from which the installation started. This is an internal installation error.
5: the partitions were not checked for operability. This means a bug in the disk driver. Parameters only have values for the installation group.


0x0000008B: MBR_CHECKSUM_MISMATCH
This error occurs during loading when the MBR checksum that the system calculated does not match the loader’s checksum. This usually means a virus. Some viruses cannot be detected / found. Boot from a floppy disk with a virus scanner (make sure that the floppy disk is write-protected!)
KerBugCheckEx
parameters:
1-Disk Signature from MBR.
2 – MBR checksum calculated by osloader.
3 – MBR checksum calculated by system.


0x0000008E
Applies to the following systems:
Microsoft Windows XP Professional
Microsoft Windows XP Home Edition
Microsoft Windows XP Professional SP1
Microsoft Windows XP Home Edition SP1


0x0000008F: PP0_INITIALIZATION_FAILED
This message appears if the plug and Play Manager phase 0 initialization failed during the kernel initialization stage (kernel-mode Plug and Play Manager failed). Actually, there is nothing that could cause this error.


0x00000090: PP1_INITIALIZATION_FAILED
This message appears if the plug and Play Manager phase 1 initialization failed during the kernel initialization stage (kernel-mode Plug and Play Manager failed). This is where all initializations occur, including the environment configuration (registry, etc.) of drivers for calling I/O afterwards.


0x00000092: UP_DRIVER_ON_MP_SYSTEM
This bug only appears when the UNIPROCESSOR driver is loaded on a system with more than one active processor.
KeBugCheckEx
parameters:
1-address of the driver database.


0x00000093: INVALID_KERNEL_HANDLE
This error occurs when the kernel code, such as the server, redirector, other drivers, and so on, tries to close a non-valid pointer.
Parameters:
1-the pointer that NtClose was called with.
2-0 means that the protected pointer was closed.
1 means that the wrong pointer was closed.


0x00000094: KERNEL_STACK_LOCKED_AT_EXIT
This message appears when a thread exists while its core stack is marked as not swapable.


0x00000096: INVALID_WORK_QUEUE_ITEM
This message appears when KeRemoveQueue deletes the data queue and the flink or blink field is 0. This practical is always caused by incorrectly applying the code of the running thread of the current object, but incorrectly applying any queue can lead to this. Rule-data can only be entered in the queue once. When an item is removed from the queue, its flink field is 0. This bug occurs when there is an attempt to delete data whose flink or blink fields are equal to 0.in order to resolve this bug, you need to find out the queue that it refers to. If this queue is one of the exworkerqueue queues, then the object that is being deleted is WORK_QUEUE_ITEM. This bug implies that this is the reason. Bug parameters help identify the driver that is using the queue incorrectly.


0x00000097: BOUND_IMAGE_UNSUPPORTED
MmLoadSystemImage was called to load bound image. This is not supported by the kernel. Make sure that bind.exe it was not pressed for the image.KeBugCheckEx
parameters:
1-Address of data in the queue, flink/blink field of which is zero.
2-Address to the referring queue. This is usually one of The exworkerqueues of the queue.
3 – the Starting address of The exworkerqueue array. This will help detect if the queue in question is one of the ExWorkerQueue queues, and if so, the offset from this parameter will detect the queue.
4 – If this is an ExWorkerQueue queue (as it usually is), this is the address of the working routine that would be called if the working element was valid. This can be used to identify a driver that is incorrectly using the work queue.


0x00000098: END_OF_NT_EVALUATION_PERIOD
Your NT system is a trial with a limited date that has come to an end. KeBugCheckEx
parameters:
1-Low 32-bit request for your installation date.
2-High 32-bit request for your installation date.
3-Trial period in minutes.


0x00000099: INVALID_REGION_OR_SEGMENT
ExInitializeRegion or ExInterlockedExtendRegion was called with an incorrect set of parameters.


0x0000009A SYSTEM_LICENSE_VIOLATION
The trial period of the software license was violated. This may be due to an attempt to change the product type of the offline system, or an attempt to change the term of the trial period of the NT.


0x0000009B: UDFS_FILE_SYSTEM
See FAT_FILE_SYSTEM

comments


0x0000009C: MACHINE_CHECK_EXCEPTION
Fatal error Machine Check Exception (machine check).KeBugCheckEx
parameters:
If the processor has ONLY MCE functions available (for example: Intel Pentium), the parameters will be:

1 – Low 32 bits of P5_MC_TYPE MSR
2 –
3 – High 32 bits of P5_MC_ADDR MSR
4 – Low 32 bits of P5_MC_ADDR MSR

If the processor also has MCA functions available (for example: Intel Pentium Pro), the parameters will be:1 – Bank number

2 – Address field of MCi_ADDR MSR for the MCA bank that had the error
3 – High 32 bits of MCi_STATUS MSR for the MCA bank that had the error
4 – Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error


0x0000009F: DRIVER_POWER_STATE_FAILURE
The driver is in an incompatible or unstable power supply state.In most cases, this occurs when the computer is turned off, or when you exit standby or hibernate mode.


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 error is always ACPI BIOS. This problem cannot be resolved by the OS.


0x000000A7: BAD_EXHANDLE
0x000000AB: SESSION_HAS_VALID_POOL_ON_EXIT
0x000000AC: HAL_MEMORY_ALLOCATION


0x000000B4: VIDEO_DRIVER_INIT_FAILURE
Windows was unable to switch to graphics mode because no video drivers were loaded. Usually there is a problem with the driver or some kind of video hardware conflict with other hardware. Boot into Safe Mode and see if this solves the problem. If so, update the video hardware drivers or roll back to the working version.


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 tried to write to read-only memory. Usually occurs after installing a faulty hardware driver, system service, or BIOS. If the driver name is specified in the error, try to fix the problem by disabling, deleting, or rolling back the drivers.


0x000000BF: MUTEX_ALREADY_OWNED


0x000000C1: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
The driver tried to write to an unauthorized area of memory. Update driver.


0x000000C2: BAD_POOL_CALLER
The kernel process or driver tried to perform an incorrect memory operation. Usually the cause is faulty drivers or software.


0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION
This is a common stop for fatal errors detected by Driver Verifier (driver verification tool). The meters are transmitted by KeBugCheckEx and displayed on a blue screen.


0x000000C5: DRIVER_CORRUPTED_EXPOOL
The cause is almost always a faulty driver. If you have just installed new software, then check the driver update on the manufacturer’s website.


0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL
The driver tried to access the freed memory.


0x000000C7: TIMER_OR_DPC_INVALID
Indicates that the kernel timer or DPC was detected in memory where it should not have been. This situation usually occurs when the driver did not cancel the timer or the Delayed Procedure Call (DPC) before freeing up memory occupied by the timer or DPC.


0x000000C8: IRQL_UNEXPECTED_VALUE


0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION
Violation of the driver verification tool.


0x000000CA: PNP_DETECTED_FATAL_ERROR


0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS
This one refers to the 0x76 stop. It may appear instead of 0x76. Indicates that the driver or I / o system did not release the IRQ. The driver name can be shown on the blue screen.


0x000000CC: PAGE_FAULT_IN_FREED_SPECIAL_POOL
0x000000CD: PAGE_FAULT_BEYOND_END_OF_ALLOCATION


0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS
The driver did not cancel the reviving operation before exiting. The usual reason is a bad driver or service.


0x000000CF: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE
0x000000D0: DRIVER_CORRUPTED_MMPOOL


0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL
An attempt was made to affect virtual memory on an internal IRQ process at a level that is too high.
The reason may be:
faulty driver
faulty RAM
corrupted virtual memory 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
This usually occurs when Page Table Entries (PTEs) are not available, when the driver requires too much system 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
The error is caused by a file system failure.


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
A problem with the hardware driver caused the system to freeze. The display driver usually waits for the hardware to go into sleep mode. Problems may be with the video adapter or its driver.


0x000000EB: DIRTY_MAPPED_PAGES_CONGESTION
0x000000EC: SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT


0x000000ED: UNMOUNTABLE_BOOT_VOLUME
The core I / O system tried to mount a device to boot the system, but it refused to work. This error may occur during an upgrade to Windows XP on a system that uses high-performance ATA disks or controllers, and they are connected with a low-pass cable. In some cases, after restarting, the system may continue to work without visible failures.


0x000000EF: CRITICAL_PROCESS_DIED
0x000000F1: SCSI_VERIFIER_DETECTED_VIOLATION


0x000000F2: HARDWARE_INTERRUPT_STORM
Usually occurs due to a faulty driver.


0x000000F3: DISORDERLY_SHUTDOWN
Windows did not shut down due to insufficient memory. Check your free disk space and whether any programs are stuck.


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


0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
The error is the same as 0x7E.


0x1000007F: UNEXPECTED_KERNEL_MODE_TRAP_M


0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
The error is the same as 0x8E.


0x100000EA: THREAD_STUCK_IN_DEVICE_DRIVER_M


0xC000009A: STATUS_INSUFFICIENT_RESOURCES
Memory loss.


0xC0000135: UNABLE TO LOCATE DLL
Windows tried to load some library, but an error occurred. This error could be caused by a corrupted, missing file, or corrupted registry.


0xC0000142: failed DLL initialization
Usually occurs when the program cannot be initialized successfully.


0xC0000218: UNKNOWN_HARD_ERROR
The required registry library cannot be loaded. The file may be missing or corrupted. The damage could be caused by a faulty hard drive or other hardware. The driver could have damaged the registry during loading, or the memory where the registry was loaded was damaged.


0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
This happens when Windows switches to kernel mode, but the user mode, such as Winlogon or Client Server Runtime Subsystem (CSRSS), is compromised and security cannot be guaranteed. Since Win XP can’t work without Winlogon or CSRSS. These are situations where user subsystems can prevent or cause the system itself to fail.
The same error may occur when the administrator has changed access rights and the SYSTEM account can no longer use system files and directories.


0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH
Indicates driver problems, system files, disk problems (such as corrupted virtual memory), or hardware memory problems.


0xC0000244
A “Stop 0xc0000244” Error Occurs When You Audit Policy Changes If CrashOnAuditFail Is Turned On {KB 323475} Win XP


0xC000026C
Usually indicates a driver problem.
It is not possible to download the driver {KB 160495} Win NT, Win 2000, Win XP


0xDEADDEAD: MANUALLY_INITIATED_CRASH1
“It’s dead, Jim!” – “He’s dead, Jim” =)

1 Звезда2 Звезды3 Звезды4 Звезды5 Звезд (Пока оценок нет)
Загрузка...

top