| Previous | Next |
| INVALID_RUNDOWN_PROTECTION_FLAGS | ERESOURCE_INVALID_RELEASE |
INVALID_SLOT_ALLOCATOR_FLAGS
INVALID_SLOT_ALLOCATOR_FLAGS is bug check 0x16D. Microsoft's public contract is narrow: flags supplied to a slot-allocator API were invalid, and parameter 1 contains the rejected flags value. Parameters 2 through 4 are reserved.
Do not infer a public slot format
The bug-check page does not publish the allocator's internal slot structure or a universal set of flag meanings. Diagnose the caller visible in the dump, resolve the function and module, and compare the flags against the contract for the actual API used in that build.
Likely code-review questions
- Was the flags variable initialized before the call?
- Did a wrapper combine bits from another flag namespace?
- Can stale structure data or a truncation/sign conversion reach the flags argument?
The rejected value in parameter 1 is direct evidence; memory or storage tests are not a substitute for tracing how that value was constructed.
References
- Microsoft: Bug Check 0x16D INVALID_SLOT_ALLOCATOR_FLAGS
- Microsoft: !analyze extension
- Microsoft: ln command
Looking for a different code? Search another status or error code.