Lauter BlueScreens - SSD schuld?

[J@ck]

Ich habe seit etwa 2 Monaten eine Samsung 830er 256GB SSD in meinem Rechner (siehe Profil) und habe seitdem BSOD.

1. Es fing mit Boot-Loops an, was am BIOS lag (hab von IDE auf AHCI umgestellt). Behelf war hiermit schnell gemacht (http://www.winfuture-forum.de/index....owtopic=171579), dennoch gab es im Betrieb BSOD.
Neu aufgesetzt.

2. Es lief 1-2 Wochen alles ruhig, bis ganz merkwürdige Grafikprobleme auftraten (BSOD nach AERO Start). Grafikkarte getauscht, System lief wieder gut durch.

3. Seit gestern bekomme ich 2-3 BSOD täglich. Da ich wegen der SSD keine Auslagerungsdatei habe, konnte auch kein DUMP File erstellt werden (hat gedauert, bis ich das behirnt habe).
Auswertung aus dem Dump:

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Mon 31.12.2012 15:23:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123112-17409-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030095F7, 0xFFFFF880071BBEF0, 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 Mon 31.12.2012 15:23:35 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: win32k.sys (win32k!EngRestoreFloatingPointState+0xB4D3) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030095F7, 0xFFFFF880071BBEF0, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\Windows\system32\win32k.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Multi-User Win32 Driver
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 a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. 



On Mon 31.12.2012 11:21:24 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123112-11949-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x54068) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EB1068, 0xFFFFF880033AEFC8, 0xFFFFF880033AE820)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 31.12.2012 11:05:52 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123112-11013-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000314C93E, 0xFFFFF880092DD720, 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 Mon 31.12.2012 10:53:58 GMT your computer crashed
crash dump file: C:\Windows\Minidump\123112-11466-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x54068) 
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF80002EA0068, 0xFFFFF880031CAFC8, 0xFFFFF880031CA820)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
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 system thread generated an exception which the error handler did not catch.
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 20.12.2012 20:19:06 GMT your computer crashed
crash dump file: C:\Windows\Minidump\122012-11840-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7EFC0) 
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80002F9893E, 0xFFFFF8800946C720, 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. 




--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

6 crash dumps have been found and analyzed. No offending third party drivers have been found. Consider configuring your system to produce a full memory dump for better analysis.

Was ich seitdem gemacht habe:
- Event Log durchforstet, nichts gefunden
- MemTest durchlaufen lassen, nach guten 3 Stunden 1 Fehler gefunden.
- Neueste Treiber für USB3.0 und AHCI Controller installiert
- BIOS Update auf aktuellste FW
- Alle anderen Treiber auf Aktualität geprüft
- Mit der Stoffpuppe meines Sohnes gegen den Rechner geschlagen

Ich hab keine Ahnung, wie ich noch ausschließen soll. Das ständige Neu-Aufsetzen wird mühsam und unendlich anstrengend, hab keine Lust mehr dazu. Zwar wollte ich als nächsten Schritt die SSD wieder gegen eine HDD tauschen, aber ich will nicht wieder neu aufsetzen.

Wie kann ich sinnvoll ohne dem Ausschlussverfahren analysieren?