I could be wrong, but I did see that they will be releasing a new version of Claymore soon to go along with the new drivers being release by AMD. Will be interesting to see what it does to speeds.

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.

There are bugs in ADL, as always. If you have problems with clocks/voltage settings in 17.7.2 - either don't use these options or use previous drivers. I suspect it will take a lot of time to make it work properly... and then AMD will release another ADL update...

17.7.2 was weird for me on 9.7.   I saw as much as 20w increase on some cards which caused throttling.  I am afraid the driver that 'fixes' the dag problem is going to suck

So, I'll have to fight again with Hynix to get close to your 13.8 Mh/s.

Judging by your posts here you are not much better.

@OP

If company you work for is doing something IT related, it could be a problem just like Alpha0One1 said, because it could be security risk for them. If it's not IT related, and they have some spare room, sure why not.

Hi guys!
I have Gigabyte GV-RX560 GAMING OC-4GD (Hynix(((), without overclocking I have 10.6 Mh/s.
Overclocking memory to 2000, brings an insignificant result. I have over9000 times tried to flash BIOS with different timings, but without success. Once I saw 16 Mh/s, but the driver left at once.
Substituting timings from Micron got 14 Mh/s at 2000 memory frequency it seems kind of stable, but HWinfo shows a lot of memory errors.
The best that could be achieved is 12.9 Mh/s and the overclocking of the memory of 1850 (with a small number of errors). I did not see in this topic that someone paid attention to memory errors. The question is: why does no one monitor errors? P.S.: GPU8 is 1050Ti. P.P.S: Sorry for my french.

This is the memory controller you are seeing afaik.

Bad idea.

1. How good is the physical security in your office e.g. gatepass for equipments coming in/out? You might be able to bring it inside the office but you may not be able to take it out.
2. That might be construed as "stealing" company resources. You bringing in a personal equipment and use company utilities for personal gain - electricity, space or computer space. You'll possibly face HR sanctions if your personal equipment is found out.
3. You'll introdude risk to your companies network infrastructure, opening network ports for mining, etc. What if a malware infects your company's computer/network system thru your miner?

If you are in control of your test PC lab and test internet network that is totally separate from production network and with no need to bring in a personal equipment, better, as that would minimize the risk to your company network and risk of an equipment being personally associated to you as well. Just run a test, not a miner running 24x7.

Strange thing that I noticed with my cards, in solo mining they do 14.5-14.7 Mh/S in Ethash.
But, when I add DCR, performance in Ethash increases up to 15.2-15.3 mh/s + 100-130 mhs in DCR.

IF you mine ethereum, epoch is 136 already, I guess RX560 does 14.5 Mh/s at most. because of huge dag file.

Thank you Branko.
May i ask you whether or not that msi rx 560 aero 4gb with hynix memory can pass 13mh/s point?
I'm far away from being an expert in edtiting bios and stuff but copying and pasting timing straps is as far as i can go.

Anyone having timing straps like these?
Everywhere i look i see the normal 200, ...2000 ones

So, I paid for (.3 ETH) the modified 560 bios that minerscott posted here: https://bitcointalk.org/index.php?topic=2024062.msg%msg_id%

He assured me that it would work for my XFX single fan 560 (hynix). I repeated the same steps I've used multiple times with other cards - and his supplied bios file rendered the GPU inoperable (in both Windows and EthOS). He assured me that I just needed to try again, which I did, with the same result. It ended up being a lot of frustration just trying to get the cards working again.

He was very nice (we've got probably 20x emails back and forth), and gave me a different bios to try, which also failed. He then went unresponsive and it has been a week since he has emailed me. I'm out the ETH and have my GPU's plodding along at roughly 12/Mh, thanks to a free bios somebody posted elsewhere. If anybody has a link to better version I'd love to have it.

I'm not going to rule out that life simply got in the way, so if you're reading this Scott, I'm happy to listen to an explanation and will take this down if you can either supply a working bios or refund my payment. This is basically my only option at this point.

Not looking for sympathy - I clearly should have invested the time into figuring this out myself. Looked for an easy way out and paid for it.  Won't be paying for bios files anymore.

which model do you have

Hey guys! Anyone tried this new AMD driver that has been released a few days ago.
Claymore said AMD will release a new driver that solves DAG hashrate drop. This might be it?