windows 10 32bit bad_pool_header

[gizmo]

hi i seem to be having a problem with win 10 as i keep getting bad_pool_header when i am on line , i have looked in google about this error but cannot find a solution , the computer has had a fresh install and updated drivers , i am woundering if it is the cpu or graphics card at fault the computer is 1 yr old and custom gaming machine , can anyone please point me in the right direction on how to solve this problem many thanks for your help and advice

 

[BigFeet]

I used to get this when gaming, and, if I remember correctly, it ended up being an issue with the video drivers. I remember uninstalling the drivers with DDU in safe mode, then reinstalling them. I believe this fixed the issue for me. There are other causes for this issue, Corrupt Device Drivers, Faulty/Corrupt Registry Entries, Damaged Hard Disk, Bad RAM, Corrupt Windows System files, Anti-virus or Anti-Malware Softwares.

Another thing that has been known to be an issue, is fast boot. Right click on start menu->Power Options->Choose what power button does(in left column)->Click"Change settings currently unavailable"->uncheck "Turn on fast startup->Apply. If that doesn't help, you can always undo that, as it will increase boot times.

 

[gizmo]

I used to get this when gaming, and, if I remember correctly, it ended up being an issue with the video drivers. I remember uninstalling the drivers with DDU in safe mode, then reinstalling them. I believe this fixed the issue for me. There are other causes for this issue, Corrupt Device Drivers, Faulty/Corrupt Registry Entries, Damaged Hard Disk, Bad RAM, Corrupt Windows System files, Anti-virus or Anti-Malware Softwares.

Another thing that has been known to be an issue, is fast boot. Right click on start menu->Power Options->Choose what power button does(in left column)->Click"Change settings currently unavailable"->uncheck "Turn on fast startup->Apply. If that doesn't help, you can always undo that, as it will increase boot times.

many thanks for your help and advice , with the power options it is all ready set to turn on fast startup , not sure what ddu is in safe mode ? windows 10 is a new install , and the computer has been upgraded 2 weeks ago with new hard drives , and dvd rom drives , we have 2 windows 10 pc both have the same security on them , i know when i was windows 7 you could download a tool for bsod issues , does this forum have the same sort of tools thanks again for your advice

 

[BigFeet]

You might want to try turning fast startup off. It's caused issues on 2 of my PC's. DDU is Display Driver Uninstaller. It completely uninstalls video drivers. Uninstalling it through Windows or just upgrading over the old ones, leaves remnants of the old drivers behind. If it's a video driver issue, that's the best way to reinstall them

I use BlueScreenView to read my BSOD dumps. That might give you a clue what's triggering it. It also wouldn't hurt to run Memtest to rule out a bad stick of ram.

There's probably going to be no easy fix. It's most likely going to take some digging to figure out the culprit.

 

[gizmo]

many thanks for your reply i have run BlueScreenView to see what is going on with the pc , it is showing 5 different problems , so unsure what to do next thanks as i done memory test as well with no issues

fwpkclnt.sys fwpkclnt.sys+e8e3 0x86960000 0x869a8000 0x00048000 0x5632d122 30/10/2015 03:08:34 Microsoft® Windows® Operating System FWP/IPsec Kernel-Mode API 10.0.10586.0 (th2_release.151029-1700) Microsoft Corporation C:\Windows\system32\drivers\fwpkclnt.sys
mwac.sys mwac.sys+7b66 0xb57f0000 0xb57ff000 0x0000f000 0x53a0f437 18/06/2014 03:06:47 Malwarebytes Web Access Control Malwarebytes Web Access Control 1.0.6.0 Malwarebytes Corporation C:\Windows\system32\drivers\mwac.sys
NETIO.SYS NETIO.SYS+991f 0x860d0000 0x86124000 0x00054000 0x5632d691 30/10/2015 03:31:45 Microsoft® Windows® Operating System Network I/O Subsystem 10.0.10586.0 (th2_release.151029-1700) Microsoft Corporation C:\Windows\system32\drivers\NETIO.SYS
ntoskrnl.exe ntoskrnl.exe+1f032c 0x8160b000 0x81bfe000 0x005f3000 0x56fa195f 29/03/2016 06:57:51 Microsoft® Windows® Operating System NT Kernel & System 10.0.10586.212 (th2_release_sec.160328-1908) Microsoft Corporation C:\Windows\system32\ntoskrnl.exe
tcpip.sys tcpip.sys+871ab 0x86780000 0x86952000 0x001d2000 0x56fa2167 29/03/2016 07:32:07 Microsoft® Windows® Operating System TCP/IP Driver 10.0.10586.0 (th2_release.151029-1700) Microsoft Corporation C:\Windows\system32\drivers\tcpip.sys

 

[gizmo]

hi i had another bsod yesterday not sure why this is happing

 

[Trouble]

hi i had another bsod yesterday not sure why this is happing

There is no way I can say for sure, but....
The last time I saw that many reports of NETIO.sys involved with a Blue Screen it was Norton or possibly another thrid party security suite causing the issue.
IF you have any such program installed, perhaps consider uninstalling that for the time being, you can always reinstall it later if it proves not to be at fault. Ideally you want to follow up a typical uninstall with the vendor specific proprietary removal tool to make sure there are not remnants left over..... Google it....
I.E. https://support.norton.com/sp/en/us/home/current/solutions/kb20080710133834EN_EndUserProfile_en_us

IF you can copy the contents of C:\Windows\MiniDump into another folder on your desktop, zip that up and attach it to your next post.....
Maybe someone can have a look at the actual dump files and perhaps provide some further insight.

 

[gizmo]

hi many thanks for your reply , the only security we use on 2 win 10 desktops are bitdefender and Malwarebytes Anti-Malware, i know 1 of the issues seems to be Malwarebytes Anti-Malware but it only happens on 1 computer and not both systems i have upload a dump file is someone would be kind enough to have a look as i have no idea thanks

 

[Trouble]

The fact that

it only happens on 1 computer and not both systems

Is not relevant, unless the two machines are identical in every respect..... That is, every piece of hardware as well as every bit of software installed are exactly the same on both.
mwac.sys 6/17/2014 would seem to be an old version.
According to my installation of Malwarebytes the date seems to be off by more than a year.

Uninstall Malwarebytes, then check C:\Windows\System32\Drivers for mwac.sys and make sure that it is gone. If not get rid of it.
Give it some time and see if you can produce a blue screen with the problem driver gone.
IF not maybe download the latest version of Malwarebytes and install it and inspect the properties of mwac.sys and see if it reflects a more current date and see if your Blue Screen returns.

I've personally never had any issues with Malwarebytes that have resulted in BSODs but something is raising hell with your network stack and since that is the driver being pointed at now ..... I figure since you gotta start somewhere, might as well start there.

 

[gizmo]

many thanks for your reply may i ask is the pitcure from my dump file if it is it dont make any sense , when i look at the same file the dates are different , i know that when i first got this computer and connected to my tv by hdmi it was crashing out , and i had to connect it by pc monitor port this is why i was thinking it is the graphics causing the problem

 

[Trouble]

may i ask is the pitcure from my dump file if it is it dont make any sense

Nope your dump file shows the date for the driver as I have indicated above
The attached image file in my post, practically labeled

my installation of Malwarebytes the date

Was included to show you the date discrepancy between your version of mwac.sys and mine (mine being what I believe to be the latest version from Malwarebytes)

 

[BigFeet]

The fact that

Is not relevant, unless the two machines are identical in every respect..... That is, every piece of hardware as well as every bit of software installed are exactly the same on both.
mwac.sys 6/17/2014 would seem to be an old version.
According to my installation of Malwarebytes the date seems to be off by more than a year.

View attachment 2903

Uninstall Malwarebytes, then check C:\Windows\System32\Drivers for mwac.sys and make sure that it is gone. If not get rid of it.
Give it some time and see if you can produce a blue screen with the problem driver gone.
IF not maybe download the latest version of Malwarebytes and install it and inspect the properties of mwac.sys and see if it reflects a more current date and see if your Blue Screen returns.

I've personally never had any issues with Malwarebytes that have resulted in BSODs but something is raising hell with your network stack and since that is the driver being pointed at now ..... I figure since you gotta start somewhere, might as well start there.

My mwac.sys was created Thursday, ‎August ‎28, ‎2014, ‏‎10:19:18 PM. It is the latest version of Malwarebytes too. It just did a version upgrade a couple weeks ago.

 

[Trouble]

Unfortunately I can't explain the difference in the dates we seem to be finding, but.....
Since his network stack is the problem with all six of the dump files provided and.....
mwac.sys (Malwarebytes Web Access Control driver) is called out in the stack, then.....
That's where I would start.
There all
BugCheck C2
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 00000007, Attempt to free pool which was already freed
Arg2: 0000126c, (reserved)
Arg3: 00000001, Memory contents of the pool block
Arg4: beb9d98c, Address of the block of pool being deallocated

AND the stack looks practically identical
STACK_TEXT:
953295dc 81a0032c 000000c2 00000007 0000126c nt!KeBugCheckEx
95329668 88f366c3 beb9d98c 00000000 92cd55e0 nt!ExFreePool+0x6a2
95329680 893371ab beb9d990 92cd5600 92cd55e0 NETIO! ?? ::FNODOBFM::`string'+0x4cb3
9532969c 88f1af66 92cd55e0 00000001 00000000 tcpip! ?? ::FNODOBFM::`string'+0x21ff
953296c0 88f1de3e 8c8bebe0 00000000 8c8bebe0 NETIO!NetioDereferenceNetBufferList+0xf6
95329700 892de9ec 00000000 00000000 8bec2000 NETIO!NetioDereferenceNetBufferListChain+0x18e
95329768 892ddeb8 c5033820 8c8bebe0 9b6ba4f8 tcpip!IppReceiveHeaderBatch+0x2ac
953297dc 893b17ea 00000001 00000000 894a142f tcpip!IppFlcReceivePacketsCore+0x2f8
953297f8 894a14c8 02000000 00000001 00000002 tcpip!IppInspectInjectReceive+0xc0
95329814 818aa4b5 953298b0 d82f035c 00000001 fwpkclnt!FwppInjectionStackCallout+0x99
9532984c 818aa3fe c5045040 02000000 0097a748 nt!KeExpandKernelStackAndCalloutInternal+0xa5
95329860 894a26ed 894a142f 953298b0 00002400 nt!KeExpandKernelStackAndCalloutEx+0x1e
9532988c 894a2433 953298b0 00000000 00000001 fwpkclnt!NetioExpandKernelStackAndCallout+0x45
95329914 bc1b5554 8c11a078 00000000 00000000 fwpkclnt!FwpsInjectTransportReceiveAsync0+0x1f1
WARNING: Stack unwind information not available. Following frames may be wrong.
9532995c bc1b58f7 8c8bebe0 944da248 00000002 mwac+0x5554
95329988 bc1b5836 944da248 00000002 00000000 mwac+0x58f7
953299b4 bc1b603e 944da248 00000002 00000001 mwac+0x5836
953299d0 bc1b34f9 944da288 00000002 00000002 mwac+0x603e
953299e8 bc1b2ee8 00000000 9e7909a8 00000002 mwac+0x34f9
95329a3c bc1b2b16 bc1bb714 9e790978 00000002 mwac+0x2ee8
95329a5c bc1b33b6 bc1bb714 000010c9 00000002 mwac+0x2b16
95329a78 bc1b8360 bc1bb468 000010c9 00000002 mwac+0x33b6
95329a98 bc1b734f bc1bb7f0 bebe5138 95329ac4 mwac+0x8360
95329aa8 818563c3 c3ff89b8 bebe5138 c3ecdda8 mwac+0x734f
95329ac4 81a8c221 d82f00a8 00000e28 6ed8fda8 nt!IofCallDriver+0x43
95329bb8 81a8b46a 00000000 2472e918 2472e918 nt!IopXxxControlFile+0xda1
95329be4 81936717 00000e28 00000b90 00000000 nt!NtDeviceIoControlFile+0x2a
95329be4 775a1400 00000e28 00000b90 00000000 nt!KiSystemServicePostCall
6ed8fdd8 00000000 00000000 00000000 00000000 0x775a1400

AS well as the process name identified......
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: mbamservice.ex

AS I've mentioned, I've never ever had a problem with Malwarebytes.
It could be Bitdefender not playing well with Malwarebytes mwac.sys and mwac.sys is just getting the blame for the problem.

IF it was me, I would remove both Malwarebytes and BitDefender temporarily, leaving the native Windows Defender and Firewall do their job in the short term and see if the machine stablized or if a different BSOD showed up blaming something different.
As I said.... you gotta start someplace.

 

[gizmo]

many thanks for your help and advice , i have removed Malwarebytes for the time being , but what i dont understand is that i bought Malwarebytes about 2 months ago and download it from there website so i am confused why it seems it is not the latest version , when i was on windows 7 i had no bsod problems with Malwarebytes or bitdefender , the reason why i got Malwarebytes is due to bitdefender not picking up some bugs and Malwarebytes seems to block any unwanted sites that i come across when surfing ,

 

[Trouble]

Don't be overly concerned by the seeming difference in dates in a particular file like mwac.sys
I can't explain it and I don't believe it is likely an area of immediate concern.

As I tried to expain above, I've not found an instance in the past where Malwarebytes was the actual cause of a BSOD, that's not to say that it has or will never happen, I've just never seen it.
I'm convinced that it is likely another program on your computer (third party not native Windows) that wants to do what mwac.sys does and the results is a blue screen and mwac.sys gets the blame.

My suggestion is and has been to remove both Malwarebytes and BitDefender (I really suspect BitDefender). Turn on the native Windows Defender product if it does not auto-start after removing BitDefender.
Run your computer computer for a while, see if you can make it Blue Screen, or wait a reasonable length of time to see if the problem seems to have disappeared.
IF so...... add Malwarebytes back to the system. It works well with the native Windows Defender product.
Run your system for a while with just Malwarebytes and see if mwac.sys produces another BSOD....
IF not ..... then add BitDefender back and see what that produces.

 

[ram1220]

I haven't been following the Bitdefender forum in a while since I upgraded to Windows 10. But I do know that Bitdefender stated that their software was not fully compatible with Windows 10. At least the free version is not. This could be the OP's problem. I use the free version of Malwarebytes and have never experienced any problem other than an occasional false positive. My guess is the problem is with Bitdefender also.

 

[Trouble]

Yep.... I've tried everything to suggest that, but.....
Getting someone to uninstall their Antivirus software is often a hard sell.
AND
It's very important to note that a common uninstall, will often not remove all remnants of the product.
That is why all the top tier vendors make their own proprietary removal tool that I strongly recommend employing following a normal uninstall through the programs and features applet in the control panel.
http://www.bitdefender.com/uninstall/

 

[Trouble]

Evidently to get Bitdefender and Malwarebytes to play nice together, it takes a bit of TLC.
https://forums.malwarebytes.org/topic/181585-bsod/
Hopefully the OP will find some of that information helpful.