Hi Emanuele Greco,
Thanks for taking the time to explain everything you've already tried. It sounds like you've been very thorough with your troubleshooting and I can understand why it's frustrating to still be dealing with the issue after several months.
Since you've already tested different audio devices, output ports, Realtek and Microsoft audio drivers, power settings, BIOS options and even a USB DAC, I'd rather not send you back through the same troubleshooting you've already done.
To help narrow things down further, could you let me know your Windows version and build number (Win + R > winver) and your motherboard or PC model?
I'd also suggest trying two tests that can help determine whether something in Windows is contributing to the behavior.
First, test in a Clean Boot environment:
- Press Windows + R, type msconfig and press Enter.
- Open the Services tab then check Hide all Microsoft services.
- Click Disable all.
- Open the Startup tab and select Open Task Manager.
- Disable all startup items then restart the PC.
*Disclaimer: A "clean boot" starts Windows with a minimal set of drivers and startup programs. It helps to determine whether a background service is interfering with your game or program and to isolate the cause of a problem.
These steps of "clean boot" might look complicated at first glance. However, to avoid any trouble for you, please follow them in order and step-by-step so that it will help you get back on track.
Once Windows starts back up, try the actions that normally trigger the popping sound, such as pausing a video, changing the volume, dismissing notifications or pausing audio in a game.
I'd also recommend testing with a new local user profile:
- Open Settings > Accounts > Other users and select Add account.
- Choose I don't have this person's sign-in information > Add a user without a Microsoft account.
- Create a temporary local account.
- Sign out and sign in to the new account.
- Test the same audio scenarios before changing any settings.
If the popping disappears during either test, that will point to a software, service or profile-related cause. If it still happens in both cases, that helps narrow the scope further.
While that wouldn't automatically confirm a hardware problem, it may suggest the behavior is related to the motherboard's audio implementation, firmware, chipset or another hardware-specific interaction. In that situation, it may also be worth checking with your PC or motherboard manufacturer to see whether there are any newer BIOS, chipset or audio-related updates, or whether they've received similar reports for your model.
Let me know the results of these checks and your winver information, I'll be happy to take a closer look.
If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.