Trojaner-Board - BSoD w8.1pro64bit

Auf dem Rechner war ein jungfräuliches w8.1. Ich habe ein paar Standardprogramme installiert und eben kam es zu einen (weiteren) BSoD.
Zu dem Rechner: Er ist gut ein Jahr alt, stand aber ca. 11 Monate in der Ecke, da es ein gerichtliches Verfahren zwecks Rücktritt vom Kaufvertrag, weil es mit dem Rechner auch noch andere Probleme, neben BSoD, (lose Steckverbindungen i.d.H.: Front-USB-Anschlüsse und Blu-ray funktionierten überhaupt nicht) gab.
Jetzt habe ich mich mit dem Verkäufer einen Vergleich geschlossen - ich bekomme noch ein paar Hundert Euros kann aber den Rechner behalten. Er ist also erst kürzlich komplett in mein Eigentum übergegangen. Mittlerweile funktioniert o.g. wieder, da ich ihn zu einem Fachbetrieb im Nachbardorf gebracht hatte der mir das Alles für einen fairen Preis gerichtet hat.
Konfiguration:
AMD A10-7870K Black Edition
Gigabyte GA-F2A78M-D3H
Kingston HyperX Beast DIMM XMP Kit 16GB, DDR3-2133
Gigabyte Radeon R7 360 OC, 2GB GDDR5
Crucial BX100 250GB
Toshiba DT01ABA200V - Festplatte - 2TB
Pioneer BDR-S09XLT Blu-ray Disc Writer
Eine vage Vermutung, die ich nicht wirklich begründen kann, geht Richtung Defekt an der SSD. Wie kann ich das prüfen? CrystalDiskInfo erkennt, kennt die SSD nicht.
Ich hoffe es kann mir geholfen werden.
Hier nun die Auswertung von WhoCrashed:

Code:

Crash Dump Analysis

--------------------------------------------------------------------------------
 

Crash dump directory: C:\Windows\Minidump
 

Crash dumps are enabled on your computer.
 

On Fri 31.03.2017 12:54:37 your computer crashed

crash dump file: C:\Windows\Minidump\033117-7062-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14E2A0) 

Bugcheck code: 0x19 (0xE, 0xFFFFE000A947A980, 0x0, 0x2A9BB99C992B5AE6)

Error: BAD_POOL_HEADER

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 pool header is corrupt.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue). 

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 31.03.2017 12:54:37 your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: ntkrnlmp.exe (nt!KeBugCheckEx+0x0) 

Bugcheck code: 0x19 (0xE, 0xFFFFE000A947A980, 0x0, 0x2A9BB99C992B5AE6)

Error: BAD_POOL_HEADER

Bug check description: This indicates that a pool header is corrupt.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue). 

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 21.04.2016 18:57:32 your computer crashed

crash dump file: C:\Windows\Minidump\042116-13515-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0) 

Bugcheck code: 0x4E (0x6, 0x30339F, 0x1, 0x546)

Error: PFN_LIST_CORRUPT

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 page frame number (PFN) list is corrupted.

This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. 

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 07.04.2016 18:11:21 your computer crashed

crash dump file: C:\Windows\Minidump\040716-10953-01.dmp

This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0) 

Bugcheck code: 0x139 (0x3, 0xFFFFD000274FF780, 0xFFFFD000274FF6D8, 0x0)

Error: KERNEL_SECURITY_CHECK_FAILURE

file path: C:\Windows\system32\ntoskrnl.exe

product: Microsoft® Windows® Operating System

company: Microsoft Corporation

description: NT Kernel & System

Bug check description: The kernel has detected the corruption of a critical data structure.

The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.