• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

pci sil3114 problem

stetser

n00b
Joined
Apr 10, 2007
Messages
12
I'm having trouble with a new sil3114 add-in card that I recently bought: I cannot boot Windows XP with any drives connected to it.

I've flashed it to the latest bios downloaded from Silicon Image, and I'm using the latest driver as well. I can boot the computer fine with the card inserted, however as soon as I try to plug any device into it, my computer will either hang on the windows boot screen (with the bar going across indefinitely), or at the raid controller screen after the BIOS POST. I've tried every single PCI slot, and I absolutely cannot figure out why connecting devices would make my computer hang.

I'm running an ABIT IC7-MAX3 motherboard, which has an integrated sil3114 to handle SATA ports, but I have no reason to believe that two sil3114's in a system would cause conflict.

If anyone has any suggestions I would greatly appreciate them.
 
I had the same problem when I installed a Promise SATA300 on top of a Promise SATA150 in my system.

The reason is conflicting drivers and saved configurations. The reason it crashes when you add a drive is because it uses the same table for both cards to detect drives. So when you add a drives to a port on the second card, it crashed because it sees that there is already an active working drive on that same slot (but on the first card).

What I *think* might work: Rename the drivers .sys file , and fix the entries in the .inf to reflect that name change.

If that doesn't work, I would suggest getting a new controller card that uses different drivers.
 
Back
Top