Occasionally I come across servers (Windows 2003 and 2008) with high processor % interrupt time. Is there a way to see what program or device is causing the interrupts?
After digging through the documentation (based on the other answers here), this is the process I ended up using:
Capture the ETW log of the problem
The easiest way to do this is using the Windows Performance Recorder. I'm not sure when it first appeared, but seems to be built in on recent versions of Windows. Set the profile to
or, using an elevated command prompt, navigate to the folder which contains it and use the command-line tool xperf:
xperf -on base+interrupt+dpc
Note, you will need to close Process Monitor or any other app which uses ETW or you will get the following error:
xperf: error: NT Kernel Logger: Cannot create a file when that file already exists. (0xb7).
Stop tracing / save the log
xperf -d interrupt_trace.etl
Open the trace in
Windows Performance Analyzer(part of Windows Performance Toolkit); some places mention using
CPU Usage (Sampled)->
DPC and ISR Usage by Module, Stack, right-click and
add graph to analysis view
This pointed right to the driver in question. In this case, HDAudBus.sys is using a constant 10.82% of my cpu via interrupts, which is exactly what Process Explorer was showing me.
If you can handle low-level system tools;
Windows Performance Analyzer (WPA) is a set of performance monitoring tools used to produce in-depth performance profiles of Microsoft Windows operating systems and applications.
After you learn how to use xperf; check out;
The DPC/ISR action produces a text report that summarizes the various metrics regarding DPCs and ISRs. The usage for this action is:
Copy Code -a dpcisr [-dpc -isr -summary -interval [n] -bucket [n] -range T1 T2 ]
Show statistics for DPC only
Show statistics for ISR only
Show summary report
Show usage report for intervals of dt, default is 1 second
Show histogram for intervals of dt, default is 2 seconds
range T1 T2
Show delays between T1 and T2
If no data type is specified, default is to show report for both DPC
and ISR. If no report type is specified, default is to print all three kinds of report.
Here's the best article I've found on how to do this, with tutorials, screenshots, and download links to the relevant tools:
Have a look at the Windows Process Explorer:
That should help.