Discussion Locked

INACCESSIBLE_BOOT_DEVICE

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

- we just upgraded a system 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 as expected, 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 during POST) -
- we have reinstalled the old motherboard, and system boots fine, with all drives functioning as expected, confirming no system damage .... but with new motherboard, error message returns as before -
- 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

6 replies

by thechas

Windows 2000 and XP do not take well to being moved to new hardware.

The supported procedure from Microsoft is to:

Back up the hard drive on the old hardware

Perform a fresh install of Windows on the new hardware

Restore from the backup.

Assuming that your user name is a valid e-mail address, I will e-mail the Microsoft Knowledge base article to you.

(Microsoft lost the article when they changed their naming format.)

Chas

by ybnormal

- most helpful ... thank you for the article -
- FYI: we have, in the meantime, located MS Knowledge Base Article #287043 which addresses our situation, and advises a Win2000 Setup repair process which actually worked! (after nearly a dozen attempts while choosing different options) .... thus with that repair and a bit of final adjustment, we were able to recover our original configuration! ... hope this can be useful to you in the future -

by timwalsh

The issue is that the motherboards probably use chipsets from different manufacturers. Therefore, the IDE controller drivers on the disk don't match the IDE controller actually on the MB. When Win2K is installed, it installs drivers only for the chipset detected. When you you move the drive, because of the above mismatch, Windows can't "read" the drive and therefore won't boot.

There actually is a workaround available from Microsoft. Take a look at MS Knowledge Base article 314082 (Whilethe title of the article talks about WinXP, the fix works with Win2K also.

I don't know if this is the same article Chas is talking about. Chas talks about the Microsoft-supported solution. The above article gives talks about (in detail) an unsupported solution. This is the workaround of which I speak. I have used this on several occasions and it has worked.

by timwalsh

I should add that this workaround worked for me under similar conditions. But this is no guarantee that it will work for you in your circumstances. Because Microsoft does not "support" the solution, you will be using it at your own risk.

by ybnormal

- most helpful ... hadn't thought of that issue -
- FYI: we have, in the meantime, located MS Knowledge Base Article #287043 which addresses our situation, and advises a Win2000 Setup repair process which actually worked! (after nearly a dozen attempts while choosing different options) .... thus with that repair and a bit of final adjustment, we were able to recover our original configuration! ... hope this can be useful to you in the future -

This discussion is closed to new replies.