(Solved)Gigabyte GA-7VRXP + previous Win2k system disk = BSOD 'inaccessible_boot_device'

[bozoguy]

I just bought a new Gigabyte GA-7VRXP mobo. The system disk I'm trying to hook up to the board is a previous Win2k install which use to sit on my old Asus A7A266 mobo untill it blew a voltage regulator.

As I have a previously configured system disk with all my apps installed I really do NOT want to have to rebuild the disk. I want to just plug it in and carry on with my current install of Win2k.

When I plug it into my new Gigabyte mobo though, I get a BSOD upon bootup. The crash happens right after the colorfull windows bootup screen pops up which comes after the black and white system loading bar that gives you the option to hit F8. The BSOD error message is about an INACCESSIBLE_BOOT_DEVICE.

This mobo has an onboard Promise IDE RAID chip in it. I've disabled the Promise RAID functionality in the BIOS. I thought that perhaps the RAID stuff was throwing Win2k for a loop and causing it to BSOD. I also have tried installing the Promise ATA 100 system drivers on the off chance that Win2k was having a problem accessing the disk. None of these things did anything to help the situation.

I've also flashed the BIOS to the most rescent version. It didn't help.

My hardware is as follows:
AMD Athalon 1.4Ghz
Gigabyte GA-7VRXP
1 x 512M DDR-PC2700: 333mhz (Samsung)
Matrox G400

I've googled for "inaccessible_boot_device gigabyte" and other variations and can't seem to find anyone else who has had the same problem. I find it hard to believe that I'm the only person who has wanted to carry over their system drive when swapping mobo's though. If other people have had the same problem I sure can't find anything on it!

Anyone have any potential insight into this?

Thanks in advance!

 

[Peter]

Normal ... W2K's IDE drivers are chipset specific, so if you move to a different one, it can't access the boot drive anymore. No way around it identified so far - just search for other threads on the same topic here.

 

[cards]

BOZOGUY - well I am not the only one with this problem -

see my recent thread on this related to a new ecs board - the problem appears to be the same regardless of the board - dbruce found an answer on the MS support site - there appears to be a work around but I haven't tried it yet. If you do it - let me know if it works.

 

[bozoguy]

Thankyou Peter and cards.

Peter, you were quite right. It was the IDE chipset drivers.

cards, thankyou for pointing me to the discussion in your thread. The solution posted by dbruce pointing at the MS Knowledge Base article fixed my problem. I used the solution in the KB article that has you install all the standard drivers for all IDE devices into your system drive before you move the drive over to the new mobo.

I was being to focused in my search for the problem. I thought it was a Gigabyte related issue when really it was a general Win2k issue.

Thankyou again for the help.

 

[cards]

bozoguy - you are most welcome. I too thought it was a motherboard problem (ECS) so I started in the same place you did.

When you did the fix did you go back to your original hardware (old motherboard, etc.)- run the registry fix and then rebuild with the gig motherboard??? I have another machine that has the same hardware config as the one I replaced with the ECS board - so I think I can mount the drive on that other machine and run the fix -

thanx

 

[bozoguy]

cards - yes, I put the drive into another computer which had an identical mobo. I added the registry entries for the additional core IDE chipset drivers when it was booted on the identical mobo, and once that had been done, I placed the drive into the Gigabyte mobo and the system booted successfully.

Once it booted the Gigabyte mobo, I had to add drivers for all the new devices (onboard lan, sound, etc..) but once I did that, everything was working wonderfully.

Good luck!