0x000000DF: IMPERSONATING_WORKER_THREAD occurs on older builds of Windows and indicates that the work item did not disable impersonation before shutting down.
The blue ACPI_BIOS_FATAL_ERROR death screen with code 0x000000E0 indicates that one of the computer components is defective. However, such an error is detected not by Windows, but by the BIOS.
WORKER_THREAD_RETURNED_AT_BAD_IRQL with the digital code 0x000000E1 indicates that the workflow has completed and returned with IRQL> = DISPATCH_LEVEL.
MANUALLY_INITIATED_CRASH with code 0x000000E2 indicates that the user deliberately triggered a crash dump using the kernel debugger or using the keyboard.
RESOURCE_NOT_OWNED with a digital code 0x000000E3 indicates that the thread tried to free a resource that it does not own.
WORKER_INVALID with a digital code 0x000000E4 indicates that the memory, which should not contain an executive work item, contains it. Or, the currently active work item has been queued.
DRIVER_VERIFIER_DMA_VIOLATION with code 0x000000E6 is an error for all DMA violations of the Driver Verifier. This BSoD occurs on older versions of Windows due to software damage, as well as system files.
The BSOD or the blue death screen INVALID_FLOATING_POINT_STATE with the digital code 0x000000E7 occurs due to a driver failure. Most often, BSOD appears when working with multimedia files, browsers and players.
The BSOD or INVALID_CANCEL_OF_FILE_OPEN blue screen of death with a digital stop code of 0x000000E8 occurs on old and new builds of Windows.
There are two different cases of an error with the code 0xc00000e9, it can appear when installing Windows Vista, Windows 7 and Windows 8, or in an already installed and long-running system.
Error 0x000000EA can occur for a number of reasons, most often it is: video card malfunctions, problems with installed drivers or programs, old BIOS version. Fortunately, all this can be solved independently.
DIRTY_MAPPED_PAGES_CONGESTION with code 0x000000EB indicates the absence of free pages that are needed to continue operations.
BSESS SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT with a digital code of 0x000000EC appears in situations when a session is unloaded while the session driver is still using memory. This BSoD occurs on older Windows builds due to damage or malfunctioning of drivers such as win32k.sys, atmfd.dll, rdpdd.dll, or a video driver.
STOP error: 0x000000ED, UNMOUNTABLE_BOOT_VOLUME, occurs when you turn on the computer and it affects all versions of Windows
Error 0x000000EF CRITICAL_PROCESS_DIED on Windows 10? How to fix and what to do when BSOD occurs, read the article.
0x000000F1 – error control code for all SCSI driver verifier violations. If you do not use the Driver Verifier, you must remove it. Removing the driver that caused the error will also fix 0x000000F1.
The blue death screen DISORDERLY_SHUTDOWN with a numerical code 0x000000F3 indicates that the Windows operating system is unable to complete the process due to out of memory.
The most common cause of the STOP: 0x000000F4 error is hardware compatibility issues with the operating system, i.e. hardware driver mismatches. Also, the cause may be technical problems with the network card, sound card, or disk from which the OS is loaded.
0x000000F5 indicates a Filter Manager failure. This means that a fatal failure has occurred in Filter Manager. It can be damaged by viruses or by the PC user.
BSOD PCI_VERIFIER_DETECTED_VIOLATION with a digital code of 0x000000F6 indicates a BIOS or other device error being verified by the PCI driver.
The blue death screen DRIVER_OVERRAN_STACK_BUFFER with a digital code of 0x000000F7 indicates that the driver has exceeded the stack buffer.
Error 0x000000F8 indicates that initialization failed while trying to boot from disk.
0x000000F9 indicates that the driver returned STATUS_REPARSE with an unnamed name IRP_MJ_CREATE.
The HTTP_DRIVER_CORRUPTED blue screen of death with digital code 0x000000FA indicates that the HTTP kernel driver (Http.sys) is corrupt or cannot be repaired.
ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY with a digital code of 0x000000FC indicates that the system tried to use non-executable memory.
The blue screen of death DIRTY_NOWRITE_PAGES_CONGESTION with the digital code 0x000000FD indicates that there are no free pages that would be necessary to perform basic system operations, but are missing or damaged. The reason 0x000000FD is a driver error, its damage, or incompatibility with the operating system.
Error 0x000000FE occurred in the universal serial bus (USB) driver. 0x000000FE indicates a USB driver error.
The blue death screen RESERVE_QUEUE_OVERFLOW with the digital code 0x000000FF indicates an attempt to insert a new element into the backup queue, which leads to its overflow.
0x00000100 – The bootloader block is invalid. Also, the cause of this error may be the mismatch of the loader block with the system that it is trying to load.
The blue screen 0x00000101 indicates that the expected interruption of the system timer on the secondary processor, in a multiprocessor system, was not performed in the allocated interval.
0x00000103 indicates that a multiple Internet Protocol Provider (MUP) has encountered invalid or unexpected data. As a result, the MUP cannot form a channel requesting the remote file system to the network redirector.
Error 0x00000104 occurs when you try to write the GPU to memory. Error 0x00000104 is related to video drivers. Also, 0x00000104 can occur if there is an old BIOS version.
The blue death screen AGP_GART_CORRUPTION with a digital code 0x00000105 indicates damage to the GART.
The blue death screen AGP_ILLEGALLY_REPROGRAMMED with digital code 0x00000106 indicates that the AGP hardware has been reprogrammed by an unauthorized agent.
The THIRD_PARTY_FILE_SYSTEM_FAILURE blue screen of death with digital code 0x00000108 indicates an unrecoverable problem in a third-party file system or file system filter.
Most often, the existence of the xntkrnl.exe file is recognized by the user when 0x00000109 or a BSOD error occurs.
Error APP TAGGING INITIALIZATION FAILED 0x0000010A (blue screen of death) appears on the screen during the initialization process for Windows and is most likely caused by a damaged or missing device driver or a malfunctioning device that was recently installed.
This indicates that a violation was detected in the file system library (FsRtl) Extra Create Parameter (ECP) package.
0x0000010D: WDF_VIOLATION indicates that the Kernel Mode Driver Framework (KMDF) has detected that Windows has found an error in the main driver platform.
BSOD VIDEO_MEMORY_MANAGEMENT_INTERNAL with a digital code 0x0000010E indicates that the video memory manager is in a state from which it is not able to recover.
0x0000010F indicates that the kernel transaction manager detected that the privileged mode resource manager raised an exception in response to a direct callback.
The blue RECURSIVE_NMI death screen with digital code 0x00000111 indicates the execution of a non-maskable interrupt (NMI) while the previous NMI was running.
The most common cause of BSoD 0x00000112 is the calling side of the Msrpc.sys driver, which violates the state semantics for such a call.
The blue screen of death VIDEO_DXGKRNL_FATAL_ERROR with digital code 0x00000113 indicates that the dxg kernel has detected a violation.
BSOD 0x00000114: VIDEO_SHADOW_DRIVER_FATAL_ERROR indicates that the driver is damaged, missing, or incompatible with the Windows operating system.
Blue Screen of Death (BSOD) 0x00000115 indicates that a graphics card driver (AGP) detected a violation.
The Blue Screen of Death (BSOD) 0x00000116 indicates that an attempt has been made to reset the display driver and restore it, but this causes a timeout to occur.
Blue screen of death (BSOD) VIDEO_TDR_TIMEOUT_DETECTED with code 0x00000117 indicates that the display driver did not respond promptly to the request.
Blue Screen of Death (BSOD) 0x00000119 indicates that the video scheduler has detected a fatal violation.
Error blue screen of death (BSOD) 0x0000011A rarely appears. To eliminate the error you need to use our tips.
This error check 0x0000011B indicates that the driver returned from a cancel routine that contains a global cancel lock. This causes all later undo calls to stop working and results in either deadlocks or other errors.
Blue Screen of Death (BSOD) 0x0000011C indicates an attempt to write a read-only configuration manager.
Blue screen of death (BSOD) EVENT_TRACING_FATAL_ERROR with digital code 0x0000011D indicates that the Event Tracing subsystem has detected a critical error.
Error 0x0000012C is caused by the exFAT file system when its internal state is in an unacceptable state and poses a greater risk of data loss.
BSOD (Blue Screen of Death) 0x00000133 indicates one of the following factors: execution of the watchdog DPC; detection of a single continuous DPC; The system spent a long time at the IRQL level DISPATCH_LEVEL or higher.
Blue Screen of Death (BSOD) 0x00000138 indicates that the GPIO driver has detected a fatal error.
BSOD 0x0000011E means that the file system caused too many recursive errors when there were not enough resources to process.
BSOD 0x0000011F means that the initial handle for the driver is closed between the driver object and the link to the handle.
BSOD BITLOCKER_FATAL_ERROR with digital code 0x00000120 indicates that BitLocker Drive Encryption encountered a problem that could not be resolved.
BSOD 0x00000123 indicates that the cryptographic subsystem did not perform the required self-test algorithm during boot.
BSOD 0x00000128 means that the IOPriority workflow was incorrectly modified by the work subroutine that was called.
BSOD 0x00000129 indicates that the Paging IOPriority workflow was not appropriately modified by the called routine.
BSOD 0x0000012A means that Windows did not find the installed language packs for the system default user interface.
BSOD 0x0000012D indicates that the volsnap driver attempted to access the common table from two different threads, which could lead to its damage.
BSOD 0x00000136 indicates that initialization failed while attempting to boot from a virtual hard disk (VHD). The volume on which the VHD is placed does not have enough free space to expand.
BSOD 0x0000013B means that the kernel has detected problems with the interrupt at the passive level.
BSOD 0x0000013C indicates that the thread is running with an invalid I / O boost status. The value should be zero when the thread terminates.
BSOD 0x00000145 means that enforcing the Windows Safe Start policy is not possible due to an incorrect policy or the failure to complete the required operation.
BSOD 0x00000147 says that Windows has passed an incorrect reset. No context entries or exceptions were saved, and no callback errors were raised.
BSOD 0x0000014C means that a fatal system error has occurred or an emergency system reset has occurred.
BSOD 0x00000151 indicates that an attempt was made to execute code using an unsupported mode of processor commands (for example, executing classic ARM commands instead of ThumbV2 instructions). This is not allowed.
BSOD 0x00000152 means that the flags provided to one of the lock APIs were invalid.
Blue screen of death 0x00000154 indicates that the storage component detected an unexpected exception.
BSOD 0x00000156 indicates that Winsock has detected a request to close the endpoint of the network transport system.
BSOD 0x00000157 means that an unauthorized operation was attempted at the priority level of a specific thread.
BSOD 0x00000158 means that the IOMMU delivered a paging error packet for an invalid ASID. This is insecure since the ASID may have already been used many times.
BSOD 0x0000015A indicates that an incompatible hardware failure has occurred on the connected SD device.
BSOD 0x00000160 means that the Win32k function violated the ATOMIC operation.
The blue screen of death 0x00000162 means that the lock monitored by AutoBoost has been released by a thread that does not belong to the lock.
Error 0x00000163 is rare, use the recommendations below.
The blue screen of death 0x0000016E means that the target chain pointer provided by ExReleaseResourceForThreadLite is invalid.
BSOD 0x0000018B means that the secure kernel encountered a fatal error. This stop error is rare.
The blue screen of death 0x00000121 indicates the presence of a driver in the system that caused a fatal error.
The blue screen of death 0x00000122 indicates that an internal error has occurred in the Windows Hardware Error Architecture (WHEA). The error may be due to the failure of the vendor-provided platform-specific hardware error driver (PSHED).
An error has occurred in the hardware of the computer. This error is detected by the Windows Hardware Error Architecture (WHEA).
The blue screen of death 0x00000127 indicates that the page that was supposed to be filled with zeros was not filled with them. This error could have occurred due to a hardware failure or because the privileged component of the operating system changed the page after it was released.
This error check indicates that a single-bit error was found on this page. This is a hardware memory error. Check memory for errors.
0x00000144 is a USB driver error. This does not automatically turn off the computer, but the USB host restarts automatically and the debug data is saved by the computer.
Error 0x1000007E means that the system thread generated an exception that the error handler did not recognize.
This means that in kernel mode, the program threw an exception that the error handler did not recognize. This problem is found in Windows Vista SP1.
The problem device driver put the system into a hang state. As a rule, this is caused by the display driver when trying to switch the computer into standby mode. This problem is related to the video adapter, or a bad video driver.
The system core of the operating system has exhausted all the system resources for its work, including the paging file. Increase hard disk space and RAM.
Windows tried to load the DLL library and got the error code. Possible cause – the file is missing or damaged. The system registry may also be damaged.
Error 0xc0000142 occurs in all versions of Windows when the application cannot be recognized correctly.
The required registry file cannot load. The file may be damaged or missing.
This happens when Windows has switched to the privileged mode, and the non-privileged mode subsystems, such as Winlogon or Client-Server Execution Time Subsystem (CSRSS), have failed, and protection cannot be guaranteed.
The blue screen of death 0x00000192 indicates that the lock monitored by AutoBoost was acquired during the execution of DISPATCH_LEVEL or higher.
0xC0000221 – Driver is corrupted or the system library has been recognized as damaged.
Blue screen of death 0x00000195 indicates that the SMB server detected a problem and received a core dump to collect debug information.
This issue occurs because of an error in the Compositebus.sys driver or a mismatch in the APC status index.