Hello everyone, I'm having this issue since last month
system information:-
Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Intel586
16Gb Gskill ram
Z170X-Gaming 3, Gigabyte Motherboard
Nvidia Geforce GTX1060 6gb amp edition
Windows 10 pro
BSOD happens mostly while playing games
watchdogs 2
tekken 7
hellblade etc
after 20 min bsod occurs with different errors
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 25-10-2017 01:13:39 your computer crashed
crash dump file: C:\Windows\Minidump\102417-5234-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
On Tue 24-10-2017 01:11:05 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalSendSoftwareInterrupt+0x50E)
Bugcheck code: 0xC5 (0xFFFFF80122799078, 0x2, 0x0, 0xFFFFF8012F698A64)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that the system attempted to access invalid 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. 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 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 23-10-2017 16:19:20 your computer crashed
crash dump file: C:\Windows\Minidump\102317-5187-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
On Mon 23-10-2017 15:10:07 your computer crashed
crash dump file: C:\Windows\Minidump\102317-5015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xA (0xFFFFDC0100A25A90, 0x2, 0x1, 0xFFFFF8006627F0C9)
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 Mon 23-10-2017 14:51:19 your computer crashed
crash dump file: C:\Windows\Minidump\102317-5312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x19 (0xE, 0xFFFFE503B59C71A0, 0x96D8EA9600E9A0B8, 0x96D8EA967DE9A0B8)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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. This problem might also be caused because of overheating (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.
Minidump
plzzz help
already done
drivers scan
memtest86
reinstalled windows
virus scan
system information:-
Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz Intel586
16Gb Gskill ram
Z170X-Gaming 3, Gigabyte Motherboard
Nvidia Geforce GTX1060 6gb amp edition
Windows 10 pro
BSOD happens mostly while playing games
watchdogs 2
tekken 7
hellblade etc
after 20 min bsod occurs with different errors
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dump directory: C:\Windows\Minidump
Crash dumps are enabled on your computer.
On Wed 25-10-2017 01:13:39 your computer crashed
crash dump file: C:\Windows\Minidump\102417-5234-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
On Tue 24-10-2017 01:11:05 your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: hal.dll (hal!HalSendSoftwareInterrupt+0x50E)
Bugcheck code: 0xC5 (0xFFFFF80122799078, 0x2, 0x0, 0xFFFFF8012F698A64)
Error: DRIVER_CORRUPTED_EXPOOL
file path: C:\Windows\system32\hal.dll
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: Hardware Abstraction Layer DLL
Bug check description: This indicates that the system attempted to access invalid 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. 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 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 23-10-2017 16:19:20 your computer crashed
crash dump file: C:\Windows\Minidump\102317-5187-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
On Mon 23-10-2017 15:10:07 your computer crashed
crash dump file: C:\Windows\Minidump\102317-5015-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0xA (0xFFFFDC0100A25A90, 0x2, 0x1, 0xFFFFF8006627F0C9)
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 Mon 23-10-2017 14:51:19 your computer crashed
crash dump file: C:\Windows\Minidump\102317-5312-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x16C580)
Bugcheck code: 0x19 (0xE, 0xFFFFE503B59C71A0, 0x96D8EA9600E9A0B8, 0x96D8EA967DE9A0B8)
Error: BAD_POOL_HEADER
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 pool header is corrupt.
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. This problem might also be caused because of overheating (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.
Minidump
plzzz help
already done
drivers scan
memtest86
reinstalled windows
virus scan