***STOP: 0x0000007B(0xF89506400,0xC0000034,0x00000000,0x00000000)

[Leonard Harvey]

Summary: Can't use Western Digital 80GB slave after using
recovery CD on Western Digital Master 120GB HD

Bought PC with ECS mainboard w/ onboard Promise IDE RAID
Controller PDC20265R and 120GB Western Digital HDD. Added
WD 80GB as Slave on Primary channel.
DVD player and DVD/CD burner were on Secondary Channel.
Things worked fine for several months and both drives were
healthy a few minutes before running the Recovery CD.
When I decided to run the recovery CD to restore the
original image on the master drive, Windows XP Home will
not load without disconnecting the 80GB drive. I get a
stop error message saying that windows has been shut down
to prevent damage to my computer. I am supposed to check
for viruses, remove any newly installed HDDs or HDD
controllers etc....

BIOS recognizes both drives, but windows won't load with
both drives connected.

The message at the bottom is:
***STOP: 0x0000007B
(0xF89506400,0xC0000034,0x00000000,0x00000000)

DataLifeguard UTILs Quick & Extended Tests on the 80GB
both return "NO ERRORS FOUND".
Moving 80GB from slave on Primary to Master on Secondary
Channel doesn't help.

Do you have any suggestions?
Leonard

 

[Joshua Smith [MSFT]]

Here is what your Stop Code says. I would guess that the original
configuration with the RAID card was something different than how things are
configured now. Did the RAID card try to combine these drives in your new
configuration? Can you remove the 80GB HD, do the recovery, and add it back
after?

INACCESSIBLE_BOOT_DEVICE (0x7B)
PARAMETERS
1 - Pointer to the device object or Unicode string of ARC name
DESCRIPTION
During the initialization of the I/O system, it is possible that the driver
for the boot device failed to initialize the device that the system is
attempting to boot from, or it is possible for the file system that is
supposed to read that device to either fail its initialization or to simply
not recognize the data on the boot device as a file system structure that
it recognizes. In the former case, the argument (#1) is the address of a
Unicode string data structure that is the ARC name of the device from which
the boot was being attempted. In the latter case, the argument (#1) is the
address of the device object that could not be mounted.
If this is the initial setup of the system, then this error can occur if
the system was installed on an unsupported disk or SCSI controller. Note
that some controllers are supported only by drivers which are in the Windows
Driver Library (WDL) which requires the user to do a custom install. See
the Windows Driver Library for more information.
This error can also be caused by the installation of a new SCSI adapter or
disk controller or repartitioning the disk with the system partition. If
this is the case, on x86 systems the boot.ini file must be edited or on ARC
systems setup must be run. See the "Advanced Server System Administrator's
User Guide" for information on changing boot.ini.
If the argument is a pointer to an ARC name string, then the format of the
first two (and in this case only) longwords will be:
USHORT Length;
USHORT MaximumLength;
PWSTR Buffer;
That is, the first longword will contain something like 00800020 where 20
is the actual length of the Unicode string, and the next longword will
contain the address of buffer. This address will be in system space, so
the high order bit will be set.
If the argument is a pointer to a device object, then the format of the
first
word will be:
USHORT Type;
That is, the first word will contain a 0003, where the Type code will ALWAYS
be 0003.
Note that this makes it immediately obvious whether the argument is a
pointer
to an ARC name string or a device object, since a Unicode string can never
have an odd number of bytes, and a device object will always have a Type
code of 3.



Joshua Smith
DirectInput Test Lab
Microsoft

 

[Leonard Harvey]

Thanks Joshua, I'll try that.
The raid controller was just an onboard chip and not a
controller card.

I ran the the recovery CD with the 80GB slave still
connected. Should I have disconnected it before running
the Recovery CD? Am I likely to have lost data because of
that? When Windows wouldn't load with the slave attached,
I immediately disconnected the slave and rebooted. When I
got windows loaded, I installed SP1 from CD.

I'll try to run the recovery without the slave connected
and see what happens. I'll let you know.

Leonard

 

[Guest]

I have just installed a new m'board (ASUS P4R800-VM) and have encountered the same error code... XP tries to boot up in one of the safe modes but can't, then this error message appears. How do I change this as I can't access the HDD

Cheers
Skiffie, Australia

----- Joshua Smith [MSFT] wrote: ----

Here is what your Stop Code says. I would guess that the original
configuration with the RAID card was something different than how things are
configured now. Did the RAID card try to combine these drives in your new
configuration? Can you remove the 80GB HD, do the recovery, and add it back
after

INACCESSIBLE_BOOT_DEVICE (0x7B
PARAMETER
1 - Pointer to the device object or Unicode string of ARC nam
DESCRIPTIO
During the initialization of the I/O system, it is possible that the drive
for the boot device failed to initialize the device that the system i
attempting to boot from, or it is possible for the file system that i
supposed to read that device to either fail its initialization or to simpl
not recognize the data on the boot device as a file system structure tha
it recognizes. In the former case, the argument (#1) is the address of
Unicode string data structure that is the ARC name of the device from whic
the boot was being attempted. In the latter case, the argument (#1) is th
address of the device object that could not be mounted
If this is the initial setup of the system, then this error can occur i
the system was installed on an unsupported disk or SCSI controller. Not
that some controllers are supported only by drivers which are in the Window
Driver Library (WDL) which requires the user to do a custom install. Se
the Windows Driver Library for more information
This error can also be caused by the installation of a new SCSI adapter o
disk controller or repartitioning the disk with the system partition. I
this is the case, on x86 systems the boot.ini file must be edited or on AR
systems setup must be run. See the "Advanced Server System Administrator'
User Guide" for information on changing boot.ini
If the argument is a pointer to an ARC name string, then the format of th
first two (and in this case only) longwords will be
USHORT Length
USHORT MaximumLength
PWSTR Buffer
That is, the first longword will contain something like 00800020 where 2
is the actual length of the Unicode string, and the next longword wil
contain the address of buffer. This address will be in system space, s
the high order bit will be set
If the argument is a pointer to a device object, then the format of the
firs
word will be
USHORT Type
That is, the first word will contain a 0003, where the Type code will ALWAY
be 0003
Note that this makes it immediately obvious whether the argument is a
pointe
to an ARC name string or a device object, since a Unicode string can neve
have an odd number of bytes, and a device object will always have a Typ
code of 3



Joshua Smit
DirectInput Test La
Microsof