Aktuelles

[Ungelöst] PC läuft nicht rund und hakt beim zocken

Allokaat

Enthusiast
Thread Starter
Mitglied seit
03.07.2008
Beiträge
233
Ort
NRW
Hallo zusammen,

folgende Hardware:
AMD Ryzen 2600x
MSI x470 Gaming Plus
16 GB G.Skill Flare X 3200 MHz
Asus 1060 GTX
Windows 10

Folgendes Problem:
Wenn ich zocke (Planetside 2) kommen in unregelmäßigen Abständen Soundstotterer und auch mal komplette Hänger des Systems. Mal lande ich auf dem Desktop, mal fängt sich das System und ich kann weiter zocken.
Mit dem aktuellen Bios waren die Hänger bis 5 Sekunden mit einer Version vorher 1-2 Sekunden. Die Soundstotterer treten in ebenfalls unregelmäßigen Abständen bei Youtube und Twitch auf. Alles nicht reproduzierbar
Die Grafikeinstellungen im Spiel sind auf mittel und Full HD was normal keine Probleme bereitet aber seit neuestem fallen die Min FPS auf unter 30 FPS wenn viel los ist. War mir vorher nie aufgefallen.
Beim Surfen habe ich das Gefühl die Maus würde gelegentlich nachziehen.

Was ich gemacht habe:
Treiber aktualisiert --> keine Besserung
Windows auf fehlende Updates geprüft --> aktuell
mit MSI Afterburner Temperaturen während des zockens geprüft --> nicht mehr als 60°C für CPU und GPU war auch immer im grünen Bereich
Habe heute den CPU Kühler getauscht und den CPU Sitz geprüft --> alles in Ordnung oder besser Problem nicht behoben...
Habe schon eine Neuinstallation von einer SSD auf eine M2-SSD gemacht um die SSD auszuschließen --> Problem besteht weiterhin
Habe auch schon sfc /scannow gemacht --> alles in Ordnung

Nach ein wenig Recherche wurde in diversen Foren bei ähnlichen Problemen LatencyMon empfohlen worden um Treiber Probleme festzustellen. Also habe ich es runtergeladen und laufen lassen.

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


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-B27UNKD
OS version: Windows 10, 10.0, version 2004, build: 19041 (x64)
Hardware: MS-7B79, Micro-Star International Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 2600X Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 16335 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 360 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): 101504,171620
Average measured interrupt to process latency (µs): 89,747180

Highest measured interrupt to DPC latency (µs): 101494,184317
Average measured interrupt to DPC latency (µs): 58,714245


_________________________________________________________________________________________________________
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): 950,860
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in ISRs (%) 0,173931

ISR count (execution time <250 µs): 56826
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 282
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): 101616,420
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

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

Total time spent in DPCs (%) 0,331941

DPC count (execution time <250 µs): 242075
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 2295
DPC count (execution time 1000-2000 µs): 1
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 1


_________________________________________________________________________________________________________
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 1165
Hard pagefault count of hardest hit process: 385
Number of processes hit: 12


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 22,148971
CPU 0 ISR highest execution time (µs): 950,860
CPU 0 ISR total execution time (s): 2,947168
CPU 0 ISR count: 51213
CPU 0 DPC highest execution time (µs): 101616,420
CPU 0 DPC total execution time (s): 5,311011
CPU 0 DPC count: 201605
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 3,254040
CPU 1 ISR highest execution time (µs): 192,330
CPU 1 ISR total execution time (s): 0,023818
CPU 1 ISR count: 2324
CPU 1 DPC highest execution time (µs): 375,60
CPU 1 DPC total execution time (s): 0,071045
CPU 1 DPC count: 2837
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 2,653124
CPU 2 ISR highest execution time (µs): 218,010
CPU 2 ISR total execution time (s): 0,018522
CPU 2 ISR count: 850
CPU 2 DPC highest execution time (µs): 246,10
CPU 2 DPC total execution time (s): 0,049135
CPU 2 DPC count: 3015
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 2,511422
CPU 3 ISR highest execution time (µs): 44,780
CPU 3 ISR total execution time (s): 0,000138
CPU 3 ISR count: 4
CPU 3 DPC highest execution time (µs): 240,380
CPU 3 DPC total execution time (s): 0,009756
CPU 3 DPC count: 427
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 2,567052
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): 213,540
CPU 4 DPC total execution time (s): 0,035349
CPU 4 DPC count: 1826
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 2,552702
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): 141,70
CPU 5 DPC total execution time (s): 0,007783
CPU 5 DPC count: 321
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 2,951476
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): 383,880
CPU 6 DPC total execution time (s): 0,114582
CPU 6 DPC count: 29195
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 2,776728
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): 166,240
CPU 7 DPC total execution time (s): 0,009960
CPU 7 DPC count: 467
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 2,79730
CPU 8 ISR highest execution time (µs): 37,370
CPU 8 ISR total execution time (s): 0,002752
CPU 8 ISR count: 2191
CPU 8 DPC highest execution time (µs): 340,660
CPU 8 DPC total execution time (s): 0,029427
CPU 8 DPC count: 1473
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 2,743060
CPU 9 ISR highest execution time (µs): 8,940
CPU 9 ISR total execution time (s): 0,000030
CPU 9 ISR count: 28
CPU 9 DPC highest execution time (µs): 129,220
CPU 9 DPC total execution time (s): 0,004393
CPU 9 DPC count: 207
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 2,760054
CPU 10 ISR highest execution time (µs): 21,740
CPU 10 ISR total execution time (s): 0,000244
CPU 10 ISR count: 105
CPU 10 DPC highest execution time (µs): 338,310
CPU 10 DPC total execution time (s): 0,019118
CPU 10 DPC count: 932
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 2,835209
CPU 11 ISR highest execution time (µs): 97,740
CPU 11 ISR total execution time (s): 0,001132
CPU 11 ISR count: 393
CPU 11 DPC highest execution time (µs): 235,910
CPU 11 DPC total execution time (s): 0,051990
CPU 11 DPC count: 2067
_________________________________________________________________________________________________________

Vielleicht kann mir einer hier helfen und mir den einen oder anderen Vorschlag geben, wie ich die Probleme behebe ohne einer Neuinstallation.


MfG Allokaat
 
Wenn Du diese Anzeige nicht sehen willst, registriere Dich und/oder logge Dich ein.
Wenn Du diese Anzeige nicht sehen willst, registriere Dich und/oder logge Dich ein.

CyLord

Enthusiast
Mitglied seit
27.01.2006
Beiträge
6.099
Ort
Leipzig
Der RAM läuft bei 3200? Ich würde testweise mal auf 2933 verstellen.
 

Allokaat

Enthusiast
Thread Starter
Mitglied seit
03.07.2008
Beiträge
233
Ort
NRW
Habe den RAM auch schon auf 2933 laufen lassen, einzige Besserung war, das der Sound nur noch kurz am stottern war.
Hatte auch die CPU mit 3600 MHz laufen lassen, gleiches wie beim RAM.
 

Beinfreiheit

Semiprofi
Mitglied seit
06.12.2019
Beiträge
43
Habe schon eine Neuinstallation von einer SSD auf eine M2-SSD gemacht um die SSD auszuschließen --> Problem besteht weiterhin

Hättest du eine Neuinstallation gemacht, oder deine Windows Installation übernommen?
Kannst du den LatencyMon einmal ohne Sound laufen lassen (im BIOS deaktivieren)?

Hast du eine analoge (Klinke) oder digitale (HDMI/USB/Optisch) Verbindung zu der Soundausgabe?
 

Allokaat

Enthusiast
Thread Starter
Mitglied seit
03.07.2008
Beiträge
233
Ort
NRW
Ich mache immer eine Neuinstallation um Softwareprobleme zu umgehen.
Der Sound ist über Klinke.

LatencyMon ohne Sound
_________________________________________________________________________________________________________
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. 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:10:02 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-B27UNKD
OS version: Windows 10, 10.0, version 2004, build: 19041 (x64)
Hardware: MS-7B79, Micro-Star International Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 2600X Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 16335 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 360 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): 101524,635114
Average measured interrupt to process latency (µs): 76,111453

Highest measured interrupt to DPC latency (µs): 101514,717653
Average measured interrupt to DPC latency (µs): 45,332157


_________________________________________________________________________________________________________
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): 599,750
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in ISRs (%) 0,008938

ISR count (execution time <250 µs): 18053
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 39
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): 101624,630
Driver with highest DPC routine execution time: storport.sys - Microsoft Storage Port Driver, Microsoft Corporation

Highest reported total DPC routine time (%): 0,027837
Driver with highest DPC total execution time: ntoskrnl.exe - NT Kernel & System, Microsoft Corporation

Total time spent in DPCs (%) 0,076191

DPC count (execution time <250 µs): 184379
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 741
DPC count (execution time 1000-2000 µs): 0
DPC count (execution time 2000-4000 µs): 0
DPC count (execution time >=4000 µs): 1


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

Total number of hard pagefaults 7751
Hard pagefault count of hardest hit process: 1191
Number of processes hit: 44


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 45,503825
CPU 0 ISR highest execution time (µs): 599,750
CPU 0 ISR total execution time (s): 0,645116
CPU 0 ISR count: 16834
CPU 0 DPC highest execution time (µs): 101624,630
CPU 0 DPC total execution time (s): 4,96270
CPU 0 DPC count: 144058
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 9,506324
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): 157,270
CPU 1 DPC total execution time (s): 0,014279
CPU 1 DPC count: 1397
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 9,430941
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): 338,530
CPU 2 DPC total execution time (s): 0,193414
CPU 2 DPC count: 15209
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 9,527108
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): 333,530
CPU 3 DPC total execution time (s): 0,019715
CPU 3 DPC count: 1329
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 9,556579
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): 315,60
CPU 4 DPC total execution time (s): 0,115661
CPU 4 DPC count: 8321
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 9,578547
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): 241,570
CPU 5 DPC total execution time (s): 0,016906
CPU 5 DPC count: 921
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 10,335426
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): 257,440
CPU 6 DPC total execution time (s): 0,044165
CPU 6 DPC count: 2822
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 10,783242
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): 167,780
CPU 7 DPC total execution time (s): 0,011922
CPU 7 DPC count: 772
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 10,627258
CPU 8 ISR highest execution time (µs): 42,790
CPU 8 ISR total execution time (s): 0,000853
CPU 8 ISR count: 1133
CPU 8 DPC highest execution time (µs): 279,790
CPU 8 DPC total execution time (s): 0,059751
CPU 8 DPC count: 4686
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 10,745196
CPU 9 ISR highest execution time (µs): 13,850
CPU 9 ISR total execution time (s): 0,000020
CPU 9 ISR count: 10
CPU 9 DPC highest execution time (µs): 309,80
CPU 9 DPC total execution time (s): 0,007504
CPU 9 DPC count: 468
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 10,278847
CPU 10 ISR highest execution time (µs): 0,830
CPU 10 ISR total execution time (s): 0,000009
CPU 10 ISR count: 16
CPU 10 DPC highest execution time (µs): 221,980
CPU 10 DPC total execution time (s): 0,023650
CPU 10 DPC count: 1950
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 10,768121
CPU 11 ISR highest execution time (µs): 14,80
CPU 11 ISR total execution time (s): 0,000155
CPU 11 ISR count: 99
CPU 11 DPC highest execution time (µs): 292,530
CPU 11 DPC total execution time (s): 0,038687
CPU 11 DPC count: 3188
_________________________________________________________________________________________________________
 

Beinfreiheit

Semiprofi
Mitglied seit
06.12.2019
Beiträge
43
Hättest du das BIOS Update vom Juli schon installiert und verwendest du die Windows Update Treiber oder die Download Treiber?
Versuch Mal den ersten Downloadtreiber von der Webseite als Inf Installation.
 
Zuletzt bearbeitet:

Allokaat

Enthusiast
Thread Starter
Mitglied seit
03.07.2008
Beiträge
233
Ort
NRW
Ich habe auf das Bios E7B79AMS.AH0 geflasht und mit diesem war es schlimmer. Mit dem E7B79AMS.AG0 sind die Probleme geringer.
Treiber installiere ich immer vom Hersteller.

Versuch Mal den ersten Downloadtreiber von der Webseite als Inf Installation.
Welchen Treiber meinst du und was ist eine Inf-Installation?
 

Beinfreiheit

Semiprofi
Mitglied seit
06.12.2019
Beiträge
43
Das ist doch schon Mal ein Anfang. Du kannst bei Treibern normalerweise auf Umwegen die eigentlichen Treiberdateien extrahieren und manuell installieren. Häufig ist die Treiber-Exe ein selbstentpackendes ZIP.

Über das Startmenü kommst du in den Gerätemanager und dort kannst du dann einen Treiber manuell von einem Pfad installieren, oder über den Rechtsklick auf die passende Inf-Datei.

Aber Versuch vorweg einmal den aktuellen Treiber zu deinstallieren und den Windows Update Treiber zu verwenden. Die sind meist besser auf Kompatibilität geprüft.
 

Allokaat

Enthusiast
Thread Starter
Mitglied seit
03.07.2008
Beiträge
233
Ort
NRW
Ok verstanden.
Aber welche Treiber soll ich deinstallieren und mit Windows Update installieren? Chipsatztreiber? Grafiktreiber? Sound kann ich nicht deinstallieren da im Bios deaktiviert. Derzeitig kommt der Sund über die Grafikkarte (Bildschirm-Klinke).
Ich habe mal testweise die Installation von den AMD Treibern gestartet und mir den Ordner angeguckt wo die entpackt werden. Da sind ja ein Haufen Dateien, die für die Installation entpackt werden. brauche ich da nur die .inf raussuchen und in einen eigenen Ordner kopieren und den als Installationsort angeben?
 

Beinfreiheit

Semiprofi
Mitglied seit
06.12.2019
Beiträge
43
Ich würde erstmal den Sound wieder aktivieren und über den Treiber mit Software deinstallieren. Den Treiber kannst du über den Gerätemanager deinstallieren. Hier dann auch nach geänderter Hardware suchen und den Treiber manuell aktualisieren. Dazu reicht es den Ordner anzugeben, in dem du den Treiber extrahiert hast.
 

Allokaat

Enthusiast
Thread Starter
Mitglied seit
03.07.2008
Beiträge
233
Ort
NRW
So habe mal den Treiber deinstalliert und nach dem Neustart LatencyMon laufen lassen und anschließend über den Gerätemanager den Treiber aktualisiert und LatencyMon nochmal laufen lassen.
Leider keine Veränderung bei dem Ergebnis von LatncyMon.

Mich beschleicht das Gefühl das evtl das Board einen weg haben könnte.

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


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-B27UNKD
OS version: Windows 10, 10.0, version 2004, build: 19041 (x64)
Hardware: MS-7B79, Micro-Star International Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 2600X Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 16335 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 360 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): 101547,263689
Average measured interrupt to process latency (µs): 87,633463

Highest measured interrupt to DPC latency (µs): 101537,346227
Average measured interrupt to DPC latency (µs): 56,603829


_________________________________________________________________________________________________________
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): 990,820
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in ISRs (%) 0,287078

ISR count (execution time <250 µs): 353716
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 2542
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): 1955,40
Driver with highest DPC routine execution time: nvlddmkm.sys - NVIDIA Windows Kernel Mode Driver, Version 452.06 , NVIDIA Corporation

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

Total time spent in DPCs (%) 0,413118

DPC count (execution time <250 µs): 1092141
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 12377
DPC count (execution time 1000-2000 µs): 12
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: firestone.exe

Total number of hard pagefaults 8996
Hard pagefault count of hardest hit process: 1604
Number of processes hit: 56


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 122,166467
CPU 0 ISR highest execution time (µs): 990,820
CPU 0 ISR total execution time (s): 22,708842
CPU 0 ISR count: 308527
CPU 0 DPC highest execution time (µs): 1955,40
CPU 0 DPC total execution time (s): 30,904687
CPU 0 DPC count: 982627
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 17,500774
CPU 1 ISR highest execution time (µs): 236,490
CPU 1 ISR total execution time (s): 0,245409
CPU 1 ISR count: 24245
CPU 1 DPC highest execution time (µs): 489,280
CPU 1 DPC total execution time (s): 0,687598
CPU 1 DPC count: 28727
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 14,233567
CPU 2 ISR highest execution time (µs): 333,510
CPU 2 ISR total execution time (s): 0,127132
CPU 2 ISR count: 4291
CPU 2 DPC highest execution time (µs): 639,210
CPU 2 DPC total execution time (s): 0,386246
CPU 2 DPC count: 37990
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 13,088773
CPU 3 ISR highest execution time (µs): 194,130
CPU 3 ISR total execution time (s): 0,002590
CPU 3 ISR count: 75
CPU 3 DPC highest execution time (µs): 286,470
CPU 3 DPC total execution time (s): 0,132419
CPU 3 DPC count: 5999
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 13,038878
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): 646,490
CPU 4 DPC total execution time (s): 0,184147
CPU 4 DPC count: 9433
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 13,085722
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): 216,510
CPU 5 DPC total execution time (s): 0,075243
CPU 5 DPC count: 2802
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 14,194131
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): 345,290
CPU 6 DPC total execution time (s): 0,212968
CPU 6 DPC count: 9318
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 14,072458
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): 317,710
CPU 7 DPC total execution time (s): 0,076059
CPU 7 DPC count: 2738
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 13,891490
CPU 8 ISR highest execution time (µs): 119,790
CPU 8 ISR total execution time (s): 0,021143
CPU 8 ISR count: 15153
CPU 8 DPC highest execution time (µs): 493,750
CPU 8 DPC total execution time (s): 0,232260
CPU 8 DPC count: 10429
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 13,286668
CPU 9 ISR highest execution time (µs): 15,040
CPU 9 ISR total execution time (s): 0,000689
CPU 9 ISR count: 379
CPU 9 DPC highest execution time (µs): 300,110
CPU 9 DPC total execution time (s): 0,098009
CPU 9 DPC count: 3018
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 13,866560
CPU 10 ISR highest execution time (µs): 29,40
CPU 10 ISR total execution time (s): 0,002790
CPU 10 ISR count: 1137
CPU 10 DPC highest execution time (µs): 299,120
CPU 10 DPC total execution time (s): 0,155187
CPU 10 DPC count: 7036
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 13,891050
CPU 11 ISR highest execution time (µs): 112,020
CPU 11 ISR total execution time (s): 0,006358
CPU 11 ISR count: 2451
CPU 11 DPC highest execution time (µs): 293,110
CPU 11 DPC total execution time (s): 0,118633
CPU 11 DPC count: 4413
_________________________________________________________________________________________________________
 

HicoN

Semiprofi
Mitglied seit
28.02.2019
Beiträge
329
Klingt nach nem klassischen ram problem. Um defekte auszuschließen lad dir memtest64 runter und lass es von einem bootable usb stick laufen. Wenn Fehler auftreten teste die Ram Sticks einzeln durch.
 

Allokaat

Enthusiast
Thread Starter
Mitglied seit
03.07.2008
Beiträge
233
Ort
NRW
Erst flashen und dann cmos clear oder cmos clear und dann flashen?

Raid-Treiber muss ich nicht installieren, oder? Habe kein Raid
 

Beinfreiheit

Semiprofi
Mitglied seit
06.12.2019
Beiträge
43
Erst Clear Cmos
 

Allokaat

Enthusiast
Thread Starter
Mitglied seit
03.07.2008
Beiträge
233
Ort
NRW
Chipsatztreiber und Flash incl. clear CMOS gemacht, keine Besserung.
_________________________________________________________________________________________________________
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:10:13 (h:mm:ss) on all processors.


_________________________________________________________________________________________________________
SYSTEM INFORMATION
_________________________________________________________________________________________________________
Computer name: DESKTOP-B27UNKD
OS version: Windows 10, 10.0, version 2004, build: 19041 (x64)
Hardware: MS-7B79, Micro-Star International Co., Ltd.
CPU: AuthenticAMD AMD Ryzen 5 2600X Six-Core Processor
Logical processors: 12
Processor groups: 1
RAM: 16332 MB total


_________________________________________________________________________________________________________
CPU SPEED
_________________________________________________________________________________________________________
Reported CPU speed: 360 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): 101094,552520
Average measured interrupt to process latency (µs): 60,456080

Highest measured interrupt to DPC latency (µs): 101082,190614
Average measured interrupt to DPC latency (µs): 36,975564


_________________________________________________________________________________________________________
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): 1039,710
Driver with highest ISR routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in ISRs (%) 0,149144

ISR count (execution time <250 µs): 265729
ISR count (execution time 250-500 µs): 0
ISR count (execution time 500-1000 µs): 663
ISR count (execution time 1000-2000 µs): 1
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): 1540,050
Driver with highest DPC routine execution time: dxgkrnl.sys - DirectX Graphics Kernel, Microsoft Corporation

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

Total time spent in DPCs (%) 0,356797

DPC count (execution time <250 µs): 1305038
DPC count (execution time 250-500 µs): 0
DPC count (execution time 500-10000 µs): 3846
DPC count (execution time 1000-2000 µs): 3
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 58032
Hard pagefault count of hardest hit process: 48526
Number of processes hit: 73


_________________________________________________________________________________________________________
PER CPU DATA
_________________________________________________________________________________________________________
CPU 0 Interrupt cycle time (s): 77,957897
CPU 0 ISR highest execution time (µs): 1039,710
CPU 0 ISR total execution time (s): 10,649132
CPU 0 ISR count: 199070
CPU 0 DPC highest execution time (µs): 1540,050
CPU 0 DPC total execution time (s): 17,532328
CPU 0 DPC count: 682769
_________________________________________________________________________________________________________
CPU 1 Interrupt cycle time (s): 15,550067
CPU 1 ISR highest execution time (µs): 267,890
CPU 1 ISR total execution time (s): 0,241227
CPU 1 ISR count: 33458
CPU 1 DPC highest execution time (µs): 400,910
CPU 1 DPC total execution time (s): 1,540710
CPU 1 DPC count: 99218
_________________________________________________________________________________________________________
CPU 2 Interrupt cycle time (s): 12,251515
CPU 2 ISR highest execution time (µs): 223,440
CPU 2 ISR total execution time (s): 0,046395
CPU 2 ISR count: 2808
CPU 2 DPC highest execution time (µs): 405,350
CPU 2 DPC total execution time (s): 0,788965
CPU 2 DPC count: 59923
_________________________________________________________________________________________________________
CPU 3 Interrupt cycle time (s): 11,378324
CPU 3 ISR highest execution time (µs): 177,610
CPU 3 ISR total execution time (s): 0,002516
CPU 3 ISR count: 131
CPU 3 DPC highest execution time (µs): 234,080
CPU 3 DPC total execution time (s): 0,477112
CPU 3 DPC count: 36428
_________________________________________________________________________________________________________
CPU 4 Interrupt cycle time (s): 12,041286
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): 496,710
CPU 4 DPC total execution time (s): 1,143352
CPU 4 DPC count: 93047
_________________________________________________________________________________________________________
CPU 5 Interrupt cycle time (s): 11,693742
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): 206,20
CPU 5 DPC total execution time (s): 0,747317
CPU 5 DPC count: 60311
_________________________________________________________________________________________________________
CPU 6 Interrupt cycle time (s): 12,471259
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): 557,710
CPU 6 DPC total execution time (s): 0,770149
CPU 6 DPC count: 51860
_________________________________________________________________________________________________________
CPU 7 Interrupt cycle time (s): 12,049829
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): 301,750
CPU 7 DPC total execution time (s): 0,478194
CPU 7 DPC count: 32865
_________________________________________________________________________________________________________
CPU 8 Interrupt cycle time (s): 11,800609
CPU 8 ISR highest execution time (µs): 146,050
CPU 8 ISR total execution time (s): 0,030506
CPU 8 ISR count: 24077
CPU 8 DPC highest execution time (µs): 262,940
CPU 8 DPC total execution time (s): 1,055948
CPU 8 DPC count: 79063
_________________________________________________________________________________________________________
CPU 9 Interrupt cycle time (s): 10,811427
CPU 9 ISR highest execution time (µs): 19,860
CPU 9 ISR total execution time (s): 0,001389
CPU 9 ISR count: 874
CPU 9 DPC highest execution time (µs): 305,340
CPU 9 DPC total execution time (s): 0,581915
CPU 9 DPC count: 41148
_________________________________________________________________________________________________________
CPU 10 Interrupt cycle time (s): 11,711371
CPU 10 ISR highest execution time (µs): 39,640
CPU 10 ISR total execution time (s): 0,003268
CPU 10 ISR count: 1672
CPU 10 DPC highest execution time (µs): 930,170
CPU 10 DPC total execution time (s): 0,675118
CPU 10 DPC count: 42144
_________________________________________________________________________________________________________
CPU 11 Interrupt cycle time (s): 11,463767
CPU 11 ISR highest execution time (µs): 205,250
CPU 11 ISR total execution time (s): 0,009160
CPU 11 ISR count: 4303
CPU 11 DPC highest execution time (µs): 218,170
CPU 11 DPC total execution time (s): 0,484975
CPU 11 DPC count: 30111
_________________________________________________________________________________________________________
 

Alpha11

Enthusiast
Mitglied seit
31.07.2012
Beiträge
13.058
Windows clean neu installieren ist da noch ne Option und natürlich bei der Windows Installation nur jenau eine SSD anschließen und alle Partitionen auf selbiger bei der Windows Installation löschen.

"Habe schon eine Neuinstallation von einer SSD auf eine M2-SSD gemacht um die SSD auszuschließen"

Was soll das genau bedeuten?

Von der SSD auf ne M2-SSD zu klonen oder kopieren ist sowas von keine Neuinstallation!

Wenn auch das nicht hilft ist da was putt und da hilft nur tausch...
 

Allokaat

Enthusiast
Thread Starter
Mitglied seit
03.07.2008
Beiträge
233
Ort
NRW
Über eine Neuinstallation habe ich auch schon nachgedacht.

"Habe schon eine Neuinstallation von einer SSD auf eine M2-SSD gemacht um die SSD auszuschließen"
Da habe ich mich nicht richtig ausgedrückt. Es war eine Neuinstallation.

"Windows Installation nur jenau eine SSD anschließen und alle Partitionen auf selbiger bei der Windows Installation löschen. "
Warum nur eine SSD anschließen?
 

Alpha11

Enthusiast
Mitglied seit
31.07.2012
Beiträge
13.058
Weil sonst die EFI-Systempartition bzw der Bootmanager auf der anderen SSD/HDD landen kann...

Gehort schon sehr sehr lange zu jeder wirklich sauberen Windows Neuinstallation!


Hängt normalerweise vom SATA Port von SSD/HDD ab, nach meiner Erfahrung aber definitiv nicht immer und deshalb schließt man definitiv bei ner wirklich sauberen Windows Neuinstallation nur jenau eine SSD/HDD an.
 
Zuletzt bearbeitet:

Phantomias88

Urgestein
Mitglied seit
19.04.2008
Beiträge
8.260
Ort
StuggiTown
Der Fehler mit der LAtenz scheint wohl schon bekannt zu sein: https://windows-nachrichten.de/dxgkrnl-sys-windows-10/
Ich würde es hiermit zuerst mal Versuche:

Lösung 6 – SFC-Scan ausführen
Wenn keine der Lösungen von oben es geschafft hat, die Arbeit zu erledigen, werden wir es mit ein paar eingebauten Fehlerbehebern versuchen, die in Windows 10 gefunden wurden. Der erste Troubleshooter, den wir versuchen werden, ist der SFC-Scan. Hier ist, wie man es ausführt:

  1. Gehen Sie zu Suchen, geben Sie cmd ein und öffnen Sie die Eingabeaufforderung als Administrator.
  2. Geben Sie den folgenden Befehl ein und drücken Sie die Eingabetaste: sfc/scannow
  3. Warten Sie, bis der Vorgang abgeschlossen ist.
  4. Starten Sie Ihren Computer neu.

Da es sich immer um die selbe Datei handelt gehe ich davon aus, dass diese Datei beschädigt ist oder das Dateisystem.
Daher ist eine Windows Neuinstallation auch eine Option, die allerdings länger dauert als nur das Problem selbst zu lösen.

MfG
 

Allokaat

Enthusiast
Thread Starter
Mitglied seit
03.07.2008
Beiträge
233
Ort
NRW
Der Fehler mit der LAtenz scheint wohl schon bekannt zu sein: https://windows-nachrichten.de/dxgkrnl-sys-windows-10/
Ich würde es hiermit zuerst mal Versuche:



Da es sich immer um die selbe Datei handelt gehe ich davon aus, dass diese Datei beschädigt ist oder das Dateisystem.
Daher ist eine Windows Neuinstallation auch eine Option, die allerdings länger dauert als nur das Problem selbst zu lösen.

MfG
Das habe ich auch schon versucht, aber keinen Erfolg. sgc/scannow hat keine Fehler angezeigt.
Weil sonst die EFI-Systempartition bzw der Bootmanager auf der anderen SSD/HDD landen kann...

Gehort schon sehr sehr lange zu jeder wirklich sauberen Windows Neuinstallation!


Hängt normalerweise vom SATA Port von SSD/HDD ab, nach meiner Erfahrung aber definitiv nicht immer und deshalb schließt man definitiv bei ner wirklich sauberen Windows Neuinstallation nur jenau eine SSD/HDD an.

Das ist meine erste Installation mit 2 laufenden SSDs. Danke für die Info.

Da scheinbar kein Lösungsansatz bei mir fruchten will, muss ich wohl oder über doch eine Neuinstallation durchführen...
 

Phantomias88

Urgestein
Mitglied seit
19.04.2008
Beiträge
8.260
Ort
StuggiTown
Das habe ich auch schon versucht, aber keinen Erfolg. sgc/scannow hat keine Fehler angezeigt.


Das ist meine erste Installation mit 2 laufenden SSDs. Danke für die Info.

Da scheinbar kein Lösungsansatz bei mir fruchten will, muss ich wohl oder über doch eine Neuinstallation durchführen...
Dann kannst noch "chkdsk C: /r" probieren, damit lässt sich das Dateisystem reparieren.
Wenn das auch keine Fehler findet, dann Neuinstallation von Windows.
 

Allokaat

Enthusiast
Thread Starter
Mitglied seit
03.07.2008
Beiträge
233
Ort
NRW
Dann kannst noch "chkdsk C: /r" probieren, damit lässt sich das Dateisystem reparieren.
Wenn das auch keine Fehler findet, dann Neuinstallation von Windows.

Das werde ich noch versuchen. Danke.

Edit: Hat leider nicht funktioniert... Jetzt wird Neuinstalliert... Was ich mich freu 😑
 
Zuletzt bearbeitet:
Oben Unten