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

AMD Gimping HBM clock on Fiji after v16.12.2 WHQL driver

WeSbO said:
To make sure I've understood correctly. So when you use a modded bios on Fiji, with oc'ed HBM, those HBM speeds are not taken into account on new drivers, at it runs at stock HBM speeds ?
Click to expand...

Hopefully you aren't about to say something negative about this on a forum listed as 'overclockers', sells permanently modified chips (removed IHS for example), sells chips beyond spec, offers modified custom watercooled cards.....

This is EXACTLY the reason people like Daniel K came around reworked Creative's drivers to put features back in that had been removed and that pretty much forced Creative to add those features back in.
 
WeSbO said:
To make sure I've understood correctly. So when you use a modded bios on Fiji, with oc'ed HBM, those HBM speeds are not taken into account on new drivers, at it runs at stock HBM speeds ?
Click to expand...

Yes.

AMD driver panel will show clock is say xxxMHz HBM.

GPU-Z, etc will state it is xxxMHz.

But I do not get the performance of xxxMHz HBM.

I get performance as if card is at HBM 500MHz (ie stock).

Same OS, FW, etc and I revert to v16.12.2 WHQL or earlier driver and I have:-

i) read back from driver, GPU-Z of HBM xxxMHz

ii) I have performance of HBM xxxMHz
 
Last edited:
Damn didn't know that, sure a crappy move, now it's one thing for "overdrive"/"wattdude" not to support HBM overclocking, which I don't have a problem with but it's another thing to lock out VBIOS clocks, what does it matter to AMD if you use a modded bios, it voids the warranty anyways. Crazy.

Oh and I agree with you gupsterg, that Fiji didn't benefit from any of that FineWine, and the feature support was subpar as well, new features not being supported on release of these said features even though it was the flagship GPU, but i'm not surprised the GPU didn't sell that well so they didn't want to put resources in software development... Not saying it's the right thing to do, just not surprised. So Vega users beware, the same thing could happen if that GPU is not a bestseller, it won't get as much love...
 
AMDMatt said:
Thankfully overclocking is supported and quite capable on Vega and HBM2.
Click to expand...

Yeah but at those prices, with that power draw, a 1080ti is a no brainer. I wanted Vega, especially that glorious limited edition version, to compliment my Ryzen cpu. But basically no choice but to go nvidia with how things are now.
 
AMDMatt said:
I've passed it on before. HBM overclocking was never officially supported on Fiji so we are not going to add support for it now, either via a Bios modification or via drivers.
Click to expand...

You again miss the point.

Let me say it clearly.

I do not want AMD to make OverDrive or Wattman to support HBM overclocking.

I do not want AMD to give documentation or support of VBIOS modding.

I want AMD driver from v17.x.x not to block a HBM clock change. And so do other Fiji owners who are aware of issue.

I can show you results from drivers from ~ June 2015 to ~ Jan 17 giving me performance gain from HBM clock change.

So why block it in v17.x.x drivers? The card is no longer even in retail supply chain.
 
Zeed said:
It was working on 16.x and its blocked on 17.x drivers ... Guess sticking to 16.x drivers if on FuryX and overclocking :p
Click to expand...

Yes :p .

The pain of it is that let's say your on W10C. Even if I change group policy not to update drivers it can sometimes down newer v17.x.x drivers and then I have to remove and roll back.

I hate W10C, thankfully. So I use W7 90% of the time, thankfully that does not at least kill the drivers.

TBH W7 benches so much better than W10. The case is far more apparent on Ryzen than when on Intel as well.

WeSbO said:
Damn didn't know that, sure a crappy move, now it's one thing for "overdrive"/"wattdude" not to support HBM overclocking, which I don't have a problem with but it's another thing to lock out VBIOS clocks, what does it matter to AMD if you use a modded bios, it voids the warranty anyways. Crazy.
Click to expand...

Totally agree. I wish AMD Matt would acknowledge this. Even if he can not do anything even an acknowledgment would less the insulting injury by AMD.

WeSbO said:
Oh and I agree with you gupsterg, that Fiji didn't benefit from any of that FineWine, and the feature support was subpar as well, new features not being supported on release of these said features even though it was the flagship GPU, but i'm not surprised the GPU didn't sell that well so they didn't want to put resources in software development... Not saying it's the right thing to do, just not surprised. So Vega users beware, the same thing could happen if that GPU is not a bestseller, it won't get as much love...
Click to expand...

Totally.

IMO Hawaii saw decent gains over the course of it's term and it was a lengthy one. Fiji has been a let down in this aspect. Polaris has been the main focus IMO.

There are plenty of Hawaii and Grenada owners posts on r/AMD and other forums where they state later drivers are borked for them as well.

Scougar said:
I know you are just the messenger on this on, but the fury was the top previous gen card, this is pretty poor form.
Click to expand...

Total failure from AMD driver team IMO.

prjwebb said:
Hahaha, seems I got rid of my Fury and went green at the right time.


prjwebb said:
Yeah but at those prices, with that power draw, a 1080ti is a no brainer. I wanted Vega, especially that glorious limited edition version, to compliment my Ryzen cpu. But basically no choice but to go nvidia with how things are now.
Click to expand...
Click to expand...

I agree I feel compelled to rebel over to green.

I have had AMD GPU for ~10yrs now. Yeah I have had Intel CPU since 2007, but I have now owned 2x R7 1700, have 3rd with me now R7 1700 and R7 1800X. I also just got TR.

AMDMatt said:
Thankfully overclocking is supported and quite capable on Vega and HBM2.
Click to expand...

Seems to me as 2017 onwards driver is the issue and VEGA has been released this year perhaps it's a tactic by AMD?

The faith in good support from AMD driver team has really taken a beating for me and other Fiji owners TBH. Perhaps from that experience we don't want VEGA?
 
Last edited:
Well it's quite simple if AMD keep going down the route they have been taking for the past 2 years, they won't be selling dGPUs in less than a decade.
At this point I think it would benefit consumers in the long run if AMD GPU division was bought by a company with funds to put into r&d and software development...
But there aren't really any companies that want to go in to the dGPU business because of the hassle in the software dev department... I mean there are big enough companies in the sector who have more than enough funds to develop dGPUs but they aren't
 
AMDMatt said:
I've passed it on before. HBM overclocking was never officially supported on Fiji so we are not going to add support for it now, either via a Bios modification or via drivers.
Click to expand...
As said, it's clear that AMD isn't going to start supporting it, but not actively seeking to disable it is a different matter. If appears that effort was put in to stop this, but it's also possible it was an unintended consequence of another change, and then I can see that it's just what it is and we accept it.
 
arby1 said:
As said, it's clear that AMD isn't going to start supporting it, but not actively seeking to disable it is a different matter. If appears that effort was put in to stop this, but it's also possible it was an unintended consequence of another change, and then I can see that it's just what it is and we accept it.
Click to expand...

Are you trying to be reasonable.

It's clear that AMD put out a driver to rob gupsterg of that last 155MHz overclock on the memory.

Doesn't matter why or that it was never officially supported or that a 3rd party program was needed, AMD engineers should be at work right now to support the overclocking they didn't support.

Or else the conspiracy drama will continue.
 
1145 545 v16.12.2 WHQL rerun tonight.

z2LIH4p.jpg

Same VBIOS v16.3.2 WHQL.

V8ltq6h.jpg

From zip in OP. 1145 600 v17.8.1.

jv1DoR7.jpg

From zip on OP. 1145 700 v17.8.1.

58zNSga.jpg

1145 545 v16.12.2 Memory Copy = 391363 MB/s

1145 545 v16.3.2 Memory Copy = 385995 MB/s

1145 600 v17.8.1 Memory Copy = 352027 MB/s

1145 700 v17.8.1 Memory Copy = 351135 MB/s

Will test some other older drivers tomorrow.
 
Having been using AMD cards since like forever, rage fury maxx and on with only one hick-up along the way, it's this sort of thing and the mess that was the polaris and vega graphics cards under delivering, was an early adopter for pretty much all ati and amd graphics cards but the past 2 generations have been a complete let down, as was the fury x "being touted" as the overclockers dream which it most certainly was not.
 
gupsterg said:
1145 545 v16.12.2 WHQL rerun tonight.

z2LIH4p.jpg

Same VBIOS v16.3.2 WHQL.

V8ltq6h.jpg

From zip in OP. 1145 600 v17.8.1.

jv1DoR7.jpg

From zip on OP. 1145 700 v17.8.1.

58zNSga.jpg

1145 545 v16.12.2 Memory Copy = 391363 MB/s

1145 545 v16.3.2 Memory Copy = 385995 MB/s

1145 600 v17.8.1 Memory Copy = 352027 MB/s

1145 700 v17.8.1 Memory Copy = 351135 MB/s

Will test some other older drivers tomorrow.
Click to expand...
What Is the 700mhz v16 memory copy speed?
 
You must log in or register to reply here.
Back
Top Bottom