Determining Why the Reflector Terminated the Host Process

This topic describes how you can analyze why the reflector terminated the driver host process (WUDFHost.exe).

The most common reason for the reflector to terminate the host process is the expiration of UMDF host process timeouts.

Using Dump Files

For many crashes, dump file details are sufficient to determine why the termination occurred. To review dump file information, follow these steps:

  1. Locate the latest .dmp file in the %windir%\system32\LogFiles\WUDF directory.

  2. Load the latest .dmp file into the debugger by using the following command:
    
    WinDbg -z <path to the .dmp file>
    
    
  3. Look at the state of the threads at the time of termination.

Using the Debugger

In other cases, you might need to attach to a live kernel-mode target to determine why the reflector terminated the host process. To set up your debugging session, follow the steps described in How to Enable Debugging of a UMDF Driver.

Once you have established a connection, display the outstanding IRPs by using the !wdfkd.wdfumirps UMDF debugger extension (!wudfext.umirps for UMDF version 1).

  • If a PnP IRP or a power IRP is pending, determine why the driver causes the IRP to hang by examining threads in the host process.

    You can use the !process extension to examine the threads running in the host process. The 0x1f flags value shows you the stack trace for each thread.

    !process <process addr> 0x1f

  • If your driver has not completed a canceled IRP quickly, determine which IRP was canceled and why it has not completed.
  • If a cleanup or close IRP is pending, determine why the IRP is taking a long time to process.

 

 

Send comments about this topic to Microsoft

Mostra:
© 2014 Microsoft