After downloaded some software, I received the following message: "lsass.exe system error", which powered off my pc. After doing some reseach, I was unable to determine if I had a legit "LSASS.EXE" error, or the "ISASS.EXE" Sasser worm. I simply could not distinguish between a lower case "L", or a capital "I".

After trying a few fixes, I decided to reformat my hard drive and do a fresh install. After my pc loaded the set up files, my pc shut down when the install began. I then ran the Boot and Nuke program to completely wipe the drives clean. I tried the install again with the same result. Thinking my install disk might be bad, I used another install disk with XP Home and got the same result. I then tried to install an old edition of Windows ME and the install was successful.

Since the lsass.exe is applicable to Windows 200,NT, and XP, and not to Windows ME, that explains the ME install, but could some reminent of the virus (assuming that is what I had to begin with) still be present after a hard drive wipe? Does anybody have a cure? Thanks

Not a virus.. sounds like something was corrupting the file or files used.

Instead of formating you could go into Recovery console and extract lsass.ex_ from CDDrive:\i386 to C:\windows\system32

That would have fixed your problem. Anytime you run into a corrupt file.. if possible, hit support.microsoft.com, type the file name and recovery console and it should pull up directions on how to restore the file.

Thanks Riser- I agree that I probably over-reacted and lost a ton of stuff (that I didn't, but should have, backed up) by re-formatting. At any rate, I still cannot re-load either my version of XP Pro, or another version of XP Home Edition that I borrowed from work (which has never been installed on my pc to have been corrupted). Windows ME will install, XP will not. I can't imagine it being a hardware issue, considering ME loads, but I'm open for any suggestions.

Try running a surface test on your harddrive. It will either a) uncover bad sectors on your hdd which isn't effecting your windows me, b) fail and perhaps indicate if your harddrive or related hardware is going bad or c) give you time to catch up unrelated real life housework

Thanks . I will try that. I had a lot of lint build up on my heat sink and I hoped that maybe my pc was overheating during the XP install. Unfortunately, I had the same condition after I cleaned all of the lint out of my fansand heat sink. The only thing I am sure of at this point is A: All of this occured after an upgrade of Limewire, and B: this is the toughest pc error I have ever dealt with.

Got it. Allowed the XP partition utility to do its thing, and it started working. Don't understand why, but it is working nonetheless.