You can also attach text based files like .log or .txt to the posts.
More importantly did it get the job done ?
If not try the next tool, rogue remover.
This one you should upload to virustotal for further analysis as avast didn’t detect it (see below).
Rogue.Dropper/Gen
C:\WINDOWS\SYSTEM32\LPHCTSDJ0EJF1.EXE
This is strange as a bmp file shouldn’t have any potential to be a trojan, but check it at VT also.
Trojan.Unknown Origin
C:\WINDOWS\SYSTEM32\PHCTSDJ0EJF1.BMP
These make me think that the two items above might not be malware, as in tsese ones SAS says they aren’t Harmful and are from sysinternals, well the file names are so close to the ones above they would most likely be for the same sysinternals bluescreen capture.
NotHarmful.Sysinternals Bluescreen Screen Saver
C:\WINDOWS\SYSTEM32\BLPHCTSDJ0EJF1.SCR
C:\WINDOWS\Prefetch\BLPHCTSDJ0EJF1.SCR-3A9C0701.pf
Also the prefetch folder doesn’t have a copy of the file just the HDD location referenced so it can be loaded quicker.
Tracking cookies are nothing to get concerned about, I have that option deselected in the SAS Scan settings. However you could certain;y do with periodically clearing out your cookies, yours are a mess, I don’t think I have see so many and this is the reason the log is so big.
You could also check the offending/suspect file at: VirusTotal - Multi engine on-line virus scanner and report the findings here.
If multiple scanners detect malware in either of the uploaded files (I would think unlikely) you should send a sample to avast.
Send the sample to virus@avast.com zipped and password protected with the password in email body, a link to this topic might help and undetected malware in the subject.
Or you can also add the file to the User Files (File, Add) section of the avast chest (if it isn’t already there) where it can do no harm and send it from there (select the file, right click, email to Alwil Software). No need to zip and PW protect when the sample is sent from chest. A copy of the file/s will remain in the original location, so any further action you take can remove that.
After uploading the files mentioned for scanning, clear your cookies I would suggest that you run SAS again but this time do a Full rather than quick scan it will look deeper as whatever was responsible for the fake alerts isn’t detected.
Or you could run the rogue remover first.