RE: Stop 0x7B after upgrading BIOS on Intel SE7520BD2 server...

This Stop message, also known as Stop 0x7B, indicates that Windows 2000 lost
access to the system partition during the startup process.

This error can be caused by a number of factors, including the failure of
the boot device driver to initialize, the installation of an incompatible
disk or disk controller, an incompatible device driver, disk cabling
problems, disk corruption, viruses, or incompatible logical block addressing
(LBA).

The system BIOS allows access to fixed disks that use fewer than 1024
cylinders. Many later disks, however, exceed 1024 cylinders. LBA is used to
provide support for these disks. Such support is often built into the system
BIOS. However, there are potential problems with LBA, such as:

• If partitions are created and formatted with LBA disabled, and LBA is
subsequently enabled, a STOP 0x7B can result. The partitions must be created
and formatted while LBA is enabled.

• Some LBA schemes are not compatible with Windows 2000. Check with your
vendor.


Warning

Changing LBA modes from one scheme to another can force you to recreate and
reformat the partitions.

For more information about Stop message 0x7B, see "Windows 2000 Stop
Messages" in this book.

You should start with the following KB article:

http://support.microsoft.com/kb/122926

I Hope this will help.

Regards,

Ashish





"Ken Morley" wrote:

Stop 0x7B after upgrading BIOS on Intel SE7520BD2 server...

My customer has an Intel SE7520BD2 server running Windows Server 2003 SP1.
The system was installed about 18 months ago and has been running fine ever
since.

The server is cconfigured with two SATA drives running off the system board
in a RAID 1 configuration (the MB has a hardware RAID option for on-board
SATA ports) for the boot drive (C:) It also has an Intel SRCS16 RAID
controller with 6 SATA drives in RAID 5 configuration for the data volume
(E:).

I recently upgraded the server BIOS from 8.2 to 9.0. Afterwards, I
defaulted CMOS and went through setup as usual. Then I tried to restart the
server.

The boot progresses normally with the black and white bars moving across the
screen. I see the Windows logo screen and then about 7-8 seconds later, I get
a STOP 0x0000007B (0xF60C2A94, 0xC0000034, 0x00000000, 0x00000000). During
the boot, there was normal disk drive activity.

If I select Safe Mode, I see many files, drivers, etc. being loaded but I
still get the STOP 0x7B. I can boot from CD into the Recovery Console
(supplying the disk driver on floppy using F6) and poke around the boot drive
without problem. Chkdsk finds no errors. I've also removed the RAID 5
controller and have the same symptoms.

I've spent hours on this by myself, and hours more with Intel technical
support with no success. Intel offers to ship me a replacement system board,
but I really don't think it's a hardware issue. If I flash the BIOS back to
8.2, the system boots up and runs just fine.

It would help if I understood why the OS can access the drive during the
initial boot but the drive becomes inaccessible seconds later. Any ideas on
how to troubleshoot this further?

Thanks!

.

Relevant Pages

  • Re: Boot Problem
    ... Was either disk set up as a Microsoft dynamic disk? ... Do not change the boot sector signature. ... I ensure all OK by swapping over drives. ... installing XP as it insisted there was no drive to install itself on! ...
    (microsoft.public.windowsxp.hardware)
  • Re: 2 drives needed to boot - how to fix
    ... my cloned drive and my system won't boot. ... seems my system wants both hard drives to be able to boot. ... Which is your primary master disk - the old or the new disk? ... Could you, in effect, start over by making a fresh install of the XP OS ...
    (microsoft.public.windowsxp.general)
  • Re: NTLDR is missing
    ... Make sure that there are no disks in any removable drives when you boot. ... NTLDR is missing, why does it happen? ... Computer hard disk drive is not properly setup in BIOS. ...
    (microsoft.public.windowsxp.basics)
  • Re: [SLE] Problems with initrd after mkinitrd
    ... A disk can have three real heads and report a dozen or a hundred! ... > natural metric for partitioning drives that use LBA. ... > - One, less frequent, is the failure of some of the cloned drives to boot ...
    (SuSE)
  • Re: Grub hangs - two hard drives and a CD
    ... > What you wrote is all based on a wrong assumption that grub numbers drives ... > that the BIOS will call to boot an OS. ... The Bios calls to read disk require the register DL to ...
    (comp.os.linux.setup)