Häufige Bluescreens

Zuerst einmal: Ich bin neu hier deshalb sorry wenn ich hier im falschen Thema gelandet bin.

Zu meinem Problem.
Ich hab seit einigen Woche im wieder Bluescreens. Hatte zuerst den verdacht auf Ram oder Festplatte, hab mit MemTest86 auch mal getestet, es wurde aber kein Fehler gefunden. Hab mal mit WhoCrashed die Fehler analysieren lassen, kann selber aber nicht viel damit anfangen.

Hab mein System vor gut 3 Jahren selber zusammen gebaut.

Graka: Asus Nvidia GTX 670
Fesplatte: Samsung SSD840 Pro
Prozessor: AMD FX(tm) 8320
RAM: 1xGeIL Evo Corsa 8GN
OS: Windoof 10

WhoCrashed:On Mon 05.12.2016 16:10:26 your computer crashed
crash dump file: C:\WINDOWS\Minidump\120516-5984-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0x139 (0x3, 0xFFFFF800EF3B8BA0, 0xFFFFF800EF3B8AF8, 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.



On Mon 05.12.2016 16:10:26 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: 0x139 (0x3, 0xFFFFF800EF3B8BA0, 0xFFFFF800EF3B8AF8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
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.



On Wed 30.11.2016 15:39:09 your computer crashed
crash dump file: C:\WINDOWS\Minidump\113016-5187-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14A510)
Bugcheck code: 0xD1 (0x0, 0xFF, 0x74, 0x0)
Error: DRIVER_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 a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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 Tue 29.11.2016 13:42:11 your computer crashed
crash dump file: C:\WINDOWS\Minidump\112916-5156-01.dmp
This was probably caused by the following module: win32kbase.sys (win32kbase+0x4E5C5)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFDD512FDDE5C5, 0xFFFFBB8194C28F70, 0x0)
Error: SYSTEM_SERVICE_EXCEPTION
file path: C:\WINDOWS\system32\win32kbase.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Basis-Win32k-Kerneltreiber
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 Fri 18.11.2016 13:42:06 your computer crashed
crash dump file: C:\WINDOWS\Minidump\111816-5937-01.dmp
This was probably caused by the following module: afd.sys (0xFFFFF8012B46A4AA)
Bugcheck code: 0xD1 (0x10, 0x2, 0x0, 0xFFFFF8012B46A4AA)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\WINDOWS\system32\drivers\afd.sys
product: Betriebssystem Microsoft® Windows®
company: Microsoft Corporation
description: Treiber für zusätzliche WinSock-Funktionen
Bug check description: This indicates that a kernel-mode driver attempted to access pageable memory at a process IRQL that was too high.
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.



Weiterlesen...