PDA

View Full Version : 2x 8800 Ultra, second one has error code 12 in WinXP


firefreak
10-02-07, 02:18 AM
I've got two 8800 Ultra (standard) from evga installed.
I can set any for primary output in the BIOS, under WinXP the other card will be marked with the error code 12 in the Device Manager (and SLI of course not available in nvidia Control Center). The active card in either variant will work perfectly.

From the two working scenarios I can extract the following resource allocations:
Card 1:
Mem: 91000000 - 91FFFFFF
Mem: A0000000 - AFFFFFFF
Mem: 92000000 - 93FFFFFF
IO: 5000 - 507F
IRQ: 19
IO: 03B0 - 03BB
IO: 03C0 - 03DF
Mem: 000A0000 - 000BFFFF

Card 2:
Mem: B1000000 - B1FFFFFF
Mem: C0000000 - CFFFFFFF
Mem: B2000000 - B3FFFFFF
IO: 7000 - 707F
IRQ: 42
IO: 03B0 - 03BB
IO: 03C0 - 03DF
Mem: 000A000 - 000BFFFF

I have dual boot with linux, there both cards and SLI work perfectly. (At least something for the upcoming UT3 and ETQW ;) )

The system is a workstation from SUN "Ultra 40 M2" (Config 3), 2x Opteron 2222SE, 4GB RAM with a 1000W power supply; WinXP Professional with SP2.
Anything unnecessary onboard is disabled in the BIOS (2 SATA controller, serial port); FireWire controller is deactivated in Win Device Manager.

Additional info snippets:
- BIOS is the newest from SUN installed, PhoenixBIOS 4.0, Release 6.1, Version 1.2 - Build 04/24/07
- IOMMU enabled and furthermore tried with a size of 256 (instead of 64); No dice.
- For a test I also had the sound card disabled; Also no dice.
- Also tried with only 2GB RAM and 4GB with /burnmem option; Both with no effect.
- Problem is the same with any driver tested from 162.18 to 163.71 (current)
- Monitoring the boot process by DebugView didn't show anything
- Showing resources by type in the device manager does not show any other conflicting device
- msinfo32.exe (Sharing/Conflicts) only lists shared resources with the working card

Long story short: The system can run SLI if everything wants to (-> linux).
The question now is, what's the difference between the two setups (what the XP driver misses or complains about)?
Is there some more (debug) info I can/should extract? Am I alone? :(

ultraraze
10-02-07, 07:53 AM
I don't have any exp with your hardware but back in the agp days fixing a code 12 was usually remedied by increasing the AGP apeture size. Is there anything like that in your bios?

firefreak
10-02-07, 10:53 AM
IOMMU is the PCIe successor of the AGP aperture - my system has no AGP slot nor corresponding settings.
I just tried the maximum IOMMU size setting possible (512MB) with no effect (other than WinXP reporting even less available memory :p )