Automatic Reboot after Lockup or BSOD

Some sites believe that security is enhanced and important information
preserved, if systems are not allowed to restart automatically after a failure
or lockup. If you have adequate operations staff to support the option or
overriding security issues, the option is controlled by the following Windows NT
registry hack:

Hive:HKEY_LOCAL_MACHINE
Key:\SYSTEM\CurrentControlSet\Control
Name:
CrashControl
Type: REG_DWORD
Value: 0Disable automatic reboot
Value:
1 Enable automatic reboot

Related: Q174630 –
Windows NT Restarts Continuously with Blue Screen
.

A common Blue Screen of Death, BSOD, is STOP 0x0000007F
(UNEXPECTED_KERNEL_MODE_TRAP). This stop error is caused by hardware
problems. The common causes are overclocking the processor, mismatched memory
modules, a bad RAM module, and a motherboard problem. If you attempted to boost
processor speed using overclocking, be aware that the heat generated tends to
damage the motherboard. If you haven’t been experimenting with overclocking,
open your box and reseat everthing: RAM modules, cards, cables, … If the stop
error still occurs, swap out your RAM. If you eliminate RAM as the cause, then
you probably have a motherboard problem.

Consider Blue Screen Administration for Windows NT and 2000

offers you the chance to administer your Windows NT
and Windows 2000 after a Blue Screen and fix boot errors or save data from
defunct volumes. You can boot NT/2000 from disk and so gain access to systems
whose passwords have been forgotten.

Leave a Comment

Your email address will not be published.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Scroll to Top