Error lsass.exe- Residual issues

[Guest]

I was hit with a version of sasser masquerading as B32.Blaster.Worm on May
19th 2004. Gradually I worked through it and plateaued in progress several
weeks back, with the error tone sounding on shut-down.
However these errors are being logged. Not in Dr. Watson-but the error log
accessed via TOOLS > Advanced System Information in XPs Help & Support. Some
days have 100 identical entries giving only the date. Service Control Manager
as SOURCE insists the "specified module could not be found".
The errors begin logging on May 19th: the day I first went on line and got
chomped when updating security within 10 min of logging on.

Any input re lsass.exe version 5.1.2600.1106, faulting module unknown,
version 0.0.0.0 fault address 0x00000000, would be a boon down here in lovely
Melbourne Oz.
Thanks all.

 

[Wesley Vogel]

To open the Event Viewer...
Start | Run | Type: eventvwr | OK

Double click the event in Event Viewer | Click: the button below the second
arrow (looks like two pages) [[Copies the details of the event to the
Clipboard.]] | Paste into Notepad | Click:
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Read all info | Copy and paste to Notepad | Click the [+] Related Knowledge
Base articles | Follow any links that might be useful

HOW TO: View and Manage Event Logs in Event Viewer in Windows XP
http://support.microsoft.com/default.aspx?scid=kb;en-us;308427


This can also be very useful.
You need to have the Event ID & the Event Source.

Windows XP Professional Events and Errors
http://www.microsoft.com/technet/su...ows Operating System&MajorMinor=5.1&LCID=1033