| Previous | Next |
| STATUS_VIDEO_HUNG_DISPLAY_DRIVER_THREAD | STATUS_FLT_CONTEXT_ALREADY_DEFINED |
STATUS_FLT_NO_HANDLER_DEFINED
This status points to the minifilter's operation-registration contract. Filter Manager dispatches only the pre-operation and post-operation callbacks that the driver registered for a given I/O operation; it is not a report that the file system rejected the user's request.
Check the FLT_OPERATION_REGISTRATION table used during FltRegisterFilter: the intended major function must have the correct callback pointers, and the table must retain its required terminator. Also verify that the operation in the trace is the one the driver intended to observe; create, cleanup, close, section synchronization, and fast-I/O related paths are distinct registrations.
Diagnostic boundary
- Compare the major/minor operation in the callback data with the driver's registered table.
- Inspect the active instance stack and the altitude ordering before assuming that another filter skipped an operation.
- Fix the registration or dispatch design rather than retrying the user I/O request.
Filter Manager concepts | Writing callback routines | NTSTATUS reference
Looking for a different code? Search another status or error code.