lsass.exe error loop at bootup - Page 2

SoCal Hobo · 11-28-2002, 08:59 PM

From what I've recently found you may be able to recover by renaming the hive SAM.BAK tp SAM in the Windows\System32\Config directory.

You will have to use a Windows 98 boot floppy to get to it -- as long as your file system is still FAT32.

Other wise you will need a bootable XP CD. Search the web for the proper boot image file and you can make a bootable XP CD.

DakotaFox · 12-03-2002, 08:57 AM

I've gotten a few emails from people wondering if I found a fix to this problem it seems to be a fairly common problem. This is for the information of anybody else that has to deal with the lsass.exe error . I didn't find any way to get the computer back into operating condition. I hope you have better luck.

This is the only way I found to deal with this problem.
I was able to get ahold of an older 3 gig HDD. I installed the 3 gig into the Emachine as the primary and then I ran the resore disk on this to install Emachines version of XP. I had thought I would copy the information from the 60 gig to the 3 gig but the installation took about 2.5 gig of space. I installed the failing 60 gig as slave. I was able to read the data on the 60 gig in Windows explorer. I networked the Emachines to my New Trend. I then was able to find and copy my much needed files to the older machine.

After that I put the 60 gig back as the primary and restored it. It seems to be working now.

I think that having to do this to a machine with the "Latest and Greatest Windows" to save one's data is BULL$HIT. I have never had to deal with a problem like this with Win95a, 95b, 98, 98SE, or ME. And the "support" from micro$oft is shameful.

I have been on the Internet for the past week finding and installing the XP drivers for the printer, scanner, camera, burner, modem, and all of the hardware that didn't come with XP drivers. It is a real pain in the a$$. I wish that the money grubbers at Micro$oft would support their product and spend some time refining the functionality of their op sys instead of figuring out how to keep a homeowner from putting a copy on their kid's computer.

The soulution seems to be to try a different operating system or to make sure you have a spare computer and hard drive around so you can save your data when XP craps on you.

firewall · 12-08-2002, 07:00 AM

Had same problem with lsas.exe today following crash.
Kept rebooting.
Problem was solved by reverting to last previously known good configuration.
Only thing I had to do is reinstall graphics drivers.

FireWall

codemaster_talon · 12-11-2002, 04:51 PM

hey guys... I have the same problem with my laptop running win XP home and I can't seem to get it to work at all... not even reverting to last known good settings helps... has anyone figured out a way to get at the files themselves yet or is this still up in the air? another interesting question that comes to mind, with win XP you can prevent other users (even admins) from gaining access to your files in the My documents folder(providing that you are an admin as well) I thought that microsoft used some sort of subtle encryption scheme to prevent other users from gaining access to these files so if you were at the command prompt and assuming that you could get to the files would they still be usefull if you could just copy them? or does the encryption make them now useless?

ashmath1 · 12-13-2002, 04:09 PM

With so many postings on this subject, it appears to be a major problem with xp (and/or some hardware compatibility problem?).

My 3-month old HP notebook with xp home edition also started with "lsass.exe system error - the specified domain did not exist" problem from yesterday. The system gets in a loop without booting in xp. Have tried safe mode and last known good configuration, still no luck. (The only new thing I did was switching my network a week ago from hardwired Linksys cable/dsl router to Linksys wireless router, and the system was working fine until yesterday.)

There isn't much documentation to fix this problem at Microsoft site and HP tech support wasn't of much help either. HP recommends restoring system to original configuration with their provided system CDs (HP didn't include WinXP install CDs with the system.). They also suggest getting setup disks from microsoft and booting the XP with the setup disks.

Can any one help with their experience of successful boot and/or data back-up before doing a complete system restore? Thanks.

Reinhold · 12-15-2002, 06:23 PM

..

Reinhold · 12-15-2002, 06:24 PM

I am another victim of the lsass.exe system error. I was loading drivers on a brand new Dell laptop, and I hit a "checkmate" which required me to reformat the hard drive and reload everything.

I could not recover using the Windows XP OEM CD.

What is going on here? I haven't been able to find a work-around for this problem anywhere.

AggieKyle · 12-19-2002, 01:27 PM

Howdy:

I found this forum by searching "lsass.exe" in google.com because I seem to be having issues with it too. I think it's the reason my laptop keeps locking up and requiring about three reboots before it sucessfully boots up.

If anyone has any suggestions on how to fix and/or eliminate it I'd appreciate it.

As for your problem with getting your files safe before formatting the harddrive, I think it will be an issue since you have an eMachine and all those kinds of companies ever give you nowadays is a "Restore Disc" which SEVERELY limits your options. If it was me I would take my harddrive out and stick it in another computer and get my files that way.

codemaster_talon · 12-24-2002, 01:42 PM

I emailed Microsoft tech support about the problem and they already know about it but haven't been able to get around to fixing what they call a minor problem.... considering how wide spread this prob seems to be I resent another e-mail with a link to this particular forum... now weather or not they decide to take a look at the thread is another question but hopefully they will have a patch or a fix out soon... as for now they recomended reformatting the drive and reinstalling because overinstalling XP over the old OS will do nothing but cause program faults and you will have more problems than before...(like that is possible) and if you put another OS onto the same partition then it "MAY" cause other OS problems... now if you are lucky enough to have another partition just hanging around on that drive then by all means go ahead and install an OS on that and go get your files... but for those of us that do not have one in our back pocket... we are SOL...

Sorry to be the bearer of bad news but it looks like we're snookered on this one.

Reinhold · 12-24-2002, 02:15 PM

I'm perplexed at the very serious nature of this particular problem and the seeming lack of concrn on the part of Microsoft or anyone else in the industry about solving it.

Reformatting a hard drive doesn't sound like a great solution to a problem which the manufacturer seems to think is not serious. Yet, the only solution I could come up with on a brand new Dell computer was to reformat the drive.