List of Windows 10 Blue Screen Error & Stop Codes (BSoD)⚠️
Imagine that suddenly and without warning, while you work on your computer, the screen says goodbye. For a short period of time, you will see a blue screen that contains prominent information but, before you can read it all, the computer will shut down and restart. How will you determine, common blue screen errors in windows 10 that kill your PC?
A Blue Screen of Death, technically called a stop error, occurs when Windows suffers a serious problem and is forced to “stop” completely.
The blue screen of death in Windows 10 (BSOD), also known as stop error or bug check, is a warning about the existence of hardware, software or a faulty driver that forces Windows to shut down.
The blue screen is, therefore, an indication of a critical system error. As a precaution, the computer suddenly shuts down, leaving you surprised or upset in front of the screen. Depending on the version of Windows you have, the blue screen will look different.
What is a blue screen error in windows (BSOD Error code)?
The simple answer: A blue screen error is an alert initiated by the system, upon receiving one of the error messages considered critical. The default solution by the system is to collect all possible information, save it and turn off the equipment to prevent damage.
When an error occurs in our computer caused by a non-recoverable software or hardware problem, Windows shuts down or restarts the computer.
When this occurs, sometimes a blue screen will be displayed with the message “A problem has been found and Windows has been turned off to prevent damage to the computer. “Other times, the message will be displayed after the computer has restarted, indicating that “Windows has recovered from a serious error or an unexpected shutdown.”
These errors are known as blue screen, death screen or STOP errors, they are caused by software problems, ie programs installed or running incompatible with the operating system, drivers added to the system, etc. or hardware errors, caused by physically anchored devices and connected to our computer.
Every time an error occurs and the blue screen is displayed, you will see in a short time, almost instantaneously, a kind of countdown.
It means that a memory dump is being performed or is recovering the information that contains the technical data that Windows is able to get over the problem and save it in a log (text file) that is saved in the Minidump folder, which is in the path:C: \Windows\Minidump.
This allows later to perform an analysis, either directly by the user or by sending it to a network error service provider.
Also Read – Background Intelligent Transfer Service (BITS) Windows 10 Problem [FIXED]
Most Common BSOD – Blue Screen of Death Errors / Stop Codes Windows 10
As you can see, the causes of errors and failures can be considerable. In any case, when such a screen appears, you must first pay attention to the description that appears at the bottom of the message. Here, we have selected the most common Windows 10 stop codes or BSOD errors that occur most often:
KMODE_EXCEPTION_NOT_HANDLED – This causes a blue screen as a result of an error in the kernel process so that you try to run an unknown instruction. It may be associated with incompatibility or equipment malfunction and errors in drivers or system services.
NTFS_FILE_SYSTEM – This error occurs as a result of a failure in the implementation of the system controller ntfs.sys code files. The main reason can be a violation of the integrity of data on disk or in memory, as well as damage to the SCSI or IDE controllers.
DATA_BUS_ERROR – The blue screen of death appears as a result of the occurrence of errors in RAM. The root cause may be incompatible or defective equipment. Moreover, the problem may be related to an incorrect driver as well as the failure of the past on the disc.
IRQL_NOT_LESS_OR_EQUAL – the blue screen of death, in this case, appears as a result of the conversion process kernel mode memory area while the unacceptably high level for it IRQL is used. This error may be due to a malfunction of the drivers, system services or incompatible software, like a software emulator or antivirus software.
PAGE_FAULT_IN_NONPAGED_AREA – the error as a result of the system can not find the necessary data, for example, when Windows finds the necessary information in the paging file, but can not find it . Often the appearance of a blue screen of death, in this case, is due to an equipment malfunction, interruptions in the operation of file systems or failure of a service or software such as an antivirus.
KERNEL_STACK_INPAGE_ERROR – This error occurs as a result of reading errors paging file to physical memory. The main cause of the blue screen of death is a damaged file virtual memory industry, incorrect operation or malfunction of the hard disk controller, insufficient free disk space, incorrect connection of the hard drive conflict disruptions, defects in RAM, virus in the operating system.
Basically, the blue screen of “death” is caused by: software (driver), sometimes in equipment (their failure, conflict or malfunction). In these cases, when the blue screen “death” appears, you must remove newly installed programs and drivers, and disconnect and remove the newly installed equipment.
You must remove the software in Windows Safe Mode. To do this, in the operating system, you should press the F8 key and select Safe Mode.
Causes of the Blue Screen Error Codes
Do you want to know what Are Possible Causes of Windows Blue Screen Error?
BSoD or blue screen of death in Windows may appear for several reasons.
Generally, the cause of the blue screen errors are failures caused by software, fatal errors due to physical failures in RAM or hard disk, make it impossible for Windows to generate any type of report.
In those cases, what is known as the blue screen of death occurs, it consists of a total blockage in which it is only possible to exit by manually resetting from the RESET button or physically shutting down from the power source.
They can sometimes be caused by simple dust particles or other external objects such as garbage, hairs, wires in electrical contacts on the motherboard, which is solved by proper maintenance.
The blue screen conflicts cannot be resolved by reinstalling Windows. The cause will occur them after the re installation. The errors will remain; the most logical thing is to know their origins.
How to identify the source of conflicts that cause errors in the system?
This is a common error known as blue screen, death screen or STOP. Analyze the logs created and saved by the system. How to solve the incompatibility of the files or devices causing these conflicts.
We have all lived a moment of panic, when an unexpected blue screen was displayed on the computer and inevitably starting the system reboot, after receiving the notification due to an error.
Always keeping the hope that Windows starts correctly and reinstallation is not necessary.
Most of the time, nothing happens, but many times, it is only the beginning of a series of conflicts.
A common cause of blue screen of death is overheating equipment (computer components). In this regard, the protection is the cause of the occurrence of BSoD is activated. To do this, you must remove the cover of the system unit and determine the source of overheating.
Very often a source of this type is a central processor, and less often a video card and a power supply. If a malfunction is detected, it (malfunction) should be removed, then the problem of the appearance of BSoD be removed.
Experience and statistics indicate that the biggest cause of blue screen errors is due to device drivers that conflict with the operating system due to bad design, that are not compatible or that are not updated properly.
Unknown device in Windows Device Manager
A large part of them are video card drivers, but also modems, capture cards, printers, USB devices and others.
Starting from a fault in a separate program, ending with a major equipment failure. If you only see BSoD once, it is too early to sound the alarm.
But if the malfunction is regular, it means that there are some problems with the computer. And we must pay attention to the information displayed in the error.
You worked silently on the computer and saw Windows 10 “blue screen of death”. What to do in this case? Do not restart the PC immediately.
Look at the error code. Accordingly, you will understand that “broke”. And you can eliminate the cause of the failure.
If you are reading this article then your computer has understood a mysterious error message, called in narrow circles BSOD and fix Blue Screen of Death in Windows 10 under different scenarios.
BSOD stop message in a Windows OS, which means literally stopped the system for unforeseen reasons. Such errors appear only in the NT operating system family: Windows NT, Windows 2000, Windows XP, Vista and Windows 7 or 8.
Most hardware problems are identified by an 8-digit hexadecimal code, but you can also write concisely; for example, the error code 0x0000000A may also be written as 0xA. Depending on the computer and the specific situation, four additional 8-digit numbers in parentheses may appear.
If this article you are greeted with a message of STOP, for which no explanation (only the number and name), it is likely that this type of BSOD is extremely rare and, as a rule, only be of interest to the programmers. In real life, it is unlikely that an ordinary computer user can join the “blue screen”, so I decided not describe these errors here, but if someone gets a BSOD, write it in the comments or PM: I will add Article .
If you have searched all over the web and cannot solve the problem, the following list of solutions will help. This list will also help eliminate some specific STOP messages such as 0x0A.
In the command line, type the command eventvwr, then analyze the events in the tabs “System” and “Application”. Perhaps there will be additional information to remove his misfortune.
Run the diagnostic equipment supplied by the manufacturer
Make sure the device drivers and BIOS are up to date
If you installed new drivers immediately before the problem appears, try to reverse them.
Open the system unit and make sure all hardware is installed correctly, that nothing has moved and everything is connected.
Make sure all your hardware is on the Hardware Compatibility List. If this is not the case of some components, pay special attention to incompatible hardware code.
Check the newly installed software
Disable caching memory BIOS
NOTE: When the blue screen of death appears, Windows creates a file with detailed information about errors. For this purpose, the operating system needs a workspace equal to the amount of physical RAM. If you make the size of the paging file is smaller than the size of physical memory, an informational message indicating that your system can not create a file with debugging information in the case of a BSOD appears.
Also Read – How To Fix/Disable Driver Signature Enforcement Windows 10
Blue Screen Error Codes List
| STOP Code |
Blue Screen Error |
|---|---|
| 0x00000001 | APC_INDEX_MISMATCH |
| 0x00000002 | DEVICE_QUEUE_NOT_BUSY |
| 0x00000003 | INVALID_AFFINITY_SET |
| 0x00000004 | INVALID_DATA_ACCESS_TRAP |
| 0x00000005 | INVALID_PROCESS_ATTACH_ATTEMPT |
| 0x00000006 | INVALID_PROCESS_DETACH_ATTEMPT |
| 0x00000007 | INVALID_SOFTWARE_INTERRUPT |
| 0x00000008 | IRQL_NOT_DISPATCH_LEVEL |
| 0x00000009 | IRQL_NOT_GREATER_OR_EQUAL |
| 0x0000000A | IRQL_NOT_LESS_OR_EQUAL |
| 0x0000000B | NO_EXCEPTION_HANDLING_SUPPORT |
| 0x0000000C | MAXIMUM_WAIT_OBJECTS_EXCEEDED |
| 0x0000000D | MUTEX_LEVEL_NUMBER_VIOLATION |
| 0x0000000E | NO_USER_MODE_CONTEXT |
| 0x0000000F | SPIN_LOCK_ALREADY_OWNED |
| 0x00000010 | SPIN_LOCK_NOT_OWNED |
| 0x00000011 | THREAD_NOT_MUTEX_OWNER |
| 0x00000012 | TRAP_CAUSE_UNKNOWN |
| 0x00000013 | EMPTY_THREAD_REAPER_LIST |
| 0x00000014 | CREATE_DELETE_LOCK_NOT_LOCKED |
| 0x00000015 | LAST_CHANCE_CALLED_FROM_KMODE |
| 0x00000016 | CID_HANDLE_CREATION |
| 0x00000017 | CID_HANDLE_DELETION |
| 0x00000018 | REFERENCE_BY_POINTER |
| 0x00000019 | BAD_POOL_HEADER |
| 0x0000001A | MEMORY_MANAGEMENT |
| 0x0000001B | PFN_SHARE_COUNT |
| 0x0000001C | PFN_REFERENCE_COUNT |
| 0x0000001D | NO_SPIN_LOCK_AVAILABLE |
| 0x0000001E | KMODE_EXCEPTION_NOT_HANDLED |
| 0x0000001F | SHARED_RESOURCE_CONV_ERROR |
| 0x00000020 | KERNEL_APC_PENDING_DURING_EXIT |
| 0x00000021 | QUOTA_UNDERFLOW |
| 0x00000022 | FILE_SYSTEM |
| 0x00000023 | FAT_FILE_SYSTEM |
| 0x00000024 | NTFS_FILE_SYSTEM |
| 0x00000025 | NPFS_FILE_SYSTEM |
| 0x00000026 | CDFS_FILE_SYSTEM |
| 0x00000027 | RDR_FILE_SYSTEM |
| 0x00000028 | CORRUPT_ACCESS_TOKEN |
| 0x00000029 | SECURITY_SYSTEM |
| 0x0000002A | INCONSISTENT_IRP |
| 0x0000002B | PANIC_STACK_SWITCH |
| 0x0000002C | PORT_DRIVER_INTERNAL |
| 0x0000002D | SCSI_DISK_DRIVER_INTERNAL |
| 0x0000002E | DATA_BUS_ERROR |
| 0x0000002F | INSTRUCTION_BUS_ERROR |
| 0x00000030 | SET_OF_INVALID_CONTEXT |
| 0x00000031 | PHASE0_INITIALIZATION_FAILED |
| 0x00000032 | PHASE1_INITIALIZATION_FAILED |
| 0x00000033 | UNEXPECTED_INITIALIZATION_CALL |
| 0x00000034 | CACHE_MANAGER |
| 0x00000035 | NO_MORE_IRP_STACK_LOCATIONS |
| 0x00000036 | DEVICE_REFERENCE_COUNT_NOT_ZERO |
| 0x00000037 | FLOPPY_INTERNAL_ERROR |
| 0x00000038 | SERIAL_DRIVER_INTERNAL |
| 0x00000039 | SYSTEM_EXIT_OWNED_MUTEX |
| 0x0000003A | SYSTEM_UNWIND_PREVIOUS_USER |
| 0x0000003B | SYSTEM_SERVICE_EXCEPTION |
| 0x0000003C | INTERRUPT_UNWIND_ATTEMPTED |
| 0x0000003D | INTERRUPT_EXCEPTION_NOT_HANDLED |
| 0x0000003E | MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED |
| 0x0000003F | NO_MORE_SYSTEM_PTES |
| 0x00000040 | TARGET_MDL_TOO_SMALL |
| 0x00000041 | MUST_SUCCEED_POOL_EMPTY |
| 0x00000042 | ATDISK_DRIVER_INTERNAL |
| 0x00000043 | NO_SUCH_PARTITION |
| 0x00000044 | MULTIPLE_IRP_COMPLETE_REQUESTS |
| 0x00000045 | INSUFFICIENT_SYSTEM_MAP_REGS |
| 0x00000046 | DEREF_UNKNOWN_LOGON_SESSION |
| 0x00000047 | REF_UNKNOWN_LOGON_SESSION |
| 0x00000048 | CANCEL_STATE_IN_COMPLETED_IRP |
| 0x00000049 | PAGE_FAULT_WITH_INTERRUPTS_OFF |
| 0x0000004A | IRQL_GT_ZERO_AT_SYSTEM_SERVICE |
| 0x0000004B | STREAMS_INTERNAL_ERROR |
| 0x0000004C | FATAL_UNHANDLED_HARD_ERROR |
| 0x0000004D | NO_PAGES_AVAILABLE |
| 0x0000004E | PFN_LIST_CORRUPT |
| 0x0000004F | NDIS_INTERNAL_ERROR |
| 0x00000050 | PAGE_FAULT_IN_NONPAGED_AREA |
| 0x00000051 | REGISTRY_ERROR |
| 0x00000052 | MAILSLOT_FILE_SYSTEM |
| 0x00000053 | NO_BOOT_DEVICE |
| 0x00000054 | LM_SERVER_INTERNAL_ERROR |
| 0x00000055 | DATA_COHERENCY_EXCEPTION |
| 0x00000056 | INSTRUCTION_COHERENCY_EXCEPTION |
| 0x00000057 | XNS_INTERNAL_ERROR |
| 0x00000058 | FTDISK_INTERNAL_ERROR |
| 0x00000059 | PINBALL_FILE_SYSTEM |
| 0x0000005A | CRITICAL_SERVICE_FAILED |
| 0x0000005B | SET_ENV_VAR_FAILED |
| 0x0000005C | HAL_INITIALIZATION_FAILED |
| 0x0000005D | UNSUPPORTED_PROCESSOR |
| 0x0000005E | OBJECT_INITIALIZATION_FAILED |
| 0x0000005F | SECURITY_INITIALIZATION_FAILED |
| 0x00000060 | PROCESS_INITIALIZATION_FAILED |
| 0x00000061 | HAL1_INITIALIZATION_FAILED |
| 0x00000062 | OBJECT1_INITIALIZATION_FAILED |
| 0x00000063 | SECURITY1_INITIALIZATION_FAILED |
| 0x00000064 | SYMBOLIC_INITIALIZATION_FAILED |
| 0x00000065 | MEMORY1_INITIALIZATION_FAILED |
| 0x00000066 | CACHE_INITIALIZATION_FAILED |
| 0x00000067 | CONFIG_INITIALIZATION_FAILED |
| 0x00000068 | FILE_INITIALIZATION_FAILED |
| 0x00000069 | IO1_INITIALIZATION_FAILED |
| 0x0000006A | LPC_INITIALIZATION_FAILED |
| 0x0000006B | PROCESS1_INITIALIZATION_FAILED |
| 0x0000006C | REFMON_INITIALIZATION_FAILED |
| 0x0000006D | SESSION1_INITIALIZATION_FAILED |
| 0x0000006E | SESSION2_INITIALIZATION_FAILED |
| 0x0000006F | SESSION3_INITIALIZATION_FAILED |
| 0x00000070 | SESSION4_INITIALIZATION_FAILED |
| 0x00000071 | SESSION5_INITIALIZATION_FAILED |
| 0x00000072 | ASSIGN_DRIVE_LETTERS_FAILED |
| 0x00000073 | CONFIG_LIST_FAILED |
| 0x00000074 | BAD_SYSTEM_CONFIG_INFO |
| 0x00000075 | CANNOT_WRITE_CONFIGURATION |
| 0x00000076 | PROCESS_HAS_LOCKED_PAGES |
| 0x00000077 | KERNEL_STACK_INPAGE_ERROR |
| 0x00000078 | PHASE0_EXCEPTION |
| 0x00000079 | MISMATCHED_HAL |
| 0x0000007A | KERNEL_DATA_INPAGE_ERROR |
| 0x0000007B | INACCESSIBLE_BOOT_DEVICE |
| 0x0000007C | BUGCODE_NDIS_DRIVER |
| 0x0000007D | INSTALL_MORE_MEMORY |
| 0x0000007E | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED |
| 0x0000007F | UNEXPECTED_KERNEL_MODE_TRAP |
| 0x00000080 | NMI_HARDWARE_FAILURE |
| 0x00000081 | SPIN_LOCK_INIT_FAILURE |
| 0x00000082 | DFS_FILE_SYSTEM |
| 0x00000083 | OFS_FILE_SYSTEM |
| 0x00000084 | RECOM_DRIVER |
| 0x00000085 | SETUP_FAILURE |
| 0x0000008B | MBR_CHECKSUM_MISMATCH |
| 0x0000008E | KERNEL_MODE_EXCEPTION_NOT_HANDLED |
| 0x0000008F | PP0_INITIALIZATION_FAILED |
| 0x00000090 | PP1_INITIALIZATION_FAILED |
| 0x00000091 | WIN32K_INIT_OR_RIT_FAILURE |
| 0x00000092 | UP_DRIVER_ON_MP_SYSTEM |
| 0x00000093 | INVALID_KERNEL_HANDLE |
| 0x00000094 | KERNEL_STACK_LOCKED_AT_EXIT |
| 0x00000095 | PNP_INTERNAL_ERROR |
| 0x00000096 | INVALID_WORK_QUEUE_ITEM |
| 0x00000097 | BOUND_IMAGE_UNSUPPORTED |
| 0x00000098 | END_OF_NT_EVALUATION_PERIOD |
| 0x00000099 | INVALID_REGION_OR_SEGMENT |
| 0x0000009A | SYSTEM_LICENSE_VIOLATION |
| 0x0000009B | UDFS_FILE_SYSTEM |
| 0x0000009C | MACHINE_CHECK_EXCEPTION |
| 0x0000009E | USER_MODE_HEALTH_MONITOR |
| 0x0000009F | DRIVER_POWER_STATE_FAILURE |
| 0x000000A0 | INTERNAL_POWER_ERROR |
| 0x000000A1 | PCI_BUS_DRIVER_INTERNAL |
| 0x000000A2 | MEMORY_IMAGE_CORRUPT |
| 0x000000A3 | ACPI_DRIVER_INTERNAL |
| 0x000000A4 | CNSS_FILE_SYSTEM_FILTER |
| 0x000000A5 | ACPI_BIOS_ERROR |
| 0x000000A7 | BAD_EXHANDLE |
| 0x000000AB | SESSION_HAS_VALID_POOL_ON_EXIT |
| 0x000000AC | HAL_MEMORY_ALLOCATION |
| 0x000000AD | VIDEO_DRIVER_DEBUG_REPORT_REQUEST |
| 0x000000B4 | VIDEO_DRIVER_INIT_FAILURE |
| 0x000000B8 | ATTEMPTED_SWITCH_FROM_DPC |
| 0x000000B9 | CHIPSET_DETECTED_ERROR |
| 0x000000BA | SESSION_HAS_VALID_VIEWS_ON_EXIT |
| 0x000000BB | NETWORK_BOOT_INITIALIZATION_FAILED |
| 0x000000BC | NETWORK_BOOT_DUPLICATE_ADDRESS |
| 0x000000BE | ATTEMPTED_WRITE_TO_READONLY_MEMORY |
| 0x000000BF | MUTEX_ALREADY_OWNED |
| 0x000000C1 | SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION |
| 0x000000C2 | BAD_POOL_CALLER |
| 0x000000C4 | DRIVER_VERIFIER_DETECTED_VIOLATION |
| 0x000000C5 | DRIVER_CORRUPTED_EXPOOL |
| 0x000000C6 | DRIVER_CAUGHT_MODIFYING_FREED_POOL |
| 0x000000C7 | TIMER_OR_DPC_INVALID |
| 0x000000C8 | IRQL_UNEXPECTED_VALUE |
| 0x000000C9 | DRIVER_VERIFIER_IOMANAGER_VIOLATION |
| 0x000000CA | PNP_DETECTED_FATAL_ERROR |
| 0x000000CB | DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS |
| 0x000000CC | PAGE_FAULT_IN_FREED_SPECIAL_POOL |
| 0x000000CD | PAGE_FAULT_BEYOND_END_OF_ALLOCATION |
| 0x000000CE | DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS |
| 0x000000CF | TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE |
| 0x000000D0 | DRIVER_CORRUPTED_MMPOOL |
| 0x000000D1 | DRIVER_IRQL_NOT_LESS_OR_EQUAL |
| 0x000000D2 | BUGCODE_ID_DRIVER |
| 0x000000D3 | DRIVER_PORTION_MUST_BE_NONPAGED |
| 0x000000D4 | SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD |
| 0x000000D5 | DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL |
| 0x000000D6 | DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION |
| 0x000000D7 | DRIVER_UNMAPPING_INVALID_VIEW |
| 0x000000D8 | DRIVER_USED_EXCESSIVE_PTES |
| 0x000000D9 | LOCKED_PAGES_TRACKER_CORRUPTION |
| 0x000000DA | SYSTEM_PTE_MISUSE |
| 0x000000DB | DRIVER_CORRUPTED_SYSPTES |
| 0x000000DC | DRIVER_INVALID_STACK_ACCESS |
| 0x000000DE | POOL_CORRUPTION_IN_FILE_AREA |
| 0x000000DF | IMPERSONATING_WORKER_THREAD |
| 0x000000E0 | ACPI_BIOS_FATAL_ERROR |
| 0x000000E1 | WORKER_THREAD_RETURNED_AT_BAD_IRQL |
| 0x000000E2 | MANUALLY_INITIATED_CRASH |
| 0x000000E3 | RESOURCE_NOT_OWNED |
| 0x000000E4 | WORKER_INVALID |
| 0x000000E6 | DRIVER_VERIFIER_DMA_VIOLATION |
| 0x000000E7 | INVALID_FLOATING_POINT_STATE |
| 0x000000E8 | INVALID_CANCEL_OF_FILE_OPEN |
| 0x000000E9 | ACTIVE_EX_WORKER_THREAD_TERMINATION |
| 0x000000EA | THREAD_STUCK_IN_DEVICE_DRIVER |
| 0x000000EB | DIRTY_MAPPED_PAGES_CONGESTION |
| 0x000000EC | SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT |
| 0x000000ED | UNMOUNTABLE_BOOT_VOLUME |
| 0x000000EF | CRITICAL_PROCESS_DIED |
| 0x000000F1 | SCSI_VERIFIER_DETECTED_VIOLATION |
| 0x000000F3 | DISORDERLY_SHUTDOWN |
| 0x000000F4 | CRITICAL_OBJECT_TERMINATION |
| 0x000000F5 | FLTMGR_FILE_SYSTEM |
| 0x000000F6 | PCI_VERIFIER_DETECTED_VIOLATION |
| 0x000000F7 | DRIVER_OVERRAN_STACK_BUFFER |
| 0x000000F8 | RAMDISK_BOOT_INITIALIZATION_FAILED |
| 0x000000F9 | DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN |
| 0x000000FA | HTTP_DRIVER_CORRUPTED |
| 0x000000FC | ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY |
| 0x000000FD | DIRTY_NOWRITE_PAGES_CONGESTION |
| 0x000000FE | BUGCODE_USB_DRIVER |
| 0x000000FF | RESERVE_QUEUE_OVERFLOW |
| 0x00000100 | LOADER_BLOCK_MISMATCH |
| 0x00000101 | CLOCK_WATCHDOG_TIMEOUT |
| 0x00000103 | MUP_FILE_SYSTEM |
| 0x00000104 | AGP_INVALID_ACCESS |
| 0x00000105 | AGP_GART_CORRUPTION |
| 0x00000106 | AGP_ILLEGALLY_REPROGRAMMED |
| 0x00000108 | THIRD_PARTY_FILE_SYSTEM_FAILURE |
| 0x00000109 | CRITICAL_STRUCTURE_CORRUPTION |
| 0x0000010A | APP_TAGGING_INITIALIZATION_FAILED |
| 0x0000010C | FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION |
| 0x0000010D | WDF_VIOLATION |
| 0x0000010E | VIDEO_MEMORY_MANAGEMENT_INTERNAL |
| 0x0000010F | RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED |
| 0x00000111 | RECURSIVE_NMI |
| 0x00000112 | MSRPC_STATE_VIOLATION |
| 0x00000113 | VIDEO_DXGKRNL_FATAL_ERROR |
| 0x00000114 | VIDEO_SHADOW_DRIVER_FATAL_ERROR |
| 0x00000115 | AGP_INTERNAL |
| 0x00000116 | VIDEO_TDR_ ERROR |
| 0x00000117 | VIDEO_TDR_TIMEOUT_DETECTED |
| 0x00000119 | VIDEO_SCHEDULER_INTERNAL_ERROR |
| 0x0000011A | EM_INITIALIZATION_FAILURE |
| 0x0000011B | DRIVER_RETURNED_HOLDING_CANCEL_LOCK |
| 0x0000011C | ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE |
| 0x0000011D | EVENT_TRACING_FATAL_ERROR |
| 0x00000121 | DRIVER_VIOLATION |
| 0x00000122 | WHEA_INTERNAL_ERROR |
| 0x00000124 | WHEA_UNCORRECTABLE_ERROR |
| 0x00000127 | PAGE_NOT_ZERO |
| 0x0000012B | FAULTY_HARDWARE_CORRUPTED_PAGE |
| 0x0000012C | EXFAT_FILE_SYSTEM |
| 0x00000133 | DPC_WATCHDOG_VIOLATION |
| 0x00000138 | GPIO_CONTROLLER_DRIVER_ERROR |
| 0x00000139 | KERNEL_SECURITY_CHECK_FAILURE |
| 0x00000144 | BUGCODE_USB3_DRIVER |
| 0x0000014B | SOC_SUBSYSTEM_FAILURE |
| 0x1000007E | SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M |
| 0x1000007F | UNEXPECTED_KERNEL_MODE_TRAP_M |
| 0x1000008E | KERNEL_MODE_EXCEPTION_NOT_HANDLED_M |
| 0x100000EA | THREAD_STUCK_IN_DEVICE_DRIVER_M |
| 0xC0000218 | STATUS_CANNOT_LOAD_REGISTRY_FILE |
| 0xC000021A | STATUS_SYSTEM_PROCESS_TERMINATED |
| 0xC0000221 | STATUS_IMAGE_CHECKSUM_MISMATCH |
| 0xDEADDEAD | MANUALLY_INITIATED_CRA |
⚠️ 0x00000001 Error: APC_INDEX_MISMATCH
APC_INDEX_MISMATCH – internal kernel error. It occurs at the completion of the system call. Error 0x00000001 occurs when the file system driver has a mismatched sequence of system calls to start or finish a protected or critical section. For example, each call must be KeEnterCriticalRegion corresponding call KeLeaveCriticalRegion.
⚠️ 0x00000002 Error: DEVICE_QUEUE_NOT_BUSY
A rare error may be caused, both by hardware and software. The highest probability of an error is a failure of the printer driver or an error signature key. Any operating system family of Windows NT from Microsoft can cause Stop 0x00000002. Including Windows 8, Windows 7, Windows Vista, Windows XP and Windows 2000.
As with any other error blue screen of death, you cannot complete the operation because the system immediately restarts or if it is linked with the settings, restart the user expects.
⚠️ 0x00000003 Error: INVALID_AFFINITY_SET
Most likely this error can be seen when installing the printer. Any operating system can cause Stop 0x00000003. it was present Windows 2000 and it is fixed in the latest updates of windows.
⚠️ 0x00000004 Error: INVALID_DATA_ACCESS_TRAP
This problem occurs in Windows XP SP2 and Windows Server 2003 when you install some antivirus and firewall programs. To resolve this problem in Windows XP SP2, you must download and install the updates. It also indicates an unacceptable interruption of access to the data.
This error occurs if your operating system drivers are outdated.
⚠️ 0x00000005 Error: INVALID_PROCESS_ATTACH_ATTEMPT
This error indicates that the flow has been attached to the process in a situation where it is not allowed. For example, this error could occur if caused KeAttachProcess, when the flow has been attached to the process (which is not allowed), or if the flow is returned from the certain function calls in the attached state (that is not valid).
It occurs when a coding error in the Http.sys file, which in turn causes damage to the stack.
⚠️ 0x00000006 Error: INVALID_PROCESS_DETACH_ATTEMPT
A rare error indicates a problem with a mutex or APC. BSoD may occur if Windows incorrectly queues function asynchronous procedure call (APC) nucleus, also known as a completion routine.
NOTE – Ottawa IT Support is to make sure you never has downtown, keep your IT business running in safew hands.
⚠️ 0x00000007 Error: INVALID_SOFTWARE_INTERRUPT
It indicates the level is not within the software range. In the present version of windows, they tried to fix it but despite all this, it still exists under the latest Windows. Usually, it occurs due to a hardware controller or a damaged or defective/incompatible software. Technically, this error means that the kernel mode process or driver attempted to access a memory location which is not allowed.
⚠️ 0x00000008 Error: IRQL_NOT_DISPATCH_LEVEL
The blue screen of death 0x00000008 indicates an attempt to remove the device at a non-dispatch level.
⚠️0x00000009 Error: IRQL_NOT_GREATER_OR_EQUAL
IRQL_NOT_GREATER_OR_EQUAL error occurs when memory access occurs at too high IRQL. Typically, this error indicates IRQL value is less than desired when a driver uses an incorrect memory address. Other possible causes of this error include an incompatible device driver, a general hardware problem, or incompatible software.
⚠️ 0x0000000A Error: IRQL_NOT_LESS_OR_EQUAL
Stop 0x0000000A occurs when entering sleep mode. This occurs because Diskdump.sys driver incorrectly sets the I/O size to 0. When the system enters hibernation mode, Diskdump.sys driver is responsible for writing the memory content in the Hiberfil.sys file. If the storage device that contains Hiberfil.sys file busy, when the device receives an I/O request from Diskdump.sys driver, it tries to send the I/O request later.
However, Diskdump.sys driver incorrectly sets the I/O size to 0 when resends the request. Therefore, the system accesses the invalid memory address and you get an error message.
⚠️ 0x0000000B Error: NO_EXCEPTION_HANDLING_SUPPORT
A blue screen of 0x0000000B indicates that exception handling was not supported.
⚠️ 0x0000000C Error: MAXIMUM_WAIT_OBJECTS_EXCEEDED
Error MAXIMUM_WAIT_OBJECTS_EXCEEDED exist due to improper use of KeWaitForMultipleObjects or FsRtlCancellableWaitForMultipleObjects. The caller may pass a pointer to the buffer parameter WaitBlockArray the routine. The system will use this buffer to track waiting objects.
If the buffer is provided, the count parameter may not exceed MAXIMUM_WAIT_OBJECTS. If the buffer is not provided, the count parameter may exceed THREAD_WAIT_OBJECTS. If the count value exceeds the allowable value, this error occurs.
⚠️ 0x0000000D Error: MUTEX_LEVEL_NUMBER_VIOLATION
It indicates an attempt to acquire the mutex at a lower level. This often happened after CPU overhead or lack of RAM, so make sure that your system does not have any virus and check your memories via test utilities.
⚠️ 0x0000000E Error: NO_USER_MODE_CONTEXT
When the computer connects and then disconnects from a remote access session to your computer with Microsoft Windows 2000 operating system, the computer may unexpectedly stop responding, and you may receive BSoD NO_USER_MODE_CONTEXT.
⚠️ 0x0000000F Error: SPIN_LOCK_ALREADY_OWNED
Typically, this error is caused by a recursive query on the spin-lock. For example, when spin-lock was obtained, stream and then the same thread calls a function that is also trying to get a spin-lock.
A second attempt to get a spin-lock is not locked, because it would lead to a deadlock. If calls are made by more than one processor, one processor will be blocked until the other processor releases the lock.
This error can also occur without explicit recursion when all flows and all spin-locks are assigned IRQL. IRQL spin-lock is always greater than or equal to the DPC, but this is not taken into account for the flows.
However, IRQL stream which comprises spin-lock must maintain greater than or equal to the value IRQL spin-lock. When reducing the flow IRQL below IRQL spin-lock, which stream contains, allows another thread executed by the processor. This new stream can try to get the same spin-lock.
Make sure you do not get the lock recursively. And, for streams that contain spin-lock, make sure that you do not reduce the flow IRQL to the level below IRQL spin-lock, which it contains.
⚠️ 0x00000010 Error: SPIN_LOCK_NOT_OWNED
0x00000010 indicates an attempt to free his own spin-lock. It may be caused by an improperly installed device, a device driver that conflicts with Windows, or an obsolete device driver. You can visit FixBit which provides the latest version of drivers. It also offers auto driver update service so that you can have a hassle-free installation. If a file name is specified, update the target device. If this does not fix the problem, uninstall all recently-installed devices cleanly, reinstall them with FixBit, and update your Windows.
⚠️ 0x00000011 Error: THREAD_NOT_MUTEX_OWNER
0x00000011 indicates an attempt to liberate the improper flow of the mutex. Uninstalling the latest installed software to find the problem. Check and verify that your newly added hardware is compatible with your Windows, and download the latest drivers by visiting the FixBit site.
⚠️ 0x00000012 Error: TRAP_CAUSE_UNKNOWN
0x00000012 indicates that there was an unknown exception. This error usually occurs on computers running Windows 2000 with a Sound Blaster and sound card integrated software Live for that sound. The problem is solved by removing the software for this zvukovuhi. It is a rare error of TRAP_CAUSE_UNKNOWN parameters which includes:
The sudden interruption
The unknown exception of floating-point
⚠️ 0x00000013 Error: EMPTY_THREAD_REAPER_LIST
0x00000013 indicates that the stream list is damaged. Uninstall the recently installed software and Make sure your newly added hardware is compatible with your Windows, and download the latest drivers available directly from your hardware manufacturer’s site.
⚠️ 0x00000014 Error: CREATE_DELETE_LOCK_NOT_LOCKED
0x00000014 is extremely rare. This error is caused by wrong hardware or inappropriate device driver issues.
⚠️ 0x00000015 Error: LAST_CHANCE_CALLED_FROM_KMODE
0x00000015 indicates that the latter is a random exception service was launched in kernel mode. This error means that the installed device is not ready and you don’t have a vital service running on your computer.
⚠️ 0x00000016 Error: CID_HANDLE_CREATION
0x00000016 indicates that a failure occurred when creating a descriptor to represent a client ID. This error can occur if you uninstall a browser so make sure you uninstall it completely through the utility to avoid this error.
⚠️ 0x00000017 Error: CID_HANDLE_DELETION
This error indicates that a failure occurred when deleting the descriptor to represent a client ID. This error code is commonly used to identify the error caused by the hardware driver vendors. The warning messages may slow down PC performance and system freezes startup/shutdown which can be quite annoying if not timely fixed.
⚠️ 0x00000018 Error: REFERENCE_BY_POINTER
The reference count for the object is invalid for the current state of the object. Every time a driver uses a pointer to an object, it calls the subroutine core to increase the object’s reference count by one.
When the driver terminates with a pointer, the driver calls another subroutine core to reduce the reference counter by one.
Drivers must call subroutines that increase (link), and decrease (dereferencing) reference count. This error occurs when non-compliance of the values of the reference count of the object.
As a rule, the inconsistency caused by the driver, which reduces the reference count of an object too many times by performing additional challenges that dereference the object. 0x00000018 error can occur at zero reference count, while still have open handles to the object.
⚠️ 0x00000019 Error: BAD_POOL_HEADER
The pool here is the address space of memory. This error particularly indicates if a computer crashes and suddenly loses contact with one of the memory card or one of the hard drives where there is a paging pool file.
⚠️ 0x0000001A Error: MEMORY_MANAGEMENT
This error is usually related to the NTFS file system. Also, if this occurs during the installation of Windows, you should check the features of the system components, including the amount of RAM and free space on your hard disk.
⚠️ 0x0000001B Error: PFN_SHARE_COUNT
0x0000001B indicates that the PFN database memory management element is damaged count the number of users. It’s a rare error related to your RAM.
⚠️ 0x0000001C Error: PFN_REFERENCE_COUNT
0x0000001C indicates that memory management PFN database element is a corrupt reference count. It means your newly added hardware is not compatible with your Windows,
⚠️ 0x0000001D Error: NO_SPIN_LOCK_AVAILABLE
0x0000001D indicates that all the spin locks are not available. A rare error in Windows XP error which occurs when you change the IPX frame type of the current network connection is automatically determined on any other type.
⚠️ 0x0000001E Error: KMODE_EXCEPTION_NOT_HANDLED
The Windows kernel detected a prohibited transaction or unknown processor instruction. The 0x1E error can be caused by a faulty memory and access violation reasons similar to those that cause Stop 0xA error.
⚠️ 0x0000001F Error: SHARED_RESOURCE_CONV_ERROR
0x0000001F indicates conversion problem shared the resource. You can uninstall any newly installed hardware and software to find the problem. Make sure your new hardware is compatible with your Windows, and download the latest drivers by using FixBit site.
⚠️ 0x00000020 Error: KERNEL_APC_PENDING_DURING_EXIT
It indicates that an asynchronous procedure call (APC) was in standby mode upon completion of the thread execution. A key parameter – the number of outages for APC stream. If the number is non-zero, then it will indicate the source of the problem.
A number of disconnections APC decreases each time when the driver calls KeEnterCriticalRegion, FsRtlEnterFileSystem, or when the mutex. The number of APC trips is gradually increased whenever the driver calls KeLeaveCriticalRegion, KeReleaseMutex, or FsRtlExitFileSystem.
⚠️ 0x00000021 Error: QUOTA_UNDERFLOW
This error indicates that the quota was returned to the process, but the process did not use all of the value of the quota. It means the remaining amount of the quota has not been returned.
⚠️ 0x00000022 Error: ARCHIVO_SISTEMA
A blue screen of 0x00000022 indicates a file system problem. A possible reason is the depletion of the non-swapped memory pool. During the indexing process, if the amount of available pool of non-pumped memory is very small, another driver requiring a pool of non-pumped memory may also trigger this error.
⚠️ 0x00000023 Error: FAT_FILE_SYSTEM
The problem occurs when reading or writing to the FAT16 or FAT32 file system. The cause of the error can be physical damage to the storage device. Other common reasons are: hard drive fragmentation, problems with some software products for RAID arrays, some antivirus programs may also cause this error.
To solve the problem, we run ScanDisk ChkDsk or as a first step; then we disable antivirus software, firewall and backup.
Also, check the properties of FASTFAT.SYS file, make sure they match the current operating system and service pack version. You must also update the drivers for all storage devices and copy the data to the current version.
⚠️ 0x00000024 Error: NTFS_FILE_SYSTEM
The problem occurs when reading or writing to the NTFS file system. The cause of the error can be physical damage to the storage device. Other common reasons are: hard drive fragmentation, problems with some software products for RAID arrays, some antivirus programs may also cause this error.
To solve the problem, we run ScanDisk ChkDsk or as a first step; then we disable antivirus software, firewall and backup.
Also, check the properties of FASTFAT.SYS file, make sure they match the current operating system and service pack version. You must also update the drivers with FixBit for all storage devices and copy the data to the current version.
⚠️ 0x00000025 Error: NPFS_FILE_SYSTEM
One of the possible causes of a blue screen 0x00000025 – damage to the hard disk. File system corruption or bad blocks (sectors) on the disk can cause this error.
Damaged SCSI and IDE drivers can also have a negative impact on the ability of the system to read and write to the hard disk, thus causing the error.
Another possible reason – the depletion of the pool is not paged memory. During the indexing process, if the amount of available paged pool memory is not very small, the other driver does not require the pool paged memory can also trigger this error.
⚠️ 0x00000026 Error: CDFS_FILE_SYSTEM
One of the possible causes of BSoD – damage to the hard disk. Damage to the CDFS file system or bad blocks (sectors) on the disk can cause this error. Damaged SCSI and IDE drivers can also have a negative impact on the ability of the system to read and write to the hard disk, thus causing the error. Another possible reason – the depletion of the pool is not paged memory.
During the indexing process, if the amount of available paged pool memory is not very small, the other driver does not require the pool paged memory can also trigger this error.
⚠️ 0x00000027 Error: RDR_FILE_SYSTEM
BSoD caused by the depletion of the pool is not paged memory. During the indexing process, if the amount of available paged pool memory is not very small, the other driver does not require the pool paged memory, can trigger this error.
This pretty rare error in the system running Windows 2000. Insufficient RAM may be one reason and add an additional bar should solve this problem.
⚠️ 0x00000028 Error: CORRUPT_ACCESS_TOKEN
During the indexing process, 0x00000028 indicates that the security system has detected an invalid token.
⚠️ 0x00000029 Error: SECURITY_SYSTEM
It indicates an internal security system problem.
⚠️ 0x0000002A Error: INCONSISTENT_IRP
BSoD usually occurs when some IRP field was inconsistent with the state of the IRP. An example can be completed IRP, remaining in a device driver queue. This error is not currently used, but there is for debugging purposes.
⚠️ 0x0000002B Error: PANIC_STACK_SWITCH
This BSoD error could be caused by a kernel-mode driver that uses too much stack space or data corruption in the kernel.
⚠️ 0x0000002C Error: PORT_DRIVER_INTERNAL
It indicates an internal error in the port driver.
⚠️ 0x0000002D Error: SCSI_DISK_DRIVER_INTERNAL
0x0000002D indicates an internal error in a SCSI hard disk and driver.
⚠️ 0x0000002F Error: INSTRUCTION_BUS_ERROR
This BSoD 0x0000002F is almost always caused by a problem of hardware – configuration problem, a hardware defect or incompatibility.
The most common problems of hardware, that can cause this error is faulty RAM, the cache memory RAM error level 2 (L2), or video memory errors. Hard disk corruption can also cause this error.
This error can also be caused when a device driver tries to access an address in 0x8xxxxxxx range that does not exist (in other words, that does not have a physical address mapping).
⚠️ 0x00000030 Error: SET_OF_INVALID_CONTEXT
Blue Screen of 0x0000002F indicates an error instruction bus.
⚠️ 0x00000031 Error: PHASE0_INITIALIZATION_FAILED
BSoD occurs when some routine attempts to set the pointer to the top of the trap stack frame in a value less than the current value of the stack pointer.
⚠️ 0x00000032 Error: PHASE1_INITIALIZATION_FAILED
At a very early stage of initialization, the system failed. An error caused by device drivers.
⚠️ 0x00000033 Error: UNEXPECTED_INITIALIZATION_CALL
0x00000033 indicates that during the initialization phase has stopped working Windows 2000. Most likely a problem with the device driver.
⚠️ 0x00000034 Error: CACHE_MANAGER
Depletion paged memory pool does not cause the error. During the indexing process, if the amount of available paged pool memory is not very small, the other driver does not require the pool paged memory, can trigger this error.
⚠️ 0x00000035 Error: NO_MORE_IRP_STACK_LOCATIONS
he emergence of high-level attempt Bsod caused the driver to call the lower-level driver through the interface IoCallDriver filled with the stack area. Because of what the lower level driver has no access to its parameters.
This is a fatal mistake, as a high-level driver filled settings for the low-level driver (as required), while in the stack is no space for low-level driver. Also, an error may indicate memory corruption.
This error indicates a problem with the controller also may indicate that the RAM is faulty.
⚠️ 0x00000036 Error: DEVICE_REFERENCE_COUNT_NOT_ZERO
A device driver attempted to remove one of its objects “unit” systems, but the reference count for the object is non-zero. This is a mistake of the device driver request.
⚠️ 0x00000037 Error: FLOPPY_INTERNAL_ERROR
0x00000037 indicates an internal error floppy disk driver.
⚠️ 0x00000038 Error: SERIAL_DRIVER_INTERNAL
0x00000038 indicates an internal serial port driver error.
⚠️ 0x00000039 Error: SYSTEM_EXIT_OWNED_MUTEX
0x00000038 indicates an internal serial port driver error.
⚠️ 0x0000003A Error: SYSTEM_UNWIND_PREVIOUS_USER
A pretty rare error, the blue screen of death 0x00000039 indicates that an attempt has been made to exit the system service when one or more mutexes are accessing it which means that an attempt has been made to return to user mode through the System Service Manager.
⚠️ 0x0000003B Error: SYSTEM_SERVICE_EXCEPTION
BSoD 0x0000003B is caused by excessive use of the pool of swappable memory and may appear due to overlapping user-mode graphics drivers and when transferring incorrect data to the kernel code.
⚠️ 0x0000003C Error: INTERRUPT_UNWIND_ATTEMPTED
It is a Windows 2000 test mode error.
⚠️ 0x0000003D Error: INTERRUPT_EXCEPTION_NOT_HANDLED
0x0000003D blue screen is a test error in Windows 2000.
⚠️ 0x0000003E Error: MULTIPROCESSOR_CONFIGURATION_NOT_SUPPORTED
0x0000003E indicates the presence of several processors in the system, while they are asymmetric with respect to each other. Stop 0x0000003E means a multiprocessor configuration is not supported. For example, not all processors are of the same level or of the same type.
⚠️ 0x0000003F Error: NO_MORE_SYSTEM_PTES
The main reason for the blue screen to appear is that the driver tried to request a large block of virtual memory, but there is no continuous block of sufficient size to satisfy this request.
Often video drivers try to capture a huge amount of memory, which simply does not exist. Backup programs can also cause this error. It
Indicates one of the following problems:
Records page table system (Pte) are deleted or fragmented by the system when a large number of input/output (I / S) is performed
A faulty device driver does not work properly with the memory
An application as a backup program incorrectly allocates large amounts of memory. Remove all newly installed software (pay special attention to utilities that work with hard drives) and newly installed drivers
⚠️ 0x00000040 Error: TARGET_MDL_TOO_SMALL
A newly installed hardware and software uninstall is recommended to find the problem. Make sure your newly added hardware is compatible with your Windows and download the latest available drivers directly from the site of your hardware manufacturer.
⚠️ 0x00000041 Error: MUST_SUCCEED_POOL_EMPTY
In Windows 2000, the must-succeed pool size is very small. Windows XP lacks the ability of drivers to use the must-succeed pool to execute their commands.
⚠️ 0x00000042 Error: ATDISK_DRIVER_INTERNAL
This BSOD appears very rarely, the blue screen of death 0x00000042 indicates an internal error in the hard disk and driver.
⚠️ 0x00000043 Error: NO_SUCH_PARTITION
This BSOD appears very rarely, if ever. Reveals a hard disk problem. Scan your computer with an online antivirus and check for viruses. Test your hard drive with the utility available on the manufacturer’s site.
⚠️ 0x00000044 Error: MULTIPLE_IRP_COMPLETE_REQUESTS
Usually, this BSOD is affected by problems with a device driver. To delete or obtain more accurate information follows. The driver called the IoCompleteRequest () function to complete the IRP, but the package has already completed.
⚠️ 0x00000045 Error: INSUFFICIENT_SYSTEM_MAP_REGS
0x00000045 indicates that an attempt was made to allocate more map registers than the adapter.
⚠️ 0x00000046 Error: DEREF_UNKNOWN_LOGON_SESSION
The blue screen of death 0x00000046 indicates the removal of a token that is not part of any login session.
⚠️ 0x00000047 Error: REF_UNKNOWN_LOGON_SESSION
A blue screen of 0x00000047 indicates that a token has been created that is not part of any login sessions.
⚠️ 0x00000048 Error: CANCEL_STATE_IN_COMPLETED_IRP
If this happens to you after installing a device, check for the latest version of the driver on the internet, directly on the manufacturer’s site.
⚠️ 0x00000049 Error: PAGE_FAULT_WITH_INTERRUPTS_OFF
A blue screen of 0x00000049 indicates a missing page during the interrupt disable.
⚠️ 0x0000004A Error: IRQL_GT_ZERO_AT_SYSTEM_SERVICE
The blue screen 0x0000004A indicates that the thread is returning to user mode from a system call when its IRQL is still above PASSIVE_LEVEL.
⚠️ 0x0000004B Error: STREAMS_INTERNAL_ERROR
The 0x0000004B blue screen indicates an internal error in the streaming environment or in the streaming driver.
⚠️ 0x0000004C Error: FATAL_UNHANDLED_HARD_ERROR
The blue screen of death 0x0000004C indicates that a fatal serious error occurred before the error handler was available. There are several reasons why this error could occur:
the registry data structure file could not be loaded because it is either damaged or not found
Winlogon or Windows did not start unexpectedly
Driver or system dll is damaged
⚠️ 0x0000004D Error: NO_PAGES_AVAILABLE
The 0x0000004D blue screen indicates a lack of free space for operations. There are a large number of causes of the Stop 0x0000004D error, but the culprit is always the same – the device driver.
⚠️ 0x0000004E Error: PFN_LIST_CORRUPT
This means that the PFN list is damaged. It can be caused by a malfunction of physical memory or driver incorrectly installed.
⚠️ 0x0000004F Error: NDIS_INTERNAL_ERROR
The 0x0000004F blue screen indicates an internal NDIS driver error (Network Driver Interface Specification).
This is a very rare error, which indicates an internal error in the shell NDIS (Interface Specification Network Controller) or the NDIS driver. Make sure you have the card driver installed network freshest.
Also read – How to Fix Mouse Cursor Disappears in Windows 10?
How to Find Windows Crash Logs Generated by Blue Screen Errors
The logs stored in the Minidump folder are files with a .log extension, the file name contains the date and another numbering, looks something like the following: 050811-33353-01.dmp and unfortunately, it will be no use trying to open them to see the information it contains if it is not with a program or application designed for that purpose.
Microsoft provides the necessary tools to analyze the logs created in the memory dumps, which you can have by installing Debugging Tools for Windows , download it at the following address:
http://www.microsoft.com/whdc/DevTools/Debugging/default.mspx
To use this tool you need some advanced knowledge since it is made for developers.
It is recommended to use Blue Screen View a small freeware application (45KB), feasible to use by any user and that will also be useful to detect and solve the conflicts that cause blue screen errors.
When appears BSoD, see the sections:
The problem seems to be caused.” Contains the file that caused the blockade
Then the name of the error is displayed
Technical information”. Technical information. After the word “STOP” must write an error number. For example, “0x0000007E” or “0xC0000135”;
Then comes the driver’s name and address error
What Are Device Drivers and Why Do You Need Them?
Drivers or device drivers are small files that function as an instruction manual needed to interact with the operating system with hardware devices (video cards, modems, printers, etc.)
They need to be updated in relation to the system where they will be used and the model of the device itself.
Detect & Update Device Driver Conflict
Updating the driver of a device with conflicts is not difficult, access the Device Manager.
For that type or paste in devmgmt.msc Start and press Enter
There you look for your device in the list, it will usually show a question mark that will allow you to identify it
Right-click on it and select: Update driver software, follow the steps in the wizard
If you cannot find the device in the list, in the View menu select: Show hidden devices, if it does not already appear, select: View Devices by connection
Also Read – How To Install Unsigned Drivers In Windows 10 [FIXED]
Automatically Get Recommended Drivers For Windows 10
Another option, the ideal is to use a program that automatically checks and updates all the drivers or drivers of the PC, Laptop or Notebook devices.
For that, the ideal option is a free program called FixBit, best driver update software for windows 10, 8, 7 XP & Vista.
It works on all versions of Windows.
