| Previous | Next |
| STATUS_ACCOUNT_EXPIRED | STATUS_NETWORK_CREDENTIAL_CONFLICT |
STATUS_POSSIBLE_DEADLOCK
The observed lock order can form a deadlock cycle
A possible-deadlock condition is about acquisition order, not necessarily a system that is already frozen. Driver Verifier deadlock detection builds a graph of resource acquisition order and looks for loops. A cycle means two or more code paths can acquire shared locks in incompatible orders and may deadlock when the timing aligns.
Collect the lock graph, owning threads and stacks for both acquisition orders. The correct fix is normally to define one global lock hierarchy, reduce nested ownership, or redesign the handoff. Timeouts and extra retries only change how long the deadlock is visible. For kernel investigations, the !deadlock debugger extension can display verifier-tracked topology.
What to inspect
- Capture both lock-order paths that create the cycle.
- Establish and enforce one acquisition hierarchy across shared code.
- Use Driver Verifier deadlock detection and debugger lock data before changing timeout values.
References
Looking for a different code? Search another status or error code.