How to decipher Windows error codes? Blue Screen of Death error codes

In accordance with the OBD-II standard, error codes are alphanumeric and contain five characters, for example, P0331. The first character is a letter that indicates the system in which the malfunction occurred. The second character - a number - indicates how the code is determined: by SAE or by the vehicle manufacturer. The remaining three digits indicate the nature of the malfunction.

The OBD-II standard uses four letters to designate the main electronic systems of a vehicle:

B - for packaged electronics (body);

C - for electronics on the chassis (chassis);

P - for electronic powertrain control systems (powertrain);

U - system type is undefined.

Not all possible code combinations have been used; many are reserved for the future for SAE.

The second character (digit) takes the values 0, 1,2, 3. The number 0 means that the error code was entered using SAE; number 1 indicates that the code was entered by the manufacturer; numbers 2 and 3 are reserved for later use by SAE. The third character (numbers 0 to 9) indicates the subsystem where the malfunction occurred. For example, for powertrain control systems (P):

1,2 — fuel and water supply systems;

3 - ignition system;

4 — toxic emissions control system;

5 — engine speed control system;

7.8- transmission;

9, 0 - reserved for SAE.

The last two digits in the error code indicate the specific cause of the problem. Fault codes various sensors, actuators, electronic and electrical circuits organized into blocks according to the values of the left digit of the two. The right number in the block corresponds to more specific information. For example, low or high voltage, signal out of range, etc.

Code P0113 is deciphered taking into account the above as follows: P - malfunction of the power unit control systems, 0 - code set by SAE, 1 - fuel and water supply system, 13 - high signal level of the air temperature sensor in the intake manifold.

Depending on the degree of significance for environmental safety, error codes for various faults can be divided into four types:

Type A codes. Type A error codes reflect the presence of a malfunction that leads to an increase in the amount of toxic substances emitted by the vehicle into the environment. In addition, such malfunctions can damage the catalytic converter. Therefore, the DE subroutine writes type A error codes into the ECU memory and turns on the MIL when a malfunction is detected on the first trip. Examples: misfires in the ignition system, over-rich or over-lean TV mixture.

Type B Codes Type B codes are stored in the ECU and the MIL will illuminate if one of the diagnostic tests is not completed on two consecutive trips. Codes of types A and B are associated with malfunctions that lead to an increase in the amount of toxic substances produced by the car. When they are entered into the ECU's memory, the MIL light comes on, usually labeled “Check Engine” or “Service engine soon”.

Type C and D codes refer to faults not related to increased contamination environment. Their appearance in the ECU memory causes the “Service” indicator to turn on, if available.

In this article we will talk about such a phenomenon in the Windows operating system as - Blue Screen of Death or in our opinion blue screen of death", also called STOP error. Let's look at the main causes and decipher these error codes.

First, let's define what " Blue Screen of Death"is a way to generate a fatal error message in the operating systems Windows NT 4.0, Windows 2000, Windows 2003, Windows XP, Windows Vista and Windows 7 caused by malfunctions of some programs or drivers, but still more often due to hardware failures of the computer.

Blue screen causes all processes in the operating system to stop and the computer to freeze after displaying a blue screen. In general, the blue screen helps us, you may ask why, but because it prevents destruction operating system and decommissioning of equipment. When " blue screen of death» the error code and how to solve it are displayed. But it may be that the STOP error was caused, for example, by distortion of data packets transmitted over the local network, in this case it helps simple reboot. If the error appears every time you start the operating system, then this may already be a problem related to the computer hardware, for example damage to drivers, file system, hard drive, blocks RAM memory. But to find out the reasons for the error that occurred, it is necessary to rewrite the first two output lines of the STOP error. For example, as shown just below:

STOP 0x0000006B (0xC0000022, 0x00000000, 0x00000000, 0x00000000) PROCESS1_INITIALIZATION_FAILED

Where 0xC0000022, 0x00000000, 0x00000000, 0x00000000- parameters that reveal the meaning of this BSoD.

By the way, there is a small feature, it lies in the fact that in the operating system, in order to see the blue screen, you must first turn on this windows possibility, or you simply won’t see this screen; if an error occurs, the computer will simply reboot quickly (and so on every time).

To enable this option, go to the properties of "My Computer", select the "Advanced" tab. In the "Boot and Recovery" field, click the "Options" button. In the window that appears, uncheck the box next to “Perform automatic reboot.”

When a STOP error appears, the text of the message briefly describes the method for solving it. English language. But I can say for sure that currently the common cause of STOP errors is hardware problems with the computer hardware or its software parts, and sometimes due to inconsistencies between one and the other.

Now let's move on directly to the errors themselves and look at the reasons for their occurrence and short solutions.

0x00000001: APC_INDEX_MISMATCH

Internal kernel error. The problem is most often associated with a driver problem, lack of RAM or hard drive space.

0x0000000A: IRQL_NOT_LESS_OR_EQUAL

Virtual memory tampering occurred on an internal IRQ process high level. The most common cause is that the device driver is using the wrong address. The error occurs due to bad drivers. Rarely occurs due to a malfunction of one of the devices in the system.
Options:

Address where the erroneous request was made
IRQL that was used to access memory
Memory access type: 0 = read operation, 1 = write operation
Address of the instruction that requested memory access at address

0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

This is a very common mistake. Typically the excluded address points to the driver or function that caused the freeze screen. Always pay attention not only to the specified driver, but also to the address or image itself that contains this error. This is usually the exception code 0x80000003. This error means that a breakpoint or handler was initialized during a memory access, but the system booted with the /NODEBUG switch. This error may not appear too often. If the error appears constantly, make sure that the debugger is connected and the system boots with the /DEBUG key.
On non-Intel systems, if the exception address is 0XBFC0304, the error occurs due to processor caching. If the error persists, contact your processor manufacturer.
Typically, you need to look at the second parameter of this message, which indicates the address of the driver/function that was causing the problem.
Options:

Exception code
Address that failed to process
Parameter 0 - exception
Parameter 1 - exception

0x00000020: KERNEL_APC_PENDING_DURING_EXIT

The error name indicates a damaged/disabled APC counter. If you have this situation, check all file systems installed on the machine, for example using the EMRD rescue kit.
The current IRQL should be equal to zero. If the IRQ is not zero, then the specific order in which drivers are unloaded when returning to a higher IRQ level may cause an error. Try to remember what you were doing or what applications you closed, what drivers were installed at the time the blue screen occurred. This symptom indicates a serious problem with third-party drivers.
Options:

APC address at the time of failure.
Failed APC thread
Current IRQ level

0x00000023: FAT_FILE_SYSTEM

FAT).

0x00000024: NTFS_FILE_SYSTEM

There was a failure to read or write to a hard disk partition with the format NTFS. The failure may be due to damage to the file system, or to the appearance of bad sectors on the disk. The failure may also be due to software that changes the disk structure ( encryption programs, etc.).

0x0000002A: INCONSISTENT_IRP

I/O Request Packet (IRP) is not functioning; Occurs when a field or multiple fields are incorrect compared to the preserved state of the IRP. For example, the IRP was already disabled when a device driver was waiting for a command.
Options:
1 - the address at which the IRP was found in idle mode

0x0000002B: PANIC_STACK_SWITCH

This error occurs when the kernel stack area is full. The error occurs when the kernel driver uses too much stack space. A possible cause of the error could also be damage to the kernel itself.

0x0000002E: DATA_BUS_ERROR

This STOP error most often occurs due to a failure in the RAM area. This can happen when the driver tries to access a memory address that does not exist.
Options:

Virtual memory address that caused the error
Physical address of the error cause
Processor Status Record (PSR)
Error Instruction Logging (FIR)

0x00000031: PHASE0_INITIALIZATION_FAILED

System initialization could not be completed at an early stage (phase 0). It is necessary to study the error in more detail, since this code errors mean virtually nothing.
0x00000032: PHASE1_INITIALIZATION_FAILED
System initialization could not be completed at a late stage (phase 1). It is necessary to study the error in more detail, since this error code does not say practically anything.
Options:

System level code that describes why the system believes that initialization has not completed
Indicates the location within INIT.C where phase 1 initialization failed

0x00000035: NO_MORE_IRP_STACK_LOCATIONS

A high level driver tried to call the driver low level via the IoCallDriver() interface, but the system did not have free space in the stack area, for this reason the low-level driver will not reach required parameters, since there are no parameters for it at all. This is a fatal situation because the high-level driver thinks it has filled in the parameters for the low-level driver (something it had to do to call the low-level driver). However, since there is no free space in the stack area, the end of the packet was overwritten. This often occurs due to corruption of stack memory blocks. It is necessary to check the memory and drivers for errors.
Options:
1 - IRP address

0x00000036: DEVICE_REFERENCE_COUNT_NOT_ZERO

The device driver tried to remove one of the components of its device from the system, but the hit counter of this component was not equal to zero - this means that there are some uncompleted tasks behind this component (the counter indicates an error code, which is why this component cannot be unloaded). This is a driver call error.
Options:
1 - object address

0x0000003E: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED

A multiprocessor system is not symmetrical with respect to each other. For proper symmetry, processors must be of the same type and level. For example, trying to use a Pentium-level processor and an 80486 at the same time will generate an error. In addition, on x86 systems, floating point capabilities must be available on all processors or on none.

0x0000003F: NO_MORE_SYSTEM_PTES

There are not enough PTE (page file entries - access points to the paging file). Usually the cause is a driver that does not clean out the swap file well and it becomes full. The cause may also be excessive fragmentation of the paging file.

0x00000040: TARGET_MDL_TOO_SMALL

The driver called IoBuildPartialMdl() and passed the MDL to it to reveal the source portion of the MDL, but the destination MDL area is not large enough to show the limits of the required addresses. This is a driver error.

0x00000041: MUST_SUCCEED_POOL_EMPTY

The system driver has requested space in the Must Suceed Pool. This function cannot be done because the system does not allocate space in the Must Suceed Pool. Replace or update the faulty system driver.
Options:

Amount of request required
Page number used
Number of pages requested
Number of available pages

0x00000044: MULTIPLE_IRP_COMPLETE_REQUESTS

The driver requested completion of the IRP, but the packet was already completed. This error is difficult to detect. Possible cause: the driver is trying to complete the same operation several times. Rare reason - 2 various drivers trying to take possession of the package and terminate it. The first one usually works, but the second one doesn’t. It is difficult to track which driver did this, since traces of the first driver were overwritten by the second.
Options:
1 - IRP address

0x00000048: CANCEL_STATE_IN_COMPLETED_IRP

This error indicates that the I/O Request Packet (IRP) that must be terminated has a cancellation order defined within it, i.e. this means that a package in this mode can be canceled. However, the package no longer belongs to the driver, since it has already entered the final stage.
Options:
1 - IRP address

0x00000049: PAGE_FAULT_WITH_INTERRUPTS_OFF

Page fault when accessing memory with IRQ interrupts disabled. The error description is the same as 0x0000000A.

0x0000004C: FATAL_UNHANDLED_HARD_ERROR

Critical unrecognized error. Most probable reasons described in 0xC0000218, 0xC000022A or
0xC0000221.

0x0000004D: NO_PAGES_AVAILABLE

There is no more free page memory to complete the operation. Check the available disk space. Replace the driver. Options:

Number of pages used
Quantity physical pages by car
Extended page size
Overall page size

0x0000004E: PFN_LIST_CORRUPT

The reason is a damaged/faulty driver I/O structure. Options:

Value 1
ListHead value that is corrupted
Number of available pages

Value 2
Data that is deleted
Maximum number of physical pages
Summary of deleted data

0x00000050: PAGE_FAULT_IN_NONPAGED_AREA

Occurs when the requested information was not found in memory. The system checks the page file, but the missing information was indicated as not being able to be written to the page file.
Options:
1. indicates the address in memory that made an error

0x00000051: REGISTRY_ERROR

An I/O error occurred with the registry when the system tried to read one of its files, which suggests that the error could be caused by a hardware problem or damage to the system itself. This could also mean that the error is caused by an update operation that is only used by the security system and this error occurs when resources are running low. If such an error occurs, check whether the machine is PDC or BDC and how many accounts are in the database SAM data(Account Security Manager), whether the corresponding libraries are almost completely filled.
Options:
1. value 1 (indicates where the error occurred)
2. value 2 (indicates where the error occurred)
3. may point to a library
4. may be HvCheckHive's return code, if any
library is damaged

0x00000058: FTDISK_INTERNAL_ERROR

The system booted from the restored primary partition of the array, as a result of which the libraries report that the mirror is ok, but in fact it is not. The real library images are in the shadow copy. You need to boot from them.

0x00000067: CONFIG_INITIALIZATION_FAILED

The error means that the registry cannot allocate the space required for the registry files to function. This error can never appear because the process of reserving such space occurs early in the system boot and sufficient space is allocated for the registry.
Options:
1. five
2. Points to NTOS\CONFIG\CMSYSINI, which failed.

0x00000069: IO1_INITIALIZATION_FAILED

Failed to initialize I/O device unknown reason. This happens if the system installer incorrectly identified the equipment during the system installation process, or the user incorrectly reconfigured the system.

0x0000006B: PROCESS1_INITIALIZATION_FAILED

Options:
1. reports to the process code that decided that system initialization was not successful.
2. reports to the location in NTOS\PS\PSINIT.C where the error was detected.
0x0000006D: SESSION1_INITIALIZATION_FAILED 0x0000006E: SESSION2_INITIALIZATION_FAILED 0x0000006F: SESSION3_INITIALIZATION_FAILED 0x00000070: SESSION4_INITIALIZATION_FAILED 0x00000071: 5_INITIALIZATION_FAILED
These codes (SESSION1 - SESSION5) indicate the location in NTOS\INIT\INIT.C where the error was made.
Options:
1. reports the session code that decided that system initialization was not successful.

0x00000073: CONFIG_LIST_FAILED

Indicates that one of the registry files is corrupted or unreadable. One of the following registry files is damaged: SOFTWARE, SECURITY, SAM (Account Security Manager). A possible reason is lack of disk space or insufficient RAM.

0x00000074: BAD_SYSTEM_CONFIG_INFO

This error may occur because the SYSTEM registry file loaded through the NTLDR component is corrupted.
This error may also mean that some required parameters and their parameters are missing. Loading into LastKnownGood may solve this problem. But it is possible that you will have to reinstall the system, or use a rescue disk.

0x00000075: CANNOT_WRITE_CONFIGURATION

This error can occur when additional data cannot be written to the system registry files (SYSTEM and SYSTEM.ALT) during the first phase of registry initialization (when file systems are accessed). This error means there is no free disk space and an attempt was made to save the registry to a read-only device.

0x00000076: PROCESS_HAS_LOCKED_PAGES

This error may occur due to a driver that is not completely unloaded after an I/O operation. Options:
1. process address
2. number of closed pages
3. number of reserved pages
4. zero

0x00000077: KERNEL_STACK_INPAGE_ERROR

Error reading one of the system kernel pages. The problem is a bad block of the virtual memory file or a disk controller error (very rarely, the cause may be a lack of system resources, or more precisely, the non-virtual memory reserve may run out with status c0000009a).
If the first and second parameters of the error code are 0, then this means that the error location in the kernel was not found. This means that the error is caused by bad hardware.
I/O status 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 reboot automatic check disk will try to determine the address of the bad block in memory. If the status is C0000185 (STATUS_IO_DEVICE_ERROR) and virtual memory located on a SCSI disk, then check the connection and operation of the SCSI device.
Options:
1. zero
2. zero
3. PTE value at the time of the error
4. kernel error address or

1. status code
2. I/O status code
3. virtual memory page number
4. Offset in the paging file

0x00000079: MISMATCHED_HAL

The HAL check level and HAL configuration type are not appropriate for the system kernel or machine type. This error is most likely caused by the user manually updating either NTOSKRNL.EXE or HAL.DLL. Either the machine has a multiprocessor HAL (MP) and a uniprocessor kernel (UP), or vice versa.

0x0000007A: KERNEL_DATA_INPAGE_ERROR

The page requested by the kernel is not read. The error is caused by a bad block in memory or a disk controller error. See also 0x00000077. Options:
1. stuck lock type
2. error status (usually I/O code)
3. current process (virtual address for blocking type 3 or PTE)
4. virtual memory address that cannot be moved to the page file

0x0000007B: INACCESSIBLE_BOOT_DEVICE

During the installation of the I/O system, the driver boot device, may have failed to initialize the device from which the system was trying to boot, or the file system that was supposed to read that device either failed to initialize, or simply did not recognize the information on the device as a file system structure. In the above case, the first argument is the address of a unicode information structure, which is the ARC name of the device from which the attempt was made to boot. In the second case, the first argument is the address of a device object that cannot be mounted.
If this error occurred during the initial installation of the system, the system may have been installed on a disk or SCSI controller that is not supported by it. Please note that some controllers are only supported by Windows Driver Driver Libraries (WDL), which must be installed in Custom Install mode.
This error can also occur after installing a new SCSI adapter or controller or after changing system partitions. In this case, on x86 systems, you need to edit BOOT.INI.
Options:
1. pointer to a device object or Unicode string, or ARC name.

0x0000007D: INSTALL_MORE_MEMORY

There is not enough RAM to run the Windows kernel (5 MB required)
Options:
1. number of found physical pages
2. bottom physical page
3. top physical page
4. zero

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED

There is a hardware problem, driver problem, or low disk space detected. The error may also appear when trying Windows updates XP to Service Pack 2 or Service Pack 3, or Windows Vista when trying to upgrade to Service Pack 1. The cause of the error may be related to hardware drivers. It is necessary to roll back the changes to the state at the time of installing the Service Pack, or remove the installed update. To solve this problem, you need to update the hardware drivers from the manufacturer's website.

0x0000007F: UNEXPECTED_KERNEL_MODE_TRAP

An unexpected kernel-mode exception, or interrupt, occurred in which the kernel does not fire. Also, the cause of the error can be an interruption, which entails immediate death in the form of a double fault. The first number in the error code is the interrupt number (8 = double fault). To find out more about what this interrupt is, refer to the Intel x86 family manual.
In other words, the error appears when the processor makes an error that the kernel cannot handle. Most often the error occurs due to bad RAM blocks and sometimes due to overclocking the processor.
Try disabling the synchronous data transfer function in the BIOS.

0x00000080: NMI_HARDWARE_FAILURE

Error initializing the kernel on this hardware. HAL should provide any specific information it has and encourage the user to contact the hardware vendor for technical support.

0x00000085: SETUP_FAILURE

An error occurs when loading the system installer in early Windows versions N.T. The "setup" text form no longer uses a bugcheck procedure to avoid causing significant interference during installation. Therefore, you will never encounter this error. All error checks have been replaced with friendlier and (where possible) more informative messages about errors.

0x0000008B: MBR_CHECKSUM_MISMATCH

The error occurs during the boot process when the MBR checksum calculated by the system does not match the bootloader checksum. This usually means a virus. Scan boot sector antivirus program after booting from the CD.
KerBugCheckEx parameters:
1 - Disk signature in MBR
2 - MBR checksum written to osloader
3 - MBR checksum recorded in the system

0x0000008E: PAGE_FAULT_IN_NON_PAGED_AREA

Incompatible or faulty RAM memory blocks. Diagnose the memory and replace faulty RAM modules.

0x0000008F: PP0_INITIALIZATION_FAILED

The error occurs during phase 0 initialization of the Plug and Play manager in kernel mode. Check your hardware and system disk.

0x00000090: PP1_INITIALIZATION_FAILED

The error occurs during initialization of the primary phase of the Plug and Play manager in kernel mode. At this point, initialized system files, drivers and registry. Check your hardware and system disk.

0x00000092: UP_DRIVER_ON_MP_SYSTEM

The error occurs when a single-processor driver is loaded on a system where there is more than one active processor. KeBugCheckEx parameters: 1 - Base address single processor driver

0x00000093: INVALID_KERNEL_HANDLE

The error appears when kernel code or other critical components The OS is trying to close a handle that is not valid.
Options:
1 - NtClose handle called
2 - 0 means the protected handle was closed
1 means the wrong handle was closed
0x00000094: KERNEL_STACK_LOCKED_AT_EXIT
This message appears when a thread exists while its stack is marked as blocked. The problem is caused by a hardware driver.

0x00000096: INVALID_WORK_QUEUE_ITEM

0x00000097: BOUND_IMAGE_UNSUPPORTED

The problem is caused incorrect driver equipment.

0x00000098: END_OF_NT_EVALUATION_PERIOD

Demo version running time Windows systems ended. Options:
1 - Installation date (lower 32-bits)
2 - Installation date (upper 32-bits)
3 - Trial period in minutes.

0x00000099: INVALID_REGION_OR_SEGMENT

ExInitializeRegion or ExInterlockedExtendRegion was called with the wrong set of parameters.

0x0000009A: SYSTEM_LICENSE_VIOLATION

A violation of the software license agreement has occurred. This could be either due to an attempt to change the system product type, or an attempt to change the OS trial period.

0x0000009B: UDFS_FILE_SYSTEM

There was a failure to read or write to UDFS-formatted media. The failure may be due to damage to the file system, or to the appearance of bad sectors on the disk. The failure may also be due to software that changes the disk structure (encryption programs, etc.).

0x0000009C: MACHINE_CHECK_EXCEPTION

Fatal error Machine Check Exception. The error is related to incorrect configuration equipment, processor overclocking, unstable operation of RAM units, overheating of system components, unstable operation of the power supply.

0x0000009F: DRIVER_POWER_STATE_FAILURE

The driver is in an inconsistent or unacceptable power consumption state. This usually happens due to power failures, rebooting, resuming from sleep mode, etc. It is necessary to replace the faulty driver, or remove software that controls the file system (antiviruses, encryption programs

0x000000A5: ACPI_BIOS_ERROR

Reason of this message are constant failures in ACPI BIOS. This problem cannot be solved at the operating system level. A detailed analysis is required.

0x000000B4: VIDEO_DRIVER_INIT_FAILURE

Windows was unable to load the video card driver. The problem is mainly related to the video drivers, or there is a hardware conflict with the video card. Reboot into safe mode and change the video driver to the standard one.

0x000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY

The driver attempted to write data to a read-only memory (ROM) device that cannot be written to. The problem is mainly due to the installation of a bad device driver, service or firmware. Change the driver.
_MEMORY_CORRUPTION
The driver wrote data to an invalid memory section. Change the driver.

0x000000C2: BAD_POOL_CALLER

The system kernel or driver issued an incorrect memory access command. Typically, a bad driver or software caused this error. Change the driver.

0x000000C4: DRIVER_VERIFIER_DETECTED_VIOLATION

The driver checker detected fatal error in the STOP error generation module. Accompanying parameters are parameters that are passed to KeBugCheckEx and displayed on the blue screen. Change the driver.

0x000000C5: DRIVER_CORRUPTED_EXPOOL

An attempt was made to access a high-level IRQL process from an invalid memory location. This error almost always occurs due to drivers that have corrupted the system pool. Change the driver.

0x000000C6: DRIVER_CAUGHT_MODIFYING_FREED_POOL

The driver attempted to access a freed memory pool. Change the driver.

0x000000C7: TIMER_OR_DPC_INVALID

A kernel timer or Delayed Procedure Call (DPC) is present in a prohibited memory location. This error occurs when the driver was unable to complete a kernel timer or Delayed Procedure Call (DPC) before discharging it from memory. Change the driver.

0x000000C9: DRIVER_VERIFIER_IOMANAGER_VIOLATION

This message is from one of the driver verification managers. Change the driver.

0x000000CB: DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS

An error similar to STOP error 0x00000076. It differs from the latter only in that in this case the error was detected during kernel tracing. The error indicates that the driver or I/O manager is unable to open locked pages after an I/O operation. Pay attention to the name of the application driver in the STOP error window. Change the driver.

0x000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

The driver cannot cancel the frozen state of system components. The error usually occurs after installing bad drivers or service components. Change the driver.

0x000000D1: DRIVER_IRQL_NOT_LESS_OR_EQUAL

The system attempted to access paged memory using a kernel process via a high-level IRQL. The most common reason is a bad device driver. This may also be caused by damaged RAM, or a damaged page file.

0x000000D8: DRIVER_USED_EXCESSIVE_PTES

The error occurs when the driver requests a large amount of kernel memory.

0x000000E3: RESOURCE_NOT_OWNED

Various file system related failures result in this STOP error. The problem may be related to the NTFS.SYS driver.

0x000000EA: THREAD_STUCK_IN_DEVICE_DRIVER

A problematic device driver has caused the system to freeze. Typically, this is caused by the display driver when the computer tries to enter standby mode. This problem is related to the video adapter, or bad video driver.
There was a problem connecting boot disk. The error can occur on computers with high-performance disk controllers that were not configured and installed correctly, or were connected with a poor-quality cable. After a normal reboot, the system can resume normal work, as if nothing had happened. This error also appears after incorrect completion Windows operation and the failure may be due to file system corruption.

0x000000F2: HARDWARE_INTERRUPT_STORM

This message appears when the kernel detects an interrupt storm, that is, when a device triggered by an interrupt level is unable to issue an interrupt request. Usually, this is caused by a bad device driver.

0x000000F3: DISORDERLY_SHUTDOWN

Windows shutdown crashed due to insufficient memory. Determine which program is running out of memory, try to discover why virtual memory is not providing the system resources it needs, and investigate whether the program (or sometimes a driver) refuses to exit without freeing open pages in memory.

0x000000FA: HTTP_DRIVER_CORRUPTED

The Http.sys system driver is corrupted. This component must be restored from the original disk.

0x000000FC: ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY

An attempt was made to execute a function in non-executable memory. Options:
1 - Address from which the attempt was made to execute the function
2 - Contents of page table entry (PTE)
0x000000FD: DIRTY_NOWRITE_PAGES_CONGESTION
There is no free page memory to continue basic system operations.
Options:
1 - Total amount of paged memory requested
2 - The amount of paged memory requested that cannot be written to.
3 -
4 - Status code at the moment last entry to page memory

0x000000FE: BUGCODE_USB_DRIVER

A critical error occurred USB controller and related devices. The problem is usually caused incorrect work USB controller, or a malfunction of the connected USB devices. Disconnect all USB devices from the computer, also try disabling the USB controller in the BIOS. Update USB drivers.

0x00000101:CLOCK_WATCHDOG_TIMEOUT

Indicates that an expected clock interrupt on a secondary processor in a multiprocessor system was not received within a specified interval. This processor does not handle interrupts. Typically, this happens when the processor is not responding or has entered an infinite loop.
Options:
1 - Interval for blocking the clock interrupt time, in
nominal system clock cycles
2 - zero
3 - Address of the processor control block (PRCB) for non-response
processor
4 - zero

0x00000104: AGP_INVALID_ACCESS

Recording attempt GPU into memory that was not reserved for this. The error is related to the video driver or an old BIOS version.
Options:
1 - Offset (in ULONG) within AGP pages to the first data
ULONG whose data is destroyed
2 - zero
3 - zero
4 - zero

0x00000105: AGP_GART_CORRUPTION

The error appears when the Graphics Aperture Remapping Table (GART) is damaged. The error is caused by the DMA (Direct Memory Access) driver not working properly.
Options:
1 - Base address (virtual) in GART
2 - Offset in GART where distortion is detected
3 - Base address (virtual) from GART cache (GART copy)
4 - zero

0x00000106: AGP_ILLEGALLY_REPROGRAMMED

The error is caused by an unsigned or damaged video driver. Replace the video driver. Options:
1 - Original team
2 - Current team
3 - zero
4 - zero

0x00000108: THIRD_PARTY_FILE_SYSTEM_FAILURE

A critical error occurred in a third-party file system filter. The error may be caused by antivirus software, defragmentation programs, data backup programs, and others. third party utilities. Try also increasing the size of the page file and RAM.

0x00000109: CRITICAL_STRUCTURE_CORRUPTION

The system kernel has detected incorrect code or data integrity violation. 64-code based systems are protected from this bug. The problem could be caused by a RAM failure or third party drivers.

0x0000010E: VIDEO_MEMORY_MANAGEMENT_INTERNAL

Discovered Internal error video drivers. Video driver problem.

0x0000010F: RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED

An exception occurred in the kernel-mode resource manager.

0x00000112: MSRPC_STATE_VIOLATION

The msrpc.sys system component returned an error code during execution. The error code is specified in the first parameter.

0x00000113: VIDEO_DXGKRNL_FATAL_ERROR

The DirectX Graphics kernel has encountered a critical error.

0x00000114: VIDEO_SHADOW_DRIVER_FATAL_ERROR

The shadow video driver has encountered a critical error.

0x00000115: AGP_INTERNAL

A critical error was detected in the AGP video interface by the video port driver.

0x00000116: VIDEO_TDR_ERROR

The video driver timeout reset was not successful.

0x0000011C: ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE

An attempt was made to write to the write-protected area of the configuration manager: Parameters:
1 - Virtual address of the attempted write command
2 - Contents of PTE
3 - reserved
4 - reserved The name of the driver attempting the write operation is printed as
Unicode string on error screen.

0x00000121: DRIVER_VIOLATION

The driver has violated access to one of the memory areas. Options:
1 - describes the type of violation
2 - reserved
3 - reserved Use a kernel debugger and look at the call stack to determine
the name of the driver that caused the access violation.

0x00000122: WHEA_INTERNAL_ERROR

An internal error occurred in the hardware error detection architecture Windows tools (Windows Hardware Error Architecture (WHEA)

0x00000124: WHEA_UNCORRECTABLE_ERROR

An error has occurred in the computer hardware. This error is detected by the Windows Hardware Error Architecture (WHEA)

0x00000127: PAGE_NOT_ZERO

The memory page was not completely filled with zeros. This error occurs due to a hardware failure, or due to a privileged operating system component triggering a premature page change in memory.
Options:

page.
2 - Physical number pages
3 - zero
4 - zero

0x0000012B: FAULTY_HARDWARE_CORRUPTED_PAGE

A single bit error was detected on the memory page. This error is related to hardware RAM. Options:
1 - Virtual address in memory, which indicates an incorrect
page.
2 - Physical page number
3 - zero
4 - zero

0x0000012C: EXFAT_FILE_SYSTEM

There was a failure to read or write to a media partition in exFat format. The failure may be due to damage to the file system, or to the appearance of bad sectors on the disk. The failure may also be due to software that changes the disk structure (encryption programs, etc.). This failure applies to media formatted for Windows Vista Service Pack 1.

0x1000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
0x1000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED_M
0xC000009A: STATUS_INSUFFICIENT_RESOURCES

The system kernel of the operating system has exhausted everything system resources for your work, including the swap file. Check the disk for errors. Increase the size of your hard drive and the amount of RAM.

0xC0000135: UNABLE TO LOCATE DLL

Windows tried to boot DLL library and received an error code. Possible reason: the file is missing or damaged. Possibly also damaged system registry.

0xC0000142: DLL Initialization Failure

This error was caused by damage system DLL libraries.

0xC0000218: UNKNOWN_HARD_ERROR

A required registry file cannot be loaded. The file may be damaged or missing (a rescue disc or reinstallation of Windows is required). The system registry files may have been destroyed due to hard drive corruption. The driver may have corrupted registry data when loading into memory, or the memory where the registry was loaded has a parity error (turn off external cache and check your RAM).

0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED

This occurs when Windows has switched to privileged mode and non-privileged mode subsystems, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), have caused some kind of failure and protection cannot be guaranteed. Because Windows XP cannot run without Winlogon or CSRSS, this is one of the few situations where a non-privileged mode service failure can cause the system to stop responding. This can also happen when the computer is restarted after the system administrator has changed permissions so that SYSTEM Account no longer had adequate permissions to access system files and folders. The error can also be caused by corruption of the user32.dll file or incorrect system drivers (.sys)

0xC0000221: STATUS_IMAGE_CHECKSUM_MISMATCH

the driver is damaged or system library was recognized as damaged. The system does everything to check the integrity of important system files. The blue screen shows the name of the damaged file. If this happens, boot into any other system or, if there are none, reinstall the system. Make sure that the version of the file that was detected as damaged matches the version of the file in the system distribution and if so, replace it from the disk. Constant errors with different file names indicate that there are problems with the storage media or with the disk controller where these files are located.

0xC0000244

A STOP error occurs when the audit policy enables the CrashOnAuditFail setting

0xC000026C

Typically indicates device driver problems. More information about this error

0xDEADDEAD: MANUALLY_INITIATED_CRASH1

"It's dead, Jim!" (It's dead, Jim!) This STOP error indicates that the user intentionally triggered a crash, either from the kernel debugger or the keyboard.

Here is a small list of errors that can appear in the operating systems Windows NT 4.0, Windows 2000, Windows 2003, Windows XP, Windows Vista and Windows 7. Everyone is afraid of the blue screen of death, but in fact, if it didn’t exist, the computer would simply break down , and you would have to have your equipment repaired, or buy a new one, or maybe even the entire computer. Therefore, let's pay tribute to the developers of this operating system, who take care of our wallets. This is where we end our conversation about the famous “ Blue screen of death».

How to decipher codes Windows errors?

If your computer displays one of the following errors, you can try to solve it yourself.
Error code: 52
Description: Failed to connect to the network due to the existence of matching names.
Elimination method: This error usually occurs when registering a computer on a network. The reason is that the IP address of the VPN connection (this address is assigned automatically) matches the IP address that is already in the system. Check what address is assigned to the DVB board, 1394 Adapter, Microsoft Loopback Adapter, or other connection, if any, in general it should be 192.168.138.138 (mask 255.255.255.0).

Error code 600, 601, 603, 606, 607, 610, 613, 614, 616, 618, 632, 635, 637, 638, 645

An internal Windows error has occurred

Restart your computer. If the error persists, check your computer for viruses. Remove recently installed programs, or undo recent changes to Windows settings, if there were any.

Error code 604, 605, 608, 609, 615, 620

File phone book Windows Remote Access subsystems and the current Remote Network Access configuration are incompatible with each other

Restart your computer. If the error persists, delete and re-create the VPN connection

Error code 611

Restart your computer and make sure that the local network functions normally on the computer. If the error does not disappear, contact technical service. support

Error code 612

Windows internal network configuration is not configured correctly

Similar to error 611. In addition, the error may be caused by a lack of resources (memory) on the computer. Try closing running programs.

Error code 617

Windows is in the process of connecting to the Internet, or an internal Windows error has occurred

Wait a few minutes. If the connection is not established and the error persists when connecting again, restart your computer

Error code 619

Security settings are incorrectly configured VPN connections, VPN traffic is blocked on the way to the gateway, or the VPN settings have not taken effect

In the properties of the VPN connection, open the "Security" tab - "Normal (recommended settings)" should be selected and the "Data encryption required (otherwise disable)" checkbox should be unchecked. Restart your computer and try connecting again. Check your firewall settings, and if you are not sure they are correct, disable it.

Error code 629

The VPN connection was disconnected due to Bad quality communication or after unsuccessful negotiation

Contact the service technical support.

Error code 633

The modem is already in use or not configured for outgoing calls

A VPN device that should be used by the network cannot be opened. Contact technical support.

Error code 635

An error occurred in Windows

Try reinstalling the VPN connection, or reinstalling Windows entirely. If all else fails, contact technical support.

Error code 642

Your computer is assigned a NetBIOS name that is already in use on the network.

Change the computer name in the properties of "My Computer" in the "Identification" section.

Error code 650, 721

VPN server is not responding

Check your settings network adapter and make sure the local network is working. If you checked everything, but found no errors, call technical support.

Error code 678, 718, 769

There is no response from the VPN (PPPoE) server.

Check if the local network is working. Check your VPN (PPPoE) connection settings and firewall settings (if installed on your computer). If all else fails, contact technical support.

Error code 691

The login or password has been entered incorrectly, or the funds in the account have run out

Make sure that when entering your login and password, the " Caps Lock" on the keyboard is turned off, and set English layout. If you are sure that you are entering your login and password correctly, and there are funds in your account (you can check this in personal account), then contact our network technical support.

Error code 734

The PPP link control protocol was interrupted

Check your VPN connection security settings:
open the "Security" tab - "Typical (recommended settings)" should be selected and the "Data encryption required (otherwise disabled)" checkbox should be unchecked

Error code 735

VPN connection is not configured correctly

Make sure that in the network settings (more precisely, in the TCP/IP protocol settings) of the VPN connection, a specific IP address is not specified, and all parameters are obtained automatically.

Error code 741, 742, 743

Encryption settings are incorrectly configured

Go to the VPN connection settings and disable the “data encryption” item.

Error code 789

Invalid selected VPN type connections

Go to the VPN connection settings and on the "Network" tab, from the "VPN Type" list, select "PPTP VPN". Try connecting again.

Error code 797

The computer settings indicate a name that is already in use

In the network identification settings, enter your login in the "computer name" field, and in the " working group" enter "netbynet" (without quotes).

Error code 800

No access to VPN server

Make sure that the local network is turned on and working, and that VPN settings server in the "Computer name" field contains the address "ppp.lan" (without quotes). Try to re-create the connection; if unsuccessful, contact technical support.

Probably every owner of a car with an injection engine has encountered various errors in the operation of this unit. This trouble is indicated by the corresponding sign on the instrument panel - “engine error”. Many will immediately go to the service station for diagnostics, while others will drive with this problem. But the third group of people will definitely be interested in the reasons and deciphering of the codes.

ECU in cars

The operation of the mentioned part is invisible, but this unit starts immediately after the driver turns on the engine.

In some car models, electronics control parameters even after the car is stopped.

Each ECU on any car is equipped with a special controller, which, when various malfunctions are detected, responds to them by lighting the “engine error” indicator. Each error has its own code and remains in the computer's memory. Some problems are not only completely saved, but the time they were detected by the system is also recorded. This option is called "freeze frame".

- causes

A light that reports errors on dashboard just one. However, they can have many reasons. This can be found out without special equipment or a trip to a service station.

Lambda probe

The oxygen sensor is part of the exhaust system. It checks how much oxygen is not burned in the engine cylinders. The lambda probe also monitors fuel consumption.

Various malfunctions of the named sensor do not allow the ECU to receive information from it. Sometimes this element provides incorrect information. Such breakdowns can increase or decrease fuel consumption and reduce engine power. Most modern cars have two to four such sensors.

Among the reasons for the failure of the described element is its contamination with waste oil or oil soot. This reduces the accuracy of information collection for regulating the fuel mixture and determining optimal flow fuel.

Fuel filler cap

Most drivers, when an error occurs, always think about the existence of very serious problems. But few people think to check whether the fuel system is tight. But this same tightness can be easily broken by a gas tank cap that is not tightly closed. And this is a fairly common situation!

What does this have to do with engine error? The fact is that when the lid is not tightly closed, air passes into the system, which increases fuel consumption. Because of this, the diagnostic system generates an error.

Catalyst

VAZ

To independently diagnose a VAZ, you can also use the diagnostic connector, but it is also permissible to do this by the vehicle itself. To do this, you need to hold down the odometer button, then turn the key to the first position, then release the button. After this, the arrows will jump.

Then the odometer is pressed again - the driver will see the firmware number. When pressed a third time, a diagnostic code can be obtained. Any VAZ engine error in a car will be presented as two digits, not four. They can be deciphered using the corresponding tables.

The information provided can help experienced and novice car enthusiasts better understand their car. Errors arise from time to time, but the main thing is to be able to eliminate them in time. Previously, there were no such options in Soviet cars, and the driver could not know what the engine was “swearing” at. Today there are many possibilities for diagnostics, repair, and condition monitoring. And with the help of modern software there is nothing easier than figuring out how to reset an engine error from the ECU memory.

To get information about the error, enter its code in the text field just below in following format: 7e or 0x0000007e

Go to description

UNEXPECTED_KERNEL_MODE_TRAP

This error means that an unexpected kernel-mode exception, or interrupt, occurred in which the kernel does not fire.

Also, the cause of the error can be an interruption, which entails immediate death in the form of a double fault. The first number in the error code is the interrupt number (8 = double fault). To find out more about what this interrupt is, refer to the Intel x86 family manual.

In short, the error appears when the processor makes an error that the kernel cannot handle. Most often the error occurs due to bad RAM blocks and sometimes due to overclocking the processor.

Try disabling the synchronous data transfer function in the BIOS.

Troubleshooting: If you installed new hardware in your computer, you will need to remove it. If the existing hardware caused the failure, then it is necessary to remove or, if necessary, replace the faulty computer components.

Scan your RAM for errors.

Make sure that all computer components are installed properly. Clean the adapter contacts.

Update your BIOS.

All hard drives, controllers hard drives and SCSI adapters must be compatible with the version of Windows installed.

If the driver is identified in the error message, disable or update this driver. Disable or remove any drivers or services that were recently added. If the error occurs during Windows boot and the system partition is formatted with a file NTFS system, use Safe Mode to reinstall or remove the defective driver. If the driver is used as a system startup process in Safe Mode, start the computer using Recovery Console to access the file.

Restart your computer and press F8 in the menu text mode, to display the operating system boot options. IN this menu select “Download latest successful configuration" This option is most effective when adding only one driver or service to the system at a time.

Overclocking central processor may cause an error. Return value clock frequency Default CPU.

Make sure the system is logged into Event Viewer. The error information there will help you identify the device or driver that is causing the 0x0000007F screen of death.

Disable caching BIOS memory.

If the UNEXPECTED_KERNEL_MODE_TRAP error appears when upgrading to a new version of the Windows operating system, it may be caused by a device driver, system service, antivirus program, or program Reserve copy, which are incompatible with new version. Remove everything third party drivers devices and system services, disable antivirus programs.

Install last package Windows updates.

If the previous steps did not solve the problem, take it to motherboard to a repair shop for diagnostics. Cracks, scratches, or defective components on the system board can cause this error.

SPIN_LOCK_INIT_FAILURE

This validation error occurs very rarely.

DFS_FILE_SYSTEM

Distributed file system errors.

Update your OS.

SETUP_FAILURE

A fatal error occurred during installation.

The setup text form no longer uses bugcheck to recover from serious errors. Therefore you will never encounter 0x85. All bug checks have been replaced with friendlier and (where possible) more informative error messages. However, some error writers have simply been replaced by our bugcheck screens, and the code for these error conditions is the same as it was. They are listed below.)

0: OEM HAL font is not a valid *.fon file format, so the installation was unable to display the text. This means that vgaxxx.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 vga.sys file (or other driver, depending on the machine) is damaged, or that this equipment not supported.

Reason for error:

0: NtCreateFile of devicevideo0

3: The desired video mode is not supported. This indicates an internal installation error.

2: Insufficient memory. This error now uses a friendlier screen, depending on how far along the installation is.

3: The keyboard has not been 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.

This may also mean that the keyboard layout dll cannot be loaded.

Reason for error:

0: NtCreateFile of deviceKeyboardClass0 .

The installation did not detect the 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 (kbdus.dll for us or other dlls) on the floppy or CD.

4: The installation was unable to find out the path of the device from which the installation started. This is an internal installation error.

5: The partition functionality test failed. This means a bug in the disk driver. The parameters have meaning only for the installation group.

MBR_CHECKSUM_MISMATCH

This error occurs during operating system boot when the MBR checksum that the operating system calculates Microsoft Windows, does not match the bootloader checksum.

This BSoD indicates the presence of viruses.

It is necessary to scan the operating system for viruses using current antivirus programs.

PAGE_FAULT_IN_NON_PAGED_AREA

This BSoD is a general error. To interpret it, you need to identify what exception was thrown.

The following exception codes exist:

0x80000002: STATUS_DATATYPE_MISALIGNMENT indicates an unaligned data reference;

0x80000003: STATUS_BREAKPOINT. Indicates a situation where the system encounters control point or ASSERT without a kernel debugger attached;

0xC0000005: STATUS_ACCESS_VIOLATION indicates a memory access violation.

To solve the error you need to:

Make sure that the system partition of the disk has enough free space;

If the error message identifies a driver, disable or update it;

Replace the video card;

Update BIOS;

Disable BIOS memory caching and memory shadowing options.

Parameter 2 (exception address) must identify the driver or function that caused the error.

If the reasons for the exception are unclear, consider the following issues:

Hardware incompatibility. Make sure that the newly installed hardware is compatible with the installed version of Windows;

A defective device driver or system service may be causing the error. Hardware issues such as BIOS incompatibilities, memory conflicts, and IRQ conflicts can also generate a blue screen.

If the error indicates the name of the driver, it must be removed or disabled. Also remove or disable any recently added drivers and services. If the error occurs during system startup and the system partition is formatted with the NTFS file system, you must use Safe Mode to remove the defective driver. If the driver is used as part of the system startup process Safe Mode, then to access the file you will need to start the computer using the Recovery Console.

If the BSoD points to the Win32k.sys system driver, the source of the error may be third party program remote control. If such software exists, it must be removed.

Make sure the system is logged into Event Viewer. The error information there will help you identify the device or driver that is causing Stop 0x0000008E.

Disable BIOS memory caching. Update your BIOS firmware.

It is also necessary to perform hardware diagnostics. Scan your RAM for errors.

The KERNEL_MODE_EXCEPTION_NOT_HANDLED blue screen may occur after the first restart during Windows installation, or after installation has completed. A possible reason is lack of disk space for installation. Remove everything temporary files, internet cache files, files backup copies applications and .chk files. You can use another hard drive with a larger capacity.

PP1_INITIALIZATION_FAILED

The error occurs during initialization of the primary phase of the Plug and Play manager in kernel mode. At this point, system files, drivers and the registry have been initialized.

Check your hardware and system disk.

WIN32K_INIT_OR_RIT_FAILURE

UP_DRIVER_ON_MP_SYSTEM

This error only occurs when a single-processor driver is loaded on a system where there is more than one active processor.

INVALID_KERNEL_HANDLE

This error occurs when some kernel code (such as a server, redirector, or other driver) attempted to close an invalid handle or protected handle.

Options:

1 – NtClose handle called

2 – 0 means the protected handle was closed

1 means the wrong handle was closed

The error may also be caused by the client service Novell NetWare version 3.5b.

PNP_INTERNAL_ERROR

INVALID_WORK_QUEUE_ITEM

This error check indicates that a queue entry was deleted that contained a null pointer.

This message appears when KeRemoveQueue removes a data queue while the flink or blink field is 0. This is almost always due to incorrect code application of the current object's running element, but incorrect application of any queue can also result in this error. The rule is that data can be entered into the queue only once. When an element is removed from a queue, its flink field is 0. This error occurs when an attempt is made to delete data whose flink or blink fields are equal to 0. In order to resolve this error, you need to find out the queue it is referencing. If this queue is one of the EX working queues (ExWorkerQueue), then the object that is deleted is WORK_QUEUE_ITEM. This error implies that this is the cause. Error parameters help identify a driver that is not using the queue correctly.

BOUND_IMAGE_UNSUPPORTED

MmLoadSystemImage was called to load the bound image. This is not supported by the kernel. Make sure bind.exe has not been run for the image.

Options:

1 – Address of the data in the queue, the flink/blink field of which is zero.

2 – Address to the referring queue. Typically this is one of the ExWorkerQueues queues.

3 – Starting address of the ExWorkerQueue array. This will help identify if the queue in question is one of the ExWorkerQueue queues and if so, then the offset from this parameter will identify the queue.

4 – If this is an ExWorkerQueue queue (as it usually is), this is the address of the running routine that would be called if the running item were valid. This can be used to identify a driver that is not using the work queue correctly.

The problem is caused by an incorrect hardware driver.

END_OF_NT_EVALUATION_PERIOD

This error check indicates that the trial period for the Microsoft Windows operating system has ended.

INVALID_REGION_OR_SEGMENT

ExInitializeRegion or ExInterlockedExtendRegion was called with the wrong set of parameters.

SYSTEM_LICENSE_VIOLATION

The Microsoft Windows operating system detected a license agreement violation.

BSoD occurs when the user attempts to change the product type of an offline system or when changing probationary period Windows Evaluation Module.

UDFS_FILE_SYSTEM

One possible cause of a blue screen is a damaged hard drive. File system corruption or bad blocks(sectors) on the disk can cause this error. Corrupt SCSI and IDE drivers can also negatively impact the system's ability to read and write to the hard drive, thus causing this error.

Other possible reason– depletion of the non-paged memory pool. During the indexing process, if the amount of available non-paged memory pool is very small, another driver requiring the non-paged memory pool may trigger an error.

Resolve disk corruption: Check Event Viewer for SCSI and FASTFAT (System Log) or Autochk (Application Log) error messages, which can pinpoint the device or driver that is causing the error. Try disabling any antivirus programs, backup programs, or disk defragmenter tools that continuously monitor the system. You should also run hardware diagnostics on the system.

Run the Chkdsk /f /r command to detect and repair any structural damage to the file system. You must restart the system before disk scanning begins on the system partition.

To resolve the non-paged memory pool depletion problem, add new physical memory to the computer. This will increase the amount of non-paged memory pool available to the kernel.

MACHINE_CHECK_EXCEPTION

Fatal error Machine Check Exception.

This happens because your computer's processor detects an error and reports it to Windows XP. To do this it uses Machine Check Exception (MCE) to Pentium processors or Machine Check Architecture (MCA) for some Pentium Pro processors. The error may be caused by the following:

System bus errors

Memory parity problems or Error Correction Code (ECC)

Caching problems in the processor or hardware

Translation Lookaside Buffers (TLB) problems in the processor