I built a new machine about a month ago with parts (apart from the SSD) from overclockers, nothing is over clocked.
Specs -
Avexir MPower Yellow Series 32GB (4x8GB) DDR3 PC3-12800C10 1600MHz Quad Channel Memory Kit (AVD3U16001008G-4CM)
Intel Core i5-4670K 3.40GHz (Haswell) Socket LGA1150 Processor - OEM
Asus GeForce GTX 660 DirectCU II 2048MB GDDR5 PCI-Express Graphics Card
Gigabyte Z87-D3HP Intel Z87 (Socket 1150) DDR3 ATX Motherboard
Asus 24x DVDąRW DRW-24B5ST SATA ReWriter - Black (Retail)
Crucial CT128M4SSD2 128GB M4 SSD
I've tried various things, driver updates, firmware update on the SSD.
I run a full memtest for 90 minutes and found no errors, I also ran Prime95 and didn't find anything.
There doesn't seem to be one particular program that's causing the issue, in fact I've had it blue screen when i've been out of the room.
It appears to be a random variety of errors, according to who crashed, but mostly in the windows kernel. (dump below)
On Tue 17/12/2013 20:55:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121713-8938-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000306DD2B, 0xFFFFF8800A75FFB0, 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 16/12/2013 23:38:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121613-8548-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030C1EBC, 0x0, 0x20000000010)
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 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/12/2013 23:55:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121313-10233-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030D0D8C, 0xFFFFF8800C23BF70, 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 09/12/2013 22:15:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120913-11949-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7807A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000309607A, 0xFFFFF88005B055C8, 0xFFFFF88005B04E20)
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 Fri 06/12/2013 21:02:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120613-8658-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x658, 0x2, 0x0, 0xFFFFF800030DB39D)
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 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 Sun 01/12/2013 18:50:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120113-8392-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFB4044BA41CB, 0x0, 0xFFFFF800030A87AF, 0x7)
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 Sun 01/12/2013 16:07:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120113-8954-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x16, 0xFFFFFA801BA422B0, 0x3000, 0x400)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
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.
Any advice on this? It's getting a bit tiresome!
Specs -
Avexir MPower Yellow Series 32GB (4x8GB) DDR3 PC3-12800C10 1600MHz Quad Channel Memory Kit (AVD3U16001008G-4CM)
Intel Core i5-4670K 3.40GHz (Haswell) Socket LGA1150 Processor - OEM
Asus GeForce GTX 660 DirectCU II 2048MB GDDR5 PCI-Express Graphics Card
Gigabyte Z87-D3HP Intel Z87 (Socket 1150) DDR3 ATX Motherboard
Asus 24x DVDąRW DRW-24B5ST SATA ReWriter - Black (Retail)
Crucial CT128M4SSD2 128GB M4 SSD
I've tried various things, driver updates, firmware update on the SSD.
I run a full memtest for 90 minutes and found no errors, I also ran Prime95 and didn't find anything.
There doesn't seem to be one particular program that's causing the issue, in fact I've had it blue screen when i've been out of the room.
It appears to be a random variety of errors, according to who crashed, but mostly in the windows kernel. (dump below)
On Tue 17/12/2013 20:55:28 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121713-8938-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF8000306DD2B, 0xFFFFF8800A75FFB0, 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 16/12/2013 23:38:33 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121613-8548-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF800030C1EBC, 0x0, 0x20000000010)
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 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/12/2013 23:55:12 GMT your computer crashed
crash dump file: C:\Windows\Minidump\121313-10233-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF800030D0D8C, 0xFFFFF8800C23BF70, 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 09/12/2013 22:15:50 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120913-11949-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x7807A)
Bugcheck code: 0x1000007E (0xFFFFFFFFC0000005, 0xFFFFF8000309607A, 0xFFFFF88005B055C8, 0xFFFFF88005B04E20)
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 Fri 06/12/2013 21:02:57 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120613-8658-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0xA (0x658, 0x2, 0x0, 0xFFFFF800030DB39D)
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 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 Sun 01/12/2013 18:50:51 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120113-8392-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x75BC0)
Bugcheck code: 0x50 (0xFFFFFB4044BA41CB, 0x0, 0xFFFFF800030A87AF, 0x7)
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 Sun 01/12/2013 16:07:37 GMT your computer crashed
crash dump file: C:\Windows\Minidump\120113-8954-01.dmp
This was probably caused by the following module: watchdog.sys (watchdog+0x122F)
Bugcheck code: 0x10E (0x16, 0xFFFFFA801BA422B0, 0x3000, 0x400)
Error: VIDEO_MEMORY_MANAGEMENT_INTERNAL
file path: C:\Windows\system32\drivers\watchdog.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Watchdog Driver
Bug check description: This indicates that the video memory manager has encountered a condition that it is unable to recover from.
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.
Any advice on this? It's getting a bit tiresome!
