WinXP illegal operation can not be turned on failure analysis

Detailed Operation of WinXP Illegal Operation

1. Stop Error Number: 0x0000000A

Description Text: IRQL-NOT-LESS-OR-EQUAL

Common Cause: Driver Incorrect memory address is used.

Solution: If you are unable to log in, restart your computer. When the list of available operating systems appears, press F8. On the Windows Advanced Options menu screen, select " Last time the correct configuration ", then press Enter.

Check that all new hardware or software is properly installed. If this is a new installation, please contact the manufacturer of the hardware or software to get 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 , adapters, hard drives, modems, etc.), drivers or software.

Make sure the hardware device drivers and system BIOS are the latest versions.

Make sure the manufacturer can help you have the latest The version also helps you get these hardware.

Disable BIOS memory options, such as cach e or shadow.

2. Stop error number: 0x0000001E

Description text: KMODE-EXPTION-NOT-HANDLED

Normal reason: Kernel mode process tried to execute an illegal Or unknown processor instructions.

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

If the stop error message indicates a specific driver , then disable him. 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 the standard VGA driver or Appropriate drivers 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.

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 to NTFS drives) Inside the 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, defragmentation Program or backup program.

Check the hard drive for damage by running the Chkdsk /f command at the command prompt, then restart the computer.

4. Stop number: 0x0000002E

Description text: DATA-BUS-ERROR

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

Solution: Remove all newly installed hardware (RAM .Adapters. Hard disks, modems, etc.).

Run system diagnostic software provided by the computer manufacturer, especially hardware diagnostic software.

Make sure the hardware device drivers and system BIOS are up to date. Version.

Use the 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 the list of available operating systems appears after startup, press F8. On the Windows Advanced Options menu screen Select "Start VGA Mode:. Then press Enter. If this does not solve the problem, you may need to replace the different video adapter list. For a list of supported video adapters, see the Hardware Compatibility List.

5. Stop number: 0x0000003F

Description text: NO-MOR-SYSTEM-PTES

Normal reason: Clean the driver correctly every time.

Solution: Disable or uninstall all anti-virus software, disk fragmentation or backup programs.

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 to Instructions for pointing to the image system driver can be found on the MIcrosoft Support Services Web site "Edit ARC path".

7. Stop error number: 0x0000007B

Description text:INACCESSI-BLE-BOOT -DEVICE

Common Cause: Failure to initialize an I/O system (usually a boot device or file system).

Deadline: 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 you find a virus, you must perform the necessary not to remove him from the computer. See the anti-virus software documentation for instructions on how to perform these steps.

Remove all newly installed hardware (RAM, adapters, modems, etc.).

Check the MIcrosoft Hardware Compatibility List to ensure 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, disable the synchronization negotiation of the SCSI device, and check if the SCSI chain is terminated. 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 are not sure how to do this, please refer to the hardware documentation.

If the computer is already using N Format the TFS file system, restart the computer, and then run the Chkdsk /f/r command on the system partition. 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 can't run the Chkdsk command, move the drive to another computer running Windows, and then run the Chkdsk command on the drive from this 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 .

Solution: Check the Microsoft Hardware Compatibility List to ensure that all hardware and drivers are compatible with Windows. This problem can occur if the computer motherboard is incompatible.

Run all system diagnostic software provided by the computer manufacturer, especially memory check, by newly installed hardware.

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 your computer manufacturer. Especially memory check.

Check that all new hardware or software is properly installed, if This is a new 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 shadow.

10. Stop error number: 0x00000077

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

Normal reason: Unable to The paging file reads the pages required for kernel data 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).

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

The kernel file for a single processor system is Ntoskml.exe, and the kernel file for a multiprocessor system is Ntkrnlmp.exe, but these files correspond to the files on the installation media; after installing Windows 2000 and 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: 0x0000007A

Description text: KERNEL-DATA-INPAGE-ERROR

Common reason: unable to get the required page of kernel data from paging file 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 Cause: User mode subsystems such as Winlogon or Client Server Runtime Subsystem (CSRSS) have been corrupted, so security is no longer guaranteed.

Solution: Remove all newly installed hardware.

If you are unable to log in, restart your computer. Press F8 when the list of available operating systems appears. On the Windows 2000 Advanced Options menu screen, choose: “ Last Known Good Configuration”. Then press the car.

Run the Recovery Console and allow the system to fix any detected errors.

14. Stop Error Number: 0xC0000221

Description Text: STATUS-IMAGE-CHECKISU7M-MISMATCH

Common Cause: The driver or system DLL has been corrupted.

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, the paging file may be corrupted, or the new RAM may be 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