Inaccessible Boot Device after installation of SP4 and solution

  • Thread starter Thread starter Karsten Ohme
  • Start date Start date
K

Karsten Ohme

I have tried to install Windows 2000 SP4.

Windows 2000 was installed on a 17 GB Maxtor 91731U4 slave disk. The
primary disk is a IBM-DJNA-351520.
The Mainboard is a older mainboard for Athlon processors with VIA
chipset. (Maybe VIA KT-133).

After I have installed Service Pack 4 the Windows 2000 did not start
successfully anymore. In the half of the graphical boot screen BSOD with
message "0x00000007B (0xED41B84C, 0xC0000032, 0x0..., 0x0...)
INACCESSIBLE_BOOT_DEVICE".

I did not want to install everything again and because of deterministic
software it should have happened again. In the Internet there were no
suitable problem resolutions. The bootlog switch was useless, because at
this stage it seems like that Windows 2000 does not write a boot log.

Maybe the problem could be examined more precisely if the PC is started
with the debug switch and debugged with a second PC by a serial line ...

It seemed for me like a driver problem so I tried to copy the original
drivers from Windows 2000 in the system32/driver directory replacing the
wrong drivers from SP4. After a first try with all new drivers replaced
with the old ones the system started again! So I was confirmed. Now I
wanted the find out which file was wrong.

From the $NTServicepackUninstall I replaced after some dozen reboots
with the quick sort algorithm the correct sys files in the
system32/driver directory:

atapi.sys

I don't know why a atapi driver is necessary for accessing my disk ...

Karsten
 
The ATAPI driver is the IDE driver for windows.as such it's the driver for
your IDE onboard Disk controller. The version of the Atapi driver included
with sp4 apparently has compatability issues with your controller. similar
issues were experienced by certain users after SP3 was released with that
version of atapi.sys
 
Back
Top