Debugging Windows NT Setup STOP Screens

This article was previously published under Q123750
This article has been archived. It is offered "as is" and will no longer be updated.
SUMMARY
If a reproducible STOP screen error appears when you run Windows NT Setup,you can usually debug the error either locally or remotely. Since Setupdoes not run in debug mode by default, you must first change the Setupconfiguration to allow debugging, and then run Setup again. How you thenproceed depends upon whether the STOP screen occurs during the text portionor the Graphical User Interface (GUI) portion of Setup.
MORE INFORMATION
The STOP Screen Occurs While Booting the System from

the Setup Floppy Disk or During the Text Portion of Setup

If the STOP screen occurs while booting the system from the Setup floppydisk or during the text portion of Setup, and Setup was able to load enoughof the operating system to invoke the debugger, you may be able to set up adebug session. To configure Setup for debugging when booting from theSetup floppy disks:

  1. Make a copy of the disk labeled "Setup Boot Disk." If you created your boot floppy disks using the WINNT or WINNT32 installation methods, use disk one of the three-disk set.
  2. Edit the Txtsetup.sif file on the copy of the Setup Boot Disk.
  3. Change the OsLoadOptions = "/nodebug" entry to read:
    OsLoadOptions = "/debug"
    NOTE: You can also add other debug parameters to the string inside the quotes. For example:
    OsLoadOptions = "/debug /debugport=com2 /baudrate=19200"
  4. Save the changed file and boot from this modified disk.
If the startup sequence gets past the point at which Ntoskrnl.exe isloaded, then the debugger is loaded.

The STOP Screen Occurs During the Text

Portion of a WINNT /B or WINNT32 /B Installation

If the STOP screen occurs during the text portion of a WINNT /B or WINNT32/B installation, and your boot drive uses a File Allocation Table (FAT)partition, edit the Txtsetup.sif file on the root of drive C and change theOsLoadOptions = "/nodebug" entry to read:

OsLoadOptions = "/debug"

NOTE: You can also add other debug parameters to the string inside the quotes. For example:

OsLoadOptions = "/debug /debugport=com2 /baudrate=19200"


  1. Save the changed file and reboot into setup.
NOTE: You need to edit the C:\Txtsetup.sif file before booting to beginSetup but after WINNT or WINNT32 has finished copying the temporary filesto the hard drive.

The STOP screen Occurs During the GUI Portion

of Setup and Your Boot Drive Uses a FAT Partition

If the STOP screen occurs during the GUI portion of Setup and your bootdrive uses a FAT partition, edit the Boot.ini file on drive C, and add the/debug switch to the correct line in the [operating systems] section of theBoot.ini file. To do this, boot from an MS-DOS floppy disk after the textportion of Setup completes, change the Boot.ini file, and then reboot fromthe hard disk.

The Boot.ini file entry you need to edit should look similar to thefollowing:

   multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT Server   Version 3.5"				


The /debug switch should be added after the text in quotation marks.

The STOP Screen Occurs During the GUI Portion

of Setup and Your Boot Drive Uses an NTFS Partition

If your boot drive uses a Windows NT file system (NTFS) partition and youneed to debug the GUI portion of Setup:

  1. Create a boot disk for NTFS.
  2. Add the /debug switch to the correct entry in the [operating systems] section of the Boot.ini file, as well as any other switches needed to configure the computer for a remote or local debug. The entry to edit should look similar to the following:
    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT Server Version 3.5"
    The /debug switch should be added after the text in quotation marks.
  3. After Setup completes the text portion and prompts you to remove all floppy disks from the disk drives and reboot, place the boot disk you have created into drive A and reboot the system. This puts the system into debug mode for the GUI portion of Setup.
NOTE: The Windows NT Setup process uses standard NT kernel and system filesduring setup. To load the appropriate debugging symbols, copy the entirecontents of the Support\Debug\<Hardware Platform>\Symbols folder of theinstallation compact disc to your symbols folder. For example, when youattempt to debug the Windows NT 3.5 setup, load the debug symbols from theWindows NT 3.5 compact disc.

For additional information about the Boot.ini and its contents, query onthe following words here in the Microsoft Knowledge Base:

   Boot.ini and arc and path				


For more information on debug Setup for Windows NT (such as how toconfigure the modem for dial in and additional debug settings andparameters), see the Windows NT Executive Messages chapter in the "WindowsNT Messages" guide of the Windows NT 3.1 and 3.5 Resource Kits.
blue screen bluescreen hang halt 1 3 disk1 tshoot
Properties

Article ID: 123750 - Last Review: 02/28/2014 07:55:58 - Revision: 2.2

Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbhowto kbsetup KB123750
Feedback