Hi Frank,
The following is from MSKB article 122926,
http://support.microsoft.com/default.aspx?scid=KB;en-us;q122926
Hope this has a solution for you. I had similar issues when I installed 2K
on my all SCSI machine, but I can't for the life of me remember how I
resolved. I do know that I always choose and use the option to install the
drivers for "additional controllers" while set up is running and then
feeding a CD or floppy as required with the drivers.
Brad Loomis
Morro Bay, CA
Troubleshooting Stop 0x0000007B or "0x4,0,0,0" Error
The information in this article applies to:
Microsoft Windows 2000 Server
Microsoft Windows 2000 Professional
Microsoft Windows NT Workstation 3.5
Microsoft Windows NT Workstation 3.51
Microsoft Windows NT Workstation 4.0
Microsoft Windows NT Server 3.5
Microsoft Windows NT Server 3.51
Microsoft Windows NT Server 4.0
Microsoft BackOffice Small Business Server 4.0
Microsoft BackOffice Small Business Server 4.0a
This article was previously published under Q122926
SYMPTOMS
When you restart your computer, you may receive one of the following error
messages:
STOP: 0x0000007B Inaccessible Boot Device
Setup has encountered a fatal error that prevents it from continuing.
Contact your software representative for help. The following status codes
will assist them "0x4, 0, 0, 0"
CAUSE
This problem may occur if one or more of the following conditions exists:
Your computer is infected with a boot sector virus.
A device driver required by your boot controller is not configured to start
at boot time or is corrupt. If during a WINNT /B installation no mass
storage device was detected.
A resource conflict exists between the boot controller and another
controller in the system or between SCSI devices.
Drive translation is not being performed or was changed.
The boot volume is corrupt and cannot be mounted by Windows NT.
Information in the Windows NT registry about which device drivers load at
start up is corrupt.
If this error occurred during Windows NT Setup while reading Windows NT
Setup floppy disk 2, you may have the Drive Swapping option enabled in your
computer BIOS.
Using winnt /b as the installation method may present a timing issue for the
disk controller. The controller is not given enough time to respond and
identify itself and is therefore detected incorrectly or not at all.
If you run Setup from a bootable SCSI CD-ROM drive, you receive a STOP 7B
error message because Setup does not allow you to add a third-party SCSI
driver when you boot from the SCSI CD-ROM.
RESOLUTION
To resolve this problem, use the appropriate method:
Method 1
Check any diskettes for viruses that may have been used in the computer
since the last time you were able to successfully restart Windows NT.
NOTE: You may need to use more than one brand of virus detection software to
detect and remove various viruses.
If a virus has infected the Windows NT computer and a virus detection
program cannot remove the virus and repair the system, you will have to
reinstall Windows NT. For more information on how to protect the boot sector
from viruses in Windows NT, see the following article in the Microsoft
Knowledge Base:
ARTICLE-ID: 122221
TITLE : How to Protect Boot Sector from Viruses in Windows NT
Method 2
Windows NT requires a mini-port driver to communicate with the boot
controller. If the device driver is corrupt or incompatible with your
controller, you can replace it by copying a new drive to the
%systemroot%\system32\drivers folder or through the Emergency Repair
process. On computers running on a SCSI controller or ATAPI enabled systems,
SCSIPORT.SYS and DISK.SYS (Windows NT 4.0 only) device drivers are also
required to successfully boot.
If you attempt a "WINNT /B" installation, you may receive a STOP 0x7B before
mass storage detection takes place. To work around this, when the computer
reboots after the initial file copy, press F6 as soon as "Setup is
inspecting your computers hardware configuration" is displayed. This will
allow you to add a mass storage device at the very beginning of text mode
setup.
ARTICLE-ID: 125933
TITLE : STOP 0x0000007B: Inaccessible Boot Device After Removing CD-ROM
ARTICLE-ID: 164471
TITLE : Replacing System Files Using a Modified Emergency Repair Disk
Method 3
If an IRQ or I/O port address conflict exists between your boot controller
and another controller in the system, Windows NT will either hang or stop
with the Stop 0x0000007B error message. If you recently added new hardware,
remove the new hardware or re-configure it so it does not conflict with the
resources of any other installed controllers.
Check the SCSI chain for proper termination. Remove any non-essential SCSI
devices or check to ensure each SCSI ID is unique.
ARTICLE-ID: 102651
TITLE : Required Settings for Adaptec 1510 SCSI Host Adapter
Method 4
The Windows NT Boot partition must exist within the first 1024 cylinders of
the boot device. This is due to restrictions of the INT-13 BIOS call used to
start the operating system. Check your CMOS settings for LBA support on IDE
based systems, or your SCSI controllers BIOS settings for enabling drive
translation for drives greater than 2GB.
-----Original Message-----
From: PCBUILD - Personal Computer Hardware discussion List
[mailto:[log in to unmask]]On Behalf Of Frank R. Brown
Sent: Thursday, November 21, 2002 4:59 AM
To: [log in to unmask]
Subject: Re: [PCBUILD] Can't re-install w2k -- STOP 0x0000007B;
Inaccessible boot device
My tale of woe continues...
Thanks to all for the suggestions about how to handle
the scsi drives.
I did the following:
I used the scsi bios to re-format the seagate scsi hard
drive, and cleared the motherboard cmos by jumpering
it. I've stripped the machine down to memory, video card,
scsi card, seagate hard drive, external IBM scsi cd-rom,
floppy, keyboard, and mouse.
This put the machine in as close to it's state when I performed
the original install.
I then attempted the w2k install off of a bootable w2k cd-rom.
I tried the install both skipping and using the option to load
drivers for the adaptec scsi card. These attempts failed.
I then went into the scsi bios, and changed the boot device
to scsi ID 1, the IBM cd-rom. (ID 0 is the seagate drive, and
ID 7 is the adapter.) I also went into the motherboard bios,
and changed the fist boot device to be "scsi".
I then tried installing again, both with and without specifically
loading the adaptec drivers.
In all cases the failure is the same: Windows 2000 Setup
runs and loads a bunch of files. It gives the message
"Setup is loading files (CD-ROM File System)...", and then
switches to the message
"Setup is starting Windows 2000".
After displaying that message for a little while (about half
a minute, the scree flashes, and brings up the
STOP 0x0000007B; Inaccessible boot device message.
In addition to the install attempts I detailed above, I've tried
many other combination --- a dozen or more. I've tried
installing off of the Plextor scsi cd-rom. I've tried installing off
of a non-bootable w2k/sp1 cd-rom, making the install
floppies. I've booted into the running, but flaky original
install, and started the install process off of the cd-rom.
I've played around with a variety of bios setting, and so on.
This is a real conundrum. All of the hardware appears to
be working fine. The install process runs smoothly up until
the Inaccessible boot device error. I've installed a copy of
"Gentus Linux" that was shipped with the motherboard
three times now (off of both the IBM and Plextor cd-roms).
The Linux installs went without a hitch, and I was able to
boot in to Linux. (The Linux install worked whether or not
I played around with the boot-orders settings in the bios.)
(P.S., on Linux, I tried both the "Gnome Workstation" and
"KDE Workstation" install options. Linux boots up to the
command line. Does anyone know how to start the
graphical shell from the command line? Thanks.)
By stripping down the machine, wiping the drive, and clearing
the cmos, I've reset the machine to very nearly it's original
state. The original install went very smoothly --- none of
this problem. I don't recall whether I specifically installed
drivers for the adaptec card, but I just followed the directions,
and everything worked, and I booted into the fresh w2k
install. (The basic install was fine --- the only tweaking
I had to do was some to get the 3d graphics card to run
stably.)
I can't figure out what could be different this time.
Well, I'm fresh out of ideas, and would appreciate any and
all suggestions. This is turning out to be much harder than
I expected!
Thanks in advance.
Ultra <[log in to unmask]> wrote:
> ----- Original Message -----
> From: "Frank R. Brown" <[log in to unmask]>
>
> > > So, given that my cd-roms are scsi, how do I follow your
> > suggestion to boot from cd-rom first? Does "boot from
> > cd-rom" really mean "boot from ide cd-rom"?
>
> Correct, in your case, forget it.
>
> >
> > I like your idea about wiping the hard drive. The *only*
> > thing I can think of that is different from when we first
> > installed w2k is that during the original install, the
> > hard drive wasn't bootable (it was completely new).
> > So maybe having the bootable cd-rom, and the bootable
> > hard-drive both on scsi is confusing the w2k install.
> >
> > I've never wiped a scsi drive from the scsi bios. Could
> > you give me a brief description of what to expect, and
> > what I'll need to do
>
> In SCSI BIOS, you should have option (under utility) to format a SCSI HDD,
> unlike IDE drive, which requires special programs to perform so called
"low
> level format", all SCSI drives can be "low level" formatted in SCSI BIOS.
> this format should get rid of everything on drives, and bring the drive to
> total empty (no partition, no nothing). Just browser in your SCSI BIOS,
you
> have nothing to lose. And, you should be able to set boot device there
too.
>
> Good Luck
>
> Jun Qian
Frank R.Brown
Frank.R.Brown@MailAndNews
The NOSPIN Group is now offering Free PC Tech
support at our newest website:
http://freepctech.com
The NOSPIN Group Promotions is now offering
Mandrake Linux or Red Hat Linux CD sets along
with the OpenOffice CD... at a great price!!!
http://freepctech.com/goodies/promotions.shtml
|
