Reboot / Restart --- continuously

[dvandusen]

I have a continuous reboot/restart on a W2K server after an update. The boot
process goes past the bios, then the boot up of the loader (the ...........
at the bottom of the screen when allowing an F8), then through the windows 2k
load (the splash screen with windows 2k with a progress bar at the bottom),
past the keyboard initialization (the lights on the shift led's), through the
final splash screen, and to the change to the light blue screen where the
pointer is supposed to show. It restarts after 2 seconds, just before the
point where the pointer icon displays. There are no devices on this machine
other than a Raid card that is/was working fine.

The f8, and last known good configuration did not work.

Thx

D

 

[Pegasus \(MVP\)]

"dvandusen" <dvandusen@discussions.microsoft.com> wrote in message
news:80395E70-46EC-41C0-8D49-8C6F9AF09EF0@microsoft.com...
>I have a continuous reboot/restart on a W2K server after an update. The
>boot
> process goes past the bios, then the boot up of the loader (the
> ...........
> at the bottom of the screen when allowing an F8), then through the windows
> 2k
> load (the splash screen with windows 2k with a progress bar at the
> bottom),
> past the keyboard initialization (the lights on the shift led's), through
> the
> final splash screen, and to the change to the light blue screen where the
> pointer is supposed to show. It restarts after 2 seconds, just before the
> point where the pointer icon displays. There are no devices on this
> machine
> other than a Raid card that is/was working fine.
>
> The f8, and last known good configuration did not work.
>
> Thx
>
> D

Try Safe Mode.

 

[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://msdn2.microsoft.com/en-us/library/ms789516.aspx



--

Regards,

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

"dvandusen" wrote:
>I have a continuous reboot/restart on a W2K server after an update. The
>boot
> process goes past the bios, then the boot up of the loader (the
> ...........
> at the bottom of the screen when allowing an F8), then through the windows
> 2k
> load (the splash screen with windows 2k with a progress bar at the
> bottom),
> past the keyboard initialization (the lights on the shift led's), through
> the
> final splash screen, and to the change to the light blue screen where the
> pointer is supposed to show. It restarts after 2 seconds, just before the
> point where the pointer icon displays. There are no devices on this
> machine
> other than a Raid card that is/was working fine.
>
> The f8, and last known good configuration did not work.
>
> Thx
>
> D

 

[dvandusen]

Now That is an answer!!!!!! I will try it, and give yourself a pat!

D

"Dave Patrick" wrote:

> 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://msdn2.microsoft.com/en-us/library/ms789516.aspx
>
>
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "dvandusen" wrote:
> >I have a continuous reboot/restart on a W2K server after an update. The
> >boot
> > process goes past the bios, then the boot up of the loader (the
> > ...........
> > at the bottom of the screen when allowing an F8), then through the windows
> > 2k
> > load (the splash screen with windows 2k with a progress bar at the
> > bottom),
> > past the keyboard initialization (the lights on the shift led's), through
> > the
> > final splash screen, and to the change to the light blue screen where the
> > pointer is supposed to show. It restarts after 2 seconds, just before the
> > point where the pointer icon displays. There are no devices on this
> > machine
> > other than a Raid card that is/was working fine.
> >
> > The f8, and last known good configuration did not work.
> >
> > Thx
> >
> > D
>

 

[Dave Patrick]

Hope it helps. You're welcome.

--

Regards,

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

"dvandusen" wrote:
> Now That is an answer!!!!!! I will try it, and give yourself a pat!
>
> D

 

[dvandusen]

Well, that did not shut off the autoreboot, but the settings that were in the
key indicated WERE different from what you suggested. Any other tricks?

Also, if the stop code is being logged, where would I find it? Are there
other logging facilities that I could turn on?

Thx

D

"Dave Patrick" wrote:

> Hope it helps. You're welcome.
>
> --
>
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "dvandusen" wrote:
> > Now That is an answer!!!!!! I will try it, and give yourself a pat!
> >
> > D

 

[Dave Patrick]

Try a digital camera to read the stop code. Almost always hardware failure
and or driver corruption. You can also copy off the memory.dmp file from
your parallel install. These may also help.

http://msdn2.microsoft.com/en-us/library/ms792466.aspx

--

Regards,

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

"dvandusen" wrote:
> Well, that did not shut off the autoreboot, but the settings that were in
> the
> key indicated WERE different from what you suggested. Any other tricks?
>
> Also, if the stop code is being logged, where would I find it? Are there
> other logging facilities that I could turn on?
>
> Thx
>
> D