I’ve had this issue for a while now, and initially disabled my scheduled nightly full scans. I decided to do the “Safe Mode”, uninstall utilitity, full install last night and ran a full scan just afterwards.
Same BSOD as normal (after a full scan) greeted me when I came to the computer this morning.
My machine runs 24/7 otherwise with no slow downs, and no issues. I only get this when running an AVAST full scan.
I have uploaded my minidump to the FTP server (ftp.avast.com) into the “incoming” folder.
I don’t believe it is the nightly full system scans that is the problem, but I would say that is overkill.
With a resident on-access antivirus like avast, the need for frequent on-demand scans is much depreciated. For the most part the on-demand scan is going to be scanning files that would be otherwise be dormant or inert. If they were active files then the on-access file system shield would be scanning them before being created, modified, opened or executed.
You could try disabling the self-defence module in the meantime and see if that resolves it.
Thanks for the reply DavidR. Have to say that I have been an AVAST user for quite some time and suggest Avast as AV for all my family and friends, so have been a bit miffed that I couldn’t identify this issue and resolve it.
You are of course right in saying that nightly scans are really overkill, but the machine is on 24/7, so I use that overnight time to confirm cleanliness. I think a weekly scan would be sufficient tbh.
I have now turned off the self-defence module and will try another full scan later, and post a reply with the outcome!
Okay so ran the full scan again this evening… still BSOD I’m afraid
I was near the machine when it “went” and it was mid scan… it had run for 40 minutes as far as the Scan Log could tell me… (Avast shows it as a completed scan!)
I have uploaded the minidump again to the FTP server into the “incoming” folder.
Some more info on my machine:
Core i5 2500K
4Gb RAM
Windows 7 Ultimate 64-Bit
Avast version:7.0.1426
When you upload the dumps do you give it a unique name (e.g. your username_dump_report_number.zip, etc.) and place that file name in the topic.
I would also suggest placing a readme.txt document in the zip file containing the dump/s, outlining the problem and a link back to this topic. Both of these measures help give it a unique ID and enable them to associate the dumps with your problem.
I will try and have one of the avast team look into it, but the unique identification of your uploads and link to the topic helps.
I have just uploaded a zip file to the FTP server called “chargenut-bsod-dump.zip”, which contains a text file of the description of what I have done so far and what is happening (called “chargenut-bsod-description.txt”) and also the minidump file (called “chargenut-060612-21465-01.dmp”).
There is a link URL to this thread in the top of the txt file as well.
I have had a response, stating that this BSOD has been fixed (in an internal build I believe), so when the next program update is released this will have been resolved.
In the meantime I would suggest just doing a Quick scan rather than a Full scan, the quick scan does the files/areas that are most at risk of attack/infection. The full scan goes a little further stuff at a lessor risk:
With a resident on-access antivirus like avast, the need for frequent on-demand scans is much depreciated. For the most part the on-demand scan is going to be scanning files that would be otherwise be dormant or inert. If they were active files then the on-access file system shield would be scanning them before being created, modified, opened or executed.
I have avast set to do a scheduled weekly Quick scan, set at a time and day that I know the computer will be on. If for some reason my system wasn’t on, no big deal I will catch up on the next scheduled scan.
