"stop 0x0000007b ... inaccessible_boot_device"

This article reffers to win NT and not win 2K and anyway the symptoms don't match.

then you need to post more here then

please post the whole string
EXAMPLE = STOP 0x0000007B (0x85e7b3f0, 0xC0000102, 0x00000000, 0x00000000)
Inaccessible_boot_device

Is your hard disk controller supported? See www.microsoft.com/hcl for details of supported hardware.

Please provide more hardware details

This second parameter 0xC0000102 keeps me curious, never heard about the Stop like this.

I'm also curious about the following:
1. What did you do with the new disk?
2. Did you connect the disk to IDE? Which one?
3. Could W98 boot and work AFTER it?
4. Could W98 detect the new hardware?
5. Did you set partitions?  When, before or during OS installation? NTFS or FAT?
6. Did you format partitions?
7. If yes, where did you install W2K on the new disk or the old one?

8. How did you start the setup, by the way?
9. Did you do W98 upgrade or just clear installation of W2K?
10. Is the W98 still available for booting?

Mike

MLSmnv: If you look, the C0000102 parameter was just an example posted by jumble, not the real error the user had.

This is my story:

At first, like I wrote, I got the error message "stop 0x0000007b ... inaccessible_boot_device", after the first reboot during W2K setup.

I tried looking for a driver for the disk controller but couldn't find one. I think that is required only for SCSI or RAID.

I seperated the IDE cables so that the HD was connacted as primary master and the CD was connected as secondary slave. I was able to continue the setup and finish it. I also installed SP3.

Then after installing NAV 7.6 and rebooting I get the following error:

stop: 0x0000001a (0x00041284, 0x03161000, 0x00001b89, 0xc0502000)
Begining dump of phusical memory. physical memory dump complete. contact your system administrator or technical support group.

After a restart I get the computer to work again but now it kept on giving me the following error message: "Explorer.exe Has Generated Errors and Will Be Closed By Windows" I checked the Task Manager and found a milion prossesses of "drwtsn32.exe" which I don't know what they mean. I didn't install any additional programs or put anything in the startup. When I saw that I can't get rid of it, not even in safe mode, I tried repair instalations (quick and long) but no use. Then I reinstalled the HD, but this time I removed an extra jumper that was on the HD.

It seems that now everything is fine. I installed the OS with updates, NAV and programs and it seems OK. I guess it was all because of the jumper.

drwtsn32.exe is part of a program called Dr.Watson. Dr. Watson is a program error debugger. It detects information about a system and program failures and records the information in a log file. This can then be used by technical support teams to diagnose a program error.

STOP 0x0000001A MEMORY_MANAGEMENT Error Message

SYMPTOMS------
If you are running Windows 2000, you may receive the following error message:

STOP 0x0000001A (parameter, parameter, parameter, parameter)
MEMORY_MANAGEMENT
For example:

Stop 1A (0x00000001, 0x00000043, 0x00024893, 0xffffffff)
The first parameter is 1, therefore the subtype is "The fork clone block reference count is corrupt. Only occurs on checked builds."

Everything else, must be examined individually.

CAUSE--------
This issue can indicate the existence of a general memory-management problem. The error message that is mentioned in the "Symptoms" section of this article is a Windows 2000 Executive character-mode STOP error message.

RESOLUTION--------
To resolve this issue, use the appropriate method:
If this is the first time you have started the computer after you install new hardware, remove the hardware and restart your computer.
View the following Microsoft Hardware Compatibility List Web site to verify that the hardware and its drivers are compatible with Windows 2000:
http://www.microsoft.com/hcl/default.asp

For more information about your hardware, contact the manufacturer of your hardware.
If you are installing Windows 2000 for the first time, verify that your computer meets the Windows 2000 system requirements, including the amount of RAM and disk space that are required to install the operating system.
If Windows 2000 is loaded and no new hardware has been installed, restart your computer with the recovery options set to create a dump file. If the error message that is mentioned in the "Symptoms" section of this article continues to appear, select the Last Known Good option when you restart your computer. If there is no Last Known Good configuration, try to use the Emergency Repair Disk (ERD).

I am getting the same issue, but I found a solution.  

The following article talks about PnP devices that allow booting.  I never even thought to check the NIC.

http://www.winnetmag.com/Article/ArticleID/8108/8108.html

Help!
 I am in the same boat, only I know the culprit.  I just need the solution.  I hope this is not considered hijacking a thread, if it is, please advise and I will start a new one and award points.  If you would be so kind as to reply here, I will do so AFTER the fact.

1) This is my work PC.  I did this without management's knowledge (yes, PEBCAK), and need to repair without thier knowledge. I have already slapped my own wrist...  :(  

2) The system is a Dell GX240.  
3) I installed the (Device: Intel Integrated Ultra ATA Controller V.6.10.011, A10) found here: http://support.dell.com/FileLib/Format.aspx?c=us&l=en&s=DHS&Category=0&OS=WNT5&OSL=EN&SvcTag=&SysID=PLX_PNT_P4_GX240&DeviceID=243&Type=&ReleaseID=R27520 (contains IntelATA.mpd, Intelvsd.vxd, intelata.sys) and the application accellerator (Contains idechndr.sys, idebusdr.sys, and iprtcnst.dll)

3) It's Win2k Pro SP4 on an NTFS partition.  I have NTFS pro and have mounted the partition.  I can view & modify files.  I have registry backups in winnt\repair\regback.

I have already done an F8 boot and restored last known good (no effect), run win2k setup (repair option) no effect.  I do NOT have an ERD.

Please help, (and ASAP if at all possible)  Many thanks in advance...

A wasted morning, and I am out of time.  Hope this will fix it:
although win2k repair "quickfix" did not work, I started the win2k install, and THEN chose repair.  Unless I am mistaken, this replaces all drivers and references with dedaults.  I'll need to reinstall SP4 but this OUGHT to resolve it.  If it does not, I will post again.

I had the same issue two days back.  Based on the technical advice given by colleagues, I made IDE CD-ROM as the first item in the boot order, inserted the Win2K CD and rebooted the PC.  Once I got the prompt once the setup copied the installation files, it asked me whether I wanted to reinstall Windows in the same WINNT directory and answered Yes.  It was that simple in my case and everything worked out fine.  Your issue involves adding new HD and memory.  I believe from my experience in this case the HD is the cause of problem.  Win2K (unless you are using advanced server CD - which will not have any sort of drivers) usually will include all sorts of drivers.  I hope this helps.

- Joe

I have a similar problem, but the machine has been running quite happily for a year. Originally I installed Win98, then I upgraded to Win2k from a (legal) MSDN subscription disk. All OK, then a couple of days ago it started BSODing at bootup (after the Win2k splash screen comes up). From looking here and elsewhere, I am guessing that the HDD driver has become corrupted (or else the kids deleted it!). I propose to do the following:-

1. Obtain driver from Internet.
2. Boot from floppy.
3. Run Recovery Console.
4. Install driver.
5. Try again.

Will let you know how I get on!

I got the same problem my stop error 0x0000007B (0x827A9AF0,0xC0000102,0x0000000,0x0000000)
INACCESSIBLE_BOOT_DEVICE

I have the same error.  It get it in Win98, Win 2K and Win XP.  Funny thing is I can boot in WIn 98 Safe Mode.  System was working fine until this morning.  

The problem I had was similar to yours. Here's how I got it:

I have a PC with an AMD-K6-III CPU and ALI chipset. I tried over 2 weeks to get win2k working on this system, but no success. I always get disk I/O errors, sometimes while loading setup from CD-ROM, sometimes while win2k is being installed. But the worst was when win2k got installed and wanted to save the settings. Then I got a blue screen again (STOP: IRQL_NOT_LESS_OR_EQUAL) and after I restarted my PC, setup restarted too. So it looks like a cycle: win2k restarts unexpected after a while, or gets a blue screen which leads to the same result - restarting the PC.

After a while I gave up and I got another idea - to install win2k on my other PC (CPU Intel and VIA chipset) and afterwards to put it back on AMD, which I did, but...

...then I got this STOP: INACESSIBLE_BOOT_DEVICE. I noticed that, when I try to load win2k even in safe mode, it always loads the drivers for the VIA chipset, because this is where I installed windows first. So the only remaining solution would be to re-install win2k on the AMD, which is impossible, as already described.

I think that there must be loaded the appropriate CHIPSET (and not HARDDISK) driver at the time when windows starts from CD-ROM (by pressing F5, or F6). Some chipsets are either too old for win2k or not supported. So my advice is to check the support web site for the chipset your mainboard has.

I'm working on a Win2k pc and had to replace a bad motherboard.  PC was working fine until I put in the rpl mbd.  Now am getting STOP: 0x0000007B Inaccessibel_Boot_Device BSOD.  Found that by booting to Win2k CD, choosing repair option and Recovery Console, choosing to log into the 1: C:\Winnt and entering the administrator password when prompted.  Next I simply typed Exit and the pc rebooted and finally went right to the network login screen and let me log right in.  Not sure how or why this worked, but am sure glad I didn't have to resetup the pc.