Create an account on the HP Community to personalize your profile and ask a question
08-07-2015 02:28 PM
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 ( http://www.thesycon.de/deu/latency_check.shtml ) 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.
1. IDT High Defintion Audio CODEC
2. Intel(R) High Defintion Audio HDMI
08-07-2015 03:34 PM
I had the same problem and now I can only hear if I use my ear buds, I have tried everything I know and nothing has helped. At first it was Crackling and Popping so I shut it off restarted it and now nothing from laptop speakers. Same with the drivers. I went back to a restore point before installing windows 10 hoping that would help, still no luck.
08-08-2015 12:58 PM
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.
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.
LatencyMon has been analyzing your system for 0:02:00 (h:mm:ss) on all processors.
Computer name: HP-COMPUTER
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: HP Pavilion dv6 Notebook PC, Hewlett-Packard, Quanta, 3627
CPU: GenuineIntel Intel(R) Core(TM)2 Duo CPU T6600 @ 2.20GHz
Logical processors: 2
Processor groups: 1
RAM: 3999 MB total
Reported CPU speed: 2194 MHz
Note: reported execution times may be calculated based on a fixed reported CPU speed. Disable variable speed settings like Intel Speed Step and AMD Cool N Quiet in the BIOS setup for more accurate results.
MEASURED INTERRUPT TO USER PROCESS LATENCIES
The interrupt to process latency reflects the measured interval that a usermode process needed to respond to a hardware request from the moment the interrupt service routine started execution. This includes the scheduling and execution of a DPC routine, the signaling of an event and the waking up of a usermode thread from an idle wait state in response to that event.
Highest measured interrupt to process latency (µs): 4881.797689
Average measured interrupt to process latency (µs): 9.510408
Highest measured interrupt to DPC latency (µs): 4863.132815
Average measured interrupt to DPC latency (µs): 4.939341
Interrupt service routines are routines installed by the OS and device drivers that execute in response to a hardware interrupt signal.
Highest ISR routine execution time (µs): 30.082042
Driver with highest ISR routine execution time: ACPI.sys - ACPI Driver for NT, Microsoft Corporation
Highest reported total ISR routine time (%): 0.098991
Driver with highest ISR total time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation
Total time spent in ISRs (%) 0.100910
ISR count (execution time <250 µs): 27651
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 0
ISR count (execution time 1000-1999 µs): 0
ISR count (execution time 2000-3999 µs): 0
ISR count (execution time >=4000 µs): 0
DPC routines are part of the interrupt servicing dispatch mechanism and disable the possibility for a process to utilize the CPU while it is interrupted until the DPC has finished execution.
Highest DPC routine execution time (µs): 8072.636281
Driver with highest DPC routine execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation
Highest reported total DPC routine time (%): 2.597129
Driver with highest DPC total execution time: ndis.sys - Network Driver Interface Specification (NDIS), Microsoft Corporation
Total time spent in DPCs (%) 3.116871
DPC count (execution time <250 µs): 143550
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 3512
DPC count (execution time 1000-1999 µs): 1284
DPC count (execution time 2000-3999 µs): 463
DPC count (execution time >=4000 µs): 0
REPORTED HARD PAGEFAULTS
Hard pagefaults are events that get triggered by making use of virtual memory that is not resident in RAM but backed by a memory mapped file on disk. The process of resolving the hard pagefault requires reading in the memory from disk while the process is interrupted and blocked from execution.
NOTE: some processes were hit by hard pagefaults. If these were programs producing audio, they are likely to interrupt the audio stream resulting in dropouts, clicks and pops. Check the Processes tab to see which programs were hit.
Process with highest pagefault count: ns.exe
Total number of hard pagefaults 1906
Hard pagefault count of hardest hit process: 1545
Highest hard pagefault resolution time (µs): 1651383.287603
Total time spent in hard pagefaults (%): 17.899784
Number of processes hit: 11
PER CPU DATA
CPU 0 Interrupt cycle time (s): 7.863693
CPU 0 ISR highest execution time (µs): 30.082042
CPU 0 ISR total execution time (s): 0.223411
CPU 0 ISR count: 25613
CPU 0 DPC highest execution time (µs): 8072.636281
CPU 0 DPC total execution time (s): 7.057330
CPU 0 DPC count: 119643
CPU 1 Interrupt cycle time (s): 0.678025
CPU 1 ISR highest execution time (µs): 20.907019
CPU 1 ISR total execution time (s): 0.018838
CPU 1 ISR count: 2038
CPU 1 DPC highest execution time (µs): 441.333637
CPU 1 DPC total execution time (s): 0.425156
CPU 1 DPC count: 29253
08-08-2015 06:12 PM
Im having the same issues too except its when playing games, just lost sound to my speaker last night, only headphones work. I have been wondering if it now becomes an hardware issue instead of software. What i mean is could this sould damage the speaker?
08-09-2015 06:48 AM
I'm having the same issues as well. I've got a HP Spectre X360 Convertable (i7/512GB/QHD) on Windows 10 Pro x64 i've tried uninstalling the drivers reinstalling them etc etc. Doesn't happen all the time, intermittent. I'd assume it's a driver issue??
08-09-2015 02:59 PM
I have tried uninstalling and reinstalling my audio drivers too. And with many of my drivers such as WLAN, USB Host, etc. drivers I've been trying disabling them one at a time to see if any one of them is causing this problem. I still haven't figured out the problem nor has any HP or Microsoft person responded to my issue.
08-09-2015 07:07 PM
This is not a permanent fix, but I found that the popping noise was coming from the "right" speaker only, while the "left" speaker produced audio as normal.
In my speakers properties, under the "levels" tab, I went to Balance and turned the right speaker to zero. Popping fixed, at least until the next update.
Hope this helps!