system hangs after 1 hour

  • Thread starter Thread starter Jim Serino
  • Start date Start date
J

Jim Serino

the only way is to physically power off the system to get
it back.

Disabled disanled sygate firewall same thing.
Disabled Avast Anti-virus Same thing.

This all happend after I did some Microsoft installs and
upgraded the sygate to its latest built. I used the system
restore to go back after I did the both installs. But the
problem was still there download the newer sygate firewall
but have not reinstalled it.

I then went to the task manager and found after the reboot
a run away process teatimer.exe it was eating up memory
thereby not allowing anything to be accessed after about 1
hour time frame. I couldn't even shut the system down the
proper way nor would it accept any keyboard command it was
that bad.

I rebooted and removed and watched thru the task manager
as the teatimer was eating up memory like a termite thru
wood. I stopped it and the system is ok for now but as
soon as I reboot the problem will be there again.

This all started after I downloaded the latest Microsoft
patches late last week for XP and Internet Explorer. No I
have not installed the XP beta sp.

I am writting this from my main system a windows 2000 pro
workstation. I spent last thrusday downloading the patches
and sygate firewall new build. It is working fine.

TO contact me since I do not use the newsgroups too often
since I hate SPAM of all kinds is thru my email address
jim.serino(removethis)@mindspring.com. The last time I
time I used a newsgroup was to look up information on
OpenVMS.

What can I do to fix the teatimer issue beside filling up
the kettle with water? I have the gateway disk for the
Operating system what is the Teatime file called so I can
delete the one the sytem disk and reinstall it from the
CD. This seems to be my only course at this.

thanx in advanced
Jim
 
I may have been a bit hasty. I found that teatimer.exe was
the sysbot -search and destroy adware software. It was the
beta version so I may have to search for the non beta
version from that downunder country and see what happens
with it. Again this all started after I installed those
patches from Microsft.
 
Back
Top