Changing to onboard IDE causes BSODs...

[Burke]

I currently have both my hard drives connected to a Promise controller card. I thought about trying the onboard IDE connectors for the drives, but when I attached them I got a BSOD as Windows XP was loading. I rebooted but got the same error; unfortunately, the screen clears so fast I can't document what it says. I then reconnected the drives to the controller card and booted normally, and according to the Device Manager the primary IDE is enabled and working properly with no conflicts.

The primary IDE is enabled in the BIOS, the jumpers are set appropriately and I have the latest Intel chipset drivers installed, but if I originally installed Windows with the hard drives attached to the controller (and had to install the SCSI drivers using F6 during setup), does that mean I can't use the onboard IDE at all? I can't believe it would be such a catastrophic change moving from the controller to the onboard IDE, but I'd appreciate any help or explanation as to why this would happen and any easy remedies (if there are any).

Gigabyte 8IRXP
Promise Ultra100TX2
80 & 120 GB WD SEs
WinXP Pro

Thanks!

[Burke]

Wait a sec...lemme try changing the boot order in the BIOS!

[TEH WIN]

when you used the on board, did you take out the controller card since you werent using it at all? if you left it in, it may be causing conflicts

[Burke]

Yep, I pulled the card as well but still get the BSOD.

[cyberskye]

IF you're getting a BSOD that means the OS has at least started loading - so you know that it is finding the boot disk ok.

I would boot into safe mode, remove the device in Device Manager (or control panel>add/remove hardware). Reboot. Windows should run you through the hardware wizard and load the right drivers.

Skye