Latencymon - Mein Laptop hat Probleme

[jackbauerx]

Ich habe gestern das gestern das erste mal Cubase 9 Elements auf meinem aktuellen Win 10 Laptop installiert.
Auf dem alten hatte ich noch Cubase 5.
Ich weiß, das Laptop ist nicht das Ideale Teil. Aber mit älterem hatte ich keine Probleme.
Ich hatte schon bei einer Spur Audioaussetzer.
Mit Latencymon habe ich dieses ausgelesen.
Ich verstehe leider nicht viel. Kann mir jemand bei der Analyse behilflich sein? DANKE!


_________________________________________________________________________________________________________

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 11:50:00 (h:mm:ss) on all processors.





_________________________________________________________________________________________________________

SYSTEM INFORMATION

_________________________________________________________________________________________________________

Computer name: LAPTOP-A02G4L8Q

OS version: Windows 10 , 10.0, build: 14393 (x64)

Hardware: Aspire F5-771G, Acer, SpiderMan_SK

CPU: GenuineIntel Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz

Logical processors: 4

Processor groups: 1

RAM: 8060 MB total





_________________________________________________________________________________________________________

CPU SPEED

_________________________________________________________________________________________________________

Reported CPU speed: 2712 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): 7706,417584

Average measured interrupt to process latency (µs): 7,520277



Highest measured interrupt to DPC latency (µs): 6699,788026

Average measured interrupt to DPC latency (µs): 2,538570





_________________________________________________________________________________________________________

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): 761,6250

Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation



Highest reported total ISR routine time (%): 0,534039

Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation



Total time spent in ISRs (%) 0,595761



ISR count (execution time <250 µs): 1336587906

ISR count (execution time 250-500 µs): 0

ISR count (execution time 500-999 µs): 57

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): 20275,745575

Driver with highest DPC routine execution time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation



Highest reported total DPC routine time (%): 0,533837

Driver with highest DPC total execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation



Total time spent in DPCs (%) 0,158055



DPC count (execution time <250 µs): 66255915

DPC count (execution time 250-500 µs): 0

DPC count (execution time 500-999 µs): 17758

DPC count (execution time 1000-1999 µs): 709

DPC count (execution time 2000-3999 µs): 2031

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 91135

Hard pagefault count of hardest hit process: 31805

Highest hard pagefault resolution time (µs): 3652659,513274

Total time spent in hard pagefaults (%): 0,249860

Number of processes hit: 63





_________________________________________________________________________________________________________

PER CPU DATA

_________________________________________________________________________________________________________

CPU 0 Interrupt cycle time (s): 1686,890948

CPU 0 ISR highest execution time (µs): 761,6250

CPU 0 ISR total execution time (s): 1015,178159

CPU 0 ISR count: 1336570025

CPU 0 DPC highest execution time (µs): 20275,745575

CPU 0 DPC total execution time (s): 139,826938

CPU 0 DPC count: 57422075

_________________________________________________________________________________________________________

CPU 1 Interrupt cycle time (s): 406,779116

CPU 1 ISR highest execution time (µs): 76,875737

CPU 1 ISR total execution time (s): 0,010698

CPU 1 ISR count: 8054

CPU 1 DPC highest execution time (µs): 14160,032080

CPU 1 DPC total execution time (s): 85,316939

CPU 1 DPC count: 4711811

_________________________________________________________________________________________________________

CPU 2 Interrupt cycle time (s): 214,935440

CPU 2 ISR highest execution time (µs): 46,448009

CPU 2 ISR total execution time (s): 0,007426

CPU 2 ISR count: 9820

CPU 2 DPC highest execution time (µs): 5075,419248

CPU 2 DPC total execution time (s): 37,575456

CPU 2 DPC count: 3452987

_________________________________________________________________________________________________________

CPU 3 Interrupt cycle time (s): 194,488242

CPU 3 ISR highest execution time (µs): 15,694322

CPU 3 ISR total execution time (s): 0,000076

CPU 3 ISR count: 64

CPU 3 DPC highest execution time (µs): 3945,824484

CPU 3 DPC total execution time (s): 6,610739

CPU 3 DPC count: 689554

_________________________________________________________________________________________________________

 

[FredTadge]

Deaktivier mal im Geräte-Manager deine Onboard-Soundkarte (HDAudBus.sys) und deine Netzwerkkarte (ndis.sys)

 

[jackbauerx]

Ja, das hat schon etwas gebracht. Bisschen umständlich zwar, wenn man alles immer deaktivieren muss dafür aber es bringt etwas.
Nachher mal probieren ob die Aussetzer auch wegbleiben. Danke

 

[FredTadge]

Ja, das hat schon etwas gebracht. Bisschen umständlich zwar, wenn man alles immer deaktivieren muss dafür aber es bringt etwas.
Nachher mal probieren ob die Aussetzer auch wegbleiben. Danke

Ich habe mir dafür ne Batch-Datei geschrieben: https://www.spin.de/forum/msg-archive/116/2008/12/42401

 

[Fuks]

vltt kannst du damit etwas anfangen

btw. ich hab immo auch win 10, also begeistert bin ich jetzt nicht, iwie laggt es bei mir ohne wirklich hohe dpc latenzen
woran es liegt kann ich nicht genau sagen :/

 

[bluebell]

Das WLAN und seine Treiber sind hin und wieder ein Quell von Latenzen. Am besten abschalten.

 

[jackbauerx]

Komisch. Hatte ja schon laut latencymon deutliche Verbeserung.
Das Video hatte ich auch abgearbeitet.
Dann Cubase gestartet. Eine Aufnahme gemacht und sofort kam dann die Meldung Audioaussetzer.
Latencymon blieb aber unauffällig, unten der Bericht.

Dann habe ich den AsioGuard deaktiviert und dann lief es ohne Probleme. Kann das sein?

Nochmal kurz zu Aufnahmen:
Ich nehme auf mit 44,1.
Buffer Size 256
Ein und Ausgangslatenz 12ms

Meint ihr für Schlagzeug-Aufnahmen auf Klick und Guidespuren ist das niedrig genug?
Stelle ich den Buffer auf 128 komme ich bei der Latenz auf 6ms.


Danke


_________________________________________________________________________________________________________
CONCLUSION
_________________________________________________________________________________________________________
Your system appears to be suitable for handling real-time audio and other tasks without dropouts.
LatencyMon has been analyzing your system for 0:04:05 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: LAPTOP-A02G4L8Q
OS version: Windows 10 , 10.0, build: 14393 (x64)
Hardware: Aspire F5-771G, Acer, SpiderMan_SK
CPU: GenuineIntel Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
Logical processors: 4
Processor groups: 1
RAM: 8060 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 2712 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): 614,700556
Average measured interrupt to process latency (µs): 4,241894

Highest measured interrupt to DPC latency (µs): 544,848220
Average measured interrupt to DPC latency (µs): 1,398068


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

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

Total time spent in ISRs (%) 0,013751

ISR count (execution time <250 µs): 40104
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): 692,377212
Driver with highest DPC routine execution time: Wdf01000.sys - Kernelmodustreiber-Frameworklaufzeit, Microsoft Corporation

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

Total time spent in DPCs (%) 0,528199

DPC count (execution time <250 µs): 834430
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 216
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: cubase le ai elements 9.exe

Total number of hard pagefaults 5517
Hard pagefault count of hardest hit process: 1756
Highest hard pagefault resolution time (µs): 844195,880162
Total time spent in hard pagefaults (%): 0,385276
Number of processes hit: 14


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 6,585153
CPU 0 ISR highest execution time (µs): 63,864676
CPU 0 ISR total execution time (s): 0,113559
CPU 0 ISR count: 26347
CPU 0 DPC highest execution time (µs): 692,377212
CPU 0 DPC total execution time (s): 3,820001
CPU 0 DPC count: 681256
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 3,959873
CPU 1 ISR highest execution time (µs): 60,425516
CPU 1 ISR total execution time (s): 0,021156
CPU 1 ISR count: 13752
CPU 1 DPC highest execution time (µs): 686,552360
CPU 1 DPC total execution time (s): 0,364258
CPU 1 DPC count: 45763
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,332432
CPU 2 ISR highest execution time (µs): 15,11910
CPU 2 ISR total execution time (s): 0,000052
CPU 2 ISR count: 5
CPU 2 DPC highest execution time (µs): 345,944690
CPU 2 DPC total execution time (s): 0,674666
CPU 2 DPC count: 72292
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2,760288
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): 280,620575
CPU 3 DPC total execution time (s): 0,317738
CPU 3 DPC count: 35335
_________________________________________________________________________________________________________

 

[Fuks]

Versuchs mal ohne Latencymon, bei mir knistert es, sobald ich mit L-mon messe.
Also iwie macht das Ding vllt. selbst stress.
Ich habe Vesion 6.51.