What would cause an lsass.exe termination even before the login window is displayed?

[Martin C]

First of all, I believe that the 'lsass.exe terminates with code 1073741819"
is not down to the Sasser worm,
as I have used a special boot disc to scan the PC for viruses and it has
found none.

Also, this termination is not occurring after Windows XP Home SP2 has
started, but during
the start up process. It gets to the stage where it is saying that Windows
is starting, then stops with
"lsass.exe error
The instruction at 0x7c914d1a referenced memory at 0x0000000000. Memory
could not be read. Press OK to terminate or Cancel to debug."
Either will then give a popup dialog with
"NT Authority/System
Terminate code 1073741819."

It is therefore impossible to get into Windows in the first place, so
options using the Run command are not possible.

I have tried doing a repair install of Windows on my friends PC (using my
copy of the XP CD).
On completion I get exactly the same error.
Two questions.
Is there any way that this could be hardware rather than software related?
If not, would a complete reinstallation of windows clear out anything
differently? Please note that it is very difficult on their PC to get to the
command prompt to FDISK if necessary.

TIA
Martin

 

[sisyphus238]

First of all, I believe that the 'lsass.exeterminates with code 1073741819"
is not down to the Sasser worm,
as I have used a special boot disc to scan the PC for viruses and it has
found none.

Also, this termination is not occurring after Windows XP Home SP2 has
started, but during
the start up process. It gets to the stage where it is saying that Windows
is starting, then stops with
"lsass.exeerror
The instruction at 0x7c914d1a referenced memory at 0x0000000000. Memory
could not be read. Press OK to terminate or Cancel to debug."
Either will then give a popup dialog with
"NT Authority/System
Terminate code 1073741819."

It is therefore impossible to get into Windows in the first place, so
options using the Run command are not possible.

I have tried doing a repair install of Windows on my friends PC (using my
copy of the XP CD).
On completion I get exactly the same error.
Two questions.
Is there any way that this could be hardware rather than software related?
If not, would a complete reinstallation of windows clear out anything
differently? Please note that it is very difficult on their PC to get to the
command prompt to FDISK if necessary.

TIA
Martin

I have been working on this for two weeks. I reinstalled XP about six
times. I got a trial version of MacAffe firewal and saw that two
meatheads kept probing two portson my machine (which were now
closed. this means after you install XP again they are back before
hyou can go get tehe XP patches for the XP vulnerabilities.