Jump to content

Bsod (Bad_Pool_Header) Caused By Mbam 2


Recommended Posts

Dear MBAM Support,

 

I must say I'm not hapy at all with the new MBAM 2.x versions. I've had MBAM 1 for ages and it ran just fine, and suddendly, when 4 days ago I patched to 2, everything started crashing with my computer.

 

It first happened 2 days ago (I had MBAM installed for 1 day, it ran just fine). Suddendly, after about 24 hours of having patched to the new version, I got a BSoD while I was doing nothing special, which is very weird. I only get BSoD once in a while when I'm loading my computer too much, but during semi-idling this never happened (I think I was checking my mail when it bluescreened). The error on the BSoD was "BAD_POOL_DRIVER". Then Windows restarted, and after having entered my password I got a BSoD again in the welcome screen (After entering the user password, but before seeing the desktop). After this it started okay-ish (I had a BSoL, Black Screen of Limbo, after the welcome screen I had a black screen with only my mouse for about 2 minutes, then the desktop appeared). I noticed everything loaded up just fine, except MBAM was not loaded. I then tried to start it manually, but it just wouldn't start, doesn't matter how many times I clicked on the icon. So I rebooted again, and this time the boot was smooth and fine and normal, but again MBAM didn't start, and nor did clicking the icon have any effect (manually open the .exe in the program files folder had no effect either). So I googled BAD_POOL_DRIVER and I saw another MBAM user come across the same error (he chose to delete MBAM completely, but I want to keep using it). So I ran the "MBAM Clean Removal Process 2x" and everything worked fine again, no more slow booting, and MBAM was running again at boot and I was also able to open it manually. I did a scan just to make sure I wans't infected (both with MBAM and with my AntiVirus, NOD32), and I had 0 threats. So I thought it was just a bug.

 

But yesterday evening, the EXACT same thing happened again. Everything was running fine, I was watching a movie, 30 minutes in, and bam, BSoD with BAD_POOL_DRIVER as reason. It rebooted and again it crashed after entering password at the welcome screen with BAD_POOL_DRIVER again. This time (Unlike 3 days ago where this just happened once) it happened 3 times after each other, 3 times after booting it gave me BSoD after entering password. 4th boot went fine, not even BSoL (the black screen with mouse only), but again, the same thing happened as before, MBAM didn't load and I can't open it manually. At the moment, after the 10th consecutive boot, MBAM is still not running, not even the process.

 

Please help me with this problem, I'm sure that the BSoDs are caused by MBAM. My preference would be to install 1.75 again, but I can't seem to find the official download link anywhere on this site (And I don't want to download this program from a 3rd party site).

 

Either give me a solution to the problem (I don't want to use the new beta version though, unless it's 100% certain that it solves my problem) or give me the download link for 1.75 please.

 

Thanks in advance for the help.

 

Alessandro

Link to post
Share on other sites

Hello and :welcome:

Thank You

Just to add... are you running any encryption software? Take note of item #5 in the FAQ if you are....

Link to post
Share on other sites

Hello and :welcome:

Thank You

Just to add... are you running any encryption software? Take note of item #5 in the FAQ if you are....

 

 

Hello,

 

What is the point of doing this? I already did this once (I said I already ran the MBAM Clean Removal Process 2x), and the problem persists, so why should I do it again anyways? I know that if I'll run this in 1-2 days I'll get the BAD_POOL_HEADER BSoD again.

Also, like I said, I don't want to install the beta unless it's 100% sure that it solves my problem, so will it solve my problem? Is this a known bug? Help me out here because I don't know anything at all about MBAM 2 yet.

 

I already read the FAQ before posting in case it was a known bug and I found nothing there, and to answer your question: I'm not running any encryption software.

 

Do you have the 1.75 download link by any chance (that's what I'm mainly looking for) ?

 

Thank you.

Alessandro

Link to post
Share on other sites

The purpose of that was to get you the info in item #4 to try out the new beta version out, that is suppose to correct a lot of issues that were in the current version. Have you tried the new beta version to see if it corrects your problem?

As for reverting to 1.75

Well you really should let us work with you to see what's going on. If you simply stick with 1.75 and think you're okay then come next year when we no longer support 1.75 you'll really be stuck as you won't have another version to fall back on.

 

FWIW, users reverting back to old version also need to realize they won't be as secure with it. The new scan engine in 2.0 has some tweaks in it to deal with current threats that old version does not.

The team is reacting to suggestions and comments with new versions as quickly as possible as has been done in the past.

Try as they might, you can't please everyone and this happens with every version we release.

If you'd like to take the time to let us help you then let me know and we'll be more than happy to take a look and see what's going on.

Please read the following topic Diagnostic Logs and post back the logs when ready and we'll see if we can determine what's going on.

Thanks

NOTE: You can download Malwarebytes version 1.75 from =>Filehippo HERE<= and click on the GREEN box titled Download This Version (9.81MB)

Link to post
Share on other sites

Thanks a lot for this useful reply!

I'm running the scans now. For some reason I can't run mbam-check.exe, it gives an appcrash everytime I try to run it, the error is (in the spoiler):

 

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    mbamcheck-vc100-x86-s-2_0_3_1.exe
  Application Version:    2.0.3.1
  Application Timestamp:    533039e7
  Fault Module Name:    mbamcheck-vc100-x86-s-2_0_3_1.exe
  Fault Module Version:    2.0.3.1
  Fault Module Timestamp:    533039e7
  Exception Code:    40000015
  Exception Offset:    0014fdde
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    2057
  Additional Information 1:    d78f
  Additional Information 2:    d78fdbaebaa720e84567dbca10486589
  Additional Information 3:    1312
  Additional Information 4:    1312ae429fa31e13a8c06a65c51d5d3f

 

As for the other scans, I added them to my reply.

So you think my best try is to install the beta and see if it runs without the same problems as now?

 

Thanks again for the help!

 

FRST.txt

Addition.txt

Link to post
Share on other sites

{{kibbitz}}

Hello,

 

Regret that you are having the BSOD issue.  I would simply just caution to not "necessarily" blame the version 2 for the BSOD.

 

You can find the setup for version 1.75 here https://malwarebytes.box.com/s/u0b4k0fttttab6q2qqrw

 

The Bad pool caller problem  could ( just) have been lying in wait due to pre-existing factors.

I have seen a fair number of these over the past years -- due to other factors --- not to do with the anti-malware.

 

Bad pool caller is error number STOP 0x000000c2.    Did you happen to catch the STOP code that you had?

A Stop 0xC2 message might also be due to failing or defective hardware.

 


Use a working pc and get a memory test utility, place on diskette, and run it on the Sony.
Run a RAM memory test. MEMTEST86 is one such utility.
See http://www.memtest86.com/

 

If you have the Windows 7 DVD, iirc, you can run the memory diagnostic from Microsoft off that DVD.

 

It may be interesting to see your Windows system event log entries.

Link to post
Share on other sites

{{kibbitz}}

Hello,

 

Regret that you are having the BSOD issue.  I would simply just caution to not "necessarily" blame the version 2 for the BSOD.

 

You can find the setup for version 1.75 here https://malwarebytes.box.com/s/u0b4k0fttttab6q2qqrw

 

The Bad pool caller problem  could ( just) have been lying in wait due to pre-existing factors.

I have seen a fair number of these over the past years -- due to other factors --- not to do with the anti-malware.

 

Bad pool caller is error number STOP 0x000000c2.    Did you happen to catch the STOP code that you had?

A Stop 0xC2 message might also be due to failing or defective hardware.

 

Use a working pc and get a memory test utility, place on diskette, and run it on the Sony.

Run a RAM memory test. MEMTEST86 is one such utility.

See http://www.memtest86.com/

 

If you have the Windows 7 DVD, iirc, you can run the memory diagnostic from Microsoft off that DVD.

 

It may be interesting to see your Windows system event log entries.

 

Hey thanks for your reply!

 

I got my laptop back from warranty about a month ago and I ran a fresh windows installation, then I did several memchecks, HDD checks, gpu and cpu checks and bechmarks to see if the laptop was really repaired.

Turns out all the components are fine. I ran diagnostics from microsoft as well, all is fine.

 

The point that I'm saying that BAD_POOL_HEADER is caused by MBAM is because the computer is running fine, and then all of a sudden I get this BSoD and MBAM dissapears. I reinstall, it's all fine again, then suddendly BSoD and MBAM dissapears again. I'm not sure whether MBAM causes this error, but it sure as hell has to do with this, don't you think? Also, never had this kind of errors with 1.75, I install 2 and the error starts, I didn't do any software or hardware modicifcation besides installing mbam 2, so my drivers, hardware and software were just fine up to that point.

 

Again, thanks for your input! I'd like to hear your opinion on my reply.

Alessandro

Link to post
Share on other sites

  • Root Admin

Well its certainly up  to you but I would agree with Maurice that it is not because of MBAM 2 (granted we may now be making it more evident), but something else on this computer is behind this.  I've now fixed a few of these myself lately and in each case the computer was infected.

I assume you know that your have a proxy set. Not an issue as long as you're aware of it.
FF NetworkProxy: "autoconfig_url", "https://mediahint.com/default.pac"
FF NetworkProxy: "type", 2


This software is designed to Pirate and steal Microsoft Office
C:\IORRT\IORRT.bat

This entry is designed to Pirate and steal software from Adobe
127.0.0.1 activate.adobe.com

In either case it's obvious this computer is being used to steal software and as such we cannot assist you unless you wish to fully uninstall these entries and the software they're being used with to steal. If you would like to follow-up and are willing to remove the items please send me a Private Message and I can unlock the topic.
 
This topic will now be closed due to evidence of cracked or pirated software on this system.

Piracy Policy
 

Thank you.

Link to post
Share on other sites

Since I've removed the current version with the Clean Removal 2x again, and installed the 2.0.2 public beta I haven't had a problem yet.

It's been almost a week and no BSOD, I don't want to rush to any conclusions, but I think it's safe to say that the previous version of MBAM was causing this.

 

I think you can lock this topic, as I don't have any problems anymore now using the 2.0.2 version.

Thanks everyone for their help!

Link to post
Share on other sites

Guest
This topic is now closed to further replies.
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.