tcpip.sys & ntoskrnl.exe Bad-pool-caller Bad-pool-header

[dragonkiller]

Hello I'm receiving this error everyday. I have ran both memtest86 and windows memtest program None have found error's. I have downloaded blue screen viewer and it told me the 2 errors that keep BSOD which is ntoskrnl.exe and tcpip.sys Reading the forums I have downloaded Whocrashed. Which I never used before and im reading that it is being caused by malwarebytes. What should I do. I kept thinking it is bad ram.
This is what Whocrashed reported.

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

Computer name: DESKTOP-MGL36PA
Windows version: Windows 10 , 10.0, build: 10586
Windows dir: C:\WINDOWS
Hardware: ASRock, H97 Pro4
CPU: GenuineIntel Intel(R) Core(TM) i5-4460 CPU @ 3.20GHz Intel586, level: 6
4 logical processors, active mask: 15
RAM: 17111662592 bytes total




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

Crash dump directory: C:\WINDOWS\Minidump

Crash dumps are enabled on your computer.

On Wed 5/4/2016 2:12:15 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050416-29234-01.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6135)
Bugcheck code: 0x19 (0x20, 0xFFFFE00117CA02B0, 0xFFFFE00117CA02D0, 0x402000E)
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.
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 Wed 5/4/2016 2:12:15 PM GMT 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, 0xFFFFE00117CA02B0, 0xFFFFE00117CA02D0, 0x402000E)
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.
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 Wed 5/4/2016 2:05:54 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050416-24421-01.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6135)
Bugcheck code: 0x19 (0x20, 0xFFFFE0011C517DE0, 0xFFFFE0011C517E00, 0x402000C)
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.
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 Wed 5/4/2016 11:33:30 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050416-22937-01.dmp
This was probably caused by the following module: mwac.sys (mwac+0x61B8)
Bugcheck code: 0xC2 (0x99, 0xFFFFE001D8F93258, 0x0, 0x0)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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_CALLER



On Wed 5/4/2016 2:48:29 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050316-23031-01.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6135)
Bugcheck code: 0x19 (0x20, 0xFFFFE001B8BBFEB0, 0xFFFFE001B8BBFED0, 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.
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 5/3/2016 2:16:15 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050316-27937-01.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6135)
Bugcheck code: 0x19 (0x20, 0xFFFFE0014D08EB30, 0xFFFFE0014D08EB50, 0x4020017)
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.
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 5/3/2016 9:16:03 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050316-24218-01.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6135)
Bugcheck code: 0x19 (0x20, 0xFFFFE001AF7A5A30, 0xFFFFE001AF7A5A50, 0x4020017)
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.
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 Mon 5/2/2016 5:58:47 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050216-22625-01.dmp
This was probably caused by the following module: mwac.sys (mwac+0x90BF)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x0, 0xFFFFE000CED4C2C8)
Error: BAD_POOL_CALLER
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 the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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_CALLER



On Mon 5/2/2016 1:43:28 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050116-25140-01.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6135)
Bugcheck code: 0x19 (0x20, 0xFFFFE0003A81A170, 0xFFFFE0003A81A190, 0x4020017)
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.
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 Mon 5/2/2016 1:10:38 AM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\050116-24015-01.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6135)
Bugcheck code: 0x19 (0x20, 0xFFFFE0002C20E320, 0xFFFFE0002C20E340, 0x4020010)
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.
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





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

23 crash dumps have been found and analyzed. Only 10 are included in this report. A third party driver has been identified to be causing system crashes on your computer. It is strongly suggested that you check for updates for these drivers on their company websites. Click on the links below to search with Google for updates for these drivers:

mwac.sys (Malwarebytes Web Access Control, Malwarebytes Corporation)

If no updates for these drivers are available, try searching with Google on the names of these drivers in combination with the errors that have been reported for these drivers. Include the brand and model name of your computer as well in the query. This often yields interesting results from discussions on the web by users who have been experiencing similar problems.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

The above part right here is what im lost at. Do i have to uninstall malwarebytes I have updated it and issue still exsit.

 

[viveknayyar007]

Hello dragonkiller

Can you please confirm since when you are facing the issue?

You may want to remove Malwarebytes from the computer.

If this doesn't help, Restoring Windows 10 to an Earlier State, i.e. when the PC worked fine might help.

Feel free to report back if further assistance is needed.

Cheers!!

 

[dragonkiller]

Hello dragonkiller

Can you please confirm since when you are facing the issue?

You may want to remove Malwarebytes from the computer.

If this doesn't help, Restoring Windows 10 to an Earlier State, i.e. when the PC worked fine might help.

Feel free to report back if further assistance is needed.

Cheers!!

To be honest Its been about 2 months now. I have wiped windows 10 and It kept doing it. I kept thinking bad ram till I been reading forums here and asking people I know online. I just re installed malwarebytes according to google thread that they posted. If it happens again today Im going to just uninstall it and See if that changes anything.

 

[johnbl]

Most likely cause will be a old network driver. You might want to put your memory dump file from c:\windows\minidump directory
on a server like microsoft one driver, share it for public access and post a link.

Or update your network driver. if you have a USB wireless network device you often have to update the BIOS, the CPU chipset driver, any usb 3.0 driver as well as the usb wireless driver.

Note: old network drivers tend to break streaming software and virus scanners. People often just assume a bugcheck with a virus scanner in the trace means it is caused by the virus scanner when in fact it may not be. Buggy filter drivers and old network driver often turn out to the the root cause.