What does BSOD 453 (IO_THREADPOOL_DEADLOCK_LIVEDUMP) mean?

 
Could be also:
ConstantTypeOS
ERROR_CAPAUTHZ_NOT_AUTHORIZEDWin32 errorWindows
Previous Next
DRIVER_VERIFIER_DETECTED_VIOLATION_LIVEDUMP FAST_ERESOURCE_PRECONDITION_VIOLATION

IO_THREADPOOL_DEADLOCK_LIVEDUMP

The IO_THREADPOOL_DEADLOCK_LIVEDUMP bug check has a value of 0x000001C5. This indicates a kernel mode threadpool encountered a deadlock situation.

Important

This topic is for programmers. If you are a customer who has received a blue screen error code while using your computer, see Troubleshoot blue screen errors.

IO_THREADPOOL_DEADLOCK_LIVEDUMP Parameters

Parameter Description
1

Pool Number.

0x0 : ExPoolUntrusted

2 Pointer to the PEX_WORK_QUEUE
3 Reserved
4 Reserved

Dump evidence for IO_THREADPOOL_DEADLOCK_LIVEDUMP

For IO_THREADPOOL_DEADLOCK_LIVEDUMP, 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 “IO_THREADPOOL_DEADLOCK_LIVEDUMP”; that sentence identifies the failure class, while the parameters and stack determine which object, driver, processor, or subsystem instance was involved.

Analysis order for IO_THREADPOOL_DEADLOCK_LIVEDUMP

  • Run WinDbg !analyze -v, then inspect the documented meaning of each IO_THREADPOOL_DEADLOCK_LIVEDUMP 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 io / threadpool / deadlock / livedump.
  • For IO_THREADPOOL_DEADLOCK_LIVEDUMP, 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 IO_THREADPOOL_DEADLOCK_LIVEDUMP before collecting the dump and event logs. For IO_THREADPOOL_DEADLOCK_LIVEDUMP, 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.