I'd like to say a bit more about ADL (library that is used to manage clocks/voltage/fan). I have been working with ADL API for a couple of years, so I have some experience.
When you use ADL, you must ask what version of API supports your GPU. For example, Tahiti reports v5, Hawaii v6.
Every API version uses own set of functions, sample code can be found in ADL SDK. I implemented v5 and v6 and it worked fine for some time.
Then in some drivers AMD disabled underclocking via ADL for some reason, API calls report "OK" but GPU still uses old clocks.
Then AMD releases Polaris cards which report API v7. And no new ADL SDK was released so no headers for new API or any samples. We had to wait for a couple of months before it was finally released.
I added code that uses v7 and it worked fine, except one thing: if I set fan 50%, API sets it to 41% or 46% and I have no idea why. I had to change fan management logic to make it work properly with this issue.
Then in some drivers AMD changed something again and OC stopped working, partially or completely.
Then AMD releases new drivers and Hawaii cards started to report that they use API v7 instead of v6. But in this mode they support v7 a bit differently than Polaris so I had to change my code again to support this new "feature" of drivers.
Then AMD releases 17.7.2 and API v7 returns "not supported" error code. After some research I found that AMD added new functions for API v7 and blocked old functions. So this time they decided not to create API v8, but changed functions for already released API version. It's awesome. No new ADL SDK is released for these changes, so again no headers or code samples for "new" API v7. Finally I made it work, but sometimes it works with strange issues, currently I try to find the reason.
Vega support in ADL has own problems currently, for example, you can set fan to 90% but then there is no way to set it to any lower value.
For Linux, AMD decided to drop ADL support completely in gpu-pro drivers and use new way that I have to support too.

So ADL is the most weird API I've ever seen, but when you see that some options don't work as expected, probably you will blame the miner
On other hand, when I decided to add fan/OC management I found that Nvidia has no public API for it at all. From this point of view, I think weird API is better than no API at all.

Wrong, no API had been better, as people would just use other tools, they used earlier.
This way they blame the miner software, like you said.

No. You need ASIC hardware the same as Bitcoin at this time.

Almost same problem with him. Any body can help if "NVML: cannot get current temperature, error 15" message appear always with 6 VGA rig?

After that it is working stable with 5 VGA only (1 disconnect automatically).

Thanks you.

Is it the 17.7.2 that will solve the DAG problem?

Hi! I'm getting the FAILOVER 4 fault, so I'm going to edit epools.txt? For ethermine the command line should be "-allpools 1" and "ESM 0" right? And in the "epools.txt" I must write -allpools 1 and ESM 0 too? My main pool is eu1.ethermine.org:1444, alternative pools will be eu1.ethermine.org:4444, eu2:ethermine.org:14444, eu2.ethermine.org:4444, us1, us2 or asian server? Which is better? I'm from spain. Thanks!

AB and WattTool don't work with 17.7.2. So don't hurry to update your rigs. Also may be it's a good idea to wait new drivers from AMD that solve DAG issue if you don't want to update rigs twice.

I think only prevents that hashrate lows for incoming DAG epoch 137. New Claymore 9.8 version improves the hashrate? Thanks

I still get the same 33 MH/s on my GTX 1070s. Mining difficulty increased for everyone whether you're AMD or NVidia. So what exactly are you LOL'ing about?



Can you enlighten me why this upgrade hits Nvidia cards the worst? I might be missing something here. Thanks.

He's probably loling about the fact that he didnt spend 50% more for a 1070 over an 8gb rx 480/580 that will get almost the same hashrate when the dag fix comes out.