• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

High DPC due to Nvidia Kernel Driver?

Reading through the thread, interesting read.

Damn I picked the worst time to switch to the green team.
 
Okay, so I said **** it and reinstalled Win10 from scratch, and took a latencymon test with absolutely no drivers installed.

Results were good, as expected. Installed the nvidia driver then did another:

SnDWzVm.png


Once all the other drivers were installed I got these results:

56YJypk.png


Basically the same, just a little higher interrupt.
 
No, HPET is not an option on X99 ASUS boards, it's also not enabled by default in W10

Source?!

They said this on every version of windows past 8 and lied through thier teeth. If the thing is in your device manager, Then it is enabled? Windows will check what timers are used and will change if HPET is detected. It did this on my Z87 just like X99 they told me HPET is disabled by default, Yea so why is a server and slower time featured in the device manager as high precision event timer clock? After i hunted down a custom bios with a toggle i manually set to off and low and behold Nvidia DPC nosedive, No more red errors either.


In short if you were told this by anyone other than Microsoft then it is probably a lie, I asked Asus and Gigabyte and thier response was Asus did not know what HPET was.... And Gigabyte put out the same line as you did which i disproved myself on 8.1 64bit
 
More reading tells me Intel NIC drivers completely suck with Win10 and can cause spikes when using the network. In lieu of that, I blasted the NIC with some data transfer and captured it in an xperf

No expert at reading them though:

https://www.dropbox.com/s/agah4ymz6ij9ar5/CPU.etl?dl=0

Hi,

This is actually a valid point to bring up. Make sure you are running the latest drivers for the Ethernet adapter.

Source?!

They said this on every version of windows past 8 and lied through thier teeth. If the thing is in your device manager, Then it is enabled? Windows will check what timers are used and will change if HPET is detected. It did this on my Z87 just like X99 they told me HPET is disabled by default, Yea so why is a server and slower time featured in the device manager as high precision event timer clock? After i hunted down a custom bios with a toggle i manually set to off and low and behold Nvidia DPC nosedive, No more red errors either.


In short if you were told this by anyone other than Microsoft then it is probably a lie, I asked Asus and Gigabyte and thier response was Asus did not know what HPET was.... And Gigabyte put out the same line as you did which i disproved myself on 8.1 64bit


ASUS will know full well what HPET is wholly. Depends on whom at ASUS you spoke to. X99 motherboards (at least ASUS) only support Windows 7 and newer operating systems/CPU's with constant rate time stamp counters (so there is no need for a BIOS option)
 
Last edited:
No,

The latest drivers (20.3) still have that issue. The last ones that didn't have them was 18.5 - which isn't on Windows 10. Until Intel fix their crap we have to deal with it.

However, it still doesn't seem likely. The ONLY driver that goes above 0.2ms is the nvidia kernel and I'm starting to think it may be a power management issue within the card drivers or the card itself.

When I have latencymon running and the screens turn off for inactivity, even if the latency was just fine before that, when its back it will have jumped up to 2.5ms. Interesting.
 
DPC issues are normally very system specific. Contact NVIDIA - I'm on X99 with no issues on W10

The rep I know personally thinks it is probably a power management bug - they have a lot of those needing fixes.

Also, have you actually tried running tests, or just saying that because you're not symptomatic? A friend on Win10 with a sandy bridge chipset and 760s showed similar results and similar audio popping on USB, he fixed it by getting a PCEi slotted USB card that plugged into one of the mobo USB slots and ignoring the inbuilt ports totally.

The lag was still there on his results though.
 
Nope..
Dpc latency issue range from a lot of things. One bad driver on your system can give you latency issues.

USB, network storage driver to name the biggest ones.

Yeah, and based on my results the nvidia kernel is the only one to blame, everything else is barely 0.2ms. Nvidia's Win10 drivers have been notoriously atrocious, and I'm thinking a downgrade to Win8.1 might be my last hope.
 
Hi guys,

Back on windows 8.1 now.

I'm still getting DPC routine executions of over 1ms when doing certain stuff (must be a power management thing in the GPU for sure) but someone in this thread earlier said to ignore that, so whatever. It hasn't gone 'red text' yet on me, and the interrupt hasn't going to frighteningly high numbers.

I'll keep monitoring and keep you guys updated, but an early conclusion looks to be, while the nvidia kernel driver has always been a resource hog, it seems complete ******** on Windows 10.
 
Nope..
Dpc latency issue range from a lot of things. One bad driver on your system can give you latency issues.

USB, network storage driver to name the biggest ones.

What's that got to do with not being system specific? Shanks, bud...really.

Yeah, and based on my results the nvidia kernel is the only one to blame, everything else is barely 0.2ms. Nvidia's Win10 drivers have been notoriously atrocious, and I'm thinking a downgrade to Win8.1 might be my last hope.

I don't know anyone else personally even on X99 with this issue, so it's not entirely common.
The rep I know personally thinks it is probably a power management bug - they have a lot of those needing fixes.

Also, have you actually tried running tests, or just saying that because you're not symptomatic? A friend on Win10 with a sandy bridge chipset and 760s showed similar results and similar audio popping on USB, he fixed it by getting a PCEi slotted USB card that plugged into one of the mobo USB slots and ignoring the inbuilt ports totally.

The lag was still there on his results though.


XidZIvd.png


_________________________________________________________________________________________________________
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:27:01 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-8L2I6FF
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., X99-DELUXE
CPU: GenuineIntel Intel(R) Core(TM) i7-5960X CPU @ 3.00GHz
Logical processors: 16
Processor groups: 1
RAM: 16285 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 30 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): 659.800599
Average measured interrupt to process latency (µs): 6.490537

Highest measured interrupt to DPC latency (µs): 658.435259
Average measured interrupt to DPC latency (µs): 3.681693


_________________________________________________________________________________________________________
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): 163.897333
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Highest reported total ISR routine time (%): 0.088449
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in ISRs (%) 0.090159

ISR count (execution time <250 µs): 1926587
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
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): 305.463333
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 355.98 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0.034590
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%) 0.090256

DPC count (execution time <250 µs): 8484724
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 22
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µ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: steam.exe

Total number of hard pagefaults 6648
Hard pagefault count of hardest hit process: 5694
Highest hard pagefault resolution time (µs): 47565.7540
Total time spent in hard pagefaults (%): 0.004875
Number of processes hit: 13


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 15.998459
CPU 0 ISR highest execution time (µs): 0.0
CPU 0 ISR total execution time (s): 0.0
CPU 0 ISR count: 0
CPU 0 DPC highest execution time (µs): 119.340
CPU 0 DPC total execution time (s): 3.466205
CPU 0 DPC count: 4439660
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 6.327177
CPU 1 ISR highest execution time (µs): 0.0
CPU 1 ISR total execution time (s): 0.0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 116.840
CPU 1 DPC total execution time (s): 0.052990
CPU 1 DPC count: 30975
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 6.474998
CPU 2 ISR highest execution time (µs): 3.287333
CPU 2 ISR total execution time (s): 0.000216
CPU 2 ISR count: 75
CPU 2 DPC highest execution time (µs): 161.442667
CPU 2 DPC total execution time (s): 0.107514
CPU 2 DPC count: 62490
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 6.477622
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): 116.379333
CPU 3 DPC total execution time (s): 0.043442
CPU 3 DPC count: 24497
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 6.288008
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): 116.727333
CPU 4 DPC total execution time (s): 0.076282
CPU 4 DPC count: 44147
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 6.402189
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): 160.445333
CPU 5 DPC total execution time (s): 0.066743
CPU 5 DPC count: 32946
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 6.399452
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): 160.088667
CPU 6 DPC total execution time (s): 0.141926
CPU 6 DPC count: 63614
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 6.165821
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): 115.4280
CPU 7 DPC total execution time (s): 0.058624
CPU 7 DPC count: 28754
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 6.263704
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): 160.123333
CPU 8 DPC total execution time (s): 0.125165
CPU 8 DPC count: 63145
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 26.359707
CPU 9 ISR highest execution time (µs): 163.897333
CPU 9 ISR total execution time (s): 12.523639
CPU 9 ISR count: 824069
CPU 9 DPC highest execution time (µs): 305.463333
CPU 9 DPC total execution time (s): 8.458177
CPU 9 DPC count: 1608892
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 6.122019
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): 159.381333
CPU 10 DPC total execution time (s): 0.127566
CPU 10 DPC count: 55155
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 6.427638
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): 159.149333
CPU 11 DPC total execution time (s): 0.068941
CPU 11 DPC count: 26734
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 5.900154
CPU 12 ISR highest execution time (µs): 0.0
CPU 12 ISR total execution time (s): 0.0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 114.960
CPU 12 DPC total execution time (s): 0.122499
CPU 12 DPC count: 45258
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 27.037791
CPU 13 ISR highest execution time (µs): 157.646667
CPU 13 ISR total execution time (s): 10.779842
CPU 13 ISR count: 1079764
CPU 13 DPC highest execution time (µs): 299.5540
CPU 13 DPC total execution time (s): 9.908779
CPU 13 DPC count: 1806810
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 6.480367
CPU 14 ISR highest execution time (µs): 18.8960
CPU 14 ISR total execution time (s): 0.082402
CPU 14 ISR count: 22679
CPU 14 DPC highest execution time (µs): 158.270
CPU 14 DPC total execution time (s): 0.470746
CPU 14 DPC count: 119859
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 6.430159
CPU 15 ISR highest execution time (µs): 0.0
CPU 15 ISR total execution time (s): 0.0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 157.962667
CPU 15 DPC total execution time (s): 0.115811
CPU 15 DPC count: 31810
_________________________________________________________________________________________________________
I don't have any audio loss or popping or latency issues, no. Smooth as butter. On any device ranging over DP, Realtek and USB headset

P.S what motherboard is this?
 
Last edited:
The motherboard is an X99-S.

As mentioned though, this persisted through a total of (3) x99 mobos, and my original G45. It definitely can't be the mobo, based on that.

When running idle in Windows 8.1, it was flawless for more than 2 hours. As soon as I dragged a tab out of chrome to become its own window, I can replicate a high >1ms+ DPC latency instantly.

Hum. That's interesting.

k9xoM8j.png
jSNGdgS.png
 
Last edited:
Probably not want you want to hear, but in the world of realtime for motion control applications (where latency spikes have more "critical" implications) Nvidia gpus are known to cause problems and are generally avoided.
 
Probably not want you want to hear, but in the world of realtime for motion control applications (where latency spikes have more "critical" implications) Nvidia gpus are known to cause problems and are generally avoided.

I picked an awful time to switch from the red team then, huh? :p
 
Back
Top Bottom