I have my System/Startup/Recovery option for Automatic Reboot checked. I
want my system to reboot automatically on any system failures (i.e., Win2K
blue screens). For some reason, this setting does not seem to work. On the
last blue screen I got, the system just sat there without rebooting.

--
-----------------------------------
Ken Varn
Senior Software Engineer
Diebold Inc.
(E-Mail Removed)
-----------------------------------

Just to clear things up. I am a Senior Software Engineer and know what is a
blue screen System Stop condition. Right now I can tell you that I have a
rogue 3rd party device driver that is causing the problem and so far it is
extremely rare and difficult to reproduce. So as a safeguard, I would like
Windows 2000 to restart on any blue screen condition as should be the case
when the "Automatically Reboot" option is selected. But for some reason
this does not happen when the condition occurs.

--
-----------------------------------
Ken Varn
Senior Software Engineer
Diebold Inc.
(E-Mail Removed)
-----------------------------------
""Seaver"" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Dear Ken,
>
> Thank you for your posting.
>
> According to your post, you wonder why sometimes computer won't reboot
> after blue screen error.
>
> If I have misunderstood your concern please don't hesitate to let me know.
>
> The "Automatically Reboot" will function whenever the system stops
> unexpectedly. However, not every blue screen error message equals with
> recognizable system stop. In general, blue screen errors are characterized
> by the entire screen going blue, resembling that of a DOS program, and an
> error message is displayed. These errors can be as simple as a floppy disk
> or CD being removed from the drive while being read from or as complex as
a
> read error on the hard drive. In many cases, the error is caused by a read
> error. This means that the operating system is attempting to write or read
> to/from a media device it was once able to.
>
> If, at the blue screen, you see "Fatal Exception Error" This usually
points
> to duplicate or incompatible DLL files being called into memory. Hit ENTER
> and try to get back to the Desktop. In the future, try to notice patterns,
> particular combinations of programs that cause the error. Look for
software
> patches at the vendor's web sites. In short, both hardware and software
> conflicts, incompatible driver or even physical hardware failure such as
> unmatched RAM chips can the cause.
>
> Therefore whenever the same blue screen error reoccurs, I suggest that you
> perform troubleshooting to find its root cause, and then eliminate the
> problem. You may refer to the following resource for more information:
>
> 325011 Support WebCast: "Blue Screen" Error Troubleshooting
> http://support.microsoft.com/?id=325011
>
> Hope it help!
>
> Sincerely,
>
> Seaver Ren
>
> Product Support Services
> Microsoft Corporation
>
> This posting is provided "AS IS" with no warranties, and confers no rights
> Get Secure! - www.microsoft.com/security
>
>
>

Dear Ken,

Thank you for your reply.

Our initial response post is aimed to explain why not every blue screen
error message will cause Windows 2000 to reboot automatically. Please feel
free to let me know if you have any further concern. In the meantime,
concerning with your description regarding the third party device driver, I
suggest that you keep troubleshooting to find and then remove the root
cause, so that the computer's performance and security can be better
assured.

1. Please gather blue screen information by using steps described in the
following article:

192463 Gathering Blue Screen Information After Memory Dump in Windows 2000
or
http://support.microsoft.com/?id=192463

More Information
=============
216206 Blue Screen or STOP Error Message Troubleshooting Before You Call
http://support.microsoft.com/?id=216206

2. You may choose to install the Debugging Tools downloadable from the
following URL,
http://www.microsoft.com/whdc/ddk/de...g/default.mspx

and then use the tool to locate the culprit.

3. Analyze the collected information to locate the culprit. The detailed
steps are mentioned from the following resource:

325011 Support WebCast: "Blue Screen" Error Troubleshooting
http://support.microsoft.com/?id=325011

4. If you want to create a service request so that we can better server
you, please submit questions by creating a new case at the Online Support
site. For your convenience, I have included the following link.
http://support.microsoft.com/support/webresponse.asp

Hope them help!

Regards,

Seaver

Albeit I need to find the reason why the blue screen is occurring. However,
the original question was why didn't Windows 2000 reboot the machine as
instructed in the System configuration setting?

--
-----------------------------------
Ken Varn
Senior Software Engineer
Diebold Inc.
(E-Mail Removed)
-----------------------------------
""Seaver"" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Dear Ken,
>
> Thank you for your reply.
>
> Our initial response post is aimed to explain why not every blue screen
> error message will cause Windows 2000 to reboot automatically. Please feel
> free to let me know if you have any further concern. In the meantime,
> concerning with your description regarding the third party device driver,
I
> suggest that you keep troubleshooting to find and then remove the root
> cause, so that the computer's performance and security can be better
> assured.
>
> 1. Please gather blue screen information by using steps described in the
> following article:
>
> 192463 Gathering Blue Screen Information After Memory Dump in Windows 2000
> or
> http://support.microsoft.com/?id=192463
>
> More Information
> =============
> 216206 Blue Screen or STOP Error Message Troubleshooting Before You Call
> http://support.microsoft.com/?id=216206
>
> 2. You may choose to install the Debugging Tools downloadable from the
> following URL,
> http://www.microsoft.com/whdc/ddk/de...g/default.mspx
>
> and then use the tool to locate the culprit.
>
> 3. Analyze the collected information to locate the culprit. The detailed
> steps are mentioned from the following resource:
>
> 325011 Support WebCast: "Blue Screen" Error Troubleshooting
> http://support.microsoft.com/?id=325011
>
> 4. If you want to create a service request so that we can better server
> you, please submit questions by creating a new case at the Online Support
> site. For your convenience, I have included the following link.
> http://support.microsoft.com/support/webresponse.asp
>
> Hope them help!
>
> Regards,
>
> Seaver
>

Dear Ken,

General causes of blue screen error message include incompatible hardware
driver, corrupt registry or system files and even conflicting third party
programs. Since they are multiple, and not every of them will cause ASR
function as expected due to the affection from User Mode, so far we cannot
conclude the cause without further troubleshooting on your specific issue.

If you'd like to find the culprit, I suggest that you perform the following
steps:

1. Gather the necessary information using steps listed in the following
article:

192463 Gathering Blue Screen Information After Memory Dump in Windows 2000
http://support.microsoft.com/?id=192463

2. Since dump debugging has been beyond Community's support policy, to
locate the root cause, please open a new service request Online or via
Phone Call. You may submit additional support questions by creating a new
case at the Online Support site. For your convenience, I have included the
following link.
http://support.microsoft.com/support/webresponse.asp

Regards,

Seaver