Audio crackling and popping with different audio devices (Windows 10)
I've been having this weird audio problem somewhat related to CPU/GPU load with every audio device I've tried.
Under moderate load, audio starts to crackle and pop, no matter what audio device I'm using. I've tried USB audio (Logitech G930) and on-board Realtek audio drivers, using them with Microsoft basic drivers or manufacturer supplied drivers. I have reinstalled Windows several times. I've also tried with Windows 7 (my current OS is Windows 10), and IIRC the problem persisted there.
Weird thing is, that with Steam In-Home streaming to another computer, audio works just fine (on the client computer the audio is crystal clear, but on the sending computer the audio is cracking and popping). I've also tried the same by streaming audio to another computer using Voicemeeter/VBAN, but the problem persists there. So I'm suspecting that Windows' audio handling does something weird (buffer underruns or something) and I've been trying to give audio processes/services higher priority, but without success.
I've also updated the UEFI/BIOS.
My computers specs also shouldn't be a problem:
- Intel i5-6600K
- NVidia GTX 1070 (also tried with 550 Ti and 680)
- 8 GB of RAM (Kingston HyperX Fury Black 2 x 4 GB (DDR4, 2666 MHz, CL15))
- Asus Z170-A (motherboard, with Realtek on-board audio)
- Logitech G930 (USB wireless audio)
Some people have found success by disabling possible audio enhancements or tweaking power settings, but I've tried those too. I have also disabled every audio device and tried them one by one, with Windows default basic drivers. Problem persists.
What could I possibly do next?
windows-7 windows-10 audio
asked Jan 23 '17 at 19:09
zini
112
|
show 6 more comments
I've been having this weird audio problem somewhat related to CPU/GPU load with every audio device I've tried.
Under moderate load, audio starts to crackle and pop, no matter what audio device I'm using. I've tried USB audio (Logitech G930) and on-board Realtek audio drivers, using them with Microsoft basic drivers or manufacturer supplied drivers. I have reinstalled Windows several times. I've also tried with Windows 7 (my current OS is Windows 10), and IIRC the problem persisted there.
Weird thing is, that with Steam In-Home streaming to another computer, audio works just fine (on the client computer the audio is crystal clear, but on the sending computer the audio is cracking and popping). I've also tried the same by streaming audio to another computer using Voicemeeter/VBAN, but the problem persists there. So I'm suspecting that Windows' audio handling does something weird (buffer underruns or something) and I've been trying to give audio processes/services higher priority, but without success.
I've also updated the UEFI/BIOS.
My computers specs also shouldn't be a problem:
- Intel i5-6600K
- NVidia GTX 1070 (also tried with 550 Ti and 680)
- 8 GB of RAM (Kingston HyperX Fury Black 2 x 4 GB (DDR4, 2666 MHz, CL15))
- Asus Z170-A (motherboard, with Realtek on-board audio)
- Logitech G930 (USB wireless audio)
Some people have found success by disabling possible audio enhancements or tweaking power settings, but I've tried those too. I have also disabled every audio device and tried them one by one, with Windows default basic drivers. Problem persists.
What could I possibly do next?
windows-7 windows-10 audio
asked Jan 23 '17 at 19:09
zini
112
Try swapping your default audio from 48kHz to 44.1kHz in your sound manager.
– Tetsujin
Jan 23 '17 at 19:13
Check the screws that hold the motherboard to the case. Make sure they are tight Excessive crackling like this this is often a grounding issue and your electronics/case may not be properly grounded. Also, if you are using an external audio front panel, I would recommend using the built in audio on the back of the computer instead.
– Narzard
Jan 23 '17 at 19:13
@Tetsujin I've tried with 44.1kHz with different audio devices, problem persists.
– zini
Jan 23 '17 at 19:17
@Narzard I've tried with both front and back connectors AND with USB audio device (which shouldn't be affected by possible grounding issues), problem persists.
– zini
Jan 23 '17 at 19:17
btw, crackling is not a grounding issue, it's a decoding/timing issue
– Tetsujin
Jan 23 '17 at 19:25
|
show 6 more comments
I've been having this weird audio problem somewhat related to CPU/GPU load with every audio device I've tried.
Under moderate load, audio starts to crackle and pop, no matter what audio device I'm using. I've tried USB audio (Logitech G930) and on-board Realtek audio drivers, using them with Microsoft basic drivers or manufacturer supplied drivers. I have reinstalled Windows several times. I've also tried with Windows 7 (my current OS is Windows 10), and IIRC the problem persisted there.
Weird thing is, that with Steam In-Home streaming to another computer, audio works just fine (on the client computer the audio is crystal clear, but on the sending computer the audio is cracking and popping). I've also tried the same by streaming audio to another computer using Voicemeeter/VBAN, but the problem persists there. So I'm suspecting that Windows' audio handling does something weird (buffer underruns or something) and I've been trying to give audio processes/services higher priority, but without success.
I've also updated the UEFI/BIOS.
My computers specs also shouldn't be a problem:
- Intel i5-6600K
- NVidia GTX 1070 (also tried with 550 Ti and 680)
- 8 GB of RAM (Kingston HyperX Fury Black 2 x 4 GB (DDR4, 2666 MHz, CL15))
- Asus Z170-A (motherboard, with Realtek on-board audio)
- Logitech G930 (USB wireless audio)
Some people have found success by disabling possible audio enhancements or tweaking power settings, but I've tried those too. I have also disabled every audio device and tried them one by one, with Windows default basic drivers. Problem persists.
What could I possibly do next?
windows-7 windows-10 audio
asked Jan 23 '17 at 19:09
zini
112
I've been having this weird audio problem somewhat related to CPU/GPU load with every audio device I've tried.
Under moderate load, audio starts to crackle and pop, no matter what audio device I'm using. I've tried USB audio (Logitech G930) and on-board Realtek audio drivers, using them with Microsoft basic drivers or manufacturer supplied drivers. I have reinstalled Windows several times. I've also tried with Windows 7 (my current OS is Windows 10), and IIRC the problem persisted there.
Weird thing is, that with Steam In-Home streaming to another computer, audio works just fine (on the client computer the audio is crystal clear, but on the sending computer the audio is cracking and popping). I've also tried the same by streaming audio to another computer using Voicemeeter/VBAN, but the problem persists there. So I'm suspecting that Windows' audio handling does something weird (buffer underruns or something) and I've been trying to give audio processes/services higher priority, but without success.
I've also updated the UEFI/BIOS.
My computers specs also shouldn't be a problem:
- Intel i5-6600K
- NVidia GTX 1070 (also tried with 550 Ti and 680)
- 8 GB of RAM (Kingston HyperX Fury Black 2 x 4 GB (DDR4, 2666 MHz, CL15))
- Asus Z170-A (motherboard, with Realtek on-board audio)
- Logitech G930 (USB wireless audio)
Some people have found success by disabling possible audio enhancements or tweaking power settings, but I've tried those too. I have also disabled every audio device and tried them one by one, with Windows default basic drivers. Problem persists.
What could I possibly do next?
windows-7 windows-10 audio
windows-7 windows-10 audio
asked Jan 23 '17 at 19:09
zini
112
asked Jan 23 '17 at 19:09
zini
112
asked Jan 23 '17 at 19:09
zini
112
asked Jan 23 '17 at 19:09
zini
112
asked Jan 23 '17 at 19:09
zini
112
112
Try swapping your default audio from 48kHz to 44.1kHz in your sound manager.
– Tetsujin
Jan 23 '17 at 19:13
Check the screws that hold the motherboard to the case. Make sure they are tight Excessive crackling like this this is often a grounding issue and your electronics/case may not be properly grounded. Also, if you are using an external audio front panel, I would recommend using the built in audio on the back of the computer instead.
– Narzard
Jan 23 '17 at 19:13
@Tetsujin I've tried with 44.1kHz with different audio devices, problem persists.
– zini
Jan 23 '17 at 19:17
@Narzard I've tried with both front and back connectors AND with USB audio device (which shouldn't be affected by possible grounding issues), problem persists.
– zini
Jan 23 '17 at 19:17
btw, crackling is not a grounding issue, it's a decoding/timing issue
– Tetsujin
Jan 23 '17 at 19:25
|
show 6 more comments
Try swapping your default audio from 48kHz to 44.1kHz in your sound manager.
– Tetsujin
Jan 23 '17 at 19:13
Check the screws that hold the motherboard to the case. Make sure they are tight Excessive crackling like this this is often a grounding issue and your electronics/case may not be properly grounded. Also, if you are using an external audio front panel, I would recommend using the built in audio on the back of the computer instead.
– Narzard
Jan 23 '17 at 19:13
@Tetsujin I've tried with 44.1kHz with different audio devices, problem persists.
– zini
Jan 23 '17 at 19:17
@Narzard I've tried with both front and back connectors AND with USB audio device (which shouldn't be affected by possible grounding issues), problem persists.
– zini
Jan 23 '17 at 19:17
btw, crackling is not a grounding issue, it's a decoding/timing issue
– Tetsujin
Jan 23 '17 at 19:25
Try swapping your default audio from 48kHz to 44.1kHz in your sound manager.
– Tetsujin
Jan 23 '17 at 19:13
Try swapping your default audio from 48kHz to 44.1kHz in your sound manager.
– Tetsujin
Jan 23 '17 at 19:13
Check the screws that hold the motherboard to the case. Make sure they are tight Excessive crackling like this this is often a grounding issue and your electronics/case may not be properly grounded. Also, if you are using an external audio front panel, I would recommend using the built in audio on the back of the computer instead.
– Narzard
Jan 23 '17 at 19:13
Check the screws that hold the motherboard to the case. Make sure they are tight Excessive crackling like this this is often a grounding issue and your electronics/case may not be properly grounded. Also, if you are using an external audio front panel, I would recommend using the built in audio on the back of the computer instead.
– Narzard
Jan 23 '17 at 19:13
@Tetsujin I've tried with 44.1kHz with different audio devices, problem persists.
– zini
Jan 23 '17 at 19:17
@Tetsujin I've tried with 44.1kHz with different audio devices, problem persists.
– zini
Jan 23 '17 at 19:17
@Narzard I've tried with both front and back connectors AND with USB audio device (which shouldn't be affected by possible grounding issues), problem persists.
– zini
Jan 23 '17 at 19:17
@Narzard I've tried with both front and back connectors AND with USB audio device (which shouldn't be affected by possible grounding issues), problem persists.
– zini
Jan 23 '17 at 19:17
btw, crackling is not a grounding issue, it's a decoding/timing issue
– Tetsujin
Jan 23 '17 at 19:25
btw, crackling is not a grounding issue, it's a decoding/timing issue
– Tetsujin
Jan 23 '17 at 19:25
|
show 6 more comments
2 Answers
2
active
oldest
votes
keep default settings (default buffer size) and select your best audio device as output A1 (giving the main stream) : First try ASIO device or WDM/KS... use MME device at the end if nothing works. Check you have no audio conflict (audio device not used twice by several apps).
Think about installing last version (currently presented on vb-audio facebook/g+) Voicemeeter 2017 Version 2.0.3.2 / 1.0.5.2 (REBOOT after de-installation, REBOOT after installation)...
If the problem remains, you may contact vb-audio with a screenshot of your Voicemeeter and its system settings dialog box.
answered Jan 24 '17 at 5:33
user258609
32116
I think you possibly misread the question. I'm not having specifically Voicemeeter problems, but other audio problem that didn't solve itself when trying with Voicemeeter.
– zini
Jan 24 '17 at 14:55
ok, right, your problem seems to be more located on system or driver level (maybe motherboard bus or bad video/network driver can disturb windows timing) but keeping default settings on Voicemeeter and select your best audio device as output A1 can help anyway.
– user258609
Jan 25 '17 at 15:36
add a comment |
You get DPC issues with come from the Microsoft USB 3.0 driver USBXHCI.SYS:
Total = 11776 for module USBXHCI.SYS
Elapsed Time, > 256 usecs AND <= 512 usecs, 12, or 0.10%
Elapsed Time, > 512 usecs AND <= 1024 usecs, 1, or 0.01%
Elapsed Time, > 1024 usecs AND <= 2048 usecs, 0, or 0.00%
Elapsed Time, > 2048 usecs AND <= 4096 usecs, 7, or 0.06%
Elapsed Time, > 4096 usecs AND <= 8192 usecs, 1, or 0.01%
Total, 11776
Everything over 1024µs is bad and you have 8 spikes where it takes longer and this causes the audio drops. Connect your USB devices that don't require fast data transfer (mouse, keyboard) to USB 2.0 ports and not USB 3.0 ones.
Also the NDIS.sys causes some drops:
Total = 3960 for module ndis.sys
Elapsed Time, > 1024 usecs AND <= 2048 usecs, 3, or 0.08%
Elapsed Time, > 2048 usecs AND <= 4096 usecs, 17, or 0.43%
Total, 3960
So update the network card drivers and all network related drivers.
If the sound/audio is fine over Displayport or HDMI on an external Monitor/TV, the cheap Realtek audio chip is causing the issue.
Buy a soundcard with a better audio chip like the ASUS Strix Soar
and connect your headphones to this sound card and disable the Realtek chip in BIOS.
answered Jan 25 '17 at 15:08
magicandre1981
81k20123202
Few spikes sounds a lot less than it feels. The audio very bad under some load. I switched every USB device to USB 2.0 ports, disabled networking entirely, but the audio is still crackling under load. I took another trace without networking: dl.dropboxusercontent.com/s/hjhajrinm4dadd3/…
– zini
Jan 25 '17 at 16:43
the new trace shows less spikes, only 2 (1 in USB3 driver and 1 in storport.sys - storage related driver) that reach 1024µs. But I still see that the logitech driver LGSHidFilt.sys is called by the usb3 driver. Was the sound still so bad when you captured the new trace?
– magicandre1981
Jan 26 '17 at 16:11
Yes, the sound was still as bad as before. My wireless headset is by Logitech, so that's the driver. The headset was plugged into USB 2.0 port, so that's weird that USB3 driver would try to use it.
– zini
Jan 26 '17 at 17:10
ok, in this case the issues are not caused by DPCs. connect a Monitor/TV via HDMI so that the audio of the GPU is used. look if the sound from the TV is also bad or not.
– magicandre1981
Jan 26 '17 at 17:36
Huh, audio through DisplayPort -> Display -> Headphone out -> Wired headphones is just fine with no crackling. Weird, I was pretty sure that I did try audio through GPU before. Maybe the display has audio buffer? Still, this is a workaround at best. I'd still like to use my wireless headphones.
– zini
Jan 26 '17 at 18:10
|
show 9 more comments
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1170712%2faudio-crackling-and-popping-with-different-audio-devices-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
keep default settings (default buffer size) and select your best audio device as output A1 (giving the main stream) : First try ASIO device or WDM/KS... use MME device at the end if nothing works. Check you have no audio conflict (audio device not used twice by several apps).
Think about installing last version (currently presented on vb-audio facebook/g+) Voicemeeter 2017 Version 2.0.3.2 / 1.0.5.2 (REBOOT after de-installation, REBOOT after installation)...
If the problem remains, you may contact vb-audio with a screenshot of your Voicemeeter and its system settings dialog box.
answered Jan 24 '17 at 5:33
user258609
32116
I think you possibly misread the question. I'm not having specifically Voicemeeter problems, but other audio problem that didn't solve itself when trying with Voicemeeter.
– zini
Jan 24 '17 at 14:55
ok, right, your problem seems to be more located on system or driver level (maybe motherboard bus or bad video/network driver can disturb windows timing) but keeping default settings on Voicemeeter and select your best audio device as output A1 can help anyway.
– user258609
Jan 25 '17 at 15:36
add a comment |
keep default settings (default buffer size) and select your best audio device as output A1 (giving the main stream) : First try ASIO device or WDM/KS... use MME device at the end if nothing works. Check you have no audio conflict (audio device not used twice by several apps).
Think about installing last version (currently presented on vb-audio facebook/g+) Voicemeeter 2017 Version 2.0.3.2 / 1.0.5.2 (REBOOT after de-installation, REBOOT after installation)...
If the problem remains, you may contact vb-audio with a screenshot of your Voicemeeter and its system settings dialog box.
answered Jan 24 '17 at 5:33
user258609
32116
I think you possibly misread the question. I'm not having specifically Voicemeeter problems, but other audio problem that didn't solve itself when trying with Voicemeeter.
– zini
Jan 24 '17 at 14:55
ok, right, your problem seems to be more located on system or driver level (maybe motherboard bus or bad video/network driver can disturb windows timing) but keeping default settings on Voicemeeter and select your best audio device as output A1 can help anyway.
– user258609
Jan 25 '17 at 15:36
add a comment |
keep default settings (default buffer size) and select your best audio device as output A1 (giving the main stream) : First try ASIO device or WDM/KS... use MME device at the end if nothing works. Check you have no audio conflict (audio device not used twice by several apps).
Think about installing last version (currently presented on vb-audio facebook/g+) Voicemeeter 2017 Version 2.0.3.2 / 1.0.5.2 (REBOOT after de-installation, REBOOT after installation)...
If the problem remains, you may contact vb-audio with a screenshot of your Voicemeeter and its system settings dialog box.
answered Jan 24 '17 at 5:33
user258609
32116
keep default settings (default buffer size) and select your best audio device as output A1 (giving the main stream) : First try ASIO device or WDM/KS... use MME device at the end if nothing works. Check you have no audio conflict (audio device not used twice by several apps).
Think about installing last version (currently presented on vb-audio facebook/g+) Voicemeeter 2017 Version 2.0.3.2 / 1.0.5.2 (REBOOT after de-installation, REBOOT after installation)...
If the problem remains, you may contact vb-audio with a screenshot of your Voicemeeter and its system settings dialog box.
answered Jan 24 '17 at 5:33
user258609
32116
edited Jan 24 '17 at 7:23
answered Jan 24 '17 at 5:33
user258609
32116
answered Jan 24 '17 at 5:33
user258609
32116
answered Jan 24 '17 at 5:33
user258609
32116
32116
I think you possibly misread the question. I'm not having specifically Voicemeeter problems, but other audio problem that didn't solve itself when trying with Voicemeeter.
– zini
Jan 24 '17 at 14:55
ok, right, your problem seems to be more located on system or driver level (maybe motherboard bus or bad video/network driver can disturb windows timing) but keeping default settings on Voicemeeter and select your best audio device as output A1 can help anyway.
– user258609
Jan 25 '17 at 15:36
add a comment |
I think you possibly misread the question. I'm not having specifically Voicemeeter problems, but other audio problem that didn't solve itself when trying with Voicemeeter.
– zini
Jan 24 '17 at 14:55
ok, right, your problem seems to be more located on system or driver level (maybe motherboard bus or bad video/network driver can disturb windows timing) but keeping default settings on Voicemeeter and select your best audio device as output A1 can help anyway.
– user258609
Jan 25 '17 at 15:36
I think you possibly misread the question. I'm not having specifically Voicemeeter problems, but other audio problem that didn't solve itself when trying with Voicemeeter.
– zini
Jan 24 '17 at 14:55
I think you possibly misread the question. I'm not having specifically Voicemeeter problems, but other audio problem that didn't solve itself when trying with Voicemeeter.
– zini
Jan 24 '17 at 14:55
ok, right, your problem seems to be more located on system or driver level (maybe motherboard bus or bad video/network driver can disturb windows timing) but keeping default settings on Voicemeeter and select your best audio device as output A1 can help anyway.
– user258609
Jan 25 '17 at 15:36
ok, right, your problem seems to be more located on system or driver level (maybe motherboard bus or bad video/network driver can disturb windows timing) but keeping default settings on Voicemeeter and select your best audio device as output A1 can help anyway.
– user258609
Jan 25 '17 at 15:36
add a comment |
You get DPC issues with come from the Microsoft USB 3.0 driver USBXHCI.SYS:
Total = 11776 for module USBXHCI.SYS
Elapsed Time, > 256 usecs AND <= 512 usecs, 12, or 0.10%
Elapsed Time, > 512 usecs AND <= 1024 usecs, 1, or 0.01%
Elapsed Time, > 1024 usecs AND <= 2048 usecs, 0, or 0.00%
Elapsed Time, > 2048 usecs AND <= 4096 usecs, 7, or 0.06%
Elapsed Time, > 4096 usecs AND <= 8192 usecs, 1, or 0.01%
Total, 11776
Everything over 1024µs is bad and you have 8 spikes where it takes longer and this causes the audio drops. Connect your USB devices that don't require fast data transfer (mouse, keyboard) to USB 2.0 ports and not USB 3.0 ones.
Also the NDIS.sys causes some drops:
Total = 3960 for module ndis.sys
Elapsed Time, > 1024 usecs AND <= 2048 usecs, 3, or 0.08%
Elapsed Time, > 2048 usecs AND <= 4096 usecs, 17, or 0.43%
Total, 3960
So update the network card drivers and all network related drivers.
If the sound/audio is fine over Displayport or HDMI on an external Monitor/TV, the cheap Realtek audio chip is causing the issue.
Buy a soundcard with a better audio chip like the ASUS Strix Soar
and connect your headphones to this sound card and disable the Realtek chip in BIOS.
answered Jan 25 '17 at 15:08
magicandre1981
81k20123202
Few spikes sounds a lot less than it feels. The audio very bad under some load. I switched every USB device to USB 2.0 ports, disabled networking entirely, but the audio is still crackling under load. I took another trace without networking: dl.dropboxusercontent.com/s/hjhajrinm4dadd3/…
– zini
Jan 25 '17 at 16:43
the new trace shows less spikes, only 2 (1 in USB3 driver and 1 in storport.sys - storage related driver) that reach 1024µs. But I still see that the logitech driver LGSHidFilt.sys is called by the usb3 driver. Was the sound still so bad when you captured the new trace?
– magicandre1981
Jan 26 '17 at 16:11
Yes, the sound was still as bad as before. My wireless headset is by Logitech, so that's the driver. The headset was plugged into USB 2.0 port, so that's weird that USB3 driver would try to use it.
– zini
Jan 26 '17 at 17:10
ok, in this case the issues are not caused by DPCs. connect a Monitor/TV via HDMI so that the audio of the GPU is used. look if the sound from the TV is also bad or not.
– magicandre1981
Jan 26 '17 at 17:36
Huh, audio through DisplayPort -> Display -> Headphone out -> Wired headphones is just fine with no crackling. Weird, I was pretty sure that I did try audio through GPU before. Maybe the display has audio buffer? Still, this is a workaround at best. I'd still like to use my wireless headphones.
– zini
Jan 26 '17 at 18:10
|
show 9 more comments
You get DPC issues with come from the Microsoft USB 3.0 driver USBXHCI.SYS:
Total = 11776 for module USBXHCI.SYS
Elapsed Time, > 256 usecs AND <= 512 usecs, 12, or 0.10%
Elapsed Time, > 512 usecs AND <= 1024 usecs, 1, or 0.01%
Elapsed Time, > 1024 usecs AND <= 2048 usecs, 0, or 0.00%
Elapsed Time, > 2048 usecs AND <= 4096 usecs, 7, or 0.06%
Elapsed Time, > 4096 usecs AND <= 8192 usecs, 1, or 0.01%
Total, 11776
Everything over 1024µs is bad and you have 8 spikes where it takes longer and this causes the audio drops. Connect your USB devices that don't require fast data transfer (mouse, keyboard) to USB 2.0 ports and not USB 3.0 ones.
Also the NDIS.sys causes some drops:
Total = 3960 for module ndis.sys
Elapsed Time, > 1024 usecs AND <= 2048 usecs, 3, or 0.08%
Elapsed Time, > 2048 usecs AND <= 4096 usecs, 17, or 0.43%
Total, 3960
So update the network card drivers and all network related drivers.
If the sound/audio is fine over Displayport or HDMI on an external Monitor/TV, the cheap Realtek audio chip is causing the issue.
Buy a soundcard with a better audio chip like the ASUS Strix Soar
and connect your headphones to this sound card and disable the Realtek chip in BIOS.
answered Jan 25 '17 at 15:08
magicandre1981
81k20123202
Few spikes sounds a lot less than it feels. The audio very bad under some load. I switched every USB device to USB 2.0 ports, disabled networking entirely, but the audio is still crackling under load. I took another trace without networking: dl.dropboxusercontent.com/s/hjhajrinm4dadd3/…
– zini
Jan 25 '17 at 16:43
the new trace shows less spikes, only 2 (1 in USB3 driver and 1 in storport.sys - storage related driver) that reach 1024µs. But I still see that the logitech driver LGSHidFilt.sys is called by the usb3 driver. Was the sound still so bad when you captured the new trace?
– magicandre1981
Jan 26 '17 at 16:11
Yes, the sound was still as bad as before. My wireless headset is by Logitech, so that's the driver. The headset was plugged into USB 2.0 port, so that's weird that USB3 driver would try to use it.
– zini
Jan 26 '17 at 17:10
ok, in this case the issues are not caused by DPCs. connect a Monitor/TV via HDMI so that the audio of the GPU is used. look if the sound from the TV is also bad or not.
– magicandre1981
Jan 26 '17 at 17:36
Huh, audio through DisplayPort -> Display -> Headphone out -> Wired headphones is just fine with no crackling. Weird, I was pretty sure that I did try audio through GPU before. Maybe the display has audio buffer? Still, this is a workaround at best. I'd still like to use my wireless headphones.
– zini
Jan 26 '17 at 18:10
|
show 9 more comments
You get DPC issues with come from the Microsoft USB 3.0 driver USBXHCI.SYS:
Total = 11776 for module USBXHCI.SYS
Elapsed Time, > 256 usecs AND <= 512 usecs, 12, or 0.10%
Elapsed Time, > 512 usecs AND <= 1024 usecs, 1, or 0.01%
Elapsed Time, > 1024 usecs AND <= 2048 usecs, 0, or 0.00%
Elapsed Time, > 2048 usecs AND <= 4096 usecs, 7, or 0.06%
Elapsed Time, > 4096 usecs AND <= 8192 usecs, 1, or 0.01%
Total, 11776
Everything over 1024µs is bad and you have 8 spikes where it takes longer and this causes the audio drops. Connect your USB devices that don't require fast data transfer (mouse, keyboard) to USB 2.0 ports and not USB 3.0 ones.
Also the NDIS.sys causes some drops:
Total = 3960 for module ndis.sys
Elapsed Time, > 1024 usecs AND <= 2048 usecs, 3, or 0.08%
Elapsed Time, > 2048 usecs AND <= 4096 usecs, 17, or 0.43%
Total, 3960
So update the network card drivers and all network related drivers.
If the sound/audio is fine over Displayport or HDMI on an external Monitor/TV, the cheap Realtek audio chip is causing the issue.
Buy a soundcard with a better audio chip like the ASUS Strix Soar
and connect your headphones to this sound card and disable the Realtek chip in BIOS.
answered Jan 25 '17 at 15:08
magicandre1981
81k20123202
You get DPC issues with come from the Microsoft USB 3.0 driver USBXHCI.SYS:
Total = 11776 for module USBXHCI.SYS
Elapsed Time, > 256 usecs AND <= 512 usecs, 12, or 0.10%
Elapsed Time, > 512 usecs AND <= 1024 usecs, 1, or 0.01%
Elapsed Time, > 1024 usecs AND <= 2048 usecs, 0, or 0.00%
Elapsed Time, > 2048 usecs AND <= 4096 usecs, 7, or 0.06%
Elapsed Time, > 4096 usecs AND <= 8192 usecs, 1, or 0.01%
Total, 11776
Everything over 1024µs is bad and you have 8 spikes where it takes longer and this causes the audio drops. Connect your USB devices that don't require fast data transfer (mouse, keyboard) to USB 2.0 ports and not USB 3.0 ones.
Also the NDIS.sys causes some drops:
Total = 3960 for module ndis.sys
Elapsed Time, > 1024 usecs AND <= 2048 usecs, 3, or 0.08%
Elapsed Time, > 2048 usecs AND <= 4096 usecs, 17, or 0.43%
Total, 3960
So update the network card drivers and all network related drivers.
If the sound/audio is fine over Displayport or HDMI on an external Monitor/TV, the cheap Realtek audio chip is causing the issue.
Buy a soundcard with a better audio chip like the ASUS Strix Soar
and connect your headphones to this sound card and disable the Realtek chip in BIOS.
answered Jan 25 '17 at 15:08
magicandre1981
81k20123202
edited Jan 26 '17 at 18:20
answered Jan 25 '17 at 15:08
magicandre1981
81k20123202
answered Jan 25 '17 at 15:08
magicandre1981
81k20123202
answered Jan 25 '17 at 15:08
magicandre1981
81k20123202
81k20123202
Few spikes sounds a lot less than it feels. The audio very bad under some load. I switched every USB device to USB 2.0 ports, disabled networking entirely, but the audio is still crackling under load. I took another trace without networking: dl.dropboxusercontent.com/s/hjhajrinm4dadd3/…
– zini
Jan 25 '17 at 16:43
the new trace shows less spikes, only 2 (1 in USB3 driver and 1 in storport.sys - storage related driver) that reach 1024µs. But I still see that the logitech driver LGSHidFilt.sys is called by the usb3 driver. Was the sound still so bad when you captured the new trace?
– magicandre1981
Jan 26 '17 at 16:11
Yes, the sound was still as bad as before. My wireless headset is by Logitech, so that's the driver. The headset was plugged into USB 2.0 port, so that's weird that USB3 driver would try to use it.
– zini
Jan 26 '17 at 17:10
ok, in this case the issues are not caused by DPCs. connect a Monitor/TV via HDMI so that the audio of the GPU is used. look if the sound from the TV is also bad or not.
– magicandre1981
Jan 26 '17 at 17:36
Huh, audio through DisplayPort -> Display -> Headphone out -> Wired headphones is just fine with no crackling. Weird, I was pretty sure that I did try audio through GPU before. Maybe the display has audio buffer? Still, this is a workaround at best. I'd still like to use my wireless headphones.
– zini
Jan 26 '17 at 18:10
|
show 9 more comments
Few spikes sounds a lot less than it feels. The audio very bad under some load. I switched every USB device to USB 2.0 ports, disabled networking entirely, but the audio is still crackling under load. I took another trace without networking: dl.dropboxusercontent.com/s/hjhajrinm4dadd3/…
– zini
Jan 25 '17 at 16:43
the new trace shows less spikes, only 2 (1 in USB3 driver and 1 in storport.sys - storage related driver) that reach 1024µs. But I still see that the logitech driver LGSHidFilt.sys is called by the usb3 driver. Was the sound still so bad when you captured the new trace?
– magicandre1981
Jan 26 '17 at 16:11
Yes, the sound was still as bad as before. My wireless headset is by Logitech, so that's the driver. The headset was plugged into USB 2.0 port, so that's weird that USB3 driver would try to use it.
– zini
Jan 26 '17 at 17:10
ok, in this case the issues are not caused by DPCs. connect a Monitor/TV via HDMI so that the audio of the GPU is used. look if the sound from the TV is also bad or not.
– magicandre1981
Jan 26 '17 at 17:36
Huh, audio through DisplayPort -> Display -> Headphone out -> Wired headphones is just fine with no crackling. Weird, I was pretty sure that I did try audio through GPU before. Maybe the display has audio buffer? Still, this is a workaround at best. I'd still like to use my wireless headphones.
– zini
Jan 26 '17 at 18:10
Few spikes sounds a lot less than it feels. The audio very bad under some load. I switched every USB device to USB 2.0 ports, disabled networking entirely, but the audio is still crackling under load. I took another trace without networking: dl.dropboxusercontent.com/s/hjhajrinm4dadd3/…
– zini
Jan 25 '17 at 16:43
Few spikes sounds a lot less than it feels. The audio very bad under some load. I switched every USB device to USB 2.0 ports, disabled networking entirely, but the audio is still crackling under load. I took another trace without networking: dl.dropboxusercontent.com/s/hjhajrinm4dadd3/…
– zini
Jan 25 '17 at 16:43
the new trace shows less spikes, only 2 (1 in USB3 driver and 1 in storport.sys - storage related driver) that reach 1024µs. But I still see that the logitech driver LGSHidFilt.sys is called by the usb3 driver. Was the sound still so bad when you captured the new trace?
– magicandre1981
Jan 26 '17 at 16:11
the new trace shows less spikes, only 2 (1 in USB3 driver and 1 in storport.sys - storage related driver) that reach 1024µs. But I still see that the logitech driver LGSHidFilt.sys is called by the usb3 driver. Was the sound still so bad when you captured the new trace?
– magicandre1981
Jan 26 '17 at 16:11
Yes, the sound was still as bad as before. My wireless headset is by Logitech, so that's the driver. The headset was plugged into USB 2.0 port, so that's weird that USB3 driver would try to use it.
– zini
Jan 26 '17 at 17:10
Yes, the sound was still as bad as before. My wireless headset is by Logitech, so that's the driver. The headset was plugged into USB 2.0 port, so that's weird that USB3 driver would try to use it.
– zini
Jan 26 '17 at 17:10
ok, in this case the issues are not caused by DPCs. connect a Monitor/TV via HDMI so that the audio of the GPU is used. look if the sound from the TV is also bad or not.
– magicandre1981
Jan 26 '17 at 17:36
ok, in this case the issues are not caused by DPCs. connect a Monitor/TV via HDMI so that the audio of the GPU is used. look if the sound from the TV is also bad or not.
– magicandre1981
Jan 26 '17 at 17:36
Huh, audio through DisplayPort -> Display -> Headphone out -> Wired headphones is just fine with no crackling. Weird, I was pretty sure that I did try audio through GPU before. Maybe the display has audio buffer? Still, this is a workaround at best. I'd still like to use my wireless headphones.
– zini
Jan 26 '17 at 18:10
Huh, audio through DisplayPort -> Display -> Headphone out -> Wired headphones is just fine with no crackling. Weird, I was pretty sure that I did try audio through GPU before. Maybe the display has audio buffer? Still, this is a workaround at best. I'd still like to use my wireless headphones.
– zini
Jan 26 '17 at 18:10
|
show 9 more comments
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1170712%2faudio-crackling-and-popping-with-different-audio-devices-windows-10%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Try swapping your default audio from 48kHz to 44.1kHz in your sound manager.
– Tetsujin
Jan 23 '17 at 19:13
Check the screws that hold the motherboard to the case. Make sure they are tight Excessive crackling like this this is often a grounding issue and your electronics/case may not be properly grounded. Also, if you are using an external audio front panel, I would recommend using the built in audio on the back of the computer instead.
– Narzard
Jan 23 '17 at 19:13
@Tetsujin I've tried with 44.1kHz with different audio devices, problem persists.
– zini
Jan 23 '17 at 19:17
@Narzard I've tried with both front and back connectors AND with USB audio device (which shouldn't be affected by possible grounding issues), problem persists.
– zini
Jan 23 '17 at 19:17
btw, crackling is not a grounding issue, it's a decoding/timing issue
– Tetsujin
Jan 23 '17 at 19:25