Okay. My uncle has a DFI CFX-3200-DR running with a 4400 and two gb corsair RAM (Two 1gb sticks) and X1900XT's in crossfire.
However, there is a small issue with the Xfire. The damn thing won't work, in the device properties for the slave card there's a device code 10 error, device cannot start. It is, apparently, sharing the IRQ with the ULI SATA RAID, Marvell network port and the USB. Gone through disabling all the things on the same IRQ, and having them all enabled, to no avail. Then tried an install on the other SATA controller, same issue. Tried removing SmartGart from the setup, and run through 6.4 - 6.6 on the catalyst versions.
It boots fine, but just does not allow Crossfire to be enabled. Read through the DFI-Street forums, OcUK forums and had a fair browse of AT forums and came up with squat. The revision of the motherboard is somewhat difficult to find, as the sticker is on the bottom of the bottom PCI slot hidden behind tubing and some cables.
Posted in Video because it is predominantly a video related issue, but it may be other hardware conflicts, Windows just doesn't want to tell us what.
Any help is appreciated, cheers.
However, there is a small issue with the Xfire. The damn thing won't work, in the device properties for the slave card there's a device code 10 error, device cannot start. It is, apparently, sharing the IRQ with the ULI SATA RAID, Marvell network port and the USB. Gone through disabling all the things on the same IRQ, and having them all enabled, to no avail. Then tried an install on the other SATA controller, same issue. Tried removing SmartGart from the setup, and run through 6.4 - 6.6 on the catalyst versions.
It boots fine, but just does not allow Crossfire to be enabled. Read through the DFI-Street forums, OcUK forums and had a fair browse of AT forums and came up with squat. The revision of the motherboard is somewhat difficult to find, as the sticker is on the bottom of the bottom PCI slot hidden behind tubing and some cables.
Posted in Video because it is predominantly a video related issue, but it may be other hardware conflicts, Windows just doesn't want to tell us what.
Any help is appreciated, cheers.