Crossfire R9 Fury not available

[RyzenMaster.sys]

Hello, I am looking to Crossfire 2 GPUs but am having trouble setting it up. I have an XFX R9 Nano and an R9 Fury X. I've tried the latest drivers and now am running 19.12.1 and neither has the option for crossfire within adrenalin settings.

Motherboard is an Asus Z68V LE which should support Crossfire. Running Windows 10 64.

Any clue what driver I need or what's going on preventing crossfire from working here? Thanks.

 

[damric]

hmmn which game? Might need older driver, maybe not tho.

 

[RyzenMaster.sys]

Not trying any games yet, there's no option in the driver to enable it to begin with.

 

[damric]

Not trying any games yet, there's no option in the driver to enable it to begin with.

If I remember correctly you have to force it in the game profiles within the driver. It didn't use to be like that but it's what I had to do recently to get some old HD 7950s going. If you need some screenshots I'll try and remember tomorrow. I will have to setup that bench rig which will take a few minutes and I'm not doing it tonight

Also try reinstalling the drivers after you add the second card.

 

[RyzenMaster.sys]

If I remember correctly you have to force it in the game profiles within the driver. It didn't use to be like that but it's what I had to do recently to get some old HD 7950s going. If you need some screenshots I'll try and remember tomorrow. I will have to setup that bench rig which will take a few minutes and I'm not doing it tonight

Also try reinstalling the drivers after you add the second card.

That would be appreciated, thanks.

This system just got a drive from my drawer so it had drivers for some other GPU on it, I threw the driver's on here with both GPUs installed at the same time. May DDU it and reinstall.

 

[damric]

That would be appreciated, thanks.

This system just got a drive from my drawer so it had drivers for some other GPU on it, I threw the driver's on here with both GPUs installed at the same time. May DDU it and reinstall.

it's always a pain in the ass to get CFX/SLI working, but I always had fun benching such systems. I'll get that system up and running tomorrow and see what I did.

 

[68Olds]

Maybe you can find some help in the thread I linked below. I used XfireX a lot, starting with the X1900 series, up to the HD 6970. All of them used a Xfire Bridge & I think "bridge-less crossfire" is kind of a different animal.

Is My CrossFire Setup Working Correctly? [Basic/Advanced Guide]

One of the questions i often see asked is, "How do i know if CrossfireX is working correctly?" Well i have written a basic and advanced guide that will...

forums.guru3d.com

 

[damric]

This is a newer driver. As you see I went into the gaming profile (superposition as example) enabled crossfire and set to AFR.

 

[RyzenMaster.sys]

No bridge on cards this new. I see launch reviews benchmarking them in bridgeless CF though.

The option just does not exist. This is after DDU and installing the latest driver.

 

[68Olds]

Have you trying overclocking the Nano GPU clock to match the Fury's clock? Maybe non-matching clocks are causing an issue (I'm really just guessing here).

 

[damric]

I would say DDU those drivers and install the ones I used in the screenshots.

The last time I did bridgeless cfx was with some vegas but I don't have those anymore to see what configuration I used.

 

[K7SEM]

Place FURY X on primary/master PCIE_16 slot and NANO on secondary/slave PCIE_16
Also the need of connector cable for master and slave is a must have
Search google for complete configuration

 

[damric]

Oof noticed something.

GQ cables plugged into a G2. Totally different platform/OEM.

 

[RyzenMaster.sys]

Oof noticed something.

GQ cables plugged into a G2. Totally different platform/OEM.

Yep, with identical pinouts, works fine. EPS is also compatible and being used here. Everyone says "oh no you can't use any of the GQ cables with anything else" so I did my own investigation since that was a non helpful answer to me. PSU didn't come with cables so I'm using what I had.

Place FURY X on primary/master PCIE_16 slot and NANO on secondary/slave PCIE_16
Also the need of connector cable for master and slave is a must have
Search google for complete configuration

That's the locations I have geen using, mostly to give the Nano breathing room. I'm unsure what "connector cable" are you talking about? These cards don't have bridge connectors on them
I noticed this review from back in the day also used a Fury X CFed with a Nano so this should absolutely work.

The AMD Radeon R9 Fury X Review: Aiming For the Top

www.anandtech.com

I would say DDU those drivers and install the ones I used in the screenshots.

The last time I did bridgeless cfx was with some vegas but I don't have those anymore to see what configuration I used.

I'll try this. If it doesn't work the only thing I can imagine is that it doesn't like this board. It has "Crossfire-X ready" printed on it, but maybe it can't do bridgeless since it's older than these cards by a couple years.

 

[damric]

Yep, with identical pinouts, works fine. EPS is also compatible and being used here. Everyone says "oh no you can't use any of the GQ cables with anything else" so I did my own investigation since that was a non helpful answer to me. PSU didn't come with cables so I'm using what I had.

That's the locations I have geen using, mostly to give the Nano breathing room. I'm unsure what "connector cable" are you talking about? These cards don't have bridge connectors on them
I noticed this review from back in the day also used a Fury X CFed with a Nano so this should absolutely work.

The AMD Radeon R9 Fury X Review: Aiming For the Top

www.anandtech.com

I'll try this. If it doesn't work the only thing I can imagine is that it doesn't like this board. It has "Crossfire-X ready" printed on it, but maybe it can't do bridgeless since it's older than these cards by a couple years.

Ok if you checked the pin-out I believe you. Also probably would have cooked already and we see both GPUs working in windows.

I wonder maybe there is an updated chipset driver for that board. I know it's only x16/x4 but it still should work. Is it PCIe 3 or 2 on that board though? Maybe not enough bandwidth but I've personally never seen that as a problem. I have high hopes that this is just an issue of finding the right driver.

 

[RyzenMaster.sys]

Tried these drivers but still no dice.

i7 2600k and this board are both Pcie 2.0 only.

I had not considered it could be chipset drivers.
Especially since there are missing drivers in device manager, and this os is from another PC.

I'll try it. If this doesn't work is there any way to just force this crap via an ini file or something?

Didn't work. Welp.

 

[zuel_techno]

Hello,

The Nano and Fury-X look similar on paper but how they are setup is VERY different. To get them to work, you will have to place the Nano as master card and the Fury as slave. They driver more than likely is having issues with trying to match the cards since they have different clocks and power requirements. The Nano will not be able to keep up with the Fury, but they Fury can keep up with the Nano. The latest driver (22.6.1) should be more than enough to get them to work together. Due note, that if you intend to play anything that requires 12.1 feature set, you will have to use the "NimeZ" for GCN cards. Crossfire works but it takes effort in some games even before feature set 12.0...

I hate that crossfire and sli were abandoned. When it was done right, it did offer measurable differences that the "Steve's" never really cared to show.

 

[eidairaman1]

Hello,

The Nano and Fury-X look similar on paper but how they are setup is VERY different. To get them to work, you will have to place the Nano as master card and the Fury as slave. They driver more than likely is having issues with trying to match the cards since they have different clocks and power requirements. The Nano will not be able to keep up with the Fury, but they Fury can keep up with the Nano. The latest driver (22.6.1) should be more than enough to get them to work together. Due note, that if you intend to play anything that requires 12.1 feature set, you will have to use the "NimeZ" for GCN cards. Crossfire works but it takes effort in some games even before feature set 12.0...

I hate that crossfire and sli were abandoned. When it was done right, it did offer measurable differences that the "Steve's" never really cared to show.

View attachment 370964

View attachment 370963

Here's a link for setting up crossfire.

https://www.amd.com/en/resources/support-articles/faqs/DH-018.html

@delshay didn'y you have some fury cards?

 

[RyzenMaster.sys]

Hello,

The Nano and Fury-X look similar on paper but how they are setup is VERY different. To get them to work, you will have to place the Nano as master card and the Fury as slave. They driver more than likely is having issues with trying to match the cards since they have different clocks and power requirements. The Nano will not be able to keep up with the Fury, but they Fury can keep up with the Nano. The latest driver (22.6.1) should be more than enough to get them to work together. Due note, that if you intend to play anything that requires 12.1 feature set, you will have to use the "NimeZ" for GCN cards. Crossfire works but it takes effort in some games even before feature set 12.0...

I hate that crossfire and sli were abandoned. When it was done right, it did offer measurable differences that the "Steve's" never really cared to show.

View attachment 370964

View attachment 370963

Thanks for the advice, I'll definitely try this tomorrow.

Honestly, I find SLI and CF more of a novelty at this point. It's just fun to see what it can do, despite it's numerous flaws. I didn't originally intend on buying either of these to crossfire, in fact the nano has been sitting on my shelf collecting dust for awhile, but here I am.

I would like to put together an 1150 system with these cards (5775c calls my name), but all my haswell stuff is locked utilitarian boringness so I more or less cobbled this system together for the time being.

Hello,

The Nano and Fury-X look similar on paper but how they are setup is VERY different. To get them to work, you will have to place the Nano as master card and the Fury as slave. They driver more than likely is having issues with trying to match the cards since they have different clocks and power requirements. The Nano will not be able to keep up with the Fury, but they Fury can keep up with the Nano. The latest driver (22.6.1) should be more than enough to get them to work together. Due note, that if you intend to play anything that requires 12.1 feature set, you will have to use the "NimeZ" for GCN cards. Crossfire works but it takes effort in some games even before feature set 12.0...

I hate that crossfire and sli were abandoned. When it was done right, it did offer measurable differences that the "Steve's" never really cared to show.

View attachment 370964

View attachment 370963

Threw nano in the top slot and the fury x in the bottom slot. Still no dice. Installed latest driver, no dice. Option just isn't there.

I have a sleeper with a b350 that should support CF, may try it in there next and give up otherwise.

It's the z68.

Needs more power it keeps shutting off when I try and bench it. (Only the dell is connected). But CF works just fine here. Guess I just need to get a better board to run these.

 

[zuel_techno]

I am sorry that my advice did not work for you. Like I showed, I have two FuryX's working fine together on a Chinese X99 motherboard, Xeon E5-2678v3, and all the latest drivers on Windows 10. I did have an issue with a Machinist based X79 motherboard where I had to run the master card in third PCI-E x16 slot and the slave in the first slot. I had to connect the monitor to that second card. I would try that. Just plug into the second card and see of you get it working. Good luck.

 

[LabRat 891]

Went through this playing with several Vega 10 MI25s. Basically, CrossfireX support is 100% depreciated and not presenting in-driver anymore. If I forced it on, crashes galore.
Ended up finding an older AmernimeZone/R.ID driver release that 'worked' but other titles weren't playing nice. I ended up giving up and eventually upgraded to a 7900 GRE.


If you're determined, I'd probably try older drivers.

I am sorry that my advice did not work for you. Like I showed, I have two FuryX's working fine together on a Chinese X99 motherboard, Xeon E5-2678v3, and all the latest drivers on Windows 10. I did have an issue with a Machinist based X79 motherboard where I had to run the master card in third PCI-E x16 slot and the slave in the first slot. I had to connect the monitor to that second card. I would try that. Just plug into the second card and see of you get it working. Good luck.

I wonder if my 'configuration' was my issue. I had one card in the CPU-connected lanes, and the other over X570 chipset.

 

[RadFX]

I have a Asus Prime B-350 plus with a Pro Duo and the last and latest drivers for my Pro Duo (Fiji). I've never had issues with the Radeon sofware enabling crossfire alas it doesn't work in all games and sometimes takes some messing around with.

I did manage to beat my old max score in superposition.

 

[RyzenMaster.sys]

I am sorry that my advice did not work for you. Like I showed, I have two FuryX's working fine together on a Chinese X99 motherboard, Xeon E5-2678v3, and all the latest drivers on Windows 10. I did have an issue with a Machinist based X79 motherboard where I had to run the master card in third PCI-E x16 slot and the slave in the first slot. I had to connect the monitor to that second card. I would try that. Just plug into the second card and see of you get it working. Good luck.

I'm 99% sure it's a PCIe issue on that Z68. It's Pcie 2 limited to begin with, but for some reason it was only showing as x2 in GPUz on the secondary card. Could be that it was running in power saving mode. Oddly enough, even on the desktop in this PC it would routinely ramp usage of that card to max as indicated by the LEDs, fan would sing, then about a second later it would go back to idle. Not sure what the drivers were doing. Wonder if there was any Pcie bios settings I could have changed...

This reminds me I do have a Chinese X99 I got off of AliExpress a whole ago literally sitting in a drawer. It's one of the $35 with a 12 core included combos so the board is real potato and only has 1 x16 slot.

I nabbed an auction for a Z87 M Power and 4770k that I intend on running these cards in. Crossfire is supported there, as is Pcie 3.0. According to the specifications page it will be able to run 2 cards in x8 mode ea. I think I'll have a lot of fun ocing and benching this system. Just hope I don't jinx this into cf not working.

Went through this playing with several Vega 10 MI25s. Basically, CrossfireX support is 100% depreciated and not presenting in-driver anymore. If I forced it on, crashes galore.
Ended up finding an older AmernimeZone/R.ID driver release that 'worked' but other titles weren't playing nice. I ended up giving up and eventually upgraded to a 7900 GRE.


If you're determined, I'd probably try older drivers.


I wonder if my 'configuration' was my issue. I had one card in the CPU-connected lanes, and the other over X570 chipset.

Crossfire works perfectly fine on the Furys with the latest drivers using this MSI B350 Gaming Plus. I ran CF in Tomb raider 2013 as well as some synthetics, no issues. That PC has a 64gb SSD so I was a lil limited about what I could install on it tho.

I suspect it allocated 8 3.0 lanes to each just based on what am4 has available. GPUz shows x16 but that's... Impossible

 

[zuel_techno]

You could be right about the lanes. I did not think about that. I have my Fury's even though now, most games need 12.1 to even start. I did try the Nimez drivers and got some games like FirstD and others to run but.... It feels like its all on purpose. There is no reason for game developers to completely abandon this tech considering we are all about chiplets and core complexes these days. Even my system I am typing on now will run Windows 11 flawlessly but has been denied in favor of lower end systems.

 

[eidairaman1]

You could be right about the lanes. I did not think about that. I have my Fury's even though now, most games need 12.1 to even start. I did try the Nimez drivers and got some games like FirstD and others to run but.... It feels like its all on purpose. There is no reason for game developers to completely abandon this tech considering we are all about chiplets and core complexes these days. Even my system I am typing on now will run Windows 11 flawlessly but has been denied in favor of lower end systems.

View attachment 372159

The difficulty to make it run correctly became uneconomical for both to continue with it, it is why they pushed it on game comps to implement it. Also most users only have 1 gpu to begin with, call it a phase.