Just posting the contents of the file for easier viewing
21:16:40 2.17 LoadSuccess = C:\WINDOWS\IFSHLP.SYS
21:16:42 0.83 Loading Vxd = VMM
21:16:43 0.00 LoadFailed = ndis2sup.vxd
21:16:43 1.00 LoadSuccess = COMBUFF
21:16:50 0.00 DEVICEINITFAILED = MTRR
21:16:50 0.44 DEVICEINITSUCCESS = VTD
21:16:52 0.33 Dynamic load success s3.vxd
21:16:53 0.33 Dynamic load success mmdevldr.vxd
21:16:54 0.28 DEVICEINIT = IOS
21:16:56 0.94 DEVICEINITSUCCESS = VMOUSE
21:16:57 0.33 DEVICEINIT = NDIS
21:16:59 24.33 Dynamic load success vnbt.386
21:17:24 0.28 Initing hsflop.pdr
21:17:25 1.50 Initing esdi_506.pdr
21:17:26 1.50 Initing esdi_506.pdr
21:17:28 0.33 Init Success esdi_506.pdr
21:17:28 39.94 INITCOMPLETE = CONFIGMG
21:18:08 0.50 INITCOMPLETESUCCESS = CONFIGMG
21:18:09 0.00 INITCOMPLETEFAILED = SDVXD
21:18:10 0.28 Dynamic load success C:\WINDOWS\system\serial.vxd
21:18:11 0.50 Dynamic init success WINMODEM
21:18:11 0.33 Dynamic load success Bt848.vxd
From Microsoft, wondering about the MTRR one, anyone know
InitCompleteFailed = SDVXD
Windows 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.
DeviceInitFailed = MTRR
Memory 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.
LoadFailed = ndis2sup.vxd
If the network driver interface specification (NDIS) 2 support driver does not find any NDIS 2 drivers to support, the driver is not loaded.