⌚️ 0x00000013 EMPTY_THREAD_REAPER_LIST
Obviously, the meaning of these errors is not as important as their solutions.
The following section is going to explain how to fix any of the errors which are showing as a blue screen (BSOD) ↴
0xC1 STOP errors mean a driver wrote to an invalid section of memory.
When using your system, the kernel of Windows uses a series of “drivers” to communicate with its hardware. These drivers have a certain allocation of memory, which are known as “pools”.
The error you’re seeing is that one of your system’s drivers tried to access a non existent memory pool. The fix is to boot into safe mode and uninstall/replace any of the drivers that are faulty & causing problems…
STOP code 0x000000C1 may also show as “SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION” — it’s caused by
0xC2 STOP errors mean the current thread is making a bad pool request ↴
The problem is that your CPU is running a “thread” which is requesting an invalid resource (memory address). Since the error affects the system’s hardware level, Windows has no choice but to shut down & show a blue screen.
The fix is to ensure the various components inside your system are working correctly (updated drivers), that Windows is working as fully & completely as possible (update Windows) and you’re not running any apps that could be leading your system to run out of memory.
You can see how to fix the error here…
STOP code 0x000000C2 may also display “BAD_POOL_CALLER”, a classic blue screen error which used to plague Windows 9x systems.
0xC4 STOP errors is the general STOP code code for fatal errors found by Driver Verifier…
Starting with Windows 7 SP1, it became necessary to have digitally signed drivers. If any of your drivers are either unsigned, or have memory leaks, this will lead to the error you’re experiencing.
The solution is to reboot into “safe mode” (if possible) and ensure your system is running all the necessary drivers. You’ll also need to use the Windows Driver Verifier tool to ensure that all of your system’s drivers are 100% compatible with your system…
STOP code 0x000000C4 may also display as “DRIVER_VERIFIER_DETECTED_VIOLATION”.
0xC5 STOP errors mean that the system attempted to access invalid memory at a process IRQL that was too high.
IRQL stands for “Interrupt Request Level” which is the core management system for how the CPU interfaces with memory and other hardware components.
The error you’re seeing is mostly due to a driver causing problems, which should either be updated, uninstalled or replaced through safe mode.
As mentioned, the main reason for blue screen errors in Windows is faulty / damaged drivers.
This is especially a problem with Windows 10, whereby some of the drivers previously used on other systems could be incompatible with your current system ↓
STOP code 0x000000C5 may also display as “DRIVER_CORRUPTED_EXPOOL”.
0xC6 STOP errors mean that a driver attempted to access a freed memory pool. Whenever you use an x86/x64 system, your CPU will allocate a series of memory “pools” which can be allocated to a number of different components.
Unfortunately, it appears a particular driver (the software which connects your software to hardware) was trying to edit a “freed” memory pool, which causes a fatal error. To fix this, you’ll need to restart into Safe Mode and modify the faulty driver (uninstall or upgrade).
The driver at fault can be identified by looking at the *.sys file mentioned on the blue screen…
STOP code 0x000000C6 may also display as “DRIVER_CAUGHT_MODIFYING_FREED_POOL”.
[[ image ]]
0xC7 STOP errors appear if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
STOP code 0x000000C7 may also display “TIMER_OR_DPC_INVALID” on the same STOP message.
0xC8 STOP errors mean that the processor’s “IRQL” (Interrupt Request Level) value is not what it should be. The error is indicative of a driver, or even a piece of software, causing memory management issues on your system…
Whilst almost certainly a driver problem, many people see the error when using a memory-intensive application such as a video-editing package or game.
The solution is to ensure that all hardware & software is working correctly. To solve this, you need to browse through the various drivers on your system and remove any of the potentially damaged ones. This is done through safe mode.
STOP code 0x000000C8 will display solely as “IRQL_UNEXPECTED_VALUE” on Windows 10 systems. The problem is almost certainly driver-related.
0xC9 STOP errors indicate Driver Verifier I/O Verification violations.
Since Windows 7, Microsoft has included the Windows Driver Verifier app in to systematize the management of the various drivers on your system.
Drivers have the perilous task of interfacing with the various hardware components on your system. This is often referred to as “I/O” (Input/Output).
The error you’re experiencing is that one of your system’s drivers did not pass one of the checks to manage its I/O verification. If this is the case, it means that your computer is unable to mange the driver’s connection to your hardware, leading to the blue screen error.
To resolve it, you’re recommended to restart into safe mode and examine each driver for potential I/O verification issues.
The STOP 0x000000C9 error may also display “DRIVER_VERIFIER_IOMANAGER_VIOLATION” on the same message.
STOP error 0xCA means that the Plug and Play Manager encountered a severe error, probably a problematic Plug and Play driver (PNP stands for “Plug and Play”).
As with most STOP errors, a driver is to blame — this time with a “plug and play” device that you loaded. This may come in the form of a USB flash drive, printer or some other hardware component…
To fix the error, you need to remove the new device, restart your system into safe mode and pre-install an applicable driver.
After doing this, you may wish to try “repairing” Windows if the problem persists. After doing this, you should be able to use the system…
STOP code 0x000000CA may also display “PNP_DETECTED_FATAL_ERROR” on Windows 10 error messages.
STOP error 0xCB means that a driver or the I/O manager failed to release locked pages after an I/O operation…
[[ description ]]
STOP code 0x000000CB may also display “DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS” on the same STOP message.
STOP error 0xCC means that the system has referenced memory which was earlier freed. STOP code 0x000000CC may also display “PAGE_FAULT_IN_FREED_SPECIAL_POOL” on the same STOP message.
STOP error 0xCD means that the system accessed memory beyond the end of some driver’s pool allocation. STOP code 0x000000CD may also display “PAGE_FAULT_BEYOND_END_OF_ALLOCATION” on the same STOP message.
STOP error 0xCE means that a driver failed to cancel pending operations before unloading…
To give context, each time a driver is loaded, it has to “mount” specific hardware components. In other systems, this is done explicitly, in Windows it’s done behind the scenes.
In the same way, when the system removes hardware, it has to “dismount” it via the driver. This is best evidenced with the “safe eject” feature for USB’s.
The problem you’re experiencing is that your system basically was unable to correctly dismount a piece of hardware from the system, thus leading it to show the fatal blue screen error.
To fix it , you need to resolve any underlying driver issues that may be present, which means accessing Safe Mode and uninstalling / updating / repairing any applicable driver…
STOP code 0x000000CE may also display DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS.
STOP error 0xCF means a driver has been incorrectly ported to the “terminal server”…
[[ image ]]
The terminal server is a core element of Windows, basically responsible for the system being able to interact with the various pieces of software it requires to run.
Seeing errors in this instance basically means that one of the system’s drivers (almost certainly the graphics driver) is causing a problem. To fix it, you need to remove the faulty driver and check to see if the hardware is damaged or corrupted.
STOP code 0x000000CF may also display the following error: TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE.
0xD0 STOP errors mean the system attempted to access invalid memory at a process IRQL that was too high. This problem is almost always caused by
STOP code 0x000000D0 will display “DRIVER_CORRUPTED_MMPOOL” on the same STOP message, typically with a reference to a *.sys driver file.
0xD1 STOP errors mean that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
STOP code 0x000000D1 may also display “DRIVER_IRQL_NOT_LESS_OR_EQUAL” on the same STOP message.
STOP error 0xD2 means that a problem occurred with an NDIS driver. STOP code 0x000000D2 may also display “BUGCODE_ID_DRIVER” on the same STOP message.
STOP error 0xD3 means that the system attempted to access pageable memory at a process IRQL that was too high. STOP code 0x000000D3 may also display “DRIVER_PORTION_MUST_BE_NONPAGED” on the same STOP message.
STOP error 0xD4 means that a driver did not cancel pending operations before unloading. STOP code 0x000000D4 may also display “SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD” on the same STOP message.
STOP error 0xD5 means that a driver has referenced memory which was earlier freed. STOP code 0x000000D5 may also display “DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL” on the same STOP message.
STOP error 0xD6 means the driver accessed memory beyond the end of its pool allocation. STOP code 0x000000D6 may also display “DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION” on the same STOP message.
STOP error 0xD7 means a driver is trying to unmap an address that was not mapped. STOP code 0x000000D7 may also display “DRIVER_UNMAPPING_INVALID_VIEW” on the same STOP message.
STOP error 0xD8 means that there are no more system page table entries (PTE) remaining. STOP code 0x000000D8 may also display “DRIVER_USED_EXCESSIVE_PTES” on the same STOP message.
STOP error 0xD9 means that the internal locked-page tracking structures have been corrupted. STOP code 0x000000D9 may also display “LOCKED_PAGES_TRACKER_CORRUPTION” on the same STOP message.
STOP error 0xDA means that a page table entry (PTE) routine has been used in an improper way. STOP code 0x000000DA may also display “SYSTEM_PTE_MISUSE” on the same STOP message.
STOP error 0xDB means that an attempt was made to touch memory at an invalid IRQL, probably due to corruption of system PTEs. STOP code 0x000000DB may also display “DRIVER_CORRUPTED_SYSPTES” on the same STOP message.
STOP error 0xDC means that a driver accessed a stack address that lies below the stack pointer of the stack’s thread. STOP code 0x000000DC may also display “DRIVER_INVALID_STACK_ACCESS” on the same STOP message.
STOP error 0xDE means that a driver has corrupted pool memory that is used for holding pages destined for disk.
STOP code 0x000000DE may also display “POOL_CORRUPTION_IN_FILE_AREA” on the same STOP message.
STOP error 0xDF means that a workitem did not disable impersonation before it completed. STOP code 0x000000DF may also display “IMPERSONATING_WORKER_THREAD” on the same STOP message.
STOP error 0xE0 means that one of your computer components is faulty. STOP code 0x000000E0 may also display “ACPI_BIOS_FATAL_ERROR” on the same STOP message.
STOP error 0xE1 means that a worker thread completed and returned with IRQL >= DISPATCH_LEVEL. STOP code 0x000000E1 may also display “WORKER_THREAD_RETURNED_AT_BAD_IRQL” on the same STOP message
STOP error 0xE2 means that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard. STOP code 0x000000E2 may also display “MANUALLY_INITIATED_CRASH” on the same STOP message.
STOP error 0xE3 means that a thread tried to release a resource it did not own. STOP code 0x000000E3 may also display “RESOURCE_NOT_OWNED” on the same STOP message.
STOP error 0xE4 means that memory that should not contain an executive worker item does contain such an item, or that a currently active worker item was queued. STOP code 0x000000E4 may also display “WORKER_INVALID” on the same STOP message.
STOP error 0xE6 is the STOP code for all Driver Verifier DMA Verification violations. STOP code 0x000000E6 may also display “DRIVER_VERIFIER_DMA_VIOLATION” on the same STOP message.
STOP error 0xE7 means that a thread’s saved floating-point state is invalid. STOP code 0x000000E7 may also display “INVALID_FLOATING_POINT_STATE” on the same STOP message.
STOP error 0xE8 means that an invalid file object was passed to IoCancelFileOpen. STOP code 0x000000E8 may also display “INVALID_CANCEL_OF_FILE_OPEN” on the same STOP message.
STOP error 0xE9 means that an active executive worker thread is being terminated. STOP code 0x000000E9 may also display “ACTIVE_EX_WORKER_THREAD_TERMINATION” on the same STOP message.
STOP error 0xEA means that a thread in a device driver is endlessly spinning. STOP code 0x000000EA may also display “THREAD_STUCK_IN_DEVICE_DRIVER” on the same STOP message.
STOP error 0xEB means that no free pages are available to continue operations. STOP code 0x000000EB may also display “DIRTY_MAPPED_PAGES_CONGESTION” on the same STOP message.
STOP error 0xEC means that a session unload occurred while a session driver still held memory. STOP code 0x000000EC may also display “SESSION_HAS_VALID_SPECIAL_POOL_ON_EXIT” on the same STOP message.
STOP error 0xED means that the I/O subsystem attempted to mount the boot volume and it failed…
STOP code 0x000000ED may also display “UNMOUNTABLE_BOOT_VOLUME” on the same STOP message…
STOP error 0xEF means that a critical system process died. STOP code 0x000000EF may also display “CRITICAL_PROCESS_DIED” on the same STOP message.
STOP error 0xF1 is the STOP code for all Driver Verifier SCSI Verification violations. STOP code 0x000000F1 may also display “SCSI_VERIFIER_DETECTED_VIOLATION” on the same STOP message.
STOP error 0xF3 means that Windows was unable to shut down due to lack of memory. STOP code 0x000000F3 may also display “DISORDERLY_SHUTDOWN” on the same STOP message.
STOP error 0xF4 means that a process or thread crucial to system operation has unexpectedly exited or been terminated.
STOP code 0x000000F4 may also display “CRITICAL_OBJECT_TERMINATION” on the same STOP message.
STOP error 0xF5 means that an unrecoverable failure occurred in the Filter Manager.
STOP code 0x000000F5 may also display “FLTMGR_FILE_SYSTEM” on the same STOP message.
STOP error 0xF6 means that an error occurred in the BIOS or another device being verified by the PCI driver. STOP code 0x000000F6 may also display “PCI_VERIFIER_DETECTED_VIOLATION” on the same STOP message.
STOP error 0xF7 means that a driver has overrun a stack-based buffer. STOP code 0x000000F7 may also display “DRIVER_OVERRAN_STACK_BUFFER” on the same STOP message.
STOP error 0xF8 means that an initialization failure occurred while attempting to boot from the RAM disk. STOP code 0x000000F8 may also display “RAMDISK_BOOT_INITIALIZATION_FAILED” on the same STOP message.
STOP error 0xF9 means that a driver returned STATUS_REPARSE to an IRP_MJ_CREATE request with no trailing names. STOP code 0x000000F9 may also display “DRIVER_RETURNED_STATUS_REPARSE_FOR_VOLUME_OPEN” on the same STOP message.
STOP error 0xFA means that the HTTP kernel driver (Http.sys) has reached a corrupted state and cannot recover. STOP code 0x000000FA may also display “HTTP_DRIVER_CORRUPTED” on the same STOP message.
STOP error 0xFC means that an attempt was made to execute non-executable memory. STOP code 0x000000FC may also display
“ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY” on the same STOP message.
STOP error 0xFD means that there are no free pages available to continue basic system operations. STOP code 0x000000FD may also display “DIRTY_NOWRITE_PAGES_CONGESTION” on the same STOP message.
STOP error 0xFE means that an error has occurred in a Universal Serial Bus (USB) driver.
STOP code 0x000000FE may also display “BUGCODE_USB_DRIVER” on the same STOP message.
STOP error 0xFF means that an attempt was made to insert a new item into a reserve queue, causing the queue to overflow. STOP code 0x000000FF may also display “RESERVE_QUEUE_OVERFLOW” on the same STOP message.
STOP error 0x100 means that either the loader block is invalid, or it does not match the system that is being loaded.
STOP code 0x00000100 may also display “LOADER_BLOCK_MISMATCH” on the same STOP message.
STOP error 0x101 means that an expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
STOP code 0x00000101 may also display “CLOCK_WATCHDOG_TIMEOUT” on the same STOP message.
STOP error 0x103 means that the multiple UNC provider (MUP) has encountered invalid or unexpected data.
As a result, the MUP cannot channel a remote file system request to a network redirector, the Universal Naming Convention (UNC) provider. STOP code 0x00000103 may also display “MUP_FILE_SYSTEM” on the same STOP message.
STOP error 0x104 means that the GPU wrote to a range of Accelerated Graphics Port (AGP) memory that had not previously been committed. STOP code 0x00000104 may also display “AGP_INVALID_ACCESS” on the same STOP message.
STOP error 0x105 means that the Graphics Aperture Remapping Table (GART) is corrupt. STOP code 0x00000105 may also display “AGP_GART_CORRUPTION” on the same STOP message.
STOP error 0x106 means that the Accelerated Graphics Port (AGP) hardware has been reprogrammed by an unauthorized agent. STOP code 0x00000106 may also display “AGP_ILLEGALLY_REPROGRAMMED” on the same STOP message.
STOP error 0x108 means that an unrecoverable problem has occurred in a third-party file system or file system filter.
STOP code 0x00000108 may also display “THIRD_PARTY_FILE_SYSTEM_FAILURE” on the same STOP message.
STOP error 0x109 means that the kernel has detected critical kernel code or data corruption.
STOP code 0x00000109 may also display “CRITICAL_STRUCTURE_CORRUPTION” on the same STOP message.
STOP error 0x10A is not very common. STOP code 0x0000010A may also display “APP_TAGGING_INITIALIZATION_FAILED” on the same STOP message.
STOP error 0x10C means that a violation was detected in the File system Run-time library (FsRtl) Extra Create Parameter (ECP) package. STOP code 0x0000010C may also display “FSRTL_EXTRA_CREATE_PARAMETER_VIOLATION” on the same STOP message.
STOP error 0x10D means that Kernel-Mode Driver Framework (KMDF) detected that Windows found an error in a framework-based driver. STOP code 0x0000010D may also display “WDF_VIOLATION” on the same STOP message.
STOP error 0x10E means that the video memory manager has encountered a condition that it is unable to recover from. STOP code 0x0000010E may also display “VIDEO_MEMORY_MANAGEMENT_INTERNAL” on the same STOP message.
STOP error 0x10F means that the kernel transaction manager detected that a kernel-mode resource manager has raised an exception in response to a direct call-back. The resource manager is in an unexpected and unrecoverable state. STOP code 0x0000010F may also display “RESOURCE_MANAGER_EXCEPTION_NOT_HANDLED” on the same STOP message.
STOP error 0x111 means that a non-maskable-interrupt (NMI) occurred while a previous NMI was in progress. STOP code 0x00000111 may also display “RECURSIVE_NMI” on the same STOP message.
STOP error 0x112 means that the Msrpc.sys driver has initiated a STOP code. STOP code 0x00000112 may also display “MSRPC_STATE_VIOLATION” on the same STOP message
STOP error 0x113 means that the dxg kernel has detected a violation.
STOP code 0x00000113 may also display “VIDEO_DXGKRNL_FATAL_ERROR” on the same STOP message.
STOP error 0x114 means that the shadow driver has detected a violation. STOP code 0x00000114 may also display “VIDEO_SHADOW_DRIVER_FATAL_ERROR” on the same STOP message.
STOP error 0x115 means that the accelerated graphics port (AGP) driver has detected a violation. STOP code 0x00000115 may also display “AGP_INTERNAL” on the same STOP message.
STOP error 0x116 means that an attempt to reset the display driver and recover from a timeout failed.
STOP code 0x00000116 may also display “VIDEO_TDR_ERROR” on the same STOP message.
STOP error 0x117 means that the display driver failed to respond in a timely fashion.
STOP code 0x00000117 may also display “VIDEO_TDR_TIMEOUT_DETECTED” on the same STOP message.
STOP error 0x119 means that the video scheduler has detected a fatal violation.
STOP code 0x00000119 may also display “VIDEO_SCHEDULER_INTERNAL_ERROR” on the same STOP message.
STOP error 0x11A is not very common. STOP code 0x0000011A may also display “EM_INITIALIZATION_FAILURE” on the same STOP message.
STOP error 0x11B means that a driver has returned from a cancel routine that holds the global cancel lock.
This causes all later cancellation calls to fail, and results in either a deadlock or another STOP code. STOP code 0x0000011B may also display “DRIVER_RETURNED_HOLDING_CANCEL_LOCK” on the same STOP message.
STOP error 0x11C means that an attempt was made to write to the read-only protected storage of the configuration manager.
STOP code 0x0000011C may also display “ATTEMPTED_WRITE_TO_CM_PROTECTED_STORAGE” on the same STOP message.
STOP error 0x11D means that the Event Tracing subsystem has encountered an unexpected fatal error.
STOP code 0x0000011D may also display “EVENT_TRACING_FATAL_ERROR” on the same STOP message.
STOP error 0x1 means that there has been a mismatch in the APC state index.
STOP code 0x00000001 may also display “APC_INDEX_MISMATCH” on the same STOP message.
STOP error 0x2 is not very common. STOP code 0x00000002 may also display “DEVICE_QUEUE_NOT_BUSY” on the same STOP message.
STOP error 0x3 is not very common. STOP code 0x00000003 may also display “INVALID_AFFINITY_SET” on the same STOP message.
STOP error 0x4 is not very common. STOP code 0x00000004 may also display “INVALID_DATA_ACCESS_TRAP” on the same STOP message.
STOP error 0x5 is not very common. STOP code 0x00000005 may also display “INVALID_PROCESS_ATTACH_ATTEMPT” on the same STOP message.
STOP error 0x6 is not very common. STOP code 0x00000006 may also display “INVALID_PROCESS_DETACH_ATTEMPT” on the same STOP message.
0x7 STOP errors denote a core issue with a piece of software on your system, typically one that’s been tapping deeper into the hardware (GPU hardware acceleration).
If you’re seeing these errors, it typically means that you’ve got problems with a program on your system, although it’s also quite common for a driver to sit at the core of it all too, as cited by the *.sys file that often shows:
STOP code 0x00000007 may also display “INVALID_SOFTWARE_INTERRUPT” on the screen. This problem is almost always software related (rather than hardware).
STOP error 0x8 is not very common. STOP code 0x00000008 may also display “IRQL_NOT_DISPATCH_LEVEL” on the same STOP message.
STOP error 0x9 is not very common. STOP code 0x00000009 may also display “IRQL_NOT_GREATER_OR_EQUAL” on the same STOP message.
STOP error 0xA means that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. STOP code 0x0000000A may also display “IRQL_NOT_LESS_OR_EQUAL” on the same STOP message.
STOP error 0xB is not very common. STOP code 0x0000000B may also display “NO_EXCEPTION_HANDLING_SUPPORT” on the same STOP message
STOP error 0xC means that the current thread exceeded the permitted number of wait objects. STOP code 0x0000000C may also display “MAXIMUM_WAIT_OBJECTS_EXCEEDED” on the same STOP message.
STOP error 0xD is not very common. STOP code 0x0000000D may also display “MUTEX_LEVEL_NUMBER_VIOLATION” on the same STOP message.
STOP error 0xE is not very common. STOP code 0x0000000E may also display “NO_USER_MODE_CONTEXT” on the same STOP message.
STOP error 0xF means that a request for a spin lock has been initiated when the spin lock was already owned. STOP code 0x0000000F may also display “SPIN_LOCK_ALREADY_OWNED” on the same STOP message.
STOP error 0x10 is not very common. STOP code 0x00000010 may also display “SPIN_LOCK_NOT_OWNED” on the same STOP message.
STOP error 0x11 is not very common. STOP code 0x00000011 may also display “THREAD_NOT_MUTEX_OWNER” on the same STOP message.
STOP error 0x12 means that an unknown exception has occurred. STOP code 0x00000012 may also display “TRAP_CAUSE_UNKNOWN” on the same STOP message.
STOP error 0x13 is not very common. STOP code 0x00000013 may also display “EMPTY_THREAD_REAPER_LIST” on the same STOP message.
STOP error 0x14 is not very common.
STOP code 0x00000014 may also display “CREATE_DELETE_LOCK_NOT_LOCKED” on the same STOP message.
If you need further support, there are a number of options…
We recommend PCFixes.com Live Support, but obviously there are several other options…
Microsoft Answers, SuperUser.com, Yahoo Answers
These services allow you to “ask” questions and receive answers ↴
Microsoft Answers can be useful, but be prepared to wait for quality respondents… SuperUser is good but getting decent responses is a game of chance…
Whilst FREE, the quality of response depends on who answers.