lsass.exe error loop at bootup

[roley]

I assume that people who had this problem also had updated virus software running at the time the problems started and am assuming you update WinXP regularly...

Otherwise, you could be having Sasser worm problems.

However, Sasser may not be the cause if users were unable to use System Restore to get to a pre infected point.

After that, much of the above may actually be the only way apart from getting someone else to fix it for money

Roley

[BengalTigger]

To all of you unable to achieve a successful XP logon screen due to the LSASS.EXE error...I feel your pain. I too have read all of the suggestions that assume you are in windows, while being doomed to stare instead at the empty blackness of a screen highlighted only by an LSASS.EXE error.

Yes, I have Norton AV 2004 up to date, and scanning regularly. I also have Windows Update set to download automatically and have kept my machine up to date with all security fixes.

I tried all of the F8 boot options, Windows Repair and Windows Recovery but all ended in the same error. I haven't yet formatted my hard drive. I plan to try Frogger90's suggestion next. But admit it is likely my last attempt. Wish me well!

While most seem to experience this as a result of the Sasser virus that is not the only cause. Last week I was uninstalling a modem and the uninstall froze. After waiting long enough to uninstall 50 modems, I finally rebooted my machine, and was presented with the greatly-feared "Lsass.exe error, Object not found". I used Windows Recovery to search through file folders looking for tell-tale signs of Sasser virus (such as avserve, avserve2, etc file names), but did not find any of them so I am betting my case was related to corruption from uninstalling the modem drivers and not a virus. Frogger90's post is the first post of literally hundreds I have read that give me some hope of fixing it without formatting my HD.

I don't pretend to understand why, but according to many posts, a fresh install after reformatting your drive does NOT always correct the problem! Wonder if zero-writing the drive would help in that instance?

[BengalTigger]

Wow! I see a desktop!
Thanks Frogger90. Your instructions worked.
I did have to do a few extras things which I will share here.

I had to access m$ for more details when I got confused.
http://support.microsoft.com/default...;en-us;307545&

When I did finally get an XP login displayed on my pc, it required product activation, but would not allow me to do the activate . The suggested fix for the activation was to do a repair install (sigh). During that repair I got a "procedure entry point GetIUMS could not be located in the dynamic link library MSDART.DLL" error. Used a fix at http://www.kellys-korner-xp.com/xp_m.htm
That got me into XP with a stable desktop. I quickly found I could not setup a modem connection and found that was due to my needing to reinstall SP1 and security updates.
Finally, I went to update my virus files to scan my HD and found Norton needed to be reinstalled as well.

It is ridiculous how badly XP can get hosed with such a simple thing as a device driver uninstall. But, I didn't have to format so I didn't lose any personal files, I'm feeling pretty lucky