Avast stops running everytime I start a scan. I upgraded from 4.8.1169 to 4.8.1195 after I downloaded sp3 for XP.Scanned for infections but could not find anything. Did a boot scan with Avast and it found nothing. It always stops around 27,000 files. IT just disappears from the screen with no logs or scan reports. Computer seems fine, but there is always a chance of infection. I scanned with Malwarebytes and SUPERAntispyware and found nothing. I deleted them, but I will try again if you think I should. Thanks in advance.
You can:
- Update to 4.8.1201 version.
- Go to the program settings and turn on the creation of the report file (with “OK files” to be included as well in the report). This way, you can find out where the scan really stopped (it’s going to be close to the end of the report). After avast! disappears, check the end of the report file - the “troublesome” file is likely to be close to the end (close in the sense that this particular file will probably not be written in the report, but the previous one will be the last line, so it shouldn’t be hard to guess). We would certainly like to have this file - if it really causes problems to avast! - so that we could fix the problem.
The report file created (if you turned it on in program settings) will be (default location) at \Data\Report\Simple User Interface.txt
Create Report File is already checked. All the files are checked, including ok files. But when I checked the menu, status information, last scan results are greyed out. Will update to newer version.
This is all right. I mean, Home version just allow the last scan results available when the scanning finishes. When avast is closed, the results are removed.
Upgraded to 4.8.1201. Scan ran normally. Too big to copy/paste. Awaiting advice/instructions.
If the scan ran and completed normally I doubt that the log needs to be posted.
The idea of the log was to try and see where it got to when it stopped, from that it may have been possible to work out what it was scanning that cause any problem.
Keep the generation of the report for OK files enabled for the next few scans and if there are no problems then you should be able to disable the reporting of OK files.
I’ll suggest the same. Even it there are too many hard errors, maybe let just the infected ones to be reported.
Sounds good guys. I’ll report back in a couple of days after a few more scans and we can decide.
No problem, till then.
Hi guys
Ran a scan and it did it again. Here are the last few lines.The whole scan exceeds the limit.
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.2180_x-ww_522f9f82\GdiPlus.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.5512_x-ww_dfb54e0c [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.5512_x-ww_dfb54e0c\GdiPlus.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Networking.Dxmrtp_6595b64144ccf1df_5.2.2.3_x-ww_468466a7 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Networking.Dxmrtp_6595b64144ccf1df_5.2.2.3_x-ww_468466a7\dxmrtp.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Networking.RtcDll_6595b64144ccf1df_5.2.2.3_x-ww_d6bd8b95 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Networking.RtcDll_6595b64144ccf1df_5.2.2.3_x-ww_d6bd8b95\rtcdll.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Networking.RtcRes_6595b64144ccf1df_5.2.2.3_en_16a24bc0 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Networking.RtcRes_6595b64144ccf1df_5.2.2.3_en_16a24bc0\rtcres.dll [+] is OK
C:\WINDOWS\WMFDist11.log [+] is OK
C:\WINDOWS\wmp11.log [+] is OK
C:\WINDOWS\wmsetup.log [+] is OK
C:\WINDOWS\wmsetup10.log [+] is OK
C:\WINDOWS\WMSysPr9.prx [+] is OK
C:\WINDOWS\WMSysPrx.prx [+] is OK
C:\WINDOWS\Wudf01000Inst.log [+] is OK
C:\WINDOWS\xpsp1hfm.log [+] is OK
C:\WINDOWS\Zapotec.bmp [+] is OK
C:\WINDOWS_DEFAULT.PIF [+] is OK
SVC: .NET CLR Data [+] is OK
SVC: .NET CLR Networking [+] is OK
SVC: .NETFramework [+] is OK
C:\WINDOWS\System32\Drivers\Aavmker4.sys [+] is OK
Will await your response.
What? Does it stall?
Seems OK
The is OK is the last file scanned when, “Ran a scan and it did it again.” (the topic title, avast scan stops).
So it looks like it is stopping in the C:\WINDOWS\System32\Drivers\ folder. From the other files in the list it appears they are in alphabetic order so what is the file after C:\WINDOWS\System32\Drivers\Aavmker4.sys in alphabetic order ?
Unless it is actually baulking/stalling/stopping on Aavmker4.sys, which is an avast driver file.
I’m at a bit of a loss as to why this would be an intermittent problem if it were a specific file then I would expect it to stop on every scan and stop at the same point. Unfortunately we cant see where it has stopped previously only in this report.
We need some input from one of the Alwil team I think.
Hi guys
Just ran another scan and it stopped in the same place. To answer your question(tech), it does not stall, it just scans about 22,000 files or so and just disappears, done. Nothing seems to be wrong with the system, for some reason, it just won’t scan the entire system. I can surf, run multiple windows at the same time, etc. There are no symptoms of any problems other than the scan itself. Here are the last lines again:
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_91481303 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_91481303\mfc80CHS.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_91481303\mfc80CHT.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_91481303\mfc80DEU.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_91481303\mfc80ENU.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_91481303\mfc80ESP.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_91481303\mfc80FRA.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_91481303\mfc80ITA.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_91481303\mfc80JPN.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFCLOC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_91481303\mfc80KOR.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05\mfc80.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05\mfc80u.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05\mfcm80.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_3bf8fa05\mfcm80u.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a\COMCTL32.DLL [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.10.0_x-ww_f7fb5805 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.10.0_x-ww_f7fb5805\COMCTL32.DLL [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.1515_x-ww_7bb98b8a [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.1515_x-ww_7bb98b8a\comctl32.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2982_x-ww_ac3f9c03\comctl32.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.5512_x-ww_35d4ce83\comctl32.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.0.0_x-ww_2726e76a [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.0.0_x-ww_2726e76a\MSVCIRT.DLL [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.0.0_x-ww_2726e76a\MSVCRT.DLL [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.10.0_x-ww_d8862ba3 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.10.0_x-ww_d8862ba3\MSVCIRT.DLL [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.10.0_x-ww_d8862ba3\MSVCRT.DLL [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.2600.2180_x-ww_b2505ed9 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.2600.2180_x-ww_b2505ed9\msvcirt.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.2600.2180_x-ww_b2505ed9\msvcrt.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.2600.5512_x-ww_3fd60d63 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.2600.5512_x-ww_3fd60d63\msvcirt.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.CPlusPlusRuntime_6595b64144ccf1df_7.0.2600.5512_x-ww_3fd60d63\msvcrt.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.0.0_x-ww_8d353f13 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.0.0_x-ww_8d353f13\GdiPlus.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.10.0_x-ww_712befd8 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.10.0_x-ww_712befd8\GdiPlus.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.2180_x-ww_522f9f82 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.2180_x-ww_522f9f82\GdiPlus.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.5512_x-ww_dfb54e0c [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.2600.5512_x-ww_dfb54e0c\GdiPlus.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Networking.Dxmrtp_6595b64144ccf1df_5.2.2.3_x-ww_468466a7 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Networking.Dxmrtp_6595b64144ccf1df_5.2.2.3_x-ww_468466a7\dxmrtp.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Networking.RtcDll_6595b64144ccf1df_5.2.2.3_x-ww_d6bd8b95 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Networking.RtcDll_6595b64144ccf1df_5.2.2.3_x-ww_d6bd8b95\rtcdll.dll [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Networking.RtcRes_6595b64144ccf1df_5.2.2.3_en_16a24bc0 [+] is OK
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Networking.RtcRes_6595b64144ccf1df_5.2.2.3_en_16a24bc0\rtcres.dll [+] is OK
C:\WINDOWS\WMFDist11.log [+] is OK
C:\WINDOWS\wmp11.log [+] is OK
C:\WINDOWS\wmsetup.log [+] is OK
C:\WINDOWS\wmsetup10.log [+] is OK
C:\WINDOWS\WMSysPr9.prx [+] is OK
C:\WINDOWS\WMSysPrx.prx [+] is OK
C:\WINDOWS\Wudf01000Inst.log [+] is OK
C:\WINDOWS\xpsp1hfm.log [+] is OK
C:\WINDOWS\Zapotec.bmp [+] is OK
C:\WINDOWS_DEFAULT.PIF [+] is OK
SVC: .NET CLR Data [+] is OK
SVC: .NET CLR Networking [+] is OK
SVC: .NETFramework [+] is OK
C:\WINDOWS\System32\Drivers\Aavmker4.sys [+] is OK
Are you saying the scanner completely disappears? Just like that?
Then it looks like a stack overflow problem…
Can you please check the folder \data\log - are there any files called unpXXX.mdmp in there? (xxx is a random number)
Thanks
Vlk
here you go: unp157256947.tmp.mdmp
The file says it is empty, but windows will not open it.