Windows 8.1 Most common BSOD List
Is a list of the most common Windows 8.1 issues and there causes, and the ways to solve them. The entire post is sorted by error code number, but for easier navigation it suggested that you use the table of contents. If an error code you are receiving is not listed, then contact us and we’ll add it.
Under each error code is the official description of the code as seen on MSDN and the most common reason: Driver, Memory, HDD, System Corruption, Third-Party applications and their chance of causing the BSOD.
0x0000000A IRQL_NOT_LESS_OR_EQUAL
This error occurs when the paged memory (invalid memory) has reached IRQL that it to high.
[tabs][tab title=”Common Solution”]| Common Reason | Faulty driver installation |
| Common Solution | Remove any recent installed drivers and software and download and install all the latest drivers for your system |
| Drivers | 5/5 |
| Memory (RAM) | 3/5 |
| HDD | 1/5 |
| System Corruption | 3/5 |
| Third-party software | 2/5 |
0x00000019 BAD_POOL_HEADER
This error indicates that a pool header is corrupted, ask an expert to help you further, since this is caused by drivers and the only way to find the cause is to use Driver Verifier, which is something that has to be done by experts.
[tabs][tab title=”Common Solution”]| Common Reason | Faulty driver installation |
| Common Solution | Remove any recent installed drivers and software and download and install all the latest drivers for your system |
| Drivers | 5/5 |
| Memory (RAM) | 4/5 |
| HDD | 1/5 |
| System Corruption | 4/5 |
| Third-party software | 1/5 |
0x0000001A MEMORY_MANAGEMENT
This error indicates that the system memory has encountered a critical error and has failed, this is in most cases caused by faulty RAM modules, and in rare cases by system corruption.
[tabs][tab title=”Common Solution”]| Common Reason | Damaged RAM Modules |
| Common Solution | Test each stick seperatly with Memtest 86+ to determine which RAM module is resulting error codes. (7 passes is adviced). Replace or remove the faulty RAM module |
| Drivers | 1/5 |
| Memory (RAM) | 5/5 |
| HDD | 1/5 |
| System Corruption | 1/5 |
| Third-party software | 1/5 |
0x00000024 NTFS_FILE_SYSTEM
This error indicates that the system its file system driver (ntfs.sys in this case) has critically failed. The most common reason for this is hard disk corruption and corrupted IDE and SCSI drivers.
[tabs][tab title=”Common Solution”]| Common Reason | Hard Disk Corruption |
| Common Solution | Start an elevated command prompt and run CHKDSK . You can do this by entering the following command in the elevated command prompt Chkdsk /f /r. This does require a reboot for System Partitions. |
| Drivers | 4/5 |
| Memory (RAM) | 1/5 |
| HDD | 5/5 |
| System Corruption | 2/5 |
| Third-party software | 1/5 |
0x0000004E PFN_LIST_CORRUPT
This error indicates that the system PFN list is corrupted and is caused in most cases by drivers .
[tabs][tab title=”Common Solution”]| Common Reason | Faulty driver installation |
| Common Solution | Remove any recent installed drivers and software and download and install all the latest drivers for your system |
| Ask an expert to examine your dump files, if reinstalling drivers does not help! | |
| Drivers | 5/5 |
| Memory (RAM) | 1/5 |
| HDD | 1/5 |
| System Corruption | 3/5 |
| Third-party software | 1/5 |
0x0000007A KERNEL_DATA_INPAGE_ERROR
A very common Windows problem and is in most cases resulting from bad clusters on the hard drive, in all other cases its damaged hardware (especially RAM)
[tabs][tab title=”Common Solution”]| Common Reason | Bad Clusters |
| Common Solution | Start an elevated command prompt and run CHKDSK . You can do this by entering the following command in the elevated command prompt Chkdsk /f /r. This does require a reboot for System Partitions. |
| Drivers | 1/5 |
| Memory (RAM) | 4/5 |
| HDD | 5/5 |
| System Corruption | 1/5 |
| Third-party software | 1/5 |
0x0000007b INACCESSIBLE_BOOT_DEVICE
This error is always caused on boot up of the operating system, and simply means that Windows could not read the boot files or it was interrupted while reading them, this is most commonly caused by a bad hard disk.
[tabs][tab title=”Common Solution”]| Common Reason | Damaged hard disk |
| Common Solution | Start the system in Safe Mode and run CHKDSK . You can do this by entering the following command in the elevated command prompt Chkdsk /f /r. If the test fails or your system doesn’t let you go into Safe Mode then ask an Expert to help you further or replace the damaged drive. |
| Drivers | 1/5 |
| Memory (RAM) | 2/5 |
| HDD | 5/5 |
| System Corruption | 2/5 |
| Third-party software | 1/5 |
0x0000007E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
The system has encountered an issue in a system thread that the error handler did not catch. [tabs][tab title=”Common Solution”]
| Common Reason | Hard Disk Space |
| Common Solution | Make sure you have enough disk space left on your main hard disk. |
| Drivers | 1/5 |
| Memory (RAM) | 2/5 |
| HDD | 5/5 |
| System Corruption | 2/5 |
| Third-party software | 1/5 |
0x0000008E KERNEL_MODE_EXCEPTION_NOT_HANDLED
The system has encountered an issue in a system thread that the error handler did not catch. [tabs][tab title=”Common Solution”]
| Common Reason | Hard Disk Space |
| Common Solution | Make sure you have enough disk space left on your main hard disk. |
| Drivers | 1/5 |
| Memory (RAM) | 2/5 |
| HDD | 5/5 |
| System Corruption | 2/5 |
| Third-party software | 1/5 |
