Debugging Tools for Windows

!wudfext.umirps

The !wudfext.umirps extension displays the list of pending I/O request packets (IRPs) in the host process.

Syntax

!wudfext.umirps [number-to-dump] [Flags]

Parameters

number-to-dump
Optional. Specifies the number of pending IRPs to display information about. The default value is 10.
Flags
Optional. Specifies the type of information to be displayed. Flags can be any combination of the following bits. The default value is 0x01.
Bit 0 (0x01)
Displays details about the pending IRPs.

DLL

Windows NT 4.0 Unavailable
Windows 2000 Unavailable
Windows XP and later Wudfext.dll

Comments

The list of pending IRPs that are displayed have either been presented to the driver or are waiting to be presented to the driver.

By default, !wudfext.umirps shows only the first ten IRPs. However, you can use the number-to-dump parameter to expand the displayed number of IRPs.

The following is an example of the !wudfext.umirps display:

kd> !umirps 
Number of pending IRPS: 0xc8
####  CWudfIrp          Type        UniqueId          KernelIrp
----  ----------------  ----------  ----------------  ---------
0000            3dd280        READ                dc  856f02f0
0001            3dd380       WRITE                dd  85b869e0
0002            3dd480        READ                de  85377850
0003            3dd580        READ                df  93bba4e8
0004            3dd680       WRITE                e0  84cb9d70
0005            3dd780        READ                e1  85bec150
0006            3dd880       WRITE                e2  86651db0
0007            3dd980        READ                e3  85c22818
0008            3dda80        READ                e4  9961d150
0009            3ddb80       WRITE                e5  85c15148


You can use the values in the UniqueId and KernelIrp columns to match a UMDF IRP (or UM IRP) to a corresponding kernel IRP. You can pass the values in the CWudfIrp column to the !wudfext.umirp extension to determine the framework IWDFRequest objects that each layer in the device stack can access.

Additional Information

For more information, see User-Mode Driver Framework Debugging.

Build machine: CAPEBUILD