TechSpot - PC Technology News and Analysis

I get this message everytime I boot up Windows. There's an "OK" button, and when I press that, it reboots the computer, only to come back to that same error message. Anybody have a clue on what it means and what i can do about it?

It sounds as though you need to do a repair install of Windows.

Go HERE and follow the instructions.

Regards Howard

Read the link, is interesting, but...

What happens if I have a pre-SP1 disc, but this install has SP2?

Obviously doing a repair install would wipe all your updates.

But it should fix the problem and then you`d need to apply the updates again.

Regards Howard

I've now experienced this problem several times and am again stuck with it.

I've gone through the XP Home repair twice. Applied updates. System was running well the other day so I decided to take a System Restore checkpoint in case I ran into problems again. System was great yesterday, but failed to boot today with the same old error.

Rolled back to the checkpoint I had just taken, but that did not eliminate the boot error.

I can boot in safe mode with networking w/o any issue. No devices show as in conflict. I recently installed ATI's graphic driver later version, but system was running well with it. I also re-installed MSN Messenger without incident, including reboots.

So here I have a system that was just humming along beautifully then wouldn't boot the next morning.

I am using XP Home, SP2 updates all applied, ATI graphics, dual 120gb drives in RAID format, dual monitors off the one ATI card. 1gb of ram.

This problem is not one of simply repairing XP. Something else is creeping into the system. Otherwise, how could it be running smoothly for days then suddenly fail to boot the next morning? (I shut down every evening.)

I've searched the net and have not found one place that seems to have a handle on this problem although many have suffered with it.

All help will be appreciated.

I've discovered a few more things about this very odd problem:

http://www.freeimagebrowser.com/foru...=7897#post7897

It seems related to both the paging space and my on-board networking on the Asus board: Marvel Yukon 88E8053 PCI-E Gigabit Ethernet.

Every other boot results in either the lsass.exe error or a boot to windows with networking not functioning due to an error reported in Device Manager for the Marvel driver. The system allows reloading the driver and networking resumes. Reboot may or may not repeat the cycle.

Very odd.

I too solved the problem by changing back to automatic system controlled rather than custom or user specified size paging.

Hi

A friend gave me his emachines PC to fix. When I turn on the PC [winXP-home] I get this lsass error as described. The same error happens in Safe Mode. I tried a non-destructive restore to no avail... still happens.

There is NO WAY to boot - I get NO LOGIN SCREEN, so I can't impliment any of the fixes I have found. There is NO /3GB switch or the /PAE switch in the Boot.ini
I have the HDD install as secondary in my "test" box. I did all the drive utilities and it's not working.

What next?

same here, egadgetguy. I had to reinstall Win XP [home] just to log in. A couple of days after updating XP, the same thing happens. I guessing this could happen again in a day or so. I'm not going to update XP this time to see what happens, as it may have something to do with a microsoft update file. [i'll post back in a day or so]

My computer system gives this message after updating spyware stormer. How can I resolve this issue?

You probably need to do a repair install. But before you do that it may be possible to boot to the recovery console and do:

Then exit the recovery console and reboot. If the problem persists you'll have to repair install.

spyware stormer this seems to cause lsass problems all of a sudden so beware

hmmm.... I had spyware stomer aswell, but after reinstall XP i didn't install it, and i haven't see 'lass' problems since.

[ Note: i haven't re-installed service pack 2]

Hello and welcome to Techspot.

This is taken from the Spyware Warrior website.

As you can see, the programme is a rogue antispyware programme and should never be installed.

If anyone has the above programme installed, uninstall it ASAP.

Regards Howard

For the boot problem "lsass.exe System Error: The endpoint is invalid" create a new pagefile on another disk while setting the current disk(s) to no pagefile, then reboot the system. Once fixed, you can delete old pagefile(s) and switch back to original settings. Contact D2@gap.net for more info.

"lsass.exe System Error: The endpoint is invalid". OK, HERE IS MY FIX FOR THIS PROBLEM. I tried all day to eradicate this problem. I had just installed some software from Hewlett Packard, and then deleted most of it as I only wanted printer drivers, not their extremely bad imaging software. So it might have something to do with this. If you get this error, boot up in safe mode (hit F8) just as your startup screen starts telling memory cpu type etc. Go into safe mode and check if you have suddenly got another user. In my case I get the screen to type in my password and you can select user in my case Chris. I noticed that suddenly there was another user called 'administrator'. Well that can't be becuase 'Chris' plays that part. So what is going on here is a conflict of 'users'. I got rid of the lsass dialog box by running one of the best utility programmes I have used Wintools.net pro which scans the registry for broken or irrelevant links. It cleared all bad links, removed the administrator in the process and machine back working fine. If you dont have an initial XP loginscreen to type in your password, still boot into safe mode and look in 'users' in control panel. If there is more than there should be delete it! Good luck

Got this error yesterday, after a defrag, and was able to fix it as follows (system is Windows XP, SP1 with all updates). 1. Booted to safe mode (press F8 while booting) and changed Virtual Memory from custom to system managed. 2. Rebooted - still not fixed. 3. Rebooted while pressing F8 and selected Last Working configuration. Was able to boot normally! 4. Then did a registry clean with RegVac. 5. Raxco PerfectDisk said Drive C needed off-line system defrag (probably the highly fragmented PageFile). Performed this, followed by a standard defrag, and the system is now running fine.

My first theory was that this was mostly a pagefile problem, but I have since been leaning toward the registry. Your results tend to add to that second theory, because even tho' you first changed the pagefile, it seems that the registry needed an extra kick to make things work.