BSOD 13 (MUTEX_LEVEL_NUMBER_VIOLATION): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: Windows detected an invalid mutex hierarchy or acquisition level in kernel mode.

Could be also:
Constant	Type	OS
ERROR_INVALID_DATA	Win32 error	Windows
KERN_NAME_EXISTS	Kern return	Mac
ippStsLSFLow	Intel Ipp Status	Any
EACCES	errno	Any

MUTEX_LEVEL_NUMBER_VIOLATION

Kernel mutex level ordering violation

MUTEX_LEVEL_NUMBER_VIOLATION is bug check code 0x0000000D. This bug check points at a lock-ordering rule being broken in kernel synchronization. It is useful when the dump shows mutex, guarded mutex, executive resource, or driver-owned lock paths that can deadlock if acquired in the wrong hierarchy.

How to read it in a dump

Use the stack to identify which thread and which driver was acquiring or releasing the lock.
The important evidence is the lock object and acquisition order, not just the symbolic stop code.
Do not treat it as a user-mode mutex failure; this is kernel synchronization state.

What to check

Review lock hierarchy and driver paths that acquire multiple locks.
Enable Driver Verifier deadlock detection for suspect drivers in a test reproduction.
Look for recent changes in cancel, unload, power, or error paths where lock ordering may differ from the normal path.

References

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