• 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.

Why is AMD quiet about black screens on 290x?

SD would have been a good/better title in regards to bandwith comparisons using the more demanding title that is SD, it's a killer of a BM if not the best gaming BM to check for stability with overclocks, it sorts out unstable oc's, if it can handle SD, you can bet your oc is 100% stable not to mention there is large performance gains to be had with vram oc'ing.

I guess Kap didn't find it worthy of his attention at the time.:cool:

Or, he simply didn't feel it was a fair comparison as it shows up the weaker original bandwidth neutered Keplers, idk.:p
 
SD would have been a good/better title in regards to bandwith comparisons using the more demanding title that is SD, it's a killer of a BM if not the best gaming BM to check for stability with overclocks, it sorts out unstable oc's, if it can handle SD, you can bet your oc is 100% stable not to mention there is large performance gains to be had with vram oc'ing.

I guess Kap didn't find it worthy of his attention at the time.:cool:

Or, he simply didn't feel it was a fair comparison as it shows up the weaker original bandwidth neutered Keplers, idk.:p

With more than two cards the SD benchmark is not a lot of fun as it is either capped or you get a huge CPU bottleneck.

The fastest entry on there is a couple of old kepler based cards and they are not even GK110 based lol.

http://forums.overclockers.co.uk/showpost.php?p=24808741&postcount=2

Once my 290Xs are on water I will be revisiting the SD benchmark though.:D
 
Downloading Sleeping Dogs onto my 290X system at the moment.

I am going to give it a quick run before I put the waterblocks on.

Anyone want to predict how many fps I will get

Here is my prediction for all four cards.

170fps
 
187fps Kaaps :)

Just run it.

146.1 @stock or overclocked.

This game is very CPU limited by the look of it as it makes no difference if I overclock the cards or not.

Even my GTX 690s did better as the CPU only has to deal with two cards.

When I upped the resolution to 1600p the 290Xs did a lot better scoring 138fps showing that the CPU is bottlenecking the cards @1080p
 
Finally got my money back for my R9 290, took a week to send it and a week for them to test it. They said it was faulty, not going to touch AMD for awhile I am very happy with my 780 now.
 
Oh yeah... :(

I'll try to get the voltage bump as low as possible, otherwise I guess I'll just have to try putting this through an RMA, thanks for your help folks.

Managed to get the voltage bump down to +30. Tried an OC at the same time as I figured if I was increasing the voltage then I may as well OC it and got 1100MHz Core and 1450MHz Mem (5200MHz Effective), so I'm happy with that.
 
Last edited:
Just run it.

146.1 @stock or overclocked.

This game is very CPU limited by the look of it as it makes no difference if I overclock the cards or not.

Even my GTX 690s did better as the CPU only has to deal with two cards.

When I upped the resolution to 1600p the 290Xs did a lot better scoring 138fps showing that the CPU is bottlenecking the cards @1080p

I am not surprised that it brings a CPU bottleneck on your 4x290X's Kaap and I imagine most optimised games would. I bet it was smoother than your 690's though?
 
I am not surprised that it brings a CPU bottleneck on your 4x290X's Kaap and I imagine most optimised games would. I bet it was smoother than your 690's though?

It seems to run best on the GTX 690s when using 4 GPUs, check the minimums out in the bench thread. The 690s minimums are twice as good as the 290Xs or Titans. As to smoothness using 4 GPUs, it is hard to split the Titans or 690s.
 
Just run it.

146.1 @stock or overclocked.

This game is very CPU limited by the look of it as it makes no difference if I overclock the cards or not.

Even my GTX 690s did better as the CPU only has to deal with two cards.

When I upped the resolution to 1600p the 290Xs did a lot better scoring 138fps showing that the CPU is bottlenecking the cards @1080p

I guess it would yeah as you're reducing load on the PCI bus. Still that's impressive as hell for those cards. Can't think of a GPU you could extract better / longer use out of :).
 
It seems to run best on the GTX 690s when using 4 GPUs, check the minimums out in the bench thread. The 690s minimums are twice as good as the 290Xs or Titans. As to smoothness using 4 GPUs, it is hard to split the Titans or 690s.

Impressive for such a 'Pre-Dinosaur' card. I thought the Titan was getting on now but the 690 still rocking and rolling :)
 
I have Sapphire Tri-X R9 290X and I'm getting Blue screens with no writing but with some glitches while watching videos on web sites (chrome browser). It may be related to Trixx software bc when I close it, videos play normally and pc don't crash. But what happens is as follows: Video slows down first, then screen goes black except for mouse icon and waiting wheel turning, it seems as windows tries to restart the display bc when I move the mouse it sutteringly moves but like every 2-3 seconds, and then it just all goes blue with glitches near the bottom of screen in some lighter blue tints. I am forced to restart the machine. As I said when I close Trixx it didn't crashed or BSOD but I'm not sure if it really is the cause or not. Is there a chance I got a bad card?
 
I have Sapphire Tri-X R9 290X and I'm getting Blue screens with no writing but with some glitches while watching videos on web sites (chrome browser). It may be related to Trixx software bc when I close it, videos play normally and pc don't crash. But what happens is as follows: Video slows down first, then screen goes black except for mouse icon and waiting wheel turning, it seems as windows tries to restart the display bc when I move the mouse it sutteringly moves but like every 2-3 seconds, and then it just all goes blue with glitches near the bottom of screen in some lighter blue tints. I am forced to restart the machine. As I said when I close Trixx it didn't crashed or BSOD but I'm not sure if it really is the cause or not. Is there a chance I got a bad card?

I was getting a black screen on my Sapphire Tri-x 290, resolved it by upping the core voltage by +30.

Although OcUK told me to wait for new drivers before I RMA it.
 
@Marine. But at 1080 even if you get 2000mhz mem clock which is impossible without burning the card, the fps you get will be the same. Memory size affects the resolution scale and memory clock fps performance at that resolution also apparently for a 512 bit bus memory to be saturated completely you need a 4k display. With the 1080p and 1440p on 512 bit bus you dont ever gonna need oc the memory.
Not on Metro2033 it's not...which is one of the game I saved for playing after upgrading my graphic card. Overclocking the memory clock alone can easily bump my frame rate from 42fps to 45fps in game, and the problem is I can't maintain the memory clock without getting black screen.

To be honest, while I myself have suggested to many others to lower the memory clock if they get black screen, but while it can "get round" the problem, there's still no confirmation of whether the "black screen behavior itself is a fault", since there are many people actually to get memory clock all the way up to 1600MHz+ without a single black screen. I mean in the pass when overclocking memory clock too high, the error would usually only occur in the form of artifacts or tearing being displayed on screen, but this black screen issue seem to be unique to the Hawaii cards...it's just one minute it's fine, the next without and warning it just go black and lock-up the PC.

The fault could well down to the power-delivery or management of the card. I mean if I get tearing and artifact for memory clock being clock to high I can understand and accept that as normal (as they are standard errors for clocking graphic memory clock too high), but black screen simply doesn't seem "normal". I came to the conclusion that high memory clock "contribute" toward the likely occurrence of black screen, but I still think AMD need to step up and confirm what's the fundamental causes/reasons for these black screen to happen.
 
Back
Top Bottom