Windows blue screen error code list at a glance, let you know what the blue screen is! Interpretation of blue screen stop code: (1)0× 0000000A: IRQL_NOT_LESS_OR_EQUAL is mainly caused by faulty drivers, defective or incompatible hardware and software. Indicates that there is too much process internal request level (IRQL) in kernel mode to access memory addresses that it does not have access to. (2)0× 00000012: TRAP_CAUSE_UNKNOWN If you encounter this error message, it is unfortunate because the result of the KeBugCheck analysis is that the cause of the error is unknown. (Installing innovative sound card may be triggered) (3)0× 0000001A: MEMORY_MANAGEMENT This memory management error is often caused by hardware, such as newly installed hardware, memory itself has problems. (4)0× 0000001EKMODE_EXCEPTION_NOT_HANDLED The Windows kernel checks for an illegal or unknown process instruction. This stop code is generally caused by a problematic memory or a similar reason as (1). (5)0× 00000023: FAT_FILE_SYSTEM 0× 00000024: NTFS_FILE_SYSTEM0× 00000023 usually occurs when reading and writing system partitions using the FAT16 or FAT32 file system, while 0× 00000024 is due to an error in the NTFS.SYS file. The 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: too many hard disk fragments; too many file read and write operations, and the amount of data is very large or Caused by some disk mirroring software or anti-virus software. (6)0× 00000027: RDR_FILE_SYSTEM The cause of this error is difficult to judge. However, a problem with Windows memory management is likely to cause this stop code to appear. (7)0× 0000002E: DATD_BUS_ERROR system memory memory parity error generated, usually due to defective memory (including physical memory, L2 cache or graphics memory) device driver access memory address does not exist, etc., in addition, The stop code will also appear if the hard drive is damaged by a virus or other problem. (8)0× 00000035: NO_MORE_IRP_STACK_LOCATIONS The reason for this stop code is that there is a problem with the driver itself, or there is a quality problem with the memory. (9)0× 0000003F: NO_MORE_SYSTEM_PTES A bug related to system memory management, such as: memory management has been caused by a large number of I/O operations, and defective drivers incorrectly use memory resources; an application The program is allocated a lot of kernel memory and so on. (10)0× 00000044: MULTIPLE_IRP_COMPLETE_REQUESTS is usually caused by a hardware driver (this stop code is not common, which is caused by the newly installed driver in the Falstaff.sys file). (11)0× 00000050: PAGE_FAULT_IN_NONPAGED_AREA There is a problematic memory (including: physical memory, L2 cache, video memory), incompatible software (mainly remote control and anti-virus software), corrupted NTFS volume and problematic hardware. (12)0× 00000051: REGISTRY_ERROR This stop code indicates that the registry or system configuration manager has crops. Because the hard disk itself has physical bad sectors or file system problems, the I/O error occurs when reading and writing the registry file. (13)0× 00000058: FTDISK_INTERNAL_ERROR indicates that an error occurred in the main drive of the fault tolerant set. (14)0× 0000005A: CRITICAL_SERVICE_FAILED A very important system service failed to start. (15)0× 0000006F: SESSION3_INITIALIZATION_FALED This error usually occurs when Windows starts up, usually caused by a problematic driver or a corrupted system file. (16)0× 00000076: PROCESS_HAS_LOCKED_PAGES is usually because a driver does not correctly release the occupied memory after completing an I/O operation. (17)0× 00000077: KERNEL_STACK_INPAGE_ERROR indicates that the kernel data to be used is not in virtual memory. Or found in physical memory. This error often indicates a problem with the hard drive and the corresponding data is corrupted or infected by a virus. (18)0× 0000007A: KERNEL_DATA_INPAGE_ERROR This error is often caused by the fact that kernel data in virtual memory is read by non-partisan people. The cause may be a bad cluster in the virtual memory page file, a virus, a disk controller error, and a memory problem. (19)0× 0000007B:INACCESSIBLE_BOOT_DEVICEWindows cannot access the system partition or boot volume during startup. This usually occurs the first time after the motherboard is replaced. Mainly because the new motherboard and the old motherboard's IDE controller use different chips. Sometimes it can be caused by a virus or hard drive damage. (20)0× 0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED system process generated an error, but the Windows error handler could not capture. It has a lot of causes. Includes: hardware compatibility, problematic drivers or system services, or some software. (21)0× 0000007F: UNEXPECTED_KERNEL_MODE_TRAP is generally caused by faulty hardware or some software, and overclocking will also produce this error. (22)0× 00000080: NMI_HARDWARE_FAILURE is usually caused by hardware. (23)0× 0000008E: KERNEL_MODE_EXCEPTION_NOT_HANDLED kernel-level application generates an error, but the Windows error handler is not captured, usually a hardware compatibility issue. (24)0× 0000009C: MACHINE_CHECK_EXCEPYION is usually caused by hardware, usually due to overclocking or hardware problems (memory, CPU, bus, power). (25)0× 0000009F: DRIVER_POWER_STSTE_FAILURE is often associated with power supplies and often occurs with power-related operations. (Shutdown, standby, sleep). (26)0× 000000A5: ACPI_BIOS_ERROR is usually because the motherboard BIOS cannot fully support the ACPI specification. (27)0× 000000B4: VIDEO_DRIVER_INIT_FAILURE This stop message indicates that Windows cannot enter the graphics interface because it cannot start the graphics card driver, or there is a hardware conflict with the graphics card (parallel or serial port conflict). (28)0× 000000BE: ATTEMPTED_WRITE_TO_READONLY_MEMORY A driver is attempting to write data to read-only memory, usually with a new driver installed. After the system service or upgraded the firmware program of the device. (29)0× 000000C2: BAD_POOL_CALLER A kernel layer process or driver error attempting to perform a memory operation, usually caused by a driver or software that has a bug. (30)0× 000000CE: DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS is usually caused by a problematic driver or system service.