Hallo,
ich habe mir am Freitag einen neuen PC zusammen gestellt und zusammen gebaut.
Alles lief gut. Nach ein paar Stunden dann der erste BSOD. Hab mir nichts gedacht, einfach neu starten lassen.
Dann wieder ein BSOD. Wurd ich schon etwas stutzig, aber hab trotzdem nichts gemacht.
Dann kam wieder einer und ich hab mich drum gekümmert. Ich habe im BIOS den RAM von 1T auf 2T gestellt, dann war erstmal Ruhe.
Irgendwann fing der PC dann an sich selber neu zu starten. Das habe ich dann bei Google eingegeben, jemand gab den Tipp, das Netzteil umzudrehen (Lüfter nach oben) - gesagt, getan.
Ich hatte danach keine Probleme mehr, der PC blieb stabil.
Bis auf heute.
Heute kam wieder ein BSOD, um genauer zu sein gerade. (KERNEL_SECURITY_CHECK_FAILURE)
Hier sind mal alle BSOD, die ich bis jetzt hatte:
CLOCK_WATCHDOG_TIMEOUT
CUSTOM_ERROR
DRIVER_IRQL_NOT_LESS_OR_EQUAL
PAGE_FAULT_IN_NONPAGED_AREA
TIMER_OR_DPC_INVALID
KERNEL_SECURITY_CHECK_FAILURE
Es war immer eine andere - nie die gleiche.
Mein System ist folgendes:
MB; ASRock 970 Performance (fatil1ty)
Grafik; MSI GTX 960
CPU; FX 8350 mit H100i Wasserkühlung
Netzteil; Pure Power (be quiet, 630 Watt)
Es regt mich ziemlich auf, deshalb muss ich jetzt hier mal fragen.
Whocrashed gibt folgendes aus:
Ich hoffe jemand kennt eine Lösung.
Liebe Grüße
ich habe mir am Freitag einen neuen PC zusammen gestellt und zusammen gebaut.
Alles lief gut. Nach ein paar Stunden dann der erste BSOD. Hab mir nichts gedacht, einfach neu starten lassen.
Dann wieder ein BSOD. Wurd ich schon etwas stutzig, aber hab trotzdem nichts gemacht.
Dann kam wieder einer und ich hab mich drum gekümmert. Ich habe im BIOS den RAM von 1T auf 2T gestellt, dann war erstmal Ruhe.
Irgendwann fing der PC dann an sich selber neu zu starten. Das habe ich dann bei Google eingegeben, jemand gab den Tipp, das Netzteil umzudrehen (Lüfter nach oben) - gesagt, getan.
Ich hatte danach keine Probleme mehr, der PC blieb stabil.
Bis auf heute.
Heute kam wieder ein BSOD, um genauer zu sein gerade. (KERNEL_SECURITY_CHECK_FAILURE)
Hier sind mal alle BSOD, die ich bis jetzt hatte:
CLOCK_WATCHDOG_TIMEOUT
CUSTOM_ERROR
DRIVER_IRQL_NOT_LESS_OR_EQUAL
PAGE_FAULT_IN_NONPAGED_AREA
TIMER_OR_DPC_INVALID
KERNEL_SECURITY_CHECK_FAILURE
Es war immer eine andere - nie die gleiche.
Mein System ist folgendes:
MB; ASRock 970 Performance (fatil1ty)
Grafik; MSI GTX 960
CPU; FX 8350 mit H100i Wasserkühlung
Netzteil; Pure Power (be quiet, 630 Watt)
Es regt mich ziemlich auf, deshalb muss ich jetzt hier mal fragen.
Whocrashed gibt folgendes aus:
On Mon 16.02.2015 12:14:54 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021615-65328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00027997390, 0xFFFFD000279972E8, 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 16.02.2015 12:14:54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x32E70)
Bugcheck code: 0x139 (0x3, 0xFFFFD00027997390, 0xFFFFD000279972E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Sat 14.02.2015 19:29:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021415-50562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xC7 (0x8, 0x1, 0xFFFFE00000ACDBB0, 0xFFFFE00003B4C180)
Error: TIMER_OR_DPC_INVALID
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
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 Sat 14.02.2015 17:47:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021415-69656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x50 (0xFFFFB000232E590C, 0x1, 0xFFFFF8035BCD7224, 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 Fri 13.02.2015 22:36:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021315-53031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFD000207A7180, 0x5)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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 13.02.2015 19:23:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021315-69468-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x1FA2)
Bugcheck code: 0xD1 (0x3, 0x2, 0x1, 0xFFFFF80000F73FA2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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.
On Fri 13.02.2015 19:23:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021315-57031-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
crash dump file: C:\Windows\Minidump\021615-65328-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x139 (0x3, 0xFFFFD00027997390, 0xFFFFD000279972E8, 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 16.02.2015 12:14:54 GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: dxgmms1.sys (dxgmms1!VidMmInterface+0x32E70)
Bugcheck code: 0x139 (0x3, 0xFFFFD00027997390, 0xFFFFD000279972E8, 0x0)
Error: KERNEL_SECURITY_CHECK_FAILURE
file path: C:\Windows\system32\drivers\dxgmms1.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: DirectX Graphics MMS
Bug check description: The kernel has detected the corruption of a critical data structure.
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 Sat 14.02.2015 19:29:59 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021415-50562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0xC7 (0x8, 0x1, 0xFFFFE00000ACDBB0, 0xFFFFE00003B4C180)
Error: TIMER_OR_DPC_INVALID
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This is issued if a kernel timer or delayed procedure call (DPC) is found somewhere in memory where it is not permitted.
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 Sat 14.02.2015 17:47:27 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021415-69656-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x50 (0xFFFFB000232E590C, 0x1, 0xFFFFF8035BCD7224, 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 Fri 13.02.2015 22:36:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021315-53031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x101 (0x18, 0x0, 0xFFFFD000207A7180, 0x5)
Error: CLOCK_WATCHDOG_TIMEOUT
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 expected clock interrupt on a secondary processor, in a multi-processor system, was not received within the allocated interval.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This problem might be caused by a 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 13.02.2015 19:23:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021315-69468-01.dmp
This was probably caused by the following module: classpnp.sys (CLASSPNP+0x1FA2)
Bugcheck code: 0xD1 (0x3, 0x2, 0x1, 0xFFFFF80000F73FA2)
Error: DRIVER_IRQL_NOT_LESS_OR_EQUAL
file path: C:\Windows\system32\drivers\classpnp.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: SCSI Class System Dll
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.
On Fri 13.02.2015 19:23:35 GMT your computer crashed
crash dump file: C:\Windows\Minidump\021315-57031-01.dmp
This was probably caused by the following module: Unknown ()
Bugcheck code: 0x0 (0x0, 0x0, 0x0, 0x0)
Error: CUSTOM_ERROR
A third party driver was identified as the probable root cause of this system error.
Google query: CUSTOM_ERROR
Ich hoffe jemand kennt eine Lösung.
Liebe Grüße
Zuletzt bearbeitet von einem Moderator:
