STOP: 0X0000008E

Windows 2 K/XP has a lot of blue screen information and cannot be fully explained in an article, however, the causes of these problems are often concentrated on incompatible hardware and drivers, problematic software, and viruses. Therefore, we first provide you with some conventional solutions, in the case of a blue screen error, you should first exclude these solutions.

1. Restart

Sometimes only a program or driver makes a mistake at the moment. After the restart, they will change themselves. (Note: see 7. query the shutdown code at this time)

2. New hardware

First, check whether the new hardware is firmly inserted. The problem that is ignored by many people may lead to many inexplicable faults. if there is no problem, unplug it, try another slot, and install the latest driver. at the same time, check whether the hardware is compatible with the operating system against the hardware compatibility category on the Microsoft website. if your hardware is not in the table, you can query the website of the hardware manufacturer or call their phone number.

Windows XP hardware compatibility list

2 k hardware compatibility for Windows

3. New drivers and services

If you have just installed a new hardware driver or a software, and it has added the corresponding project to the System Service (for example: anti-Virus Software, CPU cooling software, firewall software, etc.), blue screen failure occurs during restart or use. please uninstall or disable them in safe mode.

4. Check for viruses

For example, viruses such as shock waves and ripple waves may sometimes cause Windows blue screens to crash, so virus detection and removal are essential. At the same time, some Trojan spyware may also cause blue screens, so it is best to use related tools for scanning and inspection.

5. Check BIOS and hardware compatibility

For newly installed computers that often encounter blue screen problems, you should check and upgrade the BIOS to the latest version, and disable memory related items, such as cache and ing. check your hardware against Microsoft's hardware compatibility list. in addition, if the motherboard BIOS does not support a large-capacity hard disk, it will also lead to a blue screen and need to be upgraded.

6. Run "sfc/scannow" to check whether the system file is replaced, and then use the system installation disk to restore it.

TIPS:

BIOS cache and ing items

Video BIOS Shadowing (Video BIOS ing)

Shadowing address ranges (ing address column)

System BIOS Cacheable (System BIOS buffer)

Video BIOS Cacheable (Video BIOS buffer)

Video RAM Cacheable (Video memory buffer)

7. Check System Logs

Enter EventVwr In the start --> menu. msc. When you press enter, the "Event Viewer" appears. Check "system log" and "Application log" for "error" items.

8. query the shutdown code

The blue screen in the dense E text down, and then to other computers to access the Internet, enter the Microsoft Help and Support website http://support.microsoft.com ?, In "Search (Knowledge Base)" in the upper-left corner, enter the stop code. If the search result does not have any suitable information, select "English knowledge base" and search again. in general, we will find useful solutions here. in addition, the blue screen stop code or subsequent instructions are used as keywords in search engines such as baidu and Google.

9. The last correct configuration

Generally, after the hardware driver or the hardware is added and the driver is installed, the "Last correct configuration" provided by Windows 2 K/XP is a shortcut for solving the blue screen. restart the system. When the boot menu appears, press F8 to display the advanced boot option menu, and then select "Last correct configuration ".

10. Install the latest system patch and Service Pack

Some blue screens are caused by defects in Windows, which can be solved by installing the latest system patches and Service packs. it is often time-consuming to use windows to display blue screens, and often reinstall the system due to unclear sources of errors. Some windows Dead-end passwords are collected below for your reference.

1. 0x0000000A: IRQL_NOT_LESS_OR_EQUAL

◆ Error Analysis: mainly caused by problematic drivers, defective or incompatible hardware and software. from a technical point of view. indicates that there is a level of process request (IRQL) in kernel mode to access the memory address that is not authorized to access.

◇ Solution: Use solution 2, 3, 5, 8, and 9 in the preceding solution to try to eliminate this problem.

2. 0x00000012: TRAP_CAUSE_UNKNOWN

◆ Error Analysis: If this error message is returned, it is unfortunate that the analysis result of KeBudCheck is the cause of the error.

Unknown.

◇ Solution: Since Microsoft is not able to help, you have to rely on yourself. Please think carefully about when this error occurred. What operations did you perform on the system when it first occurred; what operations are being performed at the time of occurrence. find out the possible causes from the information and select the corresponding solution to try to eliminate them.

3. 0x0000001A: MEMORY_MANAGEMENT

◆ Error Analysis: This memory management error is often caused by hardware, such as the newly installed hardware and memory problems.

◇ Solution: If it appears during Windows installation, it may be because your computer does not meet the minimum memory and disk requirements for Windows installation.

4. 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED

◆ Error Analysis: an invalid or unknown process command is detected in the Windows Kernel. The shutdown code is generally caused by the faulty memory or similar causes as 0x0000000A.

◇ Solution:

(1) hardware compatibility problems: Check whether all hardware is included in the list against the latest hardware compatibility list mentioned above.

(2) Problematic device drivers, system services, or memory conflicts and interruptions: if the driver name appears in the blue screen information, please try to disable or delete the driver in installation mode or fault recovery console and disable all newly installed drivers and software. if the error occurs during system startup, go to secure mode and rename or delete the files marked in the blue screen information.

(3) If the error message clearly states that Win32K. sys is likely to be caused by a third-party remote control software, you need to disable the service of the software from the fault recovery console.

(4) The first restart after Windows is installed: The maximum suspicion may be caused by insufficient disk space or BIOS compatibility.

(5) If a software is disabled: the software may have design defects, please upgrade or uninstall it.

5. 0x00000023: FAT_FILE_SYSTEM

0x00000024: NTFS_FILE_SYSTEM

◆ Error Analysis: 0x00000023 usually occurs when reading and writing the system partition of the FAT16 or FAT32 file system, while 0x00000024 is caused by NTFS. sys File error (this driver file is used to allow the system to read and write. (NTFS file system disk ). these two blue screen errors may be caused by physical damage to the disk, or the failure of the interrupt request packet (IRP. other causes include: Too Many disk fragments, too frequent file read/write operations, and a large amount of data, or caused by some disk image software or anti-virus software.

◇ Solution:

Step 1: First open the command line prompt and run "Chkdsk/r" (Note: It is not CHKDISK, it feels like this, but the content they refer to is different) command to check and fix hard disk errors. If a Bad Track is reported, use the checking tool provided by the hard disk manufacturer to check and fix the problem.

Step 2: Disable all software that scans files, such as anti-virus software, firewall, or backup tools.

Step 3: Right-click C: winntsystem32driversfastfat. sys File and select "properties" to check whether the version matches the Windows version used by the current system. (Note: If it is XP, it should be C: windowssystem32

Driversfastfat. sys)

Step 4: Install the latest motherboard driver, especially the IDE driver. If your drive and removable storage have drivers, upgrade them to the latest version.

0x00000027: RDR_FILE_SYSTEM

◆ Error Analysis: it is difficult to judge the cause of this error. However, a problem with Windows Memory Management may cause this shutdown code.

◇ Solution: If it is memory management, increasing the memory will solve the problem.

7. 0x0000002EATA_BUS_ERROR

◆ Error analysis: the system memory parity error is usually caused by defective memory (including physical memory, secondary cache, or video card memory) when the device driver accesses a non-existent memory address. in addition, the hard disk is damaged by viruses or other problems to see the shutdown code.

◇ Solution:

(1) Check for viruses

(2) run the "chkdsk/r" command to check all disk partitions.

(3) Use memory testing software such as Memtest86 to check the memory.

(4) check whether the hardware is correctly installed, for example, whether it is solid or whether there are stains on the golden finger.

8. 0x00000035: NO_MORE_IRP_STACK_LOCATIONS

◆ Error Analysis: literally, the driver or some software may have a stack problem. In fact, the real cause of this fault should be a problem with the driver, or the memory may have a quality problem.

◇ Solution: Use the drivers and memory-related solutions described above to eliminate them.

9. 0x0000003F: NO_MORE_SYSTEM_PTES

◆ Error Analysis: An error related to system memory management. For example, a large number of input/output operations may cause memory management problems: defective drivers improperly use memory resources. An application (such as backup software) is allocated a large amount of kernel memory.

◇ Solution: Uninstall all newly installed software (especially those applications and anti-virus software that enhance disk performance) and drivers.

10. 0x00000044: MULTIPLE_IRP_COMPLIETE_REQUESTS

◆ Error Analysis: usually caused by hardware drivers.

◇ Solution: uninstall the recently installed driver. this fault rarely occurs. What we know now is that some software of www.in-system.com/will appear when you use the software of www.in-system.com/and the token is Falstaff. sys File. (I am not afraid of a lawsuit. I will publish the company website)

11. 0x00000050: PAGE_FAULT_IN_NONPAGED + AREA

◆ Error Analysis: problematic memory (including physical memory, secondary cache, and video memory) and incompatible software (mainly remote control and anti-virus software) damage to NTFS volumes and faulty hardware (for example, the PCI card itself is damaged) will cause this error.

◇ Solution: Use the memory, software, hardware, hard disk, and other related solutions described above to eliminate them.

12, 0x00000051: REGISTRY_ERROR

◆ Error Analysis: this shutdown code indicates that the Registry or System Configuration Manager has an error. The hard disk itself is physically damaged or the file system is faulty, resulting in input/loss during file reading.