| Previous | Next |
| STATUS_NDIS_INVALID_DATA | STATUS_NDIS_INVALID_OID |
STATUS_NDIS_BUFFER_TOO_SHORT
The request needs more buffer space, not a different operation
STATUS_NDIS_BUFFER_TOO_SHORT is a capacity failure for the submitted buffer. It commonly occurs when a query returns a variable-length list or when a caller assumes a fixed structure size for data whose actual count depends on the adapter or current configuration.
It should lead to a size-aware retry only after checking the OID contract. Blindly allocating a large constant buffer can mask integer-overflow, revision, or ownership errors and still fail on a future adapter with a larger result.
Evidence that narrows it
- Read and log any bytes-needed or required-length value returned by the driver or API.
- Validate arithmetic for count, element size, alignment, and header length before allocating the retry buffer.
- Do not confuse this with
STATUS_NDIS_INVALID_LENGTH, which can mean the request format itself is invalid.
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.