Sapphire Tri-X R9 290 turned into 290x with CF enabled?

[achocoolcho]

Has this happened to any tri-x r9 290 owners? I accidentally flashed one of my tri-x r9 290s with sapphire's reference r9 290 BIOS, then I flashed back the original Tri-X r9 290 BIOS. I also happened to update to newly released beta driver with Mantle before I discovered this.

So is it just some errors (I am guessing it is since bus width and bandwidth become very low but still interesting) or was my 290 really unlocked?

 

[GoogalyMoogaly]

Is this just because ULPS is still enabled and so the second card isn't reading properly?

 

[nicnik]

You mean you have 1 card, reflashed bio's and now it is showing you have a 2816 shaders and crossfire is enabled?

 

[achocoolcho]

Is this just because ULPS is still enabled and so the second card isn't reading properly?

ULPS is disabled via reg edit, and still reporting the same status. I am curious why it was reading 290x number of shaders and TOPs, if its just an improper reading, it could be any number right?

You mean you have 1 card, reflashed bio's and now it is showing you have a 2816 shaders and crossfire is enabled?

I have 2 290s, reflashed 1, and gpu-z showed one of them has 2816 shaders,
but when CF is disabled, both report 2560 shaders

 

[GoogalyMoogaly]

No idea then. I remember LtMatt having something similar happen, but I think that was caused by ULPS being enabled.

 

[aachil]

Hey i have a 290 tri x. Did urs unlock i want to do it aswell

 

[Doogles]

More than likely it is just a bug with GPU-Z I would imagine.

 

[aachil]

Hmm maybe ive not seen 1 tri x unlock

 

[gazzaman2k]

mine says the same so i flashed the sapphire 290x OC bios to it to get teh 1040mhz and works fine

 

[Orangey]

necroooooooo

 

[Type_R]

I had exactly the same happen when I added a Tri-X OC 290 in crossfire. One reported as a 290X but on further examination it's just a bug in GPU-Z. If you remove either card it will go back to normal 290 specs on GPU-Z

 

[LtMatt]

ULPS I'm afraid.