AMD Releases PCI-Express Power Draw Fix, We Tested, Confirmed, Works

[xkm1948]

I am having stability issue with this new driver on FuryX. 1100 OC is no longer stable no matter what amount of vcore offset is applied now. Played CSGO for 30mins and it crashed on me which have not happened since launch driver. Lower down to 1075OC and it still would crash. It can't even pass the 3DMark FireStrike Stress test now. I use DDU between all of my driver installations so it is definitely not the problem of driver files conflict. Reverted back 16.6.1 and everything is back to normal. Passed 100 loops of FSE Stress test at 99.5% for 1100 OC.

Very likely RTG is focusing on 480 driver now and somehow messed up driver support for previous gen cards. Guess I will just wait until a newer driver that does not solely focus on RX480 then.

And yes I have already submitted the problem to RTG.

 

[xkm1948]

That would make more sense, 40A*1.5V is 60W. If that's a 125°C rating, at lower temperatures we can still be talking around 80-100W. That's still huge.

@Shamalamadingdong
Yeah, I'm aware of the risks, but that applies to every overclock. Still, the headroom can be a lot higher than around 150W as initially thought. If user has PSU powerful enough to feed 6pin, VRM is there to deliver it if needed. Far beyond the original specs. Meaning AIB's only have to slam better cooling on reference design. They don't even have to redesign PCB and components on it to gain headroom.

Gusteberg over OCN is working on editing RX480 BIOS for increased power limit. With all power limit removed and heat factor dealt with the card should run 1.4GHz to 1.5GHz easily.

 

[$ReaPeR$]

I am having stability issue with this new driver on FuryX. 1100 OC is no longer stable no matter what amount of vcore offset is applied now. Played CSGO for 30mins and it crashed on me which have not happened since launch driver. Lower down to 1075OC and it still would crash. It can't even pass the 3DMark FireStrike Stress test now. I use DDU between all of my driver installations so it is definitely not the problem of driver files conflict. Reverted back 16.6.1 and everything is back to normal. Passed 100 loops of FSE Stress test at 99.5% for 1100 OC.

Very likely RTG is focusing on 480 driver now and somehow messed up driver support for previous gen cards. Guess I will just wait until a newer driver that does not solely focus on RX480 then.

And yes I have already submitted the problem to RTG.

damn! with their budget though i dont think they can "multitask" that much..

 

[xkm1948]

damn! with their budget though i dont think they can "multitask" that much..

Good thing is there are nothing new I needed from 16.7.1 at this moment. I thought FuryX would get the Wattman but nope. Oh well, I can work with traiditional way of OC.

 

[GhostRyder]

I am having stability issue with this new driver on FuryX. 1100 OC is no longer stable no matter what amount of vcore offset is applied now. Played CSGO for 30mins and it crashed on me which have not happened since launch driver. Lower down to 1075OC and it still would crash. It can't even pass the 3DMark FireStrike Stress test now. I use DDU between all of my driver installations so it is definitely not the problem of driver files conflict. Reverted back 16.6.1 and everything is back to normal. Passed 100 loops of FSE Stress test at 99.5% for 1100 OC.

Very likely RTG is focusing on 480 driver now and somehow messed up driver support for previous gen cards. Guess I will just wait until a newer driver that does not solely focus on RX480 then.

And yes I have already submitted the problem to RTG.

That's unfortunate, it didn't effect my 290X's and their overclocking. I tested it with some BF4 last night and no problems with same settings though I don't see anything that I gained either so probably could have not downloaded it.

 

[$ReaPeR$]

Good thing is there are nothing new I needed from 16.7.1 at this moment. I thought FuryX would get the Wattman but nope. Oh well, I can work with traiditional way of OC.

cool, you look like you know your stuff anyway..

 

[cdawall]

mb don't have built in a current limiter and any consumer attached to it can draw more till something is kaboom

Depends on board I have more than one high end board that allowed per slot wattage limits. Most of which I could go as high as 150w...

 

[HD64G]

well thats very neat.
So it actually works and the performance does not suffer

Nice job AMD.

@tPU and chance of running a few more games to see how they react?

Almost sure that for the next GPU review (custom RX480 probably) W1z will test them with Crimson 14.7.1 as he always does

 

[laszlo]

So, all phases can churn out 240W theoretical load and realistic max being 120W on 6pin phases and 75W on PCIe phases. That's still 195W which ain't that bad, giving some headroom. If you can cool it well enough.

you understood wrong.... 6 pin isn't max out with 120w...can deliver min. 150w....if psu rail have juice...

 

[RejZoR]

I know that, I was talking based on what phases can actually deliver. If 3 phases are dedicated to 6pin and each is 40W, then that's 120W. But someone later clarified it's 40A and not 40W...

 

[Agiels]

so is a driver or what ?? i was having big peaks of current in my r9 280, maybe it got fixed for me too ?

 

[RejZoR]

so is a driver or what ?? i was having big peaks of current in my r9 280, maybe it got fixed for me too ?

Very unlikely since this is RX480 specific control of it's VRM segment. I very much doubt they'd somehow change old R9 280 as well with it.

 

[Agiels]

damn it, i think my PSU its failing to hold my system, i will get a EVGA Supernova 750W or a CX750M ...

 

[RejZoR]

damn! with their budget though i dont think they can "multitask" that much..

Still, Fury X is still their current flagship. It deserves same attention as new RX generation. @xkm1948 send a bug report to AMD.

 

[xkm1948]

Still, Fury X is still their current flagship. It deserves same attention as new RX generation. @xkm1948 send a bug report to AMD.

Read my thread dude, already sent. Thanks for the tag though.

I don't buy cards for showing epen. I use them for work and entertainment. So far my FuryX has been more than awesome for VR as well as OpenCL computing.

Going back to Nekopalive now.

 

[Agiels]

cant be more agree with you, for me no company is better than the other, i focus on costs and perfomance, no of those companys will give you a damn product for free, they will preffer to have ur blood first !

for what i see, nVidia is always more spensive than AMD at the same level of performance, atleast here in Cuba it this, for example, GTX960 here cost around 250/270$ at that same price tag and more performance i will neve buy that above an r9 280x (220$) or a r9 380x (270$)

 

[buildzoid]

Turns out I messed up the current rating at 125C. The RX 480 Vcore VRM is 6 phases composed of a MDU1514 high side FET and an MDU1511 low side FET. The MDU 1514 has a continuous drain current of 66A @ 25C case temperature and just under 30A at 125C. It has a pulsed current rating of 100A however the pulse duration or frequency isn't specified so it's not all that useful . The low side MDU1511 has a continuous drain current of 100A at 25C case temperature and goes down to about 66A at 125C. So the low side of the VRM can handle 396A of current at 125C and the high side should be able to keep up with that depending on the duty cycle. A 100% safe rating for the high side is 180A @125C at any core voltage setting. Realisticly the VRM shouldn't get anywhere near that hot and you will have a lot more current to play with on both the high and low sides.

 

[$ReaPeR$]

they really should focus on the boot issue with high refresh rate using dvi, multi high refresh monitors increased power draw and displayport incompatibility with htc vive, but i guess any amd fault to bash is better than admitting nvidia has any

i didnt know about these problems, could you care to post some links please?

 

[cdawall]

I don't understand why people care so much about brand if it works it works if it doesn't it doesn't. Both companies have released junk for whatever reason. Move on.

i didnt know about these problems, could you care to post some links please?

Can you use google?

https://www.techpowerup.com/223669/geforce-gtx-pascal-faces-high-dvi-pixel-clock-booting-problems

http://www.tomshardware.com/news/nvidia-vive-displayport-incompatible,32204.html

 

[Frick]

There's a word for people stamping degrading titels on others without knowing the person in question: People stampting degrading titles to others sans knowing the persons they apply the stampt upon. And it's always ugly, on so many levels.

 

[cadaveca]

Since this option was a function of the VRM controller, I was really surprised AMD didn't do this from the start, especially considering that it barely affects performance.

Nice to see compatibility mode for those users with older(within limits) PSU/mobo combos can safely add in multiple 480s, too.

However, If I was AMD, I would have had these things ready at the launch and advertised them as features to boost up the bullet points and bring in more consumer confidence. Hopefully future releases will take this situation as a consideration and they'll put it to good use. Sad to see hardware released that doesn't take advantage of all it has to offer; excellent to see it used properly so quickly.

 

[$ReaPeR$]

Since this option was a function of the VRM controller, I was really surprised AMD didn't do this from the start, especially considering that it barely affects performance.

Nice to see compatibility mode for those users with older(within limits) PSU/mobo combos can safely add in multiple 480s, too.

However, If I was AMD, I would have had these things ready at the launch and advertised them as features to boost up the bullet points and bring in more consumer confidence. Hopefully future releases will take this situation as a consideration and they'll put it to good use. Sad to see hardware released that doesn't take advantage of all it has to offer; excellent to see it used properly so quickly.

that was their stupidity.. the whole problem could be avoided so easily.. i really cant get amd sometimes..

 

[W1zzard]

Since this option was a function of the VRM controller, I was really surprised AMD didn't do this from the start, especially considering that it barely affects performance.

Nice to see compatibility mode for those users with older(within limits) PSU/mobo combos can safely add in multiple 480s, too.

However, If I was AMD, I would have had these things ready at the launch and advertised them as features to boost up the bullet points and bring in more consumer confidence. Hopefully future releases will take this situation as a consideration and they'll put it to good use. Sad to see hardware released that doesn't take advantage of all it has to offer; excellent to see it used properly so quickly.

They could have just connected one more phase to the 6-pin, instead of 50/50, very easy to do during board design stage.

 

[cadaveca]

They could have just connected one more phase to the 6-pin, instead of 50/50, very easy to do during board design stage.

But that might have given the potential for higher clocking and cannibalized a future SKU.

 

[AsRock]

Thanks W1zzard for putting the time and effort in to this.