Windows 10: DPC Latency with Storport.sys and Wdf0 1000.sys

I have recently added a new mixer (Presonus Studio Live 16 Series III) to my studio and started having some major issues. It wouldn't be read by the Presonus Studio One 3 DAW. I asked Presonus for help and they asked me to give them a LatencyMon report.

The report plainly states that I have some major latency issues going on. So I proceeded to upgrade my hardware from the old i7 4770k and MSI board running 32GB DDR3 RAM to the new AMD Ryzen 7 1700 on an ASUS Crosshair VI Hero board with Corsair 32GB DDR4 RAM.

After all of that, a fresh install of Windows 10 and the programs I use, I now have an even higher latency issue.

The Presonus Support staff suggested I update drivers (which I did). Turn off CPU Throttling (which I don't know how to do in the newer motherboards) and then get back with them after I have completed those tasks. I used Driver Booster 4.4 Pro to track down all the drivers. Updated my BIOS and I still have high latency and it appears that the culprits are Storport.sys and Wdf0 1000.sys

Here are the stats from LatencyMon

____________________________________________________________________________________________________ _____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:50:26 (h:mm:ss) on all processors._________________________________________________________________________________________ ________________SYSTEM INFORMATION_________________________________________________________________________________________ ________________Computer name: DESKTOP-HNJG2JIOS version: Windows 8 , 6.2, build: 9200 (x64)Hardware: ASUSTeK COMPUTER INC., CROSSHAIR VI HEROCPU: AuthenticAMD AMD Ryzen 7 1700 Eight-Core Processor Logical processors: 16Processor groups: 1RAM: 32696 MB total_______________________________________________________________________________________________ __________CPU SPEED_______________________________________________________________________________________________ __________Reported CPU speed: 2994.0 MHzMeasured CPU speed: 5216.0 MHz (approx.)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): 4036.321766Average measured interrupt to process latency (µs): 9.277492Highest measured interrupt to DPC latency (µs): 4031.534127Average measured interrupt to DPC latency (µs): 5.861701____________________________________________________________________________________________ _____________ 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): 320.440882Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft CorporationHighest reported total ISR routine time (%): 0.073277Driver with highest ISR total time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft CorporationTotal time spent in ISRs (%) 0.118784ISR count (execution time <250 µs): 88068774ISR count (execution time 250-500 µs): 0ISR count (execution time 500-999 µs): 20ISR count (execution time 1000-1999 µs): 0ISR count (execution time 2000-3999 µs): 0ISR 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): 100339.308617Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft CorporationHighest reported total DPC routine time (%): 0.671484Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft CorporationTotal time spent in DPCs (%) 0.807031DPC count (execution time <250 µs): 60468376DPC count (execution time 250-500 µs): 0DPC count (execution time 500-999 µs): 743257DPC count (execution time 1000-1999 µs): 28DPC count (execution time 2000-3999 µs): 12DPC 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.Process with highest pagefault count: noneTotal number of hard pagefaults 0Hard pagefault count of hardest hit process: 0Highest hard pagefault resolution time (µs): 0.0Total time spent in hard pagefaults (%): 0.0Number of processes hit: 0___________________________________________________________________________________________________ ______ PER CPU DATA________________________________________________________________________________________________ _________CPU 0 Interrupt cycle time (s): 394.209828CPU 0 ISR highest execution time (µs): 300.190381CPU 0 ISR total execution time (s): 13.851122CPU 0 ISR count: 42999853CPU 0 DPC highest execution time (µs): 5182.454910CPU 0 DPC total execution time (s): 331.350578CPU 0 DPC count: 51579375____________________________________________________________________________________________ _____________CPU 1 Interrupt cycle time (s): 72.690812CPU 1 ISR highest execution time (µs): 320.440882CPU 1 ISR total execution time (s): 11.374231CPU 1 ISR count: 639323CPU 1 DPC highest execution time (µs): 1409.208417CPU 1 DPC total execution time (s): 24.058686CPU 1 DPC count: 986639______________________________________________________________________________________________ ___________CPU 2 Interrupt cycle time (s): 52.846246CPU 2 ISR highest execution time (µs): 170.350701CPU 2 ISR total execution time (s): 9.848251CPU 2 ISR count: 762474CPU 2 DPC highest execution time (µs): 823.727455CPU 2 DPC total execution time (s): 19.269337CPU 2 DPC count: 1164216_____________________________________________________________________________________________ ____________CPU 3 Interrupt cycle time (s): 24.938709CPU 3 ISR highest execution time (µs): 145.020040CPU 3 ISR total execution time (s): 0.189192CPU 3 ISR count: 88127CPU 3 DPC highest execution time (µs): 530.320641CPU 3 DPC total execution time (s): 1.275327CPU 3 DPC count: 102689______________________________________________________________________________________________ ___________CPU 4 Interrupt cycle time (s): 20.371437CPU 4 ISR highest execution time (µs): 22.775551CPU 4 ISR total execution time (s): 0.003807CPU 4 ISR count: 859CPU 4 DPC highest execution time (µs): 335.140281CPU 4 DPC total execution time (s): 0.604158CPU 4 DPC count: 74159_______________________________________________________________________________________________ __________CPU 5 Interrupt cycle time (s): 20.277739CPU 5 ISR highest execution time (µs): 20.110220CPU 5 ISR total execution time (s): 0.000428CPU 5 ISR count: 62CPU 5 DPC highest execution time (µs): 192.244489CPU 5 DPC total execution time (s): 0.068530CPU 5 DPC count: 12466_______________________________________________________________________________________________ __________CPU 6 Interrupt cycle time (s): 20.887043CPU 6 ISR highest execution time (µs): 0.0CPU 6 ISR total execution time (s): 0.0CPU 6 ISR count: 0CPU 6 DPC highest execution time (µs): 300.060120CPU 6 DPC total execution time (s): 0.372607CPU 6 DPC count: 58441_______________________________________________________________________________________________ __________CPU 7 Interrupt cycle time (s): 20.238033CPU 7 ISR highest execution time (µs): 0.0CPU 7 ISR total execution time (s): 0.0CPU 7 ISR count: 0CPU 7 DPC highest execution time (µs): 167.925852CPU 7 DPC total execution time (s): 0.061214CPU 7 DPC count: 10929_______________________________________________________________________________________________ __________CPU 8 Interrupt cycle time (s): 31.445492CPU 8 ISR highest execution time (µs): 0.0CPU 8 ISR total execution time (s): 0.0CPU 8 ISR count: 0CPU 8 DPC highest execution time (µs): 456.022044CPU 8 DPC total execution time (s): 1.957682CPU 8 DPC count: 1199210_____________________________________________________________________________________________ ____________CPU 9 Interrupt cycle time (s): 32.239437CPU 9 ISR highest execution time (µs): 0.0CPU 9 ISR total execution time (s): 0.0CPU 9 ISR count: 0CPU 9 DPC highest execution time (µs): 320.561122CPU 9 DPC total execution time (s): 0.165233CPU 9 DPC count: 46890_______________________________________________________________________________________________ __________CPU 10 Interrupt cycle time (s): 33.223726CPU 10 ISR highest execution time (µs): 0.0CPU 10 ISR total execution time (s): 0.0CPU 10 ISR count: 0CPU 10 DPC highest execution time (µs): 427.444890CPU 10 DPC total execution time (s): 1.651628CPU 10 DPC count: 505417______________________________________________________________________________________________ ___________CPU 11 Interrupt cycle time (s): 31.772490CPU 11 ISR highest execution time (µs): 0.0CPU 11 ISR total execution time (s): 0.0CPU 11 ISR count: 0CPU 11 DPC highest execution time (µs): 269.539078CPU 11 DPC total execution time (s): 0.161207CPU 11 DPC count: 55947_______________________________________________________________________________________________ __________CPU 12 Interrupt cycle time (s): 59.447627CPU 12 ISR highest execution time (µs): 160.230461CPU 12 ISR total execution time (s): 16.244654CPU 12 ISR count: 33764815CPU 12 DPC highest execution time (µs): 100339.308617CPU 12 DPC total execution time (s): 5.610136CPU 12 DPC count: 3555584_____________________________________________________________________________________________ ____________CPU 13 Interrupt cycle time (s): 39.827547CPU 13 ISR highest execution time (µs): 255.460922CPU 13 ISR total execution time (s): 1.760120CPU 13 ISR count: 3464360CPU 13 DPC highest execution time (µs): 333.657315CPU 13 DPC total execution time (s): 0.630978CPU 13 DPC count: 315780______________________________________________________________________________________________ ___________CPU 14 Interrupt cycle time (s): 35.320746CPU 14 ISR highest execution time (µs): 97.484970CPU 14 ISR total execution time (s): 1.712625CPU 14 ISR count: 2635322CPU 14 DPC highest execution time (µs): 469.148297CPU 14 DPC total execution time (s): 2.150728CPU 14 DPC count: 968751______________________________________________________________________________________________ ___________CPU 15 Interrupt cycle time (s): 37.911701CPU 15 ISR highest execution time (µs): 143.517034CPU 15 ISR total execution time (s): 2.526747CPU 15 ISR count: 3713599CPU 15 DPC highest execution time (µs): 356.963928CPU 15 DPC total execution time (s): 1.347907CPU 15 DPC count: 575182______________________________________________________________________________________________ ___________

What should be my next steps?

Thank you,

Brad

:)

 

Windows 10 DPC latency issue with ndis & tcpip.sys

Your code and my recent
CrazyPingTest3 trigger DPC latency issue of tcpip.sys after a couple of runs. Like you said.

One run of your code, one run of CrazyPingTest3 or infinite run of my infinite pings (original
CrazyPingTest) cause just 0.5 to 1 ms latency.

But! If I add a 50 ms sleep before starting a new thread, there is no latency at all. See my
CrazyPingTest3). There is a commented line.

And if I add Thread.Sleep(50); before your

p.SendAsync(ip, 1000, ip);

I see no DPC latency too.

And thank you for the link!

Upd. Oh, I was wrong. I made some more runs and had a DPC latency.

And I’m here because of “windows 10 ndis high dpc” issue too.

 

Wdf01000.sys Latency - Windows 10

Here is what is reported to me while I am using Ableton Live 9 and I am using a MOTU mk3 hybrid interface. I am able to monitor the output audio and the interface is not detecting the audio interruptions which tells me the interruptions happen between my
interface and my computer. Also I have Windows 10 Pro if that changes anything. I only ran this test for 15 seconds and here are the 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): 2194.133612

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

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

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

_________________________________________________________________________________________________________

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

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

Highest reported total ISR routine time (%): 1.111090

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

Total time spent in ISRs (%) 1.139980

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

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

ISR count (execution time 500-999 µs): 81

ISR count (execution time 1000-1999 µs): 3

ISR count (execution time 2000-3999 µ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): 99012.881448

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

Highest reported total DPC routine time (%): 2.076374

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

Total time spent in DPCs (%) 2.468677

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

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

DPC count (execution time 500-999 µs): 133

DPC count (execution time 1000-1999 µs): 43

DPC count (execution time 2000-3999 µs): 18

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.

Process with highest pagefault count: none

Total number of hard pagefaults 0

Hard pagefault count of hardest hit process: 0

Highest hard pagefault resolution time (µs): 0.0

Total time spent in hard pagefaults (%): 0.0

Number of processes hit: 0

 

You probably didn't need to upgrade, your older system should have handled audio just fine.

It is very hard to read your data dump, maybe use a screen capture?

Can you post a screen capture of the driver's page of latencymon?
Sort it by highest execution.

What port is the mixer connected to? USB?

Post your power plan settings, too.

 

Sorry when I went to post it looked much better than it does there.... So I can see how that wasn't the greatest piece to look at.

Here is the screenshot you requested.








Power Plan Settings: High Performance
Turn off disk after: 20min
Sleep/Hibernate: Never
USB Selective Suspend Setting: Enabled
PCI Express Link State Power Management: Off

Processor Power Management

• Maximum Processor Frequency: 0MHz
• Minimum Processor State: 100%
• System Cooling Policy: Active
• Maximum Processor State: 100%

I believe the Power settings are mostly the generic High Performance. If I changed anything it was the sleep function as I often access this computer when I'm at home.

As for staying with my old computer. I agree, I definitely could have, but it had been 3 years since I last built that system so I figured it was time to step it up. I also use the Creative Cloud often and my system could use a boost in speed. Plus the old components are now in a second tower and being used for offloading things to free up this computer for recording (such as rendering video, etc).

I plan to add 32GB more to the RAM over the next two months and a new 1080ti video card. Someone also told me adding an internal Soundcard might help as well, although I don't see what it has to do with this latency issue.

Thanks again,

Brad

 

The power settings look good, but I would disable the selective suspend on the USB ports, since you have a USB audio driver.

This is not the problem, though. Anything that takes more than a fraction of a millisecond as a DPC process might cause an audio dropout or glitch.

Your values for StorPort.sys are off the wall! That is the Microsoft SCSI driver for your hard drives and SCSI attached stuff.

You might have misconfigured some drive setting (like not using AHCI). Perhaps this is a BIOS setting. Are your SCSI drives using IDE or something like that?

For comparison, I use high end audio stuff on a daily basis and my system was built in 2011.

Here is what I see on latencymon:





[EDIT] - added this image:

 

This is where I go from being an above average computer person to someone who is going to completely sound like a beginner.

I didn't think SCSI was a thing still.

I have an SSD Drive (SATA) and two platter drives (both SATA). So I am not sure where SCSI or IDE comes into play.... but again this is where my knowledge ends and I'm going to stumble around a bit and probably sound like I have no clue what I'm talking about (which is probably accurate).

 

I would suggest you look up references to 'do I have ahci or ide'.

Basically, look at the device manager system control panel, set view ->devices by connection
Look for the storage controller and see if the driver is AHCI or IDE.

The configuration for the drive is usually a BIOS setting, so if it is wrong you will have to change it in BIOS.

However, if you have to change that: it is not so easy to do. If you do it wrong you might not be able to boot.

Make sure you understand these issues before you change anything (and make sure you have everything backed up).

A long time ago I had this misconfigured in one of my systems when I went from IDE to SCSI. I had a lot of problems. Nowadays everything looks like a SCSI device so you probably don't have any IDE drives.

If the SSD is misconfigured, that could also be a big problem.

If you can boot without the extra platter drives, power down, turn them off or disconnect them, and see if latency monitor improves. That will tell you is it is the SSD.

If the SSD has been used for a while, maybe the TRIM command was never done. That does garbage collection and cleanup stuff on the memory parts. Windows usually does this if it knows you have an SSD and the Vendor usually supplies a tool for this as well.

Try the vendor SSD diagnostics, too, and look at the SMART values on your drives if you have anything that shows that.

You could try the free version of HD Tune (hdtune.com) it is great for testing stuff like this.

 

I have one Storage Controller here is what the Drivers say

 

I'm afraid it is not that easy - that is a special MS port for Storage Spaces.
You need to open the CPU branch and look at each port:

 

Like this? It appears "Standard SATA AHCI Controller"

 

Yes that is the SATA AHCI controller and you have 3 devices connected to it - the SSD and 2 drives.
There is another one - the AMD SATA controller, but nothing is there.
Look at the device drivers for these connected drives and see if they are all AHCI drivers and not IDE.
You might not be able to tell by looking.
The best way, though is to check BIOS.
I'll post what my BIOS screen looks like in a moment, I'll have to restart to get it.

 

Your BIOS will naturally look different, but you need to find the SATA configuration tab and make sure the ports are set to AHCI mode.

If you have that set up then the problem is more subtle and I have no more advice.

 

It would, unfortunately, appear we are at an impasse. The BIOS says it is set to AHCI.

I appreciate the time and effort you put into this one. It has taught me a few new tricks along the way. So again, thank you.

 

I'm not familiar with Hyper kit mode, that is something you might look at.
There is also a collapsed arrow next to the SATA6G_1 port maybe there is something of interest there if you expand it.

But I'd say that BIOS looks OK.

Still your Storport driver settings should be around .1 to .2 ms not 100. So something is not right - maybe a bad cable.

If you look in the event viewer there may be some errors logged that might help.

I'd clear all the errors, restart, wait a while for restart services to settle, then open the event viewer and look at the system and application events for clues.

HD Tune might help you find problems in the SMART data.
It is free. I've used HD Tune Pro for years.

I don't think I can help any further, I'd really have to have your system in front of me to proceed further.