This file (asvwmm.sys) is the reported cause of a SYSTEM_SERVICE_EXCEPTION in my WS2008R2 server, which started happening at the end of last week (Thursday 7th). Up until then, AVG Business had been fine.
I can’t resolve this because I can’t disable the services and the system crashes before I have a chance to complete any action (eg, uninstall).
I can’t use the domain Admin account in safe mode (“no login servers to service the request”) and my local Admin account clearly isn’t using the password I thought it was >:(
Well spotted - it has been a frustrating few days and my fingers were faster than my brain…! (In my defense, I did have AVG on there previously, but hoped Avast would suit me better!)
yeah this is a tough one =( if you cant even get logged into the box at all. so you get no “Safe Mode (with networking)” option when you hit F8 at boot up? that option wont show during a normal restart after the crash, you have to hit F8 just as its leaving BIOS mode and starting to load the OS. then you get a safe mode screen with about 8 options on it.
ok a little confused. you said to rename the file .zip, but if i do that, any attempts to open it are met with “this is not a valid compressed file” type of messages. from windows, winrar and 7zip as well. it does appear to be compressed though, as it is half the size of the file i am supposed to replace? i downloaded it twice to make sure it wasnt corrupted the first time or something. no joy =(. please advise.
I believe I have seen this in the forums before, changing the file type to .txt by all accounts it is saved in the forum.avast as a text file, corrupting the archive. So downloading and changing the file type back, is no longer recognised as an archive file.
I think it was Vlk that mentioned this some time ago, might be worth checking with Chocholo ‘Petr’ if that is still the case with changing file types.
will do! it will likely be tomorrow morning or later this evening before i can replace the file. there are 2 production VMs running on this box so I cant reboot it in safe mode to replace the file until after business hours. thanks again!
seems to be stable now. I just applied the new file and the server came up. has not BSOD again, but its only been about 15 minutes. so far so good though! thank you =)
… And thanks for same! Your response is appreciated.
Unfortunately I can’t do anything with it, as I can’t do anything to asvwmm.sys - I can’t delete it, rename it or replace it - I get a Windows popup saying “permission denied”. I tried to stop the services before an enforced reboot, but I can only stop the base Avast service, which stops the AV, but I can’t stop either of the other two services, which appear to be monitoring or UI related, so one or other is using this file.
What’s really annoying, and what I don’t understand, is why this suddenly started happening when - as far as I know - nothing has changed on that machine since Avast for Business was installed.
It’s looking as though I’m going to have to trash a system that has been running happily for about 7 years, which is particularly irksome; it’s a bog standard Dell server running WS 2008 R2, nothing esoteric. Unfortunately it won’t stay up long enough for me to get data off it, and as it’s a RAID I can’t just plug a disk into another machine.
The irony is that a product intended to protect my server has f- ah - broken it, and means that I won’t touch this product again with a bargepole; I certainly won’t be recommending it - quite the reverse - it’s clearly not stable. (Consequently, I’m also concerned about the consumer version, for which I have paid, and wondering if it might do something similar to my desktop - something keeps waking it from sleep.)
Shooting from my hip here since I’ve never ran Avasts Business. Open Avast, an in Settings or options, look for Troubleshooting and deactivate Avast self-defense module. Try to replace the file Sigmon sent you.
while yes, there was a problem with the avast .sys file, its not their fault you don’t know your local admin password. you could do the replacement in safe mode if you had not forgotten it, and I am still unclear as to why you can not use safe mode with networking. Hardly seems fair to call the product unstable due to an issue a few users had on one of many supported operating systems.
