Windows Illegal Operation detailed

1. Stop error Number: 0x0000000A

Explanatory text: irql-not-less-or-equal

The usual reason: The driver uses an incorrect memory address.

WORKAROUND: If you cannot log in, restart your computer. Press F8 when a list of available make systems appears. On the Windows Advanced Options menu screen, select Last Known Good Configuration, and then press ENTER.

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

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

Disable or remove newly installed hardware (RAM, adapters, hard drives, modems, and so on), drivers, or software.

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

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

Disable BIOS memory options, such as cache or shadow.

2. Stop error Number: 0x0000001E

Explanatory text: kmode-exption-not-handled

The usual reason: the kernel-mode process is attempting to execute an illegal or unknown processor directive.

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

If the Stop error message indicates a specific driver, disable him. If you cannot start your computer. Try to start in safe mode to remove or disable the driver.

If you have a video driver that is not supported by Microsoft, try switching to the standard VGA driver or the appropriate driver provided by Windows.

Disables all newly installed drivers.

Make sure that you have the latest version of the system BIOS. The hardware manufacturer can help determine whether you have the latest version or help you get to him.

BIOS memory options, such as Cache,shadow.

3. Stop error Number: 0x00000023 or 0x00000024

Explanatory text: Fat-file-system or Mtfs-file-system

Usually the reason: The problem appears in the Ntfs.sys (allowing the system to read and write to the driver file for the NTFS drive).

Workaround: Run the system diagnostics software provided by the computer manufacturer, especially the hardware diagnostics 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 then restart the computer

4. Stop code: 0X0000002E

Description text Ata-bus-error

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

Workaround: Remove all newly installed hardware (RAM. Adapters, hard drives, modems, etc.).

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

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

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 a list of available as 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 a different list of video adapters, for a list of supported video adapters, see the Hardware Compatibility List.

5. Stop code: 0x0000003f

Explanatory text: no-mor-system-ptes

The usual reason: every yo cleans the driver properly.

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

6: Stop error Number: 0x00000058

Explanatory text: Ftdisk-intern-error

Common Cause: A primary drive in a fault-tolerant set fails.

Workaround: Boot the computer with the Windows Setup disk and boot from the Mirror (2nd) system drive. For instructions on how to edit the Boot.ini file to point to the mirror system drive, search for "Edit ARC path" at the Microsoft Support Services Web site.

7. Stop error Number: 0x0000007B

Explanatory text: Inaccessi-ble-boot-device

Usually the reason: initialization of the I/O system (usually referred to as a boot device or file system) failed.

Workaround: Boot sector viruses often cause this stop error. Use the latest version of the anti-virus software to check if there is a virus on your computer. If a virus is found, you must do the necessary not to remove him from the computer, see antivirus software documentation Learn how to perform these steps.

Remove all newly installed hardware (RAM, adapters, modems, and so on).

Check the Microsoft Hardware Compatibility List to ensure that all hardware and drivers are compatible with Windows.

If you use an appropriate SCSI adapter, you can remove the latest Windows drivers from your hardware vendor, disable synchronous negotiation of SCSI devices, check that the SCSI chain is terminated, and check the SCSI IDs of those devices, and if you cannot determine how 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 a unique primary port. Check the IDE device's master/S/unique settings. Remove all IDE devices except the hard drive. If you cannot confirm how to do this, refer to the hardware documentation.

If your computer is formatted with the NTFS file system, you can restart your computer and then run the CHKDSK/F/R command on that system partition. If the system cannot be started because of an error, use the command console and run the CHKDSK/R command.

Run the chkdsk/f command to determine if the file system is corrupted. If Windows cannot 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

Explanatory text: Unexpected-kernel-mode-trap

Common causes: Usually due to hardware or software problems, but are generally caused by hardware failures.

Workaround: Check the Microsoft Hardware Compatibility List to ensure that all hardware and drivers are compatible with Windows. This problem occurs if the computer board is incompatible.

Remove the newly installed hardware.

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

Disable BIOS memory options, such as cache or shadow.

9. Stop error Number: 0x00000050

Explanatory text: Page-fault-in-nonpaged-area

Common Cause: Memory error (data cannot be exchanged with paging file to disk).

Workaround: Remove all newly installed hardware.

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

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

Disable or uninstall all anti-virus programs.

Disable BIOS memory options, such as cache or shadow.

10. Stop error Number: 0x0000007

Explanatory text: Kernel-stel-stack-inpage-error

The usual reason: unable to read the required pages of kernel data into memory from the paging file.

WORKAROUND: Use the latest version of the anti-virus software to check for viruses on your computer. If a virus is found, perform the necessary steps to clear it off the computer. Please refer to all system diagnostics provided by the manufacturer, especially memory checks.

Disable BIOS memory options, such as Cache,shadow.

11. Stop error Number: 0x00000079

Explanatory text: Mismatched-hal

The usual reason: the hardware abstraction layer does not match the kernel or machine type (typically occurs when a single processor and a multiprocessor configuration file are mixed in the same system).

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

The kernel files for a single-processor system are Ntoskml.exe, and the kernel files for multiprocessor systems are Ntkrnlmp.exe, but these files should correspond to the files on the installation media; After installing Windows2000 and, regardless of which original file is used, will be renamed to the Ntoskrnl.exe file. The HAL file also uses the name Hal.dll after installation, but there are several possible HAL files on the installation media, but the media is installed.

12. Stop error Number: 0x0000007a

Explanatory text: Kernel-data-inpage-error

The usual reason: unable to read the required pages of kernel data into memory from the paging file. (usually due to a failure on the paging file, a virus, a disk controller error, or a faulty RAM).

WORKAROUND: Use the latest version of the anti-virus software to check for viruses on your computer. If a virus is found. Then perform the necessary steps to remove him from the computer, see the degree software documentation to learn how to perform these steps.

If the computer is formatted with the NTFS file system. You can restart the computer and then run the CHKDSK/F/R command on the system partition. If the command cannot be started because of an error, use the command console and run the CHKDSK/R command.

Run all systems provided by the computer manufacturer in very end-to-end software, especially memory checking.

13. Stop error Number: 0xc000021a

Explanatory text: status-system-process-terminated

The usual reason: the user-mode subsystem, such as the Winlogon or client Server Runtime subsystem (CSRSS), is corrupted, so security is no longer guaranteed.

Workaround: Remove any newly installed hardware.

If you are unable to log in, restart your computer. Press F8 when a list of available make systems appears. On the Windows2000 Advanced Options Menu screen, select: Last Known Good configuration. Then press passing.

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

14. Stop error Number: 0xc0000221

Explanatory text: Status-image-checkisu7m-mismatch

The usual reason: The driver or system DLL has been corrupted.

Workaround: Run the fault 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 is faulty or incompatible. Remove the Pagefile.sys and return the system to its original RAM configuration.

CR "(file name can be changed), as follows:

L 100 2 0 1

N C:bootsect. Dos

R BX

0

R CX

200

W

Q

2. Copy the above made documents to the startup disk;

3. Use the boot disk to start the computer to the DOS mode;

4. Modify the Bootsect. DOS "File properties, use the following command:

ATTRIB C:bootsect. Dos-s-h-r

5. At the command prompt, enter: DEBUG