System TipThis article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you.Visit the Windows 7 Solution Center
This article was previously published under Q314082
If you are a Small Business customer, find additional troubleshooting and learning resources at the Support for Small Business site.
This article describes how you may receive a Stop error when you try to start the Microsoft Windows XP-based backup computer after you move the system disk to a backup computer. This issue occurs when registry entries and the drivers for the mass storage controller are not installed in Windows XP. To resolve this issue, use the same hardware in the backup computer.
After you move the Microsoft Windows XP system (boot) disk
to a backup computer, you may receive the following Stop error when you try to
start the Windows XP-based backup computer:
This error may occur if the registry entries and the
drivers for the mass storage controller hardware in the backup computer are not
installed in Windows XP.
For integrated device electronics (IDE)
controllers, there are several different chip sets available, such as Intel,
VIA, and Promise. Each chip set has a different Plug-n-Play identifier
(PnP-ID).
The PnP-ID information of mass storage controllers for the
backup computer must be in the registry before startup so that Windows XP can
initialize the correct drivers.
To resolve this error, use the same hardware for the
backup computer:
Replace the problem hardware components in the backup
computer with components of the same manufacturer, make, and model as the
motherboard in the computer that you are backing up.
If the system disk is a SCSI disk, use the same make and
model of SCSI controller in the new computer.
If the system disk is an IDE disk, use the same kind of
motherboard in the new computer, a motherboard that has the same kind of IDE
chip set and the same PnP-ID as the motherboard in the computer that you are
backing up.
For SCSI-based system disks, you can prime the registry and
make sure that the drivers that you want are in place by installing the SCSI
controller that is used by the backup computer before you transfer the system
disk contents. Windows XP PnP detects the controller, sets up critical registry
entries, and copies the appropriate driver.
After you see the SCSI
controller in Device Manager, you can remove the alternate controller. If you
have to move the system disk to another computer that has the same make and
model of SCSI controller in the future, Windows XP will start successfully
because Windows XP has already used that controller one time and has retained
the correct configuration information.
Although Microsoft does not support this method, you can
import or merge the required registry entries, and copy the drivers beforehand
to support all IDE controllers that are natively supported by Windows XP. Note
that although this method might enable the relocated system disk to start
successfully, other hardware differences can lead to other problems.
This solution provides support for IDE controllers whose PnP-ID matches one of
the PnP-IDs in the following list. However, if you want to determine beforehand
the IDE controllers that are used in your current and backup computers, you can
search the %SystemRoot%\Setupapi.log file for the PnP-ID that is detected while
the Setup program is running.
After you determine the PnP-IDs that
are used in your computers, you can choose to merge or to populate the registry
with only the PnP-IDs that you need.
The following list shows the
PnP-IDs of natively supported IDE controllers in Windows XP:
;*********** Standard IDE ATA/ATAPI Controllers *********
Secondary_IDE_Channel=%SystemRoot%\inf\Mshdc.inf
;*********** Generic ESDI Hard Disk_Controller **********
*PNP0600=%SystemRoot%\inf\Mshdc.inf
;*********** Aztech IDE Controller **********************
*AZT0502=%SystemRoot%\inf\Mshdc.inf
;*********** Device ID for Generic Dual PCI IDE *********
PCI\CC_0101=%SystemRoot%\inf\Mshdc.inf
;************ALI IDE Controller ******************************
PCI\VEN_10B9&DEV_5215=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_10B9&DEV_5219=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_10B9&DEV_5229=%SystemRoot%\inf\Mshdc.inf
;************Appian Technology **************************
PCI\VEN_1097&DEV_0038=%SystemRoot%\inf\Mshdc.inf
;************CMD Technology *****************************
PCI\VEN_1095&DEV_0640=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_1095&DEV_0646=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_1095&DEV_0646&REV_05=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_1095&DEV_0646&REV_07=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_1095&DEV_0648=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_1095&DEV_0649=%SystemRoot%\inf\Mshdc.inf
;************Compaq *************************************
PCI\VEN_0E11&DEV_AE33=%SystemRoot%\inf\Mshdc.inf
;*************Intel *************************************
PCI\VEN_8086&DEV_1222=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_8086&DEV_1230=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_8086&DEV_7010=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_8086&DEV_7111=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_8086&DEV_2411=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_8086&DEV_2421=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_8086&DEV_7199=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_8086&DEV_244A=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_8086&DEV_244B=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_8086&DEV_248A=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_8086&DEV_7199=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_8086&DEV_7601=%SystemRoot%\inf\Mshdc.inf
;*************PC Technology *****************************
PCI\VEN_1042&DEV_1000=%systemroot%\inf\Mshdc.inf
;*************Silicon Integrated System *****************
PCI\VEN_1039&DEV_0601=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_1039&DEV_5513=%SystemRoot%\inf\Mshdc.inf
;*************Symphony Labs *****************************
PCI\VEN_10AD&DEV_0001=%SystemRoot%\inf\Mshdc.inf
PCI\VEN_10AD&DEV_0150=%SystemRoot%\inf\Mshdc.inf
;*************Promise Technology ************************
PCI\VEN_105A&DEV_4D33=%SystemRoot%\inf\mshdc.inf
;*************VIA Technologies, Inc. ********************
PCI\VEN_1106&DEV_0571=%SystemRoot%\inf\Mshdc.inf
;*************Standard Microsystems Corp. ***************
PCI\VEN_1055&DEV_9130=%SystemRoot%\inf\Mshdc.inf
;*************Toshiba ***********************************
PCI\VEN_1179&DEV_0105=%SystemRoot%\inf\Mshdc.inf
To import this information, follow these steps on two different test computers that exhibit the Stop 0x0000007B error after you change
disks between computers. After you follow this procedure on each test computer,
you can probably move the hard disks and start both computers without receiving
the Stop 0x0000007B error. However, other hardware differences can cause other
problems.
Copy the following information into Notepad, and then save
the file on a 3.5-inch disk. Name the file Mergeide.reg,
without the .txt file name extension.
Extract the Atapi.sys, Intelide.sys, Pciide.sys, and
Pciidex.sys files from the %SystemRoot%\Driver Cache\I386\Driver.cab file, or
copy the files to the %SystemRoot%\System32\Drivers folder.
In Microsoft Windows Explorer, right-click the
Mergeide.reg file in the floppy drive, and then click
Merge.
Windows XP displays the following message:
Are you sure you want to add the information in
A:\Mergeide.reg to the registry?
Click
Yes.
After the import process is completed, Windows
XP displays another message:
Information from
A:\Mergeide.reg was successfully entered into the registry.
Quit Windows XP, turn off the computer, and then move the
system disk to the other test computer, the one that previously produced a Stop
0x0000007B error, and then test to see if you can successfully start the second
computer.