| Previous | Next |
| STATUS_NDIS_ALREADY_MAPPED | STATUS_NDIS_MEDIA_DISCONNECTED |
STATUS_NDIS_RESOURCE_CONFLICT
A required adapter hardware resource conflicts with another device or driver
STATUS_NDIS_RESOURCE_CONFLICT belongs to miniport initialization and Plug and Play resource assignment. The conflict is about local hardware resources such as memory ranges, I/O ports, interrupts, DMA, or bus resources that the miniport needs before it can operate the network adapter.
Do not treat it as a DHCP, DNS, or remote server failure. The adapter may never reach a running state. Review the PnP resource list, bus driver assignments, device instance history, and whether another driver has already claimed the same range or interrupt. Virtual NICs can show similar failures when the virtual bus exposes inconsistent resources.
Evidence that narrows it
- Capture the translated and raw resource lists supplied to the miniport.
- Compare resource ownership with Device Manager, setup logs, and bus-driver diagnostics.
- Check whether the conflict appears only after hot-plug, docking, firmware update, or virtualization changes.
References
- Microsoft: Initializing a miniport adapter
- Microsoft: Miniport adapter states and operations
- Microsoft: NDIS driver stack
- Microsoft: MS-ERREF NTSTATUS values
Looking for a different code? Search another status or error code.