| Previous | Next |
| CLUSTER_CSV_CLUSTER_WATCHDOG_LIVEDUMP | INVALID_SLOT_ALLOCATOR_FLAGS |
INVALID_RUNDOWN_PROTECTION_FLAGS
INVALID_RUNDOWN_PROTECTION_FLAGS reports invalid flags supplied to a rundown-protection API. Parameter 1 contains the rejected flags and parameter 2 is the address of the rundown reference. The stop is about the API arguments; it is not itself proof that rundown protection leaked or that teardown waited forever.
What to inspect in the caller
Resolve the stack to the routine that assembled parameter 1. Verify that the flags belong to the exact rundown API being called and were initialized on every path. The rundown-reference address from parameter 2 can be mapped back to the owning device, object, or driver structure.
Keep flag validity separate from lifetime bugs
Rundown protection is used to prevent an object from disappearing while users still hold protected access. A separate design error can misuse acquire/release or teardown sequencing, but this specific bug check says the immediate detected violation was the flags argument. Start there before broad synchronization changes.
References
Looking for a different code? Search another status or error code.