LSASS Error on Boot Up

  • Thread starter Thread starter Skavenger
  • Start date Start date
S

Skavenger

Hello

I have acquired an intermittent error on boot up, I get the message
lsass.exe error unspecified HANDLE or something like that, the is not
consistent I.E. I have switched my PC on three times today and have not had
a problem. Yesterday I switched the PC on got the error clicked OK and the
PC rebooted had the same error clicked OK again and this time my machine
booted up fine.

I have read eleswhere that this problem requires either an OS fix or
re-installation

I am running WinXP Pro SP2 with two user accounts, a limited account and an
Administrator Priviliages account, on top of the built in hidden
Administrator account.

Any help rather than clean install would be great.

Ta
Skavenger
 
Hi,

Have you looked into the event viewer to see if there is any more detailed
information? Start/run eventvwr.msc and check the system logs.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org
 
Yep already looked there I believe the lsass worm is a derivitive of the
sasser worm so I downloaded the sasser worm fix ran it and found nothing. I
do not think the lsass worm affects boot up?

This problem occurs before the Windows Loading Splash Screen appears!!
 
Started using News Groups years and years ago and tried to attach a screen
shot many moons ago and was told that it was not good etiquette, that was
back in the days before broadband, is it now the done thing if so Yipee a
picture paints a thousand word........
 
Skavenger said:
Yep already looked there I believe the lsass worm is a derivitive of
the sasser worm so I downloaded the sasser worm fix ran it and found
nothing. I do not think the lsass worm affects boot up?

This problem occurs before the Windows Loading Splash Screen appears!!
Click to expand...

Not every error connected with lsass is a virus and I don't think yours
is viral, either. The random nature bothers me since most random errors
are caused by failing hardware instead of software (Windows). I'd do
some general hardware troubleshooting to make sure all is healthy
first, starting with the hard drive, the RAM, and the power supply. If
the hardware is good then try a Repair Install. If the Repair Install
doesn't work, you'll need to do a clean install, reinstall programs
from media, restore data from backup.

Here are some general hardware troubleshooting steps:

1) Open the computer and run it open, cleaning out all dust bunnies and
observing all fans (overheating will cause system freezing). Obviously
you can't do this with a laptop, but you can hear if the fan is running
and feel if the laptop is getting too hot.

2) Test the RAM - I like Memtest86+ from www.memtest.org. Obviously, you
have to get the program from a working machine. You will either
download the precompiled Windows binary to make a bootable floppy or
the .iso to make a bootable cd. If you want to use the latter, you'll
need to have third-party burning software on the machine where you
download the file - XP's built-in burning capability won't do the job.
In either case, boot with the media you made. The test will run
immediately. Let the test run for an hour or two - unless errors are
seen immediately. If you get any errors, replace the RAM.

3) Test the hard drive with a diagnostic utility from the mftr. Download
the file and make a bootable floppy or cd with it. Boot with the media
and do a thorough test. If the drive has physical errors, replace it.

4) The power supply may be going bad or be inadequate for the devices
you have in the system. The adequacy issue doesn't really apply to a
laptop, although of course the power supply can be faulty.

5) Test the motherboard with something like TuffTest from
www.tufftest.com. Sometimes this is useful, and sometimes it isn't.

Testing hardware failures often involves swapping out suspected parts
with known-good parts. If you can't do the testing yourself and/or are
uncomfortable opening your computer, take the machine to a professional
computer repair shop (not your local equivalent of BigStoreUSA).

Malke
 
As far as the Hardware is concerned I have changed the RAM from 2x256MB no
name brand to 2 x 512MB Kingston, the lsass error appeared before this
though.

I ran Memtest but did not let it complete takes a long time, I will run it
again.

I have two hard drives an 80GB Maxtor 6Y080L0 in two partitions and a 40GB
Seagate the Maxtors about 3 years old and the Seagate is about 5 years old.

The Mobo is an ASUS A7N8X Deluxe about 3 years old.
I'll carry out the tests as suggested thanks
 
From: "Skavenger" <[email protected]>

| Started using News Groups years and years ago and tried to attach a screen
| shot many moons ago and was told that it was not good etiquette, that was
| back in the days before broadband, is it now the done thing if so Yipee a
| picture paints a thousand word........

Microsoft does not disallow posting attachments if they are On Topic and in support of a
problem. Not that there is a size cut-off of 70~75KB.
 
Skavenger said:
Started using News Groups years and years ago and tried to attach a
screen shot many moons ago and was told that it was not good
etiquette, that was back in the days before broadband, is it now the
done thing
Click to expand...


Note the following.

1. In most newsgroups whose names do not contain the word "binaries" any
attachment, screen shot or otherwise, is still inappropriate and will get
you flamed

2. In these Microsoft newsgroups, they are not expressly forbidden. However
even here, many people feel they are inappropriate.

3. Even now, not everyone has broadband, and many people feel that having to
download an attachment is an imposition. Even among those people who do have
broadband, many people either have attachments turned off in the ir
newsreaders, or will refrain from opening them, because of the risk that
they may contain malware.

So my view is that, regardless of which newsgroup you're in, it's best never
to rely on an attachment to convey what you want to say. Spell it out in
words and you'll reach the largest audience of those who might be able to
help you.

if so Yipee a picture paints a thousand word
Click to expand...


Not if a sizable percentage of your audience never sees your picture.
 
Happy days, no attachments for me.

Forgive my lack of knowledge but I have been in Kenya for two years trying
to run an internet connection on a very unstable anolgue telephone line so
as you can appreciate I am not up to speed with progress and current
procedures.

Many thanks
 
Skavenger wrote:





Note the following.

1. In most newsgroups whose names do not contain the word "binaries" any
attachment, screen shot or otherwise, is still inappropriate and will get
you flamed

2. In these Microsoft newsgroups, they are not expressly forbidden. However
even here, many people feel they are inappropriate.

3. Even now, not everyone has broadband, and many people feel that having to
download an attachment is an imposition. Even among those people who do have
broadband, many people either have attachments turned off in the ir
newsreaders, or will refrain from opening them, because of the risk that
they may contain malware.

So my view is that, regardless of which newsgroup you're in, it's best never
to rely on an attachment to convey what you want to say. Spell it out in
words and you'll reach the largest audience of those who might be able to
help you.






Not if a sizable percentage of your audience never sees your picture.
Click to expand...

If they are using a decent newsreader program if they pay attention they
can see if a post has an attachment before dowloading it.

Steve N.
 
From: "Skavenger" <[email protected]>

| Yep already looked there I believe the lsass worm is a derivitive of the
| sasser worm so I downloaded the sasser worm fix ran it and found nothing. I
| do not think the lsass worm affects boot up?
|
| This problem occurs before the Windows Loading Splash Screen appears!!
|


No, the lsass worm is NOT derivitive of the sasser worm. There is no "lsass worm" there
are LSASS Exploits. The W32/Sasser.worm is just one example which also includes the
following (using McAfee naming convention)...

W32/Reatle.f@MM
W32/Gaobot.worm
Qhosts.apd --
W32/Plexus.b@MM
W32/Sdbot.worm!ftp
W32/Mytob.gen@MM
W32/Radebot.worm
 
Steve said:
If they are using a decent newsreader program if they pay attention
they can see if a post has an attachment before dowloading it.
Click to expand...


The newsreader doesn't much matter. You can generally do that with almost
any newsreader if you read newsgroups that way. However many people
participate in newsgroups by downloading all the unread messages in all the
newsgroups they are subscribed to at once (I do, for example). I don't
select which messages to download or download them one at a time.
 
Steve N. wrote:





The newsreader doesn't much matter. You can generally do that with almost
any newsreader if you read newsgroups that way. However many people
participate in newsgroups by downloading all the unread messages in all the
newsgroups they are subscribed to at once (I do, for example). I don't
select which messages to download or download them one at a time.
Click to expand...

Downloading headers and downloading messages are not the same thing. The
header shows if the message has an attachment.

Steve N.

Steve N.
 
From: "Plato" <|@|.|>

|
| Thanks. Changes made/uploaded.
|

It is your web site -- Fantastic.
That's much more accurate.
 
Steve said:
Downloading headers and downloading messages are not the same thing.
Click to expand...


Correct. I didn't say otherwise. My point is that many people download all
the *messages*.
 
Anyway back to original post........I do not believe my problem is a Worm of
any kind running Norton AV and keep it well up to date..............I have
been advised that it might be due to failing Hardware.
I have check the boot drive ok
will test the memory and Mobo what about any other components, this problem
occurs during boot up prior to the Loading Windows XP Screen!!
 
Back
Top