• Hallo Gast, du kaufst gerne günstig ein und erfährst oft vor deinen Freunden von interessanten Angeboten? Dann kannst du dein Talent als Schnäppchenjäger jetzt zu Geld machen und anderen PCGH-Lesern beim Sparen helfen! Schau einfach mal rein - beim Test der Community Deals!

Win10 Audio Knistern High DPC (LatencyMon)

Status
Für weitere Antworten geschlossen.

Gomox

Komplett-PC-Käufer(in)
Hallo Leute! Ich habe regelmäßig Audioknistern auf meinem Windows 10 Rechner. Kann mir jemand sagen, was mir bei der Behebung des Problems helfen könnte? Verursacher scheint unter anderem " Wdf01000.sys" zu sein.

Danke im Voraus! Hier der LatencyMon Log.

_________________________________________________________________________________________________________
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.
LatencyMon has been analyzing your system for 0:04:36 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: GAMING
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: ASUSTeK COMPUTER INC., P8H61-M LE/USB3
CPU: GenuineIntel Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
Logical processors: 4
Processor groups: 1
RAM: 16348 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3193,0 MHz
Measured CPU speed: 2184,0 MHz (approx.)

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): 28176,168884
Average measured interrupt to process latency (µs): 4,143993

Highest measured interrupt to DPC latency (µs): 17833,554136
Average measured interrupt to DPC latency (µs): 1,578280


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
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): 106,855622
Driver with highest ISR routine execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation

Highest reported total ISR routine time (%): 0,213902
Driver with highest ISR total time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation

Total time spent in ISRs (%) 0,218473

ISR count (execution time <250 µs): 5714468
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


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
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): 16320,284685
Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation

Highest reported total DPC routine time (%): 0,746790
Driver with highest DPC total execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation

Total time spent in DPCs (%) 1,395760

DPC count (execution time <250 µs): 6463775
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 303
DPC count (execution time 1000-1999 µs): 8
DPC count (execution time 2000-3999 µs): 1
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: chrome.exe

Total number of hard pagefaults 153
Hard pagefault count of hardest hit process: 75
Highest hard pagefault resolution time (µs): 3758,820858
Total time spent in hard pagefaults (%): 0,005489
Number of processes hit: 7


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 24,179694
CPU 0 ISR highest execution time (µs): 106,855622
CPU 0 ISR total execution time (s): 1,759776
CPU 0 ISR count: 4192580
CPU 0 DPC highest execution time (µs): 16320,284685
CPU 0 DPC total execution time (s): 9,897495
CPU 0 DPC count: 4467332
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 11,691766
CPU 1 ISR highest execution time (µs): 106,224241
CPU 1 ISR total execution time (s): 0,637254
CPU 1 ISR count: 1505312
CPU 1 DPC highest execution time (µs): 639,136549
CPU 1 DPC total execution time (s): 4,849683
CPU 1 DPC count: 1904283
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 3,644164
CPU 2 ISR highest execution time (µs): 29,325399
CPU 2 ISR total execution time (s): 0,015045
CPU 2 ISR count: 16576
CPU 2 DPC highest execution time (µs): 922,022236
CPU 2 DPC total execution time (s): 0,362656
CPU 2 DPC count: 57649
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 3,458410
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 1058,797056
CPU 3 DPC total execution time (s): 0,300197
CPU 3 DPC count: 34826
_________________________________________________________________________________________________________



ZWEITER LOG ZUM VERGLEICH






_________________________________________________________________________________________________________
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.
LatencyMon has been analyzing your system for 0:05:00 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: GAMING
OS version: Windows 8 , 6.2, build: 9200 (x64)
Hardware: ASUSTeK COMPUTER INC., P8H61-M LE/USB3
CPU: GenuineIntel Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz
Logical processors: 4
Processor groups: 1
RAM: 16348 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3193,0 MHz
Measured CPU speed: 2195,0 MHz (approx.)

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): 23396,437715
Average measured interrupt to process latency (µs): 4,292014

Highest measured interrupt to DPC latency (µs): 16910,575989
Average measured interrupt to DPC latency (µs): 1,535480


_________________________________________________________________________________________________________
REPORTED ISRs
_________________________________________________________________________________________________________
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): 114,346696
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0,010526
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%) 0,011672

ISR count (execution time <250 µs): 32920
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


_________________________________________________________________________________________________________
REPORTED DPCs
_________________________________________________________________________________________________________
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): 16474,967116
Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation

Highest reported total DPC routine time (%): 0,112630
Driver with highest DPC total execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

Total time spent in DPCs (%) 0,329470

DPC count (execution time <250 µs): 1408335
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 1191
DPC count (execution time 1000-1999 µs): 9
DPC count (execution time 2000-3999 µs): 0
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: avastsvc.exe

Total number of hard pagefaults 29
Hard pagefault count of hardest hit process: 14
Highest hard pagefault resolution time (µs): 109407,663952
Total time spent in hard pagefaults (%): 0,009222
Number of processes hit: 6


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 20,373268
CPU 0 ISR highest execution time (µs): 114,346696
CPU 0 ISR total execution time (s): 0,139947
CPU 0 ISR count: 32889
CPU 0 DPC highest execution time (µs): 16474,967116
CPU 0 DPC total execution time (s): 3,331424
CPU 0 DPC count: 1315922
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 7,197402
CPU 1 ISR highest execution time (µs): 8,900094
CPU 1 ISR total execution time (s): 0,000133
CPU 1 ISR count: 31
CPU 1 DPC highest execution time (µs): 612,107736
CPU 1 DPC total execution time (s): 0,212756
CPU 1 DPC count: 32964
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 6,537387
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 541,553398
CPU 2 DPC total execution time (s): 0,206566
CPU 2 DPC count: 30930
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 6,529075
CPU 3 ISR highest execution time (µs): 0,0
CPU 3 ISR total execution time (s): 0,0
CPU 3 ISR count: 0
CPU 3 DPC highest execution time (µs): 650,080489
CPU 3 DPC total execution time (s): 0,203307
CPU 3 DPC count: 29720
_________________________________________________________________________________________________________
 
Zuletzt bearbeitet:
TE
G

Gomox

Komplett-PC-Käufer(in)
Thread kann GESCHLOSSEN WERDEN! Habe meinen Netzwerktreiber geupdated und damit wohl das Problem gelöst.
 
Status
Für weitere Antworten geschlossen.
Oben Unten