Lsass.exe error endpoint format is invalid

[Guest]

System will no longer boot normally to WinXP Home Ed. The subject content
appears in a small window with an 'Ok' button being the only option, which
simply reboots to the same error window. This symptom suddenly appeared after
normal operation since building my computer 2-1/2 years ago. None of the
typical Sasser symptoms are present. Replacing the Lsass.exe file via
'Repair' with my installation CD is no help. All of my important files are
backed up but I really hate to format/reinstall everything, plus the dial-up
connection in my rural area will take forever to update Windows, AV, etc.

I have also tried to boot with a new User Accout to no avail. Booting to an
earlier operable condition has no effect nor does Restoring. I can boot to
Safe Mode.

Any help with this will certainly be appreciated.

 

[Guest]

It is difficult to diagnose from various error logs exactly what transpired
to cause this Lsass.exe system problem, or what Windows files need to be
replaced -- and whether replacement of a system file(s) from the installation
CD would actually function properly since it (they) would not have potential
benefit of various Windows updates over 2-1/2 years.

I called Microsoft today concerning this problem. As possible help to
others, little attempt was made to diagnose a cause of the problem after I
explained it and my follow-up actions. "Corrupt files" was the conclusion
after exercises in rebooting the system. The entire Windows XP files were
then reloaded over the existing installation via 'Repair' mode from my
Windows CD, resulting in the problem disappearing without needing to format
the hard drive and reloading everything 'from scratch.' None of my 3rd party
programs and downloads were affected, nor were any personal files or
settings. The downside is that all previously installed Windows Updates will
need to be downloaded again, a 'very' long process with my dial-up connection
-- and the fact that I apparently will never know what caused the problem.

Mac

 

[Guest]

Not end of story yet.... When attempting to download all of the upgrades I
thought to be necessary at the Microsoft Update web site, the web site wished
to firstly upgrade my efficiency for downloading, as I understand it. But
after certain downloads were completed along with instructions to restart,
the system rebooted to blue screen STOP error 0x0000007F (0x00000008,
0x80042000, 0x0->0, 0x0->0.) Upon rebooting to 'Last known configuration that
worked' the identical STOP error again resulted so I rebooted to Windows Safe
Mode.

Various error logs show that several Windows Updates failed to install, the
only success being "Product Windows Genuine Advantage v1.3.0254.0" which
'may' also be part of the entry in Control Panel\Add/Remove Programs
identified as 'Microsoft Data Access Components.' (?) I am now awaiting word
from Microsoft as to advice for the next step.

I realize that STOP errors are often caused by hardware problems, expecially
memory. However, I previously experienced no STOP errors and had no issues
that might be associated with memory prior to the original Lsass.exe system
error suddenly occurring. I also have not installed any new hardware or
software recently. I suspect the STOP error is somehow associated with the
corrupted Windows file(s) issue.

More later.

Mac

 

[Guest]

I had the same problem on a server last night. There is a Knowledge Base
Article ID 893712 relating to Windows server and Exchange, and it worked for
me even though I had SQL not Exchange. It 'typically' applies to to systems
with large memory switches in the boot.ini but it may help you. The fix is to
add a registry entry to hklm\system\ccs\control\session manager\memory
management with a DWORD entry called SystemPages and a value of 31000.
Check out the article - I have no idea what its' effect will be on XP!!!