It is common to use a blue screen on Windows, and it is often time-consuming to reinstall the system frequently because it is unclear about the source of the error. The following collection of some Windows blue screen stop code for your reference.
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. Indicates that in kernel mode, a level process request (IRQL) accesses a memory address that it does not have access to.
◇ Solution: Please try to eliminate it with the 2, 3, 5, and 8 solutions in the solution described above.
2, 0x00000012: TRAP_CAUSE_UNKNOWN
◆ Error Analysis: If you encounter this error message, then unfortunately, the result of KeBudCheck analysis is that the cause of the error is unknown.
◇ Solution: Since Microsoft can't help, you have to rely on yourself. Please think carefully about when this error occurred. What did you do to the system when it first occurred; what was going on when it happened? operating. Identify 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. (Windows7 recommended configuration, 1Ghz processor, 1G memory, 16G hard disk)
4, 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
◆ Error Analysis: The Windows kernel has detected an 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 check the latest hardware compatibility list mentioned above to see if all hardware is included in the list.
(2) Problematic device driver, system service or memory conflict and interrupt conflict: If the name of the driver is now displayed on the blue screen, try disabling or removing the driver in the installation mode or the recovery console, and Disable all drivers and software you just installed. If the error occurs during system startup, enter safe mode and rename or delete the file indicated in the blue screen message.
(3) If the error message clearly states that Win32K.sys: is most likely caused by third-party remote control software, the service of the software needs to be closed from the recovery console.
(4) When the first reboot after installing Windows: The biggest suspect may be when the system partition has insufficient disk space or BIOS compatibility.
(5) If it occurs when you close a software: When the software is likely to survive design flaws, 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 The driver file is used to allow the system to read and write to 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 is very large or caused by some disk mirroring software or anti-virus software.
◇ Solution:
First step: first open the command prompt, run “Chkdsk /r” (Note: not CHKDISK, it feels like this, but the content they refer to is not the same) command Check and fix hard disk errors. If there is a bad track reported, please use the inspection tool provided by the hard disk manufacturer to check and repair.
Step 2: Then disable all software that even 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> to see if 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)