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

[goodbitprofit]

I'm getting the following error when mining "ETH only" at Suprnova.cc:

Code:

ETH: Received error: {"id":15,"result":null,"error":[21,"jobnotfound"]}

My rig have multiple Nvidia GPUs. I'm runing Ubuntu 16.04 with CUDA toolkit 9.2.

This error is sporadically displayed.

Do I need to change some configuration?

Thank you!

i get this error whnever the devfee mining starts

Just add in the line -allpools 1 -allcoins 1

[Abhram]

Why there is no possibility for linux version to set core and memory voltage in config file. Is it problem of amd gpu pro or linux issue?

[blackwhite5674]

Any plans in future releases to display total stale shares?

[john1010]

I have mixed rx 570 cards with different bios memory, my problem is whan i launch the claymore miner my rig hangs and after that it restarted.. I need someone to help me regarding of this issue.. Thanks

[MekMekPL]

Hello

I have problem, with restart after timer and creating DAG.
I get occassionally problems with DAG creation when miner restart after timer... never problem when startup manually.

I PUT -GSER 4 to delay every card but that does not help.. do you think PSU is the issue ?

04:46:36:967   18cc   parse packet: 242
04:46:36:967   18cc   ETH: job is the same
04:46:36:967   18cc   new buf size: 0
04:46:39:186   14c8   GPU1 DAG creation time - 6667 ms
04:46:39:186   14c8   Setting DAG epoch #174 for GPU1 done
04:46:39:186   c4   Setting DAG epoch #174 for GPU2
04:46:39:186   c4   Create GPU buffer for GPU2
04:46:39:592   c4   GPU 2, GpuMiner cu_kd failed 4 (0), unspecified launch failure
04:46:39:592   c4   GPU 2, Calc DAG failed!
04:46:39:623   1ac8   GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
04:46:39:623   1f24   GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
04:46:39:623   103c   GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
04:46:39:623   1ac8   GPU 1, GpuMiner kx failed 1
04:46:39:623   1f24   GPU 0, GpuMiner kx failed 1
04:46:39:623   103c   GPU 4, GpuMiner kx failed 1
04:46:39:623   1ac8   Set global fail flag, failed GPU1
04:46:39:623   1ac8   GPU 1 failed
04:46:39:623   14c8   GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
04:46:39:623   1f24   Set global fail flag, failed GPU0
04:46:39:623   1f24   GPU 0 failed
04:46:39:623   56c   GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
04:46:39:623   103c   Set global fail flag, failed GPU4
04:46:39:623   103c   GPU 4 failed
04:46:39:623   116c   GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
04:46:39:623   14c8   GPU 1, GpuMiner kx failed 1
04:46:39:623   56c   GPU 0, GpuMiner kx failed 1
04:46:39:623   116c   GPU 4, GpuMiner kx failed 1
04:46:39:623   14c8   Set global fail flag, failed GPU1
04:46:39:639   14c8   GPU 1 failed
04:46:39:623   56c   Set global fail flag, failed GPU0
04:46:39:623   116c   Set global fail flag, failed GPU4
04:46:39:639   116c   GPU 4 failed
04:46:39:639   56c   GPU 0 failed
04:46:40:107   176c   Setting DAG epoch #174 for GPU3
04:46:40:107   176c   Create GPU buffer for GPU3
04:46:40:107   176c   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

[tg88]

Hello

I have problem, with restart after timer and creating DAG.
I get occassionally problems with DAG creation when miner restart after timer... never problem when startup manually.

I PUT -GSER 4 to delay every card but that does not help.. do you think PSU is the issue ?

04:46:36:967   18cc   parse packet: 242
04:46:36:967   18cc   ETH: job is the same
04:46:36:967   18cc   new buf size: 0
04:46:39:186   14c8   GPU1 DAG creation time - 6667 ms
04:46:39:186   14c8   Setting DAG epoch #174 for GPU1 done
04:46:39:186   c4   Setting DAG epoch #174 for GPU2
04:46:39:186   c4   Create GPU buffer for GPU2
04:46:39:592   c4   GPU 2, GpuMiner cu_kd failed 4 (0), unspecified launch failure
04:46:39:592   c4   GPU 2, Calc DAG failed!
04:46:39:623   1ac8   GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
04:46:39:623   1f24   GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
04:46:39:623   103c   GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
04:46:39:623   1ac8   GPU 1, GpuMiner kx failed 1
04:46:39:623   1f24   GPU 0, GpuMiner kx failed 1
04:46:39:623   103c   GPU 4, GpuMiner kx failed 1
04:46:39:623   1ac8   Set global fail flag, failed GPU1
04:46:39:623   1ac8   GPU 1 failed
04:46:39:623   14c8   GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
04:46:39:623   1f24   Set global fail flag, failed GPU0
04:46:39:623   1f24   GPU 0 failed
04:46:39:623   56c   GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
04:46:39:623   103c   Set global fail flag, failed GPU4
04:46:39:623   103c   GPU 4 failed
04:46:39:623   116c   GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
04:46:39:623   14c8   GPU 1, GpuMiner kx failed 1
04:46:39:623   56c   GPU 0, GpuMiner kx failed 1
04:46:39:623   116c   GPU 4, GpuMiner kx failed 1
04:46:39:623   14c8   Set global fail flag, failed GPU1
04:46:39:639   14c8   GPU 1 failed
04:46:39:623   56c   Set global fail flag, failed GPU0
04:46:39:623   116c   Set global fail flag, failed GPU4
04:46:39:639   116c   GPU 4 failed
04:46:39:639   56c   GPU 0 failed
04:46:40:107   176c   Setting DAG epoch #174 for GPU3
04:46:40:107   176c   Create GPU buffer for GPU3
04:46:40:107   176c   CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

Increase virtual memory on windows...

[Bigdrago]

So... what´s fastest and cheapest of Claymore, Phoenix and Ethminer?

[Teress]

Any plans in future releases to display total stale shares?

I would like to have this option too. And average hashrate over 5min / 60min / 6h. / 12h. / 20h. period.

[venico]

Hi Everyone

I am trying to filter the output of EthDcrMiner64.exe , I am trying something like:

EthDcrMiner64.exe | findstr eth

the result is basically a blank terminal, until ctrl-C and exit.
At that point, all the output is emitted and filtered by the findstr in one shot. Instead, I would love to see it progressively same way as running without  | findstr ...


Any suggestion?

Note:
I cannot use the logfile, I need to filter the output.

Thanks

[john1010]

Hi pals! What is the best amd driver for this version of claymore, what is your recommendation, kindly give me some of your thoughts.. Thanks

[Viaggiatore]

ok thx !
 

yes you can mine xvg but finding a decent pool is mission impossible. 

I have no problems with the xvg pool but the profit margin of this coin is such that I do not see the point in its extraction. Dcr is more profitable. This provided that the profit margin of dcr fell 3 times. It seems to me that dual mining is losing its relevance. Asics destroys all algorithms that allow mining in dual mode.

dual mining profit is from mining and holding not current prices
dcr i dont dual mine anymore cuz its even less coins, for me since xvg does not have an
asic miner yet its good to dual one it in the thousands and hold for a year or two

But there is also the problem that crappy XVG pools totally disrupt also ETH mining, don't know why but I lose a lot of ETH average hash because of XVG pool disconnecting and reconnecting many many times, so now I'm doing solo mining

[tenmoi]

Hi,
Claymore reports my total shares are 200, but when I look at the share tab on nanopool the “current shares” row reads 80.
There are other rows, which read 112,114 in rows “1 hour ago”, “2 hours ago” respectively. How do I interpret these numbers? 112 + 114 + 80 is ways greater than 200!

Thank you.

[infectedmushi]

i just had

CUDA error 4 - cannot write buffer for DAG

Code:

11:53:20:698	18b0	GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
11:53:20:698	18b0	GPU 4, GpuMiner kx failed 1
11:53:20:698	1ee8	sent: 225
11:53:20:714	10c4	GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
11:53:20:729	b74	GPU 5, GpuMiner cu_k1 failed 4, unspecified launch failure
11:53:20:729	b74	GPU 5, GpuMiner kx failed 1
11:53:20:745	b74	Set global fail flag, failed GPU5
11:53:20:745	ed4	GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
11:53:20:760	ed4	GPU 3, GpuMiner kx failed 1
11:53:20:776	10c4	GPU 0, GpuMiner kx failed 1
11:53:20:807	13ec	GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
11:53:20:807	1de0	GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
11:53:20:839	b74	GPU 5 failed
11:53:20:854	efc	GPU 5, GpuMiner cu_k1 failed 4, unspecified launch failure
11:53:20:854	efc	GPU 5, GpuMiner kx failed 1
11:53:20:854	efc	Set global fail flag, failed GPU5
11:53:20:854	efc	GPU 5 failed
11:53:20:854	13ec	GPU 1, GpuMiner kx failed 1
11:53:20:854	13ec	Set global fail flag, failed GPU1
11:53:20:854	13ec	GPU 1 failed
11:53:20:760	ed4	Set global fail flag, failed GPU3
11:53:20:854	ed4	GPU 3 failed
11:53:20:854	1de0	GPU 2, GpuMiner kx failed 1
11:53:20:854	1de0	Set global fail flag, failed GPU2
11:53:20:854	1de0	GPU 2 failed
11:53:20:807	10c4	Set global fail flag, failed GPU0
11:53:20:885	10c4	GPU 0 failed
11:53:20:885	5a8	GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure
11:53:20:885	1394	GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure
11:53:20:901	1cd0	GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure
11:53:20:901	1cd0	GPU 1, GpuMiner kx failed 1
11:53:20:901	59c	GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure
11:53:20:901	5a8	GPU 0, GpuMiner kx failed 1
11:53:20:901	1394	GPU 2, GpuMiner kx failed 1
11:53:20:698	18b0	Set global fail flag, failed GPU4
11:53:20:901	1cd0	Set global fail flag, failed GPU1
11:53:20:901	59c	GPU 3, GpuMiner kx failed 1
11:53:20:901	5a8	Set global fail flag, failed GPU0
11:53:20:901	1394	Set global fail flag, failed GPU2
11:53:20:901	13b8	GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure
11:53:20:901	18b0	GPU 4 failed
11:53:20:901	1cd0	GPU 1 failed
11:53:20:901	59c	Set global fail flag, failed GPU3
11:53:20:917	5a8	GPU 0 failed
11:53:20:917	1394	GPU 2 failed
11:53:20:917	13b8	GPU 4, GpuMiner kx failed 1
11:53:20:917	59c	GPU 3 failed
11:53:20:917	13b8	Set global fail flag, failed GPU4
11:53:20:917	13b8	GPU 4 failed
11:53:25:448	12d8	srv_thr cnt: 1, IP: 192.168.1.68
11:53:25:448	12d8	recv: 51
11:53:25:448	12d8	srv pck: 50
11:53:25:464	12d8	srv bs: 0
11:53:25:464	12d8	sent: 196
11:53:26:605	1548	buf: {"id":0,"jsonrpc":"2.0","result":["0x377e4d3a4c19416e09053a0dbf13301255827e3b9315086f09e2c21132c6198b","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4fb71a"]}

11:53:26:605	1548	ETH: 03/09/18-11:53:26 - New job from eu1.ethermine.org:5555
11:53:26:605	1548	target: 0x0000000112e0be82 (diff: 4000MH), epoch 174(2.36GB)
11:53:26:605	1548	ETH - Total Speed: 0.000 Mh/s, Total Shares: 1969, Rejected: 1, Time: 11:55
11:53:26:605	1548	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
11:53:27:777	1548	ETH: checking pool connection...
11:53:27:777	1548	sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

11:53:27:824	1548	buf: {"id":3,"jsonrpc":"2.0","result":["0x377e4d3a4c19416e09053a0dbf13301255827e3b9315086f09e2c21132c6198b","0x32a2478e57a4b36e5f5e5420e5443a5a82dac6ff01a0548737fada91d743d7d0","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x4fb71a"]}

11:53:30:449	1830	srv_thr cnt: 1, IP: 192.168.1.68
11:53:30:449	1830	recv: 51
11:53:30:449	1830	srv pck: 50
11:53:30:465	1830	srv bs: 0
11:53:30:465	1830	sent: 196
11:53:31:824	4d8	em hbt: 15, fm hbt: 15, 
11:53:31:824	4d8	watchdog - thread 0 (gpu0), hb time 11312
11:53:31:824	4d8	watchdog - thread 1 (gpu0), hb time 11125
11:53:31:824	4d8	watchdog - thread 2 (gpu1), hb time 11187
11:53:31:824	4d8	watchdog - thread 3 (gpu1), hb time 11312
11:53:31:824	4d8	watchdog - thread 4 (gpu2), hb time 11297
11:53:31:840	4d8	watchdog - thread 5 (gpu2), hb time 11188
11:53:31:840	4d8	watchdog - thread 6 (gpu3), hb time 11188
11:53:31:840	4d8	watchdog - thread 7 (gpu3), hb time 11313
11:53:31:840	4d8	watchdog - thread 8 (gpu4), hb time 13906
11:53:31:840	4d8	watchdog - thread 9 (gpu4), hb time 11172
11:53:31:840	4d8	watchdog - thread 10 (gpu5), hb time 11266
11:53:31:840	4d8	watchdog - thread 11 (gpu5), hb time 11406
11:53:31:855	4d8	WATCHDOG: GPU error, you need to restart miner :( 
11:53:33:081	4d8	Restarting OK, exit...

this happened after 12h .. using same OC settings, i was able to run phoenix miner for 48h w/o a single error.

i messed with the "-eres" option, raised the value. hope it helps.

[Claymore]

UPDATE: I improved support for systems with a lot of GPUs ( > 8 ) and slow CPU: less CPU load, EthMan works fine now. I will release new version within a few days, also some other improvements will be included.

[sir4o]

Noob here.  Canadian one at that.

I calculate NH is taking about 10%.  That's a lot.   I've read where I can set  up an exchange to automatically sell ETH and Decred to bitcoin?  Anyone here doing this?

I'm guessing as the Dragonmint blake 256 miner come online those coins will quickly not be profitable.

I just love it when I ask an important question and its the very last post on a page.

Wrong thread, better create your own and make sure you ask the important question once at the start of each page.

[peterboy1]

UPDATE: I improved support for systems with a lot of GPUs ( > 8 ) and slow CPU: less CPU load, EthMan works fine now. I will release new version within a few days, also some other improvements will be included.

Great, I hope you included fix for fan control issue wherein fan controls are not accurate.

OS: Win 10 1709
Driver: Adrenalin Dec Update
GPU: Spahhire Nitro+ RX570 and Powercolor Red Devil RX570

example:
-tt -60, fan is not on 60% but +/- 10%, therefore ~70

the same with fanmin and fanmax, they are above/off desired settings.

[alex_85]

Anyone with RX580 Nitro+ 8GB cards dual mining on ethermine.org -ETH and XVG on nlpool with less than 3% stale shares ?

I have avg 5% stale shares - sometimes 7,8 and sometimes 3 %

ps.
i will be waitimg for the new update from Claymore as i have 10 gpus rig and i have intel i3 6100 processor to see the difference

[Ursul0]

@Claymore thx for the nice update. v 11.2 hash rate increase is highly appreciated:)
Can you maybe add sorting to Manager app, so one could click on "Running Time" or "Name" ...etc to get it in certain order?

[MaxMidnite]

UPDATE: I improved support for systems with a lot of GPUs ( > 8 ) and slow CPU: less CPU load, EthMan works fine now. I will release new version within a few days, also some other improvements will be included.

Hey man, what about Claymore's CryptoNight AMD GPU Miner, no updates for this :-((

[mine_phun]

Hello Claymore Dual miners,

Are you looking for more profit? Start today with triple mining!

You can mine all available coins with Blake2s and Keccak algorithms in our pool NLpool for Dual mining, but now we also added Yenten (A coin for CPU mining) so you can do triple mining.

For this you need CPU miner : Download here

With CPU miner you can just run : cpuminer-aes-avx2 -t 10 -a yescryptr16 -o stratum+tcp:/mine.nlpool.nl:6333 -u <walletaddress> -p c=YTN
Please note that if you have a slow CPU, you might want to add --cpu-priority 1 so it will not influence your hashrate.

We have been tested to be the most profitable pool, so try us!

NLPool is a Dutch miningpool running in Amsterdam the Netherlands. The pool has been setup to provide a good and stable pool for people who are located in the Netherlands or Benelux. Our pool is dedicated to have less latency meaning lower risks for stale shares. This means you will get higher profits.

Our philosophy:
- Performance
- Profit by lowering latency and stale shares
- Security
- Minimum fees

Our mining fee will be of 0% for all Blake2S algo coins until April 1st. After the launch period, it will be fixed between 0.5% and 1%

How to contact us ?
E-mail: nlpool.nl@outlook.com
Telegram: : t.me/nlpool

Key features:
- Amsterdam dedicated server with DDos Protection
- Small mining fee : 0% during the 2 months launch period. After, between 0,5% and 1%
- Anonymous and no registration !
- Hourly payments
- yiimp multi-algo with several coins
- Everything is tested on a second non-productive server before launching to minimize your risks on the actual mining pool. (new stratum, webpages changes, payments and other code updates)