echy wrote:
> Hello
>
> I have a P111 700 MHz computer, 256 MB RAM, many GB of hard disk space,
> Microsoft XP Pro SP2 with all patches. It has a strange problem
> seemingly related to my anti virus software.. I use eTrust Vet
> Antivirus software - www.vet.com.au.
>
> I have not changed software or added hardware since installing the anti
> virus software. Vet is my software of choice, having used it for many
> years without fault. I have it on several computers but only the above
> is having problems. It is genuine software registered and paid for. This
> computer is not part of a network.
>
> I am getting Stop** errors all the time - each time I boot the computer
> it gives a Stop error after between 1 & 40 minutes of running. HOWEVER
> when I remove Vet Antivirus the problem disappears say 8 out of 10 times.
>
> I am wondering if anyone can throw any light on this one.
>
> Thanks
> Echy
>
> ** Stop errors mainly 0x000000C5, 0x00000050
This is a pretty old computer. When was the last time that the
case was opened and the interior given a thorough cleaning of
lint and dust. And the fans and their shrouds and ducts? Also,
when was the last time that the peripheral cards, memory, ribbon
cable connectors, etc., were checked and re-seated?
If the hardward checks out OK, then what is the state of the
hard drive(s)? Recently defragged? Scandisk checked out OK?
Follow the recommendations of Shenan Stanley in regards to the
status of the drivers. Did a complete anti-virus scan as well as
anti-adware and anti-spyware scans?
The 0x000000C5 error is "access violation" and can point to a
variety of things. Take a look at DrWtsn.log to check for an
application that might possibly be triggering the stop error.
Thanks for your reply.
Re: "When was the last time that the case was opened and the interior
given a thorough cleaning of lint and dust" ...... etc.. - I did that
a day or two ago & was very amazed at the amount of lint & dust inside.
Re: "If the hardware checks out OK, then what is the state of the hard
drive(s)? Recently defragged? Scandisk checked out OK?" - done and OK.
Re: "Did a complete anti-virus scan as well as anti-adware and
anti-spyware scans?" - all up to date - anti virus ( CA's eTrust Vet) ,
Ad-Aware, CWShredder, CCleaner, Spybot S & D, Spyware Doctor, Spyware
Blaster, Spyware Guard.
Any suggestions for any others welcome.
About to look at Dr Watson log & I am getting latest drivers.
Thanks again
Echy
Ghostrider wrote:
>
> echy wrote:
>
>> Hello
>>
>> I have a P111 700 MHz computer, 256 MB RAM, many GB of hard disk
>> space, Microsoft XP Pro SP2 with all patches. It has a strange problem
>> seemingly related to my anti virus software.. I use eTrust Vet
>> Antivirus software - www.vet.com.au.
>>
>> I have not changed software or added hardware since installing the
>> anti virus software. Vet is my software of choice, having used it for
>> many years without fault. I have it on several computers but only the
>> above is having problems. It is genuine software registered and paid
>> for. This computer is not part of a network.
>>
>> I am getting Stop** errors all the time - each time I boot the
>> computer it gives a Stop error after between 1 & 40 minutes of
>> running. HOWEVER when I remove Vet Antivirus the problem disappears
>> say 8 out of 10 times.
>>
>> I am wondering if anyone can throw any light on this one.
>>
>> Thanks
>> Echy
>>
>> ** Stop errors mainly 0x000000C5, 0x00000050
>
>
>
> This is a pretty old computer. When was the last time that the
> case was opened and the interior given a thorough cleaning of
> lint and dust. And the fans and their shrouds and ducts? Also,
> when was the last time that the peripheral cards, memory, ribbon
> cable connectors, etc., were checked and re-seated?
>
> If the hardward checks out OK, then what is the state of the
> hard drive(s)? Recently defragged? Scandisk checked out OK?
> Follow the recommendations of Shenan Stanley in regards to the
> status of the drivers. Did a complete anti-virus scan as well as
> anti-adware and anti-spyware scans?
>
> The 0x000000C5 error is "access violation" and can point to a
> variety of things. Take a look at DrWtsn.log to check for an
> application that might possibly be triggering the stop error.
