Invalid Windows operation code

Invalid Windows operation code
The comrades here must have used windows. I must have experienced "illegal operations. Generally, "invalid operations" have two options: "disabled" and "details ". However, most people cannot understand the content in "details", so they have to close it. Now, you don't have to worry about it. Let me explain the specific meaning of each detailed information about illegal operations:
1. Stop error no.: 0x0000000a
English version: IRQL-NOT-LESS-OR-EQUAL
Common cause: the driver uses an incorrect memory address.
Solution: If login fails, restart the computer. when the available system list is displayed, press F8. on the Windows Advanced Options menu screen, select "Last correct configuration" and press Enter.
Check whether all new hardware or software is correctly installed. If this is a completely new 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 computer manufacturers, especially Memory checks.
Disable or uninstall recently installed hardware (RAM, adapter, hard disk, modem, etc.), drivers or software.
Make sure that the driver and bios of the hardware device are in the latest version.
Make sure that the manufacturer can help you with the latest version or get the hardware.
Disable BIOS memory options, such as cache or shadow.
2. Stop error no.: 0x0000001e
English version: KMODE-EXPTION-NOT-HANDLED
Common Cause: kernel-mode processes attempt to execute an illegal or unknown processor command.
Solution: Make sure you have enough space, especially when performing a new installation.
If the STOP error message indicates a specific driver, disable it. If the computer cannot be started, try to start it in safe mode to delete or disable the driver.
If there are non-Microsoft-supported video drivers, try to switch to the standard VGA driver or the appropriate driver provided by windows.
Disable all newly installed drivers.
Make sure that you have the latest version of the system bios. The hardware manufacturer can help you determine whether you have the latest version or get it.
BIOS memory options, such as cache and shadow.
3. Stop error no.: 0x00000023 or 0x00000024
Description: fat-file-system or MTFS-FILE-SYSTEM
Common cause: the problem occurs in NTFS. sys (which allows the system to read and write the driver file of the NTFS drive.
Solution: Run system diagnostic software provided by computer manufacturers, especially hardware diagnostic software.
Disable or Uninstall all anti-virus software, disk fragment programs, or backup programs.
Run the chkdsk/F command at the command prompt to check whether the hard drive is damaged and restart the computer.
4. Stop ID: 0x0000002e
Description text ATA-BUS-ERROR
Common cause: the system memory parity error is usually caused by hardware problems.
Solution: Remove all recently installed hardware (RAM. adapter, hard disk, modem, etc ).
Run system diagnostic software provided by computer manufacturers, especially hardware diagnostic software.
Make sure that the driver and bios of the hardware device are the latest version.
Use the system diagnostics provided by the hardware supplier to run the memory check to find the faulty or mismatched memory.
Disable BIOS memory options, such as cache or shadow.
When the system list is available after startup, press f8. on the Windows Advanced Options menu screen, select "enable VGA mode :. then press Enter. if the problem persists, you may need to change the list of different video adapters. For the list of supported video adapters, see hardware compatibility list.
5. Stop ID: 0x0000003f
English version: NO-MOR-SYSTEM-PTES
The common cause is that the driver is cleaned up correctly.
Solution: Disable or Uninstall all anti-virus software, disk fragment processing programs, or backup programs.
6: STOP error no.: 0x00000058
English version: FTDISK-INTERN-ERROR
Common Cause: a primary drive in the fault tolerance set fails.
Solution: Use the Windows installation disk to start the computer and boot from the image (2nd) System Drive. for how to edit boot. the INI file directs to the image system drive. You can search for "Edit arc path" on the Microsoft Support Web site ".
7. Stop error no.: 0x0000007b
English version: INACCESSI-BLE-BOOT-DEVICE
Common Cause: initialization of the I/O system (usually the boot device or file system) fails.
Solution: The Boot Sector virus usually causes this stop error. is to use the latest version of anti-virus software, check whether there is a virus on the computer. if a virus is found, you must remove it from the computer. See the anti-virus software documentation to learn how to perform these steps.
Remove all recently installed hardware (RAM, adapter, modem, and so on ).
Check the Microsoft hardware compatibility list to ensure that all hardware and drivers are compatible with windows.
If the SCSI adapter is used, you can obtain the latest Windows Driver from the hardware supplier, disable synchronization negotiation for SCSI devices, check whether the SCSI chain is terminated, and check the scsi id of these devices, if you cannot determine how to perform these steps, refer to the hardware device documentation.
If you are using an IDE device, define the IDE port on the Board as a unique primary port. check the primary/secondary/unique settings of the IDE device. remove all ide devices except hard disks. if you cannot confirm how to do this, 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 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 check whether the file system is damaged. if Windows cannot run the chkdsk command, move the drive to another computer running Windows, and then run the chkdsk command on the drive.
8. Stop error no.: 0x0000007f
Description: unexpected-kernel-mode-trap
Common Cause: it is usually caused by hardware or software problems, but generally caused by hardware faults.
Solution: Check the Microsoft hardware compatibility list to ensure that all hardware and drivers are compatible with windows. This problem occurs if the computer motherboard is not compatible.
Unmount the recently installed hardware.
Run all system diagnostic software provided by computer manufacturers, especially Memory checks.
Disable BIOS memory options, such as cache or shadow.
9. Stop error no.: 0x00000050
English version: PAGE-FAULT-IN-NONPAGED-AREA
Common Cause: memory error (data cannot be switched to disk using paging files ).
Solution: Uninstall all recently installed hardware.
Run all system diagnostic software provided by computer manufacturers, especially Memory checks.
Check whether all new hardware or software is correctly installed. If this is a completely new installation, contact the hardware or software manufacturer for any windows updates or drivers that may be required.
Disable or Uninstall all anti-virus programs.
Disable BIOS memory options, such as cache or shadow.
10. Stop error no.: 0x00000077
English version: KERNEL-STEL-STACK-INPAGE-ERROR
Common cause: the page required for kernel data cannot be read to memory from the paging file.
Solution: use the latest version of anti-virus software to check whether there is a virus on the computer. If the virus is found, perform the necessary steps to remove it from the computer. See all system diagnostic software provided by the manufacturer, especially Memory checks.
Disable BIOS memory options, such as cache and shadow.
11. Stop error no.: 0x00000079
English version: MISMATCHED-HAL
The common cause is that the hardware abstraction layer does not match the kernel or machine type (usually when the single processor and multi-processor configuration files are mixed in the same system ).
Solution: To solve this error, use the command console to replace the wrong system file on the computer.
Hosts file. The Hal file also uses the name Hal. dll after installation, but is installed in the media, but there are several possible Hal files on the installation media.
12. Stop error no.: 0x0000007a
English version: KERNEL-DATA-INPAGE-ERROR
Common cause: the page required for kernel data cannot be read to memory from the paging file. (Usually caused by faults, viruses, disk controller errors, or faulty RAM) on the paging file ).
Solution: use the latest version of anti-virus software to check whether a virus exists on the computer. If the virus is found. Then perform the necessary steps to remove it from the computer. See the diseased software documentation to learn how to perform these steps.
If the computer is already formatted using the NTFS file system. Restart the computer and run the chkdsk/F/R command on the system partition. If the command cannot be started due to an error, use the console and run the chkdsk/R command.
Run all the systems provided by computer manufacturers on low-end software, especially Memory checks.
13. Stop error no.: 0xc000021a
Description: Status-system-process-terminated
Common cause: the user mode subsystem, such as Winlogon or the Client Server Runtime subsystem (CSRSS) has been damaged, so security cannot be guaranteed.
Solution: Uninstall all recently installed hardware.
If login fails, restart the computer. Press f8. On the Windows2000 advanced options menu screen, select "Last correct configuration ". Press enter.
Run the fault recovery platform and allow the system to repair any detected errors.
14. Stop error no.: 0xc0000221
English version: STATUS-IMAGE-CHECKISU7M-MISMATCH
Common cause: the driver or system DLL has been damaged.
Solution: run the fault recovery 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. Delete pagefile. sys and return the system to the original ram configuration.
Run all system diagnostic software provided by computer manufacturers, especially Memory checks.