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
    2023-09-19T19:55:00+00:00

    i got a "msi mag z690 tomahawk wifi ddr4" with a "intel i7 13700k"

    i´m using right now a "soundblaster x4", but still have the popping noise.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2023-09-19T22:14:14+00:00

    I was using an ASUS Prime Z690 MoBo with a i9 12900K CPU, my supplier has exchanged that with an ASUS Prime Z790 MoBo.

    It does appear the Z690 Chipset is the issue, as the Wdf01000.sys is the driver used to communicate with the system hardware.

    My supplier has provided evidence the the Z790 chipset does not have the same issue.

    My sound device is a Focusrite Pre 8 USB as I am primarily a music producer and song writer.

    The Z790 Chipset has been indicated to myself by a couple of DAW PC providers, both in the UK and USA as the preferred Chipset for DAW use.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  3. Anonymous
    2023-09-19T22:27:53+00:00

    okay cool, but i had the same problem for 1 year on a 10 year old gigabyte board too.

    doesn´t make any sense.

    And if so, why is no one talking about it?

    only your supplier?

    and where is the evidence, besides your post? ^^

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments
  4. Anonymous
    2023-09-19T23:43:40+00:00

    Just search YouTube or your preferred interweave search engine. See the number of people struggling with this drive causing BSoD.

    Personally I was surprised.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2023-09-20T12:06:47+00:00

    there is not even a single one saying, they had BSoD´s at all.

    And it´s not only the 690 boards that have this problem.

    Almost every new board has reporting the problem, at least from customers.

    and most people say it´s a software related thing.

    I would say it is, because i had on a older pc the same problem with different hardware.

    It happend after a update i´m pretty sure. But i don´t even know which update caused it.

    Since it´s a couple years ago.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments