Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux)

[PandaPanda!]

I have one rig in my farm which keeps crashing every 3 hours or so.

Usually I can open up the log file and find out which particular GPU is causing issues, and rectify the problem without much headache.  But this time, i'm getting this message...

13:18:08:445   5ac   buf: {"id":4,"jsonrpc":"2.0","result":true}
13:18:08:445   5ac   parse packet: 38
13:18:08:445   5ac   ETH: Share accepted (47 ms)!
13:18:08:445   5ac   new buf size: 0
13:18:09:865   eb8   GPU0 t=70C fan=82%, GPU1 t=67C fan=78%, GPU2 t=65C fan=81%, GPU3 t=65C fan=74%, GPU4 t=71C fan=79%
13:18:09:865   eb8   em hbt: 0, fm hbt: 16,
13:18:09:865   eb8   watchdog - thread 0, hb time 250
13:18:09:865   eb8   watchdog - thread 1, hb time 32
13:18:09:865   eb8   watchdog - thread 2, hb time 32
13:18:09:865   eb8   watchdog - thread 3, hb time 19906
13:18:09:865   eb8   watchdog - thread 4, hb time 234
13:18:09:865   eb8   watchdog - thread 5, hb time 32
13:18:09:865   eb8   watchdog - thread 6, hb time 297
13:18:09:865   eb8   watchdog - thread 7, hb time 94
13:18:09:865   eb8   watchdog - thread 8, hb time 125
13:18:09:865   eb8   watchdog - thread 9, hb time 328
13:18:09:865   eb8   WATCHDOG: GPU error, you need to restart miner
13:18:09:865   eb8   Rebooting


Its not specifically telling me which GPU is having issues, although i'm assuming its whatever was working on "thread 3" - how can I find out which GPU is working on thread 3?  Claymore, please help!  This is driving me nuts.   This rig usually hangs after the "Rebooting" message.

[boysie]

With 9.2 my r9 290 went from 31 to 21 mh/s (ETH). SC went from 440-450 to 640. Temps stayed the same. With 9.3, eth went up 1 mh/s (22mh/s) and SC to 660.

Yo,

yea the same happened here, you need to add -dcri ## to your command, maybe start off at -dcri 30 and while your miner is running use the - sign, you will decrease the dcri by one every time and each time you press you will see new hashspeed, do this untill you find the sweet spot for both.

ps. you might try adding -ethi 16, worked for me a bit.

-dcri is different for every card. Once you find the sweet spot you will have better speeds.

if that is the case how do you live change the dcri for 1 card? or did you mean make of card?

[jackbox]

With 9.2 my r9 290 went from 31 to 21 mh/s (ETH). SC went from 440-450 to 640. Temps stayed the same. With 9.3, eth went up 1 mh/s (22mh/s) and SC to 660.

Yo,

yea the same happened here, you need to add -dcri ## to your command, maybe start off at -dcri 30 and while your miner is running use the - sign, you will decrease the dcri by one every time and each time you press you will see new hashspeed, do this untill you find the sweet spot for both.

ps. you might try adding -ethi 16, worked for me a bit.

-dcri is different for every card. Once you find the sweet spot you will have better speeds.

if that is the case how do you live change the dcri for 1 card? or did you mean make of card?

As Claymore says in Post #1 you check the -dcri of each card by itself with no other cards in the machine. then when you run the start batch you give the value for each card, such as "-dcri 12,34,21" etc.

[philip7134]

What would you guys suggest as the best crimson drivers right now for claymore 9.3 and modding bios.

[Ursul0]

I have one rig in my farm which keeps crashing every 3 hours or so.

Usually I can open up the log file and find out which particular GPU is causing issues, and rectify the problem without much headache.  But this time, i'm getting this message...

13:18:08:445   5ac   buf: {"id":4,"jsonrpc":"2.0","result":true}
13:18:08:445   5ac   parse packet: 38
13:18:08:445   5ac   ETH: Share accepted (47 ms)!
13:18:08:445   5ac   new buf size: 0
13:18:09:865   eb8   GPU0 t=70C fan=82%, GPU1 t=67C fan=78%, GPU2 t=65C fan=81%, GPU3 t=65C fan=74%, GPU4 t=71C fan=79%
13:18:09:865   eb8   em hbt: 0, fm hbt: 16,
13:18:09:865   eb8   watchdog - thread 0, hb time 250
13:18:09:865   eb8   watchdog - thread 1, hb time 32
13:18:09:865   eb8   watchdog - thread 2, hb time 32
13:18:09:865   eb8   watchdog - thread 3, hb time 19906
13:18:09:865   eb8   watchdog - thread 4, hb time 234
13:18:09:865   eb8   watchdog - thread 5, hb time 32
13:18:09:865   eb8   watchdog - thread 6, hb time 297
13:18:09:865   eb8   watchdog - thread 7, hb time 94
13:18:09:865   eb8   watchdog - thread 8, hb time 125
13:18:09:865   eb8   watchdog - thread 9, hb time 328
13:18:09:865   eb8   WATCHDOG: GPU error, you need to restart miner
13:18:09:865   eb8   Rebooting


Its not specifically telling me which GPU is having issues, although i'm assuming its whatever was working on "thread 3" - how can I find out which GPU is working on thread 3?  Claymore, please help!  This is driving me nuts.   This rig usually hangs after the "Rebooting" message.

2 threads per GPU in their order, "time 19906"

[yslyung]

claymore says 290 tri-x 3072 mem & it squits but when i run NH miner, it uses claymore miner too but it does says 4096 mem

kinda weird.

win10 64bit, crimson 16.11.5

ddu, reinstalled same result, reinstalled win 10 n all over again, still same

[FFI2013]

With 9.2 my r9 290 went from 31 to 21 mh/s (ETH). SC went from 440-450 to 640. Temps stayed the same. With 9.3, eth went up 1 mh/s (22mh/s) and SC to 660.

Yo,

yea the same happened here, you need to add -dcri ## to your command, maybe start off at -dcri 30 and while your miner is running use the - sign, you will decrease the dcri by one every time and each time you press you will see new hashspeed, do this untill you find the sweet spot for both.

ps. you might try adding -ethi 16, worked for me a bit.

-dcri is different for every card. Once you find the sweet spot you will have better speeds.

if that is the case how do you live change the dcri for 1 card? or did you mean make of card?

As Claymore says in Post #1 you check the -dcri of each card by itself with no other cards in the machine. then when you run the start batch you give the value for each card, such as "-dcri 12,34,21" etc.

Thats the question I had because I have one rig with mixed cards but instead of taking cards out we could choose which card with -di

which drivers work well with r9 and rx cards on my mixed card rig I have a 270 that no longer mines eth and was going to replace it with my odd ball rx470

[jcpbs]

With 9.2 my r9 290 went from 31 to 21 mh/s (ETH). SC went from 440-450 to 640. Temps stayed the same. With 9.3, eth went up 1 mh/s (22mh/s) and SC to 660.

Yo,

yea the same happened here, you need to add -dcri ## to your command, maybe start off at -dcri 30 and while your miner is running use the - sign, you will decrease the dcri by one every time and each time you press you will see new hashspeed, do this untill you find the sweet spot for both.

ps. you might try adding -ethi 16, worked for me a bit.

-dcri is different for every card. Once you find the sweet spot you will have better speeds.

Thanks guys, going to try it and will report!!

[cryptominer420]

which drivers work well with r9 and rx cards on my mixed card rig I have a 270 that no longer mines eth and was going to replace it with my odd ball rx470

I am using 16.11.5 I have a mixed rig with RX 470's (4GB Cards) and R9 270X (2GB cards) and when setup this way I am still getting 15MH/s out of the 270X's but without 1 470 per 270X the 270X's won't mine. My guess is that the Dag is being shared from the 4GB cards.

[szszab]

It is so slow with gtx1080:

GPU #0: GeForce GTX 1080, 8192 MB available, 20 compute units, capability: 6.1

GPU #1: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1

...

ETH - Total Speed: 43.967 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:03
ETH: GPU0 20.961 Mh/s, GPU1 23.006 Mh/s
ETH: 04/30/17-17:22:35 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 45.882 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:03
ETH: GPU0 20.523 Mh/s, GPU1 25.359 Mh/s
ETH: 04/30/17-17:22:39 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 45.595 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:04
ETH: GPU0 20.689 Mh/s, GPU1 24.906 Mh/s
GPU0 t=73C fan=54%, GPU1 t=61C fan=39%
ETH: 04/30/17-17:22:41 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 46.282 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:04
ETH: GPU0 20.994 Mh/s, GPU1 25.288 Mh/s
ETH: 04/30/17-17:23:04 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 45.375 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:04
ETH: GPU0 20.943 Mh/s, GPU1 24.432 Mh/s

This is very bad.. I'm using Windows 10 64 bit, Cuda 8 and 381.65 driver.
Is there any solution for this? Or can I try to fix it? There is a source code somewhere?
Is it some possibility to change thread per block size?

[jackbox]

It is so slow with gtx1080:

GPU #0: GeForce GTX 1080, 8192 MB available, 20 compute units, capability: 6.1

GPU #1: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1

...

ETH - Total Speed: 43.967 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:03
ETH: GPU0 20.961 Mh/s, GPU1 23.006 Mh/s
ETH: 04/30/17-17:22:35 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 45.882 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:03
ETH: GPU0 20.523 Mh/s, GPU1 25.359 Mh/s
ETH: 04/30/17-17:22:39 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 45.595 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:04
ETH: GPU0 20.689 Mh/s, GPU1 24.906 Mh/s
GPU0 t=73C fan=54%, GPU1 t=61C fan=39%
ETH: 04/30/17-17:22:41 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 46.282 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:04
ETH: GPU0 20.994 Mh/s, GPU1 25.288 Mh/s
ETH: 04/30/17-17:23:04 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 45.375 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:04
ETH: GPU0 20.943 Mh/s, GPU1 24.432 Mh/s

This is very bad.. I'm using Windows 10 64 bit, Cuda 8 and 381.65 driver.
Is there any solution for this? Or can I try to fix it? There is a source code somewhere?

Mine ZEC.

[szszab]

I don't care ZAC. I belt that the price of ETH will grow up so fast. 3 days: 21 dollar plus (It went from 50$ to 71$, and it is just the beginning).
And the ZAC use plus watts (about 110 plus with this two cards).

[jackbox]

I don't care ZAC. I belt that the price of ETH will grow up so fast. 3 days: 21 dollar plus (It went from 50$ to 71$, and it is just the beginning).
And the ZAC use plus watts (about 110 plus with this two cards).

Nvidia cards don't mine ETH very well. That is why you have slow speeds.

[coinzoid]

It is so slow with gtx1080:

GPU #0: GeForce GTX 1080, 8192 MB available, 20 compute units, capability: 6.1

GPU #1: GeForce GTX 1070, 8192 MB available, 15 compute units, capability: 6.1

...

ETH - Total Speed: 43.967 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:03
ETH: GPU0 20.961 Mh/s, GPU1 23.006 Mh/s
ETH: 04/30/17-17:22:35 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 45.882 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:03
ETH: GPU0 20.523 Mh/s, GPU1 25.359 Mh/s
ETH: 04/30/17-17:22:39 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 45.595 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:04
ETH: GPU0 20.689 Mh/s, GPU1 24.906 Mh/s
GPU0 t=73C fan=54%, GPU1 t=61C fan=39%
ETH: 04/30/17-17:22:41 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 46.282 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:04
ETH: GPU0 20.994 Mh/s, GPU1 25.288 Mh/s
ETH: 04/30/17-17:23:04 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 45.375 Mh/s, Total Shares: 3, Rejected: 0, Time: 00:04
ETH: GPU0 20.943 Mh/s, GPU1 24.432 Mh/s

This is very bad.. I'm using Windows 10 64 bit, Cuda 8 and 381.65 driver.
Is there any solution for this? Or can I try to fix it? There is a source code somewhere?
Is it some possibility to change thread per block size?

From my understanding GTX 1080 is not good for mining ETH. I recommend RX 470/480 instead of this.

[kobazik]

I'm getting an error when trying to use calymore on ubuntu 16.04:  Cannot build OpenCL program for GPU . AMDgpu-pro drivers 16.40 and SDK are installed. Any ideas?

[szszab]

1070 and 1060 is good. Just the 1080 is bad, but the 1080 hardware is better than the others. This problem is with the software.
If I see well: 480 and 580 have bad performance/watt.

[kemo6600]

1070 and 1060 is good. Just the 1080 is bad, but the 1080 hardware is better than the others. This problem is with the software.
If I see well: 480 and 580 have bad performance/watt.

For the FUN , switching from Zec to ETH



50% power limit , that is 125W DC , under clocking memory by 300 Mhz yields 3Mh/s, if someone can crack the bios then those babies can do 40+ easily

[robminer]

Little Help?

Had an R9 280X GPU GPU laying around and decided to add it to a rig.  This rig had (4) Radeon 390 (ASUS STRIX R9 390).  The miner recognizes the card but errors out on "Cannot build OpenCL program for GPU 0"

Running Ubuntu 16.04

Any help or direction to look would be appreciated.

LOG
10:51:48:788   97059740   AMD Cards available: 5
10:51:48:788   97059740   GPU #0: Tahiti, 2520 MB available, 16 compute units
10:51:48:788   97059740   GPU #1: Hawaii, 8139 MB available, 40 compute units
10:51:48:789   97059740   GPU #1 recognized as Radeon 390
10:51:48:789   97059740   GPU #2: Hawaii, 8139 MB available, 40 compute units
10:51:48:789   97059740   GPU #2 recognized as Radeon 390
10:51:48:789   97059740   GPU #3: Hawaii, 8139 MB available, 40 compute units
10:51:48:789   97059740   GPU #3 recognized as Radeon 390
10:51:48:789   97059740   GPU #4: Hawaii, 8139 MB available, 40 compute units
10:51:48:789   97059740   GPU #4 recognized as Radeon 390
10:51:48:789   97059740   POOL/SOLO version
10:51:48:789   97059740   b343
10:51:48:789   97059740   Platform: Linux
10:51:48:867   97059740   start building OpenCL program for GPU 0...
10:51:48:868   97059740   done
10:51:48:968   97059740   Internal error: Input OpenCL binary is not for the target!

10:51:48:968   97059740   Cannot build OpenCL program for GPU 0
10:51:49:072   97059740   start building OpenCL program for GPU 1...
10:51:49:186   97059740   done
10:51:49:389   97059740   start building OpenCL program for GPU 2...
10:51:49:494   97059740   done
10:51:49:697   97059740   start building OpenCL program for GPU 3...
10:51:49:810   97059740   done
10:51:50:013   97059740   start building OpenCL program for GPU 4...
10:51:50:127   97059740   done

[notbatman]

An RX460 4GB OC will be arriving soon, I'm betting +20MH/s on this $150 card. We'll see...

Those 1080's are like $1k?

[AltScope]

Little Help?

Had an R9 280X GPU GPU laying around and decided to add it to a rig.  This rig had (4) Radeon 390 (ASUS STRIX R9 390).  The miner recognizes the card but errors out on "Cannot build OpenCL program for GPU 0"

Running Ubuntu 16.04

Any help or direction to look would be appreciated.

LOG
10:51:48:788   97059740   AMD Cards available: 5
10:51:48:788   97059740   GPU #0: Tahiti, 2520 MB available, 16 compute units
10:51:48:788   97059740   GPU #1: Hawaii, 8139 MB available, 40 compute units
10:51:48:789   97059740   GPU #1 recognized as Radeon 390
10:51:48:789   97059740   GPU #2: Hawaii, 8139 MB available, 40 compute units
10:51:48:789   97059740   GPU #2 recognized as Radeon 390
10:51:48:789   97059740   GPU #3: Hawaii, 8139 MB available, 40 compute units
10:51:48:789   97059740   GPU #3 recognized as Radeon 390
10:51:48:789   97059740   GPU #4: Hawaii, 8139 MB available, 40 compute units
10:51:48:789   97059740   GPU #4 recognized as Radeon 390
10:51:48:789   97059740   POOL/SOLO version
10:51:48:789   97059740   b343
10:51:48:789   97059740   Platform: Linux
10:51:48:867   97059740   start building OpenCL program for GPU 0...
10:51:48:868   97059740   done
10:51:48:968   97059740   Internal error: Input OpenCL binary is not for the target!

10:51:48:968   97059740   Cannot build OpenCL program for GPU 0
10:51:49:072   97059740   start building OpenCL program for GPU 1...
10:51:49:186   97059740   done
10:51:49:389   97059740   start building OpenCL program for GPU 2...
10:51:49:494   97059740   done
10:51:49:697   97059740   start building OpenCL program for GPU 3...
10:51:49:810   97059740   done
10:51:50:013   97059740   start building OpenCL program for GPU 4...
10:51:50:127   97059740   done

if memory serves amd have stopped supporting your card for linux, you'll need to use an older linux version

[edit]
https://askubuntu.com/questions/765616/amd-r9-280x-drivers-for-ubuntu-16-04