AMD Ryzen 7 7800x3d latency moon Ergebnisse

[silwo]

Meine Komponenten:

• Prozessor (CPU): AMD Ryzen 7 7800x3d
• Arbeitsspeicher (RAM): Kingston fury beast ddr5 cl36
• Mainboard: MSI pro B650-s wifi
• Netzteil: 750W MSI MAG A750GL 80+Gold ATX 3.0 - PCIE 5
• Gehäuse: ENDORFY Arx 700 ARGB
• Grafikkarte: RTX 4070 ti super
• HDD / SSD: Kingston NV2 M.2 PCle 4.0 x4 NVME
• CPU Lüfter: Be quiet dark rock 5

Hey da ich in manchen Spielen Probleme mit stuttering/ Frametime spikes habe (https://www.hardwareluxx.de/community/threads/mini-fps-trops-frametime-spikes-in-spielen.1366697/), dacht ich mir ein latency moon test könnte für Klarheit sorgen. Jedoch kann ich mit dem Ergebnis nicht viel anfangen. Jedenfalls sind hier die Ergebnisse falls sich jemand damit auskennt.

Es wurde ca. 12min Sons of the forest getestet. Ohne Overlay etc.

Danke schon mal im Vorraus

L.G.
Silwo

 

[DaObst]

Scheint wohl ein Problem mit dem GraKa-Treiber zu sein.
NV hat da seit dem Release der 5000'er ziemliche Probleme mit der Software.
Ich würde mal auf die Dezember Ausgabe (Version 566.36) zurückgehen und gucken, ob das Problem dann weiterhin besteht.

 

[silwo]

ok danke ich mache mal ein cleaninstall von der Version 566.36

Beitrag automatisch zusammengeführt: Mittwoch um 17:20

leider immer noch sehr hoch:



OS version: Windows 11, 10.0, version 2009, build: 26100 (x64)
Hardware: MS-7E26, Micro-Star International Co., Ltd.
BIOS: 1.J0
CPU: AuthenticAMD AMD Ryzen 7 7800X3D 8-Core Processor
Logical processors: 16
Processor groups: 1
Processor group size: 16
RAM: 31849 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed (WMI): 4201 MHz
Reported CPU speed (registry): 420 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): 247,70
Average measured interrupt to process latency (µs): 10,030140

Highest measured interrupt to DPC latency (µs): 239,60
Average measured interrupt to DPC latency (µs): 3,702893


_________________________________________________________________________________________________________
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): 23,950
Driver with highest ISR routine execution time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Highest reported total ISR routine time (%): 0,002263
Driver with highest ISR total time: HDAudBus.sys - High Definition Audio Bus Driver, Microsoft Corporation

Total time spent in ISRs (%) 0,003341

ISR count (execution time <250 µs): 220624
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 0
ISR count (execution time 1000-2000 µs): 0
ISR count (execution time 2000-4000 µ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): 1244,250
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 566.36 , NVIDIA Corporation

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

Total time spent in DPCs (%) 0,185922

DPC count (execution time <250 µs): 2237033
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 5
DPC count (execution time 1000-2000 µs): 2
DPC count (execution time 2000-4000 µ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: msmpeng.exe

Total number of hard pagefaults 1381
Hard pagefault count of hardest hit process: 893
Number of processes hit: 24


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 47,149296
CPU 0 ISR highest execution time (µs): 23,950
CPU 0 ISR total execution time (s): 0,338068
CPU 0 ISR count: 220624
CPU 0 DPC highest execution time (µs): 1244,250
CPU 0 DPC total execution time (s): 18,630663
CPU 0 DPC count: 2113514
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 2,543341
CPU 1 ISR highest execution time (µs): 0,0
CPU 1 ISR total execution time (s): 0,0
CPU 1 ISR count: 0
CPU 1 DPC highest execution time (µs): 39,280
CPU 1 DPC total execution time (s): 0,016842
CPU 1 DPC count: 20395
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,710758
CPU 2 ISR highest execution time (µs): 0,0
CPU 2 ISR total execution time (s): 0,0
CPU 2 ISR count: 0
CPU 2 DPC highest execution time (µs): 113,150
CPU 2 DPC total execution time (s): 0,049004
CPU 2 DPC count: 19230
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2,645122
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): 39,860
CPU 3 DPC total execution time (s): 0,010371
CPU 3 DPC count: 6048
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2,505731
CPU 4 ISR highest execution time (µs): 0,0
CPU 4 ISR total execution time (s): 0,0
CPU 4 ISR count: 0
CPU 4 DPC highest execution time (µs): 41,370
CPU 4 DPC total execution time (s): 0,015869
CPU 4 DPC count: 16136
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2,331905
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): 52,630
CPU 5 DPC total execution time (s): 0,009978
CPU 5 DPC count: 6704
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 2,546866
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): 258,760
CPU 6 DPC total execution time (s): 0,023954
CPU 6 DPC count: 21986
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 2,348762
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): 44,430
CPU 7 DPC total execution time (s): 0,018030
CPU 7 DPC count: 16178
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 2,323176
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): 41,140
CPU 8 DPC total execution time (s): 0,004073
CPU 8 DPC count: 2191
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 2,253959
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): 37,720
CPU 9 DPC total execution time (s): 0,003727
CPU 9 DPC count: 1639
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 2,422051
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): 38,540
CPU 10 DPC total execution time (s): 0,007480
CPU 10 DPC count: 4334
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 2,329433
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): 39,630
CPU 11 DPC total execution time (s): 0,007406
CPU 11 DPC count: 3534
_________________________________________________________________________________________________________
CPU 12 Interrupt cycle time (s): 2,141512
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): 43,170
CPU 12 DPC total execution time (s): 0,002494
CPU 12 DPC count: 1040
_________________________________________________________________________________________________________
CPU 13 Interrupt cycle time (s): 2,112004
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): 31,30
CPU 13 DPC total execution time (s): 0,001599
CPU 13 DPC count: 410
_________________________________________________________________________________________________________
CPU 14 Interrupt cycle time (s): 2,370564
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): 46,790
CPU 14 DPC total execution time (s): 0,005292
CPU 14 DPC count: 2213
_________________________________________________________________________________________________________
CPU 15 Interrupt cycle time (s): 2,319978
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): 250,750
CPU 15 DPC total execution time (s): 0,007136
CPU 15 DPC count: 1488

 

[silwo]

Lustigerweise schießt dieser Nvidia Treiber beim start von z.B. FireFor direkt nach oben auf 1000+