1, 0x0000000A: IRQL_NOT_LESS_OR_EQUAL
◆ Error analysis: mainly caused by the driver of the problem, defective or incompatible hardware and software. From a technical point of view, indicating that there is too high process internal request level in kernel mode (IRQL) access the memory address that it does not have access to.
◇ Solution: Try to exclude using the 2, 3, 5, 8, and 9 solutions in the solution described above.
2, 0x00000012:TRAP_CAUSE_UNKNOWN< Br>◆Error analysis: If you encounter this error message, then unfortunately, the result of KeBudCheck analysis is the cause of the error
Unknown.
◇ Solution: Since Microsoft can't help, you have to rely on yourself Please remember carefully when this error occurred; what did you do to the system when it first occurred; what was happening at the time of the occurrence. Find out the possible causes from this information and choose the appropriate solution to try to exclude .
3,0x0000001A:MEMORY_MANAGEMENT
◆Error Analysis: This memory management error is often caused by hardware, such as: newly installed hardware, memory itself has problems.
Solution: If it appears when installing Windows, it may be because your computer does not meet the minimum memory and disk requirements for installing Windows.
4, 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
◆Error analysis: Windows kernel checks one Illegal or unknown process instruction, this stop code is usually caused by the memory of the problem or the reason similar to the previous 0x0000000A.
◇ Solution:
(1) Hardware compatibility problem: Please refer to the above mentioned The latest hardware compatibility list, see if all hardware is included in the list.
(2) Problematic device driver, system service or memory conflict and interrupt conflict: If the driver name appears in the blue screen message, Try disabling or removing the driver in the installation mode or the Recovery Console and disabling all newly installed drivers and software. If the error occurs during system startup, enter safe mode and double the file indicated in the blue screen message. Named or deleted.
(3) If the error message clearly states Win32K.sys: It is most likely caused by third-party remote control software, need The software in the Recovery Console will be shut down.
(4) When the first reboot after installing Windows: The maximum suspect may be insufficient disk space or BIOS compatibility in the system partition.
(5 If it appears when closing a certain software: When there is a possibility that the software has a design flaw in the province, please upgrade or uninstall it.
5, 0x00000023: FAT_FILE_SYSTEM
0x00000024: NTFS_FILE_SYSTEM
◆Error Analysis: 0x00000023 Usually occurs when reading or writing the system partition of the FAT16 or FAT32 file system, and
0x00000024 is due to an error in the NTFS.sys file (this driver file is used to allow the system to read and write the disk using the
NTFS file system) These two blue screen errors are most likely caused by physical damage to the disk itself or by the interruption of the request packet (IRP). Other reasons include: excessive disk fragmentation; file read and write operations are too frequent, and the amount of data Very up to or caused by some disk mirroring software or anti-virus software.
◇ Solution:
First step: first open the command line prompt, run "Chkdsk /r" (Note: not C HKDISK, feels like this, but the ……) command checks and fixes hard drive errors. If there is a Bad Track report, please use the check tool provided by the hard drive manufacturer to check and repair.
Step 2: Next Disable all software that scans files, such as anti-virus software, firewalls, or backup tools.
Step 3: Right-click on the C:\\winnt\\system32\\drivers\\fastfat.sys file and select "Properties" Whether the version matches the version of Windows used by the current system. (Note: If it is XP, it should be C:\\windows\\system32
\\drivers\\fastfat.sys)