Windows 10: Excessive non-random audio popping/static with all media (Win 7/10)

We most definitely own the same case lol which are Antec mid-tower gaming cases https://www.amazon.com/Antec-Nine-Hu.../dp/B000I5JHB0 I am fairly certain he had a lot of interference on his top port as well. I also ain't gonna lie.. the cord situation is a bit of a mess in my case, and from what I remember his too. The main HDD (Windows) is at the very bottom of my case and about 5 or so inches across from the PSU along with a dozen or so wires almost touching the HDD from the PSU.... this actually sounds pretty terrible and stupid and I should probably move things around to make sure that isn't the cause.

I had HD Audio connected last from my top audio jacks to my motherboard, I will try the AC'97 input as well and see if the older audio codec does anything. I know it's older tech but worth a shot?

My older build had a Gigabyte GA-MA790X-UD4P GA-MA790X-UD4P (rev. 1.0) | Motherboard - GIGABYTE Global
of course all builds have ever only had AMD processors.

 

Well although you might not find an answer you are zero in on common ground.

 

Well it was at least worth a shot. My wiring is a bit more tidy now.

I decided to run LatencyMon for around 20 minutes while performing some light tasks (web surfing and listening to the odd song in WMP), figured I throw out some images and logs of the test in hopes there is something nasty in here for the pros to spot. Just to note: I know it says Windows 7 service pack 1, I have had this issue on both 7 and 10 (fully updated), I am just trying to figure it out so I have been going back and forth between the two OS quite a lot lately.







____________________________________________________________________________________________________ _____
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 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:31 (h:mm:ss) on all processors.


____________________________________________________________________________________________________ _____
SYSTEM INFORMATION
____________________________________________________________________________________________________ _____
Computer name: HELLRAZAH
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: MS-7693, MSI, 970 GAMING (MS-7693)
CPU: AuthenticAMD AMD FX(tm)-6300 Six-Core Processor
Logical processors: 6
Processor groups: 1
RAM: 7980 MB total


____________________________________________________________________________________________________ _____
CPU SPEED
____________________________________________________________________________________________________ _____
Reported CPU speed: 350 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): 27929.858806
Average measured interrupt to process latency (µs): 4.849968

Highest measured interrupt to DPC latency (µs): 339.366450
Average measured interrupt to DPC latency (µs): 1.643405


____________________________________________________________________________________________________ _____
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): 44.156286
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0.035685
Driver with highest ISR total time: hal.dll - Hardware Abstraction Layer DLL, Microsoft Corporation

Total time spent in ISRs (%) 0.049023

ISR count (execution time <250 µs): 1534348
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): 845.542571
Driver with highest DPC routine execution time: ndis.sys - NDIS 6.20 driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0.092655
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.

Total time spent in DPCs (%) 0.181568

DPC count (execution time <250 µs): 7579272
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 13
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: firefox.exe

Total number of hard pagefaults 5628
Hard pagefault count of hardest hit process: 2514
Highest hard pagefault resolution time (µs): 505781.346857
Total time spent in hard pagefaults (%): 0.118780
Number of processes hit: 12


____________________________________________________________________________________________________ _____
PER CPU DATA
____________________________________________________________________________________________________ _____
CPU 0 Interrupt cycle time (s): 33.294874
CPU 0 ISR highest execution time (µs): 44.156286
CPU 0 ISR total execution time (s): 2.876292
CPU 0 ISR count: 1316136
CPU 0 DPC highest execution time (µs): 220.034571
CPU 0 DPC total execution time (s): 8.639556
CPU 0 DPC count: 6668622
____________________________________________________________________________________________________ _____
CPU 1 Interrupt cycle time (s): 14.987532
CPU 1 ISR highest execution time (µs): 38.1920
CPU 1 ISR total execution time (s): 0.113584
CPU 1 ISR count: 25476
CPU 1 DPC highest execution time (µs): 166.317714
CPU 1 DPC total execution time (s): 0.632362
CPU 1 DPC count: 89438
____________________________________________________________________________________________________ _____
CPU 2 Interrupt cycle time (s): 18.309408
CPU 2 ISR highest execution time (µs): 40.311143
CPU 2 ISR total execution time (s): 0.115840
CPU 2 ISR count: 25609
CPU 2 DPC highest execution time (µs): 845.542571
CPU 2 DPC total execution time (s): 0.826813
CPU 2 DPC count: 167432
____________________________________________________________________________________________________ _____
CPU 3 Interrupt cycle time (s): 16.621125
CPU 3 ISR highest execution time (µs): 37.2120
CPU 3 ISR total execution time (s): 0.113179
CPU 3 ISR count: 25555
CPU 3 DPC highest execution time (µs): 120.292571
CPU 3 DPC total execution time (s): 0.618781
CPU 3 DPC count: 97104
____________________________________________________________________________________________________ _____
CPU 4 Interrupt cycle time (s): 10.487339
CPU 4 ISR highest execution time (µs): 37.915429
CPU 4 ISR total execution time (s): 0.127648
CPU 4 ISR count: 29169
CPU 4 DPC highest execution time (µs): 191.866286
CPU 4 DPC total execution time (s): 0.893159
CPU 4 DPC count: 184287
____________________________________________________________________________________________________ _____
CPU 5 Interrupt cycle time (s): 18.610620
CPU 5 ISR highest execution time (µs): 41.001143
CPU 5 ISR total execution time (s): 0.453361
CPU 5 ISR count: 112403
CPU 5 DPC highest execution time (µs): 130.404857
CPU 5 DPC total execution time (s): 2.463316
CPU 5 DPC count: 372402
____________________________________________________________________________________________________ _____

 

From your post # 12

I'm not sure what this means.

Is your CPU throttling? If so, have you checked your temps?
Also, if your GPU is throttling temps could be a problem.
Both CPU and GPU temps could cause the fan speeds to change. This might create the noise. It will depend a lot on the quality of your fans.

I did read that you move a few times. Not knowing what you took with you on your moves like a desk lamp, fan, heater ect. was the reason I asked. With that many moves I doubt if your problem is a wall socket.

Now I'm going way out on the limb.
Remove your internet modem connection to the computer and test.
Remove all usb items and other external connected items except the power supply cable and head phones and test.
If by chance things are good, plug things back in one at a time and test.

**Fireberd will have to evaluate your post #16. All that means nothing to me.
Fireberd is the sound person.


Jack

 

Sorry for the confusion, I was typing out what LatencyMon always states when the program is showing problems, it asks you to disable CPU throttling in control panel or BIOs settings, I was just short terming the message basically in a confusing way :/ Sorry 'bout that! MY PC temps are pretty good across the board.

I will disconnecting everything tomorrow including the internet and give that a shot.

Thanks for the help all.

 

This is a "stock" statement. Don't put much in that. It comes up anytime it detects problems, regardless of what it is. I'm pushed for time right now. I'll try to analyze it later and get back.

Jack

 

I would shut off any over clocks and I would load the BIOS defaults. Think you might have done that already but just to be sure.

 

Can you run Latency Mon on Win 10, with Realtek and not the Windows installed HD Audio driver. Do not have any browser or any other program running. See what it tells you.