Solved Audio buzzing problem when watching twitch.tv or Youtube

I started having audio issues yesterday when I would watch twitch.tv or youtube and searched around trying to find answers for the problem. I updates all of my drivers and changed power management to see if it would fix the problem, but it didn't I saw a few answers to run LatencyMon to see what the problem was and this is the full report I have after running it. I have a Lenovo Y410P

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


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: 20216, LENOVO, VIQY0Y1
CPU: GenuineIntel Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Logical processors: 8
Processor groups: 1
RAM: 8104 MB total


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


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

Highest measured interrupt to DPC latency (µs): 11331.941466
Average measured interrupt to DPC latency (µs): 1.488981


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

Highest reported total ISR routine time (%): 0.000647
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%) 0.000707

ISR count (execution time <250 µs): 2898
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): 13775.916040
Driver with highest DPC routine execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Highest reported total DPC routine time (%): 0.090788
Driver with highest DPC total execution time: Wdf01000.sys - Kernel Mode Driver Framework Runtime, Microsoft Corporation

Total time spent in DPCs (%) 0.140198

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

Total number of hard pagefaults 24313
Hard pagefault count of hardest hit process: 15717
Highest hard pagefault resolution time (µs): 2791832.274436
Total time spent in hard pagefaults (%): 4.044322
Number of processes hit: 13


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 13.206760
CPU 0 ISR highest execution time (µs): 36.380952
CPU 0 ISR total execution time (s): 0.005638
CPU 0 ISR count: 766
CPU 0 DPC highest execution time (µs): 13775.916040
CPU 0 DPC total execution time (s): 2.629188
CPU 0 DPC count: 1281499
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 12.076505
CPU 1 ISR highest execution time (µs): 43.497076
CPU 1 ISR total execution time (s): 0.016321
CPU 1 ISR count: 989
CPU 1 DPC highest execution time (µs): 12354.798246
CPU 1 DPC total execution time (s): 1.500029
CPU 1 DPC count: 52561
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 6.577201
CPU 2 ISR highest execution time (µs): 42.119048
CPU 2 ISR total execution time (s): 0.001204
CPU 2 ISR count: 147
CPU 2 DPC highest execution time (µs): 11098.104010
CPU 2 DPC total execution time (s): 0.231866
CPU 2 DPC count: 36389
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 12.970073
CPU 3 ISR highest execution time (µs): 43.490393
CPU 3 ISR total execution time (s): 0.003084
CPU 3 ISR count: 316
CPU 3 DPC highest execution time (µs): 12396.414787
CPU 3 DPC total execution time (s): 0.712617
CPU 3 DPC count: 22694
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 5.382472
CPU 4 ISR highest execution time (µs): 25.184628
CPU 4 ISR total execution time (s): 0.000422
CPU 4 ISR count: 67
CPU 4 DPC highest execution time (µs): 5504.54010
CPU 4 DPC total execution time (s): 0.120791
CPU 4 DPC count: 19220
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 12.205397
CPU 5 ISR highest execution time (µs): 37.991646
CPU 5 ISR total execution time (s): 0.002554
CPU 5 ISR count: 278
CPU 5 DPC highest execution time (µs): 11758.441103
CPU 5 DPC total execution time (s): 0.611787
CPU 5 DPC count: 17503
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 6.223893
CPU 6 ISR highest execution time (µs): 26.085213
CPU 6 ISR total execution time (s): 0.000512
CPU 6 ISR count: 89
CPU 6 DPC highest execution time (µs): 6822.874687
CPU 6 DPC total execution time (s): 0.151392
CPU 6 DPC count: 23560
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 12.698931
CPU 7 ISR highest execution time (µs): 38.745196
CPU 7 ISR total execution time (s): 0.002456
CPU 7 ISR count: 246
CPU 7 DPC highest execution time (µs): 6320.807018
CPU 7 DPC total execution time (s): 0.425527
CPU 7 DPC count: 16466
_________________________________________________________________________________________________________

The Latency Mon can overwhelm with data and sometimes hard to interpret (at least for me).

However, one thing I see reference is "High Definition Audio Bus driver, which suggests you do not have the correct sound driver installed. In most cases if the generic, basic function, Windows installed High Definition Audio Drivers (Codec) is installed that says the correct sound driver has not been installed. The High Definition Audio can also be installed for HDMI Audio (if you have HDMI) and that can also indicate the correct HDMI audio driver has not been installed. You specific model uses RealTek for the PC audio and can have either Intel or NVIDIA for HDMI (depending on optional video).

Considering the audio does not appear to have the correct drivers, install the proper drivers and see if that makes any difference as a first step.

I updated my realtek driver to the newest version and I haven't been getting the buzzing problem anymore. Thank you for the help.

Wow! that was easier than I thought. But, glad to hear it is working OK