BSODs on XP due to Avast driver aswStmXP.sys

Got a second BSOD this month on my XP - while nothing was happening.

The immediate culprit seems to be the Avast AV Free driver aswStmXP.sys, which is version 17.9.3754.0, last modified December 21, 2017, 1:06:34 PM.

My XP machine is fully updated using the POS hack. With the reg key and driver changes instigated by the AV companies for Meltdown and Spectre, I wonder whether there isn’t a new conflict.

I have a zip with ALL the BSOD info. How can I upload my zip with all the BSOD info to an Avast engineer?

Thanks.

I have attached the picture of the BSOD showing the Avast driver aswStmXP.sys as the cause.

I’ll get this escalated now.

Well my XP Pro SP3 system (in signature), no POS hack and no BSODs either.

Even with the Compat registry key (I have the reg key), I don’t know if there would have been a Windows Update KB for it. There certainly wasn’t for my XP SP3 system. Then again systems running XP are also more likely to be running old CPUs ones that aren’t vulnerable to the Meltdown CPU issue.

I have tried finding what CPUs are effected and I can find nothing indicating that my Core2Duo E8300 CPU is effected.

There is also the AMD CPUs (if you have one) that apparently aren’t effected and for a while MS pulled the WU KB as it was breaking systems.

AMD’s are only effected by Spectre.

Alikhan - How do I send to the proper Avast engineer my zip of the BSOD-related files, including my mini-dump?

Unfortunately, David R and Bob’s comments above are not on point. Avast’s XP driver is causing BSODs, so this needs attention.

Thanks.

It’s been escalated and Avast is apparently looking at something from the replies I’ve seen.
You’ll need to wait for them to respond.

I responded to your having BSOD on XP as I also have XP and no BSOD, so it doesn’t appear consistent across the board.

You mentioned Meltdown and Spectre queried “I wonder whether there isn’t a new conflict.” If there is I haven’t bumped into it.

Hi Glnz, if it is possible, please attach zipped mini-dump file to this thread. Tnanks

Not possible, he can upload it to the Avast FTP server, though.
You can upload your minidump(s) here: ftp://ftp.avast.com/incoming/

Martin and Asyn - I would prefer to upload to you directly rather than attach here.
EDIT – Asyn, I copied my BSOD zip to your link (which I opened on my PC as if it were a folder). Its name is glnz BSOD 1-24-18.zip. Please confirm you got it.
Thanks.

Here you go: https://support.avast.com/article/160/

Asyn - I copied my BSOD zip to your original link ftp://ftp.avast.com/incoming/ (which I opened on my PC as if it were a folder). Its name is glnz BSOD 1-24-18.zip.
Please confirm you got it.

Thanks Glnz and Asyn. I got the file.

@glnz

I’M a bit confused concerning your

Avast AV Free driver aswStmXP.sys, which is version 17.9.3754.0, last modified December 21, 2017, 1:06:34 PM.
For I`ve on my MAIN machine this Free version [b]17.9.2322 (Build 17.9.3761.278)[/b]!

=Snake=

Snake - my Avast Free is the same version as yours.

Above in this thread, I gave the version info for the particular avast driver .sys file that apparently triggered the BSODs.

Thanks.

I knew it, but wasn’t quite sure, that you updated to the ‘last build 3761.278’, for you had ‘3754.0’!
That means to me: your machine isn’t up to date yet.
:wink:
=Snake=

Snake - interesting.

On your XP machine, please search for your driver aswStmXP.sys, check its Properties, and let us know what version you see.

Thanks.

My latest μUpdate is 335 and the version of the driver file “aswStmXP.sys” is 17.9.3754.0 (Avast Stream Filter). Have no problems with Windows XP sp3 x86 (updates as of December 2017) with a BSOD.

:slight_smile:

Hey, you should recognize, that your XP machine needs a so called ‘micro update’ (from Avast, that should bring it to that build version ‘3761.278’) I have!!!
I would only follow your thought (searching for ‘aswStmXP.sys’), after you have updated to the last version of the build!
:wink:
=Snake=