Amd Vulkan beta driver & Fah

[DarkFoss]

So far these drivers are amazing on my Fury X's . I typically run non crossfired so I can fold on the second Fury non stop and game simultaneously. 100% gpu load no more constant reclocking according to gpu-z previous drivers would downclock every 20-40 seconds gaming or not. I used to use DDU for a clean install for every release but recently I went back to the 15.11 and let the AMD installer upgrade each version of the driver.
One note do not attempt running a game in Mantle mode while folding unless you like bluescreens haven't tested it with this driver and not going to
http://support.amd.com/en-us/kb-article ... -Beta.aspx

[JonasTheMovie]

Tonight I installed the Vulkan beta midWU and can confirm that it is an improvement so far. You can see in the log how load stays on 100%, a big difference there.
FAHclient reports expected ppd of 370k instead of the 310k I believe I read before pausing, but that is still to be confirmed over time.

[Sven]

Installed the first Beta-Vulcan Driver 16.3 for my two R9 290X and one Fury X.

I too can confirm, it's a huge improvement in performance for both.

My Fury X jumped from average of 300'000PPD to 370'000PPD, and the R9 290X from 275'000 to 320'000PPD with Core21 units.

[DarkFoss]

Thanks for the feedback on the 16.3 drivers sven. Initially I blew them off.
I did a clean install of them after installing all my Windows updates. At first they didn't seem any different from the previous Vulkan betas, I had toggled the new Power Efficiency button to off after installing but before rebooting. Then after rebooting and starting FAH a straggler win update popped up and I did a second reboot. Everything's better berfore using gpu-z monitoring to a log file under Gpu load the bar would show 100% but the log clearly showed a lot more 99% . With the 16.3 driver those 99% are now 100% tpf is up ppd is up I'm often around 400k now. better framerates in games as well. Temps are up a bit too around 56-58c. Hands down the best Fury X driver to date on my system anyways.

[DarkFoss]

Yesterday AMD released the 16.3.1 driver it's every bit as good as the previous 16.3 no loss of performance on my system. Temps are lower back to the pre-vulkan releases yet maintaining 100% gpu loads instead mostly stopping at 99%. I confirmed it with gpu-z log to file at the default 1 second interval and compared it with the last few releases. Folding on second Fury X Non-Crossfired the new Power Efficiency button toggled off.

[bcavnaugh]

Running release the 16.3.2 now, not sure I am seeing any real change from the 16.2.x release.

[JonasTheMovie]

I updated my Vulcan beta to the latest offical release, but saw ppd decrease, and load going up and down again.
Reverted to the beta to confirm and it seems to be the WU. Otherwise has the Vulcan beta given stable 100% load.
So, goint to 13.4.1 beta now....

[DarkFoss]

The 13.4.1 beta has been working well for me overall. Outside of the occasional wu that doesn't seem to stress the card enough like my current 13104 (2, 31, 51) gpu load never hits 100% always stops at 99% temps low too 48-49c, still TPF is only 4 seconds slower than the 16.3 driver. Last week I reinstalled the 16.3 then let the driver update to 16.3.1 then 16.3.2 the results for the week'
Week Points WUs
03.27.16 2,572,246 36

imo not bad for a single card. I let the driver update to the 16.4.1 on Monday so far looks to be another good week of production.

[road-runner]

I tried the new drivers on there website crimson drivers borked my folding with 7970s win 7 32 bit it loads the gpu but barely folds. I tried that new hotfix driver last night same thing..

[DarkFoss]

I hope you can find the time to fill out a Issue Report Form there is a links one on the main page right side(report a driver bug) and a second under the release notes tab at the bottom of the page. It's sad to see GCN 1.0 support is still being broken while optimizing for the latest GCN version they need to know and the more info the better chances of it getting addressed. Old thread but still appropriate I guess viewtopic.php?f=81&t=27115

[toTOW]

The 13.4.1 beta has been working well for me overall. Outside of the occasional wu that doesn't seem to stress the card enough like my current 13104 (2, 31, 51) gpu load never hits 100% always stops at 99% temps low too 48-49c, still TPF is only 4 seconds slower than the 16.3 driver. Last week I reinstalled the 16.3 then let the driver update to 16.3.1 then 16.3.2 the results for the week'
Week Points WUs
03.27.16 2,572,246 36

imo not bad for a single card. I let the driver update to the 16.4.1 on Monday so far looks to be another good week of production.

I don't know whether you're running a CPU slot alongside you GPU one, but some projects (like p13xxx) don't like when something interfere with the core on the CPU. Try to pause your CPU slot, or free more threads (SMP 6 on a 8 threads CPU for instance).

[bruce]

... gpu load never hits 100% always stops at 99% temps low too 48-49c...

I wouldn't worry about that 1%. There's always some time spend moving data between RAM and VRAM through the bus. The time to move data actually causes a bigger percentage of wait-state on a fast card than on a slower one because the computations are faster while the data transfers don't change. The GPU will run out of work sooner until more can be supplied.

What's your PCIe bus speed? ... and as toTOW suggests, are you sure your CPU can keep up with the demand?

[bcavnaugh]

Are their any known issues with AMD Hotfix Driver Version 16.4.1?
Thanks

[Bryman]

The 13.4.1 beta has been working well for me overall. Outside of the occasional wu that doesn't seem to stress the card enough like my current 13104 (2, 31, 51) gpu load never hits 100% always stops at 99% temps low too 48-49c, still TPF is only 4 seconds slower than the 16.3 driver. Last week I reinstalled the 16.3 then let the driver update to 16.3.1 then 16.3.2 the results for the week'
Week Points WUs
03.27.16 2,572,246 36

imo not bad for a single card. I let the driver update to the 16.4.1 on Monday so far looks to be another good week of production.

Okay, so... first of all, the gpu usage never goes up to 100%, it always stops at 99% (guess it depends on what program you're using)

Second of all, the gpu usage is an estimate based on real-world conditions.. when it says 99%, it really means about 60%

You need to run something like OCCT to get truly close to 100%

Made my 7970 use 480 watts... heh... apparently the TDP is 225... for some reason my video card doesn't power throttle and I upped the max voltage from 1.3 to 1.35 by editing the bios... but even at 1.3 volts I got it up to 450 watts

My power supply reported 42 amps (about 500 watts) going to my video card, but there's voltage drop

It was just for a few seconds... the VRM temp went from about 50 to 110 in about 20-25 seconds... and then it started throttling

[7im]

What makes you think Fah is not using more than 60%? The Fah CPU stress test is known to test a CPU as hard if not harder (and hotter) than OCCT. And the CPU client isn't far behind that. Fah has a special talent for optimizing performance to squeeze every CPU cycle to make the science go faster.

If Fah isn't using full gpu resources (which may be true, but haven't seen proof of that) then some other hardware or software is holding it back. And that will be the next target for development.