| Previous | Next |
| STATUS_NDIS_INTERFACE_NOT_FOUND | STATUS_NDIS_INVALID_PORT |
STATUS_NDIS_UNSUPPORTED_REVISION
The structure family is recognized, but its revision is not
STATUS_NDIS_UNSUPPORTED_REVISION is more specific than a bad global NDIS version. The framework or miniport recognized the request structure family, but the caller supplied a revision that the target does not support.
For OID processing, the request and result structures carry revision information so a driver can report the supported revision. Correct recovery is to negotiate or build the documented compatible revision, not to truncate fields opportunistically.
Evidence that narrows it
- Log header type, revision, size, all optional fields present, and the supported revision reported by the target when available.
- Build the structure using the revision constants for the deployed NDIS and WDK target, not merely the newest header on the build machine.
- Keep revision compatibility separate from a bad OID value or insufficient buffer size.
References
- Microsoft: Handling OID requests in a miniport adapter
- Microsoft: NDIS_OID_REQUEST structure
- Microsoft: MiniportOidRequest
Looking for a different code? Search another status or error code.