│ 1 └-┘ xa: IRQL _ not _ less _ or _ equal

◆ Error analysis: mainly caused by faulty drivers, defective or incompatible hardware and software. Access the memory address that it does not have permission to access.

◇ Solution: Please try to exclude it by using the 2, 3, 5, 8 and 9 schemes in the previous solution.

┌-┐

└-x12. Because the result of KeBudCheck analysis is that the cause of the error is unknown.

◇ Solution: Since Microsoft can't help, it has to rely on itself, please carefully recall when this error occurred; What did you do to the system the first time

happened? What was going on when it happened? Find out the possible reasons from this information, and then choose the corresponding

solution to try to eliminate it.

┌-┐

┖ 3 └

┘ x1a: memory _ management

◆ Error analysis: this memory. For example, there is something wrong with the newly installed hardware and memory itself.

◇ Solution: If it appears when installing Windows, It may be that your computer can't meet the minimum memory and

disk requirements for installing Windows.

┌-┐

└ ┘ x1e: kmode _ exception _ not _ handled

◆ Error analysis: Windows. This shutdown code is generally caused by faulty memory or

a reason similar to the previous xA.

◇ Solution:

(1) There is something wrong with hardware compatibility: please refer to the latest hardware compatibility list mentioned above. Check whether all the hardware is included in the list.

(2) There are problems with device drivers, system services or memory conflicts and interrupt conflicts: If the name of the driver appears in the blue screen information,

please try to disable or delete the driver in the installation mode or the recovery console, and disable all the newly installed drivers and software. If the error

appears in the system startup process by mistake, please enter the safe mode. Rename or delete the file indicated in the blue screen information.

(3) If the error message clearly indicates that Win32K.sys: is probably caused by a third-party remote control software, The service of the software needs to be turned off from the fault recovery

console.

(4) It appears at the first restart after installing Windows: the maximum suspicion is that the disk space of the system partition is insufficient or there is a problem with BIOS compatibility.

(5) If it appears at the time of turning off a software, it is likely that the software has design defects in the province. Please upgrade or uninstall it.

┌-┐

│ 5 │ x23: fat _ file _ system

└-x24: NTFS _ file _ system

◆ Error analysis: x. x24 is

caused by an error in the NTFS.sys file (the function of this driver file is to allow the system to read and write the disk using the NTFS file system). These two blue screen

errors are probably caused by physical damage of the disk itself or the damage of the interrupt request packet (IRP). Other reasons include: too many magnetic

disk fragments on the hard disk; File reading and writing operations are too frequent, and the amount of data is very large or it is caused by some disk mirroring software or antivirus software.

◇ Solution:

Step 1: First, open the command prompt and run "Chkdsk /r" (note: it's not CHKDISK, it feels like this, but ...) command to check

and repair hard disk errors. If a Bad Track is reported, please use the inspection tools provided by the hard disk manufacturer to check and repair it.

Step 2: Then disable all software that scans files, such as antivirus software, firewall or backup tools.

Step 3: Right-click the file C: \ winnt \ system32 \ drivers \ fastfat.sys and select "Properties". Check whether its version is consistent with the version of Windows currently used by the

system. (Note: if it is XP, it should be C: \ Windows \ System32 \ drivers \ fastfat.sys)

Step 4: Install the latest motherboard driver, especially IDE driver. If your CD-ROM drive and mobile storage also provide drivers,

it's better to upgrade them to the latest version.

┌— ┐

│ 6 └ ┘ x27: RDR _ file _ system

◆ Error analysis: It's difficult to judge the cause of this error, but there is something wrong with Windows memory management. Usually increasing memory will solve the problem.

┌-┐

│ 7 │

└-┘ x2 EATA _ BUS _ ERROR

◆ Error analysis: The system memory parity generates errors, usually because of defective memory (including physical memory and secondary cache) The hard disk is

damaged by virus or other problems, so this shutdown code appears.

◇ Solution:

(1) Check the virus

(2) Check all disk partitions with "chkdsk /r" command.

(3) Check the memory with memory testing software such as Memtest86.

(3) For example, whether the gold finger is firm or not, and whether the gold finger is stained.

┌— ┐

│ 8 └ ┘ x35: no _ more _ IRP _ stack _ locations

◆ Error analysis: literally, Or there is a quality problem with the memory.

◇ Solution: Please use the scheme related to drivers and memory in the conventional solution described above to eliminate it.

┌-┐

└-┘ x3f: no _ more _ system. An application (such as backup software) is allocated a lot of

kernel memory, etc.

◇ Solution: uninstall all the latest installed software (especially those applications and antivirus software that enhance disk performance). And drivers.

┌-┐

┖ 1 ┖

└-x44: multiple _ IRP _ compile _ requests

◆ Error analysis: usually caused by hardware drivers.

┘ It will appear when using

/ some software of this company, and the culprit is the Falstaff.sys file. (The author is not afraid of taking legal action. Publish the company website)

┌-┐

┌ 11 │

└-x5: page _ fault _ in _ nonpaged+area

◆ Error analysis: faulty memory (including room memory and secondary cache) Damaged NTFS volume and faulty hardware (for example, the PCI card itself is damaged) will cause this error.

◇ Solution: Please use the conventional solution described above which is related to memory, software, hardware, Hard disk and other related solutions are excluded.

┌-┐

│ 12 │

└-┘ x51: registry _ error

◆ Error analysis: this stop code indicates that there is an error in the registry or system configuration manager, because the hard disk itself is physically damaged or the file system is < This causes input/output errors when reading the registration file.

◇ Solution: Use "chkdsk/ R "Check and repair disk errors.

┌— ┐

│ 13 │

└— ┘ x58: ftdisk _ internal _ error

◆ Error analysis: Error occurred in the main driver of the fault-tolerant set.

┘. Then try "last correct configuration" to solve

┌-┐

│ 14 │

└-┘ x5e: critical _ service _ failed

◆ Error analysis: caused by a very important system service startup identification. < And check whether it is

compatible with Windows 2K/XP through the online list, and then start the computer. If the blue screen still appears, please use "Last Correct Configuration" to start Windows.

If this still fails, It is recommended to repair, install or reinstall.

┌-┐

│ 15 │

└-┘ x6f: Session3 _ initialization-failed

◆ Error analysis: This error usually occurs when Windows starts. Generally,

is caused by faulty drivers or damaged system files.

◇ Solution: It is recommended to use the Windows installation CD to repair and install the system.

┌-┐

│ 16 └-┘ x76: process. Run: regedt32, find [hklm \ system \ current control set \ control \ session

manager \ memory management], and create a new double-byte value "TrackLockedPages" on the right. The value is 1, so that Windows can track which driver has the problem when the error

appears again.

Step 2: If the blue screen appears again, the error message will become:

STOP:xCB(xY,xY,xY, xY) driver _ left _ locked _ pages _ in _ process

The fourth "xy" will be displayed as the name of the problem driver, and then it will be updated or deleted.

Step 3: Enter the registry. Delete the added "TrackLocked Pages".

┌— ┐

│ 17 ┖

└— ┘ x77: kernel _ stack _ inpage _ error

◆ Error analysis: it means that the kernel data needed is not in virtual memory or physics. Use the "chkdsk /r" command to check and repair disk errors. If it doesn't work, use the tools provided by the disk

manufacturer to check and repair it.

┌-┐

└-┘ x7a: kernel _ data _ inpage _ error

◆ Error analysis: this error is often in virtual memory. There is something wrong with the disk controller and there is something wrong with the memory.

◇ Solution: First, use the anti-virus software upgraded to the latest virus database to kill the virus. If there is xC9C or

xC16A code in the prompt message, it means that it is caused by a bad cluster, and the disk detection tool of the system cannot be automatically repaired. At this time, you should enter the "Fault Recovery Console". Use the "chkdsk /r" command for manual repair.

┌-┐

└ ┘ x7b: inaccessible _ boot _ device

◆ Error analysis: Windows cannot access the system partition during startup. Mainly because the IDE controller of the new motherboard and the old motherboard uses different chipsets. Sometimes it may be caused by virus or hard disk damage.

◇ Solution: generally, just start the computer with the installation chkd, and then perform repair installation to solve the problem. For the virus, you can use DOS

antivirus software to kill it (the main battle is kv25DOS download). If there is a problem with the hard disk itself, please