Windows 10: BSOD-0xC2: BAD_POOL_CALLER after running dgreadiness_v3.6 tool

BSOD-0xC2: BAD_POOL_CALLER after running dgreadiness_v3.6 tool.

No matter how it is set, dump file cannot be generated.

:)

 

FWPKCLNT.SYS throwing an 0xC2 bsod

Hello there.

It's pretty normal to ask for what to do or stuff, but pretty damn weird to talk about the causes.

So, I've found a cool BitTorrent Bundle (yep, that's a thing) and wanted to download via uTorrent.

Wanted to download it to listen to it (it was a music related bundle).

Started downloading and after few seconds, no matter what I've done or what I haven't done, I've got a BAD_POOL_CALLER 0xC2 BSOD caused by FWPKCLNT.sys

I'm not sure what I've done wrong, I've got Win10 licensed as an update to OEM Win8.1 on Asus X550D laptop.

MiniDumps (packed as zip file): http://1drv.ms/1KQoHZU

 

Crazy BSOD Loop. Genuis Needed.

Hi,



Thank you for writing to Microsoft Community Forums.



Method 1:

• This issue seems to be more related to hardware, please go through
  
  CRITICAL_PROCESS_DIED and
  BAD_POOL_CALLER and check for the resolution steps.
  

If you could contact your system manufacturer and run a hardware diagnostic that will help you out with this issue.



Method 2:

• You can also refer to this
  suggestion by Krishna Prasobh V posted on September 4.
  

Hope it helps.



Amit Sunar

Microsoft Community - Moderator

 

BSOD - BAD_POOL_CALLER

Hi Gerry,

Do not worry any further as I have resolved the problem.

I downloaded another program called WhoCrashed which was able to analyse the MEMORY.DMP file which told me the below. As this only appears to happen during surfing the web and my BAD_POOL_CALLERS had issues with the TCP drivers within Windows, it makes perfect
sense. I have Googled the issue and found that the Killer Networking drivers are simply rubbish, to run a full uninstall, and just install the drivers without the software suite. Should this continue to happen again, I will try uninstalling the drivers, disabling
the device, and use my Intel NIC as I have two ethernet ports on my motherboard (EVGA Z270 Classified K). It's annoyed me a little as I have lost my overclock settings now after running a CMOS so I will have to play around with those over the weekend but at
least it's not a hardware issue and I can resolve it over time

I apologise for wasting your time as it could have been used helping someone else.

Thank you!

- Mitch

On Fri 17/03/2017 00:28:51 your computer crashed

crash dump file: C:\Windows\memory.dmp

This was probably caused by the following module: e2xw1.sys (e2xw10x64+0x892D)

Bugcheck code: 0xC2 (0x7, 0x0, 0x3, 0xFFFFB088BDD203D8)

Error: BAD_POOL_CALLER

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: e2xw1.sys .

Google query: e2xw1.sys BAD_POOL_CALLER