STOP: Inaccessible_boot_device

  • Thread starter Thread starter aa
  • Start date Start date
A

aa

On booting a PC with multiple OS (w2k and XP), the OS selection screen shows
OK
Then after showing that initial W2K window (logo on white background), a
blew screen with white letters reading
STOP: 0x0000007B (0x817E7670,0xC0000032,0x00000000,0x00000000
Inaccessible_boot_device

The other OS - XP still boots well

What can I do?
 
First, I had power interruption when the computer was on
Then I booted into w2k OK, but Outlook would not start.
I booted into XP, it said that disk check is needed, I allowed it to compete
disk chen and XP booted OK. Then I re-booted into w2k and got the blue-white

Dave Patrick said:
More info required. What is the history here.


--

Regards,

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


aa said:
On booting a PC with multiple OS (w2k and XP), the OS selection screen
shows
OK
Then after showing that initial W2K window (logo on white background), a
blew screen with white letters reading
STOP: 0x0000007B (0x817E7670,0xC0000032,0x00000000,0x00000000
Inaccessible_boot_device

The other OS - XP still boots well

What can I do?
Click to expand...
Click to expand...
 
I'd suspect file system corruption but you can try a boot disk. For the
floppy to successfully boot Windows 2000 the disk must contain the "NT" boot
sector. Format a diskette (on a Windows 2000 machine, not a DOS/Win9x, so
the NT boot sector gets written to the floppy), and copy Windows 2000
versions of 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. Below is an
example of boot.ini. The default is to start the operating system located on
the first partition of the primary or first drive (drive0). Then drive0
partition 2 and so on.

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



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
Thank you, Dave, Could I get a bit of theory first to have understanding of
what and why I will be doing.

The same ntldr, ntdetect.com, and boot.ini are used by XP and it works. I
know that ntldr and ntdetect.com for XP are different from those for w2k,
but they are OK for w2k.
Are u saying that these files might be partly corrupted, i.e. the part for
XP is OK but the part for w2k is bad?
 
Thank you, Dave, Could I get a bit of theory first to have understanding of
what and why I will be doing.

The same ntldr, ntdetect.com, and boot.ini are used by XP and it works. I
know that ntldr and ntdetect.com for XP are different from those for w2k,
but they are OK for w2k.
Are u saying that these files might be partly corrupted, i.e. the part for
XP is OK but the part for w2k is bad?

Also if I replace my existing XP's files with w2k, my XP will not boot, and
I will be left with no access to this help. Perhaps I should replace the
XP's files with the XP's ones?
 
Thank you, Dave, Could I get a bit of theory first to have understanding of
what and why I will be doing.

The same ntldr, ntdetect.com, and boot.ini are used by XP and it works. I
know that ntldr and ntdetect.com for XP are different from those for w2k,
but they are OK for w2k.
Are u saying that these files might be partly corrupted, i.e. the part for
XP is OK but the part for w2k is bad?

Also if I replace my existing XP's files with w2k, my XP will not boot, and
I will be left with no access to this help. Perhaps I should replace the
XP's files with the XP's ones?
 
Thank you, Dave, Could I get a bit of theory first to have understanding of
what and why I will be doing.

The same ntldr, ntdetect.com, and boot.ini are used by XP and it works. I
know that ntldr and ntdetect.com for XP are different from those for w2k,
but they are OK for w2k.
Are u saying that these files might be partly corrupted, i.e. the part for
XP is OK but the part for w2k is bad?

Also if I replace my existing XP's files with w2k, my XP will not boot, and
I will be left with no access to this help. Perhaps I should replace the
XP's files with the XP's ones?
 
I'm guessing there may have been some file system corruption on the Windows
2000 boot partition, that was the reason chkdsk ran and the system no longer
starts.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
 
aa said:
On booting a PC with multiple OS (w2k and XP), the OS selection screen shows
OK
Then after showing that initial W2K window (logo on white background), a
blew screen with white letters reading
STOP: 0x0000007B (0x817E7670,0xC0000032,0x00000000,0x00000000
Inaccessible_boot_device

The other OS - XP still boots well

What can I do?
Click to expand...


Boot to XP

then run chkdsk /f
on the Win2k partition
 
thank you. How do I make sure that chkdsk /f runs on w2k partition?
Does chkdsk /f takes a target drive letter as a parameter?
 
if this is the case, then replacing the three files you mentioned will not
help will it?
Also if I have the second OS working can't I replace the three files from
that OS without bothering with floppy?
 
An attempt to run chkdsk resulted in a message:
File system NTFS
CHKDSK cannot be executed as this volume is used by other processes. DO you
want to run CHKDISK next time you boot in?
 
run chkdsk w2k_drive_letter: /f
file check
index check
descriptors check
No errors found

Thereafter it booted OK
Thank you
Just one question left - if no erors were found and consequently corrected,
how come simple run of chkdsk sorted out the problem?
 
Dave Patrick said:
The disk drive may be failing.
Click to expand...


As a precaution yes, I'd run the manufacturer's diagnostic.

Either way, backup the data on that drive

then perform a repair install
--

Regards,

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


aa said:
run chkdsk w2k_drive_letter: /f
file check
index check
descriptors check
No errors found

Thereafter it booted OK
Thank you
Just one question left - if no erors were found and consequently
corrected,
how come simple run of chkdsk sorted out the problem?
Click to expand...
Click to expand...
 
Back
Top