High Latency on Wdf01000.sys driver causing Real Time Audio Playback issues

Anonymous
2022-12-20T11:06:29+00:00

Hi

I have ran Latency Mon as I am getting issues when using using my Traktor Kontrol s3 DJ controller causing real time audio play back issues and the above driver is reporting Highest execution of over 5.83 which appears to be causing the audio issues - have you any advice on what I can do to improve this?

Windows/drivers/BIOS are all up to date

Info below

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: LAPTOP-RP5HJ9VC

OS version: Windows 11, 10.0, version 2009, build: 22621 (x64)

Hardware: 81NC, LENOVO

BIOS: AMCN25WW(V1.08)

CPU: AuthenticAMD AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx

Logical processors: 8

Processor groups: 1

Processor group size: 8

RAM: 6082 MB total

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed (WMI): 230 MHz

Reported CPU speed (registry): 2296 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

Windows 11 Version 22H2 (OS Build 22621.963)

I am not aware of any changes prior to my my issue

_________________________________________________________________________________________________________

CONCLUSION

_________________________________________________________________________________________________________

Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns

appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing

for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for

BIOS updates.

LatencyMon has been analyzing your system for 0:09:40 (h:mm:ss) on all processors.

_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: LAPTOP-RP5HJ9VC

OS version: Windows 11, 10.0, version 2009, build: 22621 (x64)

Hardware: 81NC, LENOVO

BIOS: AMCN25WW(V1.08)

CPU: AuthenticAMD AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx

Logical processors: 8

Processor groups: 1

Processor group size: 8

RAM: 6082 MB total

_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed (WMI): 230 MHz

Reported CPU speed (registry): 2296 MHz

Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed

Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

_________________________________________________________________________________________________________

MEASURED INTERRUPT TO USER PROCESS LATENCIES

_________________________________________________________________________________________________________

The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the

moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an

event and the waking up of a usermode thread from an idle wait state in response to that event.

Highest measured interrupt to process latency (µs): 418.20

Average measured interrupt to process latency (µs): 18.544421

Highest measured interrupt to DPC latency (µs): 399.30

Average measured interrupt to DPC latency (µs): 5.148406

_________________________________________________________________________________________________________

REPORTED ISRs

_________________________________________________________________________________________________________

Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

Highest ISR routine execution time (µs): 72.415941

Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total ISR routine time (%): 0.008239

Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in ISRs (%) 0.008239

ISR count (execution time <250 µs): 68316

ISR count (execution time 250-500 µs): 0

ISR count (execution time 500-1000 µs): 0

ISR count (execution time 1000-2000 µs): 0

ISR count (execution time 2000-4000 µs): 0

ISR count (execution time >=4000 µs): 0

_________________________________________________________________________________________________________

REPORTED DPCs

_________________________________________________________________________________________________________

DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it

is interrupted until the DPC has finished execution.

Highest DPC routine execution time (µs): 5830.930749

Driver with highest DPC routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total DPC routine time (%): 0.116586

Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.246767

DPC count (execution time <250 µs): 537267

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-10000 µs): 210

DPC count (execution time 1000-2000 µs): 1

DPC count (execution time 2000-4000 µs): 1

DPC count (execution time >=4000 µs): 1

_________________________________________________________________________________________________________

REPORTED HARD PAGEFAULTS

_________________________________________________________________________________________________________

Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped

file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and

blocked from execution.

NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream

resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

Process with highest pagefault count: msmpeng.exe

Total number of hard pagefaults 49848

Hard pagefault count of hardest hit process: 23033

Number of processes hit: 76

_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 29.199812

CPU 0 ISR highest execution time (µs): 72.415941

CPU 0 ISR total execution time (s): 0.382205

CPU 0 ISR count: 68295

CPU 0 DPC highest execution time (µs): 5830.930749

CPU 0 DPC total execution time (s): 9.460795

CPU 0 DPC count: 353658

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 3.327245

CPU 1 ISR highest execution time (µs): 12.952526

CPU 1 ISR total execution time (s): 0.000158

CPU 1 ISR count: 21

CPU 1 DPC highest execution time (µs): 199.577091

CPU 1 DPC total execution time (s): 0.131493

CPU 1 DPC count: 16616

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 5.915394

CPU 2 ISR highest execution time (µs): 0.0

CPU 2 ISR total execution time (s): 0.0

CPU 2 ISR count: 0

CPU 2 DPC highest execution time (µs): 653.486498

CPU 2 DPC total execution time (s): 0.450144

CPU 2 DPC count: 39039

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 3.192211

CPU 3 ISR highest execution time (µs): 0.0

CPU 3 ISR total execution time (s): 0.0

CPU 3 ISR count: 0

CPU 3 DPC highest execution time (µs): 76.172474

CPU 3 DPC total execution time (s): 0.154109

CPU 3 DPC count: 17995

_________________________________________________________________________________________________________

CPU 4 Interrupt cycle time (s): 5.699611

CPU 4 ISR highest execution time (µs): 0.0

CPU 4 ISR total execution time (s): 0.0

CPU 4 ISR count: 0

CPU 4 DPC highest execution time (µs): 223.598868

CPU 4 DPC total execution time (s): 0.369758

CPU 4 DPC count: 30900

_________________________________________________________________________________________________________

CPU 5 Interrupt cycle time (s): 4.162972

CPU 5 ISR highest execution time (µs): 0.0

CPU 5 ISR total execution time (s): 0.0

CPU 5 ISR count: 0

CPU 5 DPC highest execution time (µs): 127.471690

CPU 5 DPC total execution time (s): 0.233076

CPU 5 DPC count: 26874

_________________________________________________________________________________________________________

CPU 6 Interrupt cycle time (s): 4.355492

CPU 6 ISR highest execution time (µs): 0.0

CPU 6 ISR total execution time (s): 0.0

CPU 6 ISR count: 0

CPU 6 DPC highest execution time (µs): 195.680314

CPU 6 DPC total execution time (s): 0.374942

CPU 6 DPC count: 31047

_________________________________________________________________________________________________________

CPU 7 Interrupt cycle time (s): 3.526148

CPU 7 ISR highest execution time (µs): 0.0

CPU 7 ISR total execution time (s): 0.0

CPU 7 ISR count: 0

CPU 7 DPC highest execution time (µs): 570.812718

CPU 7 DPC total execution time (s): 0.277543

CPU 7 DPC count: 21351

_________________________________________________________________________________________________________

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

73 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-08-29T21:43:02+00:00

    Yeah I've tried everything in every solution rabbit hole at this point... HPET was never on, Assigned specific Cores / affinity to individual processes, then tried assigning 'sets' of Cores (process lasso). Used Iobit to install any out of date drivers. Tried several different Nvidia drivers with clean installs (Nvidia cleanup tool and DDU), changed power management stuff everywhere in BIOS and windows device manager etc... (every USB device) I disabled Dynamic lighting and tried moving the mouse to different USB port ...several things listed in my last post. This a new supposedly powerhouse computer and it's junk.

    Wdf01000.sys and ntoskrnl.exe

    _________________________________________________________________________________________________________

    CONCLUSION

    _________________________________________________________________________________________________________

    Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates.

    LatencyMon has been analyzing your system for 1:19:12 (h:mm:ss) on all processors.

    _________________________________________________________________________________________________________

    SYSTEM INFORMATION

    _________________________________________________________________________________________________________

    Computer name: VINS-DESKTOP

    OS version: Windows 11, 10.0, version 2009, build: 22631 (x64)

    Hardware: Intel(R) Core(TM) i7-14700KF, iBUYPOWER

    BIOS: 1663

    CPU: GenuineIntel Intel(R) Core(TM) i7-14700KF

    Logical processors: 28

    Processor groups: 1

    Processor group size: 28

    RAM: 32613 MB total

    _________________________________________________________________________________________________________

    CPU SPEED

    _________________________________________________________________________________________________________

    Reported CPU speed (WMI): 340 MHz

    Reported CPU speed (registry): 3418 MHz

    Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.

    _________________________________________________________________________________________________________

    MEASURED INTERRUPT TO USER PROCESS LATENCIES

    _________________________________________________________________________________________________________

    The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.

    Highest measured interrupt to process latency (µs): 17060.70

    Average measured interrupt to process latency (µs): 16.683094

    Highest measured interrupt to DPC latency (µs): 2153.60

    Average measured interrupt to DPC latency (µs): 4.263323

    _________________________________________________________________________________________________________

    REPORTED ISRs

    _________________________________________________________________________________________________________

    Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.

    Highest ISR routine execution time (µs): 250.803394

    Driver with highest ISR routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

    Highest reported total ISR routine time (%): 0.000695

    Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

    Total time spent in ISRs (%) 0.000695

    ISR count (execution time <250 µs): 176453

    ISR count (execution time 250-500 µs): 0

    ISR count (execution time 500-1000 µs): 1

    ISR count (execution time 1000-2000 µs): 0

    ISR count (execution time 2000-4000 µs): 0

    ISR count (execution time >=4000 µs): 0

    ________________________________________________________________________________________________________

    REPORTED DPCs

    _________________________________________________________________________________________________________

    DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.

    Highest DPC routine execution time (µs): 4598.384143

    Driver with highest DPC routine execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

    Highest reported total DPC routine time (%): 0.006395

    Driver with highest DPC total execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

    Total time spent in DPCs (%) 0.014761

    DPC count (execution time <250 µs): 1894459

    DPC count (execution time 250-500 µs): 0

    DPC count (execution time 500-10000 µs): 276

    DPC count (execution time 1000-2000 µs): 0

    DPC count (execution time 2000-4000 µs): 0

    DPC count (execution time >=4000 µs): 1

    _________________________________________________________________________________________________________

    REPORTED HARD PAGEFAULTS

    _________________________________________________________________________________________________________

    Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.

    NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.

    Process with highest pagefault count: msmpeng.exe

    Total number of hard pagefaults 49229

    Hard pagefault count of hardest hit process: 19076

    Number of processes hit: 52

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2024-10-26T18:33:40+00:00

    Windows vers. 23H2 didn't solve my latency with latency for Wdf01000.sys 's driver.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-11-08T03:44:00+00:00

    For my specific setup, the issue ultimately ended up being high DPC latency caused by the Nvidia drivers for my 3080. I'm sure different unique combinations of PC hardware might require different solutions, but this is what is working for me.

    I did several days of experimentation with DDU and NVCleanInstall, updating BIOS and changing all of the CPU power options in BIOS (as oft recommended), disabling plugins, Windows power plan tweaks, using Lasso to assign Ableton to high CPU priority + affinity to p-cores, changing USB ports, disabling services and unused hardware drivers, etc. And re-running LatencyMon with every change. It's possible some of these things contributed to marginally improving things, and a few times I thought I saw some minor improvements, but it's difficult to track as the problem would sometimes come and go.

    I also tried two different interfaces, an RME Fireface UFX III and a 1st gen Scarlett 18i20, each with their native drivers, and both had similar issues. Particularly surprising with the new RME. Both needed a buffer size of 256 or more on a small project to avoid the random drop-outs with some measure of reliability.

    The one thing that had the most noticeable effect with the CPU spikes and glitches in Ableton was going to Nvidia Control Panel -> Manage 3D Settings, and setting Low Latency Mode to "Ultra", and Power Management Mode to "Prefer Maximum Performance". Surprisingly, this cured most of my big CPU/latency spikes while playing back audio in Ableton. Running with a buffer of 128 was now much smoother. Just note that you need to re-set these options after reinstalling your drivers with NVCleanInstall. Even with this config, the drop-outs will still happen on rare occasion, but they are much less common, and perhaps that's enough for some people.

    I then got curious about whether using an AMD/Radeon card instead of Nvidia would make any further difference. As an experiment, I pulled an old RX 590+ out of another PC and replaced my 3080, and installed the AMD drivers. Wow, huge difference. Despite being a much older GPU, Ableton not only doesn't glitch at all, but it also runs much more efficiently and uses less baseline CPU in general, and I can lower my buffer size to the lowest value of 32 without any problems. And unlike the Nvidia drivers, the AMD drivers don't register any latency at all in LatencyMon. So I think Nvidia simply must not play well with real-time audio, at least with certain hardware combinations.

    I guess I'm buying a new AMD GPU now.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2024-11-08T12:52:13+00:00

    Thanks for replying Edmond, I will try that Low Latency mode set to Ultra as it was by default set to OFF.

    I will post back if this makes any noticable changes on my machine.

    Thanks again!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-11-08T18:38:26+00:00

    I've found a solution to this issue! But I don't perfectly like it, still doesn't explain much, and isn't a general solution.

    My MOTU audio card was apparently "the problem". I've started using my Virus TI main output (SPDIF) as a windows audio card; I've disabled Windows audio MOTU WDM & left my MOTU as an ASIO only audio card.. so my Virus handles Windows WDM computer audio & passes that via SPDIF input to my MOTU which is still my main sudio out (and Windows ASIO card) to amps & monitors. This lets me use MOTU ASIO through my audio software, and I just have a spdif/line input for windows audio into my main 'external' audio card.

    It is a little strange thinking of my main computer ASIO audio card as 'external' to my main windows audio card, but it's not difficult and it works just fine. All audio issues and latencies are now resolved.

    I guess Windows doesn't like MOTU WDM audio drivers, or doesn't like them in combination with some other set of things in my rig.

    Was this answer helpful?

    0 comments