The famous Windows blue screen, also known as screen of death or blue screen of death , continues to be present in Windows 10. Although its appearance is gradually becoming less common, no computer is exempt from presenting this type of error . Along with the appearance of the blue screen, a code or text string is usually reflected that defines the type of error that is thrown. The problem is that the description of this error is usually limited or even redundant. For this reason we have made a compilation of all the errors and codes of the Windows 10 blue screen of death with its subsequent explanation and its possible solution.
index of contents
- ACPI BIOS ERROR
- ATTEMPTED EXECUTE OF NOEXECUTE MEMORY
- BAD CONFIG SYSTEM INFO
- BAD POOL CALLER
- BAD POOL HEADER
- BUGCODE NDIS DRIVER
- CLOCK WATCHDOG TIMEOUT
- CRITICAL OBJECT TERMINATION
- CRITICAL OBJECT TERMINATION
- CRITICAL PROCESS DIED
- DRIVER CORRUPTED EXPOOL
- DRIVER IRQL NOT LESS OR EQUAL
- DRIVER POWER STATE FAILURE
- DRIVER UNLOADED WITHOUT CANCELLING PENDING OPERATIONS
- END OF NT EVALUATION PERIOD
- FATAL SYSTEM ERROR
- HAL INITIALIZATION FAILED
- INACCESSIBLE BOOT DEVICE
- INTERNAL POWER ERROR
- IRQL NOT LESS OR EQUAL
- KERNEL AUTO BOOST LOCK ACQUISITION WITH RAISED IRQL
- KERNEL DATA INPAGE ERROR
- KERNEL MODE EXCEPTION NOT HANDLED
- KERNEL STACK INPAGE ERROR
- KMODE EXCEPTION NOT HANDLED
- MACHINE CHECK EXCEPTION
- MEMORY MANAGEMENT
- MULTIPLE IRP COMPLETE REQUESTS
- NMI HARDWARE FAILURE
- NO MORE IRP STACK LOCATIONS
- NTFS FILE SYSTEM
- PAGE FAULT IN NONPAGED AREA
- POWER OFF ERROR
- REGISTRY FILE FAILURE or stop c0000218
- SESSION 3 INITIALIZATION FAILED
- STATUS IMAGE CHECKSUM MISMATCH
- STATUS SYSTEM PROCESS TERMINATED
- SYSTEM SERVICE EXCEPTION
- SYSTEM THREAD EXCEPTION NOT HANDLED
- THREAD STUCK IN DEVICE DRIVER
- UNEXPECTED KERNEL MODE TRAP
- UNMOUNTABLE BOOT VOLUME
- VIDEO TDR FAILURE
- WHEA UNCORRECTABLE ERROR
- The general solution to most Windows 10 blue screens
ACPI BIOS ERROR
There is a conflict between the BIOS and the ACPI system. It is usually solved by disabling the ACPI option in the BIOS.
ATTEMPTED EXECUTE OF NOEXECUTE MEMORY
It is usually related to the conflict between different drivers or to using an old component. In general, this error usually appears when a component is installed in the computer (hard disk, RAM memory, processor, etc.).
BAD CONFIG SYSTEM INFO
Conflicts with the Windows startup or registry or with the hard disk. In this other article we give some solutions to this error.
BAD POOL CALLER
Conflicting driver or driver. It may appear when a driver is installed that is not designed for the version of Windows it is running on.
BAD POOL HEADER
Generally, this error usually comes from a conflict with the RAM memory. Incorrectly installed modules, unsupported RAM ...
BUGCODE NDIS DRIVER
It is usually related to a conflict in the network drivers. For example, when using an external device as an access point (mobile phone, antenna or USB WiFi etc.).
CLOCK WATCHDOG TIMEOUT
The processor is not able to manage threads. It may be a problem with the processor itself or with Windows.
CRITICAL OBJECT TERMINATION
This message comes to notify that an important component of Windows has been modified in a sudden way, causing a corruption of the kernel and virtual memory. It can be due to malware or even a faulty component.
CRITICAL OBJECT TERMINATION
Violation of some Windows protocols associated with system drivers or the kernel itself. It usually occurs when Windows is suspended or hibernated.
CRITICAL PROCESS DIED
It usually occurs when a critical system process stops suddenly, such as the csrss.exe process.
DRIVER CORRUPTED EXPOOL
Damaged controller. If we have recently updated the drivers of our computer, it is likely that they are generating a conflict with Windows. The solution is to go back to a previous version of the drivers.
DRIVER IRQL NOT LESS OR EQUAL
Driver not compatible with Windows. It is recommended to uninstall the driver or install a newer or older compatible version.
DRIVER POWER STATE FAILURE
A driver is preventing Windows from properly managing the power supplied to the components. It usually occurs when the computer is hibernated or suspended.
DRIVER UNLOADED WITHOUT CANCELLING PENDING OPERATIONS
Windows has detected that a driver is not compatible with the system when it is performing critical operations.
END OF NT EVALUATION PERIOD
End of Windows trial period. We will have to activate Windows with a legal license to eliminate this error.
FATAL SYSTEM ERROR
The csrss.exe or winlogon.exe files have been corrupted or we have installed a damaged component. It also usually appears as STOP c000021a. It usually has a solution by restoring the system to a previous point.
HAL INITIALIZATION FAILED
Conflict with the hal.dll library.
INACCESSIBLE BOOT DEVICE
The boot hard disk cannot be accessed. It may be due to partition system corruption or a bad connection between the hard drive and the motherboard.
INTERNAL POWER ERROR
It usually occurs when Windows detects an abnormal flow of power during the system's execution (electrical storms, power surges, etc.). For safety, the computer will be shut down to avoid damage to the motherboard and other components.
IRQL NOT LESS OR EQUAL
Driver not compatible with Windows. It is solved with the installation of a previous or more recent version that is compatible.
KERNEL AUTO BOOST LOCK ACQUISITION WITH RAISED IRQL
Various drivers are causing a conflict with the Windows kernel.
KERNEL DATA INPAGE ERROR
Windows is unable to interpret the data stored in RAM due to a possible component error.
KERNEL MODE EXCEPTION NOT HANDLED
In general, it usually appears when the RAM memory is faulty, although it is also associated with problems with the hard disk or the motherboard.
KERNEL STACK INPAGE ERROR
It may be due to a virus or a bad condition of the cables that connect the drives to the motherboard.
KMODE EXCEPTION NOT HANDLED
Several drivers are causing a conflict with the Windows kernel when starting or executing a certain action. It can also be due to a faulty component.
MACHINE CHECK EXCEPTION
It is usually related to overclocking processes generally associated with the processor, motherboard or graphics card. Setting all the components to their normal values usually has a solution.
Defective RAM or virtual memory limit reached. It could be due to a virus or a program or game that is occupying a greater amount of RAM than the memory installed in the computer.
MULTIPLE IRP COMPLETE REQUESTS
A controller called the IoCompleteRequest class to request the completion of an IRP process but ended up with an error.
NMI HARDWARE FAILURE
It usually comes from a conflict with RAM or ROM. It can also be due to a faulty component.
NO MORE IRP STACK LOCATIONS
The IoCallDriver class has no more stack locations left to handle IRP processes.
NTFS FILE SYSTEM
The origin of this error has multiple reasons. It may be caused by a conflict with the damaged boot hard drive, a problem with the partitioning system, or a defect in the hard drive or the drive cables connecting it to the motherboard.
PAGE FAULT IN NONPAGED AREA
Various drivers are causing a conflict with the Windows kernel. It can also be due to a faulty component.
POWER OFF ERROR
The system is not able to shut down properly. It may be due to a problem with the power supply, the processor, or a virus that is causing the system not to shut down.
REGISTRY FILE FAILURE or stop c0000218
It usually occurs when a hive in the Windows registry is unable to be read or paged.
SESSION 3 INITIALIZATION FAILED
Hard disk, RAM or disk drive damaged or in conflict with Windows.
STATUS IMAGE CHECKSUM MISMATCH
A driver or DLL library is corrupt. The solution is to reinstall the driver or library manually.
STATUS SYSTEM PROCESS TERMINATED
Driver or software not compatible with Windows.
SYSTEM SERVICE EXCEPTION
It usually occurs when updating the BIOS firmware or running a program that is not compatible with the operating version of Windows.
SYSTEM THREAD EXCEPTION NOT HANDLED
Incompatible drivers or software. It can also be due to a BIOS corruption or the installation of an unsupported component.
THREAD STUCK IN DEVICE DRIVER
Problems with the graphics card drivers. It is usually solved by reinstalling the driver or reverting to an old version of the driver in question.
UNEXPECTED KERNEL MODE TRAP
Incompatible software or faulty hardware. Generally they are usually RAM or hard drives.
UNMOUNTABLE BOOT VOLUME
The boot disk cannot be mounted. The origin of this problem can be due to a corruption of the boot partitions, a bad installation of a hard disk or problems with the SATA or IDE cables that go from the disk to the motherboard. They are also associated with a motherboard change or a priority change when executing disks from the BIOS. For example, when you try to boot from a pendrive or hard drive but there is no system loaded on it.
VIDEO TDR FAILURE
The graphics card is faulty or the display driver has failed. It is recommended to update the driver to the latest version or check the connection to the card board.
WHEA UNCORRECTABLE ERROR
Windows has encountered an uncorrectable hardware error. RAM memory, processor, hard disk, graphics card ...
The general solution to most Windows 10 blue screens
Let's be frank, there is no one-size-fits-all solution to all these errors. But this does not mean that we cannot carry out a common method to solve some Windows errors.
To do this, we will first have to access the Window 's CMD by typing 'Command Prompt' in the search box . Once Windows shows us the result, we will right-click on the program in question and run it as administrators. Now we will have to enter the following command:
- sfc / scannow
Windows will automatically start a general repair process that will try to repair some system errors, if any, and that can last up to 30 minutes , depending on the power of our computer. In case the program does not detect any error we will have to enter the following command:
- DISM.exe / Online / Cleanup-image / Restorehealth
Once the command has been executed, we will restart the computer so that the changes are applied correctly. If the error persists, we can follow the methods detailed in this article, where we solve one of the most common errors in Windows 10. We can also contact Microsoft's support service directly if we have a legal license for the system.