| Previous | Next |
| STATUS_INVALID_LABEL | STATUS_AMBIGUOUS_SYSTEM_DEVICE |
STATUS_DRIVER_PROCESS_TERMINATED
The hosted driver lost its execution process
UMDF drivers run in a host process rather than directly in the kernel. An unhandled exception, fail-fast, external termination or framework timeout can end that process and invalidate every device stack pooled in it. The hardware may remain present, but requests cannot continue until the framework restarts or re-enumerates the host.
Investigate the host crash or timeout before blaming the physical device. Pooling means one faulty driver can terminate a process containing other devices. Capture user-mode dumps, WDF logs and the list of modules hosted in that specific process instance.
What to inspect
- Collect the WUDFHost process dump, exception code and WDF framework logs.
- Identify every UMDF device stack pooled in the terminated host.
- Check callback duration, deadlocks and external process termination before restarting the device.
References
- Microsoft: Debugging UMDF 2 drivers
- Microsoft: Device objects and device stacks
- Microsoft Open Specifications: NTSTATUS values
- ReactOS source: driver loading and I/O manager
Looking for a different code? Search another status or error code.