INACCESSABLE_BOOT_DEVICE

[RANDOMNUMBERS234]

i am not very great on computers and i have been having problems starting up my computer. i keep getting the bsod an it says:

***STOP: 0x0000007B (0x8186E130, 0xC000014F, 0x00000000, 0x00000000)
INACCESIBLE_BOOT_DEVICE

there is also some instructions on the page but i cant follow them because it says to goto start>run and type in:

CHKDSK /F

i cant do this though because my computer won't get past the blue screen. someone please respond. im in great distress.

 

[wolluf]

Is there any history to this problem (eg, when did it start happening, did you change any hardware/software, have major crash, virus etc just before this)?

If you have access to another machine running NT/2k/XP, you could try installing drive as slave and running chkdsk from there. If you have access to a 2k or XP install CD, you could run their recovery console (works with NT installations too) - which would also allow you to run chkdsk (or you could download the 2k or XP 'install disk set', which also allows you to start recovery console -

http://www.bootdisk.com/bootdisk.htm).

 

[dwah]

I am having the identical problem, and I notice by the date that this is recent for you. I am therefore concerned that there is an external source.

I have run the chkdsk /f, and the system continues to fail startup. At this point, chkdsk does not complete for any of three partitions.

I am wondering if anyone has experience with a failed mounting. Does this mean that the master boot record is faulty? Is it appropriate to replace it with the fixboot or fixmbr commands in recovery console?

I welcome the assistance and offer my own attempts at correction to "randomnumbers."

 

[wolluf]

dwah - r u running NT, 2k or XP? (and same questions as for RANDOMNUMBERS234 - any history?)

I also don't understand 'I have run the chkdsk /f, and the system continues to fail startup. At this point, chkdsk does not complete for any of three partitions.' Where are you running chkdsk from - and has it ever completed for any partition? I'd get the drive manufacturer's utility to check the integrity of the drive (they've nearly all got one on their sites). Other hardware issues can also cause this sort of error.

 

[andyfram]

I just had this problem on my PDC. I moved the drive to a windows 2000 server as a slave drive. On bootup, it automatically ran a scandisk and moved data from some bad sectors. I put the drive back into the PDC and it started up OK.