BAD_POOL_CALLER on fresh Windows 10 install, with all drivers updated

[bernas]

Hello,

I get a constant BAD_POOL_CALLER error on my Desktop, that makes the PC reboot.

I made a fresh Windows 10 Install, made a hard drive format and updated every drivers from the manufacturer's site.

The error still happens.

This is the kind of blue screen that I get:


The text is written in Portuguese, and it says: "There was a problem with your PC and a reboot is necessary. Some information about this error is beeing collected and after that the PC will automatically be rebooted. (80% done)
For more information, look later for this error online: BAD_POOL_CALLER"

My desktop config looks like this:

SSD Crucial MX100 256GB
SSD Samsung 2.5" 850 Pro 512G
Processor Intel Core i7-4790K 4GHz 8MB Sk1150
Water Cooler Corsair Hydro Series H100i
Graphic Card Asus GTX980-4GD5
Motherboard Asus Maximus VII Hero
Case Corsair Obsidian 550D
Power Supply Corsair RM750W
Memory Kingston HyperX Savage DDR3-2400MHz 2x8GB
Monitor Asus 27" 144Hz VG278HE
Sound Card Asus Xonar Essence STX II 7.1
Headphones Sennheiser Momentum
Keyboard Asus Echelon PT
Mouse Razer DeathAdder 2013 4G 6400DPI

This build has aproximaly 2 years since it was bought.

Here is my .dmp file, which I uploaded on the .zip form to DropBox:
https://www.dropbox.com/s/7ddf8drr3ronu38/060916-5687-01.zip?dl=0

Could you help me correct this error, please?

 

[Laptop_Nerd]

Hi,

Please do try these troubleshooting steps that I suggested to others that may help.
- First is to run Windows Update and install all the update available.
- Once done, do run SFC Scanner.
- Search for Command Prompt, right click on it and select Run as Administrator.
- Once open, type sfc/scannow then press Enter. While until it finish the scan and see if it will solve the issue or not.
- If these steps will not work, proceed with doing a clean install of the graphics card driver.
- Go to Device Manager and uninstall the Nvidia graphics driver.
- Next is to open Programs and Features then uninstall anything related to Nvidia.
- Once done, download and install the latest driver.
- Here's the link: http://www.nvidia.com/Download/index.aspx
- Reboot the laptop once the latest driver has been installed then test it again.
- If the same problem will persist, do also run a memory test just to make sure everything is working properly.
- Do also try installing the latest BIOS version.
- Here's the link: http://dlcdnet.asus.com/pub/ASUS/mb/LGA1150/MAXIMUS-VII-HERO/MAXIMUS-VII-HERO-ASUS-3103.zip?_ga=1.91035544.305422646.1455979617
- If these will still not work, try removing one of the SSD of the PC and see if that will make any difference as well.

 

[bernas]

All the Windows Updates are installed.

Did the SFC Scan, selected Run as Administrator, a black window appeared and immediately closed, nothing happened.

Uninstalled everything related to Nvidia. Installed the latest driver and rebooted.

I have the latest BIOS version installed.

The main SSD has the Operating System installed on it. The other one has nothing, I made a hard drive format on both of them and did a fresh Windows 10 install.

Would it be possible for someone to check the .dmp file I uploaded? I think that by seeing it, some reason for this BAD_POOL_CALLER may be found.

 

[johnbl]

see if you can get a update for your near field communication driver. Start by looking at your motherboard website if it came with your mother board
it looks like two parts:
http://netfiltersdk.com/download.html
and another part that looks like part of a Network Flow Control SDK

if you don't use this you might just want to remove it.

---------------------
the bugcheck was in networking code called by your virus scanner. Generally something like this will be in bug in the networking driver.

It is not likely to be your intel network driver. you can see if there is a update here: https://downloadcenter.intel.com/


Very likely to be cause by your Near field communication driver.
(I would remove it or update it if you can)
"Titan ARC Network Flow Control SDK WFP Driver ???)
NFC_Driver.sys Tue Mar 11 02:14:42 2014
or this driver:
NetFilter SDK TDI Hook Driver
netfilter2.sys Sun Jan 04 07:04:47 2015

basically some network driver used a memory block from the kernel but corrupted it before it released the memory back to windows.
It corrupted the windows portion of the data structure so windows called a bugcheck.

machine:
BIOS Version 3103
BIOS Starting Address Segment f000
BIOS Release Date 03/09/2016

Manufacturer ASUSTeK COMPUTER INC.
Product MAXIMUS VII HERO
Version Rev 1.xx

Processor Version Intel(R) Core(TM) i7-4790K CPU @ 4.00GHz
Processor Voltage 8ch - 1.2V
External Clock 100MHz
Max Speed 3800MHz
Current Speed 4000MHz

memory:
Speed 2400MHz
Manufacturer Kingston
Part Number KHX2400C11D3/8GX

 

[bernas]

I have uninstalled the software that had "NFC_Driver.sys" and also removed the remaining file, from the computer.

But the Blue Screen BAD_POOL_CALLER just happened again.

I have uploaded the present .dmp file, could you please see what cause the Blue Screen again?

Link for the .dmp file

Do I have to manually remove the "netfilter2.sys" file too? Will it cause any trouble for windows If I do delete that one also?

 

[johnbl]

still looks like a bug in a network driver. netfilter2.sys Sun Jan 04 07:04:47 2015 is still installed.
a filter driver is a 3rd party extension to windows. It gets first look at data going to a resource on you machine, in this case a network resource.
I see google listings that it is being used by adware/malware programs so they insert/remove network data.
you might use a guide like https://www.fixyourbrowser.com/removal-instructions/how-to-remove-genvariant-adware-netfilter-2-removal-guide/

or you could try the windows commands (below)


start cmd.exe as an admin then run
Fltmc.exe
then look at the list of filters it will show a list of filters, see if you can figure out which one is netfilter2.sys
at this point you can at least see if the filter is still install.

to remove the filter: I do not know much about these filters, you can run fltmc.exe /help
to see the options. something like
I think the command would be
fltmc.exe /detach "bad filter name" but it would be better to use a tool like the adware remover, or go into windows control panel and remove the program that installed it.

I say this because these programs might be in startup, or might start in a way that your system will not startup if it is deleted directly (i just don't know)
if you do manually delete the file, it might automatically be restored from a hidden back up copy so check again for the file after you reboot.







here is the list of filters that is on my machine (so you have something to compare with)
C:\WINDOWS\system32>fltmc

Filter Name Num Instances Altitude Frame
------------------------------ ------------- ------------ -----
WdFilter 5 328010 0
storqosflt 0 244000 0
FileCrypt 0 141100 0
luafv 1 135000 0
npsvctrig 1 46000 0
FileInfo 5 45000 0
Wof 4 40700 0

 

[bernas]

Hello

I uninstalled and cleaned netfilter2.sys from my computer, using adware removing tools.

But the Blue Screen BAD_POOL_CALLER just happened again. 🙁

Here is the .dmp file:
https://www.dropbox.com/s/yes9s8oha528u5q/062016-5625-01.zip?dl=0

I have checked fltmc.exe and these are the filters that I have:

Filter Name Num Instances Altitude Frame
------------------------------ ------------- ------------ -----
MBAMProtector 6 328800 0
gzflt 6 320820 0
ignis 6 320811 0
avckf 6 320810 0
avc3 6 320780 0
trufos 5 320770 0
storqosflt 0 244000 0
FileCrypt 0 141100 0
luafv 1 135000 0
npsvctrig 1 46000 0
FileInfo 6 45000 0
Wof 4 40700 0

I have searched for each of them online and they are working for the anti virus and the windows operative system.

Could someone help me please?

 

[johnbl]

you also have SAMSUNG Android Modem Device Driver (driver = ssudbus.sys, ssudmdm.sys)
this is a network driver and a likely cause of a network stack corruption problem.
(just guessing the virus scanner is scanning that device and it has bugs)
-------------
something corrupted your network code,
It could be your bit defender software,
it could be your network driver.
it could be your malwarebytes driver.
it could be your overclocking software


-you should remove all but one anti virus scanner.
- remove the overclock driver IOMap64.sys (it is a asus driver)
- remove the asus usb filter driver

it could be that the asus usb filter driver is just messing up all of the bit defender filter drivers.

At this point the stack has been corrupted but you can not tell what corrupted it.
you would have to stop the system at the time of the corruption.

to do that you have to run cmd.exe as an admin then run
verifier.exe /standard /all

and reboot your machine. if verifier finds a driver with the is writing outside of its memory space it will call a bugcheck and name the driver.
be sure you know how to get into safe mode (F5 or shift+f5 while booting windows)
if you machine bugchecks on the reboot, you will have to turn off verifier.exe
verifier.exe /reset
also when done testing you will have to turn off the verifier functions.

also, you might want to change the memory dump type to kernel. This will force the system to save much more debug info.
how to change windows memory dump type : https://www.sophos.com/en-us/support/knowledgebase/111474.aspx
select kernel rather than full memory dump. it your system crashes, you would need to put the file c:\windows\memory.dmp on a serve and post a link.

 

[Astralv]

I also had BAD_POOL_CALLER happening few times on my 2.5 years old system. I also have Asus motherboard and Asus AMD graphic card. I used to have another similar error, but BAD_POOL_CALLER happened yesterday when I was massing with different monitors settings and connecting things to USB ports. My computer some time randomly restarts, and it related to KVM switch and the time when computer recognizes monitors/keyboard/mouse.

johnbl, I am glad somebody can follow your directions- I cant understand what you recommending to do. Lacily, my Bad_Pool only happened few times so far...

 

[johnbl]

change the memory dump type to kernel, here are instructions : https://www.sophos.com/en-us/support/knowledgebase/1114...
(but select kernel, not full memory dump)

Turn on windows verifier to check device drivers for bugs: here is how:

start cmd.exe as a admin (windows key+x, then type A)
run the following command:

verifier.exe /standard /all

reboot your machine.


Note: know how to get into windows safe mode so you can turn off verifier if you machine bugchecks on the next boot.
to turn off verifier you start cmd.ex as a admin
then run
verifier.exe /reset
when done testing turn off verifier (above command) or your machine will run slowly until you do.

if verifier finds a problem with one of your drivers it will bugcheck the system (BSOD) and record the info in a memory dump
either in c:\windows\minidump directory
or c:\windows\memory file

you would then place the file on a cloud server like microsoft onedrive, google docs or dropbox, share the files for public access and post a link.

 

[bernas]

I have changed the memory dump type to kernel and turned on verifier to check device drivers for bugs.

When testing was done, I turned verifier off.

Here is the memory dump files that I got:

mini dump file at 9:47 pm
https://www.dropbox.com/s/4k5e0am6yjn2bti/minidump%2021H47%20%28same%20day%29.zip?dl=0

mini dump file at 10.32 pm
https://www.dropbox.com/s/7rdo1t1d6qe0spm/minidump%2022H32%20%28same%20day%29.zip?dl=0

I removed the asus usb driver and the mouse stopped working so I had to use keyboard to reach an older system image and restore windows by that date.

Some people say that this may be happening because I have Bitdefender Total Security 2016 running on my system, as the same time as Malwarebytes Anti-Malware Home (Premium). Could these two programs, working simultaneously, be causing this Blue Screen BAD_POOL_CALLER?

 

[johnbl]

kernel memory dumps are stored in a different file.
c:\windows\memory.dmp

the minidumps do not contain the debug info.

I have changed the memory dump type to kernel and turned on verifier to check device drivers for bugs.

When testing was done, I turned verifier off.

Here is the memory dump files that I got:

mini dump file at 9:47 pm
https://www.dropbox.com/s/4k5e0am6yjn2bti/minidump%2021H47%20%28same%20day%29.zip?dl=0

mini dump file at 10.32 pm
https://www.dropbox.com/s/7rdo1t1d6qe0spm/minidump%2022H32%20%28same%20day%29.zip?dl=0

I removed the asus usb driver and the mouse stopped working so I had to use keyboard to reach an older system image and restore windows by that date.

Some people say that this may be happening because I have Bitdefender Total Security 2016 running on my system, as the same time as Malwarebytes Anti-Malware Home (Premium). Could these two programs, working simultaneously, be causing this Blue Screen BAD_POOL_CALLER?

 

[johnbl]

the system did not have enough room to create a kernel memory dump so it made a minidump. (kernel memory dumps are very large, often 1 GB)
(either you are out of drive space, or maybe your pagefile is too small)

second bugcheck:
RzSynapse.exe talking to rzudd.sys (razer drivers)
debug info not saved but it looks like the driver rzudd.sys continued to use a memory block after it was freed back to the system.
this can lead to memory corruption so verifier bugchecked the system to shut it down.
file was rzudd.sys Tue Aug 11 04:13:50 2015
Razer Rzudd Engine Driver
check for software updates http://drivers.razersupport.com/index.php?_m=downloads&_a=view&_m=downloads&_a=view
--------------------

anyway, the first one looks like a network problem, the second one looks