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

[AzzAz]

I've run into trouble with my hashrates:

6 GPU mining rig (4x570, 1x470, 1x480 - all with modded bios'es) on MSI Z270 A Pro, 4GB Ram, Windows 10, AMD 17.6.1 Driver.
PC was working for days now (all on -100 mV, 1150MHz, 2000 Mhz, set with MSI AB). Constantly reporting hashrate of 168 MHs / ~2900 SIA (Dual Mining).
PC was shut down, started again, all settings of AB applied and suddenly a 570 and the 480 making troubles. The hashrate of 2 cards in claymore is changing from 28MHs down to 7ish. RX480 made the system crash, even on stock settings when running claymore for some mins.

I've tryed uninstalling driver, reinstalling (the one what was working before), applying the AMD driver fix, changing back to 4g decoding so all cards reported working again. but the hashrates of these two cards are abysmal.

Now the system is running with 5 gpus (without 480) but the hashrate of one RX570 is fluctuating heavily (see attached screenshot).

Can anybody help?

Let me guess: Windows updated?

[Tmdz]

It dropped 2% because it's accessing a second memory module, right? So, from 2 to 4GB we shouldn't see a difference in the hashrate, correct?

correct

No, all RX cards will be feeling the effects of DAG. 4gb and 8gb

[Bojcha]

From the description I understood that now they generate DAG on GPU too. So it is not related to this issue.

I see the speed drop. I checked possible workarounds, at least for Polaris, they failed. So probably this hashrate drop cannot be fixed, at least on miner software level.

Well it can and it is fixed, but maybe you cant fix it. I think its time for competitive miner to be released...

Care to explain this part? Where/when did you see a fix for it?

No, I can't. Its part of my next project

While you there, fix 280x too!
Get out!

[edop2005]

Dualmining ETH/SIA on nanopool doesn't work for me. ETH works fine but SC gets job timeouts.

---------------------------------------------------------------------------------
ETH: 06/20/17-10:15:39 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 20.727 Mh/s, Total Shares: 5, Rejected: 0, Time: 00:18
ETH: GPU0 20.727 Mh/s
 SC - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0
 SC: GPU0 0.000 Mh/s
GPU0 t=67C fan=0%
Socket was closed remotely (by pool)
 SC: Job timeout, disconnect, retry in 20 sec...
---------------------------------------------------------------------------------

I used nanopool's autoconfig generator, here s my config

EthDcrMiner64.exe -epool eth-eu1.nanopool.org:9999 -ewal 0xmyethwallet -epsw x -dcoin sia -dpool sia-eu1.nanopool.org:7777 -dwal mysiawallet -dpsw x -ftime 10

Am I the only one? I tried replacing -dcoin sia with -dcoin sc but same result.

[jackbox]

Dualmining ETH/SIA on nanopool doesn't work for me. ETH works fine but SC gets job timeouts.

---------------------------------------------------------------------------------
ETH: 06/20/17-10:15:39 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 20.727 Mh/s, Total Shares: 5, Rejected: 0, Time: 00:18
ETH: GPU0 20.727 Mh/s
 SC - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0
 SC: GPU0 0.000 Mh/s
GPU0 t=67C fan=0%
Socket was closed remotely (by pool)
 SC: Job timeout, disconnect, retry in 20 sec...
---------------------------------------------------------------------------------

I used nanopool's autoconfig generator, here s my config

EthDcrMiner64.exe -epool eth-eu1.nanopool.org:9999 -ewal 0xmyethwallet -epsw x -dcoin sia -dpool sia-eu1.nanopool.org:7777 -dwal mysiawallet -dpsw x -ftime 10

Am I the only one? I tried replacing -dcoin sia with -dcoin sc but same result.

Did you change "0xmyethwallet" and "mysiawallet" to your actual wallet addresses?

[bumblebee24]

Has anyone ran into an issue with setting global temp for rx560s using ethos?

Seems as if its only setting for the 1st GPU, while others run to their stock target temp of 80 °C and very low fan speeds, 18-25%.

Any help would be greatly appreciated.

Thanks!

[miner63456]

Claymore,
do you have any ideas how to overcome Polaris hashrate drop for epoch >129 ?

Genoil said that DAG now took 100% of first memory bank (2gb) and go to second memory bank, so access two banks instead of one leads significant hashrate drop.

Do you make any research in this direction, or it is hopeless? What you think, any comments?

I have this probleme with 8g rx 480 hash drop every new dag epoche on ethereum and ethereum classic

Minergate miner say with her laste version we do not loss effective Hashrate see here;

https://minergate.com/blog/v-6-5-no-hashrate-drop-after-dag-epoch-switch/

From the description I understood that now they generate DAG on GPU too. So it is not related to this issue.

I see the speed drop. I checked possible workarounds, at least for Polaris, they failed. So probably this hashrate drop cannot be fixed, at least on miner software level.

Well it can and it is fixed, but maybe you cant fix it. I think its time for competitive miner to be released...

If claymore can't fix it, chances are nobody can. Its hardware related. People with 280x suffered this also and they just mine ZEC now or bought RX series.

Since claymore,genoil couldn't find a solution with the 280x, chances are there is nothing that can be done.

My 6 year old Radeon 6990, never suffered from this problem and that card was crazy old.

The 2 GB problem can be solved with a certain memory management scheme.  Level of effort may not be worth it, but Claymore can PM me to discuss.

[fr4nkthetank]

go in win10, "services".  Disable windows update there.  Use DDU to remove drivers, and re-install them.  Should work.

[erdubya]

@simon66, go to windows device manager, do your cards show up without yellow exclaims?

My card was working fine (Sapphire Rx480 Nitro 8GB) with Claymore 9.5.  After modding the bios I get the error "no amd opencl or nvidia cuda gpus found exit" and the miner stops...and yes my card shows up with yellow exclaim.

[Aquazi]

@simon66, go to windows device manager, do your cards show up without yellow exclaims?

My card was working fine (Sapphire Rx480 Nitro 8GB) with Claymore 9.5.  After modding the bios I get the error "no amd opencl or nvidia cuda gpus found exit" and the miner stops...and yes my card shows up with yellow exclaim.

You didn't validate the bios, windows doesn't recognize the card. Anyway it's not claymore related.

[vogonpoetry]

The 2 GB problem can be solved with a certain memory management scheme.  Level of effort may not be worth it, but Claymore can PM me to discuss.

We're talking about literally millions of dollars at stake here. I don't think any level of effort would be too much.

[Aquazi]

anyway good, I'll sell my Polaris cards asap and buy coins with them for fiat-bitcoin.

no more mining, feels good tbh

[isthc3]

Can't seem to get dual mining working, if I try to enable ETH + DCR I always receive this message:

 DCR: Job timeout, disconnect, retry in 20 sec...

I've tried with this configuration:


setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
EthDcrMiner64.exe -epool us2.ethermine.org:14444 -ewal wallet.rig -epsw x -dpool stratum+tcp://yiimp.ccminer.org:3252 -dwal wallet_here -dpsw x

Any advice? I've tried several different pools, and using a worker + password instead of wallet.

[kaka81994]

My rig have 6 VGA Giga 3g. But whenappear error, 1st VGA is disconect and stopped, then five others still run. And MSI lost one VGA.
This is error in log file. Anyone can help me pls, thanks so much
10:42:50:448   aa4   ETH: GPU0 19.917 Mh/s, GPU1 20.846 Mh/s, GPU2 0.000 Mh/s, GPU3 20.885 Mh/s, GPU4 17.849 Mh/s, GPU5 20.847 Mh/s
10:42:51:729   d00   GPU 1, GpuMiner cu_k1 failed 30, unknown error
10:42:51:745   d00   GPU 1, GpuMiner kx failed 1
10:42:51:792   d40   GPU 5, GpuMiner cu_k1 failed 30, unknown error
10:42:51:807   d80   GPU 4, GpuMiner cu_k1 failed 30, unknown error
10:42:51:823   d28   GPU 3, GpuMiner cu_k1 failed 30, unknown error
10:42:51:823   c6c   GPU 0, GpuMiner cu_k1 failed 30, unknown error
10:42:51:839   914   GPU 2, GpuMiner cu_k1 failed 30, unknown error
10:42:51:776   d00   Set global fail flag, failed GPU1
10:42:51:854   d00   GPU 1 failed
10:42:51:854   d80   GPU 4, GpuMiner kx failed 1
10:42:51:870   d28   GPU 3, GpuMiner kx failed 1
10:42:51:917   c6c   GPU 0, GpuMiner kx failed 1
10:42:51:932   d40   GPU 5, GpuMiner kx failed 1
10:42:51:948   e64   GPU 1, GpuMiner cu_k1 failed 30, unknown error
10:42:51:964   914   GPU 2, GpuMiner kx failed 1
10:42:51:870   d80   Set global fail flag, failed GPU4
10:42:51:995   d80   GPU 4 failed
10:42:51:932   c6c   Set global fail flag, failed GPU0
10:42:52:011   c6c   GPU 0 failed
10:42:52:026   e64   GPU 1, GpuMiner kx failed 1
10:42:52:042   e64   Set global fail flag, failed GPU1
10:42:51:917   d28   Set global fail flag, failed GPU3
10:42:52:057   d28   GPU 3 failed
10:42:51:948   d40   Set global fail flag, failed GPU5
10:42:52:198   d40   GPU 5 failed
10:42:51:979   914   Set global fail flag, failed GPU2
10:42:52:198   914   GPU 2 failed
10:42:52:214   504   GPU 3, GpuMiner cu_k1 failed 30, unknown error
10:42:52:214   e64   GPU 1 failed
10:42:52:214   e60   GPU 0, GpuMiner cu_k1 failed 30, unknown error
10:42:52:214   c88   GPU 5, GpuMiner cu_k1 failed 30, unknown error
10:42:52:229   a9c   GPU 4, GpuMiner cu_k1 failed 30, unknown error
10:42:52:229   da8   GPU 2, GpuMiner cu_k1 failed 30, unknown error
10:42:52:229   504   GPU 3, GpuMiner kx failed 1
10:42:52:229   e60   GPU 0, GpuMiner kx failed 1
10:42:52:261   c88   GPU 5, GpuMiner kx failed 1
10:42:52:261   a9c   GPU 4, GpuMiner kx failed 1
10:42:52:261   da8   GPU 2, GpuMiner kx failed 1
10:42:52:229   504   Set global fail flag, failed GPU3
10:42:52:276   504   GPU 3 failed
10:42:52:261   c88   Set global fail flag, failed GPU5
10:42:52:276   c88   GPU 5 failed
10:42:52:276   da8   Set global fail flag, failed GPU2
10:42:52:292   da8   GPU 2 failed
10:42:52:261   a9c   Set global fail flag, failed GPU4
10:42:52:307   a9c   GPU 4 failed
10:42:52:261   e60   Set global fail flag, failed GPU0
10:42:52:307   e60   GPU 0 failed
10:42:53:682   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:42:53:682   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:42:53:776   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:42:53:776   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:42:53:886   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
0:42:57:292   aa4   ETH: checking pool connection...
10:42:57:292   aa4   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

10:42:57:370   aa4   got 248 bytes
10:42:57:370   aa4   buf: {"id":3,"jsonrpc":"2.0","result":["0x70f4f001d6b3cde7946e54364bdf935cb338fb3325c2d844f2c9d299dcc0262f","0x129656acf5804305816f3dc0b32b47077c8cf4b8724f181efc529a93e4c1385b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3b87e1"]}

10:42:57:386   aa4   parse packet: 247
10:42:57:401   aa4   ETH: job is the same
10:42:57:401   aa4   new buf size: 0
10:42:57:589   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:42:57:589   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:42:57:698   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:42:57:698   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:42:57:807   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:42:57:807   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:42:57:917   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:42:57:917   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:42:58:026   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:42:58:026   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:42:58:136   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:42:58:136   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:42:59:557   aa4   got 248 bytes
10:42:59:557   aa4   buf: {"id":0,"jsonrpc":"2.0","result":["0xc3cd3933f585f9fce0aa8fe7dcd38a4b423735db57bbb2ab042a14c18a5eb1c7","0x129656acf5804305816f3dc0b32b47077c8cf4b8724f181efc529a93e4c1385b","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3b87e2"]}

10:42:59:573   aa4   parse packet: 247
10:42:59:589   aa4   ETH: job changed
10:42:59:589   aa4   new buf size: 0
10:42:59:589   aa4   ETH: 06/20/17-10:42:59 - New job from asia1.ethermine.org:4444
10:42:59:589   aa4   target: 0x0000000112e0be82 (diff: 4000MH), epoch #130
10:42:59:604   aa4   ETH - Total Speed: 0.000 Mh/s, Total Shares: 52, Rejected: 0, Time: 00:24
10:42:59:604   aa4   ETH: GPU0 0.000 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 0.000 Mh/s
10:43:01:511   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:01:511   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:01:620   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:01:620   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:01:729   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:01:729   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:01:839   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:01:839   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:01:948   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:01:948   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:02:058   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:02:058   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:02:167   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:02:167   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:02:276   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:02:276   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:02:370   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:02:370   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:02:479   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:02:479   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:02:573   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:02:573   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:02:683   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:02:683   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:02:698   fc4   GPU0 t=0C fan=0%, GPU1 t=0C fan=0%, GPU2 t=0C fan=0%, GPU3 t=0C fan=0%, GPU4 t=0C fan=0%, GPU5 t=0C fan=0%
10:43:02:698   fc4   em hbt: 0, fm hbt: 32,
10:43:02:698   fc4   watchdog - thread 0 (gpu0), hb time 11516
10:43:02:714   fc4   watchdog - thread 1 (gpu0), hb time 11468
10:43:02:714   fc4   watchdog - thread 2 (gpu1), hb time 11375
10:43:02:714   fc4   watchdog - thread 3 (gpu1), hb time 11281
10:43:02:729   fc4   watchdog - thread 4 (gpu2), hb time 18813
10:43:02:729   fc4   watchdog - thread 5 (gpu2), hb time 18859
10:43:02:729   fc4   watchdog - thread 6 (gpu3), hb time 11563
10:43:02:729   fc4   watchdog - thread 7 (gpu3), hb time 11484
10:43:02:745   fc4   watchdog - thread 8 (gpu4), hb time 11500
10:43:02:745   fc4   watchdog - thread 9 (gpu4), hb time 11297
10:43:02:745   fc4   watchdog - thread 10 (gpu5), hb time 11500
10:43:02:745   fc4   watchdog - thread 11 (gpu5), hb time 11297
10:43:02:761   fc4   WATCHDOG: GPU error, you need to restart miner
10:43:02:839   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:02:839   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:02:948   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:02:948   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:03:058   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:03:058   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:03:167   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:03:167   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:03:276   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:03:276   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:03:370   fc4   NVML: cannot get current temperature, error 999 (an internal driver error occurred)
10:43:03:370   fc4   NVML: cannot get fan speed, error 999 (an internal driver error occurred)
10:43:04:511   fc4   Restarting OK, exit...

[nonsence]

Hi Everybody and Claymore Dev.

I monitoring Claymore V9.5  from epoch 128-130. Hashrate is Down. I used RX480 8GB x6 on hashrate around 175.5 MH/s

epoch 128 : 175.5 MH/s
epoch 129 : 174.3 MH/s
Now epoch 130 : 173.1 MH/s

please help me . Why to resolve this. Thank you

[adaseb]

Hi Everybody and Claymore Dev.

I monitoring Claymore V9.5  from epoch 128-130. Hashrate is Down. I used RX480 8GB x6 on hashrate around 175.5 MH/s

epoch 128 : 175.5 MH/s
epoch 129 : 174.3 MH/s
Now epoch 130 : 173.1 MH/s

please help me . Why to resolve this. Thank you

Its normal.

[nonsence]

Hi Everybody and Claymore Dev.

I monitoring Claymore V9.5  from epoch 128-130. Hashrate is Down. I used RX480 8GB x6 on hashrate around 175.5 MH/s

epoch 128 : 175.5 MH/s
epoch 129 : 174.3 MH/s
Now epoch 130 : 173.1 MH/s

please help me . Why to resolve this. Thank you

Its normal.

Thanks adaseb, Please let me know, why  ? . Thank you

[adaseb]

Hi Everybody and Claymore Dev.

I monitoring Claymore V9.5  from epoch 128-130. Hashrate is Down. I used RX480 8GB x6 on hashrate around 175.5 MH/s

epoch 128 : 175.5 MH/s
epoch 129 : 174.3 MH/s
Now epoch 130 : 173.1 MH/s

please help me . Why to resolve this. Thank you

Its normal.

Thanks adaseb, Please let me know, why  ? . Thank you

Its a bug on a software or hardware level with those types of GPUs.

[edop2005]

Dualmining ETH/SIA on nanopool doesn't work for me. ETH works fine but SC gets job timeouts.

---------------------------------------------------------------------------------
ETH: 06/20/17-10:15:39 - New job from eth-eu1.nanopool.org:9999
ETH - Total Speed: 20.727 Mh/s, Total Shares: 5, Rejected: 0, Time: 00:18
ETH: GPU0 20.727 Mh/s
 SC - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0
 SC: GPU0 0.000 Mh/s
GPU0 t=67C fan=0%
Socket was closed remotely (by pool)
 SC: Job timeout, disconnect, retry in 20 sec...
---------------------------------------------------------------------------------

I used nanopool's autoconfig generator, here s my config

EthDcrMiner64.exe -epool eth-eu1.nanopool.org:9999 -ewal 0xmyethwallet -epsw x -dcoin sia -dpool sia-eu1.nanopool.org:7777 -dwal mysiawallet -dpsw x -ftime 10

Am I the only one? I tried replacing -dcoin sia with -dcoin sc but same result.

Did you change "0xmyethwallet" and "mysiawallet" to your actual wallet addresses?

Yes I replaced both. ETH is mining normally but I only get timeouts for sia. Can you paste your start.bat file? I ll try it and see it it works. Maybe there s something wrong with my SIA address?

[nonsence]

Hi Everybody and Claymore Dev.

I monitoring Claymore V9.5  from epoch 128-130. Hashrate is Down. I used RX480 8GB x6 on hashrate around 175.5 MH/s

epoch 128 : 175.5 MH/s
epoch 129 : 174.3 MH/s
Now epoch 130 : 173.1 MH/s

please help me . Why to resolve this. Thank you

Its normal.

Thanks adaseb, Please let me know, why  ? . Thank you

Its a bug on a software or hardware level with those types of GPUs.

Thank you for your information.