| Previous | Next |
| STATUS_INVALID_PLUGPLAY_DEVICE_PATH | STATUS_DRIVER_ENTRYPOINT_NOT_FOUND |
STATUS_DRIVER_ORDINAL_NOT_FOUND
The driver binary and its dependency are incompatible
PE images can import functions by name or ordinal. An ordinal is meaningful only for the exact export table expected by the producer. This status occurs when loader resolution cannot find the requested ordinal in a dependent kernel image, often after mixing binaries from different versions or loading a third-party module built against an unsupported dependency.
Copying a DLL or SYS file from another computer is unsafe and can create a larger version mismatch. Determine the importing image and dependency from loader diagnostics, then restore a matched driver package or operating-system component. Kernel drivers should use documented WDK interfaces instead of private ordinal contracts.
What to inspect
- Inspect the driver import table and identify the image that should provide the ordinal.
- Compare file versions, architecture and package provenance for every dependency.
- Restore or update the complete signed package rather than replacing one binary.
References
- Microsoft: PE/COFF image format
- Microsoft: Driver Store
- Microsoft: SetupAPI and Code Integrity diagnostics
- Microsoft Open Specifications: NTSTATUS values
- ReactOS source: driver loading and I/O manager
Looking for a different code? Search another status or error code.