| Previous | Next |
| ERROR_INCOMPATIBLE_SERVICE_SID_TYPE | ERROR_IMPLEMENTATION_LIMIT |
ERROR_DRIVER_PROCESS_TERMINATED
The UMDF host process ended while I/O was still outstanding
User-Mode Driver Framework drivers run inside WUDFHost rather than directly in the application process. If the driver host fails or the reflector terminates it, outstanding requests can complete to Win32 callers with ERROR_DRIVER_PROCESS_TERMINATED. The framework can then report a PnP host problem and attempt to restart the device.
Treat this as a driver-host failure boundary. Check UMDF WER reports, trace logs, and System events 10110 through 10112. A crash, unhandled exception, verifier failure, or timeout of a critical PnP, power, or cancellation callback can terminate the host. Also close stale application handles after the failure: Windows does not tear down and restart the old device stack until handles to it are closed. Retrying I/O forever against the old handle is therefore the wrong recovery model.
What to inspect
- Inspect UMDF WER dumps and WudfTrace for the host instance.
- Check System events 10110, 10111, and 10112 around the failure.
- Close handles to the failed stack and reopen the device after restart.
References
- Microsoft: how UMDF handles driver failures
- Microsoft: UMDF host process timeouts
- Microsoft: how UMDF handles driver failures
Looking for a different code? Search another status or error code.