| Previous | Next |
| SPIN_LOCK_NOT_OWNED | TRAP_CAUSE_UNKNOWN |
THREAD_NOT_MUTEX_OWNER
Mutex ownership violation for THREAD_NOT_MUTEX_OWNER
THREAD_NOT_MUTEX_OWNER is bug check code 0x00000011. Kernel mutexes are thread-owned synchronization objects. This bug check indicates that ownership bookkeeping no longer matches the release or wait path, usually because a driver used the wrong object, wrong thread context, or bad unwind path.
How to read it in a dump
- Identify the thread in the dump and compare it with the mutex owner.
- Look for APC, worker-thread, completion, or cleanup paths that run in a different thread than the acquisition path.
- This is separate from spin-lock misuse because mutex ownership is tied to a thread.
What to check
- Verify that lock release occurs in the same ownership model used for acquisition.
- Inspect handoff between system threads, work items, callbacks, and cancel routines.
- Use verifier deadlock detection for repeatable ownership and ordering failures.
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 thread / mutex / owner.
- 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.