Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
Load Failures Listed in the Bootlog.txt File
Article ID: 127970 - View products that this article applies to.
This article was previously published under Q127970
The Bootlog.txt file in the root folder on your hard disk may contain the following lines, even though your computer is running properly:
These load failures do not necessarily indicate a problem. It is common for some, if not all, of these load attempts to fail, depending on your system configuration. The following sections of this article contain more information about the causes of specific types of load failures.
LoadFailed = dsoundMany sound drivers are DirectSound-enabled. DirectSound is part of Microsoft DirectX, a set of libraries that are used by most Windows-based games. When a DirectSound-enabled sound driver is loaded, the driver attempts to register with the DirectSound library so that games can use the library. If no DirectX-based games are installed on your computer, the DirectSound library is not loaded. This behavior is typical.
LoadFailed = ebiosIf the extended basic input/output system (BIOS) driver does not find an extended BIOS, the driver is not loaded.
LoadFailed = ndis2sup.vxdIf the network driver interface specification (NDIS) 2 support driver does not find any NDIS 2 drivers to support, the driver is not loaded.
LoadFailed = vpowerdIf the Advanced Power Management (APM) driver determines that your computer does not support APM, the driver is not loaded. However, APM support might be disabled. To determine if APM is disabled in Device Manager:
LoadFailed = vserver.vxdVserver.vxd saves memory by loading later in the startup process only if it is needed, rather than loading statically. For example, Vserver.vxd might not be needed when you start a laptop computer while the laptop computer is out of its docking station.
LoadFailed = vshareIf you examine the Bootlog.txt file, the file indicates that Vshare loaded successfully earlier in the startup process. The second copy of Vshare detects the instance of Vshare that is already loaded, and the second copy is not loaded.
Font FailuresAfter you first start Windows, the Bootlog.txt file may list many font load failures. This behavior is typical. When Font Manager searches the hard disk for fonts, it may find fonts in several folders. After Font Manager finds fonts, it records the information so that future attempts to locate a font proceed more quickly.
InitCompleteFailed = SDVXDWindows automatically loads a miniature disk cache to increase the speed of the startup process. When the startup process is complete, the miniature disk cache is unloaded from memory. When the cache is unloaded, the "InitCompleteFailed = SDVXD" line is added to the Bootlog.txt file to indicate that the miniature disk cache has been removed from memory. This behavior is typical.
SysCritInitFailed = JAVASUPIf the Java support driver is not needed on your computer, the driver is not loaded. Java is a programming language that is used on the World Wide Web (WWW). Microsoft Internet Explorer versions 3.0 and later include a Java subsystem.
DeviceInitFailed = MTRRMemory Type Range Registers (MTRR) is a .vxd file that is responsible for manipulating memory ranges. This file is loaded with DirectX 5.0; however, none of the DirectX core components use the service that is provided by MTRR. The Ntkern file and some video adapter drivers do use the service that is provided by MTRR to change memory ranges.