Sapphire Radeon R7 260X will not display

kissmekate

Reputable
Jul 16, 2014
11
0
4,510
I've recently purchased a new 650w PSU and a Sapphire Radeon R7 graphics card. I've reset the CMOS, updated the BIOS, uninstalled all old graphics drivers, installed the drivers that came with it and the ones from the Sapphire website, uninstalled all the graphics drivers again and installed ones from AMD that mentioned a known issue with some motherboards with AMD chipsets and still get nothing from the graphics card. The monitor doesn't detect any kind of signal from HDMI or DVI with the new card installed and it doesn't show up in the Windows dev manager. I've put the old card in and it works fine (not sure the make and model but it's old and pretty terrible and with no PSU connectors) so I don't think it's the PCI slot (there is only one PCIe x16 slot and I don't have another PC at home I can test it with). I've tried both 6 pin connectors from the PSU and with both the fan is spinning but nothing is displayed. I've also tried another monitor (different make and model) and swapped out all the cables.

I've read all the threads on here and various other forums that I could find mentioning this motherboard and/or this graphics card and haven't been able to find a solution.

Before exchanging it or getting a new card I'd like to know if there are any other suggestions that I can try. It's my husbands computer and the new PSU and card were birthday gifts and we're a couple weeks past his birthday now and he's getting pretty sad about not being able to play anything :-(

Graphics Card: Sapphire Radeon R7
Motherboard: Asus M4N68T-M V2
PSU: FSP Raider 650 Watt Power Supply
OS: Windows 7 64bit
(first time posting on here so please let me know if you need any other specs)

Thanks in advance!
 
Solution
well then, signs lead to a posible psu or gpu failure. your older gpu which doesnt require additional power works but 260x which requires a 6pin pcie power cable doesnt. 650w psu is more than enough for such system so you really need to test another one! however , there is a chance though 260x is the culprit but you need to test it.does gpu fan(s) spin or try to, while posting.?if yes then i suspect the psu, if not it is unclear and might be either one!
maybe you have to disable the intergrated grahics. at post, get into bios and on the graphic options change, from on-board to pcie, save changes and exit. from now on, monitor should receive signal from your new gpu! (ensure gpu is properly inserted in the slot)
 

kissmekate

Reputable
Jul 16, 2014
11
0
4,510


Hey Chris,
Sorry, I meant to include that in my original post. The board doesn't let you turn off the onboard from BIOS, only allows you to set the priority of the display adapters, which is set to the PCI-E first.

I was worried that it was just the board not fitting properly, there is a capacitor that looks like it might be in the way but upon close inspection with a flashlight and one of us holding the case up while the other looked there is nothing blocking it from sitting in the slot properly and I can hear it click into place :-(
 
well then, signs lead to a posible psu or gpu failure. your older gpu which doesnt require additional power works but 260x which requires a 6pin pcie power cable doesnt. 650w psu is more than enough for such system so you really need to test another one! however , there is a chance though 260x is the culprit but you need to test it.does gpu fan(s) spin or try to, while posting.?if yes then i suspect the psu, if not it is unclear and might be either one!
 
Solution

kissmekate

Reputable
Jul 16, 2014
11
0
4,510


Thanks again! Yeah, the GPU fan spin perfectly fine. His old PSU was causing surges to the mob so I don't want to try it with that and I don't have another PC at home to test it with. I've called a shop near us and they'll test it in another machine tomorrow (and/or in his machine with a diff PSU) for free for us so hopefully they can give us an answer.
 

kissmekate

Reputable
Jul 16, 2014
11
0
4,510
Just for the sake of tying I updated the drivers one more time and (by a fluke I think) it worked! After another reboot though it stopped working and I'm getting an AMD/Catalyst error message though. Opening a new thread for that. Thanks for your help Chris!
 


you are welcome and dont worry, a driver issue is more easily delt!