Use !wdfkd.wdfdriverinfo MyDriver.dll 0x10 to display the device tree in verbose form. In Windows 8.1, the reflector times out after one minute. cache forcedecodeuser and lmu to verify that your driver is hosted in the current process.Įxamine thread call stacks ( !thread Address) to determine if a driver callback timed out. process /r /p Process to switch process context to that of the Wudfhost process that is hosting your driver. You can then click on the process address to display information specific to that process.

When you click on the image name of a UMDF driver, the debugger displays the address of the hosting process. You can also use !wdfkd.wdfumtriage and !wdfkd.wdfldr to display all drivers that are currently bound to WDF. Use !process 0 0x1f wudfhost.exe to list all Wudfhost.exe driver host processes, including thread stack information. Use !analyze to display information about the failure, and additional UMDF extension commands you can try. **** Note that driver host process may get terminated if you go past this break, making it difficult to debug the problem! **** Helpful UMDF debugger extension commands: !wdfkd.wdfhelp **** Dump UMDF trace log: !wmitrace.logdump WUDFTrace **** Dump UM Irps for this stack: !wdfkd.wdfumirps 0x000000BEBB49AE20 **** Dump UMDF driver image name and stack: !wdfkd.wdfumdevstack 0x000000BEBB49AE20 For example: **** Problem detected in UMDF driver 'WUDFOsrUsbFx2'.

In the debugger output, you will see several suggestions on how to begin, including links you can click on. If HostFailKdDebugBreak is set (this should be enabled by default starting Windows 8), the reflector breaks into the kernel-mode debugger when the timeout threshold is exceeded. AppVerif –enable Heaps Exceptions Handles Locks Memory TLS Leak –for WudfHost.exe Use the following command, attach a kernel debugger and then reboot. We strongly recommend doing all development and testing of your UMDF driver with a kernel debugger attached to the test system and enabling Application Verifier (AppVerif.exe) on WUDFHost.exe. To investigate, first set up a kernel-mode debugging session as described in How to Enable Debugging of a UMDF Driver. In this case, the reflector terminates the driver host process. If the driver host process is terminated, your driver might have a problem in a callback that results in the host timeout threshold being exceeded. Determining Why a UMDF 2.0 Driver Crashed This topic describes which commands you might start with to troubleshoot UMDF driver problems.

Starting in User-Mode Driver Framework (UMDF) version 2, you can use a subset of the debugger extension commands implemented in Wdfkd.dll to debug a UMDF driver.

Reflector 2 troubleshooting