Kaiwen

Calm down. I didn't answer to Maurice because I am working and I don't have the time to do the log file etc. I am not in USA too but in Europe so it's not the same time here. I'll do the report after. If you want to ban/ignore me in your users folder, let's go. I don't know who you are, it makes me neither hot nor cold.

I already updated all drivers. This BSOD occurs on many computers and motherboards when Bitdefender and Mbam coexist (all drivers updates or not). It's not a network driver problem. The french Bitdefender technician said that Bitdefender tech assist strongly advises customers to do not install Malwarebytes or another AV solution with Bitdefender... He said that it's written on the manual. So, I asked him when the software will be updated to erase automatically Malwarebytes Premium if it's not compatible 'cause if it is not compatible >> No discussion ! I can't obtain an official answer...

Another motherboard ASUS Z77 : This is the proof that a BSOD is not always correct on the paper. On Thu 14/04/2016 07:31:06 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\041416-14593-01.dmp uptime: 3 days, 15:35:23 This was probably caused by the following module: netwbw02.sys (Netwbw02+0xA2820) Bugcheck code: 0xC2 (0x7, 0x126C, 0x0, 0xFFFFE0012B4B25F8) Error: BAD_POOL_CALLER file path: C:\WINDOWS\system32\drivers\netwbw02.sys product: Intel® Wireless WiFi Link Adapter company: Intel Corporation description: Intel® Wireless WiFi Link Driver 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: netwbw02.sys (Intel® Wireless WiFi Link Driver, Intel Corporation). Google query: Intel Corporation BAD_POOL_CALLER On Thu 14/04/2016 07:31:06 GMT your computer crashed crash dump file: C:\WINDOWS\memory.dmp uptime: 3 days, 15:35:23 This was probably caused by the following module: netwbw02.sys (Netwbw02+0xA2820) Bugcheck code: 0xC2 (0x7, 0x126C, 0x0, 0xFFFFE0012B4B25F8) Error: BAD_POOL_CALLER file path: C:\WINDOWS\system32\drivers\netwbw02.sys product: Intel® Wireless WiFi Link Adapter company: Intel Corporation description: Intel® Wireless WiFi Link Driver 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: netwbw02.sys (Intel® Wireless WiFi Link Driver, Intel Corporation). Google query: Intel Corporation BAD_POOL_CALLER

With WhoCrashed Pro : On Sun 10/04/2016 15:54:38 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\041016-12500-01.dmp uptime: 08:31:57 This was probably caused by the following module: mwac.sys (mwac+0x61B8) Bugcheck code: 0xC2 (0x7, 0x126C, 0x0, 0xFFFFE00089D060D8) 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 Sun 10/04/2016 07:21:35 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\041016-15171-01.dmp uptime: 9 days, 14:15:14 This was probably caused by the following module: mwac.sys (mwac+0x6135) Bugcheck code: 0x19 (0x20, 0xFFFFE001B0A490D0, 0xFFFFE001B0A490F0, 0x402000D) 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 30/03/2016 20:08:25 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\033116-14015-01.dmp uptime: 08:56:20 This was probably caused by the following module: mwac.sys (mwac+0x90BF) Bugcheck code: 0xC2 (0x7, 0x126C, 0x0, 0xFFFFE00004015778) 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 Sat 26/03/2016 09:42:32 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\032616-13687-01.dmp uptime: 1 day, 02:23:56 This was probably caused by the following module: mwac.sys (mwac+0x90BF) Bugcheck code: 0xC2 (0x7, 0x126C, 0x0, 0xFFFFE001F531F818) 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 Fri 25/03/2016 07:17:30 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\032516-17500-01.dmp uptime: 3 days, 12:20:09 This was probably caused by the following module: mwac.sys (mwac+0x90BF) Bugcheck code: 0xC2 (0x7, 0x126C, 0x0, 0xFFFFE000B6448688) 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 21/03/2016 18:56:17 GMT your computer crashed crash dump file: C:\WINDOWS\Minidump\032116-14500-01.dmp uptime: 01:23:55 This was probably caused by the following module: mwac.sys (mwac+0x61B8) Bugcheck code: 0xC2 (0x7, 0x126C, 0x1, 0xFFFFE0006A1BBF38) 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

Always on Z97 PRO GAMER, new BSOD "BAD POOL HEADER" this time without Anti-Exploit, with Bitdefender and Malwarebytes (without Malicious Website Protection). Now, I am trying to uninstall Bitdefender and let Malwarebytes alone. See you soon !

One computer Z97 PRO GAMER : BSOD "BAD POOL CALLER" without Malicious Website Protection (ndis.sys). I uninstalled Mbam. Is it possible that Mbam Anti-Exploit Premium and Mbam Premium cause BSOD ? Anti-Exploit is installed on this computer. I can try to uninstall it and reinstall Mbam Premium alone with Bitdefender to see but I think there is no difference with the crash.

That's why I said it's a Mbam/Bitdefender incompatibily/BSOD even if BlueScreenView shown ndis.sys, tcpip.sys or netio.sys in my case. I am trying on two computer without the Malicious Protection, no BSOD actually. Wait & see.

First, I am trying without Malicious Web Protection, after I'll try Maurice's solution. Have a nice week-end.

Understood but there is no problem one month ago... :'( So, something changed and I remember that one month ago Malwarebytes was automatically updated.

Oh sorry, I forget to say that I've report the BSOD's problem to Bitdefender forum (french section) : https://forum.bitdefender.com/index.php?showtopic=69293

I will try to stop the Malicious Website Protection from Malwarebytes. I think that's is the problem. I will report you the result in few hours/days.

It's just a conflict between Bitdefender 2016 and last Mbam. I tried to uninstall Bitdefender, just use Mbam (with Windows Defender) : no BSOD. I tried to install Avira : no BSOD. I reinstalled Bitdefender 2016 : BSOD BAD POOL CALLER ndis.sys on Firefox (on Asus M2N68-AM plus, no Intel chipset, no BIOS UEFI !) Now, I don't want to know if the faulty code is in Mbam or Bitdefender. Maybe it's a Bitdefender problem but, the fact is when Mbam is not present with Bitdefender : no BSOD anymore. I am not here to play beta tester. You have some volontaries to do that and I think you can work with Bitdefender's devs to word on the problem. I just wanted to report this actual incompatibility on many computers/motherboards and this serious BSOD who can do a crash BIOS UEFI. 20 years that I am working on computer repair, chasing BSOD, I never saw a BSOD like this.

It's not a question of refund and It's too easy to reject the fault on Gigabyte or Asus. I repeat, I never installed Gigabyte or Asus' apps on computers and It's not a H/Z87/97's problem. On older motherboard (for example the computer that I use to write this message is a Asus P7P55D-EVO), it's exactly the same thing, BAD POOL CALLER/HEADER when Mbam and Bitdefender co-exist and when I am manipulating tabs on Firefox or Chrome. First, I thought about a plugin problem like Flash Player. I already tried to uninstall it and to use Chrome without Flash or any plugin. Result : BAD POOL CALLER (ndis.sys, netio or tcpip.sys). So, I just uninstall Mbam and all is going ok, no BSOD anymore. On another computer, I tried to change the motherboard Gigabyte GA-Z87X-D3H to a Asus Z97-PRO GAMER, I've "clean reinstalled" W10x 64 after the motherboard switch. I've just up to dated all drivers properly, installed Bitdefender first, Mbam after, Firefox without any plugin and tried to navigate... BSOD BAD POOL. I tried to uninstall Mbam, no BSOD. All RAM are OK without Memtest and Memtest86+ and all motherboard's BIOS were updated. I tried without PCI GPU, just with Intel GMA (BSOD too). And, sometimes, when a BSOD comes : "Sorry your computer... BAD POOL CALLER (0%)" > big freeze. Must stop the computer with I/O button and the BIOS doesn't want to boot anymore. The only way is to force the backup BIOS to start if a clear CMOS can't reboot the motherboard properly and reflash BIOS. Cool BSOD !

Thanks for the answer but without Mbam there is no problem on Z87, Z97 or Z170 GA or Asus motherboard, same thing on old P55. I have not installed Asus or Gigabyte apps. Only fresh w10, bitdef, mbam premium, firefox to get bsod. Many of m'y customers who use Mbam and Bitdefender encounter this issue. About the crash bios, it's not systematic.

Dear Maurice, I don't want to play beta tester with log file, etc. I have no time for this. It's very simple to reproduce the BSOD sequence because it's an internal error from Malwarebytes I think. I already did the correct diagnostic on multiple computers. It's my job to repair them. At my store, I've obtained these BSOD BAD POOL CALLER on different motheboards when Malwarebyte and Bitdefender co-habit : Gigabyte GA-Z77-D3H, GA-Z87X-D3H, GA-Z97P-D3, GA-Z170-HD3, Asus P7P55D-EVO, Asus Z97-PRO GAMER, Z97P-D3. All these motherboard's BIOS crashed after a certain number of BSOD BAD POOL HEADER/CALLER ! I have to clear CMOS, reinsert RAM and reflash BIOS to recover it. It's a very huge bug, not a simple BSOD, that's why I am talking about incompatibility between for software Mbam Premium last version and Bitdefender 2016. If I uninstall Malwarebytes, BSOD disappears. I repeat, I already tried on a brand new motherboard to do a clean install of Windows 10 Threshold 2 x64, update all drivers properly (or not, don't change anything !), just install Bitdefender, Malwarebytes, Firefox or Chrome and navigate with tabs... Result : BSOD. So, no old antivirus installed, no upgrade. Just a new installation or a first install. On a old Asus motherboard with Windows 7 x64, same problem. Thanks.

This BSOD from MBAM can crash the BIOS UEFI. It's an emergency to reproduce it and correct it quickly. To reproduce it on Gigabyte or Asus motherboards (Z77, Z87, Z97, Z107 - tested here). Just reinstall properly W10 X64, update all drivers. Install BD2016 (IS or Total Sec.), install the last MBAM version. Install Firefox or Chrome, manipulate tabs and the BSOD should appear randomly : BAD POOL CALLER/HEADER : mwac.sys, ndis.sys, netio.sys, tcpip.sys (crashed). If the BIOS crashed, clear CMOS, eject CMOS, eject RAM, reinsert RAM and if the BIOS is corrupted, reflash it to recever the boot sequence.

Still getting the BSOD after a clean reinstall of W10 Threshold 2 X64. Just reinstall W10 x64, update all driver. Install Bitdefender TS 2016, Install MBAM Premium (last version) > On Firefox/Chrome/Edge when manipulating tabs : BSOD BAD POOL CALLER or sometimes HEADER > ndis.sys, netio.sys or tcpip.sys just crashed. It's an internal incompatibilty between BD2016 and the new MBAM, vice versa. It's easy to reproduce the bug. I had it on multiple computers. This bug can occurs BIOS crash. Only way to recover : Clear CMOS and reflash last BIOS. What the hell ?! 1 month, no update, no solution... Thanks Mbam !

On five different computers, many bsod randomly come on Internet browser with Edge, Firefox or Chrome when trying to open tabs : Bad Pool Caller (ndis.sys, netio.sys or tcpip.sys). Sometimes, on Gigabyte motherboard the Bios crashed and I've to clear cmos and reflash to recover this censoredin' mbam's bug !This BSOD appeared one month ago with the new mbam version.Please, correct the bug quickly. It seems to be an incompatibily with Bitdefender 2016. Best Regards, Kaiwen.