Neues Ryzen System läuft unrund (Leistung gering, hohe DPC Latenz)

Ok, also ca. das zehnfache des normalen. Und mir der anderen SSD(?) läuft es geschmeidig, dann müsste sich die Ursache doch schnell finden lassen.
 
Und hier der Log vom "alten Intel OS"

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


_
SYSTEM INFORMATION
_
Computer name: DESKTOP-NE2856L
OS version: Windows 10 , 10.0, build: 17763 (x64)
Hardware: ASRock, B450 Gaming K4
CPU: AuthenticAMD AMD Ryzen 5 2600 Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 16315 MB total


_
CPU SPEED
_
Reported CPU speed: 3394 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): 186,80
Average measured interrupt to process latency (µs): 6,135560

Highest measured interrupt to DPC latency (µs): 181,40
Average measured interrupt to DPC latency (µs): 1,959006


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

Highest reported total ISR routine time (%): 0,000453
Driver with highest ISR total time: ndis.sys - NDIS (Network Driver Interface Specification), Microsoft Corporation

Total time spent in ISRs (%) 0,000939

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

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

Total time spent in DPCs (%) 0,025480

DPC count (execution time <250 µs): 130926
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-999 µs): 4
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: chrome.exe

Total number of hard pagefaults 6995
Hard pagefault count of hardest hit process: 1704
Number of processes hit: 61


_
PER CPU DATA
_
CPU 0 Interrupt cycle time (s): 2,850465
CPU 0 ISR highest execution time (µs): 51,220389
CPU 0 ISR total execution time (s): 0,024484
CPU 0 ISR count: 12639
CPU 0 DPC highest execution time (µs): 454,742487
CPU 0 DPC total execution time (s): 0,593349
CPU 0 DPC count: 104899
_
CPU 1 Interrupt cycle time (s): 0,755338
CPU 1 ISR highest execution time (µs): 15,156747
CPU 1 ISR total execution time (s): 0,002966
CPU 1 ISR count: 778
CPU 1 DPC highest execution time (µs): 241,516205
CPU 1 DPC total execution time (s): 0,022260
CPU 1 DPC count: 1901
_
CPU 2 Interrupt cycle time (s): 0,703791
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): 121,203889
CPU 2 DPC total execution time (s): 0,018828
CPU 2 DPC count: 1844
_
CPU 3 Interrupt cycle time (s): 0,605612
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): 34,370654
CPU 3 DPC total execution time (s): 0,001992
CPU 3 DPC count: 285
_
CPU 4 Interrupt cycle time (s): 0,906370
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): 304,477313
CPU 4 DPC total execution time (s): 0,044334
CPU 4 DPC count: 5353
_
CPU 5 Interrupt cycle time (s): 0,738157
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): 69,081909
CPU 5 DPC total execution time (s): 0,004449
CPU 5 DPC count: 486
_
CPU 6 Interrupt cycle time (s): 0,906829
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): 264,206246
CPU 6 DPC total execution time (s): 0,051968
CPU 6 DPC count: 5418
_
CPU 7 Interrupt cycle time (s): 0,821633
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): 55,527991
CPU 7 DPC total execution time (s): 0,00520
CPU 7 DPC count: 591
_
CPU 8 Interrupt cycle time (s): 1,080981
CPU 8 ISR highest execution time (µs): 8,374779
CPU 8 ISR total execution time (s): 0,002459
CPU 8 ISR count: 2894
CPU 8 DPC highest execution time (µs): 198,520330
CPU 8 DPC total execution time (s): 0,036606
CPU 8 DPC count: 4278
_
CPU 9 Interrupt cycle time (s): 0,842196
CPU 9 ISR highest execution time (µs): 1,853270
CPU 9 ISR total execution time (s): 0,000043
CPU 9 ISR count: 49
CPU 9 DPC highest execution time (µs): 204,060106
CPU 9 DPC total execution time (s): 0,002552
CPU 9 DPC count: 317
_
CPU 10 Interrupt cycle time (s): 1,047874
CPU 10 ISR highest execution time (µs): 4,948733
CPU 10 ISR total execution time (s): 0,000443
CPU 10 ISR count: 452
CPU 10 DPC highest execution time (µs): 182,331762
CPU 10 DPC total execution time (s): 0,030311
CPU 10 DPC count: 3671
_
CPU 11 Interrupt cycle time (s): 0,996059
CPU 11 ISR highest execution time (µs): 2,163819
CPU 11 ISR total execution time (s): 0,000104
CPU 11 ISR count: 84
CPU 11 DPC highest execution time (µs): 245,753683
CPU 11 DPC total execution time (s): 0,015583
CPU 11 DPC count: 1887
_


Neues OS

Highest measured interrupt to process latency (µs): 1751,689111
Average measured interrupt to process latency (µs): 57,662468

Highest measured interrupt to DPC latency (µs): 1316,228739
Average measured interrupt to DPC latency (µs): 29,778561


Altes OS

Highest measured interrupt to process latency (µs): 186,80
Average measured interrupt to process latency (µs): 6,135560

Highest measured interrupt to DPC latency (µs): 181,40
Average measured interrupt to DPC latency (µs): 1,959006
 
Nun dazu überwunden Windows neu zu installieren. Scheint bisher das Problem gelöst zu haben. Werde jedoch die Latenzen im Auge behalten immer nach dem ich etwas neu installiert habe um ggf. herauszufinden, wer der Schuldige ist, falls es erneut auftaucht.

Nun übrigens:

Highest measured interrupt to process latency (µs): 126,0
Average measured interrupt to process latency (µs): 4,376135

Highest measured interrupt to DPC latency (µs): 123,0
Average measured interrupt to DPC latency (µs): 1,797156
 
das klingt sehr gut, schaue aber bitte auch ob sich durch irgendwelche updates von Win etwas ändert, ansosnten viel spass endlich mit deinem Rechner
 
  • Gefällt mir
Reaktionen: Leitzz
Zurück
Oben