Win XP illegal operation detailed

Win XP illegal operation detailed

1. Stop error number: 0x0000000A

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

Common cause: The driver used an incorrect memory address.

Solution: If you are unable to log in, restart your computer. When the list of available operating systems appears, press F8. In Windows Advanced Options On the menu screen, select "Last Known Good Configuration" and press Enter.

Check that all new hardware or software is properly installed. If this is a new installation, please contact the hardware or Contact the software manufacturer for any Windows updates or drivers that may be required.

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

Disable or unload 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 Can help you have the most The version also helps you get these hardware.

Disable BIOS memory options, such as cache or shadow.

2. Stop error number: 0x0000001E

Description text: KMODE- EXPTION-NOT-HANDLED

Common Cause: Kernel-mode processes attempt to execute an illegal or unknown processor instruction.

Workaround: Make sure there is enough space, especially when executing a new one When installing.

If the stop error message indicates a specific driver, disable it. If you are unable to 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 the appropriate driver provided by Windows.

Disable all newly installed drivers.

Make sure 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 it.

BIOS memory options, such as cache, shadow.

3. Stop Error number: 0x00 000023 or 0x00000024

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

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

Solution: Run system diagnostic software provided by the computer manufacturer, especially 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, then restart the computer.

4. Stop number: 0x0000002E

Description text ATA -BUS-ERROR

The usual reason: system memory parity error, usually caused by hardware problems.

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

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

Make sure that the hardware device driver and system BIOS are the latest version.

Use a hardware vendor to mention System diagnostics, run a memory check to find faulty or mismatched memory.

Disable BIOS memory options, such as cache or shadow.

When a list of available operating systems appears after booting, 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 Hardware Compatibility list.

5. Stop number: 0x0000003F

Description text: NO-MOR-SYSTEM-PTES

Common reason: Clean up the driver correctly every time. Br>

Workaround: 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 a 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 refer to Instructions for mirror system drivers 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: Initializing an I/O system (usually referring to a boot device or file system) fails.

Solution: Boot sector viruses usually cause this stop error. The latest version of anti-virus software, 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 to understand 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 a suitable SCSI adapter, you 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. To perform these steps, 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 all IDE devices except the hard disk. If you are not sure how to do this, please refer to the hardware documentation.

If your computer has been formatted with the NTFS file system, you can restart your computer and then on the system. Run the Chkdsk /f/r command on the 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. Windows cannot run the 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

Text: UNEXPECTED-KERNEL-MODE-TRAP

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

Solution: Check Micros The oft hardware 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 AGE-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, 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. Into the 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 Cause: Unable to extract kernel page 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.

Running all the systems provided by the computer manufacturer is very useful in software, especially memory checking.

13. Stop Error Number: 0xC000021A

Description Text: STATUS-SYSTEM-PROCESS-TERMINATED

Common Cause: 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 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