***STOP: 0x0000007B (On installation of W2K)

[CHRIS_ANORUO]

Hello Friends!

Kindly assist me to resolve this issue of stop error on 1st installation of W2K server on HP Netserver LC2000
with 9Gb hard disk.
The system stopped with this error message after coping the W2K files.
***STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
INACCESSIBLE_BOOT_DEVICE


Regards

[Roger Faucher · Accepted solution]

Hi:

It sounds like maybe you don't have the latest drivers, especially for your hard disk controller. Download them from http://www.hp.com/cposupport/swindexes/hpnetserve19399_swen.html

If you still have the problem, there is a point during the install where you can press F6 and force the install to take the newest driver from floppy or CDROM. Good luck!

[CHRIS_ANORUO]

See link!

http://forums.itrc.hp.com/cm/QuestionAnswer/1,1150,0x9a8de7e60861d511abcd0090277a778c,00.html

[Vernon Dickinson]

Just one other point. If you have any boot managers running (such as Boot magic etc.), you must disable them before installing any NT based OS :)

[JUbilee]

I got the same error on a NetServer LT6000R after performing an unattended installation using two time-limited evaluation copies of Windows XP Pro (Build 2600). Did anyone ever find a solution for this?

[Keld]

This is a Windows 2000 Executive character-mode STOP message. During I/O system initialization, the driver for the boot device might have failed to initialize the device the system is attempting to start from. It is also possible that the file system failed to initialize because it did not recognize the data on the boot device. If this error occurs during initial system setup, the system might have been installed on an unsupported disk or SCSI controller. Also, this error might occur because of the installation of a new SCSI adapter or disk controller or if the disk was repartitioned with the system partition.

User Action:
If this is the first time you have booted after installing new hardware, remove the hardware and boot again. Check the Microsoft Hardware Compatibility List to verify that the hardware and its drivers are compatible with Windows 2000. For information about the hardware, contact the supplier. If you are installing Windows 2000 for the first time, check the Windows 2000 system requirements, including the amount of RAM and disk space required to load the operating system. Also, check the Hardware Compatibility List to verify that the system can run Windows 2000. If Windows 2000 is loaded and no new hardware has been installed, reboot with recovery options set to create a dump file. If the message continues to appear, select the Last Known Good option when you reboot. If there is no Last Known Good configuration, try using the Emergency Repair Disk. If you do not have an Emergency Repair Disk, contact your technical support group.

[ngabordh]

I have a similar problem. After clean install my Win2K, while booting the system stops with a 7B, INACCESSIBLE_BOOT_DEVICE. I did not change my HDD`s parameter, or anything else. I Used Win NT 4 before, and worked smoothly. Any ideas?

[ngabordh]

ngabordh (Programmer) Jun 15, 2003
Here is my solution.
After reading all this forum, microsoft`s knoledge base, and other mailing lists i have found the answer.

I have a shuttle HOT-661 i440bx motherboard, with a 2 Gb HDD. I used Win NT4 without a problem. Then I bought a 40 GB Seagate ATA/100 HDD. I thought its time to change my old NT, and install a Win 2k on the new HDD. I started the installation process, and boom, BSOD, INACCESSIBLE_BOOT_DEVICE. I could not even install Win2k! Windows stucked in safe mode, so it was hopeless.

I tried everything, I read on this forum: atapy.sys, IDE cable, UDMA, boot.ini, format, repartitioning... Nothing helped.

I noticed that my Seagete HDD has an UDMA toggle utility on Seagate`s website, which is able to change the HDD`s speed in its firmware. With this utility i changed the speed to mode 1, 25 M/s. Just a value that i thought is slow enough to avoid problems. After restart, I changed my BIOS PIO settings to Mode 1 also. The next restart was smooth. Win2k did not stuck, I coud finish the installation process, and the BSOD went away. :)