"inaccessable_boot_device"

  • Thread starter Thread starter Ron Lehman
  • Start date Start date
R

Ron Lehman

- we just upgraded from an AOpen AK72 motherboard (with
Athlon 700MHz CPU)to an ASUS A7A266 motherboard (with
Athlon XP 2400+ CPU) -
- system worked fine with the former motherboard and no
changes were made to the system hardware other than
motherboard replacement -
- we can boot to the floppy drive so we used it to flash
the BIOS to the latest version (ASUS A7A266 ACPI BIOS
Revision 1012) and now the system can recognize the CPU as
2400+ and memory checks out OK (1.5G Corsair SDRAM)-
- problem: when booting to the hard drive, everything
checks out OK until the Windows 2000 Pro opening screen
which quickly becomes a blue screen with following message:
" *** STOP: 0x0000007B
(0xF681B84C,0xC0000034,0x00000000,0x00000000)
INACCESSIBLE_BOOT_DEVICE " and includes suggestions for
checking hard drives and controllers -
- we have no reason to believe anything has changed or
corrupted the hard drives .... we simply replaced the
motherboard, and we have checked all connections to board
and drive (system correctly identifies all drives when
posting) -
- can anyone explain why ? .... and how to solve this
problem ? -


system:
ASUS A7A266 mainboard
3 Corsair 512M SDRAM DIMMS
primary master - Maxtor 80G drive
primary slave - Hitachi DVD-ROM drive
secondary master - WDC 80G drive
secondary slave - TDK CD-RW drive
floppy drive
NVIDIA video AGP card
Diamond modem PCI card
NetGear PNA network PCI card
 
Greetings --

Normally, unless the new motherboard is virtually identical to the
old one (same chipset, IDE controllers, etc), you'll most likely need
to perform a repair (a.k.a. in-place upgrade) installation, at the
very least (and don't forget to reinstall any service packs and
subsequent hot fixes):

How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175

What an In-Place Win2K Upgrade Changes and What It Doesn't
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306952

If that fails:

How to Move a Windows 2000 Installation to Different Hardware
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q249694&ID=KB;EN-US;Q249694


Bruce Chambers

--
Help us help you:



You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
 
we simply replaced the
motherboard, and we have checked all connections to board
and drive (system correctly identifies all drives when
posting) -
- can anyone explain why ? .... and how to solve this
problem ? -
Click to expand...

Why? Because Microsoft built this flaw into Windows 2000.

Solution in Bruce Chambers post - I strongly recommend you bookmark the MS
support website. You'll need it.
 
- can anyone explain [Stop 0x7B]?
- and how to solve this problem?
Click to expand...

I suggest putting the AK72 back in the system. Then add the necessary
drivers and registry settings for the various IDE chipsets as explained in
KB article 271965.

Then put the new motherboard in and cross your fingers.
 
Back
Top