Win 10 popping noises

SeekaX

New member
Hey guys, today i installed the anniversary update and since then i keep getting sound popping noises whenever sound starts or stops, i'm fairly sure it's some dumb power saving feature. It's especially annoying when sound starts because it causes the sound to cut out for the first half second or so. The only solution i found online was setting the minimum processor state to 100%, but that didn't work for me. I also did a clean install of win10, but the problem remains. I use a FiiO E10, so there are no drivers interfering either. Any ideas?
/edit
The issue disappears when i use onboard sound, so it must be USB related.
 
Last edited:
There could still be drivers interfering. Try running latencymon to see if it highlights any problems.
 
There could still be drivers interfering. Try running latencymon to see if it highlights any problems.

8ppq6Fy.png
 
Are you running on high performance power profile? Because even in balanced windows will cut off power to usb devices if not used
 
reading that says nvidia driver, do you install the HD audio drivers with your card? if so try only installing driver and physx (i imagine you already do, but looking at that report says nvidia driver to me)
 
reading that says nvidia driver, do you install the HD audio drivers with your card? if so try only installing driver and physx (i imagine you already do, but looking at that report says nvidia driver to me)

I uninstalled all nvidia drivers and the issue remained.
/edit
Disregard the Latencymon reading, it came from me booting up a game for testing, i get the same results when using onboard sound.
/edit 2
Just got my flatmates FiiO E10, same model and everything, it doesn't have the issue. ??? never been so confused in my life.
 
Last edited:
Luckily my flatmate doesn't need his E10 so i am using that now. We have tested my E10 on his PC and it worked without any issues, so the E10 is definitely fine.
 
Luckily my flatmate doesn't need his E10 so i am using that now. We have tested my E10 on his PC and it worked without any issues, so the E10 is definitely fine.

proper bizzar stuff going on there.. at least you found a (somewhat dissatisfactory) fix
 
proper bizzar stuff going on there.. at least you found a (somewhat dissatisfactory) fix

I wasn't even going to try it at first because no matter what the cause of the problem was switching an amp for an identical amp seemed to address none of them. Even now that i have a fix i can't pinpoint what the issue may have been. Couldn't have been drivers or USB power management because else the other amp wouldn't work, can't be the amp itself because otherwise it wouldn't work on a different PC. The magical world of IT support, no one knows where the issue comes from and when it is fixed no one knows why.
 
I wasn't even going to try it at first because no matter what the cause of the problem was switching an amp for an identical amp seemed to address none of them. Even now that i have a fix i can't pinpoint what the issue may have been. Couldn't have been drivers or USB power management because else the other amp wouldn't work, can't be the amp itself because otherwise it wouldn't work on a different PC. The magical world of IT support, no one knows where the issue comes from and when it is fixed no one knows why.

Have you tried switching it back to your other one? does the popping come back?
 
Have you tried switching it back to your other one? does the popping come back?

Yea i have and it does come back. Same USB port, same headphones, same USB cable even.


No i haven't yet, but most of the stuff listed there i've already done, except for the ASIO driver, but that seems like an unlikely fix considering that a second identical amp/dac works without any issues.
 
It might be a bad capacitor that is nearly dead, but the fact that the e10k works on your friend's PC without a problem.. Makes it hard to explain that...
 
Could be something to do with the USB driver and the hardware ID. May have set an incorrect setting. Can only suggest trying other USB ports, like a USB3.0 or something.
 
Could be something to do with the USB driver and the hardware ID. May have set an incorrect setting. Can only suggest trying other USB ports, like a USB3.0 or something.

The problem was consistent across all USB ports. My only idea would be that windows pulled some driver before i disabled the autoupdates and that driver only works with the specific piece of hardware it was installed for.
 
Glad you've posted this, (well not glad) but it kind of makes me relieved. My missus PC has been doing the same thing since the Anniversary update and it drives me nuts! But not as much as the fact no mobile devices are detected anymore, be that Windows Mobile or Android they simply aren't recongnised anymore and Microsoft are about as helpful as a chocolate fire guard.
 
Back
Top