Version 6 by Mahmoud Al-Qudsi
on Jul 03, 2008 18:32.

<< Changes from 5 to 6
compared with
Current by Mahmoud Al-Qudsi
on Sep 09, 2008 22:53.
(show comment)
 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 4 changes. View first change.

 h1. Troubleshooting Various Windows XP Dual-Boot Problems
  
 Unfortunately, as a result of the [convoluted process|Windows XP] used to load Windows NT through XP/2003 up and running, there is plenty of room for confusion and error.
  
 h2. General Troubleshooting Guidelines
  
 # Make sure EasyBCD's Windows XP entry points to the *boot drive* and that the boot drive has NTLDR, NTDETECT.COM, BOOT.INI in the root directory. You can grab those files [here|http://neosmart.net/wiki/pages/viewpageattachments.action?pageId=196612].
 # Quadruple-check your BOOT.INI {{\[operating systems\]}} list. Make sure the {{default}} entry matches one of the entries in the {{\[operating systems\]}} list. Make sure {{rdisk(x)partition(y)}} points to the right partition that Windows XP is installed to.
  # Quadruple-check your BOOT.INI {{\[operating systems\]}} list. Make sure the {{default}} entry matches one of the entries in the {{\[operating systems\]}} list. Make sure {{rdisk(x)partition\(y)}} points to the right partition that Windows XP is installed to.
 # Make sure you only have one copy of NTLDR, NTDETECT.COM, and BOOT.INI on your system. Having multiple copies leads to lots of confusion as to which files you should edit and check.
 # Make sure you selected "Windows XP" from the drop-down menu in EasyBCD's Add/Remove Entries section when you added XP to the Vista bootloader. If you kept it at the default option ("Windows Vista/Longhorn Server"), Windows XP will never boot.
  
 h2. Specific Error Messages
  
  
 h3. NTLDR is missing or corrupt (or one of its variants)
  
 {noformat}
 Windows Boot Manager has experienced a problem.
 File: \ntldr
 Status: 0xc000000f
 Info: The selected entry couldn't be loaded because the application is missing or corrupt.
 {noformat}
 As this error message says, NTLDR could not be located. Make sure the Windows XP entry in EasyBCD points to the system drive and keep in mind that this is _not_ necessarily the same as the drive that Windows XP is installed to.
  
 If the drive is correct, make sure NTLDR and NTDETECT.COM exist in the root partition. If they don't or if they're corrupted, you can [download them here|http://neosmart.net/wiki/pages/viewpageattachments.action?pageId=196612].
  
 h3. After choosing to boot into Windows, I get a black, blank screen.
  
 This means that NTLDR was found, but NTDETECT.COM wasn't. Grab it [here|http://neosmart.net/wiki/pages/viewpageattachments.action?pageId=196612].
  
 h3. winload.exe is missing or corrupt
  
 {noformat}
 Windows Boot Manager has experienced a problem.
 File: \windows\system32\winload.exe
 Status: 0xc000000f
 Info: The selected entry couldn't be loaded because the application is missing or corrupt.
 {noformat}
 You added a Windows XP entry without setting the "Type" drop-down box in EasyBCD to Windows XP. Delete this entry, go back to the Add/Remove Entries section, and re-create it. This time, make sure to set its type to Windows XP before doing so.
  
 h3. ntoskrnl.exe is missing or corrupt
  
 {noformat}
 "Windows could not start because the following file is missing or corrupt:
  
 <Windows root>\system32\ntoskrnl.exe.
  
 Please re-install a copy of the above file"
 {noformat}
This means the ARC paths in the {{\[operating systems\]}} section or the {{default}} entry in BOOT.INI is incorrect. Double-check that {{multi()}} and {{disk()}} are both set to 0, and verify that {{rdisk(x)partition(y)}} points to the correct partition where Windows XP is installed. Instructions on the correct configuration of boot.ini can be found [here|Rebuilding Boot.ini].
  This means the ARC paths in the {{\[operating systems\]}} section or the {{default}} entry in BOOT.INI is incorrect. Double-check that {{multi()}} and {{disk()}} are both set to 0, and verify that {{rdisk(x)partition\(y)}} points to the correct partition where Windows XP is installed. Instructions on the correct configuration of boot.ini can be found [here|Rebuilding Boot.ini].
  
 h3. Hal.dll is missing or corrupt
  
 {noformat}
 Windows\System32\Hal.dll missing or corrupt:
  
 Please re-install a copy of the above file.
 {noformat}
This means the ARC paths in the {{\[operating systems\]}} section or the {{default}} entry in BOOT.INI is incorrect. Double-check that {{multi()}} and {{disk()}} are both set to 0, and verify that {{rdisk(x)partition(y)}} points to the correct partition where Windows XP is installed. Instructions on the correct configuration of boot.ini can be found [here|Rebuilding Boot.ini].
  This means the ARC paths in the {{\[operating systems\]}} section or the {{default}} entry in BOOT.INI is incorrect. Double-check that {{multi()}} and {{disk()}} are both set to 0, and verify that {{rdisk(x)partition\(y)}} points to the correct partition where Windows XP is installed. Instructions on the correct configuration of boot.ini can be found [here|Rebuilding Boot.ini].
  
 h3. &nbsp;Windows could not start because of a disk hardware configuration problem
  
 {noformat}
 Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk.
  
 Check boot path and disk hardware. Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information.
 {noformat}
 This means the ARC paths in the {{\[operating systems\]}} section or the {{default}} entry in BOOT.INI is incorrect. Double-check that {{multi()}} and {{disk()}} are both set to 0, and verify that {{rdisk(x)partition(y)}}points to the correct partition where Windows XP is installed.
  This means the ARC paths in the {{\[operating systems\]}} section or the {{default}} entry in BOOT.INI is incorrect. Double-check that {{multi()}} and {{disk()}} are both set to 0, and verify that {{rdisk(x)partition\(y)}}points to the correct partition where Windows XP is installed.
  
 Generally speaking, this particular error message means that the partition referenced in the ARC paths in boot.ini does not exist, so check the {{partition()}} number first. If you're sure the {{partition()}} value is correct then try different {{rdisk()}} values until you get a working configuration. Further instructions on the correct configuration of boot.ini can be found [here|Rebuilding Boot.ini].
  
 h3. I get a BSOD when I boot into Windows XP
  
 Congratulations\! As hard as it may be to believe, this means your dual-boot is working just fine. Unfortunately, _after_ EasyBCD successfully starts to load Windows XP, it crashes. This can be caused by using an imaged copy of a Windows XP installation from another PC, a hardware mis-configuration, or one of the zillion other BSOD-causing problems. Your best bet is to perform an [in-place upgrade/repair install|http://support.microsoft.com/kb/315341] of Windows XP and/or ask for help in [our friendly forums|http://neosmart.net/forums/].