| Previous | Next |
| STATUS_ACCESS_DISABLED_BY_POLICY_OTHER | STATUS_DEVICE_ENUMERATION_ERROR |
STATUS_FAILED_DRIVER_ENTRY
DriverEntry rejected initialization
The I/O manager calls DriverEntry after mapping the image and resolving imports. DriverEntry initializes driver-wide objects, dispatch entry points and resources; PnP device initialization normally occurs later in AddDevice and start-device handling. This status therefore points to global initialization rather than failure of one already started device.
Preserve the exact NTSTATUS returned by DriverEntry. Common causes include unavailable dependencies, invalid configuration, allocation failure or a failed framework initialization call. A driver must unwind every resource it acquired before returning failure, or subsequent load attempts can behave differently.
What to inspect
- Break on DriverEntry return and record the first failing initialization call.
- Check service parameters and system resources read before AddDevice is invoked.
- Verify cleanup of symbolic links, callbacks, lookaside lists and framework objects on failure.
References
- Microsoft: Writing a DriverEntry routine
- Microsoft: Standard driver routines
- 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.