There's a difference between "can't make an assumption" and "don't make an assumption". I would have preferred a short sentence instead of a already written text, because you were to lazy enough to write one. I've seen on the forum the same post you made for someone else, and you just used your Ctrl+V for my topic too... Am I correct? It's ok, I'm just saying... I expect from from an old veteran member who helps people to at least post different information for them, and not just paste some of his own stuff caring about his post counter...
No offense, I think I did posted a proper report and not some partial information, and I did think that it looks like a post from an experienced user. Now I'm interested if it's a real problem in avast! or it's just my machine, that a reinstallation of Windows can fix easily...
Can we at least get to the core of the problem instead of fighting with each other?
1. Oh god another avast! evangelist...
2. Do other regular people use this forum?
3. Also if you point your finger at me, then I'm not the only one who continued the war!
4. So yeah, as I said before logical explanations are always welcome!
So yeah, as I said before logical explanations are always welcome!I'm still trying to figure out the logic. ???
If you get a bsod next time (or any other member here), it's better to let us know (e.g. send me a PM).
Your crash was caused by a bug in aswsp.sys driver (antirootkit part), I think it was already fixed.
This problem should be fixed in next (R3) release.That is definitely awesome guys! Good to see that this problem will be fixed in the next revision of the software. I'm a loyal fan of your antivirus system, and recommended avast! for many many people over the years. Thank you very much avast! team and keep up with the great work!
I'm a loyal fan of your antivirus system, and recommended avast! for many many people over the years.Thanks for spreading the word :)