home.gif button
editorial.gif button
aboutus.gif button
search.gif button
technology.gif button
projects.gif button
site map.gif button
archive.gif button
search.gif button

BuildOrBuy Group Network
www.buildorbuy.org | www.buildorbuy.net ]

BuildOrBuy News
images/bullet2.gifMicrosoft Online Crash Analysis - Welcome
BSOD - Stop Error Messages:

Stop Error - A serious Error affecting the Operating System possibly placing Data at risk. The Operating System generates an obvious message, a screen with the STOP Error, rather than continuing on and possibly causing further damage. A STOP Error is also called a Fatal System Error a.k.a. BSOD in some circles.

Choosing Recovery Actions if Windows Stops Unexpectedly:

Using the Recovery feature in Control Panel, under 'System' - Configure Windows to do the following when a Stop Error or Fatal System Error occurs:

  1. Write an Event to the System Log. Best choice!
  2. Alert Administrators - User YOU!
  3. Dump System Memory to a File for Advanced Users to use in Debugging the Error.
  4. Automatically Restart the Computer.

The Dump of System Memory to a Log File can be valuable for Debugging the cause of a Stop Error. Note: Windows 2000 writes the Log File to the same File Name (Memory.dmp, by default) each time a Stop Error occurs. To preserve Log Files, rename the Log File with a unique name after the Computer Restarts.

  1. Specify what Windows 2000 does if the system stops unexpectedly: Details of above.
    1. Open System in Control Panel.
    2. On the Advanced tab, click Startup and Recovery, and under System Failure, choose which of the following actions Windows 2000 should perform if a Stop Error occurs:
      1. Write an event to the system log specifies that Event information will be recorded in the System Log.
      2. Send an administrative alert specifies that your system administrator will be notified.
      3. Automatically reboot specifies that Windows 2000 will automatically restart your computer.
    3. Under Write Debugging Information, choose what type of information Windows 2000 should record when the system stops unexpectedly.
      1. Small Memory Dump records the smallest set of useful information that will help identify the problem. This option requires a Paging File of at least 2 MB on the Boot Volume of your computer and specifies that Windows 2000 will create a new file each time the system stops unexpectedly. A history of these files is stored in the directory listed under Small Dump Directory.
      2. Kernel Memory Dump records only kernel memory, which speeds up the process of recording information in a log when the system stops unexpectedly. Depending on the amount of RAM in your computer, you must have 50 MB to 800 MB available for the paging file on the boot volume.
      3. Complete Memory Dump records the entire contents of system memory when the system stops unexpectedly. If you choose this option you must have a paging file on the boot volume large enough to hold all of the physical RAM plus one megabyte (MB).
  2. Basic STOP Error (Blue Screen) Troubleshooting (PPT File.)
  3. Microsoft TechNet - Appendix B - Troubleshooting Stop Errors: Win2000.
  4. www.gregorybraun.com - Software Design - Error Messages for Windows: (5/23/2003).


To Recover When Win2000 Stops:
  1. Restart the computer and log on using an account in the Administrators Group.
  2. Open Event Viewer, archive the currently logged security events (if desired), and then clear all events from the security log.
  3. Open Registry Editor and locate the following key:

    HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Control\Lsa

  4. Delete and replace the CrashOnAuditFail value, using data type REG_DWORD and a value of 1.
  5. Exit Registry Editor and restart the computer.

Caution: Edit the Registry @ your own risk! NOT for the squeamish!

Config Files
DNS Events
Event Logs
Network Protocols
Ntldr Is Missing
Windows Help
Microsoft Office Converters and Viewers - Microsoft Office

Copyright 1992, 1994, 1995-97, 2000-2001, BuildOrBuy Group Network News!
Web Development, Gill Boyd & Team - Posted 03/24/2003; Updated 06/16/2003