Determining Why UMDF Indicates Outstanding Files at Device Removal Time
You can perform the following steps to determine why UMDF indicates that there are outstanding files when you remove a device:
Use the !wudfext.umdevstack UMDF debugger extension to dump the device stack. The dump includes outstanding UMDF intra-stack files (that is, file objects that a driver in the stack created as opposed to file objects that were created by an application or by a driver in another stack).
For each intra-stack file, run the !wudfext.umfile UMDF debugger extension as shown in the following example to obtain information about the file:
The output includes the list of IRPs that are pending.
Determine why each IRP is outstanding by using the !wudfext.umirp UMDF debugger extension to obtain information about the IRP, as shown in the following example:
From the output of each !wudfext.umirp:
- Determine if the IRP completed.
- Determine if a driver-created request was not deleted either explicitly by the driver or implicitly by the object tree.
Build date: 4/1/2013