Lsass.exe - System Error

[stockjock]

Friends computer is stuck in this start up loop. This error happens right when windows XP trys to start up. I've tried the F8 start up of going to the last known good start up and Safe Mode...It just wont go!. I've done google searches too and nothing seems to help. any ideas??

 

[amdskip]

It's not a good thing if a pc won't boot into safe mode. Usually means format c:

 

[Mrpilot007]

I had a similar issue recently with one of my pc's. The solution was a new hd and reinstall. The interesting thing was that I took the hd that I thought to be bad and put it as a slave in my backup pc and on boot up the pc recognized the hd and said there was a file system problem and began to fix the issue. Now the hd is fine. Not sure if this is related. I recommend to use an imaging(backup) program in case this happens again.

 

[sykopath79]

Boot into Recovery Console off your Windows XP disc, and run CHKDSK /R, then try booting into Windows again and see if it fixed anything. If not, you probably need to format & reinstall.

 

[stockjock]

Boot into Recovery Console off your Windows XP disc, and run CHKDSK /R, then try booting into Windows again and see if it fixed anything. If not, you probably need to format & reinstall.

Thanks...that is what I'm gonna try next and then I'll go for a format:disgust:

 

[jmarkos]

is this the same bostonredsox, replicon, and my boot & reboot failure? I removed a stick of RAM and things are back to normal.

 

[kumanchu]

sounds like a corrupt lsass.exe file. corruption = bad.

 

[Saga]

Got the same issue with the little sisters sempron machine. Ended up taking out the HDD and throwing it into my RAM test machine as a slave and doing a chkdsk e: /r, fixed a few things and worked like a charm after that.

The odd thing was I reformatted and reinstalled XP Pro three times and everytime the lsass.exe error would start up, imagine it's possible it's the blaster worm or some similar variant aimed at computers which are not up to date on the service packs, and I'm pretty sure it was in the boot sector of the HDD itself.