Domain Controller is Rebooting Endlessly

[CHANGE USERNAME to westes]

This one is a bit weird. Our lab domain controller is a Win 2000 Advanced
Server machine running RC2. Today after rebooting, it gets to the very
final step of the boot before the ctrl+alt+del dialog comes up and it starts
network connections. Right *before* this dialog, the machine reboots.

This happens no matter which safe mode you select. I tried just about every
options imaginable off of the F8 key, and they all produce the identical
result. There is always a reboot right at the end of the boot up process.

How do I go about debugging this problem and repairing the installation?

--
Will

NOTE: To reply, CHANGE the username to westes AT uscsw.com

[Jason]

can you get into safe mode command prompt to try and get a look at
ntbtlog.txt in the %windir% directory -

If you can you can get an ides of what driver/service is causing the
problems, then you can boot fro the CD (if you don't already have the repair
console loaded) and select the repair option --when prompted to repair, I
believe you hot F10 (sorry, it's been a while) then use the accompanying
command set in the repair console to try and either rename the bad driver or
disable the device/service startup

Conversely if this is on FAT drive --do the same from a Win98 boot disk

jason
mailto:jp...@home.com

"CHANGE USERNAME to westes" <junk...@uscsw.com> wrote in message
news:eUunhpia$GA.256@cppssbbsa05...

[Thomas B. Slinkard]

Don't know about the "debugging" (what was the last thing that was changed/added before it started this behavior?), but You might try restarting setup and after the EULA, you will be asked if you wish to repair the WINNT folder that is found from the original setup. Select this repair option and you should be back up and rolling just fine.

 

Thomas B. Slinkard

[CHANGE USERNAME to westes]

We tried doing a repair and it makes no difference. I suspect we
have some specific service that has a bug, and when we are
starting that service it reboots the machine. Is there any way
to disable all non-essential services during boot up so we can
test one by one and disable services until we find the one
responsible?

--
Will
Internet: westes at uscsw.com

PLEASE READ: To send me Internet e-mail, you must change
the userid on this message from the word 'junkmail' to the
word 'westes'. If you reply to the default address then I will
not get the message!!

"Thomas B. Slinkard" <tsli...@boldata.com> wrote in message
news:O9fV$via$GA...@cppssbbsa02.microsoft.com...

[Bart Robinson]

Can u get to safe mode?
I had this happen with AS...resource conflict: NIC\Video card.

"CHANGE USERNAME to westes" <junk...@uscsw.com> wrote in message news:ulz1Bx2a$GA....@cppssbbsa02.microsoft.com...

[Laski]

I think this is caused by a SYSTEM SERVICE that starts up during boot.

If you have the systems settings to "Reboot if windows encountered an
error", the system will reboot. unfortunately there is no way you can change
it unless you can modify registry settings without booting:-))

I would suggest a fresh reinstall...

And first thing you do would be to set the system setting not to reboot but
write a log and/or a dmp file.

Hope this helps
Laski...

/* --------------------------------------------------------------------*/

[Kaiser-Sose]

DON'T do a fresh install yet. Before you go through that trouble. And in
case safe mode doesn't bring you up. If a problem occurs when booting I have
successfully booted by doing the following. Remove whatever other cards
there are in the machine. Leave in only the video. This will stop most of
the communication services due to no NIC. If that doesn't work go into the
bios and make check to see if you have on bios shadowing (this throws it off
sometimes and makes it react in a different manner). Either enable them or
disable them depending on the original settings. If you get it up, set the
services that are not needed to manual. Reboot noting which ones you
started with. Incrementally add a piece of hardware back to your system and
you will probably find the bug by then. It will probably be a driver of
some sort that is not compatible with Win2k. Good luck.

-Harry Bates
Rock Systems & Development