Windows 10: Major Issues With Graphics and Audio Windows 10

Hi there,

I have recently upgraded to Windows 10. However, ever since I have done this I am having issues with my audio. I use a LG TV as my monitor which I have connected via HDMI. However, whenever watching a video or listening to music on Spotify, a occasional buzz can be heard. It usually lasts about half a second and then continues.

In addition, when playing a game online, the game will occasionally freeze and the sound will buzz at the same time. This lasts no longer then 1/2-1 second and then the game carries on only to happen again 5-10 secs later. However, occasionally there does seem to be periods when the game plays as it should.

So far I have tried uninstalling and reinstalling my network, graphics and sound card drivers which didn't work. Any additional suggestions will be welcome. I should also say I never had any problems on Windows 8.1

My specs:

AMD Radeon 7800 Series graphics card
Intel I7 Processor (quad core)
Realtek sound card (though actual sound comes from LG TV).

Thanks

:)

 

Audio issues with latest major feature Windows 10 feature release

Thank you for the reply. I have tried those steps you have listed above, but they didn't make any difference. My computer has an Asus P7P55D-E Pro motherboard. The audio solution embedded on it is from VIA. Here is the link to the download page for the Windows
10 driver for the audio chip, which I installed when I upgraded from Windows 7 Pro to Windows 10 Pro a few months back:

VIA Audio Driver for Windows 10









I have included some screenshots to hopefully help see what happens when I plug in my headset. The only thing I didn't capture was the box that pops up from Windows saying that it needs to "disable audio enhancement features" when I go to switch the default
sound device from my computer speakers to my headset. The first screenshot clearly shows Windows not recognizing the microphone on my headset, even though it is plugged in. So I can get it to work, but what I have to do is run the "Troubleshoot sound problems"
wizard, and it removes the audio from the computer and has me restart. Once I do that, everything is working as it should (Windows recognizes my headset properly and I can get onto Teamspeak). The other two screenshots I provided show what happens when I plug
my headset in. The VIA control panel pops up showing that it sensed I plugged my headset into the front jacks on my computer, just as it should.

Any other ideas??? Do I have to pray and hope VIA will come out with another driver that bypasses whatever the Windows Update broke?

 

Audio issues with latest major feature Windows 10 feature release

The latest "feature release" through Windows Update has somehow created audio issues I didn't have before the update. Every time I plug in my headset into the mic and headphone jacks, my VIA audio control panel recognizes them and all is good. Before whatever
latest feature update was installed onto my computer, I would right click on the audio icon on the taskbar, and set the headphones as default, and all was fine. I could then go into Teamspeak, and everything worked. Now none of that works. When I plug in my
headset into the front jacks on my computer, VIA pops up like it always does. But when I got to change the default sound device from my speakers to my headset, Windows pops up with some annoying error about disabling "sound enhancements" or something, and
so I say yes. But when I look at the audio device properties, my headset microphone is not be recognized by Windows. This never happened before the update. So I run the audio troubleshooter, and restart the computer, and my audio is working again. But I have
to do this every time I want to use my headset. What was broken by the Windows update? Do I have to hope that VIA comes out with an audio driver to bypass whatever was broken by this supposed latest, greatest release of Windows 10.

 

How is the PC connected to the TV..?
Can you post details of the GFX AMD driver you are using at the moment..

 

Sorry I have now given up and rolled back to Windows 8.1 which now works as it should.

I'll mark this as solved.

 

Better to mark it as "Dodged.." *Wink