Yesterday, the version of avast was updated on my system automatically. I rebooted this morning, and get to the windows login screen. After I log in, the system then crashes, giving a blue screen of death. The screen disappears quickly, but I am able to see the file AAVMKER4.SYS mentioned on the screen. Every time I reboot and login, this happens.
So I booted into safe mode and renamed c:\windows\system32\drivers\aavmker4.sys. When I rebooted, the system worked properly again, except the Avast icon in the tray has a small red icon in it, obviously indicating that it isn’t running properly. Properties on aavmker4.sys indicates it is version 4.6.652.0.
I’ve searched the forums and found some other threads with similar problems, but didn’t find the exact issue, nor did I find any solutions. Is anyone experiencing this issue? Any solutions on how to resolve it besides removing Avast? I love Avast and would hate to have to live without it.
I have some minidump files available if that will help.
I may have posted here prematurely. While aavmker4.sys was renamed and avast was not running correctly, I used the update options for both iAVS and Program. One of these installed a new aavmker4.sys file. When I rebooted, I no longer got a BSOD. Perhaps I just got a corrupted aavmker4.sys file on the first install.
If any further problems occur, I’ll make sure to post them here.
I had the same problem today and some weeks ago.
My machine has XP PRO SP2 with the latest patch and some very restrictive permissions on system folders and GPO, so I thought that the BSOD depended by this “hardening” conflicting with the antivirus.
Weeks ago (at the first BSOD), I unistalled Avast Free and reinstalled it and I had no problem for a couple of week.
Today the problem is present again.
I started in “safe” mode + network and I succeded in download the last update of the Avast SW. Then, I restarted and the whole thing went ok.
I’m wrinting at 15 minutes after the reboot so I don’t know if the problem is actually resolved.
Best regards.
only for your concern:
w2k avast 4.6.744 / vps0603-3.
entering in a https page and BSOD… some data of the page:
Page fault in non paged area.
address EB75A415 at EB758000 / DateStamp 43a7f5f7 - Aavmker4.sys
well, that’s it. New boot and always seems to work fine.
\windows\minidump folder
send me the latest *.dmp file
anyway, thanks for your numbers from BSOD, i found it was a problem in scanning - but still, i think it’s hw error (according to statistics: from the dumps of this file), so try some memory tests (www.memtest.org)…