Protocol Driver Reset Operations

Protocol drivers cannot initiate a reset operation in NDIS 6.0 and later versions.

Typically, an underlying miniport driver resets a NIC because the NIC is timing out during send or request operations. This condition causes NDIS to call the miniport driver's MiniportCheckForHangEx and subsequently MiniportResetEx functions. Alternatively, the miniport driver determines a NIC's receive capability is dysfunctional.

If a reset is initiated by NDIS and MiniportResetEx returns NDIS_STATUS_PENDING, NDIS calls the ProtocolStatusEx(or ProtocolCoStatusEx) function of each bound protocol driver with a status of NDIS_STATUS_RESET_START. When the miniport driver calls NdisMResetComplete, NDIS again calls ProtocolStatusEx(or ProtocolCoStatusEx) with a status of NDIS_STATUS_RESET_END.

A protocol driver must handle the possibility that outstanding sends on a binding to an underlying NIC can be canceled because the NIC is reset. If a bound protocol driver has any transmit requests pending, NDIS will indicate a send complete to the protocol driver with an appropriate status. The protocol driver must resubmit the send requests when the reset operation is completed, assuming the NIC becomes operational again.

When a protocol driver receives a status of NDIS_STATUS_RESET_START, it should:

  • Hold any network data that is ready to be transmitted until Protocol(Co)Status receives an NDIS_STATUS_RESET_END notification.

  • Not make any NDIS calls that are directed to the underlying miniport driver, except calls to return resources such as returning network data with NdisReturnNetBufferLists.

After ProtocolStatusEx(or ProtocolCoStatusEx) receives an NDIS_STATUS_RESET_END message, the protocol driver can resume sending network data and OID requests.