Problem 3: Inaccessible Boot Device in Windows XP ( WINXP )
After you change motherboards, or move the Windows
system (boot) disk to another computer with a different motherboard, you
may receive the following blue screen stop message when you try to
***STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
This event is standard with Win2000, and uncommon with Win98 and Me. The cause is that the registry entries and drivers for the mass storage controller hardware on the new motherboard are not installed in Windows. Accordingly, Windows setup can't find the drive controller and/or the driver for it. Other causes might be:
- The boot device setting in CMOS setup may be incorrect, or
- poor drive or drive controller cable connections.
Win2K can cope with most hardware changes (by running the Found New Hardware wizard) but only if it can boot as far as the GUI desktop in the first place. And one of the few device changes that might prevent that is a change to the hard disk controller.
For IDE controllers, there are several different
chipsets available. Each chipset uses a different Plug-n-Play (PNP) ID
to identify it. The PNP-ID information of mass storage controllers
for the new motherboard must be in the registry prior to startup for
Windows to initialize the correct drivers. To fix, you must
install the UDMA 66/100 or SCSI controller drivers in Win2000 before the
hard drive will be recognized as the primary boot device; (To install
drivers: <F6> during Setup).
In addition to the OS-specific motherboard-change
procedures described later in this document, users report that the
following solutions also correct this IBD problem.
IBD Solution 1: Load generic Microsoft drivers
IBD Solution 2: Load mass storage drivers for new motherboard during setup
IBD Solution 3: Load mass storage drivers for new motherboard during setup
IBD Solution 5: Install unbootable drive as slave