New LSASS.exe problem! (firewall related)

[Guest]

So, you think you've heard it all about the trigger-like LSASS.exe, right?
Try this for size: A valid program killed it. No sasser, no virus at all.
Just incompetence.

It all started when I was less educated and seeing what my Sygate Personal
Firewall could do. I decided to see what was really running under the hood by
examining the programs that were running, one of which was lsass.exe. So, I
right-clicked, looking for "properties" or something similar, and... whoops!
Did I just click "terminate?"

The crazy thing died then and there, and hasn't been able to calm down
since. Exact message:
NT AUTHORITY\SYSTEM
'c:\winnt\system32\lsass.exe' terminated unexpectedly with status code
-1073741819

The worst thing is that it won't even get to the desktop before the timer
runs out and the computer restarts. The countdown begins as the Windows XP
Professional tries to set up profile settings for Outlook.

 

[Mac]

http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls=GGLD,GGLD:2004-01,GGLD:en&q=-1073741819

After the first few entries

Mac

 

[Guest]

I'd love to say that that helped, but it literally did everything but help--
the searched term was "NOT 1073741819." Nonetheless, I searched for the
actual code-- and found everything that would help if I was infected with a
virus. May I remind you that my own accident triggered this? Sygate Personal
Firewall somehow caused a repeat-shutdown of lsass.

I considered trying to run the phrase "shutdown -a," but I cannot reach the
desktop before the timer ends.

 

[Guest]

Problem resolved, I believe! After a heroic amount of patience, I made it to
the desktop and typed in "shutdown -a" with only 5 seconds left. From there I
was able to inform Sygate that LSASS was a good program.