4.2 Troubleshooting and Repair
Your computer may reboot for no apparent reason, and without any prior warning.
This is the default behavior when Windows XP encounters a System failure. This behavior can be changed by going to the System applet in Control Panel, select the Advanced tab and click the Settings button under the Startup and Recovery heading. Under System failure, un-check Automatically restart.
* FYI: This also pertains to Win 2000 also.
How to Use a Windows Boot Disk to Prevent Boot Failure in Windows 2000 or Windows NT (Q101668)•How to Use System Files to Create a Boot Disk to Guard Against Being Unable to Start Windows XP (Q314079)
Windows 2000 Resource or download the information as a compressed Microsoft Word file from the link below. If you do not own Word, Wordpad will open it as well.
We recommend performing a right-click and Save Target As: FNDC_REC.doc.
Another way to access the viewer is by going to START menu >> Run, type eventvwr.msc and pressing ENTER (works in all flavors).
To make the tool easier to access In XP, you can right click on the START button >> Properties >>> Customize >> Advanced tab, then scroll down until you see System Administrative Tools and check 'Display on the all programs menu'.
Now that you know the system error codes, you can uses the resources below to find out what they mean.
This Microsoft TechNet link allows you to enter your event information and get the details and possible fixes to correct the error.
Events and Errors Message Center
Additional information on system error codes can be found at this MSDN site: System Error Codes.
Windows Server 2003 Resources.
Boot.ini and ARC Path Naming Conventions and Usage. This Microsoft Software Developers Network document explains further -- Overview of the Boot.ini File.
Available Switch Options for the Boot.ini File are described in this MS article.
How do I edit my Boot.ini?
If you just want to Remove an Invalid Entry, you can use this method.
Before editing the Boot.ini file, you must remove the file attributes that Windows uses to protect the file from inadvertent changes. When the Boot.ini file is on an NTFS file system drive, you must be a member of the Administrators group on the computer to change its attributes. Use the following procedure to prepare the Boot.ini file for manual editing. This procedure removes the system, hidden, and read-only attributes of the file.
Refer to this MSKB article on using bootcfg.exe to (among other things) modify the boot.ini -- Description of the BOOTCFG Command and Its Uses.
For more extensive Boot.ini editing refer to:
Feedback received on this FAQ entry:
There are three situations that can cause this to happen:
•If you try to run CHKDSK on the boot volume - CHKDSK cannot dismount the boot volume. If you try to run the CHKDSK repair process on the boot volume, the system gives you the choice to run CHKDSK (actually AUTOCHK) on the next reboot.
•Files are open (on any volume) will prevent CHKDSK from running
•If the "dirty bit" is set - There is a system flag known as the dirty bit that indicates that AUTOCHK will be run on the next reboot. This is usually set when the system (or a program like a defragger) thinks there is an error in the volume.
To see the status of the dirty bit, use the following command (at the Command Prompt):
fsutil dirty query c: (assuming, in this case, the C: Drive)
If AUTOCHK tries to run, you should allow it to run until completion. After it runs, you can check the completion status in the Event Viewer (applicaton log). Simply look for entries with Winlogin as the source.
If after running AUTOCHK to completion, it wants to run again, this may be the sign of a persistent hardware problem. At that time, one should consider running the manufacturer's diagnostics on the hard drive.