The famous Windows blue screen, also known as the screen of death, is still present in Windows 10. Along with the appearance of the blue screen, there is usually a code or text string that defines the type of error that is displayed. The problem is that the description of this error is usually limited or even redundant. For this reason, we have made a compilation with all the errors and codes of the blue screen of the death on Windows 10 with its subsequent explanation and possible solution.
ACPI BIOS Error
There is a conflict between the BIOS and the ACPI system. This 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 for using an old component. This error usually appears when a component is installed on the computer (hard disk, RAM, processor, etc.).
Bad System Config Info
Conflicts with the Windows boot or registry or with the hard disk. In this other article, we give some solutions to this error.
Bad Pool Caller
Conflicting driver or controller. It may appear when you install a driver that is not designed for the version of Windows you are running.
Bad Pool Header
Usually, this error comes from some conflict with RAM. Badly installed modules, unsupported RAM…
Bugcode NDIS Driver
It is usually related to a conflict in the network controllers. 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 capable of managing the process threads. It can be a problem with the processor itself or Windows.
Critical Object Termination
This message notifies that an important component of Windows has been suddenly modified, causing kernel and virtual memory corruption. This may 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. This usually occurs when Windows is suspended or hibernated.
Critical Process Died
It usually appears when a critical process in the system stops suddenly, such as the csrss.exe process.
Driver Corrupted Expool
Damaged controller. If you have recently updated your computer’s drivers, they are likely generating some conflict with Windows. The solution is to go back to an earlier version of the drivers.
Driver Irql Not Less Or Equal
The driver is 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. This usually occurs when the computer is hibernating or shutting down.
Driver unloaded without canceling 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 the Windows trial period. You will need to activate Windows with a legal license to remove this error.
Fatal System Error
The files csrss.exe or winlogon.exe have been corrupted or some damaged component has been installed. It is also usually called STOP c000021a. It can be fixed by resetting the system to an earlier point.
HAL initialization failed
Conflict with the hal.dll library.
Inaccessible Boot Device
Cannot access the hard drive for booting. This may be due to a corruption of the partitioning system or a bad connection between the hard disk and the motherboard.
Internal Power Error
This usually occurs when Windows detects an abnormal power flow during system execution (thunderstorms, power surges, etc.). For safety reasons, the computer will be turned off to prevent damage to the motherboard and other components.
IRQL Not Less Or Equal
The driver is not compatible with Windows. This is solved by installing an older or more recent version that is compatible.
Kernel Auto Boost Lock Acquisition With Raised IRQL
Several drivers are causing a conflict with the Windows kernel.
Kernel Data Inpage Error
Windows is not able to interpret the data stored in RAM due to a possible component error.
Kernel-mode exception not handled
It usually appears when RAM is defective but is also associated with hard disk or motherboard problems.
Kernel stack inpage error
This may be due to a virus or the poor condition of the cables connecting the disks to the motherboard.
Kmode Exception Not Handled
Several drivers are causing a conflict with the Windows kernel at startup or when a certain action is executed. This may 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 components to their normal values usually provides a solution.
Defective RAM or virtual memory limit reached This can be caused by a virus or by a program or game that is taking up more RAM than the memory installed on your computer.
Multiple IRP complete requests
A controller has called the IoCompleteRequest class to request the completion of an IRP process but it has ended up generating an error.
NMI Hardware Failure
It usually comes from a conflict with RAM or ROM memory. It may also be due to a defective component.
No more IRP stack locations
The IoCallDriver class has no more stack locations left to manage the IRP processes.
NTFS file system
The origin of this error has multiple reasons. It may be due to a conflict with the damaged boot disk, a problem with the partitioning system, or a defect in the hard disk or the disk cables that connect it to the motherboard.
Page Fault In Nonpaged Area
Several drivers are causing a conflict with the Windows kernel. This may also be due to a faulty component.
Power Off Error
The system is not able to shut down properly. This 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 Failure or Stop C0000218
It usually occurs when a sub-tree of the Windows registry is not readable or paginated.
Session 3 initialization failed
Damaged or conflicting hard disk, RAM or disk drive
Status Image Checksum Mismatch
A driver or DLL library is corrupted. The solution is to reinstall the driver or library manually.
Status System Process Terminated
Driver or software not compatible with Windows.
System Service Exception
This usually occurs when updating the BIOS firmware or when running a program that is not compatible with the operating version of Windows.
System Thread Exception Not Handled
Incompatible drivers or software. It may also be due to a BIOS corruption or the installation of an unsupported component.
Thread Stuck In Device Driver
Problems with graphics card drivers. This is usually solved by reinstalling the driver or reverting to an older version of the driver in question.
Unexpected Kernel Mode Trap
Incompatible software or defective hardware. These are usually RAM or hard disk.
Unmountable Boot Volume
The boot disk cannot be mounted. This problem can be caused by a corruption of the boot partitions, a bad installation of a hard disk, or problems with the SATA or IDE cables going from the disk to the motherboard. They are also associated with a change of motherboard or a change of priority when running discs from the BIOS. For example, when you try to boot from a pen drive or hard disk but there is no system loaded on it.
Video TDR Failure
The graphics card is defective or the display driver has failed. It is recommended to update the driver to the latest version or check the board connection of the card.
Whea uncorrectable error
Windows has detected an incorrigible hardware error. RAM, processor, hard disk, graphics card…
The Overall Solution to Most Blue Screens in Windows 10
Let’s be frank, there is no single solution to all these mistakes. But this doesn’t mean that we can’t carry out a common method to solve some Windows errors.
To do so, you will have to first access the Windows CMD by typing ‘Command Prompt’ in the search box. Once Windows shows us the result, right-click on the program in question and run it as an administrator. Now we’ll have to enter the following command:
Windows will automatically start a general repair process that will try to repair some system errors if any and can take up to 30 minutes, depending on the power of your computer. In case the program does not detect any errors you will have to enter the following command:
DISM.exe /Online /Cleanup-image /Restorehealth
Once the command has been executed restart the computer so that the changes are applied correctly. If the error persists you can follow the methods detailed in this article where we give solutions to one of the most common errors in Windows 10. You can also contact directly with Microsoft support service if you have a legal license for the system.
This post may contain affiliate links, which means that I may receive a commission if you make a purchase using these links. As an Amazon Associate, I earn from qualifying purchases.