Win XP - SP3 "Bad_Pool_Caller" - Stop error (Avast! 5.x)

[YXtanyaXY]

Hi,
I see that several people have had BSOD's (recently) which are apparently due to aswSP.sys.
I have had 2: Both "BAD_POOL_CALLER"s

I use: Avast! 5.0.545 (Free Version).
The one on 11/19/10 was several hours after I'd updated the Engine and virus definitions. (I don't remember if I'd updated on the 25th - I update manually)

I have run WhoCrashed HOME EDITION v 3.00 and have the results but I guess you want them sent to avast! directly?

I will be running: "Malwarebytes Anti-Malware (MBAM)", and following this will disable the avast! self-defense module.

Assuming this is clean, would following the directions given to: "zubina" - "BSOD caused by aswSP.SYS" 
http://forum.avast.com/index.php?topic=64953.msg548359#msg548359
October 25th, 2010
be the fix for version 5.0.545
Thanks

[Pondus]

I use: Avast! 5.0.545 (Free Version).

why not try latest version ?.....

Avast! Free Antivirus 5.0.677  http://filehippo.com/download_avast_antivirus/

[YXtanyaXY]

Hi,

I use: Avast! 5.0.545 (Free Version).

why not try latest version ?.....

Avast! Free Antivirus 5.0.677  http://filehippo.com/download_avast_antivirus/

Thanks for the link.
I have read 2 threads of problems with 5.0.677
“BSOD caused by aswSP.SYS”
http://forum.avast.com/index.php?topic=64953.msg548359#msg548359

and

“aswSP.sys BSOD”
http://forum.avast.com/index.php?topic=65907.0

Do you know if there is a patch for 5.0.545?
Or whether the issues have been fixed in 5.0.677?

[DavidR]

Lets not lose sight of the fact you are on a support forum and the BAD_POOL_CALLER could be for many different reasons, where these topics you read would have mentioned/implicated aswSP.sys (avast self protection). But this isn't an issue for the greatest majority of users.

However, if you haven't got the latest avast version it is almost impossible to chase down any problem on an old version and is almost counter productive. So I would still say to get the latest version 5.0.677 and see how it goes for you.

As was said that this bug has been identified and corrected on an internal build, which will be released with the next program update (not in 5.0.677), but in the reply by one of the avast team in your first link gives a way to patch it in 5.0.677, until that next program update. See http://forum.avast.com/index.php?topic=64953.msg548402#msg548402 - this obviously wouldn't apply to earlier builds.