Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux)

[crazyq]

v12.3:

- slightly improved speed, about 410H/s on stock 390X, 465H/s on stock Nano, 300H/s on stock 280X, 305H/s on stock RX480.
- improved stability for high "-i" option values, added "-i 9" option value.
- fixed a few bugs.

Anyone got 16.3.2 drivers on Linux?
Now i've got 2240 sol/S with 1070W - 1095W on wall using 5 x r9 Furys, on latest drivers.
I want check how that work with 16.3.2

[bmtrader]

@Claymore Can you make something to improve 380 series? Currently I have 210H. Too low... Thank you in advance

[IOTUSA]

v12.3:

- slightly improved speed, about 410H/s on stock 390X, 465H/s on stock Nano, 300H/s on stock 280X, 305H/s on stock RX480.
- improved stability for high "-i" option values, added "-i 9" option value.
- fixed a few bugs.

Anyone got 16.3.2 drivers on Linux?
Now i've got 2240 sol/S with 1070W on wall using 5 x r9 Furys, on latest drivers.
I want check how that work with 16.3.2

I'll see what I can do, in exchange for your settings and BIOS
I assume you modded the Bios and run voltage, memory and core clock custom?

[crazyq]

v12.3:

- slightly improved speed, about 410H/s on stock 390X, 465H/s on stock Nano, 300H/s on stock 280X, 305H/s on stock RX480.
- improved stability for high "-i" option values, added "-i 9" option value.
- fixed a few bugs.

Anyone got 16.3.2 drivers on Linux?
Now i've got 2240 sol/S with 1070W - 1095W on wall using 5 x r9 Furys, on latest drivers.
I want check how that work with 16.3.2

I'll see what I can do, in exchange for your settings and BIOS
I assume you modded the Bios and run voltage, memory and core clock custom?

Stock GPUs and i just Update Motherboard bios. Thats it.

[YIz]

20H/s~ improvement on Hawaii GPUs with v12.3.

[Claymore]

To all: you can see low speed at highest possible "-i" value, if so, reduce it. For example, you specify "-i 8" for 280X 3GB card, miner reduces it to "-i 7" automatically (shows "not enough GPU memory" message), but it may work much slower than "-i 6".
So if you see that new version is slower than old version - try to reduce "-i" value a bit.
In some cases you can increase "-i" value, for example, in my tests Nano cards work best with v12.2 using "-i 7", but for v12.3 "-i 8" is faster.

@Claymore Can you make something to improve 380 series? Currently I have 210H. Too low... Thank you in advance

Tonga is really weak for ZEC.

[IOTUSA]

v12.3:

- slightly improved speed, about 410H/s on stock 390X, 465H/s on stock Nano, 300H/s on stock 280X, 305H/s on stock RX480.
- improved stability for high "-i" option values, added "-i 9" option value.
- fixed a few bugs.

Anyone got 16.3.2 drivers on Linux?
Now i've got 2240 sol/S with 1070W - 1095W on wall using 5 x r9 Furys, on latest drivers.
I want check how that work with 16.3.2

I'll see what I can do, in exchange for your settings and BIOS
I assume you modded the Bios and run voltage, memory and core clock custom?

Stock GPUs and i just Update Motherboard bios. Thats it.

Impressively low power draw I have to say. You don't use any flags in the Claymore software either? Just standard intensity and Claymore 12.3?

I don't think 16.3.2 exists for Fury/Nano under linux. Official Linux driver packages here: http://support.amd.com/en-us/download/linux

[hhdllhflower]

To all: you can see low speed at highest possible "-i" value, if so, reduce it. For example, you specify "-i 8" for 280X 3GB card, miner reduces it to "-i 7" automatically (shows "not enough GPU memory" message), but it may work much slower than "-i 6".
So if you see that new version is slower than old version - try to reduce "-i" value a bit.
In some cases you can increase "-i" value, for example, in my tests Nano cards work best with v12.2 using "-i 7", but for v12.3 "-i 8" is faster.

@Claymore Can you make something to improve 380 series? Currently I have 210H. Too low... Thank you in advance

Tonga is really weak for ZEC.

why my nano can't use -i 8?

AMD Cards available: 3
GPU #0: Fiji, 4096 MB available, 56 compute units
GPU #1: Fiji, 4096 MB available, 64 compute units
GPU #1 recognized as Fury X/Nano
GPU #2: Fiji, 4096 MB available, 64 compute units
GPU #2 recognized as Fury X/Nano
POOL version
GPU #0 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #0 algorithm ASM, intensity 7
GPU #1 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #1 algorithm ASM, intensity 7
GPU #2 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #2 algorithm ASM, intensity 7

[IOTUSA]

To all: you can see low speed at highest possible "-i" value, if so, reduce it. For example, you specify "-i 8" for 280X 3GB card, miner reduces it to "-i 7" automatically (shows "not enough GPU memory" message), but it may work much slower than "-i 6".
So if you see that new version is slower than old version - try to reduce "-i" value a bit.
In some cases you can increase "-i" value, for example, in my tests Nano cards work best with v12.2 using "-i 7", but for v12.3 "-i 8" is faster.

@Claymore Can you make something to improve 380 series? Currently I have 210H. Too low... Thank you in advance

Tonga is really weak for ZEC.

why my nano can't use -i 8?

AMD Cards available: 3
GPU #0: Fiji, 4096 MB available, 56 compute units
GPU #1: Fiji, 4096 MB available, 64 compute units
GPU #1 recognized as Fury X/Nano
GPU #2: Fiji, 4096 MB available, 64 compute units
GPU #2 recognized as Fury X/Nano
POOL version
GPU #0 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #0 algorithm ASM, intensity 7
GPU #1 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #1 algorithm ASM, intensity 7
GPU #2 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #2 algorithm ASM, intensity 7

literally 3 posts earlier:

To all: you can see low speed at highest possible "-i" value, if so, reduce it. For example, you specify "-i 8" for 280X 3GB card, miner reduces it to "-i 7" automatically (shows "not enough GPU memory" message), but it may work much slower than "-i 6".
So if you see that new version is slower than old version - try to reduce "-i" value a bit.
In some cases you can increase "-i" value, for example, in my tests Nano cards work best with v12.2 using "-i 7", but for v12.3 "-i 8" is faster.

Also, why do the compute units differ between your cards?

[marvykkio]

have you noticed a speed increase of 470/480?

[hhdllhflower]

To all: you can see low speed at highest possible "-i" value, if so, reduce it. For example, you specify "-i 8" for 280X 3GB card, miner reduces it to "-i 7" automatically (shows "not enough GPU memory" message), but it may work much slower than "-i 6".
So if you see that new version is slower than old version - try to reduce "-i" value a bit.
In some cases you can increase "-i" value, for example, in my tests Nano cards work best with v12.2 using "-i 7", but for v12.3 "-i 8" is faster.

@Claymore Can you make something to improve 380 series? Currently I have 210H. Too low... Thank you in advance

Tonga is really weak for ZEC.

why my nano can't use -i 8?

AMD Cards available: 3
GPU #0: Fiji, 4096 MB available, 56 compute units
GPU #1: Fiji, 4096 MB available, 64 compute units
GPU #1 recognized as Fury X/Nano
GPU #2: Fiji, 4096 MB available, 64 compute units
GPU #2 recognized as Fury X/Nano
POOL version
GPU #0 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #0 algorithm ASM, intensity 7
GPU #1 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #1 algorithm ASM, intensity 7
GPU #2 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #2 algorithm ASM, intensity 7

literally 3 posts earlier:

To all: you can see low speed at highest possible "-i" value, if so, reduce it. For example, you specify "-i 8" for 280X 3GB card, miner reduces it to "-i 7" automatically (shows "not enough GPU memory" message), but it may work much slower than "-i 6".
So if you see that new version is slower than old version - try to reduce "-i" value a bit.
In some cases you can increase "-i" value, for example, in my tests Nano cards work best with v12.2 using "-i 7", but for v12.3 "-i 8" is faster.

Also, why do the compute units differ between your cards?

ZEC: GPU0 455.346 H/s, GPU1 481.857 H/s, GPU2 460.153 H/s
v12.3 -i 7
gpu0 is fury
gpu1 is fury x
gpu2 is nano
for v12.2 can't use -i 7 , for v.12.3 i can use -i 7 but can't -i 8

[IOTUSA]

To all: you can see low speed at highest possible "-i" value, if so, reduce it. For example, you specify "-i 8" for 280X 3GB card, miner reduces it to "-i 7" automatically (shows "not enough GPU memory" message), but it may work much slower than "-i 6".
So if you see that new version is slower than old version - try to reduce "-i" value a bit.
In some cases you can increase "-i" value, for example, in my tests Nano cards work best with v12.2 using "-i 7", but for v12.3 "-i 8" is faster.

@Claymore Can you make something to improve 380 series? Currently I have 210H. Too low... Thank you in advance

Tonga is really weak for ZEC.

why my nano can't use -i 8?

AMD Cards available: 3
GPU #0: Fiji, 4096 MB available, 56 compute units
GPU #1: Fiji, 4096 MB available, 64 compute units
GPU #1 recognized as Fury X/Nano
GPU #2: Fiji, 4096 MB available, 64 compute units
GPU #2 recognized as Fury X/Nano
POOL version
GPU #0 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #0 algorithm ASM, intensity 7
GPU #1 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #1 algorithm ASM, intensity 7
GPU #2 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #2 algorithm ASM, intensity 7

literally 3 posts earlier:

To all: you can see low speed at highest possible "-i" value, if so, reduce it. For example, you specify "-i 8" for 280X 3GB card, miner reduces it to "-i 7" automatically (shows "not enough GPU memory" message), but it may work much slower than "-i 6".
So if you see that new version is slower than old version - try to reduce "-i" value a bit.
In some cases you can increase "-i" value, for example, in my tests Nano cards work best with v12.2 using "-i 7", but for v12.3 "-i 8" is faster.

Also, why do the compute units differ between your cards?

ZEC: GPU0 455.346 H/s, GPU1 481.857 H/s, GPU2 460.153 H/s
v12.3 -i 7
gpu0 is fury
gpu1 is fury x
gpu2 is nano
for v12.2 can't use -i 7 , for v.12.3 i can use -i 7 but can't -i 8

I think that's pretty normal, my Fury default to i6 and I see the same ballpark speed. Honestly doesn't even change if I force it to i5 or i4

[Claymore]

To all: you can see low speed at highest possible "-i" value, if so, reduce it. For example, you specify "-i 8" for 280X 3GB card, miner reduces it to "-i 7" automatically (shows "not enough GPU memory" message), but it may work much slower than "-i 6".
So if you see that new version is slower than old version - try to reduce "-i" value a bit.
In some cases you can increase "-i" value, for example, in my tests Nano cards work best with v12.2 using "-i 7", but for v12.3 "-i 8" is faster.

@Claymore Can you make something to improve 380 series? Currently I have 210H. Too low... Thank you in advance

Tonga is really weak for ZEC.

why my nano can't use -i 8?

AMD Cards available: 3
GPU #0: Fiji, 4096 MB available, 56 compute units
GPU #1: Fiji, 4096 MB available, 64 compute units
GPU #1 recognized as Fury X/Nano
GPU #2: Fiji, 4096 MB available, 64 compute units
GPU #2 recognized as Fury X/Nano
POOL version
GPU #0 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #0 algorithm ASM, intensity 7
GPU #1 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #1 algorithm ASM, intensity 7
GPU #2 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #2 algorithm ASM, intensity 7

Make sure you set these env variables:

GPU_MAX_HEAP_SIZE 100
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100

[Orielres]

To all: you can see low speed at highest possible "-i" value, if so, reduce it. For example, you specify "-i 8" for 280X 3GB card, miner reduces it to "-i 7" automatically (shows "not enough GPU memory" message), but it may work much slower than "-i 6".
So if you see that new version is slower than old version - try to reduce "-i" value a bit.
In some cases you can increase "-i" value, for example, in my tests Nano cards work best with v12.2 using "-i 7", but for v12.3 "-i 8" is faster.

@Claymore Can you make something to improve 380 series? Currently I have 210H. Too low... Thank you in advance

Tonga is really weak for ZEC.

why my nano can't use -i 8?

AMD Cards available: 3
GPU #0: Fiji, 4096 MB available, 56 compute units
GPU #1: Fiji, 4096 MB available, 64 compute units
GPU #1 recognized as Fury X/Nano
GPU #2: Fiji, 4096 MB available, 64 compute units
GPU #2 recognized as Fury X/Nano
POOL version
GPU #0 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #0 algorithm ASM, intensity 7
GPU #1 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #1 algorithm ASM, intensity 7
GPU #2 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #2 algorithm ASM, intensity 7

literally 3 posts earlier:

To all: you can see low speed at highest possible "-i" value, if so, reduce it. For example, you specify "-i 8" for 280X 3GB card, miner reduces it to "-i 7" automatically (shows "not enough GPU memory" message), but it may work much slower than "-i 6".
So if you see that new version is slower than old version - try to reduce "-i" value a bit.
In some cases you can increase "-i" value, for example, in my tests Nano cards work best with v12.2 using "-i 7", but for v12.3 "-i 8" is faster.

Also, why do the compute units differ between your cards?

ZEC: GPU0 455.346 H/s, GPU1 481.857 H/s, GPU2 460.153 H/s
v12.3 -i 7
gpu0 is fury
gpu1 is fury x
gpu2 is nano
for v12.2 can't use -i 7 , for v.12.3 i can use -i 7 but can't -i 8

I think that's pretty normal, my Fury default to i6 and I see the same ballpark speed. Honestly doesn't even change if I force it to i5 or i4

That is right. My R9 Nano run better on -i 7 in 12.3 and -i 6 in 12.2.

[Mr.Coinzer]

how can set mining intensity for r9295x2

[hhdllhflower]

To all: you can see low speed at highest possible "-i" value, if so, reduce it. For example, you specify "-i 8" for 280X 3GB card, miner reduces it to "-i 7" automatically (shows "not enough GPU memory" message), but it may work much slower than "-i 6".
So if you see that new version is slower than old version - try to reduce "-i" value a bit.
In some cases you can increase "-i" value, for example, in my tests Nano cards work best with v12.2 using "-i 7", but for v12.3 "-i 8" is faster.

@Claymore Can you make something to improve 380 series? Currently I have 210H. Too low... Thank you in advance

Tonga is really weak for ZEC.

why my nano can't use -i 8?

AMD Cards available: 3
GPU #0: Fiji, 4096 MB available, 56 compute units
GPU #1: Fiji, 4096 MB available, 64 compute units
GPU #1 recognized as Fury X/Nano
GPU #2: Fiji, 4096 MB available, 64 compute units
GPU #2 recognized as Fury X/Nano
POOL version
GPU #0 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #0 algorithm ASM, intensity 7
GPU #1 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #1 algorithm ASM, intensity 7
GPU #2 is going to use too high intensity (, not enough GPU memory, intensity value reduced (7)
GPU #2 algorithm ASM, intensity 7

Make sure you set these env variables:

GPU_MAX_HEAP_SIZE 100
GPU_MAX_ALLOC_PERCENT 100
GPU_SINGLE_ALLOC_PERCENT 100

thanks it work but i get more speed on i7

[rpg]

dwarwpool is so fast, lets make it great pool, it needs more workers. It does not need ssl/tlc connection btw...you dont need to worry about 2.5 dev fee

dwarfpool is a thief.

flypool is doing good job now a days

Maybe the variation in Dwarfpool is too high as it has fewer users.

Supernova has issues paying and are not replying to emails

[rpg]

Gigabyte 7950 hashing at 317. A 3% improvement. The best $50 I ever invested lol
Gigabyte g1 rx480 heading at 335

Will later test the others

[suggsy89]

have you noticed a speed increase of 470/480?

No hash-rate increase for RX480, adjusting intensity settings does nothing for speed.

I think in general just bug fixes for this release.

[Swiped]

Make sure your AMD Gaming Evolve app didn't automatically update your drivers, I had to use DDU and reinstall 4 times until I figured out it does that EVEN IF you uncheck the box during installation. You have to manually open AMD Gaming Evolved, click on the wheel besides deriver update and uncheck auto updates.

That's not it. And this is a 100% clean and updated Windows 10 x64 install with 4GB ram, 20 GB virtual mem, and NOTHING but AMD 16.3 drivers and claymore installed. Blows my damn mind.

General behavior is:

1. A card (random) will hash at 0% while all others are fine
2. OpenCL call hangs.
3. Crash

Sometimes all cards will be hashing just dandy for a minute or two, then one drops, then OpenCL call fail on 1 card.

Experience has shown me that the OpenCL hang for any of my rigs (I am small time with 16 rigs) is that it is one of three things:

1. Video drivers need to be re-installed.  I have been using 16.11.5 for all my rigs for several months now without issue, or at least with the least number of issues.  Install it with only one card connected to the motherboard, and then add the other cards and let them auto-populate/auto-install.  This is probably 50% of my issues.
2.  I run a mod'd bios on all my cards that I make that uses the #5 voltage strap across #6 and #7 straps and runs the mem speed at 1750 Mhz.  Sometimes this causes the voltage to be too low on the #7 strap and I have to raise that voltage up in 20 mV steps until I get it stable, and then I will flash the bios with that change, or you can use WattTool or whatever you have to make that change.  None of the cards are exactly the same due to variations in manufacturing even though they are all the same make and model, so getting the voltage right is key.  This is probably 40% of my issues.
3.  Bad riser cards or bad riser cables, or a bad connection to the motherboard.  This has only happened twice in 6 months, but it is a possible contributor on a less frequent case.

A few times I have had to do a complete Windows 10 clean install, but I have come to realize that most of the issues are really video drivers and undervolting the GPU core clock.  Hope this helps.