| Previous | Next |
| STATUS_NDIS_ADAPTER_NOT_READY | STATUS_NDIS_INVALID_DATA |
STATUS_NDIS_INVALID_LENGTH
The length is structurally wrong, not merely insufficient for a result
STATUS_NDIS_INVALID_LENGTH means the size presented for a request is not valid under the receiving contract. This can involve an incorrect structure size, a header whose declared size disagrees with the buffer, or an OID-specific fixed or variable-length layout that cannot be parsed safely.
Do not collapse it into buffer-too-short. A too-short output buffer can often be resized using returned requirements, whereas an invalid length can also mean that the request was constructed with the wrong revision or shape.
Evidence that narrows it
- Log the request header type, revision, declared size, information-buffer length, and bytes written or needed fields.
- Verify the caller uses the exact structure and size required by the selected OID and NDIS revision.
- Compare with
STATUS_NDIS_BUFFER_TOO_SHORTonly after confirming the structure itself is valid.
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.