Malwarebytes Antimalware causes BSOD
Results 1 to 5 of 5

Thread: Malwarebytes Antimalware causes BSOD

  1. #1
    Join Date
    Jun 2000
    Location
    California
    Posts
    4,127

    Malwarebytes Antimalware causes BSOD

    Just wanted to throw you guys a tip in case you weren't aware of it.

    Malwarebytes Antimalware has been known to cause a BSOD with the following errors:

    BAD_POOL_HEADER
    0x00000019
    0x00000020
    0x087993E8

    It's usually error 19 that comes up with the others shown in paren. The error can recur on reboot or happen after 15 minutes of normal use.

    I had the error on a client's machine, looked it up and discovered that many people have fixed the same error by uninstalling Malwarebytes. I did the same thing and sure enough, the problem was gone. If you put Malwarebytes back, the error will return - though MBAM is not the only cause of BAD_POOL_HEADER.

    rev

  2. #2
    Join Date
    Jul 1998
    Location
    Toronto
    Posts
    25,427
    I haven't run into that error with regards to Malwarebytes. Perhaps it would be helpful to ask about it directly in the Malwarebytes proprietary forums and see if it's something they're aware of.

    https://forums.malwarebytes.org/

    Doing a search there for BAD_POOL_HEADER does not come up with anything relevant to this problem though.

    VirtualDr email notices are not working.
    Check back regularly for responses.

    _____________________
    cat lovers click here

  3. #3
    Join Date
    Jun 2001
    Location
    Albuquerque, NM USA
    Posts
    14,686
    Reverend--
    I find other causes of the BSOD with message BAD_POOL_HEADER . For Example:
    http://msdn.microsoft.com/en-us/libr...(v=vs.85).aspx

    http://www.tomshardware.com/answers/...ol-header.html

    http://www.computerhope.com/issues/ch001142.htm

    etc.

    Run Google on BAD_POOL_HEADER
    Jim
    WIN7 Ultimate SP1 64bit, IE 11, NTFS,
    cable, MS Security Essentials, Windows 7 firewall

  4. #4
    Join Date
    Jun 2000
    Location
    California
    Posts
    4,127
    Yes, there are other causes but I've come across several instances where taking MBAM off fixes the problem and putting it back gives you the problem again. I've just done it myself. I did Google BAD_POOL_HEADER, I could probably find those references again.

    It's a bummer to report because I'm an MBAM fan. They recently updated the look and feel of the application and I suspect that's when the problem started. We're always told to update drivers etc but latest is not always best! Latest is bigger, for sure and probably more complicated but not always better. I'm still using Snagit 5.1, winzip81, PowerISO 4.6, winrar330, and a bunch of others because if it works, don't fix it.

    In the case of MBAM, we didn't get a choice, the update was downloaded and installed without our consent.
    ====
    I had bad pool header . It appeared randomly, roughly 15 minutes after start. I tried all kinds of programs, and nothing actually helped. Suprisingly i found out that the problem was caused by malware bytes /a program which i rely on to keep my system clean/. I discovered the source of my problem accidently, and once i uninstalled it, my system is OK. I do not say that all bad pool headers are caused by it, but in my case it was. Moreover, you could try to use system restore to the longest period possible. I did that, and everything was working OK unitl i updated malware bytes /it crashed again/ .That's how i discovered my problem.
    Reply to vvn050

    m
    0
    l
    Zeek9001 August 25, 2014 9:49:44 AM
    vvn050 said:
    I had bad pool header . It appeared randomly, roughly 15 minutes after start. I tried all kinds of programs, and nothing actually helped. Suprisingly i found out that the problem was caused by malware bytes /a program which i rely on to keep my system clean/. I discovered the source of my problem accidently, and once i uninstalled it, my system is OK. I do not say that all bad pool headers are caused by it, but in my case it was. Moreover, you could try to use system restore to the longest period possible. I did that, and everything was working OK unitl i updated malware bytes /it crashed again/ .That's how i discovered my problem.


    It really pains me to say this, but I had the same conclusion. I was working on an old lenevo laptop, it had malware on it, and when i installed malware bytes, I ran a scan, everything went well, and like 15 minutes after that while uninstalling a few programs, the whole system bluescreened. I then spent the next two days, restoring, reuninstalling, scanning, updating drivers, cleaning registry, only to have it bluescreen time and time again, and have trouble starting up (stuck at windows loading, black screen when i log in, freeze ups once it logged in).

    The only solution i found was after i uninstalled malwarebytes in safemode. Now the computer works fine again. I'm not saying correlation equals causation but.. its interesting

    from: http://www.tomshardware.com/answers/...ows-error.html

    and my own experience.

  5. #5
    Join Date
    Jun 2001
    Location
    Albuquerque, NM USA
    Posts
    14,686
    Reverend--
    You might also look at post #34 here
    https://forums.malwarebytes.org/inde...tection/page-2

    There is no resolution to the problem in that thread, but it may give you a contact within MalwareBytes to learn if the problem has been fixed.
    Jim
    WIN7 Ultimate SP1 64bit, IE 11, NTFS,
    cable, MS Security Essentials, Windows 7 firewall

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •