| Previous | Next |
| STATUS_NDIS_LOW_POWER_STATE | STATUS_NDIS_NOT_SUPPORTED |
STATUS_NDIS_REINIT_REQUIRED
The current miniport instance cannot continue without reinitialization
STATUS_NDIS_REINIT_REQUIRED signals that the requested operation cannot be completed by the current miniport instance without returning through initialization or a reinitialization path. It is stronger than a temporary not-ready result, because the existing operational context is not sufficient to continue safely.
Capture the event that made reinitialization necessary: configuration replacement, hardware recovery, driver state loss, or a change whose effect cannot be applied in place. A blind application retry does not recreate miniport state.
Evidence that narrows it
- Record the preceding operation, adapter state, and any reset, PnP, power, or driver-update events.
- Ensure the component that owns the miniport performs its documented stop, initialize, restart, and binding lifecycle.
- After reinitialization, verify capabilities and port or interface identities again instead of reusing stale cached data.
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.