[SOLVED] [Win10 x64] BAD_POOL_CALLER & BAD_POOL_HEADER crashes - Windows 10 x64

W

Wildfire

Active member
Joined
Nov 3, 2015
Posts
28
I've been having problems with regular crashes on my system, BAD_POOL_CALLER and BAD_POOL_HEADER crashes were popping up regularly. Last November I opened a thread (https://www.sysnative.com/forums/bs...ezes-no-immidiate-clear-cause.html?highlight=) about this issue. The one suggestion that came out of that, disabling the Intel Management Engine, had no effect. After a while using an Intel network card it became clear that the Killer Network card also wasn't the issue.

As luck would have it, I was able to switch out my motherboard/CPU/RAM for new components. I went from a MSI Z97 Gaming 7 to an ASUS Maximus VIII Hero, from an i7-4790K to an i7-6700K and from 32GB (4x8GB) DDR3-2133 RAM to 32GB (4x8GB) DDR4-2666 RAM.

Of course I did a fresh install of 64-bit Windows 10 including the most recent drivers.

Unfortunately enough, it would appear the cause of the crashes is something else -- even with those new components, I'm still experiencing the crashes I was hoping to escape. This night and just now before I posted this, the system crashed again with a BAD_POOL_CALLER error... given that, I expect there will be a BAD_POOL_HEADER BSOD sometime soon too.

So here I am again... hoping that there's someone here who can help figuring out where things go wrong on my system.

Attached, of course, the zipped PERFMON output and the Sysnative BSOD Collection dumps (please note, the information will indicate that the Intel Management Engine is disabled, but I did that after the first crash, the second crash occured with the Intel Management Engine disabled).

Also, as requested, information about my system:


· Windows 10 Pro 64-bit (version 1511, build 10586.63; fully up-to-date; clean install after upgrade from Windows 8.1)
· Motherboard, CPU, memory: new; Intel SSD: half a year old; Samsung SSD: approximately 18 months; hard drives: approximately 24 months;
· Intel Core i7-6700K (NOT overclocked)
· ASUS GeForce GTX980Ti (NOT overclocked)
· ASUS Maximus VIII Hero motherboard
· Kingston HyperX Fury DDR4-2666 (4x8GB, NOT overclocked)
· Corsair AX760 PSU
· SoundBlaster ZxR sound card
· Intel 750 SSD 480GB (PCI-Express)
· 2x Western Digital Green 2TB hard drives
· Samsung 840 Pro 500GB
· Self-built desktop system


I'll be running memory diagnostics (even though I've already swapped out one DDR4 set for another) and hard drive diagnostics later on, at the moment I cannot spare the time for those extensive tests. I'll update this post when I have the results from these tests.

Of course I'll also try Driver Verifier. Let's see if that won't result in an immediate crash at boot, as happened with my previous system :)


View attachment perfmon.zip
View attachment SysnativeFileCollectionApp.zip
 
re: [Win10 x64] BAD_POOL_CALLER & BAD_POOL_HEADER crashes - Windows 10 x64

I could successfully enable Driver Verifier, so as soon as a new BSOD occurs I'll post a new minidump.
 
re: [Win10 x64] BAD_POOL_CALLER & BAD_POOL_HEADER crashes - Windows 10 x64

Hi. . .

A VERIFIER_ENABLED dump file could be very helpful to us. Thanks.

Regards. . .

jcgriff2
 
jcgriff2 said:
Hi. . .

A VERIFIER_ENABLED dump file could be very helpful to us. Thanks.

Regards. . .

jcgriff2
Click to expand...

Of course, now that I *want* my system to crash, it doesn't... :)

I'm sure it'll happen soon, so I'll check in here again when it does. :)
 
Update: after 13.5 hours of Memtest86 (3 passes), no errors found.

(your guide suggests running it for 7 to 10 passes, but unfortunately enough due to the time required for that I cannot do that -- it would mean not having access to my computer for nearly two full days)
 
Hi Wildfire,

Both of your dump files have the probable cause as NETIO.sys, which is kind of just a generic/default response. Looking at the relevant stack text however, both dump files include MWAC.sys, Malwarebytes Web Access Control.

011616-15734-01
Code: 
#  Child-SP          RetAddr           Call Site
00 ffffd000`2580c1b8 fffff800`1e047cf1 nt!KeBugCheckEx01 ffffd000`2580c1c0 fffff800`a3ec4a20 nt!ExFreePool+0x1d1
02 ffffd000`2580c2a0 fffff800`a3cf5b2e NETIO! ?? ::FNODOBFM::`string'+0x9bb0
03 ffffd000`2580c2f0 fffff800`a3e91781 tcpip! ?? ::FNODOBFM::`string'+0x336fe
04 ffffd000`2580c340 fffff800`a3f41d4e NETIO!NetioDereferenceNetBufferList+0x161
05 ffffd000`2580c3c0 fffff800`a3f41c75 fwpkclnt!FwppDereferenceNetioNetBufferList+0x46
06 ffffd000`2580c410 fffff800`a65390bf fwpkclnt!FwpsDereferenceNetBufferList0+0x25
07 ffffd000`2580c440 ffffe001`09ec8010 [COLOR=#ff0000]mwac[/COLOR]+0x90bf
08 ffffd000`2580c448 00000000`c0000900 0xffffe001`09ec8010
09 ffffd000`2580c450 fffff800`a653e500 0xc0000900
0a ffffd000`2580c458 ffffe001`0302f1a0 [COLOR=#ff0000]mwac[/COLOR]+0xe500
0b ffffd000`2580c460 00000000`00000008 0xffffe001`0302f1a0
0c ffffd000`2580c468 fffff800`a65361ea 0x8
0d ffffd000`2580c470 00000000`00000008 [COLOR=#ff0000]mwac[/COLOR]+0x61ea
0e ffffd000`2580c478 00000000`00000008 0x8
0f ffffd000`2580c480 00000000`c000000d 0x8
10 ffffd000`2580c488 ffffe001`09ec8034 0xc000000d
11 ffffd000`2580c490 ffffe001`09ec8024 0xffffe001`09ec8034
12 ffffd000`2580c498 ffffe001`00000011 0xffffe001`09ec8024
13 ffffd000`2580c4a0 00000000`00000000 0xffffe001`00000011


011616-17328-01
Code: 
#  Child-SP          RetAddr           Call Site
00 ffffd000`23130cd8 fffff803`01846cf1 nt!KeBugCheckEx
01 ffffd000`23130ce0 fffff801`6dd64a20 nt!ExFreePool+0x1d1
02 ffffd000`23130dc0 fffff801`6ded5b2e NETIO! ?? ::FNODOBFM::`string'+0x9bb0
03 ffffd000`23130e10 fffff801`6dd31781 tcpip! ?? ::FNODOBFM::`string'+0x336fe
04 ffffd000`23130e60 fffff801`6dd31507 NETIO!NetioDereferenceNetBufferList+0x161
05 ffffd000`23130ee0 fffff801`6de1c560 NETIO!NetioDereferenceNetBufferListChain+0x367
06 ffffd000`23130fb0 fffff801`6de1d818 tcpip!IppReceiveHeaderBatch+0x4b0
07 ffffd000`231310b0 fffff801`6df33c78 tcpip!IppFlcReceivePacketsCore+0x338
08 ffffd000`231311d0 fffff801`6e054fa6 tcpip!IppInspectInjectReceive+0xf8
09 ffffd000`23131210 fffff803`0168ab35 fwpkclnt!FwppInjectionStackCallout+0x116
0a ffffd000`231312a0 fffff801`6e056886 nt!KeExpandKernelStackAndCalloutInternal+0x85
0b ffffd000`231312f0 fffff801`6e0564dd fwpkclnt!NetioExpandKernelStackAndCallout+0x52
0c ffffd000`23131330 fffff801`703161b8 fwpkclnt!FwpsInjectTransportReceiveAsync0+0x2ad
0d ffffd000`23131470 ffffe001`c5eb2fa0 [COLOR=#ff0000]mwac[/COLOR]+0x61b8
0e ffffd000`23131478 00000000`00000000 0xffffe001`c5eb2fa0

Since you already did a fresh install of Windows 10 and the issue persisted, I'd recommend uninstalling Malwarebytes and seeing if the crash continues. You could also just leave things as they are for now and wait for a crash with Verifier so we can look at that dump file first.
 
Thanks for the input. As I needed my computer back to its normal performance level, I have disabled Verifier and uninstalled Malwarebytes for now. I'll try running my system like this for a week to see how it goes. I will, of course, let you know how things work out.
 
Wildfire said:
Thanks for the input. As I needed my computer back to its normal performance level, I have disabled Verifier and uninstalled Malwarebytes for now. I'll try running my system like this for a week to see how it goes. I will, of course, let you know how things work out.
Click to expand...

Sounds good. Best of luck!
 
Xer said:
Wildfire said:
Thanks for the input. As I needed my computer back to its normal performance level, I have disabled Verifier and uninstalled Malwarebytes for now. I'll try running my system like this for a week to see how it goes. I will, of course, let you know how things work out.
Click to expand...

Sounds good. Best of luck!
Click to expand...

Thanks! I'm almost positive MBAM is the cause, seeing that there are more people at this forum with MBAM and these crashes. :)
 
Still no problems, so I'm now very confident it was indeed MBAM... a shame really, as an anti-malware program it was excellent. Perhaps I'll install it again and see if I can help the team at Malwarebytes at fixing the issue with their driver.
 
The thread has already been marked as solved, but just to verify: it's now two weeks later and still no crashes. So it's absolutely 100% definitive that it was the MBAM webfilter driver.

Couldn't have figured it out without this forum, so again -- many thanks!!! :rofl12::thumbsup2:
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top