All win 7 user has this issue??

6 card ETH rig went from ~139 MH/s ====> ~146 MH/s
6 card UBIQ rig stayed the same at ~145 MH/s, so the drivers do work to fix the epoch hash issue!

I used DDU to uninstall the drivers in safe mode and had to apply the pixel patcher to bypass the signature check. Also needed to use AB Beta 16 to be able to set the undervolt and clocks.

reboot again...

This driver is legit.

I run 6x RX480 Sapphire Nitro+OC 8GB cards. I get about an 8 Mh/s increase with it, from under 160 Mh/s to 168 Mh/s, dual mining with Claymore ETH and Siacoin.

I run a custom bios on all of them that has the 1750 timing straps copied to the 2000 and set the CPU downclocked to 1125Mhz.
I use a monitor emulator dongle and WattTool to drop the voltage -16 (100mv) and currently run the cards at 2070 Mhz.
I was previously only able to get 2050 Mhz before stability issues occured (daily hangs or reboots.)

Total power consumption as monitored by HWinfo/Corsair AX1200i is about 1000 Watts, so no increase in power draw.
HWInfo GPU memory errors are minimal and within acceptable range.

Claymore if you see this, someone alerts you to this, OR this has already been hashed out and fixed (my apologies I haven't read through the 700+ pages yet, working on it).

Cards with the 9000gbps OC'd memory, notably the 1060 Gaming X+ (I don't know if AMD cards have the same issue), seem to hash slower than their peers with the non OC'd mem.,

Any reasons to why they are under-performing would be greatly appreciated! Some speculation was that the OC'd mem isn't able to be processed/accessed properly whether by the mining software or OS, etc.
Also with most users they report GPU load at 58%, 60%, 80%, but never more - even when power limit increased to 110%.

Thanks in advance!

@baracuda yeah well that did solve my issue for that 1 GPU at least 

@Munhenhos i bought for those GPUs a Server PSU with 2400W i think this should be enough for 6 GPUs or am i wrong?

for now, the only thing left for me to do is to get claymore to work with 6 GPUs in Win10 without the AMD Driver not installing properly. Kudos for the great program doktor83!

With Regards

Hello doktor83,

I went back read through the thread. Apologies, I will delete my post. However, I am still not able to use this tool, as it asks me to install .NET framework 3.5 and the install fails giving me an error code  0x800f081f. Please see the screenshots (http://imgur.com/a/D4oQu). Can you please advise how to fix these errors and use this tool.

FYI, I am using Windows 10 OS on my mining machine.

Thanks.

Just a question @doktor83, i have only used the SRBPolaris to flash my cards, but GPU-Z shows me unknown values, is that right?
Any way to fix this?

EDIT: So i fixed it but not with SRB but with PBE, any way to locate the problem at hand from my side?

With Regards

I updated the drivers some days back and all of the GPU speed increased back to normal. Thank you Robinhood.

But I have a lot of Incorrect ETH shares message especially on one of the GPU (RX 580 Gaming).
About 15%. The others is about 1%. But I had none some time back.

I don't know if this has to do with the new drivers or something I did.
Already tried to put things back to normal but no luck.

Did anyone had this problem with the drivers so that I can discard this possibility?

I've tested this on all my rigs and at first glance all seemed great.

I did have to bypass windows not allowing me to assign a unsigned software.

My hash rates appeared to be the same as before the nasty Dag creation started.
My power usage is the same after under volting.
My REPORTED hash rate to the pool of course matching my Rigs hash rate.

BUT here's the kicker my effective hash rate on the pool is about the same if not a little less than it was before applying the driver.  So my question is this.
Is the driver merely creating false readings on the cards with no actual effect on total shares submitted to the pool much like when you think you have found the golden card that reports a hash rate of 45Mh/s when in reality its only hashing at the same speed as the others.  Had the new Driver running for 7 hours now ....so of course I need test some more just incase its the pool on a go slow....although it normally only takes a couple of hours to get fairly accurate readings.