- Jul 10, 2016
- 3
- 0
- 1,510
I've gotten 2 BSOD, both BAD_POOL_HEADER. I downloaded BlueScreenView and both of those BSOD were "Caused by Driver: tcpip.sys"
I justed downloaded WhoCrashed and analyzed this and got this:
On Sat 10/15/2016 2:44:23 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\101516-32515-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x15F505)
Bugcheck code: 0x19 (0x20, 0xFFFFA90F41908050, 0xFFFFA90F41908070, 0x4020005)
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. This problem might also be caused because of overheating (thermal issue).
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 10/15/2016 2:44:23 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6135)
Bugcheck code: 0x19 (0x20, 0xFFFFA90F41908050, 0xFFFFA90F41908070, 0x4020005)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\mwac.sys
product: Malwarebytes Web Access Control
company: Malwarebytes Corporation
description: Malwarebytes Web Access Control
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation).
Google query: Malwarebytes Corporation BAD_POOL_HEADER
On Tue 10/11/2016 4:57:25 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\101116-30328-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x15F525)
Bugcheck code: 0x19 (0x20, 0xFFFF9C87234B92E0, 0xFFFF9C87234B9300, 0x4020008)
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. This problem might also be caused because of overheating (thermal issue).
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.
I justed downloaded WhoCrashed and analyzed this and got this:
On Sat 10/15/2016 2:44:23 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\101516-32515-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x15F505)
Bugcheck code: 0x19 (0x20, 0xFFFFA90F41908050, 0xFFFFA90F41908070, 0x4020005)
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. This problem might also be caused because of overheating (thermal issue).
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 10/15/2016 2:44:23 PM your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6135)
Bugcheck code: 0x19 (0x20, 0xFFFFA90F41908050, 0xFFFFA90F41908070, 0x4020005)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\mwac.sys
product: Malwarebytes Web Access Control
company: Malwarebytes Corporation
description: Malwarebytes Web Access Control
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).
A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation).
Google query: Malwarebytes Corporation BAD_POOL_HEADER
On Tue 10/11/2016 4:57:25 PM your computer crashed
crash dump file: C:\WINDOWS\Minidump\101116-30328-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x15F525)
Bugcheck code: 0x19 (0x20, 0xFFFF9C87234B92E0, 0xFFFF9C87234B9300, 0x4020008)
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. This problem might also be caused because of overheating (thermal issue).
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.
Facebook
Twitter
Instagram