All computer speakers Popping/Crackling

[TripleBullet]

I have had the Logitech Z623 speakers. The Logitech's kept popping all the time even though they sounded amazing. Games, YouTube anything, they would just pop and crackle away and it was very annoying. I bought a Sound blaster Sound-card and the issue still persisted. So I swapped the Z623's for the Klipsch ProMedia 2.1 set. It wasn't the speakers. Sooooo.

I ran a LatenctMon test and it didn't turn out to hot. I don't know exactly where to go from here but some of you I know can help. I am not a huge audio person so this is getting into more unknown territory for me. I am not using a wifi chip. I am plugged directly into the router. I don't believe there are any throttling issues either as I am set to high performance via Power Management. My BIOS are up to date as well.

Looking for any ideas. Please and thanks!

Specs:

PC: Corsair 750D |

• 
  Asus Z270F
  Intel i7-7700k
  EVGA GTX 1070 SC SLI x 2
  16GB Corsair Vengeance LP
  Corsair RM750 80+ Gold
  500GB 960 Evo M.2/1TB
  Western Digital HDD
  Windows 10

_________________________________________________________________________________________________________
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. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results. 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:21:06 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-00TSIKQ
OS version: Windows 10 , 10.0, build: 17134 (x64)
Hardware: ASUSTeK COMPUTER INC., STRIX Z270F GAMING
CPU: GenuineIntel Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz
Logical processors: 8
Processor groups: 1
RAM: 16319 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 420 MHz
Measured CPU speed: 1 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.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.



_________________________________________________________________________________________________________
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): 2199.160564
Average measured interrupt to process latency (µs): 2.962373

Highest measured interrupt to DPC latency (µs): 1307.549679
Average measured interrupt to DPC latency (µs): 1.269040


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

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

Total time spent in ISRs (%) 1.09540

ISR count (execution time <250 µs): 6705766
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 1
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): 1048.808810
Driver with highest DPC routine execution time: NDIS.SYS - Network Driver Interface Specification (NDIS), Microsoft Corporation

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

Total time spent in DPCs (%) 0.697030

DPC count (execution time <250 µs): 14795927
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 390
DPC count (execution time 1000-1999 µs): 1
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.


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


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 115.382388
CPU 0 ISR highest execution time (µs): 285.733095
CPU 0 ISR total execution time (s): 67.792586
CPU 0 ISR count: 3886065
CPU 0 DPC highest execution time (µs): 1048.808810
CPU 0 DPC total execution time (s): 41.420472
CPU 0 DPC count: 9342438
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 63.550754
CPU 1 ISR highest execution time (µs): 157.330238
CPU 1 ISR total execution time (s): 42.612206
CPU 1 ISR count: 2514222
CPU 1 DPC highest execution time (µs): 650.689762
CPU 1 DPC total execution time (s): 18.369183
CPU 1 DPC count: 4567234
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 14.009517
CPU 2 ISR highest execution time (µs): 104.082381
CPU 2 ISR total execution time (s): 0.542755
CPU 2 ISR count: 305480
CPU 2 DPC highest execution time (µs): 698.973571
CPU 2 DPC total execution time (s): 8.887028
CPU 2 DPC count: 475614
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 4.712538
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): 173.399524
CPU 3 DPC total execution time (s): 0.280159
CPU 3 DPC count: 62648
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 5.190128
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): 173.0350
CPU 4 DPC total execution time (s): 0.368636
CPU 4 DPC count: 99126
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 4.474370
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): 172.850476
CPU 5 DPC total execution time (s): 0.298040
CPU 5 DPC count: 65437
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 5.181524
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): 172.969762
CPU 6 DPC total execution time (s): 0.430492
CPU 6 DPC count: 94796
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 4.693242
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): 245.983095
CPU 7 DPC total execution time (s): 0.544641
CPU 7 DPC count: 89025
_________________________________________________________________________________________________________

 

[stdragon]

Does it sound like it's an analog issue, or digital?

If it's analog popping/hissing, it's possible there's some grounding issues, perhaps with the wall outlet.

If it's digital, it might be due to any potential over-clocking if you have any such settings in place.

 

[TripleBullet]

Does it sound like it's an analog issue, or digital?

If it's analog popping/hissing, it's possible there's some grounding issues, perhaps with the wall outlet.

If it's digital, it might be due to any potential over-clocking if you have any such settings in place.

I don't have any over clocks. Run it all at stock settings. GPU's, CPU, RAM, the whole nine. I think it is probably a grounding issue. I have had the speakers plugged into two different Rocketfish power strips. The power strips were both on seperate sockets and they both have the "Grounded" light lit up. How do you test that exactly? To determine if they are grounded or not? Also when the computer is shut down or asleep the sub does hum. Which I feel like might indicate the grounding be the issue again as well.

 

[stdragon]

Power Gear 3 Wire Receptacle Tester, Outlet Tester, 6 Visual Indications, Light Indicator, UL Listed, Yellow, 50542
by Power Gear
Link: http://a.co/5WP38wy

Just be sure both the PC and speakers are connected to the same surge strip. Otherwise, you could end up with a grounding loop due to the difference in potential.