Big DPC/ISR latency issues and can't open windows performance recorder

Question

Big DPC/ISR latency issues and can't open windows performance recorder

Martin Banatovski 0

I'm trying to diagnose a DPC/ISR latency issue, that has been bothering me for almost a year now. Updated drivers countless times to different versions, reset windows nothing seems to fix it. I'm trying to gather proof that it is a hardware problem, so I can send my laptop back and windows performance recorder seemed a good first step. The only problem is I can't open windows performance recorder since it is giving me an Not enough memory resources are available to complete this operation with error code 0x8007000e. I have 64 GB of ram, with 50 GB being free.
Any other methods of diagnosing latency issues are also kindly appreciated.

Gary Nebbett 6,476 Reputation points

2026-03-11T08:38:18.7833333+00:00

Hello Martin,

How big is your .etl file? I would guess that it could be several gigabytes.

Windows Performance Recorder (WPR) and Windows Performance Analyzer (WPA) are good tools for analysing DPC/ISR problems, but troubleshooting is often an iterative process. You may have tried to gather too much information over too long a period - I often start with a short (in time) trace to form an impression of what might be happening and then "tune" the trace (customize the set of events to be captured, omitting less helpful events) if a longer period needs to be traced.

If you are willing to share your captured trace data, details of the behaviour that you believe to be due to DPC/ISR latency, etc. then I will take a look at it.

Gary
Martin Banatovski 0 Reputation points

2026-03-15T21:30:52.1933333+00:00

Hi Gary,

I can't open WPR. I don't have an .etl file I can look at. The error I mentioned happens when opening WPR.
Gary Nebbett 6,476 Reputation points

2026-03-16T08:35:44.01+00:00
Hello Martin,

Sorry for not reading your question carefully enough.

When exactly does the problem occur? Every time you issue the command "wpr" or "wprui" or when you try to start a profile ("wpr -start" or pushing the start button in wprui)?

If the problem occurs when trying to start a profile, then which profile are you trying to start?

The default profiles can be exported (wpr -exportprofile) and the buffering parameters adjusted - that might help.

<WindowsPerformanceRecorder Version="1.0"> <Profiles> <SystemCollector Id="WPR_initiated_WprApp_WPR_System_Collector" Name="WPR_initiated_WprApp_WPR System Collector"> <BufferSize Value="1024" /> <Buffers Value="20" /> </SystemCollector> <EventCollector Id="WPR_initiated_WprApp_WPR_Event_Collector" Name="WPR_initiated_WprApp_WPR Event Collector"> <BufferSize Value="1024" /> <Buffers Value="20" /> </EventCollector>

Tools other than WPR can be used to control a trace; some examples are "netsh trace", logman, pktmon, PowerShell cmdlets.

Gary
Martin Banatovski 0 Reputation points

2026-03-17T16:27:18.0933333+00:00

The error is when opening the wprui app (both cmd by typing wprui and from start menu). Ill try messing around with the CLI version
Gary Nebbett 6,476 Reputation points

2026-03-17T18:06:04.7666667+00:00

Hello Martin,

That is bad news - there is probably more than one problem with your PC.

Gary