Stop 0x7B : (p1,p2,p3,p4) INACCESSIBLE_BOOT

Stop 0x7B : (p1,p2,p3,p4) INACCESSIBLE_BOOT_DEVICE

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

MasterK - 27 Dec 2004 19:32 GMT

I am receiving the blue screen on windows load with the above error). I
suspect this is a virus. I cannot even load the windows cd if the Hard
Drive is powered.

I reset the bios to defaults, and now the Win2K Pro load freezes (with the
start-up bar completely filled across at the bottom of the screen).

Someone just set me off on the right path, I'll go from there. Thanks ...

Reply to this Message

Dave Patrick - 27 Dec 2004 21:54 GMT

What drive controller are you using?

Signature

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

|I am receiving the blue screen on windows load with the above error). I
| suspect this is a virus. I cannot even load the windows cd if the Hard
[quoted text clipped - 4 lines]
|
| Someone just set me off on the right path, I'll go from there. Thanks ...

Reply to this Message

MasterK - 28 Dec 2004 04:02 GMT

Controller is a Bus Master IDE Ultra ATA/66/100/133
(Dual Controller)

Note - this has been working for over a year.

The drive is a WD1200 EIDE (120 Gb).
I have tried to boot from floppy and get a Disk I/O error: Status =
00000200
NTDETECT failed

Thanks for helping ...

Reply to this Message

Dave Patrick - 28 Dec 2004 04:15 GMT

You might try a boot floppy so you can add the driver. For a floppy to
successfully boot Windows NT the disk must contain the "NT" boot sector.
Format a diskette (on an NT machine, not a DOS/Win9x, so the NT boot sector
gets written to the floppy), and copy ntldr, ntdetect.com, and boot.ini to
it; Edit the boot.ini to give it a correct ARC path for the machine you wish
to boot.

In your case you'll want to change the arc path in boot.ini from multi
syntax to scsi syntax to indicate that Windows NT will load a boot device
driver and use that driver to access the boot partition. Then also copy the
manufacturer's Windows NT Ultra ATA controller driver to the floppy but
renamed to ntbootdd.sys

Something like this below;

[boot loader]
timeout=10
default=scsi(0)disk(0)rdisk(0)partition(1)\winnt
[operating systems]
scsi(0)disk(0)rdisk(0)partition(1)\winnt="Windows 0,1"
scsi(0)disk(0)rdisk(0)partition(2)\winnt="Windows 0,2"
scsi(0)disk(1)rdisk(0)partition(1)\winnt="Windows 1,1"
scsi(0)disk(1)rdisk(0)partition(2)\winnt="Windows 1,2"

Signature

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

| Controller is a Bus Master IDE Ultra ATA/66/100/133
| (Dual Controller)
[quoted text clipped - 7 lines]
|
| Thanks for helping ...

Reply to this Message

MasterK - 30 Dec 2004 03:01 GMT

Ok Dave, I was able to get back to this mess. I created the disk as you
suggested. The following message is displayed;

"Windows 2000 could not start because of a computer disk hardware
configuration problem.
Could not read from the selected boot disk. Check boot path and disk
hardware.
Please check the Windows 2000(TM) documentation about hardware disk
configuration and your hardware reference manuals for additional
information."

I also ran the Western Digital DataLifeguard tools on the drive by
creating a DataLifeguard boot floppy from the WD CD. I perform both the
quick test and the complete scan on the drive and no errors were found. It
appears as though the problem lies in the boot partition. So far, I have
not been successful at getting to it.

Next?

Again, thanks for helping.
-Mark

Reply to this Message

Dave Patrick - 30 Dec 2004 03:33 GMT

Did you try all four possible disk/partition combinations? You may need to
adjust for the location of the boot partition.

Signature

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

| Ok Dave, I was able to get back to this mess. I created the disk as you
| suggested. The following message is displayed;
[quoted text clipped - 17 lines]
| Again, thanks for helping.
| -Mark

Reply to this Message

MasterK - 30 Dec 2004 04:01 GMT

Yes. Tried them all. I was finally able to get the Windows CD to boot. Ran
chkdsk ... it's hosed. Ran fixboot ... boot partition is corrupt. I'm
going to re-install if I can. I don't think I have any other choice.

I'll post back soon and let you know if it was successful.

Reply to this Message