Baqd Pool Error is Back

[DanFlak]

With the older version of Malwarebytes, I had to turn off real time protection because the incompatibility between MWB and Windows Defender (Window 10) was causing repeated BSOD Bad Pool Errors. I upgraded to 3.0 about two months ago. Everything ran fine for two whole months. This morning I had 2 BSOD Bad Pool Errors within minutes of launching my browser.

I've turned off my real time protection in hopes that I can use my computer.

Why is this happening? What is the fix? And why am I paying for protection I can't use?

[Porthos]

2 hours ago, DanFlak said:

With the older version of Malwarebytes, I had to turn off real time protection because the incompatibility between MWB and Windows Defender (Window 10) was causing repeated BSOD Bad Pool Errors. I upgraded to 3.0 about two months ago. Everything ran fine for two whole months. This morning I had 2 BSOD Bad Pool Errors within minutes of launching my browser.

I've turned off my real time protection in hopes that I can use my computer.

Why is this happening? What is the fix? And why am I paying for protection I can't use?

Can you grab some information please so we can try to figure out what's going on?

1. Please download Farbar Recovery Scan Tool from here http://www.bleepingcomputer.com/download/farbar-recovery-scan-tool/ and save it to your desktop.
   Note: You need to run the version compatible with your system.
   **After you click the Download Now 64-bit, or the Download Now 32-bit, another page will open — DO NOT CLICK ANY ADDITIONAL 'download now' buttons, just wait and look toward the bottom of your browser for the option to Run or Save. Click Save.
2. Double-click to run it. When the tool opens click Yes to the disclaimer.
   Note: If you are prompted by Windows SmartScreen, click More info followed by Run anyway.
3. Click the Scan button.
4. When the scan has finished, it will save 2 logs  in the same directory the tool was run from.  Please attach the following logs:
   Addition.txt
   FRST.txt 
5. Make sure Malwarebytes it closed by right clicking the system tray icon and choosing Quit Malwarebytes
6. Open up Malwarebytes
7. Go to Settings -> Application
8. Find the Event Log Notification setting and turn it on
9. Go to Settings -> Protection
10. Try to turn on Web Protection
11. Wait 2-3 minutes while it sticks in Starting...
12. Zip up the following folder: C:\ProgramData\Malwarebytes\MBAMService\logs by right clicking the logs folder and choosing Send To -> Compressed (Zipped) folder
13. This will create a zip file on your desktop
14. Please upload the zip file and the two log files from step 4 above to your reply

 

[Porthos]

23 minutes ago, Castoff said:

+1 this. As described by the topic creator, this same issue that I experienced regularly around December is back with an absolute vengeance - it's never consistent, sometimes the system will behave itself for a good while, other times it will produce a BAD_POOL_HEADER BSOD shortly after the system starts and Chrome is launched. I've attached my logs below, on this occasion I'd been using Chrome to browse random sites for a while without encountering the BAD_POOL_HEADER error. I then launched Steam, signed into the Steam Community and launched Torment: Tides of Numenera, upon hitting the title screen for that game, the BAD_POOL_HEADER error hit (Chrome was still running in the background). 

Using Windows 10 64bit, which is up to date with the latest updates in conjunction with Malwarebytes 3.0 Premium and Bitdefender Total Security.

 

Malwarebytes version: 3.0.6.1469

Component Package version: 1.0.75

Update Package version : 1.0.0

 

From a WhoCrashed report:

On Tue 07/03/2017 16:55:39 your computer crashed
crash dump file: C:\WINDOWS\Minidump\030717-17468-01.dmp
This was probably caused by the following module: tcpip.sys (tcpip+0x15F665) 
Bugcheck code: 0x19 (0x20, 0xFFFFA504BBE1A170, 0xFFFFA504BBE1A190, 0x4020017)
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 Tue 07/03/2017 16:55:39 your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: mwac.sys (mwac+0x6C8A) 
Bugcheck code: 0x19 (0x20, 0xFFFFA504BBE1A170, 0xFFFFA504BBE1A190, 0x4020017)
Error: BAD_POOL_HEADER
file path: C:\WINDOWS\system32\drivers\mwac.sys
product: Malwarebytes Web Protection
company: Malwarebytes
description: Malwarebytes Web Protection
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 Protection, Malwarebytes). 
Google query: Malwarebytes BAD_POOL_HEADER

 

Logs are attached, for now I've no choice but to disable the Web Protection in Malwarebytes, which I'm not too happy about but random BSODs are unacceptable.

 

Addition.txt

FRST.txt

logs.zip

I have asked this topic be moved to its own topic. Keep in that topic when created, Thanks.