BSOD 20 (CREATE_DELETE_LOCK_NOT_LOCKED): causes and diagnosis

Status / error code:		Category:

Constant name:
Source:		Operating System:
Description: The kernel detected create/delete lock state that was not held when required.

Could be also:
Constant	Type	OS
ERROR_BAD_UNIT	Win32 error	Windows
KERN_INVALID_CAPABILITY	Kern return	Mac
ippStsNonIntelCpu	Intel Ipp Status	Any
ENOTDIR	errno	Any

CREATE_DELETE_LOCK_NOT_LOCKED

Object lifetime create/delete lock violation

CREATE_DELETE_LOCK_NOT_LOCKED is bug check code 0x00000014. This code indicates an internal object-lifetime path was entered without the required protection. It is useful when the dump points at handle, process, thread, or object manager creation/deletion state.

How to read it in a dump

The important clue is which object type is being created or deleted.
The stop code alone does not identify a user-mode handle problem; it indicates kernel synchronization around object lifetime.
Look for stack frames in object manager, process/thread, security, or a third-party callback.

What to check

Review object callbacks and drivers that participate in process, thread, handle, or image events.
Check for memory corruption around executive objects.
Use Driver Verifier on file-system, security, and monitoring drivers involved in object lifetime.

References

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