Win2K Restarting By Itself

[Arpan]

I have been working with Win2K Pro for a long long time. Today while
starting Win2K, I find that after the Win2K logo screen (which shows
the progress bar), my m/c gets rebooted on its own. I tried restarting
Win2K again & again but the outcome remains the same - Win2K reboots on
its own. I am not shown any error message.

Can someone please help me resolve this issue?

I don't know what happened suddenly....Win2K was running absolutely
fine till yesterday....

Thanks,

Arpan

 

[NewScience]

Something is wrong either with a new patch/update, new application installed
(printer software, ...), or the filesystem has problems.

Restart the system using F8 when the system starts up (as soon as you can
keep hittin the F8 button) in either Last Known Configuration and if that
does not work, restart in Safe Mode and perform a CHKDSK /R on the drive.
This will check if you have an filesystem errors preventing Windows XP from
starting.

The system is restarting continually because the Automatic Restart on
Failure is set. You should see an option on the same Menu Screen (from F8
on boot-up), that will Disable this feature. Once selected, the system will
reboot, but not automatically reboot on a failure. It will tell you the
reason for failure and then leave it on the screen. You will then have to
manually reboot your system by use of the Power Button/Reset Button.

 

[Dave Patrick]

There's no such thing with Windows 2000

--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

:

on boot-up), that will Disable this feature.

<snip>

 

[Dave Patrick]

From a parallel install, run regedt32.exe, then from the Local Machine Hive,
choose Registry|Load Hive, then navigate to the
%systemroot%\system32\config
directory on the other install, and find the system file, then Open, in the
Key Name box give it some temp name, then under tempname, navigate to
HKEY_LOCAL_MACHINE\SYSTEM\Select
and look in the Reg_Dword value of "Current", this is the current
controlset, then navigate to
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet00x\Control\CrashControl
Where x = the value of "Current" (found above) and set the values as follows

"AutoReboot"=dword:00000000
"CrashDumpEnabled"=dword:00000001
"LogEvent"=dword:00000001
"Overwrite"=dword:00000001
Then navigate back up to "tempname" and choose Unload Hive, and boot your
original install, Autoreboot is now turned off so you should be able to read
the stop error.

These may also help.
http://support.microsoft.com/kb/266465

http://msdn.microsoft.com/library/d..._f55acfed-3296-4e84-8885-c3162fd0ddbf.xml.asp


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

 

[***** charles]

I have been working with Win2K Pro for a long long time. Today while
starting Win2K, I find that after the Win2K logo screen (which shows
the progress bar), my m/c gets rebooted on its own. I tried restarting
Win2K again & again but the outcome remains the same - Win2K reboots on
its own. I am not shown any error message.

Can someone please help me resolve this issue?

I don't know what happened suddenly....Win2K was running absolutely
fine till yesterday....

Thanks,

Arpan

Is it possible you picked up a virus? or maybe some piece of hardware
(ram bit/power supply/etc...) has gone bad?

later....

 

[Arpan]

The system is restarting continually because the Automatic Restart on
I did so & this is error message that gets generated:

----------
STOP: c000021a {Fatal System Error}
The Windows Logon Process system process terminated unexpectedly with a
status of 0x00000080 (0x00000000 0x00000000).

The system has been shut down.

If this is the first time you've seen this Stop error screen, restart
your computer. If this screen appears again, follow these steps:

Check to make sure any new hardware or software is properly installed.
If this is a new installation, ask your hardware or software
manufacturer for any Windows 2000 updates you might need.

If problems continue, disable or remove any newly installed hardware or
software. Disable BIOS memory options such as caching or shadowing. If
you need to use Safe Mode to remove or disable components, restart your
computer, press F8 to select Advanced Startup Options, and then select
Safe Mode.

Refer to your Getting Started manual for more information on
troubleshooting Stop errors.
----------

One thing is for sure - neither have I added any new hardware nor have
I installed any new software. I went through a number of articles on
the Net (including the Micrososft website) to resolve this Stop error
but have failed. All my efforts went in vain & down the drain.

I came across an article which said replacing the LSASS.EXE file (which
resides in the C:\WINNT\system32 folder) with a good LSASS.EXE file
from another Win2K m/c. might resolve this issue.

If possible, can someone please mail me a copy of LSASS.EXE from Win2K
Pro at my e-mail ID? I would be highly obliged if someone could please
mail me this EXE file.

Is it possible you picked up a virus? or maybe some piece of hardware
(ram bit/power supply/etc...) has gone bad?

No, Charles, I don't think so because till yesterday night, it was
working fine & today I find that it's restarting by itself.

Actually about 4-5 days back, Windows generated the following error &
refused to start (in this case as well, Win2K was working fine till the
night before but generated this error when I tried to start Win2K the
next morning):

----------
Windows could not start because the following file is missing or
corrupt:

C:\WINNT\system32\config\system

You can attempt to repair this file by starting Windows Setup using the
original setup CD-ROM. Select 'r' at the first screen to start repair.
----------

Since I also have WinXP Pro installed in the D:\ drive, I searched the
Net for a solution by logging into WinXP & finally managed to resolve
the Win2K error by executing the following command from Command Prompt:

copy C:\WINNT\repair\system C:\WINNT\system32\config

After this, I could as usual log into Win2K & do my work.

I also did a virus check but my anti-virus (AVG7.5) didn't report any
viruses or worms or trojans. Neither did I make any changes in the
hardware configuration.

Dave, what do you mean by a "parallel install"? I have Win2K Pro
installed in the C:\ drive & WinXP Pro installed in the D:\ drive.

Could someone pleassssssse provide me a concrete solution to overcome
this Stop error?

Thanks to all,

Regards,

Arpan

 

[NewScience]

I can e-mail you the file since my system is dual booted.

However, sometimes when I run into this problem, a chkdsk /f on the drive
fixes it.
Also, just coming up in Safe Mode, fixed the problem sometimes.

Bring it up in Safe Mode, then reboot and bring up in Normal Mode.
If still a failure, while in Safe Mode, schedule a CHKDSK (fix errors
automatically), and then reboot.

You can also check for the original System registry hive under:

C:\winnt\system32\config\system.sav
OR
C:\winnt\repair and see if there is a RegBack folder with a system file
OR
C:\winnt\repair\system

Check all the dates to pick the most up to date.

The LSASS.EXE error was W2K being told to shutdown. You would be getting a
Message Window displaying that message.

 

[Arpan]

I can e-mail you the file since my system is dual booted.

I will be highly obliged if you could please do so but please note one
thing - Hotmail doesn't allow users to download attachments if the file
has the ".EXE" extension. So you could do 2 things - either zip
LSASS.EXE or change the extension from "EXE" to "TXT" & then attach it
(if the latter, I will change the extension back to "EXE" once I have
downloaded it).

However, sometimes when I run into this problem, a chkdsk /f on the drive
fixes it.
Also, just coming up in Safe Mode, fixed the problem sometimes.

Bring it up in Safe Mode, then reboot and bring up in Normal Mode.
If still a failure, while in Safe Mode, schedule a CHKDSK (fix errors
automatically), and then reboot.

I did run CHKDSK (with the ne=cessary parameters) on the C:\ drive
where Win2K is installed but that didn't help me out.

Thanks once again,

Regards,

Arpan