Latenzprobleme -> LatencyMon Check

Hallo Mitteinander

seit kurzem leide ich unter Latenzproblemen.

Meine Konfiguration wäre folgende.

MB: Gigabyte 78LMT-USB3 Rev. 6.0
Prozessor: AMD FX 8350
Arbeitsspeicher: 16 GB DDR3 RAM
Betriebssystem: Windows 7 Professional
DAW: Cubase 9 Pro
Interface: Steinberg UR22
DAW-Controller: Steinberg CC121

Der Test mit LatencyMon ergab folgendes…

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. Also one or more ISR 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:01:18 (h:mm:ss) on all processors.

\


SYSTEM INFORMATION


Computer name: RUDI-PC
OS version: Windows 7 Service Pack 1, 6.1, build: 7601 (x64)
Hardware: GA-78LMT-USB3 6.0, Gigabyte Technology Co., Ltd.
CPU: AuthenticAMD AMD FX™-8350 Eight-Core Processor
Logical processors: 8
Processor groups: 1
RAM: 15613 MB total

\


CPU SPEED


Reported CPU speed: 40 MHz
Measured CPU speed: 1 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.

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): 7433,306445
Average measured interrupt to process latency (µs): 3,979638

Highest measured interrupt to DPC latency (µs): 342,776366
Average measured interrupt to DPC latency (µs): 1,927746

\


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): 2480,311750
Driver with highest ISR routine execution time: USBPORT.SYS - USB 1.1 & 2.0-Porttreiber, Microsoft Corporation

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

Total time spent in ISRs (%) 0,142313

ISR count (execution time <250 µs): 233313
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): 10
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): 7392,461250
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 378.49 , NVIDIA Corporation

Highest reported total DPC routine time (%): 0,042080
Driver with highest DPC total execution time: rspLLL64.sys - Resplendence Latency Monitoring and Auxiliary Kernel Library, Resplendence Software Projects Sp.

Total time spent in DPCs (%) 0,171076

DPC count (execution time <250 µs): 457196
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 64
DPC count (execution time 1000-1999 µs): 0
DPC count (execution time 2000-3999 µs): 52
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.


Process with highest pagefault count: svchost.exe

Total number of hard pagefaults 4
Hard pagefault count of hardest hit process: 2
Highest hard pagefault resolution time (µs): 9,0890
Total time spent in hard pagefaults (%): 0,000005
Number of processes hit: 2

\


PER CPU DATA


CPU 0 Interrupt cycle time (s): 2,102296
CPU 0 ISR highest execution time (µs): 51,0740
CPU 0 ISR total execution time (s): 0,285513
CPU 0 ISR count: 164822
CPU 0 DPC highest execution time (µs): 362,705250
CPU 0 DPC total execution time (s): 0,406192
CPU 0 DPC count: 407716


CPU 1 Interrupt cycle time (s): 1,375888
CPU 1 ISR highest execution time (µs): 2413,929250
CPU 1 ISR total execution time (s): 0,072932
CPU 1 ISR count: 8728
CPU 1 DPC highest execution time (µs): 2418,44750
CPU 1 DPC total execution time (s): 0,067605
CPU 1 DPC count: 7545


CPU 2 Interrupt cycle time (s): 1,603676
CPU 2 ISR highest execution time (µs): 2429,100250
CPU 2 ISR total execution time (s): 0,069350
CPU 2 ISR count: 7582
CPU 2 DPC highest execution time (µs): 384,4710
CPU 2 DPC total execution time (s): 0,055668
CPU 2 DPC count: 4710


CPU 3 Interrupt cycle time (s): 1,498464
CPU 3 ISR highest execution time (µs): 2356,35750
CPU 3 ISR total execution time (s): 0,097417
CPU 3 ISR count: 10927
CPU 3 DPC highest execution time (µs): 2606,7050
CPU 3 DPC total execution time (s): 0,123401
CPU 3 DPC count: 6788


CPU 4 Interrupt cycle time (s): 1,357703
CPU 4 ISR highest execution time (µs): 2480,311750
CPU 4 ISR total execution time (s): 0,075522
CPU 4 ISR count: 8875
CPU 4 DPC highest execution time (µs): 4972,0730
CPU 4 DPC total execution time (s): 0,083065
CPU 4 DPC count: 8165


CPU 5 Interrupt cycle time (s): 1,586186
CPU 5 ISR highest execution time (µs): 2439,455750
CPU 5 ISR total execution time (s): 0,079623
CPU 5 ISR count: 8313
CPU 5 DPC highest execution time (µs): 2677,69350
CPU 5 DPC total execution time (s): 0,071037
CPU 5 DPC count: 5965


CPU 6 Interrupt cycle time (s): 1,388123
CPU 6 ISR highest execution time (µs): 58,35150
CPU 6 ISR total execution time (s): 0,075124
CPU 6 ISR count: 8907
CPU 6 DPC highest execution time (µs): 2482,4460
CPU 6 DPC total execution time (s): 0,066086
CPU 6 DPC count: 5223


CPU 7 Interrupt cycle time (s): 1,311177
CPU 7 ISR highest execution time (µs): 2431,550750
CPU 7 ISR total execution time (s): 0,133634
CPU 7 ISR count: 15169
CPU 7 DPC highest execution time (µs): 7392,461250
CPU 7 DPC total execution time (s): 0,195761
CPU 7 DPC count: 11202


1.JPG
2.JPG
3.JPG
Vielleicht erfuhr ja der ein oder andere schonmal das selbe Schicksal und hat ein paar helfende Worte parat.

FG

Mysanity

Vielleicht erfuhr ja der ein oder andere schonmal das selbe Schicksal und hat ein paar helfende Worte parat.

Die Latenzen scheinen vor allem vom Treiber der Grafikkarte und der damit verbundenen Windows DirectX -Engine auszugehen. Versuche mal ob es einen aktuelleren Grafikkarten Treiber für die NVIDIA gibt. Vor dem Installieren eines neuen Grafikkartentreibers würde ich unter Software den bestehenden Treiber zuerst deinstallieren und dann den Computer neu starten. Erst dann das Setup des neuen Treibers starten.

PS: Manchmal haben leider auch neue Treiber Probleme, in solchen Fällen muss dann unter Umständen eine ältere Version genommen werden. In weiteren Fällen hilft es schon wenn man zuerst den Treiber vollständig deinstalliert -neu startet- und denselben Treiber nochmals nimmt, aber darauf achtet alle überflüssigen Optionen die angeboten werden nicht auszuwählen.

Manchmal ist ein Dienst der NVIDIA aktiv mit dem Namen NVIDA PowerMizer, was hier besprochen wurde:

https://www.native-instruments.com/forum/threads/solved-dropouts-cracks-pops-on-windows-7-and-nvidia-gfx-card.126080/

Solche “Energiespartreiber” sind Gift für ein professionelles Audiosystem. Falls sowas voranden ist sollte man das deaktivieren, was dann bei einem Laptop halt die Batterielaufzeit verringert -aber man kann nicht alles haben :unamused: