Popping noise with new build

Associate
Joined
20 May 2010
Posts
61
I recently bought new components which was recommended by forum users. I got the following:

MSI Radeon R9 280 Gaming 3072MB
AMD Piledriver FX-6 Six Core 6300 Black Edition 3.50GHz
MSI 970A-G46 AMD 970A (Socket AM3+)
TeamGroup Elite Black 8GB (2x4GB) DDR3 PC3-12800C11 1600MHz
SuperFlower Amazon 450W "80 Plus Bronze"

Now, after installing windows 7 Ultimate and all the drivers from the disc. As well as the latest Catalyst drivers. I'm constantly hearing a 'popping' sound from my monitor. I use HDMI, which was by the same cable I've always used and this didn't occur before putting the new parts together. The 'popping' sounds occur in 2-3 second intervals and it's only when I have the sound on. I've tried connecting my monitor through HDMI to my wifes computer and it didn't happen.

I'm not sure what's causing this problem, but it's incredibly annoying to hear it. I've tried re-installing all sound drivers. Realtek HDMI drivers, ATI high definition audio driver. Weird thing is.. When I had no audio drivers at all, the basic windows audio worked without the popping noise. But when I install catalyst without audio, it comes back.

Other things I've tried:

Disabling all audio enhancements
Changed all the sample rate and bit depth options, nothing changed


Hopefully someone can help me figure out this issue as it's driving me mad.

Thanks.
 
You could try this:

run: msconfig and disable the auto start of the Realtekaudio drivers
Boot in to windoze, go to the speaker icon (by the clock/sys tray)
right click and select playback devices.
disable all the devices you do not need or use including the other HDMI ports and try make sure you are using HMDI port 0 only between GFX and monitor

also go to Realtek digital output and select properties, then supported formats (make sure DTS & Dolby Digital are ticked and also set the sample rate to 48Khz
now go to the enhancements tab and tick disable all sound enhancements and untick intermediate mode
 
Tried all the above, but didn't change anything. However, setting PP_SclkDeepSleepDisable to 1 in the registry seems to of fixed it. Not sure how or why, but it did.

Thanks you for the replies.
 
Back
Top Bottom