Hallo zusammen,
vor mehreren Tagen habe ich mir voller Vorfreude ein Line 6 UX2 Audio-Interface als zusätzliche "Soundkarte" gegönnt, um somit Gitarrensounds aufzunehmen. Dabei ist mir aufgefallen, dass ich diese Art "Soundkarte" nicht sinnvoll nutzen kann, da Latenzen immer die Wiedergabe des Input verzögern. Nach weiterer Analyse mit dem DPC Checker und LatencyMon habe ich bemerkt, dass mein System auch mit seiner Standard-Asus-Soundkarte-Latenzen hat und ich erst dieses Problem lösen muss.
Zunächst mein System:
Intel i7 4770S @ 3.10 GHz
Asus Z87-Pro (C2)
8 GB Corsair Vengeance LP 1600 MHz
Gigabyte 770 GTX 4 GB
2 TB Seagate 7.200 u/min SATA3-HDD
Asus Xonar D2X 1x PCI-E
Windows 7 Professional 64 bit
Sobald ich LatencyMon einschalte, erhalte ich Meldung, dass zunächst alles ok sei.
Erst, wenn ich zum Beispiel über den Media Player einige Minuten Musik laufen lasse, erhalte ich die Latenzwarnung. Der DPC-Checker zeigt, dass die ganze Zeit alles in Ordnung sei - scheinbar ist das Programm nicht ganz nützlich bei meinem Problem. Die folgenden Übeltäter nennt mir LatencyMon:
DPC-Checker:
Geräte-Manager:
Latency-Mon:
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 332.21 , NVIDIA Corporation
Driver with highest DPC total execution time: cmudaxp.sys - C-Media Audio WDM Driver, C-Media Inc
Weitere Latenzverursacher sind:
NDIS 6.20-Treiber
Intel USB 3.0 Host-Controller
TCP/IP-Driver
Was habe ich bisher getan?
- ASUS AI Suite deinstalliert (hat nichts gebracht)
- Onboard-Sound deaktiviert (keine Besserung)
- Soundkarte ASUS D2X entfernt und nur das Line 6 Interface genutzt - hat die Latenzen minimal reduziert, jedoch trotzdem vorhanden durch diverse andere Treiber
- Wenn ich das Line 6 USB-Interface an einem Port hinten genutzt habe, war die Latenz deutlich geringer als über die vorderen USB-Anschlüsse. Dennoch war die Latenz zu hoch!
- sämtliche Treiber aktualisiert (lediglich bei den Bluetooth-Geräten heißt es trotz Update immer Stand 2006)
- Nvidia-Grafikkartentreiber aktualisiert: Ich habe jedoch gelesen, dass jedes Mal, wenn die Grafikkarte ihre Taktfrequenz anpasst, Latenzen hervorgerufen werden können. Dies könnte ein Nvidia-Bug sein.
Habt ihr eine Idee, was ich noch unternehmen kann? Ich weiß langsam nicht mehr weiter und würde gerne das Latenzproblem lösen, um auch mein Audio Interface für meine Gitarre vernünftig nutzen zu können. Ansonsten bemerke ich von den Latenzen rein gar nichts, aber um zu Hause am Rechner Instrumente aufzunehmen, ist der Rechner derzeit nicht geeignet. Irgendwie vermute ich bei den Infos, dass an den Netzwerkgeräten etwas nicht stimmen könnte. Oder ist es doch einzig und allein die Energieverwaltung der GraKa, die alles bremst?
Vielen Dank für eure Tipps!
Viele Grüße,
Nico
PS:
Anbei noch der komplette Latency-Mon-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 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:25 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z87-PRO
CPU: GenuineIntel Intel(R) Core(TM) i7-4770S CPU @ 3.10GHz
Logical processors: 8
Processor groups: 1
RAM: 8129 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3100,0 MHz
Measured CPU speed: 832,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): 2337,655646
Average measured interrupt to process latency (µs): 20,278845
Highest measured interrupt to DPC latency (µs): 664,268123
Average measured interrupt to DPC latency (µs): 13,752710
_________________________________________________________________________________________________________
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): 172,927742
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,068039
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,134820
ISR count (execution time <250 µs): 525019
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): 772,615161
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 332.21 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0,991645
Driver with highest DPC total execution time: cmudaxp.sys - C-Media Audio WDM Driver, C-Media Inc
Total time spent in DPCs (%) 1,234689
DPC count (execution time <250 µs): 2104978
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 25229
DPC count (execution time 1000-1999 µs): 0
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: svchost.exe
Total number of hard pagefaults 2126
Hard pagefault count of hardest hit process: 1051
Highest hard pagefault resolution time (µs): 607204,809355
Total time spent in hard pagefaults (%): 0,788192
Number of processes hit: 16
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 33,619185
CPU 0 ISR highest execution time (µs): 98,240
CPU 0 ISR total execution time (s): 1,322208
CPU 0 ISR count: 368898
CPU 0 DPC highest execution time (µs): 654,397742
CPU 0 DPC total execution time (s): 24,502566
CPU 0 DPC count: 1976389
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 8,955993
CPU 1 ISR highest execution time (µs): 156,144194
CPU 1 ISR total execution time (s): 0,803504
CPU 1 ISR count: 83335
CPU 1 DPC highest execution time (µs): 674,807742
CPU 1 DPC total execution time (s): 0,734440
CPU 1 DPC count: 53604
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 3,188401
CPU 2 ISR highest execution time (µs): 91,338387
CPU 2 ISR total execution time (s): 0,073450
CPU 2 ISR count: 8365
CPU 2 DPC highest execution time (µs): 666,474839
CPU 2 DPC total execution time (s): 0,120521
CPU 2 DPC count: 14125
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 18,100404
CPU 3 ISR highest execution time (µs): 172,927742
CPU 3 ISR total execution time (s): 0,311732
CPU 3 ISR count: 24970
CPU 3 DPC highest execution time (µs): 772,615161
CPU 3 DPC total execution time (s): 0,336035
CPU 3 DPC count: 20511
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 10,129220
CPU 4 ISR highest execution time (µs): 127,736129
CPU 4 ISR total execution time (s): 0,004839
CPU 4 ISR count: 557
CPU 4 DPC highest execution time (µs): 199,585161
CPU 4 DPC total execution time (s): 0,047092
CPU 4 DPC count: 9126
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 9,503365
CPU 5 ISR highest execution time (µs): 128,001613
CPU 5 ISR total execution time (s): 0,162051
CPU 5 ISR count: 16290
CPU 5 DPC highest execution time (µs): 645,505484
CPU 5 DPC total execution time (s): 0,216823
CPU 5 DPC count: 16080
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 8,629759
CPU 6 ISR highest execution time (µs): 118,205161
CPU 6 ISR total execution time (s): 0,162368
CPU 6 ISR count: 19439
CPU 6 DPC highest execution time (µs): 558,672903
CPU 6 DPC total execution time (s): 0,198872
CPU 6 DPC count: 17414
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 8,283424
CPU 7 ISR highest execution time (µs): 73,820
CPU 7 ISR total execution time (s): 0,025751
CPU 7 ISR count: 3165
CPU 7 DPC highest execution time (µs): 512,625806
CPU 7 DPC total execution time (s): 0,089770
CPU 7 DPC count: 22958
________________________________________________________________________________________________________
vor mehreren Tagen habe ich mir voller Vorfreude ein Line 6 UX2 Audio-Interface als zusätzliche "Soundkarte" gegönnt, um somit Gitarrensounds aufzunehmen. Dabei ist mir aufgefallen, dass ich diese Art "Soundkarte" nicht sinnvoll nutzen kann, da Latenzen immer die Wiedergabe des Input verzögern. Nach weiterer Analyse mit dem DPC Checker und LatencyMon habe ich bemerkt, dass mein System auch mit seiner Standard-Asus-Soundkarte-Latenzen hat und ich erst dieses Problem lösen muss.
Zunächst mein System:
Intel i7 4770S @ 3.10 GHz
Asus Z87-Pro (C2)
8 GB Corsair Vengeance LP 1600 MHz
Gigabyte 770 GTX 4 GB
2 TB Seagate 7.200 u/min SATA3-HDD
Asus Xonar D2X 1x PCI-E
Windows 7 Professional 64 bit
Sobald ich LatencyMon einschalte, erhalte ich Meldung, dass zunächst alles ok sei.
Erst, wenn ich zum Beispiel über den Media Player einige Minuten Musik laufen lasse, erhalte ich die Latenzwarnung. Der DPC-Checker zeigt, dass die ganze Zeit alles in Ordnung sei - scheinbar ist das Programm nicht ganz nützlich bei meinem Problem. Die folgenden Übeltäter nennt mir LatencyMon:
DPC-Checker:
Geräte-Manager:
Latency-Mon:
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 332.21 , NVIDIA Corporation
Driver with highest DPC total execution time: cmudaxp.sys - C-Media Audio WDM Driver, C-Media Inc
Weitere Latenzverursacher sind:
NDIS 6.20-Treiber
Intel USB 3.0 Host-Controller
TCP/IP-Driver
Was habe ich bisher getan?
- ASUS AI Suite deinstalliert (hat nichts gebracht)
- Onboard-Sound deaktiviert (keine Besserung)
- Soundkarte ASUS D2X entfernt und nur das Line 6 Interface genutzt - hat die Latenzen minimal reduziert, jedoch trotzdem vorhanden durch diverse andere Treiber
- Wenn ich das Line 6 USB-Interface an einem Port hinten genutzt habe, war die Latenz deutlich geringer als über die vorderen USB-Anschlüsse. Dennoch war die Latenz zu hoch!
- sämtliche Treiber aktualisiert (lediglich bei den Bluetooth-Geräten heißt es trotz Update immer Stand 2006)
- Nvidia-Grafikkartentreiber aktualisiert: Ich habe jedoch gelesen, dass jedes Mal, wenn die Grafikkarte ihre Taktfrequenz anpasst, Latenzen hervorgerufen werden können. Dies könnte ein Nvidia-Bug sein.
Habt ihr eine Idee, was ich noch unternehmen kann? Ich weiß langsam nicht mehr weiter und würde gerne das Latenzproblem lösen, um auch mein Audio Interface für meine Gitarre vernünftig nutzen zu können. Ansonsten bemerke ich von den Latenzen rein gar nichts, aber um zu Hause am Rechner Instrumente aufzunehmen, ist der Rechner derzeit nicht geeignet. Irgendwie vermute ich bei den Infos, dass an den Netzwerkgeräten etwas nicht stimmen könnte. Oder ist es doch einzig und allein die Energieverwaltung der GraKa, die alles bremst?
Vielen Dank für eure Tipps!
Viele Grüße,
Nico
PS:
Anbei noch der komplette Latency-Mon-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 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:25 (h:mm:ss) on all processors.
_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name:
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: All Series, ASUS, ASUSTeK COMPUTER INC., Z87-PRO
CPU: GenuineIntel Intel(R) Core(TM) i7-4770S CPU @ 3.10GHz
Logical processors: 8
Processor groups: 1
RAM: 8129 MB total
_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 3100,0 MHz
Measured CPU speed: 832,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): 2337,655646
Average measured interrupt to process latency (µs): 20,278845
Highest measured interrupt to DPC latency (µs): 664,268123
Average measured interrupt to DPC latency (µs): 13,752710
_________________________________________________________________________________________________________
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): 172,927742
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Highest reported total ISR routine time (%): 0,068039
Driver with highest ISR total time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation
Total time spent in ISRs (%) 0,134820
ISR count (execution time <250 µs): 525019
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): 772,615161
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 332.21 , NVIDIA Corporation
Highest reported total DPC routine time (%): 0,991645
Driver with highest DPC total execution time: cmudaxp.sys - C-Media Audio WDM Driver, C-Media Inc
Total time spent in DPCs (%) 1,234689
DPC count (execution time <250 µs): 2104978
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 25229
DPC count (execution time 1000-1999 µs): 0
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: svchost.exe
Total number of hard pagefaults 2126
Hard pagefault count of hardest hit process: 1051
Highest hard pagefault resolution time (µs): 607204,809355
Total time spent in hard pagefaults (%): 0,788192
Number of processes hit: 16
_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 33,619185
CPU 0 ISR highest execution time (µs): 98,240
CPU 0 ISR total execution time (s): 1,322208
CPU 0 ISR count: 368898
CPU 0 DPC highest execution time (µs): 654,397742
CPU 0 DPC total execution time (s): 24,502566
CPU 0 DPC count: 1976389
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 8,955993
CPU 1 ISR highest execution time (µs): 156,144194
CPU 1 ISR total execution time (s): 0,803504
CPU 1 ISR count: 83335
CPU 1 DPC highest execution time (µs): 674,807742
CPU 1 DPC total execution time (s): 0,734440
CPU 1 DPC count: 53604
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 3,188401
CPU 2 ISR highest execution time (µs): 91,338387
CPU 2 ISR total execution time (s): 0,073450
CPU 2 ISR count: 8365
CPU 2 DPC highest execution time (µs): 666,474839
CPU 2 DPC total execution time (s): 0,120521
CPU 2 DPC count: 14125
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 18,100404
CPU 3 ISR highest execution time (µs): 172,927742
CPU 3 ISR total execution time (s): 0,311732
CPU 3 ISR count: 24970
CPU 3 DPC highest execution time (µs): 772,615161
CPU 3 DPC total execution time (s): 0,336035
CPU 3 DPC count: 20511
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 10,129220
CPU 4 ISR highest execution time (µs): 127,736129
CPU 4 ISR total execution time (s): 0,004839
CPU 4 ISR count: 557
CPU 4 DPC highest execution time (µs): 199,585161
CPU 4 DPC total execution time (s): 0,047092
CPU 4 DPC count: 9126
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 9,503365
CPU 5 ISR highest execution time (µs): 128,001613
CPU 5 ISR total execution time (s): 0,162051
CPU 5 ISR count: 16290
CPU 5 DPC highest execution time (µs): 645,505484
CPU 5 DPC total execution time (s): 0,216823
CPU 5 DPC count: 16080
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 8,629759
CPU 6 ISR highest execution time (µs): 118,205161
CPU 6 ISR total execution time (s): 0,162368
CPU 6 ISR count: 19439
CPU 6 DPC highest execution time (µs): 558,672903
CPU 6 DPC total execution time (s): 0,198872
CPU 6 DPC count: 17414
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 8,283424
CPU 7 ISR highest execution time (µs): 73,820
CPU 7 ISR total execution time (s): 0,025751
CPU 7 ISR count: 3165
CPU 7 DPC highest execution time (µs): 512,625806
CPU 7 DPC total execution time (s): 0,089770
CPU 7 DPC count: 22958
________________________________________________________________________________________________________
Zuletzt bearbeitet:
