📎 AI Summary:
The thread discusses troubleshooting a BSOD error when booting a Windows XP VM created from a legacy disk image, likely caused by registry corruption or IDE controller configuration issues. The original poster confirms that setting the virtual hard drive controller to IDE (PIIX4) allows the VM to boot, but registry corruption prevents programs from functioning properly. Ultimately, they mention finding a solution related to disabling Windows XP’s IDE controller checks, with a link to their detailed answer on Superuser.

Cardinal System

Honorable Member
Joined
Jan 24, 2016
Messages
87
Thread Author #1
I am setting up a virtual machine to host a Windows XP environment with specific legacy software to replace a customer's broken Dell MTC2 desktop. I used Disk2vhd to generate a VHD from the customer's IDE hard disk and created the virtual machine with VirtualBox. The system begins to boot but then stops with the following BSOD error:

MLyjR.png


If I copy the C:\WINDOWS directory from a different Win XP installation to this same drive and boot from it, everything works with no issues. I suspect that somewhere in the C:\WINNT directory is there is a corrupt file or registry entry. I tried running the following commands in the recovery console, but the OS still fails to boot:
Code:
chkdsk /r
bootcfg /rebuild
fixboot

This tutorial mentions that "Windows memorizes which IDE/ATA controller it was installed on and fails to boot in case the controller changes." It says that the solution "is to perform several modifications to the Windows registry" to disable these checks, using a tool called `MergeIDE`. Unfortunately, this approach requires the original computer to be functional, which it is not. It also provides a link to an MS Docs page, but I cannot find anything that details how to disable this checks.

How can I resolve this issue?
 

Last edited:

Neemobeer

Windows Forum Team
Staff member
Joined
Jul 4, 2015
Messages
8,995
Make sure the hard drive controller within Virtual box is set to IDE. XP does not support SATA without a driver.
 

Cardinal System

Honorable Member
Joined
Jan 24, 2016
Messages
87
Thread Author #4
It's definitely a corrupt registry. I copied the registry files over from a fresh Windows XP installation (on the same disk) and the OS booted without an issue. However, a lot of the programs previously installed do not work without the original registry files.

7R2cU.png


In addition, a lot of the programs previously installed do not work without the original registry files. So this is not a real solution.
 

Last edited: