SnowManInHI
MIS
100 machines running Win NT 4.0 SP6a
VirusScan v.4.5.1 SP1
Engine 4.2.40
Dat 4.0.4271
Most machines are running PII 400 with 64 meg ram, also occurring on machines with faster processors and up to 384 meg ram.
EPO version 2.5.1.213
Randomly throughout the day most machines are getting the following error:
Dr Watson:
VsStat.exe
Exception: access violation (0xc0000005)
Normally when this happens, the system is being extremely sluggish, McShield is running 90% CPU usage.
I have noticed that if you open the about dialog box, this will usually trigger the Dr Watson error if the system has not had the error yet today. Once the error occurs, the anti-virus software will stop functioning but will reenable after a few hours if the user does not reboot the system.
Other symptoms on the machine which may not be related are that the systems are really sluggish on Monday mornings, McShield will run at 90% or higher CPU utilization for hours, rebooting the system again will stop the McShield from monopolizing the systems. If left long enough the McShield will eventually stop killing system performance, but it can be 10-11 hours. We used to be getting tons of Dr Watson errors in regards to McShield, Scan32, Webscanx, naimag32, but uninstalling and reinstalling 4.5.1SP1 eliminated all but the VsStat.exe ones.
Anyone have any ideas on why we are getting the VsStat.exe error?
VirusScan v.4.5.1 SP1
Engine 4.2.40
Dat 4.0.4271
Most machines are running PII 400 with 64 meg ram, also occurring on machines with faster processors and up to 384 meg ram.
EPO version 2.5.1.213
Randomly throughout the day most machines are getting the following error:
Dr Watson:
VsStat.exe
Exception: access violation (0xc0000005)
Normally when this happens, the system is being extremely sluggish, McShield is running 90% CPU usage.
I have noticed that if you open the about dialog box, this will usually trigger the Dr Watson error if the system has not had the error yet today. Once the error occurs, the anti-virus software will stop functioning but will reenable after a few hours if the user does not reboot the system.
Other symptoms on the machine which may not be related are that the systems are really sluggish on Monday mornings, McShield will run at 90% or higher CPU utilization for hours, rebooting the system again will stop the McShield from monopolizing the systems. If left long enough the McShield will eventually stop killing system performance, but it can be 10-11 hours. We used to be getting tons of Dr Watson errors in regards to McShield, Scan32, Webscanx, naimag32, but uninstalling and reinstalling 4.5.1SP1 eliminated all but the VsStat.exe ones.
Anyone have any ideas on why we are getting the VsStat.exe error?