Windows stop error number detailed explanation

1. Stop error number: 0x0000000A
Description text: IRQL-NOT-LESS-OR-EQUAL
Normal reason: The driver used an incorrect memory address.
Solution: If you can't log in, restart your computer. When the list of available systems appears, press the F8 key.
On the Windows Advanced Options menu screen, select "Last Known Good Configuration" and press Enter.
Check if all new hardware or software is properly installed. If this is a fresh installation, contact the manufacturer of the hardware or software to obtain any Windows updates or drivers that may be required.
Run all system diagnostic software provided by the computer manufacturer, especially memory check.
Disable or remove newly installed hardware (RAM, adapter, hard drive, modem, etc.), drivers or software.
Make sure that the hardware device driver and system BIOS are the latest versions.
Make sure the manufacturer can help you with the latest version and help you get the hardware.
Disable BIOS memory options such as cache or shadow.

2, stop error number: 0x0000001E
Description text: KMODE-EXPTION-NOT-HANDLED
The usual reason: kernel mode process attempts to execute an illegal or unknown processor instruction.
Workaround: Make sure there is enough space, especially when performing a new installation.
If the stop error message indicates a particular driver, disable it. If you are unable to start your computer, try booting in Safe Mode to remove or disable the driver.
If you have a non-Microsoft supported video driver, try to switch to the standard VGA driver or the appropriate driver provided by Windows.
Disable all newly installed drivers.
Make sure you have the latest version of the system BIOS. The hardware manufacturer can help determine if you have the latest version and can also help you get him.
Disable BIOS memory options, such as cache, shadow.

3, stop error number: 0x00000023 or 0x00000024
Description text: FAT-FILE-SYSTEM or MTFS-FILE-SYSTEM
Normal reason: the problem occurs in Ntfs.sys (allows the system to read and write NTFS Inside the driver's driver file).
Solution: Run the system diagnostic software provided by the computer manufacturer, especially the hardware diagnostic software.
Disable or uninstall all anti-virus software, disk defragmenter or backup program.
Check the hard drive for damage by running the Chkdsk /f command at the command prompt and restart the computer.

4, stop number: 0x0000002E
Description text: DATA-BUS-ERROR
The usual reason: system memory parity error, usually caused by hardware problems.
Solution: Remove all newly installed hardware (RAM. Adapters, hard drives, modems, etc.).
Run system diagnostic software provided by computer manufacturers, especially hardware diagnostic software.
Make sure that the hardware device driver and system BIOS are the latest version.
Use system diagnostics provided by your hardware vendor to run a memory check to find faulty or mismatched memory.
Disable BIOS memory options, such as cache or shadow.
When it appears as a system list after startup, press F8. On the Windows Advanced Options menu screen, select "Start VGA Mode and press Enter. If this does not solve the problem, you may need to replace the list of different video adapters. For a list of supported video adapters, see the Hardware Compatibility List.

5, stop number: 0x0000003F
Description text: NO-MOR-SYSTEM-PTES
The usual reason: the driver is not cleaned properly.
Solution: disable or uninstall all Anti-virus software, disk fragmentation program or backup program.

6, stop error number: 0x00000058
Description text: FTDISK-INTERN-ERROR
The usual reason: a master in the fault-tolerant set The drive has failed.
Workaround: Boot the computer using the Windows installation disk and boot from the mirror (2nd) system drive. Instructions on how to edit the Boot.ini file to point to the image system driver are available on the MIcrosoft Support Services Web. Site search "Edit ARC path".

7, stop error number: 0x0000007B
Description text: INACCESSI-BLE-BOOT-DEVICE
Normal reason: Initialize I/O system The system (usually refers to the boot device or file system) fails.
Workaround: Boot sector viruses usually cause this stop error. Use the latest version of anti-virus software to check if there is a virus on the computer. If found The virus must be executed without removing it from the computer. Please refer to the anti-virus software documentation for instructions on how to perform these steps.
Remove all newly installed hardware (RAM, adapter, modem, etc.). BR>Check the MIcrosoft hardware compatibility list to ensure that all hardware and drivers are compatible with Windows.
If you are using a suitable SCSI adapter, you can get the latest WINDOWS driver from the hardware vendor and disable the synchronization negotiation of the SCSI device. Check if the SCSI chain is terminated and check the SCSI ID of these devices. If you are not sure how to perform these steps, refer to the documentation of the hardware device.
If you are using an IDE device, define the IDE port on the board as The only primary port. Check the master/slave/unique settings of the IDE device. Remove all IDE devices except the hard disk. If you want to do this, please refer to the hardware documentation.
If the computer has been formatted using the NTFS file system, restart the computer and run the Chkdsk /f/r command on the system partition. If it is not possible due to an error To start the system, use the command console and run the Chkdsk /r command.
Run the Chkdsk /f command to determine if the file system is corrupt. If Windows can't run the Chkdsk command, move the drive to another computer running Windows, and then run the Chkdsk command on that drive from that computer.

8, stop error number: 0x0000007F
Description text: UNEXPECTED-KERNEL-MODE-TRAP
The usual reason: usually caused by hardware or software problems, but generally caused by hardware failure .
Workaround: Check the Microsoft Hardware Compatibility List to make sure all hardware and drivers are compatible with Windows. This problem can occur if the computer motherboard is not compatible.
Remove the newly installed hardware.
Run all system diagnostic software provided by the computer manufacturer, especially memory check.
Disable BIOS memory options, such as cache or shadow.

9, stop error number: 0x00000050
Description text: PAGE-FAULT-IN-NONPAGED-AREA
The usual reason: memory error (data can not be used to exchange paging files to disk).
Solution: Remove all newly installed hardware.
Run all system diagnostic software provided by the computer manufacturer. Especially the memory check.
Check that all new hardware or software is properly installed. If this is a new installation, contact your hardware or software manufacturer for any Windows updates or drivers you may need.
Disable or uninstall all anti-virus programs.
Disable BIOS memory options, such as cache or shadow.

10, stop error number: 0x00000077
Description text: KERNEL-STEL-STACK-INPAGE-ERROR
The usual reason: the page required for kernel data cannot be read from the paging file to the memory in.
Workaround: Use the latest version of anti-virus software to check for viruses on your computer. If you find a virus, perform the necessary steps to get rid of it from your computer. Please refer to all system diagnostic software provided by the manufacturer, especially the memory check.
Disable BIOS memory options, such as cache, shadow.

11, stop error number: 0x00000079
Description text: MISTACHED-HAL
The usual reason: the hardware abstraction layer does not match the kernel or machine type (usually occurs in single-processor and multi-processor Profiles are mixed in the same system).
Workaround: To resolve this error, use the command console to replace the wrong system file on your computer.
The kernel file of the single processor system is Ntoskml.exe, and the kernel file of the multiprocessor system is Ntkrnlmp.exe, however, these files should correspond to the files on the installation media; after installing Windows2000 and regardless of the use Which original file is renamed to the Ntoskrnl.exe file. The HAL file also uses the name Hal.dll after installation but is installed on the media, but there are several possible HAL files on the installation media.

12, stop error number: 0x0000007A
Description text: KERNEL-DATA-INPAGE-ERROR
The usual reason: the page required for kernel data cannot be read from the paging file into memory. (usually due to a failure on a paging file, a virus, a disk controller error, or caused by a failed RAM).
Workaround: Use the latest version of anti-virus software to check for viruses on your computer. If you find a virus. Then perform the necessary steps to remove him from the computer, see the Illness Software documentation for instructions on how to perform these steps.
If the computer has been formatted using the NTFS file system. You can restart your computer and then run the Chkdsk /f/r command on that system partition. If the command cannot be started due to an error, use the command console and run the Chkdsk /r command.
Run all system diagnostic software provided by the computer manufacturer, especially memory check.

13, stop error number: 0xC000021A
Description text: STATUS-SYSTEM-PROCESS-TERMINATED
Common reason: user mode subsystem, such as WinLogon or Client Server Runtime Subsystem (CSRSS) It has been damaged, so security cannot be guaranteed.
Solution: Remove all newly installed hardware.
If you are unable to log in, restart your computer. Press F8 when a list of available systems is available. On the Windows 2000 Advanced Options menu screen, choose: "Last Known Good Configuration." Then press Enter.
Run the recovery board and allow the system to fix any detected errors.

14, stop error number: 0xC0000221
Description text: STATUS-IMAGE-CHECKISU7M-MISMATCH
The usual reason: the driver or system DLL has been damaged.
Workaround: Run the failback console and allow the system to fix any detected errors.
If an error occurs immediately after the RAM is added to the computer, it may be that the paging file is corrupted, or the new RAM is faulty or incompatible. Delete Pagefile.sys and return the system to the original RAM configuration.
Run all system diagnostic software provided by the computer manufacturer, especially memory check.