Windows 10: Something causing high DPC (User process and at times a driver)

Have noticed that i seem to get sky high DPC at soem occasions.
I haven't really suffered from anything before, but recently i had some audio glitches which i haven't been able to reproduce.
As i have overclocked recently with offset voltage i though that might be the cause, however as said i cannot reproduce the audio glitch, might have been something interfering (it was huge glitch though, though it was gonna crash, happened like 2-3 times).

Anyhow, i have tried non-OC as well, but looking at my DPC it seems that it always gets high for some reason.

Especially the User process. Driver has become high, but hasn't confirmed that without OC (it's a bit rarer, and i think it's USB driver, though no idea why).





This is with no overclock, just the default BIOS settings, with only some stuff disabled (USB 3.0, etc, and HDD set to AHCI).

:)

 

Wdf01000.sys Latency - Windows 10

***Update***

I have removed the interface from the equation and Ableton live 9 for the past week. I am now only trying basics tasks like play audio from iTunes and have the browser open. However I am still experiencing latency from the same driver as well as some other
Microsoft drivers.

_________________________________________________________________________________________________________

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

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

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

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

_________________________________________________________________________________________________________

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

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

Highest reported total ISR routine time (%): 0.016099

Driver with highest ISR total time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

Total time spent in ISRs (%) 0.046577

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

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

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

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

ISR count (execution time 2000-3999 µs): 8

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

Driver with highest DPC routine execution time: ataport.SYS - ATAPI Driver Extension, Microsoft Corporation

Highest reported total DPC routine time (%): 0.227243

Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%) 0.695677

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

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

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

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

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

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

 

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 are on the right track. High DPCs are usually driver problems.

 

Well it seems to be overclock related.

I noticed that Voltage Offset was the first thing to blame.

I changed to Manual and it works, though it can still happen, though i can't trigger is like i always could with Voltage Offset.
It's weird cause i never experienced this before, it was after i had to re-clock my overclock cause it wasn't stable,
and when it was stable i have this issue, no idea how to fix it*Sad