Page 1 of 1
Inaccessible Boot Device...
Posted: 2003-12-28 08:32pm
by Hobot
I've been using a fresh instal of Windows 2000 on my newly built computer for a couple weeks and I've just recently set up a wireless network. So today I decided to update Windows 2000 with service pack 4 and installed it. I restarted and to my horror I got a blue screen of death telling me "Inaccessible Boot Device". I restarted several times and tried changing my BIOS settings (I have an SATA drive so I thought that might be a problem), but nothing worked. Does anyone have any idea what might be wrong?
System Specs:
AMD 2200+ XP
DFI Lanparty NFII Ultra
36.7 GB Western Digital Raptor (SATA)
80 GB Maxtor IDE (set to slave)
Liteon DVD/CD-RW
Mitsumi CD-RW
Posted: 2003-12-28 10:03pm
by TrailerParkJawa
1. If you go into your mainboard BIOS does it detect a drive?
2. Have you checked to see if the serial ATA cable is loose either at
the mainboard or the back of the drive?
3. Does it BSOD before you even get a chance to try starting in safe mode?
Posted: 2003-12-29 12:14am
by Hobot
1. Yes
2. Yes
The drive itself is completely fine, it's connected properly and other operating systems (like Win98, Mandrake and Win2k before SP4) work fine.
3. I can select safe mode but I still get the bsod, about the only thing I could do was use the console
I've now formatted and reinstalled Win2k, it seemed to be less of a hassle. Still, I would like to find out what went wrong. I've got a similar error before from trying to instal XP...
Posted: 2003-12-31 02:45pm
by Hobot
Does anybody have any idea? =/
Posted: 2003-12-31 03:16pm
by Vertigo1
Did you check MSDN for issues with SATA controllers?
Posted: 2004-01-03 02:22am
by Hobot
I've been checking and I can't find any related SATA issues. I don't understand why the latest versions of Windows will not work on my computer but everything else does. You'd think it'd be the opposite...
Posted: 2004-01-03 05:45pm
by Pu-239
Did you update drivers before installing SP4?
Posted: 2004-01-20 12:31am
by Hobot
Sorry for the thread necromancy but I finally came across a solution! It turns out that the DFI motherboard's SATA controller gets all fucked up if you have another read/write device on the primary IDE channel. So all I had to do was disconnect my secondary hard drive and I was able to install Windows XP without the BSOD. Now I'm not sure what this means if I want a secondary hard drive, perhaps I'll be able to attach it to the RAID IDE connections on my mobo. Stupid DFI, if they had only announced this bug on their website.