The message reads "while trying to update password lsass.exe encountered and
error and your system..."
Any ideas?
Regards
Greg.
"Gerard Verhoef" <Gerard_...@Hotmail.com> wrote in message
news:ONsdfCY%23EHA...@TK2MSFTNGP10.phx.gbl...
Does the sytem just reboot or do you receive a message that indicates the machine is being
shutdown and you have xx seconds (usually 60 secs.) before the system is shutdown ?
--
Dave
"Greg Steer" <gr...@keswickcomputers.co.uk> wrote in message
news:OfMpVAY%23EHA...@TK2MSFTNGP15.phx.gbl...
The system simply reboots with hardly anytime to read the message correctly,
it is not exhibiting the usual Blaster/Sasser items. The system was cleaned
of Viri before NAV 2005 was installed and since then has got stuck in this
reboot cycle
Regards
Greg.
"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:udScKHY%23EHA...@TK2MSFTNGP15.phx.gbl...
Gerard
"Greg Steer" <gr...@keswickcomputers.co.uk> wrote in message
news:%23qprJHY%23EHA...@TK2MSFTNGP12.phx.gbl...
The system was NOT "...cleaned of Viri..." because there is NO such terminology as viri or
virii. The plural of virus is viruses - period.
That being said, I didn't think it was a worm. However I think you may have to boot from
the WinXP CDROM and perform a Repair Install.
--
Dave
"Greg Steer" <gr...@keswickcomputers.co.uk> wrote in message
news:%23tLj8IY%23EHA...@TK2MSFTNGP15.phx.gbl...
--
Dave
"Gerard Verhoef" <Gerard_...@Hotmail.com> wrote in message
news:ucVqyMY%23EHA...@TK2MSFTNGP10.phx.gbl...
We have no keycode for this system, and the customer doesn't have it either
(sounds about right!) and the Admin password is unknown, well partially
known but no combinations work to get to the recovery console. Only access
we have is by throwing the HD into one of our test systems to access it.
Any ides on this "remote" fix situation?
Greg.
"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in message
news:egeQaNY%23EHA...@TK2MSFTNGP15.phx.gbl...
--
Dave
"Greg Steer" <gr...@keswickcomputers.co.uk> wrote in message
news:OhSPmgY%23EH...@TK2MSFTNGP09.phx.gbl...
> The problem continues...
>
> We have no keycode for this system, and the customer doesn't have it
> either (sounds about right!) and the Admin password is unknown, well
> partially known but no combinations work to get to the recovery
> console. Only access we have is by throwing the HD into one of our
> test systems to access it.
>
> Any ides on this "remote" fix situation?
I would do some hardware testing. As far as getting into the system, I'm
not sure what you mean by "keycode". Do you mean a BIOS password? It is
quite easy to reset BIOS passwords on a desktop system. It is also easy
to reset a Windows password. Try the hardware troubleshooting first and
do post back if you meant a BIOS password and need help in resetting
that first.
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 - let the test
run for an extended (like overnight) period of time - unless errors are
seen immediately.
3) Test the hard drive with a diagnostic utility from the mftr.
4) The power supply may be going bad or be inadequate for the devices
you have in the system - this isn't applicable to a laptop, of course.
5) Test the motherboard with something like TuffTest from
www.tufftest.com.
Malke
--
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"