Laptop + 2 Monitore

[Noyze]

Hallo zusammen,

verzweifel hier langsam.
Wenn ich 2 Monitore per HDMI über einen USB-C Hub am Notebook anschließe, laggt es bzw. läuft es irgendwie nicht rund. Selbst Chrome braucht lange um zu laden.

Ich komm aber nicht hinter was das Problem ist. Die Hardware ist folgende:

Aorus X6LAG
GeForce 4070 RTX Laptop
2x HP M27FW 27 Zoll(beide auf 60hz)
HP G5 USB C Dockingstation (Thunderbolt kompatibel)

Hat jemand eine Lösung ? Langsam gehts mir auf die Nerven. Grafikanwendungen sind gerade undenkbar

VG
Noyze

 

[Gurdi]

Klingt nach Problemen bei der Latenz. Laptops haben da gelegentlich mit zu kämpfen. Lade dir mal LatencyMon runter und poste deine Werte.

 

[Noyze]

Danke für die Info.
Ich hoffe das sprengt jetzt nicht den Rahmen

_________________________________________________________________________________________________________
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. 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:39 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: RAPHAEL
OS version: Windows 11, 10.0, version 2009, build: 26100 (x64)
Hardware: AORUS 16X 9SG, GIGABYTE
BIOS: F6
CPU: GenuineIntel 13th Gen Intel(R) Core(TM) i7-13650HX
Logical processors: 20
Processor groups: 1
Processor group size: 20
RAM: 16047 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 260 MHz
Reported CPU speed (registry): 2803 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): 7685,10
Average measured interrupt to process latency (µs): 54,282264

Highest measured interrupt to DPC latency (µs): 6566,70
Average measured interrupt to DPC latency (µs): 13,938262


_________________________________________________________________________________________________________
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): 2035,285765
Driver with highest ISR routine execution time: ACPI.sys - ACPI-Treiber für NT, Microsoft Corporation

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

Total time spent in ISRs (%) 0,003392

ISR count (execution time <250 µs): 29670
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 17
ISR count (execution time 1000-2000 µs): 2
ISR count (execution time 2000-4000 µs): 1
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): 7520,49340
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 555.99 , NVIDIA Corporation

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

Total time spent in DPCs (%) 0,106573

DPC count (execution time <250 µs): 287297
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 1223
DPC count (execution time 1000-2000 µs): 81
DPC count (execution time 2000-4000 µs): 38
DPC count (execution time >=4000 µs): 33


_________________________________________________________________________________________________________
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: msmpeng.exe

Total number of hard pagefaults 3446
Hard pagefault count of hardest hit process: 964
Number of processes hit: 44


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 17,618494
CPU 0 ISR highest execution time (µs): 2035,285765
CPU 0 ISR total execution time (s): 0,038596
CPU 0 ISR count: 355
CPU 0 DPC highest execution time (µs): 7520,49340
CPU 0 DPC total execution time (s): 1,624135
CPU 0 DPC count: 62031
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 9,583557
CPU 1 ISR highest execution time (µs): 143,637888
CPU 1 ISR total execution time (s): 0,017820
CPU 1 ISR count: 3138
CPU 1 DPC highest execution time (µs): 1687,859080
CPU 1 DPC total execution time (s): 0,253147
CPU 1 DPC count: 7581
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 13,896464
CPU 2 ISR highest execution time (µs): 290,344631
CPU 2 ISR total execution time (s): 0,090817
CPU 2 ISR count: 18790
CPU 2 DPC highest execution time (µs): 617,532644
CPU 2 DPC total execution time (s): 1,351290
CPU 2 DPC count: 38067
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 10,472570
CPU 3 ISR highest execution time (µs): 8,888334
CPU 3 ISR total execution time (s): 0,000079
CPU 3 ISR count: 12
CPU 3 DPC highest execution time (µs): 3398,961470
CPU 3 DPC total execution time (s): 0,098660
CPU 3 DPC count: 11800
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 18,052515
CPU 4 ISR highest execution time (µs): 288,815555
CPU 4 ISR total execution time (s): 0,006769
CPU 4 ISR count: 128
CPU 4 DPC highest execution time (µs): 5209,199786
CPU 4 DPC total execution time (s): 0,606012
CPU 4 DPC count: 31119
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 18,400763
CPU 5 ISR highest execution time (µs): 278,767035
CPU 5 ISR total execution time (s): 0,015559
CPU 5 ISR count: 3571
CPU 5 DPC highest execution time (µs): 3591,380307
CPU 5 DPC total execution time (s): 0,342759
CPU 5 DPC count: 15337
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 15,581019
CPU 6 ISR highest execution time (µs): 169,173742
CPU 6 ISR total execution time (s): 0,006369
CPU 6 ISR count: 1148
CPU 6 DPC highest execution time (µs): 4081,965751
CPU 6 DPC total execution time (s): 0,442435
CPU 6 DPC count: 27153
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 16,995245
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): 514,357474
CPU 7 DPC total execution time (s): 0,079981
CPU 7 DPC count: 7576
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 8,664046
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): 443,448805
CPU 8 DPC total execution time (s): 0,094414
CPU 8 DPC count: 13918
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 7,849843
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): 1011,110953
CPU 9 DPC total execution time (s): 0,031572
CPU 9 DPC count: 3342
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 8,871818
CPU 10 ISR highest execution time (µs): 241,824474
CPU 10 ISR total execution time (s): 0,013630
CPU 10 ISR count: 2548
CPU 10 DPC highest execution time (µs): 560,96040
CPU 10 DPC total execution time (s): 0,257016
CPU 10 DPC count: 14902
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 7,882872
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): 241,767035
CPU 11 DPC total execution time (s): 0,021223
CPU 11 DPC count: 1974
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 4,717609
CPU 12 ISR highest execution time (µs): 0,0
CPU 12 ISR total execution time (s): 0,0
CPU 12 ISR count: 0
CPU 12 DPC highest execution time (µs): 415,171959
CPU 12 DPC total execution time (s): 0,105172
CPU 12 DPC count: 9914
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 4,155403
CPU 13 ISR highest execution time (µs): 0,0
CPU 13 ISR total execution time (s): 0,0
CPU 13 ISR count: 0
CPU 13 DPC highest execution time (µs): 368,312522
CPU 13 DPC total execution time (s): 0,070445
CPU 13 DPC count: 6786
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 4,840247
CPU 14 ISR highest execution time (µs): 0,0
CPU 14 ISR total execution time (s): 0,0
CPU 14 ISR count: 0
CPU 14 DPC highest execution time (µs): 497,410988
CPU 14 DPC total execution time (s): 0,157667
CPU 14 DPC count: 7736
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 3,927910
CPU 15 ISR highest execution time (µs): 0,0
CPU 15 ISR total execution time (s): 0,0
CPU 15 ISR count: 0
CPU 15 DPC highest execution time (µs): 456,910810
CPU 15 DPC total execution time (s): 0,073506
CPU 15 DPC count: 6643
_________________________________________________________________________________________________________
CPU 16 Interrupt cycle time (s): 4,456246
CPU 16 ISR highest execution time (µs): 0,0
CPU 16 ISR total execution time (s): 0,0
CPU 16 ISR count: 0
CPU 16 DPC highest execution time (µs): 541,125223
CPU 16 DPC total execution time (s): 0,089971
CPU 16 DPC count: 6804
_________________________________________________________________________________________________________
CPU 17 Interrupt cycle time (s): 4,386707
CPU 17 ISR highest execution time (µs): 0,0
CPU 17 ISR total execution time (s): 0,0
CPU 17 ISR count: 0
CPU 17 DPC highest execution time (µs): 379,587941
CPU 17 DPC total execution time (s): 0,082272
CPU 17 DPC count: 5953
_________________________________________________________________________________________________________
CPU 18 Interrupt cycle time (s): 4,434746
CPU 18 ISR highest execution time (µs): 0,0
CPU 18 ISR total execution time (s): 0,0
CPU 18 ISR count: 0
CPU 18 DPC highest execution time (µs): 452,508741
CPU 18 DPC total execution time (s): 0,083691
CPU 18 DPC count: 4923
_________________________________________________________________________________________________________
CPU 19 Interrupt cycle time (s): 4,177744
CPU 19 ISR highest execution time (µs): 0,0
CPU 19 ISR total execution time (s): 0,0
CPU 19 ISR count: 0
CPU 19 DPC highest execution time (µs): 551,784160
CPU 19 DPC total execution time (s): 0,093699
CPU 19 DPC count: 5113
_________________________________________________________________________________________________________

 

[Gurdi]

Das sieht übel aus.
Die NV Mobile Chips sind wirklich ne Katastrophe was das angeht. Nun, du brauchst das MSI tool.

Hier ne Anleitung,wenn du nicht weiter weist, poste deine Werte aus dem Tool mal hier dann schau ich drüber.

Leserartikel - Anleitung um mit LatencyMon & MSI_util_v3 die Systemlatenz verbessern

Mit diesem Thema betrete ich kein Neuland, fasse aber mal in Kürze zusammen was vielleicht problematisch ist, wie man mit den beiden Tools das analysiert und dann eine potenzielle Lösung anwendet. Zu LatencyMon gibt es nämlich nahezu wissenschaftliche Abhandlungen, die es in der Fülle für die...

www.computerbase.de

Bitte nichts ändern wovon du keine Ahnung hast!!! Wo kein MSI hintersteht, bitte auch kein MSi aktivieren.

 

[Noyze]

Schau ich mir an. Feedback kommt ! Danke schonmal !

 

[Noyze]

Sooo,

bei manchen war das MSI schon aktiviert.

Leider hat sich nichts verändert. Neustart wurde gemacht.

 

[Gurdi]

Der NV Treiber ist dein Problem. Der ist wie gesagt ne Seuche bei Laptops.
Mach mal folgendes, Intel Grafiktreiber sauber neu installieren den neusten, aber von der Website von Intel, nicht vom Laptophersteller.

Danach den NV Treiber neu drüber bügeln.

 

[Noyze]

Der ganze neue Schrott geht mir tierisch auf die Nerven. Ich kann hier auswählen ob ich einen Studio oder Gaming Ready Treiber will? Dann gibt es hier noch son Gigabyte Kontrollcenter wo man auch noch etliche Dinge einstellen kann.

Soll ich denn dann den Studio oder Gaming Ready Treiber installieren?

 

[Gurdi]

Das spielt im Grunde keine Rolle. Wenn du mehr produktiv arbeitest nimm den Studio, ansonsten GameReady. Beide tun aber im Grunde das selbe. Controllcenter brauchst du nicht.

 

[Markzzman]

Wir schleifen die Monitore auf der Arbeit einfach durch per USB-C.
Läuft prima.

Früher hat man das per Docking Station geregelt.
Braucht es aber nicht mehr.
Und läuft ja auch in deinem Fall nicht wirklich gut.

Dann hast du nur ein USB-C Kabel im Notebook und das wird darüber auch noch geladen.
Wenn du LAN über die Monitore nutzt liefert das Kabel auch Daten darüber.
Oder auch Tastatur, Maus Signale etc.

Ergo sind nun deine Monitore deine "Docking Station".

Brauchst halt das richtige USB-C Kabel.

Dann läuft das auch bei dir.

 

[Gurdi]

Das könnte das Problem lösen, da die TB bzw USB C Ports in der Regel an der integrierten Grafik angebunden sind. Das umgeht den lästigen NV Chip.

 

[Noyze]

Auf der Arbeit mit meinem Surface ist das auch kein Problem. Naja. Das USB-C Kabel kann ich schlecht entfernen, weil das an der HP Dockingstation sitzt.

Ich habe alle Treiber mal deinstalliert, nur den Intel Treiber draufgepackt und jetzt läuft es besser. Nicht perfekt aber besser. Allerdings macht der ACPI-Treiber noch Probleme und sorgt für hohe Latenzen. Gibt es hier noch einen Workaround?

 

[Gurdi]

Auf der Arbeit mit meinem Surface ist das auch kein Problem. Naja. Das USB-C Kabel kann ich schlecht entfernen, weil das an der HP Dockingstation sitzt.

Ich habe alle Treiber mal deinstalliert, nur den Intel Treiber draufgepackt und jetzt läuft es besser. Nicht perfekt aber besser. Allerdings macht der ACPI-Treiber noch Probleme und sorgt für hohe Latenzen. Gibt es hier noch einen Workaround?

Kaum. Dieses ganze Sound super duper AI schlag mich tot fancy Stuff verstopft noch gerne die Ports und sorgt für höhere Latenzen. Den kann man noch killen, Beispiel wäre hier diese Intel Smart Sound Müll. Der rest ist dann technisch bedingt. Die Boards auf den kompakten Laptops kommen so langsam an Ihre Grenzen, Stromsparmechanismen tun dann Ihr übriges.