This link may take you forward:
http://snipurl.com/5a3t

The second parameter is very important because it can indicate
whether the 0x7B Stop message was caused by file system issues
or problems with storage hardware and drivers. Values of
0xC000034 or 0xC000000E typically indicate:

Disks or storage controllers that are failing, defective, or improperly
configured.

Storage-related drivers or programs (tape management software,
for example) that are not fully compatible with Windows XP Professional.
--

Hope this helps.

Gerry
~~~~
FCA
Stourport, England

Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~

"Nehmo" <nehmo54@hotmail.com> wrote in message
news:1135903492.453605.3420@f14g2000cwb.googlegrou ps.com...
> My machine is down and I'm using one at a different location to post
> these questions. I have a few questions. I'll be back to see if I
> got any answers in the NG tomorrow. But if anybody wants to call and
> help, _Please Do So_ anytime day or night (I go to bed late anyway)
> 913 766-1899.
> {I think I'll be on this for a few days, so if it's in or before
> the first week of January '06, if you can help, please call!} Thanks.
>
> AN35N Ultra Shuttle mboard
> Award BIOS
> Windows XP Home SP1, NTFS file system
> 3 HD drives and 1 CD/DVD:
> 120 GB as C boot/system
> 80 GB as D
> 160 GB as H
>
> Computer stalled when rebooting, but on forth attempt was successful.
> I ran virus scan but it froze late in the scan.
> Successfully rebooted and tried to run Checkdisk setting it up to work
> on next boot. This was the last time I had normal Windows working.
> Checkdisk was stalled when I looked at, perhaps after an hour.
>
> Every time I try to boot, I now get the blue screen 7b stop code
> 0x0000007B (0xF789E640) (0xc0000034) (0x000000) (0x000000), which I
> understand to mean INACCESSABLE_BOOT_DEVICE (which is not actually
> written with the stop code; I got that string from the MS kb page).
> http://support.microsoft.com/default...b;en-us;324103
>
> Running CHKDSK from a command prompt in the XP recovery counsel
> (booting form CD), I try the option /F , but it says (I think I
> remember correctly) that /F was an invalid parameter. I used /R
> instead, and it ran through it twice on C drive. It reported fixed
> errors.
>
> Q1: Why couldn't I have ran the /F option?
>
> A little on CHKDSK
> http://www.microsoft.com/resources/d...us/chkdsk.mspx
>
> At this point I was still unable to boot Windows normally.
>
> I experimentally physically replaced the 120 GB drive with a 15 GB
> drive I had on a shelf. This drive I know to have a good XP
> installation that works with this machine. I got the same error stop
> code.
>
> I physically put the original 120 GB drive back in.
>
> I tried to reinstall XP via using the CD, but it's only an upgrade CD
> and I don't have my old Windows ME disk. For some reason, install
> program didn't find the old XP installation, and it asked for
> qualifying media, a ME disk or something similar. I couldn't continue
> with the installation.
>
> Looking in the BIOS, Standard CMOS Features,
>
> IDE Primary Master - none
> IDE Primary Slave - none
> IDE Secondary Master - none
> IDE Secondary Slave - 80 GB (and some more characters, don't remember
> exactly, but the drive is listed)
>
> Q2: I have my boot drive on Secondary Master, so maybe this is where
> the problem is. It doesn't show in the BIOS. All the detections are on
> Auto. Should I change something?
>
> Nonetheless, I am able to navigate in the drives via the command prompt
> in the recovery counsel.
>
> Q3: Why does the BIOS seem to not detect the drives, but yet I can work
> with them via the command prompt?
>
> Q3: When trying to boot via the CD, it gives an option for Windows XP,
> and for Windows XP Home. Why does it give two options? I only have
> Home. I've been trying both (one, then the next time, the other) with
> no luck, but which one should I choose?
>
> --
> (||) Nehmo (||)
>