System interrupts high CPU spikes, audio stutter, freeze.

I'm gonna check that right now, thanks for the advice!

So the BIOS didn't had any of those options and the windows services regarding bluetooth and wifi are all disabled.

1) I do not have any marks in the device manager
2) The realtek audio is disabled from the BIOS I couldn't find the model of the chip. I use my G430 Headset which has it's own soundcard.
3) Realtek and 6.0.1.7240 / Logitech 8.83.51.0 (for the G430)
4) 16 bit, 48000Hz
5) The g430 USB soundcard

With any of the devices I still get the spikes, also I have the NVDIA HD audio driver installed for when I want to use my monitor speakers.

6) I didn't had parked cores
7) Just adjusted that, let's see if it solves the problem
8) I'm gonna take a look at that
9) I already have all updates disabled

Gonna see how it goes with the background settings changed to performance and I'll report back, it might take me a day to see if the problem comes back as it doesn't happen very frequently.

Thanks for the help.

Also let me get a good pic of the LatencyMon and what I can find.

So here's what latencymon looks like.



When the sound stutter and freeze happen is when Highest measured interrupt goes extremely high, usually from what I can tell when the DPC goes high, nothing happens.

Also storport.sys only gets that high since I did a clean install of windows 10.
Before that it would usually be another random driver.

So after a lot of testing and almost 2 days without having the trouble, I have come to the conclusion that the conflicting driver is USBPORT.SYS still haven't found a solution.


Heres the latencymon stats:

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


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: VICTOR-PC
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: Intel Corporation, DX79TO
CPU: GenuineIntel Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz
Logical processors: 16
Processor groups: 1
RAM: 16308 MB total


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

Highest measured interrupt to DPC latency (µs): 2062.500418
Average measured interrupt to DPC latency (µs): 1.079381


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

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

Total time spent in ISRs (%) 0.075956

ISR count (execution time <250 µs): 313595
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): 5988.643462
Driver with highest DPC routine execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0.083588
Driver with highest DPC total execution time: USBPORT.SYS - USB 1.1 & 2.0 Port Driver, Microsoft Corporation

Total time spent in DPCs (%) 0.217937

DPC count (execution time <250 µs): 1193756
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1
DPC count (execution time 1000-1999 µs): 4
DPC count (execution time 2000-3999 µs): 1
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: chrome.exe

Total number of hard pagefaults 296
Hard pagefault count of hardest hit process: 142
Highest hard pagefault resolution time (µs): 69481.554231
Total time spent in hard pagefaults (%): 0.041433
Number of processes hit: 6


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 3.021647
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): 90.838846
CPU 0 DPC total execution time (s): 0.623584
CPU 0 DPC count: 560078
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 2.160852
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): 104.341154
CPU 1 DPC total execution time (s): 0.004178
CPU 1 DPC count: 763
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 1.924459
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): 93.910769
CPU 2 DPC total execution time (s): 0.077014
CPU 2 DPC count: 22615
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2.236446
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): 121.332308
CPU 3 DPC total execution time (s): 0.035366
CPU 3 DPC count: 3845
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2.135053
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): 139.323846
CPU 4 DPC total execution time (s): 0.159255
CPU 4 DPC count: 13849
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2.040968
CPU 5 ISR highest execution time (µs): 35.129231
CPU 5 ISR total execution time (s): 0.010481
CPU 5 ISR count: 1883
CPU 5 DPC highest execution time (µs): 98.7350
CPU 5 DPC total execution time (s): 0.013005
CPU 5 DPC count: 2827
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 2.070368
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): 126.820385
CPU 6 DPC total execution time (s): 0.076378
CPU 6 DPC count: 8681
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 1.971521
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): 104.038462
CPU 7 DPC total execution time (s): 0.003690
CPU 7 DPC count: 516
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 1.863697
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): 152.766538
CPU 8 DPC total execution time (s): 0.050793
CPU 8 DPC count: 6285
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 2.007455
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): 82.5950
CPU 9 DPC total execution time (s): 0.013926
CPU 9 DPC count: 2103
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 9.688131
CPU 10 ISR highest execution time (µs): 138.404231
CPU 10 ISR total execution time (s): 2.221911
CPU 10 ISR count: 304737
CPU 10 DPC highest execution time (µs): 5988.643462
CPU 10 DPC total execution time (s): 5.339058
CPU 10 DPC count: 549878
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 2.066497
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): 80.1250
CPU 11 DPC total execution time (s): 0.029060
CPU 11 DPC count: 2618
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 1.926844
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): 89.008846
CPU 12 DPC total execution time (s): 0.047473
CPU 12 DPC count: 5867
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 2.527983
CPU 13 ISR highest execution time (µs): 58.946154
CPU 13 ISR total execution time (s): 0.064709
CPU 13 ISR count: 6975
CPU 13 DPC highest execution time (µs): 93.597692
CPU 13 DPC total execution time (s): 0.019605
CPU 13 DPC count: 3279
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 1.870822
CPU 14 ISR highest execution time (µs): 0.0
CPU 14 ISR total execution time (s): 0.0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 95.949615
CPU 14 DPC total execution time (s): 0.049869
CPU 14 DPC count: 5867
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 2.232735
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): 121.154231
CPU 15 DPC total execution time (s): 0.048712
CPU 15 DPC count: 4693
_________________________________________________________________________________________________________

Ok, so now I figured that USBPORT.SYS spikes were caused by my headset microphone, didabled it and now the spikes occur with either NDIS.SYS, NVLDDMKM.SYS or DXGKRNL.SYS, If I disable one, another one causes the spikes, I think that the spikes only happen when watching youtube videos, still not sure about that.

Already did that, just installed an SSD and the problems persist, I think it passes from driver to driver in latencymon but the actual driver that's causing the problem is the network driver, I'm gonna be testing with different driver versions and see if I get any freezes/audio glitches with the SSD.

So I just found that my graphics card and a USB controller have the same IRQ PCI number, I think that might be causing the issue.
But I cannot disable the USB driver and I obviously need my GPU.