Hello, I wonder whether you could help me?
I have been having intermittent BSOD on windows 10 64bit on my new pc:
i7 6700k
H100i GTX
EVGA Z170 FTW
16gb Corsair lpx ddr4
GTX 980 ti FTW
I have saved the mini dump files and got them analysed
Could somebody more knowledgeable than me take a look and see if, hopefully, there is a solution?
On Thu 31/03/2016 12:38:53 GMT your computer crashed
crash dump file: C:\Windows\Minidump\033116-4734-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14F4D0)
Bugcheck code: 0x1A (0x41793, 0xFFFFF68003587F18, 0x4, 0x3)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 31/03/2016 12:38:53 GMT 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: 0x1A (0x41793, 0xFFFFF68003587F18, 0x4, 0x3)
Error: MEMORY_MANAGEMENT
Bug check description: This indicates that a severe memory management error occurred.
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 Tue 29/03/2016 14:03:43 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032916-5625-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF802C60C9F0F, 0xFFFFD00021D96C10, 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 28/03/2016 23:24:41 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032916-3500-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14E240)
Bugcheck code: 0x1A (0x41792, 0xFFFFF68000026BC8, 0x2000000000000000, 0x0)
Error: MEMORY_MANAGEMENT
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 severe memory management error occurred.
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 Mon 28/03/2016 23:09:36 GMT your computer crashed
crash dump file: C:\Windows\Minidump\032916-2828-01.dmp
This was probably caused by the following module: ntfs.sys (NTFS+0xEF5E)
Bugcheck code: 0x1E (0xFFFFFFFFC0000005, 0xFFFFF8010489EF5E, 0xFFFFD00122D39CF8, 0xFFFFD00122D39510)
Error: KMODE_EXCEPTION_NOT_HANDLED
file path: C:\Windows\system32\drivers\ntfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT File System Driver
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 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.