Not sure if this the right forum to put this in, but here goes. I own an Aspire 8735G Laptop with Windows 7 64 bit. I haven't owned my laptop.
THEY NO LONGER CARE about their customers, so badly that even their WINDOWS DRIVERS - TO THIS VERY DAY - STILL have this same choppy audio bug (as. Omg thanks a ton. That dpc thing was the problem on my laptop(recently upgraded win 7 to win 8) and the problem was in one of my network adapters driver. Fixed Windows 7 Sound (Popping, Cracking & Skipping). Solved: Crackling and popping sound in Windows 8.1 The Wanderer - [] worked for me?
Hello everyone. I have recently upgraded to Windows 10 from Windows 7 (the problem I am about to say never occured on Windows 7). When listening to music, I now hear popping/crackling sounds. I use my headphones to listen to music but I checked using my speakers and the same problem occurs. My PC info is: System Manufacturer: Hewlett-Packard System Model: HP Pavilion dv6 Notebook PC System Type: x64-based PC Processor: Intel(R) Core(TM)2 Duo CPU T6600 @ 2.20GHz, 2200 Mhz, 2 Core(s), 2 Logical Processor(s) Installed Physical Memory (RAM): 4.00 GB I have checked DPC Latency ( ) and there does seem to be a problem. The latency spikes very often. The latency that I always have is between 1000-1500us but it spikes very high.
For some reason, right now it says my current latency is 1192us but my maximum is 908,300,885! This does not seem normal!
I don't know how to fix it! Has anyone else heard something like this and does anyone know a fix? On device manager under 'Sound, video and game controllers' there are two drivers. I have used Device manager to try to update the drivers but it is saying that I have the latest version for both. IDT High Defintion Audio CODEC 2.
Intel(R) High Defintion Audio HDMI Thank you. Hello everyone, this is an update on my issue. So I just tried uninstalling the IDT High Defintion Audio Driver, rebooted my computer and reinstalled the IDT High Defintion Audio Driver and I have no luck. I can still hear the popping and crackling sounds. I thought I'd share some information on this fourm. I just did a DPC Latnecy test (from LatencyMon) with nothing running but the test for 2 minutes and this is the report I got.
If anyone either from HP or other people can assist me on my issue, I would very much appreciate it. _________________________________ CONCLUSION: Your system appears to be having trouble handling real-time audio and other tasks. You are likely to experience buffer underruns appearing as drop outs, clicks or pops. One or more DPC routines that belong to a driver running in your system appear to be executing for too long. At least one detected problem appears to be network related. In case you are using a WLAN adapter, try disabling it to get better results.
One problem may be related to power management, disable CPU throttling settings in Control Panel and BIOS setup. Check for BIOS updates. Halex Softech 4000.
LatencyMon has been analyzing your system for 0:02:00 (h:mm:ss) on all processors.
I have a windows 7 PC, with built-in sound card in the motherboard and a USB headphone. After waking from sleep, the sound very often (though not every time) crackles/pops (say, when playing a flash movie on youtube, or play audio from an audio application). The crackling happens even in the audio test from when you 'test' the sound by right clicking on the 'Sound' icon in the tray, selecting 'playback devices'. However this only happens when i use the USB headset device, and not a normal speaker i plugin via the audio jack in the motherboard. Another observation is that if the crackling sound happens, then after some time of audio playback, i get a blue screen of death. If i don't play audio, the BSOD doesn't occur. If i sleep the machine (start menu->shut-down menu ->sleep), then wake it up again, the crackling disappears, and never occurs again until the next time i sleep the machine (after which it might happen - it seems random).
I tried restarting the audio services by doing 'net stop audiosrv' then 'net start audiosrv' in the command line, but that doesn't seem to fix anything. Has anyone any clue about what could be the problem?