| Previous | Next |
| STATUS_FLT_DELETING_OBJECT | STATUS_FLT_DUPLICATE_ENTRY |
STATUS_FLT_MUST_BE_NONPAGED_POOL
This status is about memory residency for a Filter Manager context. The relevant context can be accessed where pageable memory is not permitted, so the registered allocation and cleanup design must provide nonpaged storage.
Do not fix the symptom by changing only an allocation tag or by manually allocating an unrelated structure. Check the context type and its FLT_CONTEXT_REGISTRATION entry, the pool flags requested from Filter Manager, and every callback that may touch the context. The context lifetime still belongs to Filter Manager and must follow its reference-count rules.
Review checklist
- Context type, registration flags, allocation size, and cleanup callback.
- Whether code accesses the context in paths that cannot tolerate pageable memory.
- References held across teardown and the code that calls
FltReleaseContext.
Managing minifilter contexts | FltAllocateContext | NTSTATUS reference
Looking for a different code? Search another status or error code.