安装系统出现 STOP : 0X7B

以下是从一个BBS上回帖的对0X7B的说明，看的我头都大了,在电脑上看英文老感觉头脑空白。
Bug Check 0x7B: INACCESSIBLE_BOOT_DEVICE

The INACCESSIBLE_BOOT_DEVICE bug check has value 0x0000007B. This indicates
that Windows has lost access to the system partition during startup. This er
ror always occurs while the system is starting and cannot be debugged becaus
e it generally occurs before the operating system has loaded the debugger.

说明分区坏了，试试看把系统装在好的分区
Cause

This error often results from a boot device failure. During I/O system initi
alization, the boot device driver might have failed to initialize the boot d
evice (typically a hard disk). File system initialization might have failed
because it did not recognize the data on the boot device. Also, repartitioni
ng the system partition or installing a new SCSI adapter or disk controller
might induce this error.

This error can also result from incompatible disk hardware. If the error occ
urred at the initial setup of the system, the system might have been install
ed on an unsupported disk or SCSI controller. Some controllers are supported
only by drivers that are in the Windows Driver Library (WDL), which require
s the user to do a custom installation.

Resolving the Problem

Resolving a failed boot device problem: If this happens on x86 systems, the
boot.ini file must be edited; on Alpha systems, system Setup must be run.

Resolving an incompatible disk hardware problem: If Setup autodetected the c
ontroller, you might need to skip detection and use a specific manufacturer'
s diskette to load the driver. Also, check the availability of updates for t
he system BIOS and SCSI controller firmware. Updates of this kind are typica
lly available on the web site or BBS of the hardware manufacturer.

Remove any recently added hardware, especially hard disks or controllers, to
see if the error is resolved. If the offending piece of hardware was a hard
disk, the disk firmware version might be incompatible with your version of
Windows. Contact the manufacturer for updates. If the removal of another pie
ce of hardware resolved the error, IRQ or I/O port conflicts likely exist. R
econfigure the new device according to the manufacturer's instructions.

Confirm that all hard disks, hard disk controllers, and SCSI adapters are li
sted on the Microsoft Windows Hardware Compatibility List (HCL).

If a driver was recently added, restart your computer, and press F8 at the c
haracter-based menu that displays the operating system choices. At the resul
ting Windows Advanced Options menu, choose the Last Known Good Configuration
option. This option is most effective when only one driver or service is ad
ded at a time.

In addition, check your computer for viruses using any up-to-date, commercia
l virus scanning software that examines the Master Boot Record of the hard d
isk. All Windows file systems can be infected by viruses.

This error can also be a result of hard disk corruption. Run Chkdsk /f /r on
the system partition. You must restart the system before the disk scan begi
ns. If you cannot start the system due to the error, use the Recovery Consol
e and run Chkdsk /r.

Warning  If your system partition is formatted with the FAT file system, the
long filenames used by all NT-based operating systems can be damaged if Sca
ndisk or another MS-DOS?–based hard disk tool is used to verify the integri
ty of your hard disk from an MS-DOS prompt. (An MS-DOS prompt is typically d
erived from an MS-DOS startup disk or from starting MS-DOS on a multiboot sy
stem.) Always use the version of Chkdsk that matches your Windows version.

If your system has SCSI adapters, contact the adapter manufacturer to obtain
updated Windows drivers. Try disabling sync negotiation in the SCSI BIOS, c
hecking the cabling and the SCSI IDs of each device, and confirming proper t
ermination. For IDE devices, define the onboard IDE port as Primary only. Al
so check each IDE device for the proper master/slave/stand alone setting. Tr
y removing all IDE devices except for hard disks. Finally, check the System
Log in Event Viewer for additional error messages that might help pinpoint t
he device or driver that is causing the error.

To analyze this error: Execute an LM command on the debugger. Verify that th
e following drivers were loaded: disk, classpnp, ftdisk, partmgr, and either
FAT or NTFS.

You'll probably need pci or isapnp loaded. Also make sure your controller dr
ivers were loaded — atapi.sys with the channel drivers (pciide and pciidex
or intelid) or scsiport.sys with the appropriate miniport driver.

It's always helpful to know as much as possible about the boot device Window
s was installed on. Useful ways to investigate include:

Find out what type of controller the boot device is connected to (SCSI, IDE,
1394, etc). Try to find out the manufacturer of non-IDE controllers (Adapte
c, Symbios, and so on).

Note the SCSI ID of the boot device if you're using SCSI.

Indicate if other devices are attached to the same controller the boot devic
e is on (CD-ROMs, zip drives, and so on).

Note the file system used on the drive.

If you know how to read through !devnode debugger extension output, and you
know what your boot devices are, you can get further. Usually Plug and Play
couldn't assign resources to the boot device. You can verify this by finding
an entry for the service. If the status flags include DNF_INSUFFICIENT_RESO
URCES and/or don't include DNF_STARTED or DNF_ENUMERATED, then you've confir
med the problem. Try !devnode 0 1 scsi or !devnode 0 1 atapi to save some ti
me instead of dumping the whole device tree.

 

 

上面这么多英文，看着头昏，头大。网上查一下，发现是没找到硬盘的原因，于是到CMOS里面，把BIOS设置恢复为出场设置，一切OK，顺利装完系统。