Avast Internet Security causing BSOD BAD POOL CALLER 

ktorpil · 2017-07-15T19:03:08.000Z

I’m using Windows 10 Pro x64 with all latest updates/drivers. I have no other problems with anything. As soon as I pass the login screen, I get a BAD POOL CALLER BSOD. So I formatted my system and at day 2, when I finally get to install Avast, I got a BSOD in the middle of the installation. Tried older installation executables, cleaned everything with avastclean, no avail. Avast installed = BSOD. Avast not installed = everything perfect.

What’s even more disturbing is that the exact same thing happened to my office computer also which has completely different hardware specifications.

Please fix your software.

Asyn · 2017-07-15T19:16:11.000Z

The last MS update broke it, Avast is in contact with MS already.

system · 2017-07-16T22:57:41.000Z

I have exactly the same problem.
If this does not get fixed, that is the end of Avast for me.

Hope they fix this soon.
Regards,

Juan

ktorpil · 2017-07-20T09:52:13.000Z

No confirmation, no acknowledgement whatsoever.

Tried again today, same thing.

That’s it. I’m cancelling my auto renewals and buying AVG.

system · 2017-07-23T21:37:56.000Z

Today I got the same bsod BAD_POOL_HEADER 0x00000019 on Win7 x32 with Avast Free Antivirus 7.0. Can boot in Safe mode ok, “normal” win gives bsod after user login. If boot in Safe mode and disable Avast from there then can boot in “normal” win ok. Can this happen after todays signatures updates? And how to fix?

Asyn post:2:

The last MS update broke it, Avast is in contact with MS already.

[s]I do only manual win updates and last updates I installed 2 months ago. User above doesn’t installed win updates at all. I’m sure this happened after last Avast signatures update.

Asking developers for help or other info. Thanks.[/s]

UPD: Reinstalled my Avast Free Antivirus 7.0 today and BSOD gone. Everything seems to be ok again. Sorry for troubling, don’t know what happened (chkdsk and sfc /scannow was ok).

bob3160 · 2017-07-23T22:09:21.000Z

gue5t post:5:

Today I got the same bsod BAD_POOL_HEADER 0x00000019 on Win7 x32 with Avast Free Antivirus 7.0. Can boot in Safe mode ok, “normal” win gives bsod after user login. If boot in Safe mode and disable Avast from there then can boot in “normal” win ok. Can this happen after todays signatures updates? And how to fix?

Asyn post:2:

The last MS update broke it, Avast is in contact with MS already.

I do only manual win updates and last updates I installed 2 months ago. User above doesn’t installed win updates at all. I’m sure this happened after last Avast signatures update.

Asking developers for help or other info. Thanks.

I’ve already reported this thread to the developers.
Hopefully sometime tomorrow we’ll see a reply.

system · 2017-07-27T18:22:20.000Z

bob3160 post:6:

I’ve already reported this thread to the developers.

Thanks, but my problem with Avast Free Antivirus 7.0 solved: I just reinstalled it and everything ok again. Don’t know what happened: I made chkdsk and sfc /scannow and got no errors, but something was broken anyway. Now everything ok.

jaroslav.nix · 2017-07-28T07:12:14.000Z

Is it please possible to set up generation of kernel/complete memory dump:
https://support.microsoft.com/en-us/help/969028/how-to-generate-a-kernel-or-a-complete-memory-dump-file-in-windows-ser

and upload it to our FTP for analysis:
https://www.avast.com/faq.php?article=AVKB160

There might be already one located in c:\windows\memory.dmp, so please just compress and upload it. Thank you.

Announcements