Blue Screen code and solution in XP

1. Code 0x0000000 @: HRPL ^ NNT ^ LERS_OR_DQU @ L
◆ Failure Analysis: mainly caused by problematic drivers, defective or incompatible hardware and software. from a technical point of view. it indicates that there is an Ethernet internal request level (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. xp blue screen code 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 ***** and interruptions *****: if the driver name appears in the blue screen information, please try at 0 Cang 0D #? Or disable or delete drivers and disable all newly installed drivers and software in the Recovery Console. If an error occurs during system startup, go to security xJ? 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 program 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 in this province, 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
0x00000024 is caused by an error in the NTFS. sys file (this driver file is used to allow the system to read and write data.
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 extremely high data volume, or because of some disk image software or anti-virus tool Yin QIZ.
TIPS:
Next step: First open the command line prompt and run Chkdsk/r (Note: It is not CHKDISK, it feels like this, ......) Command to check and fix hard disk errors. If the report contains a Bad Track, use the checking tool provided by the hard disk vendor 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: winntsystem32drivers astfat. 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
Drivers astfat. 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. blue screen code 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 has a stack problem. In fact, the real cause of this fault should be that the driver has a problem in this province, or the memory has 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. blue screen code STOP: 0x00000044: MULTIPLE_IRP_COMPLIETE_REQUESTS
◆ Error Analysis: usually caused by hardware drivers.
◇ Solution: uninstall the recently installed driver. This fault rarely occurs. It is known that
11. 0x00000050: P @ FD ^ F @ TLT ^ HN_NONPAGDD + @ REA
◆ Error Analysis: problematic memory (including in-house 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.
Row exclusion.
12, 0x00000051: REGISTRY_ERROR
◆ Error analysis: the shutdown code indicates that the Registry or System Configuration Manager is incorrect. The hard disk is physically damaged or the file system is faulty, this results in an input/output error when reading the registered file.
◇ Solution: Use chkdsk/r to check and fix disk errors.
13. 0x00000058: FTDISK_INTERNAL_ERROR
◆ Error Analysis: It indicates that an error occurs in the master drive of the fault tolerance set.
◇ Solution: First, try restarting the computer to see if the problem can be solved. If not, try the last correct configuration.
14. 0x0000005E: CRITICAL_SERVICE_FAILED
◆ Error analysis: a very important system service startup identification result.
◇ Solution: if a new hardware is installed, You can first remove it and check whether it is compatible with Windows 2 K/XP through the online list, start the computer. If the blue screen still appears, use the last correct configuration to start Windows. If this still fails, it is recommended to repair and install or reinstall it.
15, 0x0000006F: SESSION3_INITIALIZATION-FAILED
◆ Error Analysis: this error is usually caused by a faulty driver or damaged system file when Windows is started.
◇ Solution: We recommend that you use Windows to install L6T? System for repair and installation.
16. 0x00000076ROCESS_HAS_LOCKED_PAGES
◆ Error Analysis: Usually it is because a driver has completed an input/input haze. Why? The occupied memory is not correctly released
◇ Solution:
Step 1: Click start --> Run: regedt32, find [HKLMSYSTEMCurrentcontrol setcontrolsession managermemory managsment], and create a two-byte value TrackLockedPages on the right. The value is 1. in this way, Windows will track the driver when the error occurs again. step 2: If the blue screen appears again, the error message will be: STOP: 0x0000000CB (0xY, 0xY, 0xY, 0xY) DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS. The fourth 0xY will be the name of the problematic driver, then update or delete it. step 3: Go to the Registry and delete the added TrackLockedPages.
17. 0x00000077: KERNEL_STACK_INPAGE_ERROR
◆ Error Analysis: It indicates that the kernel data to be used is not found in the virtual memory or physical memory. This error is often caused by disk problems, data corruption or virus erosion.
◇ Solution: Use anti-virus software to scan the system. Use the chkdsk/r command to check and fix disk errors. If not, use the disk manufacturer's taobaoz tea for repair.
18. 0x0000007A: JERNEL_DATA_INPAGE_ERROR
◆ Error Analysis: this error is often caused by kernel data in the virtual memory being unable to be read into the memory. the possible cause is that the virtual memory page file contains bad clusters, viruses, disk controller errors, and memory problems.
◇ Solution: first, use the latest antivirus software to scan and kill viruses.
Or 0xC000016A code, it indicates that it is caused by a bad cluster, and the system's disk detection tool cannot be automatically repaired. In this case, you need to go to the fault recovery console and use the chkdsk/r command for manual repair.
19. 0x0000007B: INACESSIBLE_BOOT_DEVICE
◆ Error Analysis: Windows cannot access system partitions or start volumes during startup. generally, it occurs when the motherboard is started for the first time after the motherboard is changed because the new motherboard and the IDE controller of the old motherboard use different chipset. it may also be caused by viruses or hard disk damage.
◇ Solution: Generally, you only need to use the installation disc to start the computer, and then perform repair and installation to solve the problem. for viruses, you can use anti-virus software of the DOS version to scan and kv2005DOS for viruses ). if there is a problem with the hard disk itself, install it on another computer, and then use chkdsk/r to check and fix disk errors.
20. 0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
◆ Error Analysis: system process errors are generated, but cannot be captured by the Windows Error processor. There are many causes, including hardware compatibility, problematic drivers, system services, and some software.
◇ Solution: Use the Event Viewer to obtain more information and find the root cause of the error. (It seems that it is not a solution. It seems that we are going to be self-reliant here !)

21. 0x0000007F: UNEXPECTED_KERNEL_MOED_TRAP
◆ Error Analysis: this error is generally caused by faulty hardware (such as memory) or some software. Sometimes this error is caused by overclock.
◇ Solution: Use the detection software (for example, Memtest86) to check the memory. If the overclocking is performed, cancel the overclocking. remove the PCI hardware plug-in from the motherboard slot or change the slot. in addition, some motherboard (such as nForce2 motherboard) after the frequency is too high, the south bridge chip overheating will also lead to a blue screen, at this time for the chip to add a heat sink alone can effectively solve the problem.
22, 0x00000080: NMI_HARDWARE_FAILURE
◆ Error Analysis: it is usually caused by hardware. (It seems that blue screen and hardware errors do not exist)
◇ Solution: If you have recently installed new hardware