BSOD Happens Frequently - Bad Pool Header

Usually when I am using my pc for a prolonged period of time, I get a BSOD with a Bad pool header message almost everytime. Below is my "Who Crashed" Report. Any help is strongly appreciated.



--------------------------------------------------------------------------------
System Information (local)
--------------------------------------------------------------------------------

windows version: Windows 8.1 , 6.2, build: 9200
windows dir: C:\Windows
Hardware: ASRock, H97M Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-4670K CPU @ 3.40GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 8522113024 total

--------------------------------------------------------------------------------
Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dump directory: C:\Windows\Minidump

Crash dumps are enabled on your computer.

On Sat 4/25/2015 3:54:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042415-3906-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x14B770)
Bugcheck code: 0x19 (0xD, 0xFFFFD000226EE290, 0xFFFFF80181BF5770, 0xEBC0487F8F683539)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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.
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 4/25/2015 3:54:36 AM GMT your computer crashed
crash dump file: C:\Windows\memory.dmp
This was probably caused by the following module: npfs.sys (Npfs+0xB872)
Bugcheck code: 0x19 (0xD, 0xFFFFD000226EE290, 0xFFFFF80181BF5770, 0xEBC0487F8F683539)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\npfs.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NPFS Driver
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.
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 Thu 4/23/2015 4:08:51 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\042315-3828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
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 Sun 4/19/2015 4:13:39 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041915-3843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x19 (0xE, 0xFFFFD00024448290, 0x0, 0x35E22E8230843C5D)
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.
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 4/17/2015 2:18:36 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041615-3843-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x153FA0)
Bugcheck code: 0x19 (0xD, 0xFFFFD00023C51290, 0x0, 0x9FFCBAFEA881861)
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.
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 4/13/2015 2:00:01 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\041215-3875-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x154B78)
Bugcheck code: 0x19 (0xD, 0xFFFFD00026F38230, 0xFFFFF80001179B78, 0x8661C8431CB246C7)
Error: BAD_POOL_HEADER
file path: C:\Windows\system32\drivers\tcpip.sys
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: TCP/IP Driver
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.
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 Tue 4/7/2015 3:32:26 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040615-3718-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x19 (0xD, 0xFFFFD0002947F230, 0xFFFFF8010BF1430A, 0xAA0A3D9C5839691A)
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.
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 4/4/2015 3:52:23 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\040315-3828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x14DCA0)
Bugcheck code: 0x19 (0xD, 0xFFFFD000273A6230, 0xFFFFE00007DCEA90, 0x9DB64CE78073DF06)
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.
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 3/12/2015 12:56:00 AM GMT your computer crashed
crash dump file: C:\Windows\Minidump\031115-6750-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
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 Sun 3/8/2015 10:22:25 PM GMT your computer crashed
crash dump file: C:\Windows\Minidump\030815-3890-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x1500A0)
Bugcheck code: 0x133 (0x1, 0x1E00, 0x0, 0x0)
Error: DPC_WATCHDOG_VIOLATION
file path: C:\Windows\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL or above.
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.

 

Hi wilha, Welcome to WindowsBBS. Have you recently installed software or drivers to your system? Have you tried a System Restore to a time before your troubles began? Neil.

 

Well its been happening for the last couple months and I have tried updating all of the drivers and using windows update to get the most recent updates, but to no avail. I dont have restore points so I can revert back.

Thanks

 

PHP:

I dont have restore points so I can revert back.


'WOOPS'
Can only suggest a basic start with minimal hardware/devices connected and see how it performs. Neil.

 

Well I will try that as soon as I can and get back to you. Thanks