|
X370 Taichi Crossfire Issue |
Post Reply 
|
Page 12> |
| Author | |
mysticjbyrd 
Newbie 
Joined: 27 Mar 2017 Location: USA Status: Offline Points: 36 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: X370 Taichi Crossfire IssuePosted: 17 Apr 2017 at 4:39am |
|
I had a 470 laying around, and I put it into my system. I now have a 480 and 470 in xfire, and I didn't have any issues. I know this isn't terribly helpful, but I thought you might want to know it's working for others.
I am using bios version 2.0. EDIT: Solved. That's good. Edited by mysticjbyrd - 17 Apr 2017 at 4:41am |
|
|
Is "God" able, but not willing to stop evil? Then he is malevolent.
Is he both able and willing? Then whence cometh evil? Is he neither able nor willing? Then why call him God??? ??Epicurus |
|
 |
|
|
clubfoot
Newbie
Joined: 28 Mar 2016 Location: Canada Status: Offline Points: 246 |
Post Options
Thanks(0)
Quote Reply
Posted: 17 Apr 2017 at 2:13am |
|
Excellent!
 Just an FYI, I also found the upgrade method worked better than the clean install of 1703. Because weirdly it changed my Windows version from Pro to Enterprise  |
|
|
|
|
|
|
TooQik
Newbie
Joined: 06 Apr 2017 Location: Australia Status: Offline Points: 104 |
Post Options
Thanks(0)
Quote Reply
Posted: 16 Apr 2017 at 9:21pm |
|
Hi clubfoot, thanks for the suggestion. I haven't actually tried a CMOS clear at this stage but I'll hold off trying this as the issue appears to now be resolved. I've just finished updating Windows 10 to the new 1703 version. After this update I've been able to restart my PC ten times in a row without either Crossfire disabling or an empty blue screen with mouse pointer at the login appearing, so it seems promising at this point. I'll keep an eye on things and update this thread again if I strike any further issues. Edited by TooQik - 16 Apr 2017 at 9:22pm |
|
|
|
|
clubfoot
Newbie
Joined: 28 Mar 2016 Location: Canada Status: Offline Points: 246 |
Post Options
Thanks(1)
Quote Reply
Posted: 16 Apr 2017 at 8:44pm |
|
|
|
|
|
|
TooQik
Newbie
Joined: 06 Apr 2017 Location: Australia Status: Offline Points: 104 |
Post Options
Thanks(0)
Quote Reply
Posted: 16 Apr 2017 at 9:10am |
|
Well, tried reinstalling Windows and this makes no difference either.
I'm currently at a loss as to what to try next so any/all suggestions welcome. |
|
|
|
|
TooQik
Newbie
Joined: 06 Apr 2017 Location: Australia Status: Offline Points: 104 |
Post Options
Thanks(0)
Quote Reply
Posted: 12 Apr 2017 at 10:26am |
Tried both the 1x16 and 2x8 options for the PCIe configuration on the 1.60 BIOS and it made no difference. The PCIe switch option is no longer available on the 2.0 BIOS though. I've also tried disabling ULPS in the Windows registry. This improved the situation some what in that I now have less frequent blue screens where the Windows login screen would normally appear but crossfire is still disabling itself on consecutive successful Windows boots. I still haven't tried a Windows reinstall, I'll attempt this on the coming Easter weekend. Edited by TooQik - 12 Apr 2017 at 10:32am |
|
|
|
|
TooQik
Newbie
Joined: 06 Apr 2017 Location: Australia Status: Offline Points: 104 |
Post Options
Thanks(0)
Quote Reply
Posted: 12 Apr 2017 at 10:23am |
Cheers for the info. GPU-Z will let you check the current crossfire status, as will AMD Radeon Settings. |
|
|
|
|
datonyb
Senior Member 
Joined: 11 Apr 2017 Location: London U.K. Status: Offline Points: 3139 |
Post Options
Thanks(1)
Quote Reply
Posted: 11 Apr 2017 at 11:23pm |
|
|
|
JoJoDaClown
Newbie
Joined: 10 Mar 2017 Status: Offline Points: 14 |
Post Options
Thanks(1)
Quote Reply
Posted: 11 Apr 2017 at 10:24pm |
|
I'm running MSI 7950's, Win 10, and currently BIOS 2.0, but my crossfire was working on 1.4 when I started the system up the first time. I'll have to take a closer look at my system to confirm crossfire is working as intended. My PC works fine and gaming fine, but I haven't verified the 2nd GPU is listed as enabled and crossfire enabled. I'll have to think of a crossfire friendly game and try it out. |
|
|
Ryzen 1800X
ASRock X370 Taichi GSkill TridentZ CL14 3200 |
|
|
|
|
TooQik
Newbie
Joined: 06 Apr 2017 Location: Australia Status: Offline Points: 104 |
Post Options
Thanks(0)
Quote Reply
Posted: 11 Apr 2017 at 10:00am |
|
Thanks for the feedback JoJo.
It's great to know that someone else is running Crossfire on this board and it's working as expected. May I ask what GPUs , BIOS version and OS you're using? To answer your questions, I checked the BIOS for both PCIe and Crossfire settings in both the 1.60 and 2.0 BIOS versions when troubleshooting the issue but any changes I made seemed to have zero affect; currently everything is set to Auto. It's worth noting that some of the PCIe configuration has been removed from the 2.0 BIOS. The Crossfire ribbon cable is installed. I've even tried different cables in case I was having a cable issue but this makes no difference. Definitely didn't install the SLI bridge. I'm running a single monitor and have it connected to the first GPU ie PCIe2. Power connections to both GPUs are definitely connected and working. Currently I've removed the second GPU to allow the system to behave normally. I'm leaning towards reinstalling Windows again to see this fixes the issue, but at this stage I'm at a loss as to what is causing the problem. |
|
|
|
|
Post Reply
|
Page 12> |
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
Topic Options
clubfoot wrote: