[BSOD (BAD_POOL_CALLER) / network]

Since my first post I also added the latest Malwarebytes exclusions to Bitdefender which I found here:

https://support.malwarebytes.com/docs/DOC-1123

Problem continues (BSOD in my attachment).

[BSOD (BAD_POOL_CALLER) / network]

@ Vlad

Many thanks for your respone.

A search for memory.dmp in C:\Windows shows zero results (display of hidden/system files is enabled). I regularly run CCleaner which also cleans dump files, but I had a fresh BSOD an hour ago after which I did not run CCleaner yet.

Attached is the latest dump file and an older one which I saved. I've also included some older BlueScreenView logs if this of any help.

 

dump files & logs.zip

[BSOD (BAD_POOL_CALLER) / network]

I'm having regular BSOD (BAD_POOL_CALLER) on my main computer since end of Jan 2018. I'm running Malwarebytes Premium 3.4.5 (the problem started on an earlier version) and Bitdefender Total Security 2018, and if I recall correctly both programs had medium updates just before the problem started.

 

Bug Check Code      : 0x000000c2

Crash Address         : ntoskrnl.exe+1640e0

Caused By Driver     : fwpkclnt.sys

Caused By Address : fwpkclnt.sys+1244e

File Description       : FWP/IPsec Kernel-Mode API

 

While Malwarebytes is not mentioned in the logs I found out that

- the problem only occurs when a second or third computer (both running Malwarebytes free without live protection & Bitdefender 2018) is connected to my network while Malwarebytes Premium is active on my main computer with all four protection modes enabled. It appears that Malwarebytes Premium tries to scan the other computers and then hangs (other comps are fine).

- the BSOD never happens when Malwarebytes is completely shut down on my main computer

- I cannot solve the problem by adding my other network computers to Malwarebytes exclusions, because my main comp will always freeze before reaching that point.

 

If it's not a Malwarebyes-only problem, my guess is that it might be a compatibility issue between MBAM's llive protection and Bitdefender. I've had these issues in 2016 and solved them by adding the following MBAW exclusions to Bitdefender recommended in this forum (plus new exe's contained in later versions):

 

See diagnosis attached.

mb-check-results.zip