hello,
I have been having this issue a number of times, it has happened 3 times very recently and i am needing to get this sorted out.
the file aswsp.sys is causing this issue.
I have uploaded a minidump to the ftp server for you,
it is named neil rowlands, tremault, aspwsp.
I could not upload a memory dump because i had small free space and windows decided to delete it.
This happens a lot, not only on win7 x64, also on other OSs. I see this issue very often on winXP 32. It is a long standing bug, that -for some reason- hasn’t been completely fixed. It seems it’s more likely to happen when you upgrade avast over an older version. Try removing all traces of avast and doing a clean installation. This solved the problem in many cases.
ok thank you
how do I make sure I remove all traces?
If I were to do this on my own I would uninstall, then delete the avast folder. would that be enough?
I suggest an installation from scratch:
- Download the latest version of avast! Uninstall Utility and save it.
- Download the latest avast! version and save it.
- Uninstall avast from Control Panel (if possible). If, for any reason, you can’t run it, try booting in Safe Mode and doing it from there. Anyway, boot after that.
- Run the avast! Uninstall Utility saved on 1. If, for any reason, you can’t run it, try booting in Safe Mode and doing it from there. Anyway, boot after you’ve run it.
- Install avast! using the setup saved on 2. Boot.
- Register your free copy or add the license key for Pro. Or even upgrade your key from old versions.
- Check and post the results. If, for any reason, you did not solve, try doing the step 3 in Safe Mode anyway.
@tremault, you’re still using 6.0.1091.0 version, this bug was already fixed… please update your avast.
hi PK, my avast installation informs me that I am using 6.0.1289. is it bugged?
thanks Tech, I will attempt those steps you outlined for me.
I still see all your drivers are from 6.0.1091 version, e.g.:
Image path: \SystemRoot\System32\Drivers\aswTdi.SYS
Image name: aswTdi.SYS
Timestamp: Mon [b]Apr 18[/b] 19:16:21 2011 (4DAC71E5)
FileVersion: [b] 6.0.1091.0[/b]
ok thanks.
that must be causing some issues!
but anyway, i cleared it all off using the above method and it appears to have been behaving differently from before.
can’t say if it has solved the BSOD issue but i guess it must have if it was a messed up install previously.