Lsass.exe problems

[ZeroDread]

I have done research on this is file. Its on my task manager. It is killing my resources. Usually its about 2,000k or so. But at times, for no reason, it jumps to 40,000k to 70,000k. The only way i know how to get rid of it is to reboot.....

any suggestions!

**EDIT**
BTW: XP pro is my operating system

[DimViesel]

Oh yeah ...good ol' Lsass.exe. This is termed GODware. It is installed by God and keeps track of any prurient activity on your computer, the usage of your resources will be linearly proportional to such activity. It was coded by the Angel Gabriel (not Peter Gabriel as many have said . . .doh!) if you uninstall or attempt to by-pass you have sold your way to certain damnation.

Microsoft have an elucidating evangelical article which stipulates all this in point form:
Symptoms of the Lsass.exe process ceasing

On a more serious note this may also be informative:
"SUMMARY When you first install the Active Directory Connector (ADC), the Lsass.exe process consumes 95-100 percent of processor usage.
MORE INFORMATION
This behavior is to be expected.

The Local Security Authentication Server (Lsass.exe) process receives authentication requests from Winlogon and calls the appropriate authentication package to perform account verification and validation. When you install the ADC, for each modification made to the Windows 2000 Active Directory Schema, a call is made to Lsass.exe to verify that the ADC service account has the correct permissions necessary to modify the Active Directory Schema.
Last Reviewed: 1/31/2002
Keywords: kbinfo KB237434"
From:Active Directory Connector Setup

[ZeroDread]

Hmmm, thanks for the links, but what am i suppose to do? Live with it.....I didnt have this problem on my other Xp pro..

[DimViesel]

This IS the prob. with Microsoft OSes its not clear what Microsoft intended and its impossible to make them accountable, or to find the authoritative source that will allow you to formulate your own conclusion or solution.
There is something which attempts to address these very issues by the nature of its creation and following this ideology . . .have you heard of something being developed for desktops called . . . L I N U X, I think, or something.

[Aedan]

LSASS, if you hadn't worked it out already, is the process that handles all security on the system. It handles authentication, permission checking and many other security features.

In my limited experience with problems with LSASS, they tend to be caused by corrupted information in the registry.

Áedán

[timbob2469]

ZeroDread, this is what I found:
LSASS.exe is responsible for running certain groups of drivers (.dlls) associated with several background services in windows xp.
If this file is using a lot of cpu reserve it is probably because it is sitting on quite a few .dlls whilst attempting to launch one or two services.
The only way to contol the services that windows runs in the background is to roll up your sleeves and get under the bonnet
and configure them one by one
You'll find them here: Control Panel / Administrative Tools / double click the last icon "Services"
Expand the page to get a clearer view then click once on the first icon "Alerter". In the left hand panel will be a description of what this service does. Now right click the icon and choose "Properties" from the drop down menu, in the center panel next to "Startup type:" is a drop down allowing you to set it to one of three modes, it is here that you can configure each service in turn.

here's a tip:
LSASS.exe runs Netlogon which on a home pc you should really dissable - unless of course you actually do have your own Domain!!


Also this might help if you don't have Norton Windoctor:
http://www.pcnet-online.com/picks/registryfirstaid.htm
free to try for 21 days. Or you could try and run Drwtsn32.exe
or do a search in winxp help for "registry checker" which is part of win98 and it willpoint you in the possibly right direction. Lastly, you could try the repair function in TweakUI in winxp powertoys.
bob