BSOD 0x13 (EMPTY_THREAD_REAPER_LIST): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: The kernel thread-reaper path found inconsistent termination bookkeeping.

Could be also:
Constant	Type	OS
ERROR_WRITE_PROTECT	Win32 error	Windows
KERN_UREFS_OVERFLOW	Kern return	Mac
ippStsDomain	Intel Ipp Status	Any
ENODEV	errno	Any

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

Looking for a different code? Search another status or error code.