I don't have any hardware changes, and everything was fine with my
computer until 2 days ago, when I tried to boot my PC running Windows
2000 Professional, I get this stop error in blue screen:

0x0000007B (0x818227D0,0xC0000006,0x00000000,0x00000000)
Inaccessible Boot Device.

I guess this is boot sector virus infected.

In BIOS, I am able to see the hard disk. I tried to boot from Windows
2000 CD and reach setup screen, and when I chose option "set up windows
2000 now", or "repair", I get the
error: "Setup did not find any hard disk drives installed in your
computer."

I cannot even have chance to repair using the recovery console.

any ideas?

please help and advise.
thanks!!

jrefactors@hotmail.com wrote:

>0x0000007B (0x818227D0,0xC0000006,0x00000000,0x00000000)
>Inaccessible Boot Device.
>
>I guess this is boot sector virus infected.

From your description it rather sounds like a hardware malfunction.
Check the IDE cable (or SCSI, if you have that), try another one. If the
setup CD doesn't see it at all, it could be a defective drive. Had a
similar problem with a faulty SCSI disk recently, luckily not the
primary one. Controller could always see it but with Windows started it
popped in and out of existence, filling the event log with controller
and disk errors and sometimes randomly crashing the machine.




JK'05

Thanks Jan!!

When you say hardware malfunction, it basically means defective hard
drive?
If the hard drive has defects, how can I fix that? This is a laptop
machine. The cable can have problem too? If so, how can I fix?

please advise. thanks!!


Jan Kannemacher wrote:
> jrefactors@hotmail.com wrote:
>
> >0x0000007B (0x818227D0,0xC0000006,0x00000000,0x00000000)
> >Inaccessible Boot Device.
> >
> >I guess this is boot sector virus infected.
>
> From your description it rather sounds like a hardware malfunction.
> Check the IDE cable (or SCSI, if you have that), try another one. If
the
> setup CD doesn't see it at all, it could be a defective drive. Had a
> similar problem with a faulty SCSI disk recently, luckily not the
> primary one. Controller could always see it but with Windows started
it
> popped in and out of existence, filling the event log with controller
> and disk errors and sometimes randomly crashing the machine.
> 
> 
> 
> 
> JK'05

My Windows 2000 machine has "stop error: 0x0000007B Inaccessible Boot
Device." when starting up the machine. It never happen before.

I boot the system with Windoes 98 boot disk, I don't know why when I
use Windows 2000 boot disk, it says non system disk. Anyway, after
booting the system with Windows 98 boot up disk, I could type a:, b:,
but couldn't see c:, I couldn't see the contents of the hard disk,
there is something called RAM drive, but I have no idea what is that.

any ideas? thanks!!

> I boot the system with Windoes 98 boot disk, I don't know why when I
> use Windows 2000 boot disk, it says non system disk. Anyway, after
> booting the system with Windows 98 boot up disk, I could type a:, b:,
> but couldn't see c:, I couldn't see the contents of the hard disk,
> there is something called RAM drive, but I have no idea what is that.
> any ideas? thanks!!

Win2k uses NTFS, and Win98 uses FAT32 - it cannot read an NTFS drive 
without additional software, which can typically read but not write to 
the drive.

As for why you`re getting non-system disk, are the connections in place, 
does it spin up, can it be accessed using a linux bootable CD such as 
Knoppix ?

Or the drive could just be knackered :-}

-- 
Please add "[newsgroup]" in the subject of any personal replies via email
--- My new email address has "ngspamtrap" & @btinternet.com in it ;-) ---

jrefactors@hotmail.com wrote:

>When you say hardware malfunction, it basically means defective hard
>drive?

Pretty much. It sounds to me like shot hardware.

>If the hard drive has defects, how can I fix that?

Get a new one. ;^>

>This is a laptop
>machine. The cable can have problem too? If so, how can I fix?

Open it up, look inside. Is the thing still under warranty?




JK'05

Jan Kannemacher wrote:
>>If the hard drive has defects, how can I fix that?
> 
> Get a new one. ;^>

The OP is probably somewhat partial to the data currently residing on 
the wonky drive. Losing it would be bad. Throwing it away due to what 
turns out to only be a flaky cable or controller would be worse.

-- 
http://www.gnu.org/philosophy/right-to-read.html
Palladium? Trusted Computing? DRM? Microsoft? Sauron.
"One ring to rule them all, one ring to find them
  One ring to bring them all, and in the darkness bind them."

Twisted One <twisted0n3@gmail.invalid> wrote:

>The OP is probably somewhat partial to the data currently residing on 
>the wonky drive. Losing it would be bad. Throwing it away due to what 
>turns out to only be a flaky cable or controller would be worse.

Then he should stuff the disk as secondary into another notebook or an
external 2.5" case in order to salvage as much as possible. But if his
own notebook doesn't even recognize the drive anymore when booting off
the W2K CD it looks a lot like a disk failure.




JK'05

Jan Kannemacher wrote:
> Twisted One <twisted0n3@gmail.invalid> wrote:
>
> >The OP is probably somewhat partial to the data currently residing
on
> >the wonky drive. Losing it would be bad. Throwing it away due to
what
> >turns out to only be a flaky cable or controller would be worse.
>
> Then he should stuff the disk as secondary into another notebook or
an
> external 2.5" case in order to salvage as much as possible. But if
his
> own notebook doesn't even recognize the drive anymore when booting
off
> the W2K CD it looks a lot like a disk failure.
>


Thanks a lot. I just borrowed someone's notebook hard disk and replace
the one in the laptop, it is able to boot the machine and works fine.
So it means hard disk failure then. I guess cable and other things are
fine. But any ideas how to fix that?


thanks!!

jrefactors@hotmail.com wrote...

>Thanks a lot. I just borrowed someone's notebook hard disk and replace
>the one in the laptop, it is able to boot the machine and works fine.
>So it means hard disk failure then. I guess cable and other things are
>fine. But any ideas how to fix that?

Ask a friend to fix it for you.

It needs some kind of tools that boot up on a CD or floppy
that can detect your hard drive and then fix the MBR, assume
the hard drive still workable.

Examples of such tools are:
- Acronic Partition Expert
- PowerQuest Parition Magic
- Bart's Bootable PE
- Winternala Admin Pak

Thanks. Well, I can see the Windows 2000 Professional splash screen,
but it just stuck in progress bar, and eventually it shows the blue
screen 0x0000007B (0x818227D0,0xC0000006,0x00000=AD000,0x00000000)
Inaccessible Boot Device. I have PowerQuest Parition Magic, and I ran
that and it shows some errors, but looks like it didn't fix for me. Ok,
it is obvious the hard drive has problem, my question is which tools
can fix the hard drive?

jrefactors@hotmail.com wrote...
>
>Thanks. Well, I can see the Windows 2000 Professional splash screen,
>but it just stuck in progress bar, and eventually it shows the blue
>screen 0x0000007B (0x818227D0,0xC0000006,0x00000=AD000,0x00000000)
>Inaccessible Boot Device. I have PowerQuest Parition Magic, and I ran
>that and it shows some errors, but looks like it didn't fix for me. Ok,
>it is obvious the hard drive has problem, my question is which tools
>can fix the hard drive?

The easiest way to fix this kind of problem is restoring from a backup.
But usually people don't have backup ... and that's why they ask for
help.

There is no simple answer to your Q (re: which tool to fix the hard drive),
assume there is no physical damage to the hard drive.

Different people may tickle your problem in different ways.
For me, I will try to re-install the OS and restore those rescued
data with the following procedure.

1. borrow a good hard drive (with bootable OS installed) from a friend.
   Boot up your computer with the good hard drive mounted on.
2. hook up your original hard drive to the PC as a data drive.
   Maybe via USB, or via some sort of networking.
3. copy those important data file from the original hard drive,
   and burn them to CDs/DVDs
4. remount your computer with the orginal hard drive.
5. boot up a CD with Partition Magic and reformat the hard drive
6. Install the OS from a OS CD
7. reinstall any custom programs
8. restore the rescued data from step 3 back to your hard drive
9. backup your OS and burn to CD/DVD
10 Do regular backup. Next time you have the same problem, it will be
   easy to restore your OS from the backup.

Good luck.

Thanks Harry, your suggestion is helpful, but the suggestion is based
on the assumption that there is no physical damage to the hard drive.
Correct? What if the hard drive has physical damage?

please advise. thanks!!

jrefactors@hotmail.com wrote...
>
>Thanks Harry, your suggestion is helpful, but the suggestion is based
>on the assumption that there is no physical damage to the hard drive.
>Correct? What if the hard drive has physical damage?

Usually BSOD (Blue Screen Of Death) is not due to corrupted files.
In case of a hard ware failure, rescue as much useful data as possible.
And replace the fautlty hard drive with a new one.