PC hat andauernd Bluescreens wohl wegen einem fehlerhaften Treiber

cris318

Ensign
Dabei seit
Apr. 2014
Beiträge
140
Hallo zusammen,
ich bin leider schon wieder. Auf die Gefahr hin, dass ich etwas mit meinem PC Problemen nerve, aber es geht wohl nicht anders.
So, Ende letzter Woche hat mein PC angefangen Bluescreens zu erleiden mit verschiedenen Fehlercodes. Da ich keine Probleme mit einem Treiber finden konnte und auch keine Probleme mit dem Speicher (siehe Thema hier), dachte ich der RAM wäre inkompatibel (Memtest hat nichts ergeben). Um das zu testen, benutze ich die RAMs meines Bruders: 16GB G.Skill RipJaws V schwarz DDR4-3200 DIMM CL16 Dual Kit . Dieser lief auch ohne zwischenfälle... bis heute. Drei Abstürtze in kürzester Zeit. Der RAM ist also nicht das Problem. Also ging ich noch einmal meine Treiber im Gerätemanager durch. Jetzt habe ich gemerkt, dass ich ein blaues Fragezeichen habe. Habe es nicht bemerkt, weil ich mch auf die gelben Warndreiecke konzentriert habe.

Hier istmal meine Hardware:
Mainboard: B550 Steel Legend
HDD: 1TB Seagate Desktop HDD https://www.mindfactory.de/product_...3-32MB-3-5Zoll--8-9cm--SATA-6Gb-s_775365.html
GPU: 3GB PowerColor Radeon r9 280 TurboDuo https://www.mindfactory.de/product_...uo-OC-Aktiv-PCIe-3-0-x16--Retail-_956579.html
SSD: 120GB Crucial M500 https://www.mindfactory.de/product_...m--SATA-6Gb-s-MLC--CT120M500SSD1-_844175.html
SSD mit neum Windwos Pro https://www.mindfactory.de/product_...TA-6Gb-s-3D-NAND-TLC--CT1000MX50_1219929.html
Arctic Freezer 34 eSport duo
CPU Ryzen 5 3600
Eigentlicher RAM: Corsair Vengeance RGB PRO 32 gb 3200

Geräte die angeschlossen sind:
Monitor: https://www.amazon.de/gp/product/B00BPL078S/ref=ppx_yo_dt_b_asin_title_o05_s01?ie=UTF8&psc=1

Wlan Adapter: https://www.amazon.de/gp/product/B07H3RYFQV/ref=ppx_yo_dt_b_asin_title_o07_s00?ie=UTF8&psc=1

Lautsprecher: https://www.amazon.de/gp/product/B003LNXT7Y/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1

USB Hub: https://www.amazon.de/gp/product/B0719L1316/ref=ppx_yo_dt_b_asin_title_o07_s00?ie=UTF8&psc=1

Zurück zum Treiber:
Es handelt sich dabei um den AMD PSP 11.0 Device. Ich weiß nicht was das ist, was es macht oder ob es wichtig ist. Falls es zu GPU gehört: Könnte es Probleme mit Firefox verursachen (Tabs und Programm stürzen ab)?

treibe_Fehler.PNG


Info.PNG


Falls es nicht dieser Treiber sein sollte sind hier noch einpaar Geräte mit etwas älteren Treiber:

AMD High Definition Audio Device: 10.0.1.12
BenQ GL2450H (AMD High Definition Audio Device), Lautsprecher (Realtekt audio), alle Festplatten: 10.0.19041.1 (von Microsoft)
REaltek 8812Bu Wireless LAN 802.11ac USB NIC (Netzwerkadapter (nehme ich an)): 1030.38.712.2019.

Hier noch einmal was WhoCrashed sagt:

Part 1:

Welcome to WhoCrashed (HOME EDITION) v 6.65


This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



Home Edition Notice


This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


System Information (local)


Computer name: DESKTOP-LLAO93Q
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\Windows
Hardware: ASRock, B550 Steel Legend
CPU: AuthenticAMD AMD Ryzen 5 3600 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 34284011520 bytes (31,9GB)




Crash Dump Analysis


Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Fri 10.07.2020 18:27:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071020-10937-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x1FF00000002, 0x8, 0x1FF00000002)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10.07.2020 18:27:28 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: ntkrnlmp.exe (nt!memset+0x3E2B9)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0x1FF00000002, 0x8, 0x1FF00000002)
Error: KMODE_EXCEPTION_NOT_HANDLED
Bug check description: This indicates that a kernel-mode program generated an exception which the error handler did not catch.
This might be a case of memory corruption. This may be because of a hardware issue such as faulty RAM, overheating (thermal issue) or because of a buggy driver.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10.07.2020 16:46:52 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071020-8468-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x18 (0x0, 0xFFFFBD0A82E1D360, 0x2, 0xFFFFFFFFFFFFFFFF)
Error: REFERENCE_BY_POINTER
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the reference count of an object is illegal for the current state of the object.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 10.07.2020 16:27:14 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071020-8406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x3B (0x80000003, 0xFFFFF8063CD31633, 0xFFFF868CD418C7D0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that an exception happened while executing a routine that transitions from non-privileged code to privileged code.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Thu 09.07.2020 22:59:56 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\070920-8406-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x35 (0xFFFFCE09D9C43740, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check occurs when the IoCallDriver packet has no more stack locations remaining.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





Conclusion


5 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

Part 2:


Welcome to WhoCrashed (HOME EDITION) v 6.65


This program checks for drivers which have been crashing your computer. If your computer has displayed a blue (or black) screen of death, suddenly rebooted or shut down then this program might help you find the root cause of the problem and a solution.

Whenever a computer suddenly reboots without displaying any notice or blue (or black) screen of death, the first thing that is often thought about is a hardware failure. In reality, on Windows a lot of system crashes are caused by malfunctioning device drivers and kernel modules. In case of a kernel error, many computers do not show a blue or black screen unless they are configured for this. Instead these systems suddenly reboot without any notice.

This program will analyze your crash dumps with the single click of a button. It will tell you what drivers are likely to be responsible for crashing your computer. It will report a conclusion which offers suggestions on how to proceed in any situation while the analysis report will display internet links which will help you further troubleshoot any detected problems.

To obtain technical support visit www.resplendence.com/support

Click here to check if you have the latest version or if an update is available.

Just click the Analyze button for a comprehensible report ...



Home Edition Notice


This version of WhoCrashed is free for use at home only. If you would like to use this software at work or in a commercial environment you should get the professional edition of WhoCrashed which allows you to perform more thorough and detailed analysis. It also offers a range of additional features such as remote analysis on remote directories and remote computers on the network.

Please note that this version of WhoCrashed is not licensed for use by professional support engineers.

Click here for more information on the professional edition.
Click here to buy the the professional edition of WhoCrashed.


System Information (local)


Computer name: DESKTOP-LLAO93Q
Windows version: Windows 10 , 10.0, build: 19041
Windows dir: C:\Windows
Hardware: ASRock, B550 Steel Legend
CPU: AuthenticAMD AMD Ryzen 5 3600 6-Core Processor AMD8664, level: 23
12 logical processors, active mask: 4095
RAM: 17103151104 bytes (15,9GB)




Crash Dump Analysis


Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump

On Wed 15.07.2020 17:08:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071520-9140-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x44 (0xFFFFC40B71747920, 0x1232, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Wed 15.07.2020 17:08:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: fltmgr.sys (FLTMGR!FltDecodeParameters+0x6B6)
Bugcheck code: 0x44 (0xFFFFC40B71747920, 0x1232, 0x0, 0x0)
Error: MULTIPLE_IRP_COMPLETE_REQUESTS
file path: C:\Windows\system32\drivers\fltmgr.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Microsoft Dateisystem-Filter-Manager
Bug check description: This indicates that a driver has tried to requested an IRP be completed that is already complete.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in a file system driver. Since there is no other responsible driver detected, this could be pointing to a malfunctioning drive or corrupted disk. It's suggested that you run CHKDSK.



On Wed 15.07.2020 17:01:06 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071520-8656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0xA (0xFFFFF8030200FFF8, 0x2, 0x0, 0xFFFFF8036C039FA2)
Error: IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that Microsoft Windows or a kernel-mode driver accessed paged memory at DISPATCH_LEVEL or above. This is a software bug.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 13.07.2020 16:02:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071320-8437-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x35 (0xFFFF870ACAD1A880, 0x0, 0x0, 0x0)
Error: NO_MORE_IRP_STACK_LOCATIONS
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This bug check occurs when the IoCallDriver packet has no more stack locations remaining.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 13.07.2020 12:26:09 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071320-8312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x50 (0xFFFFE38902010008, 0x0, 0xFFFFF801270CE754, 0x2)
Error: PAGE_FAULT_IN_NONPAGED_AREA
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that invalid system memory has been referenced.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Mon 13.07.2020 10:21:08 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\071320-10328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x3DDA20)
Bugcheck code: 0x1 (0x7FFDD456BB84, 0x0, 0xFFFF0000, 0xFFFF998F2419CB80)
Error: APC_INDEX_MISMATCH
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that there has been a mismatch in the APC state index.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.





Conclusion


6 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.




Soo, falls noch einige Leute dieses lesen sollten. Was kann ich tun? Wo kann ich mir die akktuellsten Versionen für einige Treiber holen (Seriöse Seite?)? Wäre ein Neuaufsetzen besser? Sollte ich meine Crucial Ballistix Bestellung bei Amazon stornieren...?

Vielen Dank ComputerBase Forums Mitglieder :)
 
Ich würde dazu raten die aktuellen Chipsatztreiber bei AMD (Klick) herunterzuladen und zu installieren.
Wird der PSP-Treiber nicht automatisch eingebunden so ist dieser nach Installation der Chipsatztreiber normalerweise in diesem Verzeichnis zu finden C:\AMD\PSP Driver\WTx64.
Wenn man im Geräte-Manager die Treibersuche auf dem eigenen Rechner startet sollten die Treiber installiert werden.
Ist für das Mainboard das aktuelle BIOS installiert? Gerade bei neuen Chipsätzen kann das "First Release"-BIOS manchmal etwas wackelig sein.
 
  • Gefällt mir
Reaktionen: wupi und cris318
Danke für die Antworten. Das Bios wurde auf 1.10 geupdated. Die Chipsatztreiber habe ich damals direkt bei asrock runtergeladen. Soll ich die aktuellen Chipsatztreiber erst deinstallieren bevor ich die von der AMD Seite installiere? Der Ordner für PSP existiert sogar. Falls im Gerätemanager das Fragezeichen immer noch auftaucht, sollte ich PSP besser ausschalten?
 
gut, bios wäre mein erster punkt gewesen.
treiber immer direkt von amd, weil es keine nicht-amd gibt, auch die auf herstellerseiten sind von amd, aber meist älter.
ausnahme: eventuell notebook-graka treiber.
drüberinstallieren sollte passen.
speicher intensiv testen.
 
  • Gefällt mir
Reaktionen: cris318 und Darkling71
Alle klar danke euch :).
Es ist jetzt installiert. Im Gerätemanager ist der Eintrag mit dem Fragezeichen jetzt weg. Ich hoffe das bleibt so. Ich mache drei x Kreuze wenn es jetzt endlich stabil läuft. Mal gucken, ob ich meine RAM Bestellung storniere...
 
Falls du es noch nicht getan hast, empfehle ich in solchen Fällen immer, den System File Checker laufen zu lassen.

Rechtsklick auf Start -> Windows PowerShell (Administrator)

sfc /scannow

Mit Enter bestätigen und nach 5-15 Minuten sollte man ein (hoffentlich) intaktes System als Ergebnis haben.
 
  • Gefällt mir
Reaktionen: cris318 und whats4
ist grundsätzlich eine gute idee, sfc/scannow mal hie und da laufen zu lassen, ohne anlass, nur vorbeugend.
ob jetzt in admin-powershell oder admin-cmd ist wurscht.
ebenso wie chkdsk c: , ohne /f, reicht zur überprüfung vollkommen.

edit: ich z.b. mach das routinemäßig nach jedem win-update.
 
Hallo,
beides hat nichts fehlerhaftes festgestellt. Das haben sie jedoch auch vorher nicht.... Einfach mal hoffen 😅
 
Tu das. @cris318

Und wenn es wieder zu BSOD kommt, nimmst Du die letzten drei aktuellen MiniDumpFiles, packst diese in ein ZIP-Archiv und postest dieses Archiv hier bei CB und hier in diesem Thread. Keinen extra neuen aufmachen, dann kriegen das eigentlich alle mit die diesen Thread hier beobachten. 👍

BFF
 
  • Gefällt mir
Reaktionen: cris318
Hallo zusammen,

PC macht wieder Bluescreens 😩. Im Gerätemanager wird nichts angegeben bezüglich fehlerhaften treibern. Der verifier.exe hat ebenfalls nichts gemeldet. Habe euch wie empfohlen die drei letzten dumps in einem zip Ordner getan und hochgeladen. Da hatte man endlich ruhe....

LG
 

Anhänge

  • Dump.zip
    1.000,7 KB · Aufrufe: 260
Dir sind drei verschiedene Programme (Sky Ticket, firefox, steam) abgeraucht mit drei verschiedenen Fehlern.
Das riecht nach Problemen mit dem RAM. Was aber nicht bedeutet, das der unbedingt defekt ist sondern eventuell nur etwas anders eingestellt werden muesste.

BFF
 
  • Gefällt mir
Reaktionen: cris318
Danke für die Antwort. Wollte gerade gucken, wie mein RAM eingestellt ist. Bin da aufs falsche Programm gegangen (RAIDXper2). Dieser sagt mir das er den rccfg RAID driver nicht finden kann. Frage: Kann das eine Ursache sein und brauche ich RAIDXpert2 (War in der Mainboard Programm Liste deshalb habe ich es heruntergeladen).

RAM sollte auf den default Einstellungen sein. Also morgen einmal memtest. Was könnte man beim RAM sonst noch machen?
 
Wenn Du keinen RAID bauen willst mit Datentraegern brauchst das Programm nicht. Wuerde ich deinstallieren.

Wegen RAM.
Du hast da wohl 32 GByte (2 Riegel) verbaut.
Ich persoenlich vermute das die etwas mehr VDIMM gebrauchen koennten.
Frag einfach unverbindlich @SV3N an deswegen.
 
  • Gefällt mir
Reaktionen: cris318
Das Kit sollte mit XMP-Profil eigentlich recht unkompliziert sein. Ich würde mal 1mv mehr draufgeben, sprich 1,375v und fertig.

Ansonsten mal gescheite Timings ausloten. Planst du RAM OC oder bis du mit DDR4-3200 glücklich?
 
  • Gefällt mir
Reaktionen: BFF und cris318
So ich habe das XMP Profil geladen, aber die voltage wollte er nicht auf 1,375v machen. Er ist von alleine auf 1,374 gesprungen.
Ram OC plane ich nicht. Die 3200 reichen mir erstmal.
 
Mit 1,374 - 1,375v hast du auf jeden Fall mehr als Genug VDIMM anliegen, daran sollte es nicht scheitern. Aber auch mit 1,35 - 1,36v sollten die Riegel laufen, bei XMP-Profil.

Schau mal wie sich das System in Sachen Stabilität jetzt so macht.
 
  • Gefällt mir
Reaktionen: cris318
So... der PC ist heute wieder einmal abgeraucht. Diesmal während einem Spiel. Also wieder bei Steam bzw. Fallout 3. Habe heute einen kompletten mentest durchgeführt. In diesen knapp 6 Stunden wurde nichts aber auch gar nichts gefunden. Ich füge mal einen Ordner mit der neusten DMP File bei. Weiß ehrlich nicht was ich noch machen kann, um den fehler, defekt oder fehlerhaften Treiber zu finden. Werde wohl die idee von thompson004 mal versuchen.
 

Anhänge

  • Dump.zip
    1,3 MB · Aufrufe: 284
Zurück
Top