Hohe Latenz wird durch LatencyMon angezeigt

Dabei seit
Dez. 2016
Beiträge
168
Hallo Leute LatencyMon zeigt mir hohe Latenzen an obwohl ich den OnboardAudioChip im BIOS deaktiviert habe!

AutoUpdate ist aus.

Im Gerätemanager wird kein RealtekAudioTreiber angezeigt.
Ich dachte es wäre der RealTimeAudioTreiber demnach ist es meines erachtens aber nicht so hab diesen mit DDU deinstalliert.

CPU Throttling ist in Win 10 deaktiviert.
System ist in der Signatur.

CPU Temperaturen sind i.O.
Allgemeine Temps sind auch in Ordnung.

________________________________________________________________________________________
LatencyMon01.01.2019.PNG
_________________
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. 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:23:51 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-D6DATR5
OS version: Windows 10 , 10.0, build: 17763 (x64)
Hardware: ASUSTeK COMPUTER INC., ROG STRIX X470-F GAMING
CPU: AuthenticAMD AMD Ryzen 7 2700X Eight-Core Processor
Logical processors: 16
Processor groups: 1
RAM: 16314 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 380 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.

WARNING: the CPU speed that was measured is only a fraction of the CPU speed reported. Your CPUs may be throttled back due to variable speed settings and thermal issues. It is suggested that you run a utility which reports your actual CPU frequency and temperature.



_________________________________________________________________________________________________________
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): 38436,169960
Average measured interrupt to process latency (µs): 12,151570

Highest measured interrupt to DPC latency (µs): 38420,525514
Average measured interrupt to DPC latency (µs): 6,476538


_________________________________________________________________________________________________________
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): 387,410
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in ISRs (%) 0,228690

ISR count (execution time <250 µs): 1670072
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-999 µs): 2
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): 1291,140
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 417.22 , NVIDIA Corporation

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

Total time spent in DPCs (%) 0,275991

DPC count (execution time <250 µs): 6150198
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 143
DPC count (execution time 1000-1999 µs): 6
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: steamservice.exe

Total number of hard pagefaults 28054
Hard pagefault count of hardest hit process: 27447
Number of processes hit: 24


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 163,021331
CPU 0 ISR highest execution time (µs): 387,410
CPU 0 ISR total execution time (s): 52,138210
CPU 0 ISR count: 1498400
CPU 0 DPC highest execution time (µs): 1291,140
CPU 0 DPC total execution time (s): 57,758408
CPU 0 DPC count: 5862052
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 38,166846
CPU 1 ISR highest execution time (µs): 148,830
CPU 1 ISR total execution time (s): 0,156508
CPU 1 ISR count: 96700
CPU 1 DPC highest execution time (µs): 229,540
CPU 1 DPC total execution time (s): 4,147063
CPU 1 DPC count: 190290
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 16,266619
CPU 2 ISR highest execution time (µs): 17,230
CPU 2 ISR total execution time (s): 0,012781
CPU 2 ISR count: 7661
CPU 2 DPC highest execution time (µs): 379,570
CPU 2 DPC total execution time (s): 0,367946
CPU 2 DPC count: 22304
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 16,948942
CPU 3 ISR highest execution time (µs): 13,320
CPU 3 ISR total execution time (s): 0,003358
CPU 3 ISR count: 2127
CPU 3 DPC highest execution time (µs): 178,630
CPU 3 DPC total execution time (s): 0,064073
CPU 3 DPC count: 3765
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 14,127878
CPU 4 ISR highest execution time (µs): 4,630
CPU 4 ISR total execution time (s): 0,000070
CPU 4 ISR count: 41
CPU 4 DPC highest execution time (µs): 77,270
CPU 4 DPC total execution time (s): 0,031306
CPU 4 DPC count: 3840
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 13,499823
CPU 5 ISR highest execution time (µs): 0,0
CPU 5 ISR total execution time (s): 0,0
CPU 5 ISR count: 0
CPU 5 DPC highest execution time (µs): 74,920
CPU 5 DPC total execution time (s): 0,003195
CPU 5 DPC count: 453
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 11,919749
CPU 6 ISR highest execution time (µs): 0,0
CPU 6 ISR total execution time (s): 0,0
CPU 6 ISR count: 0
CPU 6 DPC highest execution time (µs): 123,740
CPU 6 DPC total execution time (s): 0,033534
CPU 6 DPC count: 3599
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 11,885107
CPU 7 ISR highest execution time (µs): 0,0
CPU 7 ISR total execution time (s): 0,0
CPU 7 ISR count: 0
CPU 7 DPC highest execution time (µs): 122,540
CPU 7 DPC total execution time (s): 0,097126
CPU 7 DPC count: 8775
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 15,488495
CPU 8 ISR highest execution time (µs): 0,0
CPU 8 ISR total execution time (s): 0,0
CPU 8 ISR count: 0
CPU 8 DPC highest execution time (µs): 83,590
CPU 8 DPC total execution time (s): 0,096241
CPU 8 DPC count: 8141
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 13,433162
CPU 9 ISR highest execution time (µs): 0,0
CPU 9 ISR total execution time (s): 0,0
CPU 9 ISR count: 0
CPU 9 DPC highest execution time (µs): 51,630
CPU 9 DPC total execution time (s): 0,004929
CPU 9 DPC count: 621
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 22,306051
CPU 10 ISR highest execution time (µs): 0,0
CPU 10 ISR total execution time (s): 0,0
CPU 10 ISR count: 0
CPU 10 DPC highest execution time (µs): 83,050
CPU 10 DPC total execution time (s): 0,172039
CPU 10 DPC count: 9480
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 12,581456
CPU 11 ISR highest execution time (µs): 0,0
CPU 11 ISR total execution time (s): 0,0
CPU 11 ISR count: 0
CPU 11 DPC highest execution time (µs): 74,420
CPU 11 DPC total execution time (s): 0,006154
CPU 11 DPC count: 645
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 15,964128
CPU 12 ISR highest execution time (µs): 19,370
CPU 12 ISR total execution time (s): 0,039143
CPU 12 ISR count: 49722
CPU 12 DPC highest execution time (µs): 75,030
CPU 12 DPC total execution time (s): 0,249944
CPU 12 DPC count: 23240
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 13,154578
CPU 13 ISR highest execution time (µs): 10,760
CPU 13 ISR total execution time (s): 0,001325
CPU 13 ISR count: 1338
CPU 13 DPC highest execution time (µs): 145,590
CPU 13 DPC total execution time (s): 0,008733
CPU 13 DPC count: 969
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 14,575019
CPU 14 ISR highest execution time (µs): 18,890
CPU 14 ISR total execution time (s): 0,004749
CPU 14 ISR count: 4686
CPU 14 DPC highest execution time (µs): 104,560
CPU 14 DPC total execution time (s): 0,107891
CPU 14 DPC count: 9122
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 14,110527
CPU 15 ISR highest execution time (µs): 20,120
CPU 15 ISR total execution time (s): 0,009255
CPU 15 ISR count: 9399
CPU 15 DPC highest execution time (µs): 88,480
CPU 15 DPC total execution time (s): 0,047803
CPU 15 DPC count: 3051
_________________________________________________________________________________________________________

LatencyMon 01.01.2019 (2).PNG

LatencyMon 01.01.2019 (3).PNG

LatencyMon 01.01.2019 (4).PNG
 
Zuletzt bearbeitet:

DrAgOnBaLlOnE

Lt. Junior Grade
Dabei seit
Nov. 2005
Beiträge
501
Es ist doch klar ersichtlich an Deinem Screenshot, das es am DirectX-Kernel von Microsoft liegt, das Du hohe Latenzen hast. Wie kommt man also dann bitte darauf die Soundkarte im Verdacht zu haben?
 
Zuletzt bearbeitet:

Ambisonte Nibor

Ensign
Ersteller dieses Themas
Dabei seit
Dez. 2016
Beiträge
168
Es ist doch klar ersichtlich an Deinem Screenshot, das es am DirectX-Kernel von Microsoft liegt, das Du hohe Latenzen hast. Wie kommt man also dann bitte darauf die Soundkarte im Verdacht zu haben?
daher > "Your system appears to be having trouble handling real-time audio and other tasks."

gut hab mal "sfc /scannow" als admin durchgeführt (Aufgrund dieses Artikels )
dabei kam das raus

Der Windows-Ressourcenschutz hat beschädigte Dateien gefunden, die teilweise nicht repariert werden konnten.
Bei Onlinereparaturen finden Sie Details in der CBS-Protokolldatei unter
windir\Logs\CBS\CBS.log. Beispiel C:\Windows\Logs\CBS\CBS.log. Bei Offlinereparaturen
finden Sie Details in der durch das /OFFLOGFILE-Kennzeichen angegebenen Protokolldatei.

gut wo genau muss ich in dem Logfile Ausschau halten um die Fehlerhaften Dateien zu erkennen?

Wenn ich in der Logfile Datei "/OFFLOGFILE" suche finde ich nichts
 
Zuletzt bearbeitet:

Ambisonte Nibor

Ensign
Ersteller dieses Themas
Dabei seit
Dez. 2016
Beiträge
168

DrAgOnBaLlOnE

Lt. Junior Grade
Dabei seit
Nov. 2005
Beiträge
501
Du kannst nur schauen...das Du alles an Programmen ausmachst...welche Du für die Audio-Bearbeitung nicht zwingend benötigst. Alles was ausgeführt wird ohne Grund erzeugt Verzögerungen.

Ansonsten würde ich einfach probieren und schauen ob Du überhaupt Probleme beim Echtzeit Audio-Bearbeiten hast. Das Programm mag vielleicht Latenzen messen können, aber so ganz vertrau ich dieser kleinen kostenfreien Lösung nicht über den Weg.
 

Ambisonte Nibor

Ensign
Ersteller dieses Themas
Dabei seit
Dez. 2016
Beiträge
168
naja DPC Latency Checker zeigt mir das gleiche an....
 
Zuletzt bearbeitet:
Top