blue screen error: inaccessible boot device?
Motorhead
Hi,
I have a problem booting Windows NT 4.0 on a AMD K6-2 450 with a
Microstar 5169 Motherboard and an IBM DJNA 371350 hard drive (I used an
UltraATA66 (80 conductors) IDE cable (even though the IDE
controller works on UltraDMA33 mode)). Also I have 128 MB PC100 memory.
The version of NT being installed has Service Pack 1 included with it.
I installed it just fine, but when I reboot, i get the following blue
screen error message:
*** STOP: 0x0000007B (...three more hexadecimal numbers...)
INACCESSIBLE_BOOT_DEVICE
...Then comes the CPU ID, and a few other things. They appear OK. Next
is a list of DLL files (7 of them).
...It then lists a lot of hex numbers in columns, like this:
address dword dump Build [1381] -name
(hex numbers) ntoskrnl.exe
(repeat for about 20 lines, w/ different numbers))
My question is: Is this a software problem (e.g. faulty installation) or
is there a hardware problem (e.g. bad HD)? I've installed the OS about
five times, and the outcome is always the same -- when the system boots
AFTER the installation is over, this error message appears on the blue
screen.
If anyone can offer insights and/or advice, it would be greatly
appreciated. Thanks!
Viorel Negoita
vio...@phyast.pitt.edu
DaveC
ID: Q126423
----------------------------------------------------------------------------
----
The information in this article applies to:
Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
Microsoft Windows NT Server versions 3.5, 3.51, 4.0
----------------------------------------------------------------------------
----
SYMPTOMS
Many computers are equipped with both the 5.25-inch and 3.5-inch floppy
drives in one single unit. When you install Windows NT on a computer with
this floppy drive unit, the following error message may appear during
Windows NT Setup Disk 2.
STOP: 0x0000007B
Inaccessible_Boot_Device
CAUSE
This problem occurs if the original path of the floppy drives has changed
through the BIOS configuration of the computer. Some computers that include
the two floppy drives in a single unit have a BIOS option to swap the floppy
drives logically without changing the hardware jumpers. This allows any one
of the floppy drives to become the "boot" floppy drive. When you install
Windows NT, this BIOS setting is ignored and the Windows NT kernel addresses
the floppy drives as configured with the jumpers.
RESOLUTION
To correct this problem, do the following:
Do not use the DRIVE SWAPPING option in the computer system BIOS to change
the logical configuration of the floppy drive letters. If you have changed
the configuration, change it back to the original settings.
Make sure the jumpers on the floppy drive unit matches the drive types
defined in the computer system BIOS.
MORE INFORMATION
This error may also occur on systems with a LS/120 floppy disk drive
installed.
For additional information, see the following article in the Microsoft
Knowledge Base:
Q172773: Problems Using LS/120 Floppy Disk Drive with Windows NT Setup
Additional query words: cmos stop 0x7B
Keywords : kbhw kbsetup ntstop ntsetup nthw
Version :
Platform :
Issue type :
Last Reviewed: February 24, 1999
----------------------------------------------
Service Pack 1? I'll attach this anyway:
----------------------------------------------
STOP 0x0000007B INACCESSIBLE_BOOT_DEVICE After Applying Windows NT 4.0
Service Pack 4
ID: Q214810
----------------------------------------------------------------------------
----
The information in this article applies to:
Microsoft Windows NT Server version 4.0
Microsoft Windows NT Workstation version 4.0
----------------------------------------------------------------------------
----
SYMPTOMS
In some instances, after the application of Service Pack 4, when the
computer is restarted, it will do either of the following:
The system will fail to boot and will display the following error:
Stop 0x0000007B INACCESSIBLE_BOOT_DEVICE
The system will boot, but some devices will not be recognized on the SCSI
bus.
CAUSE
This problem occurs because the Aic78xx.sys driver chosen during the
application of Service Pack 4 is not compatible with the computer's Adaptec
SCSI controller.
RESOLUTION
This problem can be corrected by replacing the existing Aic78xx.sys driver,
located in the %systemroot%\Winnt\System32\Drivers folder, with the
Aic78xx.sys driver from the i386 directory within Service Pack 4.
Windows NT 4.0 Service Pack 4 contains the following Aic78xx drivers:
Aic78xx.sys 26,704 bytes
Aic78xx.001 56,272 bytes
To determine which Aic78xx.sys driver is in use, and to copy the correct
driver, depends upon the file system on the Windows NT boot partition (where
%SystemRoot%\Winnt resides).
If Windows NT resides on a FAT formatted partition, perform the following
steps:
Boot to MS-DOS by using an MS-DOS 6.x boot floppy disk.
Change to the %systemroot%\Winnt\System32\Drivers folder.
Compare the size of AIC78xx.sys with the table above.
Replace the existing AIC78xx.sys file in %systemroot%\Winnt\System32\Drivers
with the other AIC78xx file in the i386 directory within Serivce Pack 4.
If AIC78xx.001 is copied, be sure to rename it AIC78xx.sys.
If Windows NT resides on an NTFS formatted partition, perform the following
steps:
Either boot to a parallel installation of Windows NT or create a parallel
installation of Windows NT. To create a parallel copy of Windows NT, perform
a fresh installation of Windows NT to a different folder.
From the parallel installation, look in the
%systemroot%\Winnt\System32\Drivers of the failing copy of Windows NT.
Compare the size of AIC78xx.sys with the table above.
Replace the existing AIC78xx.sys file in %systemroot%\Winnt\System32\Drivers
with the other AIC78xx file in the i386 directory within Serivce Pack 4.
If AIC78xx.001 is copied, be sure to rename it AIC78xx.sys.
MORE INFORMATION
There are two different versions of the AIC78XX driver for the Adaptec 2940
and 7800 family of SCSI controllers included in Service Pack 4. The
Aic78xx.sys file in Service Pack 4 is the same file that is in Service Pack
3. The Aic78xx.001 file of Service Pack 4 is only placed on the computer if
%systemroot%\Winnt\System32\Drivers\AIC78xx.sys has a revision between
x.x.1382.x and x.x.1420.x.
Additional query words: Stop 0x0000007B AHA-2940 nt 4.00 sp4
Keywords : ntstop
Version : winnt:4.0
Platform : winnt
Issue type : kbprb
Last Reviewed: February 16, 1999
--------
Dave
Motorhead <vio...@alpha.phyast.pitt.edu> wrote in message
news:Pine.LNX.4.10.991116...@alpha.phyast.pitt.edu...
Jörg Klein
thread Blue screen of death during installtion in this newsgroup. There
you will find the answer.
Jörg
Ken Taylor
>
> STOP: 0x0000007B "Inaccessible_Boot_Device" -
I get this same message under much different conditions.
I have an older disk with dual boot to Win95/NT 4.0/SP4 that runs just
fine.
I have created an NT 4.0/SP4 disk that I want to be my main disk. To
that end I have installed both disks in my system with the older disk on
the secondary controller so I can copy data across.
When I boot the new system with the older disk installed, I get the 7B
error. Without it the new disk runs fine.
I tried making the old disk a slave -- no change. If the old dual boot
disk is present I cannot boot the new disk.
I do not have a SCSI controller in my machine. The AIC78xx.sys file is
not present in my /DRIVERS directory. I am not doing floppy swapping.
Keith Eckhardt
for Ken Taylor
Marcus Zort
Pavan
You get this error mesg when the HDD driver loaded during NT installation
is corrupted or not the right one. Contact vendor and ask fo NT driver for
ur controller & Hdd. We faced similar problems here in IBM.
Hope this helps u
--
Posted via CNET Help.com
http://www.help.com/
Frank Wiegerinck
problem you have to install a bigfix delivered with SP4. (Not automaticly
installed)
Frank Wiegerinck
Frank.Wi...@cs.utwente.nl
"Pavan" <pavan.de...@corpmail.telstra.com.au> wrote in message
news:s4oho1...@corp.supernews.com...
Eric
boot-partition under 8 Gb.
During installation you can add a custom Mass Storage Device-driver.
ideatapi.sys is the name of the IDE version.
Regards,
Eric de Groot
Frank Wiegerinck <Frank.Wi...@cs.utwente.nl> wrote in message
news:82in9s$lv$1...@dinkel.civ.utwente.nl...
: The problem is that NT does not support disks bigger then 8Gb. To solve
:
:
Hermie Sadler
this may help you out.
Luck.
--