Re: New LSASS.exe problem! (firewall related)
- From: "Mac" <mac@xxxxxxxxxx>
- Date: Thu, 8 Jun 2006 09:49:00 +0100
http://www.google.com/search?sourceid=navclient&ie=UTF-8&rls=GGLD,GGLD:2004-01,GGLD:en&q=%2D1073741819
After the first few entries
Mac
"ISuffix" <altiansuffix3@xxxxxxxxxxx> wrote in message
news:1036C8B2-8602-4082-8FDC-B3B8A7A63B41@xxxxxxxxxxxxxxxx
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.
--
out of cards
.
- Prev by Date: Re: Determine UUID/GUID on Windows XP?
- Next by Date: Re: Taskbar issues
- Previous by thread: Re: Failed SP2 upgrade - possible causes?
- Next by thread: Re: Taskbar issues
- Index(es):
Relevant Pages
|
