Windows 10: BSOD "BAD_POOL_CALLER" caused by "fwpkclnt.sys"

Hello

Recently my PC which is 1 month old started getting BSOD "BAD_POOL_CALLER" I tried to do something ; i check my RAM, updated windows and all drivers but it didn't help.

Here is link to onedrive with 3 minidump files caused by the same file.

https://1drv.ms/u/s!Ar-GPjtOCiRMizd_gWzAQAwaZCrQ?e=1lFF5c


I would gladly appreciate any help.

:)

 

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

 

Bad_Pool_Caller


I have read quite a few "Bad_Pool_Caller" posts and none that I've read have been any help. It really is getting frustrating; as many as three times in a day. I've tried safe mode, but couldn't figure anything from that. In fact as I write here I'm expecting a crash. Jeez this really is a backward step. I don't remember windows 3 crashing like this with no explanation as to what is causing the crash. I have a Dell Studio 1747 laptop (six years old now). I installed a 240GB SSD drive a week or so ago. I can't remember if I had these BSOD's with the old drive. I've attached the suggested system file from previous posts. I notice ads to repair this problem, but hesitate to try them; any suggestions on that.

Thanks, Allan

 

BAD_POOL_CALLER x000000c2 bsod in WIndows 10

Hello Ali,

We realize the inconvenience you are experiencing with error
BAD_POOL_CALLER x000000c2 in Windows 10. We will certainly help you.

The BAD_POOL_CALLER bug check has a value of 0x000000C2. This indicates that the current thread is making a bad pool request.

Blue screens (BSOD) is mostly occur due to hardware and sometimes due to incompatible software. In a lot of cases it is a corrupted driver or a driver conflict. The most common causes of blue screens are overheating, faulty RAM, video card problem
and BIOS.

We suggest you to follow the steps from the link below and check if it helps:

Troubleshoot blue screen errors

Let us know the status of the issue. We will be happy to assist you further.

Thank you.