Unusual STOP 0x0...7B error

  • Thread starter Thread starter BSartist
  • Start date Start date
B

BSartist

I am getting a STOP 0x7B INACCESSIBLE_BOOT_DEVICE error and after doing
a bunch of research on how to solve it, I have come up empty for my
particular case.

I am not changing motherboards or trying to take an O/S image to
another computer.

What I AM doing is upgrading my harddirve to a larger disk using GHOST
9.0

I had a 160GB SATA drive partitioned into 3 partitions. I am replacing
it with a 360GB SATA drive.

The first two partitions are for dual boot operating systems; the third
for data:

Original drive:

1st: Win2000 - size = 5GB
2nd: WinXP Pro - Size = 20GB
3rd: Data (balance of disk)

New drive:

1st: Win2000 = size = 5GB (same)
2nd: WinXP Pro = size = 40GB
3rd: Data (balance of disk)

I have two on board SATA controllers that I used to hook both up for
copying. I used GHOST 9.0 copy disk function.

The XP partition boots fine.

The Win2K partition boots up to partway through the logo screen and
then I get the BSOD with the STOP 0x7B INACCESSIBLE_BOOT_DEVICE error.
I could swear I had it booting fine before I moved onto copying the XP
partition. But when I went back to boot it, no dice.

I am pretty sure the boot.ini file is OK since it gets as far as it
does.

I tried moving the disk between the two controllers and the same thing
occurs. I tried using disk manager to force the disk letter to C: (what
it originally was for the Win2K boot). Still no dice.

If anyone can point me in a direction to troubleshoot this further it
would be greatly appreciated. Could this be something in the registry
having to do with mounted drives or something? One thing that confused
me about this process was whether I needed to tag the new partition
with the old drive letter.

BTW, the original drive still boots OK from that partition.

Thanx much in advance
Bill Smith
 
BSartist said:
...

I tried moving the disk between the two controllers and the same thing
occurs. I tried using disk manager to force the disk letter to C: (what
it originally was for the Win2K boot). Still no dice.
Click to expand...

Are you saying that the drive letter was changed? Seems to me that
doesn't yield an 0x7b error. Anyhow, from the Windows XP installation
edit the Windows 2000 registry: http://support.microsoft.com/kb/223188/

You can also try the Windows 98 fdisk /mbr command on the non booting
drive.

John
 
Drive letter did not change. I was trying to make sure it stayed the
same. When I ghosted to the new drive I wasn't sure if the drive letter
would come with it. I wanted it to stay as C:.

It is C: but still will not complete the boot.

Bill
 
Try Fdisk /mbr on it.

John
Drive letter did not change. I was trying to make sure it stayed the
same. When I ghosted to the new drive I wasn't sure if the drive letter
would come with it. I wanted it to stay as C:.

It is C: but still will not complete the boot.

Bill
Click to expand...
 
I tried FDISK /MBR and now NEITHER partition will boot.

When I try to boot the XP partition, it comes up to the blue screen
that says "Windows XP" but does not display the words "Starting
Windows" and it just hangs there.
 
That probably means the image was corrupt or the new disc was not
properly prepared before the ghosting process. You will have to
re-image the disk.

http://service1.symantec.com/SUPPORT/ghost.nsf/docid/2000112817032525
http://service1.symantec.com/SUPPORT/powerquest.nsf/docid/2005052419404662?OpenDocument
http://service1.symantec.com/SUPPORT/ghost.nsf/0/12fa47d4dc98df6b88256c3f005576d2?OpenDocument

Also, make sure that the Windows 2000 installation is at SP4 level, that
it has the 48-bit LBA support enabled and that the SATA drivers are
properly installed.

John
 
Back
Top