cancel
Showing results for 
Search instead for 
Did you mean: 

Rampage IV Extreme Crossfire Issues

foana
Level 7
I tried to setup Crossfire with 2 Sapphire HD7950 cards. Followed instructions perfectly. After installing the latest driver with both graphics cards installed I rebooted.

Now I get no display. Debug code is 25. Tried booting with each card individually and still get debug code 25 with no display.

I have searched the internet and this forum and could not find any information on debug code 25, I am hoping someone else has had this issue.
3930K
RIVF
2 x HD7950 1100/1250
16Gb G.SKILL RipjawsZ 2133Mhz
2 x Samsung 840 Pro 256Gb Raid0, OCZ Vertex 3 Max IOPS 120Gb
2 x 2Tb WD Caviar Black, WD Raptor 150Gb
Seasonic X-1250
HAFX
XSPC AX360 3 x Scythe GT 1850
Yamakasi Catleap 2B 2560x1440@124hz
Windows 7 x64
24,060 Views
40 REPLIES 40

foana
Level 7
After removing power from PC for ~10 minutes tried to boot with 1 card in and still no display but had a different debug code, 61.
3930K
RIVF
2 x HD7950 1100/1250
16Gb G.SKILL RipjawsZ 2133Mhz
2 x Samsung 840 Pro 256Gb Raid0, OCZ Vertex 3 Max IOPS 120Gb
2 x 2Tb WD Caviar Black, WD Raptor 150Gb
Seasonic X-1250
HAFX
XSPC AX360 3 x Scythe GT 1850
Yamakasi Catleap 2B 2560x1440@124hz
Windows 7 x64

foana
Level 7
After trying to clear CMOS with back IO button, now receive debug code 14. It hangs on this whether I have a graphics card installed or not.
3930K
RIVF
2 x HD7950 1100/1250
16Gb G.SKILL RipjawsZ 2133Mhz
2 x Samsung 840 Pro 256Gb Raid0, OCZ Vertex 3 Max IOPS 120Gb
2 x 2Tb WD Caviar Black, WD Raptor 150Gb
Seasonic X-1250
HAFX
XSPC AX360 3 x Scythe GT 1850
Yamakasi Catleap 2B 2560x1440@124hz
Windows 7 x64

foana
Level 7
After removing cmos battery for 5 minutes I now get debug code b0 or 60, it would read as b0 if you were to look at it. This also leads me to believe that the above post could have actually been debug code b1, not 61.

Been waiting on the RMA for this rampage iv extreme since January 10th and only received today. Seriously considering scrapping the lot and starting a new build.
3930K
RIVF
2 x HD7950 1100/1250
16Gb G.SKILL RipjawsZ 2133Mhz
2 x Samsung 840 Pro 256Gb Raid0, OCZ Vertex 3 Max IOPS 120Gb
2 x 2Tb WD Caviar Black, WD Raptor 150Gb
Seasonic X-1250
HAFX
XSPC AX360 3 x Scythe GT 1850
Yamakasi Catleap 2B 2560x1440@124hz
Windows 7 x64

HiVizMan
Level 40
Please remove all your hardware from the case and start your build from scratch.

Start with only one stick of ram, then run the Memtest86+ application as per the guide in my sig.

Once you have done that then we will take the next step.

Clear CMOS is your friend as you know, as is the mem OK button.
Remember you have the option of a dual bios so please do switch from the A to the B and see if that helps.
To help us help you - please provide as much information about your system and the problem as possible.

After more testing it is most common for the system to hang on debug codes 14, and 61. In some cases it starts on 14, jumps to 60 then 61, back to 14 and will hang, or will jump onto 60 and hang, or jump to 61 and hang, all with different memory modules.
3930K
RIVF
2 x HD7950 1100/1250
16Gb G.SKILL RipjawsZ 2133Mhz
2 x Samsung 840 Pro 256Gb Raid0, OCZ Vertex 3 Max IOPS 120Gb
2 x 2Tb WD Caviar Black, WD Raptor 150Gb
Seasonic X-1250
HAFX
XSPC AX360 3 x Scythe GT 1850
Yamakasi Catleap 2B 2560x1440@124hz
Windows 7 x64

foana
Level 7
Thanks HiVizMan,
I removed everything from board. Installed CPU + cooler. Inserted 4 8 and 24 pin power. Installed one stick of ram and the new graphics card of the 2 7950s that I have.
Had a load of different debug codes which hung, or just reset the PC, including debug code 10, 14, 15, 60, 61, and AF. Tried each stick of ram that I have (total of 4) which all had same debug codes listed. Tried cmos reset switch and back IO and that mainly resulted in debug code 14 hang.
One time after resetting the cmos on back IO, the system went through a load of debug codes very quickly and actually posted, I went into the bios and it hung, at which point I changed the stick of ram to another thinking it could have been faulty.
I am unsure how I supposed to run memtest if I cannot get a display up? Also, I cannot deduce whether I am on bios A or B, how is this done?
So lost as to how this has all happened from installing a second gfx card in a system, which is supposed to handle 4, that worked perfectly before the second card was installed.
3930K
RIVF
2 x HD7950 1100/1250
16Gb G.SKILL RipjawsZ 2133Mhz
2 x Samsung 840 Pro 256Gb Raid0, OCZ Vertex 3 Max IOPS 120Gb
2 x 2Tb WD Caviar Black, WD Raptor 150Gb
Seasonic X-1250
HAFX
XSPC AX360 3 x Scythe GT 1850
Yamakasi Catleap 2B 2560x1440@124hz
Windows 7 x64

HiVizMan
Level 40
As to the how, well you are not going to like it. When you installed the second card I am willing to bet you did not wear an anti-static band. And static electricity is not your friend when it comes to PC bits and pieces. I constantly have myself earthed while working at my test bench. But that is neither here nor there. What is important is that we try to sort out your little issue and get your system running again.

You have two BIOS chips as you know, the toggle is either in one position or the other. It makes no difference at this point select the one that is closest to the edge of the motherboard and lets move on. 🙂

Since your system is stripped to the bone that is good. I am going to paste in my full clear CMOS procedure. Please do follow it to the letter.

Clear CMOS

Completely remove all the hardware from your motherboard, and take the motherboard out of your case. Remember to disconnect the PSU connectors before you start to remove stuff.

Place the motherboard, now without CPU or battery on the box that your motherboard came in. It is a non-conductive and non-static surface.

Inspect the CPU socket area. I doubt that there is anything problematic there, but since the mobo is naked have a visual inspection for bent or misaligned pins.

Press start button for a couple of seconds to discharge the caps of any residual current.

Hold down the Clear CMOS button for a slow count of 3. Look in your manual if you are not sure where it is.

Leave your system as is over night. Or at least 8 hours.

Then with the bare minimum of hardware assembled in this order.

CPU and cooler.

One stick of ram in the furthest slot from the CPU.

One VGA

No hard drive.

No optical drive.

Keyboard and mouse.

VGA power connectors.

12 Volt CPU connector (8 Pin)

24 Pin power supply connector.

Plug the PSU into the wall socket.

Fat formatted USB stick with the latest BIOS connected a USB2 port.

Power up your system.

Make note of the two digit Q-Codes (if your motherboard supports a LED poster that is - if not look on your notebook using ROG connect.

Please use the delete key on the numeric keyboard, but most likely you will need to use F1 when prompted due to the clear CMOS.

Now navigate to the Tools in BIOS.

Select EZFlash2 and flash your BIOS.

DO NOT POWER DOWN.

The only time you will do anything is to select yes when asked if you wish to reset and reboot.

Let the system complete the iRog firmware upgrade if needed. This may take a few minutes but no longer than 30 mins.

Once you have completed the Flash and your system has reset and rebooted and you are back in BIOS. Power down.

Press Clear CMOS one more time.

Now add your OS hard drive only.

Power up to BIOS and set your SATA mode if needed.

Rebuild your system.
To help us help you - please provide as much information about your system and the problem as possible.

foana
Level 7
Ok I found the bios switch and that did not help, same as before, except that one time i did get debug code b9, which hung, after rebooting it just hangs on 14, 60 or 61, on both bios.
3930K
RIVF
2 x HD7950 1100/1250
16Gb G.SKILL RipjawsZ 2133Mhz
2 x Samsung 840 Pro 256Gb Raid0, OCZ Vertex 3 Max IOPS 120Gb
2 x 2Tb WD Caviar Black, WD Raptor 150Gb
Seasonic X-1250
HAFX
XSPC AX360 3 x Scythe GT 1850
Yamakasi Catleap 2B 2560x1440@124hz
Windows 7 x64

HiVizMan
Level 40
Will check back once you have done the full clear CMOS.
To help us help you - please provide as much information about your system and the problem as possible.