hidden hit counter
Help!

INACCESSIBLE_BOOT_DEVICE

 
  

Post new topic   General Reply to Topic (not reply to a specific post)    Forums Home -> Setup RSS
Next:  TCP/IP enable in connection configuration  
Author Message
tk72
External


Since: Jan 31, 2007
Posts: 2



PostPosted: Wed Jan 31, 2007 8:46 pm    Post subject: INACCESSIBLE_BOOT_DEVICE
Archived from groups: microsoft>public>windowsnt>setup (more info?)

One morning when I powered up my computer, I received the lovely
INACCESSIBLE_BOOT_DEVICE message on my computer, which runs Windows
2000 Professional SP4. I had not done any hardware or software
upgrades. I have tried all kinds of tools, and I have always been
able to see my drives (I have two SCSI drives), so I am pretty sure it
isn't a hardware problem. I finally broke down and installed another
copy of the same OS (not any service packs though), on the same drive
but in a different folder, and I can boot successfully from that
installation now. I am however still getting the
INACCESSIBLE_BOOT_DEVICE when I try to boot to the original
installation. In the BOOT.INI file, the only difference in that the
old installation is showing WINNT and the new TEMPWIN. The
INACCESSIBLE_BOOT_DEVICE message shows up about half way through the
colorfull Windows screen if that helps anything. I have tried to boot
in both Safe Mode and Last Known Good Configuration with the same
outcome. Does anyone know what I can try next? Are there files I can
copy from the new installation to the old, or are there other steps I
can try. My guess is that one of the files has became corrupt, but I
have no idea which one. I did try booting with loging turned on, but
if I've done my research correctly, the ntbtlog.txt file isn't created
until later.

Thanks for any advice,

Tor
Back to top
Jiri Tuma1
External


Since: Mar 09, 2004
Posts: 31



PostPosted: Thu Feb 01, 2007 1:29 pm    Post subject: Re: INACCESSIBLE_BOOT_DEVICE [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

there are two modules able to produce this error message NTLOADER and
NTKERNEL, next time you get this message, look for source module
identification somewhere on this blue screen of death. It is important
information to know

The cause of this error message is, that actual disk driver is unable to
access critical files under WINNT folder specified by operating system
descriptor inside boot.ini, usually kernel module itself, system registry or
runtime disk driver file (it can produce different message saying that
specific file is corrupted or missing, it depends on situation). Possible
causes on previously running machine:
* reset of BIOS setting - sometimes happen when CMOS battery is weak or on
some faults (peaks or leaks) of computer electrical power. Especially if you
are using SATA or SCSI disks, it is possible your BIOSes (both motherboard
and disk controller) should be set accordingly to disk driver settings. To
repair this, you need either to set BIOS back to functional settings or
replace manually disk driver file or settings in unfunctional OS instance
(not recommended for unexperienced users!)
* previous change made to disk or partions system. - Adding or removing of
disk, disk controller, adding or deleting of partition on system disk. All
this can change physical order of disks and partitions and can make
operating system descriptor in boot.ini to point to inexistant location. It
is probably not your case, as your descriptors seems to be the same. To
repair this, "just" change OS descritptor in bott.ini to point to correct
disk and partition.
* corrupted or missing file or filesystem - make deep check of filesystem
using other OS instance, eventually apply the same SP and critical system
updates to your temporary instance and try to replace the same files in
SYSTEM32 and system32/drivers folders.

ALWAYS backup original files before making any changes!


"tk72" <t_karlsson72 DeleteThis @hotmail.com> píse v diskusním príspevku
news:1170305211.791404.309970@j27g2000cwj.googlegroups.com...
> One morning when I powered up my computer, I received the lovely
> INACCESSIBLE_BOOT_DEVICE message on my computer, which runs Windows
> 2000 Professional SP4. I had not done any hardware or software
> upgrades. I have tried all kinds of tools, and I have always been
> able to see my drives (I have two SCSI drives), so I am pretty sure it
> isn't a hardware problem. I finally broke down and installed another
> copy of the same OS (not any service packs though), on the same drive
> but in a different folder, and I can boot successfully from that
> installation now. I am however still getting the
> INACCESSIBLE_BOOT_DEVICE when I try to boot to the original
> installation. In the BOOT.INI file, the only difference in that the
> old installation is showing WINNT and the new TEMPWIN. The
> INACCESSIBLE_BOOT_DEVICE message shows up about half way through the
> colorfull Windows screen if that helps anything. I have tried to boot
> in both Safe Mode and Last Known Good Configuration with the same
> outcome. Does anyone know what I can try next? Are there files I can
> copy from the new installation to the old, or are there other steps I
> can try. My guess is that one of the files has became corrupt, but I
> have no idea which one. I did try booting with loging turned on, but
> if I've done my research correctly, the ntbtlog.txt file isn't created
> until later.
>
> Thanks for any advice,
>
> Tor
>
Back to top
tk72
External


Since: Jan 31, 2007
Posts: 2



PostPosted: Thu Feb 01, 2007 4:09 pm    Post subject: Re: INACCESSIBLE_BOOT_DEVICE [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

I upgraded the new installation to SP4 as well, rebooted that verson
with logging turned on, and used the log file from that run to create
a BAT file that copied all the files it laoded into the non-working
installation (I did back up all those files from the non-working
version first). Doing that actually took me past the
INACCESSIBLE_BOOT_DEVICE. Now it looks like the registry files got
messed up in the process as well, so I might have to install all the
software over again anyway. I do have some recovery tools, and maybe
one of those will work. If I had only backed up the system now and
then. Oh well. Thanks for the help though.

Tor
Back to top
John John
External


Since: Jun 05, 2004
Posts: 1937



PostPosted: Fri Feb 02, 2007 10:09 am    Post subject: Re: INACCESSIBLE_BOOT_DEVICE [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Run a chkdsk on the drive.

John

tk72 wrote:

> I upgraded the new installation to SP4 as well, rebooted that verson
> with logging turned on, and used the log file from that run to create
> a BAT file that copied all the files it laoded into the non-working
> installation (I did back up all those files from the non-working
> version first). Doing that actually took me past the
> INACCESSIBLE_BOOT_DEVICE. Now it looks like the registry files got
> messed up in the process as well, so I might have to install all the
> software over again anyway. I do have some recovery tools, and maybe
> one of those will work. If I had only backed up the system now and
> then. Oh well. Thanks for the help though.
>
> Tor
>
Back to top
loyal2blue



Joined: Jan 30, 2009
Posts: 1



PostPosted: Fri Jan 30, 2009 2:34 pm    Post subject: [Login to view extended thread Info.]

STOP: 0x0000007B (0x814AF2D, 0xC0000032, 0x00000000, 0x00000000) INACCESSIBLE_BOOT_DEVICE

We had this problem and this is how you fix it...............

If your error code (0x814AF2D, 0xC0000032, 0x00000000, 0x00000000) is different than this one, this solution may not work............

Could not find anyone who had this exact error code on the internet or examples
of it in the Microsoft Knowledge Base

Found similar examples but they all related to people moving hardware around or adding new hardware

We saw this error appear on boot up and the machine had no problems the previous day, and no changes in configuration, the error appeared out of the blue (pun intended).........

Suspect power surge or loss of power during a shutdown......as the cause

You will need a five disk set of windows 2000 floppy disks.....
Boot the machine, then interrupt the boot and access the bios............
Change the boot order so the computer boots off the floppy disk first..........
Put a windows 2000 boot disk #1 in the floppy drive............
Save the change you made in the bios and let the machine finish the boot up.........
It should then begin booting off the windows floppy #1...........
It wll continue the boot process and ask you for the first four floppy disks in a row.....
It will then prompt you and ask you if you want to do a repair or setup ...........
Choose repair........
it will then ask you for recovery or emergency........
Choose emergency............
it will then ask you for manual or fast........
Choose manual.................
it will then offer you three repair options.........
Deselect inspect startup........
Deselect verify..............
Leave inspect boot sector active and scroll down to continue, hit enter............
It will ask you if you have an emergency disk.......choose L
it will find the windows installation automatically..........
Now choose repair..............

When it is finished the machine will automatically try to re-boot itself.......
Remove floppy #4 so the machine can re-boot and you should be ready to go.......
Back to top
Display posts from previous:   
Post new topic   General Reply to Topic (not reply to a specific post)    Forums Home -> Setup All times are: Eastern Time (US & Canada) (change)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum