• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

HIS R9 290 overclocked to 290X problem

Cat_In_Pyjamas

Cat_In_Pyjamas

Cat_In_Pyjamas

Associate
Joined
4 Mar 2006
Posts
1,063
Location
Macc
Hi guys,

I've tried tech support already but on the off chance someone else stumbled on this problem and found a solution I'll ask here as well.

Recently I got myself the HIS R9 290 overclocked to 290X card together with the "FX8 SPEC OPS" AMD FX-8 8350 @ 4.6GHz Overclocked Gaming PC Bundle and found a problem where the graphics card doesn't get picked up by any monitor I have available to me (the card is running as evidenced by the spinning fan). At the same time my old AMD 6970 works perfectly fine. Before someone asks - I'm running a 1000W PSU so not an issue there.
I tried updating bios to the latest version (2104 for win 8.1 64bit), downloaded the latest ASUS driver suite as well as the latest AMD 290 series drivers, removed the overclock on the CPU in case that was causing the issue as well. None of this seems to be working. At the same time when the card was originally RMA'd Overclockers found it to be working on their end, so there is obviously some issue between the card and the motherboard.
If anyone has any other suggestions to try I'm all ears, otherwise I'll have to send the card back for a refund and hope the mobo works with other latest gen cards.
 
Unusual, the spec ops bundle shows a sabertooth mobo
I have recently bobbed the HIS 290 to 290x flashed into my housemates comp.
He uses an 8320 on a sabertooth r2.0 with no issues but an older bios (also win8.1).

is your board a 2.0?

dhtDBm1.png
 
I'll throw in an update as I tried something different - connected the card to my old mobo and lo and behold it works fine there. So in short - new mobo works with my old 6970 and old mobo works with r9 920. If anyone has any ideas I'm all ears =/.
 
Final update on this issue. Catalyst 13.11 drivers kind of resolved the issue in the way that I'd get image after around 30 seconds - 1 minute and only once windows loaded up (that's only using HDMI cable, DVI remained non-responsive). However soon as I logged into any user profile and processes started loading up, the system would freeze up (only switching the PC off through the power button did anything - not even the reset button responded).
This made me adapt a different approach, I set the system to a clean start and downloaded catalyst 13.12 drivers. Since then, with only catalyst suite and my antivirus loading on start up there is no freezing issue and I get image on both HDMI and DVI connections, HOWEVER regardless of which connection I use I can never get any image in the bios (it only appears soon as windows boots up).
I'll stick to that for now and hope that eventually there will be an update that lets me access the bios, but in the mean time if anyone else has issues similar to mine I hope my experience helps them out.
 
As in device boot priority (as I remember no other option that would allow this)? I tried it before and it hasn't worked but that was with the old drivers. I'll give it a shot again, but I don't hold my hopes up.

There are only three options in the bios that I see relating to the PCI-E device:
the frequency
the boot priority
the driver chose on boot from the device

Changed the option on both the boot priority and the driver but that has no effect on the card remaining switched off prior to the OS loading up.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom