Computer 38 blue screen analysis Daquan

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 a process that is too high in the kernel mode The internal request level (IRQL) accesses the memory address that it does not have access to.
◇Solution: Try to exclude it using the 2, 3, 5, 8, and 9 solutions in the solution described earlier.
2,0x00000012 :TRAP_CAUSE_UNKNOWN
◆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 think carefully about when this error occurred; what did you do to the system when it first occurred; what was happening when it happened. Find out the possible causes from this information and choose the appropriate solution Solution 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, etc.
◇ 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.
0x0000001E: KMODE_EXCEPTION_NOT_HANDLED
◆Error Analysis: The Windows kernel has detected an illegal or unknown process command. This stop code is usually caused by the memory of the problem or a similar reason to the previous 0x0000000A.
◇Solution: Br> (1) Hardware compatibility problem: Please check all the hardware included in the list according to the latest hardware compatibility list mentioned above.
(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 , please enter the safe mode, rename or delete the file marked in the blue screen information.
(3) If wrong The information clearly states that Win32K.sys: is most likely caused by third-party remote control software, and needs to be shut down from the recovery console. [br> (4) appears when the first reboot after installing Windows : The biggest suspicion is that there is a problem with insufficient disk space or BIOS compatibility in the system partition.
(5) If it is caused when the software is closed: It is very likely that there is a design defect in the software 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 FAT16 or FAT32 file system, and
0x00000024 is due to NTFS.sys file Error (The purpose 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 most likely caused by physical damage to the disk itself or by interruption of the request packet (IRP). Other reasons include: too many hard disk fragments; too many file read and write operations, and the amount of data is very high or due to some disk mirrors Software or anti-virus software.
◇Solution:
Step 1: First open the command line prompt, run "Chkdsk /r" (Note: not CHKDISK, it feels like this, but …… The command checks and fixes the hard disk error. If the report has Bad Track, please use the check tool provided by the hard disk manufacturer to check and repair.
Step 2: Then disable all software even if scanning files, for example: antivirus Software, firewall or backup tool.
Step 3: Right-click on the C:\\winnt\\system32\\drivers\\fastfat.sys file and select "Properties" to see if its version matches the Windows version used by the current system. (Note: If it is XP, it should be C:\\windows\\system32
\\drivers\\fastfat.sys)