| Previous | Next |
| TRAP_CAUSE_UNKNOWN | CREATE_DELETE_LOCK_NOT_LOCKED |
EMPTY_THREAD_REAPER_LIST
Thread termination bookkeeping failure for EMPTY_THREAD_REAPER_LIST
EMPTY_THREAD_REAPER_LIST is bug check code 0x00000013. This historical bug check is tied to internal thread cleanup state. It suggests corruption or inconsistent list management around terminating threads rather than an ordinary process-exit problem.
How to read it in a dump
- The stack and list pointers are more important than public parameter names.
- Look for memory corruption, stale list entries, or a driver that damaged executive thread objects.
- A full kernel dump is usually needed because thread lists and pool state matter.
What to check
- Analyze pool corruption and recently unloaded drivers.
- Check callbacks, process/thread notification routines, and security products that observe thread lifetime.
- Use special pool and verifier for drivers near thread creation or teardown.
References
Dump evidence
Preserve the complete dump, the four bug-check parameters, the exact Windows build, loaded-module list, and the event timeline immediately before the stop. AllStat summarizes the condition as “this result”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.
Analysis order
- Run WinDbg
!analyze -v, then inspect the documented meaning of each parameter instead of relying only on the probably-caused-by line. - find the earliest abnormal event: driver update, firmware change, device reset, storage error, verifier report, resource exhaustion, or application hang connected with empty / thread / reaper / list.
- keep third-party filter, security, storage, graphics, and virtualization drivers in the module inventory; removing evidence before dump analysis can obscure the responsible path.
Do not repeatedly reboot a machine affected by this result before collecting the dump and event logs. Recovery actions should follow the component identified by the stack and parameters, not merely the symbolic stop-code name.
Looking for a different code? Search another status or error code.