hidden hit counter
Welcome to WindowsForumz.com!
FAQFAQ      ProfileProfile    Private MessagesPrivate Messages   Log inLog in

INACCESSIBLE_BOOT_DEVICE

 
   Win 2000/NT/98/ME (Home) -> Setup RSS
Next:  where is the log file for chkdsk /f on nt 4.0 ser..  
Author Message
tk72

External


Since: Jan 31, 2007
Posts: 2



(Msg. 1) Posted: 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

 >> Stay informed about: INACCESSIBLE_BOOT_DEVICE 
Back to top
Login to vote
Jiri Tuma1

External


Since: Mar 09, 2004
Posts: 31



(Msg. 2) Posted: 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.TakeThisOut@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
>

 >> Stay informed about: INACCESSIBLE_BOOT_DEVICE 
Back to top
Login to vote
tk72

External


Since: Jan 31, 2007
Posts: 2



(Msg. 3) Posted: 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
 >> Stay informed about: INACCESSIBLE_BOOT_DEVICE 
Back to top
Login to vote
John John

External


Since: Jun 05, 2004
Posts: 808



(Msg. 4) Posted: 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
>
 >> Stay informed about: INACCESSIBLE_BOOT_DEVICE 
Back to top
Login to vote
Display posts from previous:   
Related Topics:
missing kernel file... - Hi. I am hoping someone might be able to help me... Background: I worked at a big firm, the tech dept installed NT 4.0 on my computer so I could log on from home... Useful while I was working there... bad idea now that I left. Because I don't have an...

NT4 Ent. System Requirements - Hello: I would like to know how many memory does NT4 Ent. can supported? Does the NT4 Ent. can support Up to 32 CPU? Thanks!

Is Adaptec Aha-1542cp supported by Windows2000? - I cannot find any drivers of whatsoever or any documentation that could verify that this controller is supported by Windows2000. However, my guess is that it should be, as it is ISA legacy PnP hardware. Am I right or there are drivers some ware..

Can't run repair on Dell Poweredge - Hope someone out there can help me. I'm attemting to run a repair on a Dell Poweredge 4400 server, but the NT4.0 CD fails to find the operating system when trying to run the checks. It shows detected SCSI devices then comes up with a message that the...

BDC NT4.0 on domain 2003 - Hi, I cannot add a BDC in domain 2003. The domain in mixed mode. The error is "Unable to connect to the domain controller for thi domain. Either the user name or password entered is inconrrect" You can helpme.... Jaime
   Win 2000/NT/98/ME (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

Categories:
 Windows XP
  Win 2000/NT/98/ME
 Windows Vista!


[ Contact us | Terms of Service/Privacy Policy ]