Role of Bootlog.txt in Windows 98 Troubleshooting

During the Windows 98 era, Bootlog.txt served as a critical diagnostic log file that recorded every action taken by the operating system during the startup sequence. This article explains how technicians and users generated this log, how it tracked the initialization of hardware drivers and system components, and how reading its entries allowed users to pinpoint the exact causes of startup freezes, crashes, and driver conflicts.

In Windows 98, startup failures often manifested as a frozen screen, a blue screen of death, or an abrupt reboot with little to no explanatory error messaging. To diagnose these issues, users could generate a Bootlog.txt file by pressing the F8 key (or holding Ctrl) during system POST to bring up the Windows 98 Startup Menu, then selecting the "Logged (\BOOTLOG.TXT)" option. The operating system could also generate this log by executing the command win /b directly from the MS-DOS prompt.

Once enabled, the operating system created or updated Bootlog.txt in the root directory of the boot drive (typically C:\Bootlog.txt). The file recorded the loading process in chronological order, documenting the initialization of real-mode device drivers, virtual device drivers (VxDs), system fonts, and core dynamic-link libraries (DLLs).

Each logged event typically generated paired entries: an initiation entry and a completion status. Common entries appeared as:

  • Loading Device = [driver name] followed by LoadSuccess = [driver name] or LoadFailed = [driver name]
  • Loading Vxd = [vxd name] followed by LoadSuccess = [vxd name] or LoadFailed = [vxd name]
  • SYSCRITINIT = [component] followed by SYSCRITINITSUCCESS = [component]

When Windows 98 hung or crashed during startup, troubleshooting involved booting into Safe Mode or an MS-DOS prompt and opening Bootlog.txt in a text editor like Notepad or DOS Edit. The primary indicator of a failure was often the very last line in the file. If an operation showed a "Loading" entry without a corresponding "LoadSuccess" entry, it indicated that the system crashed while attempting to initialize that specific driver or device.

Additionally, searching the file for "LoadFailed" or "Failure" helped identify missing files, corrupted system components, or conflicting hardware resources. While some LoadFailed entries were harmless—such as Windows checking for hardware that was not physically installed—a failed load of a critical video driver, disk controller, or network adapter provided a clear path to resolution. Technicians could then disable, remove, or replace the offending driver in Safe Mode to restore normal system operation.