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?
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.
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.
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.
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.
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.
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!