Jump to content

Windows 10 64 BSOD Error 1392


Recommended Posts

Just went through a week+ of BSOD crashes that appear to have come from some conflict arising from the most recent Malwarebytes Pro upgrade that kept causing BAD_POOL_HEADER & BAD_POOL_CALLER BDOSs. At one point I got a specific Malwarebytes error message 1392. (It might've been 1392L but I think I wrote the L in by mistake. It rebooted before I could doublecheck.) I uninstalled Malwarebytes but reinstalled (as instructed by Microsoft) after I rebooted. Crashes continued so I've uninstalled it again but would like to figure out what the problem is so I can correct it & reinstall ASAP. Malwarebytes seemed to be having conflicts with the file sptd2.sys.

Any suggestions?

Link to post
Share on other sites

Hello and welcome:

We have a special forum area reserved for BSOD work and staffed by BSOD experts.

I suggest starting with the advice in this pinned topic: Blue Screen of Death (BSOD) Posting Instructions - Windows 10, 8.1, 8, 7 & Vista

Then, please start a new post there, including as much of the requested information as you can.

Thanks,

Link to post
Share on other sites

  • 2 weeks later...

@Ovious1

Do you know the make / model of your pc's systemboard?  Is it an Asus or Gigabyte ?  If so, please see  

Posted by Imacri

https://forums.malwarebytes.org/topic/181812-malwarebytes-causing-repeated-bsods-windows-10/?do=findComment&comment=1034349

 

Plus, tell me what brand-name of antivirus is on this box.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • 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.