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

You may use AMD or Intel profile for memory in BIOS. I use. It work, but need some more voltege: 0,02-0,05 V that do profile. Another it will be BSOD as mamory chip is Samsung or also Hynix.

Also I see recomendation use for system process another cores than first or thouse, that not used for another app. Another words - use core that is clean from another process.

It is my Latency today report after Windows reinstalling with app and data

_________________________________________________________________________________________________________

CONCLUSION

_________________________________________________________________________________________________________

Your system appears to be suitable for handling real-time audio and other tasks without dropouts.

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

_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: PC3

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

Hardware: B650 AORUS ELITE AX, Gigabyte Technology Co., Ltd.

BIOS: FA2

CPU: AuthenticAMD AMD Ryzen 5 7500F 6-Core Processor

Logical processors: 12

Processor groups: 1

Processor group size: 12

RAM: 32405 MB total

_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed (WMI): 3701 MHz

Reported CPU speed (registry): 3693 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): 465.0

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

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

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

_________________________________________________________________________________________________________

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): 27.632277

Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0.001383

Driver with highest ISR total time: Wdf01000.sys - Среда выполнения платформы драйвера режима ядра, Microsoft Corporation

Total time spent in ISRs (%) 0.001569

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

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): 693.391822

Driver with highest DPC routine execution time: Wdf01000.sys - Среда выполнения платформы драйвера режима ядра, Microsoft Corporation

Highest reported total DPC routine time (%): 0.575988

Driver with highest DPC total execution time: Wdf01000.sys - Среда выполнения платформы драйвера режима ядра, Microsoft Corporation

Total time spent in DPCs (%) 0.597395

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

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

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

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

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

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

_________________________________________________________________________________________________________

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: latmon.exe

Total number of hard pagefaults 47

Hard pagefault count of hardest hit process: 9

Number of processes hit: 6

_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 21.684445

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

CPU 0 ISR total execution time (s): 0.029050

CPU 0 ISR count: 47529

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

CPU 0 DPC total execution time (s): 12.316690

CPU 0 DPC count: 113572

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 4.878762

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

CPU 1 ISR total execution time (s): 0.003925

CPU 1 ISR count: 399

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

CPU 1 DPC total execution time (s): 0.170331

CPU 1 DPC count: 7608

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 1.161069

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): 149.933658

CPU 2 DPC total execution time (s): 0.008039

CPU 2 DPC count: 979

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 1.044495

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): 155.614406

CPU 3 DPC total execution time (s): 0.001355

CPU 3 DPC count: 198

_________________________________________________________________________________________________________

CPU 4 Interrupt cycle time (s): 0.573097

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): 68.960466

CPU 4 DPC total execution time (s): 0.00170

CPU 4 DPC count: 258

_________________________________________________________________________________________________________

CPU 5 Interrupt cycle time (s): 0.512585

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): 141.547793

CPU 5 DPC total execution time (s): 0.000562

CPU 5 DPC count: 79

_________________________________________________________________________________________________________

CPU 6 Interrupt cycle time (s): 3.191660

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): 354.881397

CPU 6 DPC total execution time (s): 0.043139

CPU 6 DPC count: 4107

_________________________________________________________________________________________________________

CPU 7 Interrupt cycle time (s): 3.096684

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): 346.525589

CPU 7 DPC total execution time (s): 0.014119

CPU 7 DPC count: 1181

_________________________________________________________________________________________________________

CPU 8 Interrupt cycle time (s): 0.253027

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

CPU 8 ISR total execution time (s): 0.0

CPU 8 ISR count: 0

CPU 8 DPC highest execution time (µs): 35.657460

CPU 8 DPC total execution time (s): 0.001407

CPU 8 DPC count: 169

_________________________________________________________________________________________________________

CPU 9 Interrupt cycle time (s): 0.238213

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

CPU 9 ISR total execution time (s): 0.0

CPU 9 ISR count: 0

CPU 9 DPC highest execution time (µs): 30.157054

CPU 9 DPC total execution time (s): 0.000271

CPU 9 DPC count: 37

_________________________________________________________________________________________________________

CPU 10 Interrupt cycle time (s): 0.349654

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

CPU 10 ISR total execution time (s): 0.0

CPU 10 ISR count: 0

CPU 10 DPC highest execution time (µs): 151.326293

CPU 10 DPC total execution time (s): 0.000818

CPU 10 DPC count: 73

_________________________________________________________________________________________________________

CPU 11 Interrupt cycle time (s): 0.343730

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

CPU 11 ISR total execution time (s): 0.0

CPU 11 ISR count: 0

CPU 11 DPC highest execution time (µs): 28.784457

CPU 11 DPC total execution time (s): 0.000278

CPU 11 DPC count: 44

_________________________________________________________________________________________________________

I have set off for HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Afer reinstallation Windows it is set on. Need to set off this audio Chanall. There will be more good results for latency.

I I found an intermediate but working solution. The first is that I connect my US366 USB card to a fast USB port, to a HOST that does not have any other devices and not via a PCIe expansion card. The second solution is that for playback I use a program that properly performs synchronization, which eliminates the jitter of the sync pulses.

True, for each file the program requires a significant time delay before playback. App use ASIO drivers.

ASIO output Bug head Nontallion / WASAPI EXCLUSIVE output Also supports PINK HQ Qctahedron / SSE2 CPU. Supports music format formats WAV FLAC DSD, MP3 CDA, and pursues accurate sound balance by strictly enforcing electronic bit standards based on the internal circuitry of the memory chip. Two output modes are available: High , which output FLOAT32 without changing [ ] the music data, and [Low] and [Super Black] and [Extreme], which output FLOAT32 with low frequency interpolation from the music data.

Using unique memory manipulation

techniques, the result is an I2S waveform correction algorithm.

It is Super Easy Music Player

App has 3 exe files and start exe file. See Easy_English_Manual_2020.pdf in app derectory.

Bug head 12.25 x64

Qctahedron 3.12 x64

Nontallion 12.25 x64

Developer information author : Hiroyuki Yokota (oryaaaaa) address: Kuyo-bo, Shinden-cho, Okazaki, Aichi, Japan (444-3174) E-mail: ******@gmail.com Homepage: http://www.mics.ne.jp/~coolverse/
download link https://www.bytesin.com/software/Download-Bug-head/ -not use Softpedia or Russian jr not Russian links with Emperor player.

This is so terrible! I've been away from all Microsoft's products for years but I had to return to Windows 10 a few months ago and I'm telling you I feel like I'm 10 years older. This clicking noise caused by Wdf01000.sys is ruining my life! I'm considering a downgrade to Windows 7 and Nuendo 10!

Core i5
16 GB RAM
Behringer UMC1820

I am having a horrible time troubleshooting this, I've even gone so far as to disable or uninstall most of my devices & manage interrupt affinity for the ones that are left, as well as managing process affinity for everything running on my box. The issue with all that, however, is that on restart the Wd01000.sys runtime can choose a different processor or set of processors to clog.

I have a 12/24 core Ryzen 9 5900X proc, GeForce RTX 3070, and MOTU UltraLite-mk4 and am getting unbelievable audio and video stutters. All the basics have been tried (updating everything & all types of system health scans).

Is there any tool that will allow me to see what is causing this Kernel Mode Driver Framework Runtime to wait for so long? Something that would allow me to trace the origin of the process or driver that triggered the DPC? And possibly even allow me to see what messages or processes it's waiting for?