- Jun 18, 2018
- 2
- 0
- 10
Hello,
I have been using Tomshardware to troubleshoot various problems in the past, but this is my first time posting. I'm a computer rookie, so if I need to provide any further details, I'd be happy to do so as long as I understand how.
So, these BSOD's have been an ongoing pain for the past month. I was running on a stable Win7 machine, with no new software or driver updates or installs. After days of troubleshooting various driver fixes and updates, I decided the only good method to rule out drivers would be to upgrade to Win10.
Within the first hour of Win10 install, I got another BSOD. At first I thought it was because I was still installing updates and drivers, etc.
Kept getting BSODs.
Ran Prime95 on several different occasions. First time, I had 2 thread errors. Next time, it ran clean for 20 mins. 3rd time I had errors on 2 different threads. And 4th time, ran 30 mins with no errors.
Memory tests showed the same thing. Ran windows mem diagnostic twice (with the enhanced test) and it showed some faults. Ran it again and no faults.
Ran FurMark to test GPU. First time, BSOD'ed within 30 seconds. 2nd, 3rd and 4th time, ran for several minutes with no issue.
The Intel Proces Diagnostic has shown mix results of faulty CPU as well as several clean runs.
I'm suspecting this to be a motherboard problem (Gigabyte Z170mx-Gaming 5), but I was hoping someone here might have experienced otherwise as I'm not sure how Gigabyte handles warranty claims and I dread going weeks without my only PC.
Here's the Minidump logs from just today. I have several days worth exported, and if they would help find a solution, I'd gladly provide them:
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-28RNO0O
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: Z170MX-Gaming 5, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17131442176 bytes total
(RAM: Corsair Vengeance LPX 16GB (2x8GB) DDR4 DRAM 2400MHz C14 Memory Kit - Black (CMK16GX4M2A2400C14))
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Wed 6/20/2018 9:01:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062018-9046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0xC1 (0xFFFF828985864F40, 0xFFFF828985864681, 0x7340C0, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
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 Wed 6/20/2018 8:54:55 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062018-9125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0xC1 (0xFFFFF7011189CF40, 0xFFFFF7011189C281, 0xE340C0, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
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 Wed 6/20/2018 7:19:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062018-10562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80123D08AA3, 0xFFFFFA0A298B6C60, 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 Wed 6/20/2018 7:08:33 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062018-9031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0xC1 (0xFFFFAD8778B0CE00, 0xFFFFAD8778B0C181, 0xE7C200, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
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 Wed 6/20/2018 7:06:47 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062018-8343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0xC1 (0xFFFFB08742790F40, 0xFFFFB08742790A41, 0x7340C0, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
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.
I have been using Tomshardware to troubleshoot various problems in the past, but this is my first time posting. I'm a computer rookie, so if I need to provide any further details, I'd be happy to do so as long as I understand how.
So, these BSOD's have been an ongoing pain for the past month. I was running on a stable Win7 machine, with no new software or driver updates or installs. After days of troubleshooting various driver fixes and updates, I decided the only good method to rule out drivers would be to upgrade to Win10.
Within the first hour of Win10 install, I got another BSOD. At first I thought it was because I was still installing updates and drivers, etc.
Kept getting BSODs.
Ran Prime95 on several different occasions. First time, I had 2 thread errors. Next time, it ran clean for 20 mins. 3rd time I had errors on 2 different threads. And 4th time, ran 30 mins with no errors.
Memory tests showed the same thing. Ran windows mem diagnostic twice (with the enhanced test) and it showed some faults. Ran it again and no faults.
Ran FurMark to test GPU. First time, BSOD'ed within 30 seconds. 2nd, 3rd and 4th time, ran for several minutes with no issue.
The Intel Proces Diagnostic has shown mix results of faulty CPU as well as several clean runs.
I'm suspecting this to be a motherboard problem (Gigabyte Z170mx-Gaming 5), but I was hoping someone here might have experienced otherwise as I'm not sure how Gigabyte handles warranty claims and I dread going weeks without my only PC.
Here's the Minidump logs from just today. I have several days worth exported, and if they would help find a solution, I'd gladly provide them:
System Information (local)
--------------------------------------------------------------------------------
Computer name: DESKTOP-28RNO0O
Windows version: Windows 10 , 10.0, build: 17134
Windows dir: C:\Windows
Hardware: Z170MX-Gaming 5, Gigabyte Technology Co., Ltd.
CPU: GenuineIntel Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz Intel586, level: 6
8 logical processors, active mask: 255
RAM: 17131442176 bytes total
(RAM: Corsair Vengeance LPX 16GB (2x8GB) DDR4 DRAM 2400MHz C14 Memory Kit - Black (CMK16GX4M2A2400C14))
--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------
Crash dumps are enabled on your computer. This system is not configured for complete or automatic crash dumps. For best results, configure your system to write out complete or automatic crash dumps. Select Tools->Crash Dump Configuration from the main menu to configure your system to write out complete memory dumps.
Crash dump directories:
C:\Windows
C:\Windows\Minidump
On Wed 6/20/2018 9:01:06 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062018-9046-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0xC1 (0xFFFF828985864F40, 0xFFFF828985864681, 0x7340C0, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
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 Wed 6/20/2018 8:54:55 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062018-9125-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0xC1 (0xFFFFF7011189CF40, 0xFFFFF7011189C281, 0xE340C0, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
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 Wed 6/20/2018 7:19:24 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062018-10562-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0x3B (0xC0000005, 0xFFFFF80123D08AA3, 0xFFFFFA0A298B6C60, 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 Wed 6/20/2018 7:08:33 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062018-9031-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0xC1 (0xFFFFAD8778B0CE00, 0xFFFFAD8778B0C181, 0xE7C200, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
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 Wed 6/20/2018 7:06:47 PM your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\062018-8343-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x198330)
Bugcheck code: 0xC1 (0xFFFFB08742790F40, 0xFFFFB08742790A41, 0x7340C0, 0x32)
Error: SPECIAL_POOL_DETECTED_MEMORY_CORRUPTION
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 the driver wrote to an invalid section of the special pool.
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.
Facebook
Twitter
Instagram