| Previous | Next |
| STATUS_NDIS_INVALID_LENGTH | STATUS_NDIS_BUFFER_TOO_SHORT |
STATUS_NDIS_INVALID_DATA
The structure is accepted, but its requested value is not
STATUS_NDIS_INVALID_DATA identifies an OID-specific validation failure. NDIS does not validate the contents of every OID payload on behalf of the miniport; the driver must reject values that are out of range, malformed, or incompatible with the hardware and current configuration.
This differs from invalid length. A buffer can be correctly sized and aligned yet still contain an illegal enumeration value, address, bitmask, capability combination, or configuration request.
Evidence that narrows it
- Capture the decoded OID value rather than only its raw buffer, including all bit flags and enumerations.
- Compare the requested value with the adapter capabilities and the OID-specific valid ranges.
- Preserve the returned status before retrying with defaults, because an automatic fallback can conceal which policy or value was rejected.
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.