| Previous | Next |
| STATUS_NDIS_INVALID_DEVICE_REQUEST | STATUS_NDIS_INVALID_LENGTH |
STATUS_NDIS_ADAPTER_NOT_READY
The adapter is present, but not operational for this request
STATUS_NDIS_ADAPTER_NOT_READY distinguishes presence from readiness. An adapter can have a valid device and binding identity while initialization, restart, power, port, or other lifecycle work prevents it from completing the requested operation.
The correct evidence is adapter state and timing. In NDIS 6, adapters move through Initializing, Paused, Restarting, Running, and Pausing states, and OID handling has different constraints from send and receive traffic.
Evidence that narrows it
- Record the miniport state, last successful restart or initialization event, and the request class that failed.
- Check for overlapping reset, power, port, or PnP activity before assuming a permanent hardware fault.
- Compare with
STATUS_NDIS_ADAPTER_NOT_FOUND: this result retains a target but cannot yet service the operation.
References
- Microsoft: NDIS driver stack
- Microsoft: Miniport adapter states and operations
- Microsoft: Stopping a driver stack
Looking for a different code? Search another status or error code.