lsass.exe process 100% CPU usage

From: Víctor Martínez (vmartinez@consorciodeaguas.com)
Date: 04/16/03 

From: "Víctor Martínez" <vmartinez@consorciodeaguas.com>
Date: Wed, 16 Apr 2003 17:09:57 +0200

I have the following problem,
the process lsass.exe is running on my NT server 4.0 and it´s consuming all
CPU usage time. That means that other processes or applications i want to
execute goes extremely slow.
I have tried several things, from reinstalling service pack to stopping the
process manually or analyzing the machine for searching a virus.
None of these actions resolved the problem.
Have anybody any idea about what is happening on my machine?
Thanks.

Relevant Pages

  • Re: Not quite where Im going
    ... and consuming no licences. ... therefore consume a Client Access licence. ... If you have 5 workstations and the server, and any 3rd party software on ... Director - Business Technology Partners Pty Ltd - Microsoft ...
    (microsoft.public.windows.server.sbs)
  • Store.exe consuming lots of RAM (1GB)
    ... W2k server running Exchange 2000. ... RAM, and appears to be slowing the server down. ... recall Store.exe ever consuming that much RAM before and it seems to have ...
    (microsoft.public.exchange2000.information.store)
  • Store.exe eating up RAM (around 1GB)
    ... W2k server running Exchange 2000. ... RAM, and appears to be slowing the server down. ... recall Store.exe ever consuming that much RAM before and it seems to have ...
    (microsoft.public.exchange2000.information.store)
  • Store.exe eating up lots of RAM (around 1GB)
    ... W2k server running Exchange 2000. ... RAM, and appears to be slowing the server down. ... recall Store.exe ever consuming that much RAM before and it seems to have ...
    (microsoft.public.exchange2000.information.store)
  • Re: Issues with latest released patches from MS
    ... This virtuell Windows server is currently running solo on the HW ... Last week it was running perfectly just under 200Mb Ram in running ... After reboot it consuming directly 400-500Mb RAM and from there ...
    (microsoft.public.windows.server.sbs)