Reasons for illegal operation of the system and solutions

        Everyone has used Windows, and they must have experienced "illegal operations." The general "illegal operation" has two options: "close" and "details". However, most of the contents of the "Details" do not understand, and the grass has been closed. Don't be afraid now, let me explain the specific meaning of each detail of the illegal operation.

1. Stop error code: 0x0000000A

caption: IRQL-NOT-LESS-OR-EQUAL

usual reasons: the driver uses an incorrect memory address

Solution: If you can't log in, restart your computer. When the available system list appears, press F8. On the Windows Advanced Options menu screen, select "Last Known Good Configuration", then Press Enter.

Check that all new hardware or software is properly installed. If this is a new installation, contact the manufacturer of the hardware or software for any Windows updates or drivers you may need.

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 drivers and system BiOS are the latest versions.

Make sure the manufacturer can help you with the latest version and also help you get these hardware

Forbidden Use BiOS memory options, such as cache or shadow.

2. Stop error number: 0x0000001E

Description text: KMODE-EXPTION-NOT-HANDLED

Common reason: kernel The pattern process attempts to execute an illegal or unknown processor instruction.

Solution: Make sure there is enough space, especially when performing a new installation.

If the stop error message indicates For a specific driver, disable it. If you can't start the 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 Standard VGA driver or appropriate driver provided by Windows.

Disable all newly installed drivers.

Make sure you have the latest version of System BiOS. Hardware manufacturers can help determine if you have The latest version can also help you get him.

BiOS memory options, such as cache, shadow.

3. Stop error number: 0x00000023 or 0x00000024

Description text: FAT -FILE-SYSTEM or MTFS-FILE-SYSTEM

Normal Cause: The problem occurs in Ntfs.sys (allows the system to read and write the driver files of the NTFS drive).

Solution: Run by System diagnostic software provided by computer manufacturers, especially hardware diagnostic software..

Disable or uninstall all anti-virus software, disk defragmenter or backup program.

By at the command prompt Run the Chkdsk /f command to check whether the hard drive is damaged, and then restart the computer

4. Stop number: 0x0000002E

Description text ATA-BUS-ERROR

Common reason : System memory parity error, usually caused by hardware problems.

Solution: Remove all newly installed hardware (RAM.Adapter. Hard disk. Modem, etc.).

Run by 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 the system diagnostics provided by the hardware vendor to run Memory check To find faulty or mismatched memory.

Disable BiOS memory options, such as cache or shadow.

When it appears as a list of systems after booting, press F8. In the Windows Advanced Options menu On the screen, select "Start VGA Mode:. Then 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, please refer to the Hardware Compatibility List.

5. stop number: 0x0000003F

caption: NO-MOR-SYSTEM-PTES

usual reasons: the right of each yo clean up drivers

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 cause: A host drive in the fault-tolerant set has failed.

Solution: Boot the computer using the Windows installation disk and boot from the mirror (2nd) system drive. How to edit the Boot.ini file Drive to the mirror system For guidance, you can search for "Edit ARC path" on the MIcrosoft Support Services Web site.

7. Stop error number: 0x0000007B

Description text: INAccessI-BLE-BOOT-DEVICE
< BR> Common Cause: Initializing an I/O system (usually referring to a boot device or file system) fails.

Solution: Boot sector viruses usually cause this stop error. It is the latest with anti-virus software. Version, check if there is a virus on the computer. If you find the virus, you must perform the necessary not to remove him from the computer. Please refer to the anti-virus software documentation for how to perform these steps.

Remove all Newly installed hardware (RAM, adapter, modem, etc.).

Check the MIcrosoft hardware compatibility list to ensure that all hardware and drivers are compatible with Windows.

If you are using SCSI Adapter, which can obtain the latest Windows driver from the hardware vendor, disable the SCSI device synchronization negotiation, check whether the SCSI chain is terminated, and check the SCSI ID of these devices. If you are not sure how to perform these For more information, refer to the documentation for your 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 it. All IDE devices other than the hard disk. If you are not sure how to do this, please refer to the hardware documentation.

If the computer has been formatted with the NTFS file system, you can restart the computer and run it on the system partition. Chkdsk /f/r command. If the system cannot be started due to an error, 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 does not run Chkdsk command, move the drive to another computer running Windows, and then run the Chkdsk command from the computer on this computer.

8. Stop error number: 0x0000007F
< BR> Description text: UNEXPECTED-KERNEL-MODE-TRAP

The usual reason: usually caused by hardware or software problems, but generally caused by hardware failure..

Solution: Check Microsoft A compatibility list to ensure that all hardware and drivers are compatible with Windows. This problem can occur if the computer motherboard is not compatible.

Uninstall 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

Common reason: memory error (data cannot be exchanged to disk using paging file).

Solution: Remove all Newly installed hardware.

Run all system diagnostic software provided by the computer manufacturer. Especially memory check.

Check if all new hardware or software is installed correctly, if this is a new For installation, please contact the 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 sh Adow.

10. Stop error number: 0x0000007

Description text: KERNEL-STEL-STACK-INPAGE-ERROR

Common reason: unable to extract kernel data from paging file The required page is read into memory.

Solution: 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: MISMATCHED-HAL

Common reason : The hardware abstraction layer does not match the kernel or machine type (usually when single-processor and multi-processor configuration files are mixed on the same system).

Solution: To resolve this error, use the command console to replace the wrong system file on your computer.

kernel file system is Ntoskml.exe single processor, the multi-processor system kernel file is Ntkrnlmp.exe, but these files to install the files on the medium corresponding to a; in installing and Windows2000 No matter which original file is used, it will be renamed to 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: KERNEL-DATA-INPAGE-ERROR

usual reasons:: Text 0x0000007A

instructions from the paging file will not be required to kernel data page Read into memory. (usually due to a failure on a paging file, a virus, a disk controller error, or caused by a failed RAM).

Solution: 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 the systems provided by the computer manufacturer in the very end software, especially the memory check.

13. Stop error number: 0xC000021A

Description text: STATUS-SYSTEM-PROCESS-TERMINATED

Common reason: user mode subsystem, such as Winlogon or client server running The Time Subsystem (CSRSS) has been corrupted, 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 the car.

Run the recovery desk 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.

Solution: Run the faulty console and allow the system to fix any detected errors.

If an error occurs immediately after the RAM is added to the computer,