A short while ago and for the first time in…well, for a long long time, I got a Blue Screen in XP. It was a DRIVER_IRQL_NOT_LESS_OR_EQUAL event fingering Avast’s aswSP.SYS driver as the offending culprit. I anaylsed the memory dump file and have attached the full results to this post. The following files are attached:
bluescreen.png
windbg-fullresults.txt Mini040411-01.txt (it is a dmp file. I had change extension from dmp to txt to upload) removed, seems to get corrupted
I wasn’t even doing anything out of the ordinary (typing a text message in PCSuite) so it is a bit alarming.
Using Avast Pro 6.0.1000 on XP pro.
Thanks.
edit…
I am currently uploading the MEMORY.DMP file to your ftp server. It is rarred up as:
Sorry, I am confused. How does the link relate to the error I posted? From what I can see (following the link) the fix is for users with ext2/3 partitions (not me) and version 4.8.xx version of Avast…which I’m not using. Can you be a bit more specific about this fix.
Those errors may also show up as result of faulty RAM.
As long as it does not reoccur, don’t worry. Maybe check your RAM when you have an hour to spare with memtest.
If it happens frequently and always shows Avast as problem, then you might want to try the Beta 6.0.1044 - you could do that anyway, it’s a very stable beta.
Those errors may also show up as result of faulty RAM.
That was actually the first thing I thought of, Zyndstoff. The RAM I have now is actually fairly new though: it is only 11 months old installed after my other RAM (OCZ) developed faults galore and caused loads of BSODs. OCZ later replaced the 2GB set under warranty and generously sent me new 4GB set instead…very nice too, but I’d already added 4GB of Kingston HyperX so now it is spare ;D Anyhow, unnecessary story over with, I still checked the new Kingston memory out, just in case it has also developed faults, but after an hour or so of checking no problems showed there at all. I checked the new boards for over 4 hours when I installed them, and they showed no problems then either. I’m pretty certain the problem isn’t the memory therefore.
As long as it does not reoccur, don't worry.
Well, yes, fair advice I suppose. Just used to ultra stability of XP and no BSODs without good cause. Whenever there is a BSOD I can usually uncover what has caused it: either something has changed or it's faulting hardware. In this case nothing has changed and hardware checks out okay.
...then you might want to try the Beta 6.0.1044 - you could do that anyway, it's a very stable beta.
Yeah, okay, good idea. I tried the first beta and had a few problems so that's why I'm back with 6.0.1000. But if this latest beta is near final then I'll certainly give it a go.