| Previous | Next |
| ERROR_NOT_SAFE_MODE_DRIVER | ERROR_DEVICE_ENUMERATION_ERROR |
ERROR_FAILED_DRIVER_ENTRY
The driver image loaded far enough to call DriverEntry, but initialization failed
DriverEntry is the kernel driver initialization entry point. It initializes driver-wide state and registers standard entry points such as AddDevice, dispatch routines, and optionally Unload. Returning failure from DriverEntry prevents the driver from becoming available to manage its devices.
This status is more specific than a missing or blocked driver image: execution reached the driver's initialization code. Debug the return path from DriverEntry and any initialization routine it calls. Check configuration data, allocation failures, framework initialization, and global resources acquired before the failure. Cleanup must also be correct on every error path because partially initialized state can affect later load attempts. SetupAPI and System logs can identify the package and service, but the root cause often requires driver tracing or a kernel debugger at module load.
What to inspect
- Capture the exact DriverEntry return status before it is mapped to Win32.
- Audit initialization and cleanup paths executed before the failure return.
- Break on driver load or enable driver tracing to locate the first failed initialization step.
References
Looking for a different code? Search another status or error code.