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

[dislorth]

I have 2 rigs and I have been using Clymore 11.02 and my rigs were working perfectly, but Claymore 11.02 is not working anymore, Claymore 11.02 stopped working on my rigs, so I just downloaded Claymore 15.0 but my rigs started getting stocked with this error:
WATCHDOG: GPU 3 hangs in OpenCL call, exit. --- This error in my rig Number 1
WATCHDOG: GPU 0 hangs in OpenCL call, exit. --- This error in my rig Number 2

I think this is a Claymore Bug because Im just getting this errors after downloading Claymore 15.0 with older vertions of Claymore I didnt get any error like this ones.... anyone knows a solution to solve this issue or this Claymore bug?

I have 2 rigs with 6 GPU AMD RX470 4GB each one

Thank you in advance.

What is the command line used to start Claymore?

Are these rigs with windows or linux?

They are Windows 10

The comMand line to start Claymore is:
EthDcrMiner64.exe -epool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -ewal MYWALLETADRESSHERE -epsw x -esm 3 -allpools 1 -estale 0 -dpool stratum+tcp://decred.eu.nicehash.com:3354 -dwal MYWALLETADRESSHERE -dcoin decred

Is it wrong?

[tg88]

EthDcrMiner64.exe -epool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -ewal MYWALLETADRESSHERE -epsw x -esm 3 -allpools 1 -estale 0 -dpool stratum+tcp://decred.eu.nicehash.com:3354 -dwal MYWALLETADRESSHERE -dcoin decred

Is it wrong?

All ok with the command line ...

This error is usually related to bad risers, excessive overclocking or driver issues.

[dislorth]

EthDcrMiner64.exe -epool stratum+tcp://daggerhashimoto.eu.nicehash.com:3353 -ewal MYWALLETADRESSHERE -epsw x -esm 3 -allpools 1 -estale 0 -dpool stratum+tcp://decred.eu.nicehash.com:3354 -dwal MYWALLETADRESSHERE -dcoin decred

Is it wrong?

All ok with the command line ...

This error is usually related to bad risers, excessive overclocking or driver issues.

But it is kind of weird... last week my rigs were working perfectly with Older Claymore version... but this weekend version I was using stopped working so I have had to downloaded the new one Claymore 15.0 and my rigs started getting stocked with this issue

Now I change mining ETH Solo and it is working ok with Claymore 15.0 so it is really weird. If there is a hardware or a software issue it should get stocked with the same issue, dont you think?  

I have another question, I have setup this config in each GPU in my rigs:
Core Voltage: -62 mV
Power Limit: 50%
Temp Limit: 90 ºC
Core clock: 1050 MHz
Memory clock: 1650 MHz

and Im getting this Hashrate:
Hashrate
Current
87.8 MH/s

Average
49.1 MH/s

Reported
132.0 MH/s

Shares
Valid 100%
79
Stale
0

Is it possible to increase this Hashrate average?

[tg88]

Is it possible to increase this Hashrate average?

If your gpus has original bios use claymore's -strap function this will help improve speed.

Watch some videos on youtube, this for example will help you:
https://www.youtube.com/watch?v=Qwq0yGBtqNs

[dislorth]

Is it possible to increase this Hashrate average?

If your gpus has original bios use claymore's -strap function this will help improve speed.

Watch some videos on youtube, this for example will help you:
https://www.youtube.com/watch?v=Qwq0yGBtqNs

Thank you, I going to try video steps.

I have another old rig with 6 GPU EVGA Geforce GTX 1060 3GB video cards and I was wondering if it's possible to use Claymore 15.0 to mine on it.
I was trying it but Claymore doesnt work in this rig. Look at this log:

Code:

09:44:36:800	2984	Check and remove old log files...
09:44:36:801	2984	args: -epool eu1.ethermine.org:4444 -ewal 0xD69af2A796A737A103F12d2f0BCC563a13900E6F -epsw x -rxboost 1 
09:44:36:802	2984	
09:44:36:803	2984	ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
09:44:36:804	2984	º                Claymore's Dual GPU Miner - v15.0               º
09:44:36:804	2984	º              ETH + DCR/SIA/LBC/PASC/BLAKE2S/KECCAK             º
09:44:36:805	2984	º                       Supercharged Edition                     º
09:44:36:806	2984	ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
09:44:36:807	2984	
09:44:36:807	2984	b755 
09:44:37:009	2984	You specified default wallet address, it is good for tests only, for normal mining you must change it to your wallet address!
09:44:37:010	2984	ETH: 1 pool is specified
09:44:37:010	2984	Main Ethereum pool is eu1.ethermine.org:4444
09:44:37:011	2984	DCR: 0 pool is specified
09:44:37:211	2984	OpenCL platform: NVIDIA CUDA
09:44:37:212	2984	AMD OpenCL platform not found 
09:44:37:505	2984	CUDA initializing...

09:44:37:505	2984	NVIDIA Cards available: 6 
09:44:37:506	2984	CUDA Driver Version/Runtime Version: 10.0/8.0
09:44:37:535	2984	GPU #0: GeForce GTX 1060 3GB, 3072 MB available, 9 compute units, capability: 6.1  (pci bus 1:0:0)
09:44:37:538	2984	GPU #1: GeForce GTX 1060 3GB, 3072 MB available, 9 compute units, capability: 6.1  (pci bus 2:0:0)
09:44:37:540	2984	GPU #2: GeForce GTX 1060 3GB, 3072 MB available, 9 compute units, capability: 6.1  (pci bus 4:0:0)
09:44:37:542	2984	GPU #3: GeForce GTX 1060 3GB, 3072 MB available, 9 compute units, capability: 6.1  (pci bus 5:0:0)
09:44:37:544	2984	GPU #4: GeForce GTX 1060 3GB, 3072 MB available, 9 compute units, capability: 6.1  (pci bus 7:0:0)
09:44:37:547	2984	GPU #5: GeForce GTX 1060 3GB, 3072 MB available, 9 compute units, capability: 6.1  (pci bus 8:0:0)
09:44:37:548	2984	Total cards: 6 
09:44:37:549	2984	
All GPUs are 2GB...3GB, miner is completely free in this case, developer fee will not be mined at all.
See Readme for details.

09:44:37:551	2984	
Please consider using "-strap" option to increase mining speed, check Readme for details.

09:44:41:571	2984	NVML version: 10.416.94
09:44:41:620	2984	Driver is not installed! Trying to install it...
09:44:41:625	2984	Driver is in use, try to start miner with "-driver uninstall" parameter.
09:44:43:925	2984	SSL: Imported 36 certificates from local storage
09:44:44:030	2984	No pool specified for Decred! Ethereum-only mining mode is enabled

09:44:44:033	2984	ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

09:44:44:037	2984	ETH: eth-proxy stratum mode
09:44:44:041	2984	Watchdog enabled
09:44:44:046	2984	Remote management (READ-ONLY MODE) is enabled on port 3333
09:44:44:056	2984	

09:44:44:075	22bc	ETH: Stratum - connecting to 'eu1.ethermine.org' <172.65.207.106> port 4444 (unsecure)
09:44:44:231	22bc	sent: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0xD69af2A796A737A103F12d2f0BCC563a13900E6F", "x"], "id": 2, "method": "eth_submitLogin"}

09:44:44:232	22bc	ETH: Stratum - Connected (eu1.ethermine.org:4444) (unsecure)
09:44:44:455	22bc	buf: {"id":2,"jsonrpc":"2.0","result":true}

09:44:44:456	22bc	ETH: Authorized
09:44:44:457	22bc	sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:44:44:712	22bc	buf: {"id":0,"jsonrpc":"2.0","result":["0x8b35e53c4bfae77609cf7884038108f346e4dd30d8c99043e1a20de2dcbe772f","0x5605f1feb945dc2af20b5a16a9e88b88e1c7874022e238fcc070f2f635358d75","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x88d9db"]}

09:44:44:782	f48	Setting DAG epoch #298(3.33GB)...
09:44:48:662	2830	Setting DAG epoch #298 for GPU3
09:44:48:663	ad0	Setting DAG epoch #298 for GPU5
09:44:48:664	ad0	Create GPU buffer for GPU5
09:44:48:669	ad0	CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

09:44:48:675	222c	Setting DAG epoch #298 for GPU4
09:44:48:672	630	Setting DAG epoch #298 for GPU0
09:44:48:672	f48	Setting DAG epoch #298 for GPU2
09:44:48:661	2564	Setting DAG epoch #298 for GPU1
09:44:48:680	222c	Create GPU buffer for GPU4
09:44:48:681	630	Create GPU buffer for GPU0
09:44:48:677	2830	Create GPU buffer for GPU3
09:44:48:683	222c	CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

09:44:48:685	630	CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

09:44:48:687	2830	CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

09:44:48:683	f48	Create GPU buffer for GPU2
09:44:48:684	2564	Create GPU buffer for GPU1
09:44:48:690	2564	CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

09:44:48:691	f48	CUDA error - cannot allocate big buffer for DAG. Check readme.txt for possible solutions.

09:44:49:067	22bc	buf: {"id":0,"jsonrpc":"2.0","result":["0xf6909e48f11bb654eade2e3f43ecb04a45f36b785400c9f583bbd4841dc42fc3","0x5605f1feb945dc2af20b5a16a9e88b88e1c7874022e238fcc070f2f635358d75","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x88d9db"]}

09:44:49:069	22bc	ETH: 11/20/19-09:44:49 - New job from eu1.ethermine.org:4444
09:44:49:070	22bc	target: 0x0000000112e0be82 (diff: 4000MH), epoch 298(3.33GB)
09:44:49:070	22bc	ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:44:49:073	22bc	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
09:44:50:142	22bc	buf: {"id":0,"jsonrpc":"2.0","result":["0x40331ffd562b7ba9b75a289dc12ce2eec2c2206cdd443893f66d51e558b3f1a6","0x5605f1feb945dc2af20b5a16a9e88b88e1c7874022e238fcc070f2f635358d75","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x88d9dc"]}

09:44:50:148	22bc	ETH: 11/20/19-09:44:50 - New job from eu1.ethermine.org:4444
09:44:50:149	22bc	target: 0x0000000112e0be82 (diff: 4000MH), epoch 298(3.33GB)
09:44:50:149	22bc	ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:44:50:152	22bc	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
09:44:50:973	22bc	buf: {"id":0,"jsonrpc":"2.0","result":["0x4f9d9903566c8e73f7d0432c90769e0a331f66586ba1dab7789a8858559b6b66","0x5605f1feb945dc2af20b5a16a9e88b88e1c7874022e238fcc070f2f635358d75","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x88d9dc"]}

09:44:50:977	22bc	ETH: 11/20/19-09:44:50 - New job from eu1.ethermine.org:4444
09:44:50:977	22bc	target: 0x0000000112e0be82 (diff: 4000MH), epoch 298(3.33GB)
09:44:50:978	22bc	ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:44:50:979	22bc	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
09:44:51:672	ad0	Set global fail flag, failed GPU5
09:44:51:677	ad0	GPU 5 failed
09:44:51:680	de0	Setting DAG epoch #298 for GPU5
09:44:51:684	de0	GPU 5, CUDA error 11 - cannot write buffer for DAG

09:44:51:686	222c	Set global fail flag, failed GPU4
09:44:51:688	222c	GPU 4 failed
09:44:51:690	2638	Setting DAG epoch #298 for GPU4
09:44:51:690	2830	Set global fail flag, failed GPU3
09:44:51:688	630	Set global fail flag, failed GPU0
09:44:51:695	630	GPU 0 failed
09:44:51:696	b34	Setting DAG epoch #298 for GPU0
09:44:51:697	2638	GPU 4, CUDA error 11 - cannot write buffer for DAG

09:44:51:699	2830	GPU 3 failed
09:44:51:695	f48	Set global fail flag, failed GPU2
09:44:51:692	2564	Set global fail flag, failed GPU1
09:44:51:702	2564	GPU 1 failed
09:44:51:699	2364	Setting DAG epoch #298 for GPU3
09:44:51:705	b34	GPU 0, CUDA error 11 - cannot write buffer for DAG

09:44:51:706	2964	Setting DAG epoch #298 for GPU1
09:44:51:707	2364	GPU 3, CUDA error 11 - cannot write buffer for DAG

09:44:51:705	890	Setting DAG epoch #298 for GPU2
09:44:51:709	f48	GPU 2 failed
09:44:51:710	2964	GPU 1, CUDA error 11 - cannot write buffer for DAG

09:44:51:711	890	GPU 2, CUDA error 11 - cannot write buffer for DAG

09:44:54:116	22bc	buf: {"id":0,"jsonrpc":"2.0","result":["0x60df3196f0b58275fe0f1a9bb3b8a43790f40e68b12038d9f1b84480c4910200","0x5605f1feb945dc2af20b5a16a9e88b88e1c7874022e238fcc070f2f635358d75","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x88d9dc"]}

09:44:54:119	22bc	ETH: 11/20/19-09:44:54 - New job from eu1.ethermine.org:4444
09:44:54:120	22bc	target: 0x0000000112e0be82 (diff: 4000MH), epoch 298(3.33GB)
09:44:54:120	22bc	ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:44:54:123	22bc	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
09:44:54:687	de0	Set global fail flag, failed GPU5
09:44:54:688	de0	GPU 5 failed
09:44:54:699	2638	Set global fail flag, failed GPU4
09:44:54:701	2638	GPU 4 failed
09:44:54:707	b34	Set global fail flag, failed GPU0
09:44:54:707	b34	GPU 0 failed
09:44:54:709	2364	Set global fail flag, failed GPU3
09:44:54:710	2364	GPU 3 failed
09:44:54:712	2964	Set global fail flag, failed GPU1
09:44:54:713	2964	GPU 1 failed
09:44:54:713	890	Set global fail flag, failed GPU2
09:44:54:714	890	GPU 2 failed
09:44:54:716	22bc	ETH: checking pool connection...
09:44:54:717	22bc	sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:44:55:334	22bc	buf: {"id":0,"jsonrpc":"2.0","result":["0x60df3196f0b58275fe0f1a9bb3b8a43790f40e68b12038d9f1b84480c4910200","0x5605f1feb945dc2af20b5a16a9e88b88e1c7874022e238fcc070f2f635358d75","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x88d9dc"]}

09:44:58:333	22bc	buf: {"id":0,"jsonrpc":"2.0","result":["0x43cf35072216568b3cc9a4ff3277777fd4bb10c6469e23ea7db82b51f168cecf","0x5605f1feb945dc2af20b5a16a9e88b88e1c7874022e238fcc070f2f635358d75","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x88d9dc"]}

09:44:58:337	22bc	ETH: 11/20/19-09:44:58 - New job from eu1.ethermine.org:4444
09:44:58:338	22bc	target: 0x0000000112e0be82 (diff: 4000MH), epoch 298(3.33GB)
09:44:58:339	22bc	ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:44:58:340	22bc	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
09:45:01:028	22bc	buf: {"id":0,"jsonrpc":"2.0","result":["0xece5fa87eae1f2c48863707460bff24a783306faabf6c2895362cd16b11805c7","0x5605f1feb945dc2af20b5a16a9e88b88e1c7874022e238fcc070f2f635358d75","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x88d9dd"]}

09:45:01:030	22bc	ETH: 11/20/19-09:45:01 - New job from eu1.ethermine.org:4444
09:45:01:031	22bc	target: 0x0000000112e0be82 (diff: 4000MH), epoch 298(3.33GB)
09:45:01:034	22bc	ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:45:01:035	22bc	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
09:45:01:116	22bc	buf: {"id":0,"jsonrpc":"2.0","result":["0xa598669dd85f9fb3aa379f8ef949780f5a155b1799794c05f3d22c1106db4a64","0x5605f1feb945dc2af20b5a16a9e88b88e1c7874022e238fcc070f2f635358d75","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x88d9dd"]}

09:45:01:119	22bc	ETH: 11/20/19-09:45:01 - New job from eu1.ethermine.org:4444
09:45:01:120	22bc	target: 0x0000000112e0be82 (diff: 4000MH), epoch 298(3.33GB)
09:45:01:121	22bc	ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:45:01:121	22bc	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
09:45:04:717	22bc	sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x000000000000000000000000000000000000000000000000000000000e4a4d69"]}

09:45:04:733	22bc	ETH: checking pool connection...
09:45:04:733	22bc	sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:45:05:351	22bc	buf: {"id":0,"jsonrpc":"2.0","result":["0x8e8056ebe143859b809f521c90b6e53c0c2fd7a90547cef422691a7b4da9ec87","0x5605f1feb945dc2af20b5a16a9e88b88e1c7874022e238fcc070f2f635358d75","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x88d9dd"]}

09:45:05:352	22bc	ETH: 11/20/19-09:45:05 - New job from eu1.ethermine.org:4444
09:45:05:353	22bc	target: 0x0000000112e0be82 (diff: 4000MH), epoch 298(3.33GB)
09:45:05:354	22bc	ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00
09:45:05:354	22bc	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
09:45:07:107	1f94	GPU0 t=32C fan=100% P=26W, GPU1 t=30C fan=100% P=28W, GPU2 t=32C fan=100% P=26W, GPU3 t=29C fan=100% P=26W, GPU4 t=29C fan=100% P=26W, GPU5 t=31C fan=100% P=27W
09:45:07:109	1f94	Total GPUs power consumption: 159 Watts
09:45:07:112	22bc	buf: {"id":6,"jsonrpc":"2.0","result":true}
{"id":0,"jsonrpc":"2.0","result":["0x8e8056ebe143859b809f521c90b6e53c0c2fd7a90547cef422691a7b4da9ec87","0x5605f1feb945dc2af20b5a16a9e88b88e1c7874022e238fcc070f2f635358d75","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x88d9dd"]}

09:45:07:112	22bc	remove first packet 254
09:45:07:247	1eb4	em hbt: 16, fm hbt: 16, 
09:45:07:247	1eb4	watchdog - thread 0 (gpu0), hb time 15547
09:45:07:248	1eb4	watchdog - thread 1 (gpu0), hb time 15547
09:45:07:248	1eb4	watchdog - thread 2 (gpu1), hb time 15547
09:45:07:248	1eb4	watchdog - thread 3 (gpu1), hb time 15547
09:45:07:249	1eb4	watchdog - thread 4 (gpu2), hb time 15547
09:45:07:249	1eb4	watchdog - thread 5 (gpu2), hb time 15547
09:45:07:250	1eb4	watchdog - thread 6 (gpu3), hb time 15547
09:45:07:250	1eb4	watchdog - thread 7 (gpu3), hb time 15547
09:45:07:251	1eb4	watchdog - thread 8 (gpu4), hb time 15547
09:45:07:251	1eb4	watchdog - thread 9 (gpu4), hb time 15547
09:45:07:251	1eb4	watchdog - thread 10 (gpu5), hb time 15547
09:45:07:252	1eb4	watchdog - thread 11 (gpu5), hb time 15547
09:45:07:252	1eb4	WATCHDOG: GPU error, you need to restart miner :( 
09:45:08:522	1eb4	Restarting OK, exit...

Is there a way to mine with Claymore 15.0 with this rig?

[prostor]

Is there a way to mine with Claymore 15.0 with this rig?

you must mining only fork eth in 3Gb devices - Metaverse(ETP), QuarkChain(QKC), Ubiq(UBQ), ect

[MATHReX]

Thank you, I going to try video steps.

I have another old rig with 6 GPU EVGA Geforce GTX 1060 3GB video cards and I was wondering if it's possible to use Claymore 15.0 to mine on it.

Is there a way to mine with Claymore 15.0 with this rig?

https://investoon.com/tools/dag_size

Here, you can see the DAG size for ETH and ETC has surpassed 3GB so you won't be able to mine ETH or ETC.
You can mine other Ethash based coins which have DAG less than 3GB and use Claymore for it.

Also, in the log, you haven't set your primary address so it is trying to mine at default address.

[nmrsa89]

Hey guys, i used to read last 50 pages before but i didnt find the solve. I have 5 rigs with 8x470/480/580 and all of them worked perfectly utill couple days ago... with claymore v10.. i was getting about 30hs from all of them and now when i tryied clayomor v15 only about 9hs.. im running it on win10, and used to overclock them with .bat file... Please can anyone help me, or show me the post where i can find the answers...

[Binary100100]

Hey guys, i used to read last 50 pages before but i didnt find the solve. I have 5 rigs with 8x470/480/580 and all of them worked perfectly utill couple days ago... with claymore v10.. i was getting about 30hs from all of them and now when i tryied clayomor v15 only about 9hs.. im running it on win10, and used to overclock them with .bat file... Please can anyone help me, or show me the post where i can find the answers...

Sounds like you are using Graphics Mode instead of Compute Mode.

[nmrsa89]

Hey guys, i used to read last 50 pages before but i didnt find the solve. I have 5 rigs with 8x470/480/580 and all of them worked perfectly utill couple days ago... with claymore v10.. i was getting about 30hs from all of them and now when i tryied clayomor v15 only about 9hs.. im running it on win10, and used to overclock them with .bat file... Please can anyone help me, or show me the post where i can find the answers...

Sounds like you are using Graphics Mode instead of Compute Mode.

Looks like working now  i reinstalled prevous working good drivers instead of latest, and added some new comands i .bat file, "-rxboost 1 -strap 2" and worked like a charm  with newest drivers wasnt working even with that commads. i still have red line to try to use -driver unnistal, and driver alredy running but it s working good so far getting expected hashes... Thank you.

[carel]

will dual mining support be added nervos (ckb)?

[Marvell2]

its there a way to use just the straps and disable the miner ?

[dortortz]

Are the 1050ti still giving "cannot write dag" errors on windows? And has anyone found a new fix for it?

[tg88]

its there a way to use just the straps and disable the miner ?

Under the circumstances that's not possible since gpu will return old strap and memory clock when miner is closed.

[newcomer01]

17:04:11:200   1dbc   start building OpenCL program for GPU 0...
17:04:11:874   1dbc   done
17:04:12:082   1dbc   start building OpenCL program for GPU 1...
17:04:12:459   1dbc   done
17:04:12:665   1dbc   start building OpenCL program for GPU 2...
17:04:13:040   1dbc   done
17:04:13:247   1dbc   start building OpenCL program for GPU 3...
17:04:13:623   1dbc   done
17:04:13:830   1dbc   start building OpenCL program for GPU 4...
17:04:14:191   1dbc   done
17:04:14:398   1dbc   start building OpenCL program for GPU 5...
17:04:14:760   1dbc   done
17:04:15:028   1dbc   GPU #0: algorithm ASM 1
17:04:15:102   1dbc   GPU #1: algorithm ASM 1
17:04:15:159   1dbc   GPU #2: algorithm ASM 1
17:04:15:219   1dbc   GPU #3: algorithm ASM 1
17:04:15:291   1dbc   GPU #4: algorithm ASM 1
17:04:15:350   1dbc   GPU #5: algorithm ASM 1
17:04:15:351   1dbc   cudaGetDeviceCount failed (35, CUDA driver version is insufficient for CUDA runtime version), probably no CUDA devices
17:04:15:352   1dbc   No NVIDIA CUDA GPUs detected.
17:04:15:352   1dbc   Total cards: 6
17:04:15:354   1dbc   No NVIDIA cards in the list, NVML library will not be used.
17:04:15:354   1dbc   Driver is not installed! Trying to install it...
17:04:15:359   1dbc   Driver is in use, try to start miner with "-driver uninstall" parameter.
17:04:16:423   1dbc   SSL: Imported 40 certificates from local storage
17:04:16:499   193c   ETH: Stratum - connecting to 'us1.ethpool.org' <172.65.229.54> port 3333 (unsecure)
17:04:16:524   1dbc   No pool specified for Decred! Ethereum-only mining mode is enabled

17:04:16:525   1dbc   ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)

17:04:16:527   1dbc   ETH: eth-proxy stratum mode
17:04:16:527   1dbc   Watchdog enabled
17:04:16:528   1dbc   Remote management (READ-ONLY MODE) is enabled on port 3333


Hello, can someone pls assist to advise how can I fix this error?

17:04:15:354   1dbc   Driver is not installed! Trying to install it...
17:04:15:359   1dbc   Driver is in use, try to start miner with "-driver uninstall" parameter.

Thank you!

[MATHReX]

Are the 1050ti still giving "cannot write dag" errors on windows? And has anyone found a new fix for it?

You mean cannot allocate DAG because of 4GB video memory in 1050ti.
See, Windows OS reserves some memory in a dedicated VGA. So even though DAG size of ETH hasn't reached 4GB, you won't be able to mine in Windows no matter what.
The only solution can be to use a Linux distro to mine as there are no such problems.

[KAOS247365]

Have similar issue,

Updated my miners to Claymore 15 and now they just keep crashing...

8 x Asus RX 580 OC 8GB edition per mining rig
Windows 10 with Latest Update
8GB DDR4 Ram on Motherboard
Additional 24GB Virtual Memory.
120GB SSD drive.

Using older AMD ASUS Drivers that were working fine before update

Everything was working fine until new Claymore 15 released...hoping it is a bug and will be fixed soon.

Some of the GPUs start up fine but then the miner crashes and restarts

I am using latest version of Awesome Miner to run my mining farm. Anyone else having similar issues?

Any help would be much much appreciated.

Cheers

[Binary100100]

Have similar issue,

Updated my miners to Claymore 15 and now they just keep crashing...

8 x Asus RX 580 OC 8GB edition per mining rig
Windows 10 with Latest Update
8GB DDR4 Ram on Motherboard
Additional 24GB Virtual Memory.
120GB SSD drive.

Using older AMD ASUS Drivers that were working fine before update

Everything was working fine until new Claymore 15 released...hoping it is a bug and will be fixed soon.

Some of the GPUs start up fine but then the miner crashes and restarts

I am using latest version of Awesome Miner to run my mining farm. Anyone else having similar issues?

Any help would be much much appreciated.

Cheers

Did you try increasing your virtual memory? I always heard that you should have a 1:1 for your combined card memory. So in your case I'd go with 64gb. On a 120GB hard drive that might be difficult. Personally I have 500GB SSD on each of my rigs. Maybe you can add another cheap SSD and just use that for VM?

You could also try just enabling one card at a time and see how many work?
Miner Properties > GPU Selection at the bottom > Use selected from list > (Select just one or two then hit OK) > See if it runs (stable.) If so, add another until it stops.

I also use Awesome Miner for all of my rigs and I'm not having any issues with Claymore 15. Alternatively, try PhoenixMiner. If you have the same problem then it's probably not with the software.

[Marvell2]

its there a way to use just the straps and disable the miner ?

Under the circumstances that's not possible since gpu will return old strap and memory clock when miner is closed.

damn k

[dingdongtobias]

https://bitcointalk.org/index.php?topic=5059817.msg53174391#msg53174391

We will shortly release a Ethash miner testing tool, it's just a simple open source node.js project. You will be able to run controlled long-running tests on all miners. The reason this is important is that the displayed hashrates of Claymore and Phoenix are just bullshit. They both add +1.5% or more of fake hashrate. I don't ask anyone to buy these claims without being able to verify it themselves though, which is why we'll release the tool (which acts as a low diff fake pool with a static epoch and controlled job update mechanism) and everyone can see for themselves if they are willing to mine air for ~24h. To verify that we're not insane, we've also reverse engineered both miners, analysed their kernels, traced their OpenCL enqueue calls, and the evidence is clear.

Plenty of people have already pointed this out just by logging all shares over time, but it's really hard to prove anything. You need controlled runs of (preferably) 1 million shares, which is more or less impossible without controlling the environment properly. Another simple way is just to find a big farm from e.g. the frontpage of ethermine.org (found blocks) and check the difference between their reported and accepted hashrate.

Here is one example: https://ethermine.org/miners/6F714AaAAF72977267601cC1cADC49fb3966Ff89/dashboard

Reported: 3.206 TH/s, Accepted: 3.111 TH/s, difference -2.97%. I'm fairly certain this is Phoenix miner. Why do we have a diff of -3%? The dev fee is 0.65%, and there are 1% stale shares, and this is a HUGE sample set that should converge nicely. Contrary to what people seem to believe, the additional -1.35% just should _not_ disappear. For comparison, here is a run using our soon-to-be-released testing tool for 247k shares on Phoenix 4.7c:

Code:

Hashrates for 1 active connections:
    Global hashrate: 228.51 MH/s vs 235.43 MH/s avg reported [diff -2.94%] (A247366:S1575:R0 shares, 93582 secs)
    Global stats: 99.37% acc, 0.63% stale, 0% rej.
    [1] hashrate:  228.51 MH/s vs 235.43 MH/s avg reported [diff -2.94%] (A247366:S1575:R0 shares, 93582 secs)


Look at that, a diff of -2.94% between the reported and accepted hashrate, what a coincidence? To be fair though, 247k shares is only good for a +-0.5% estimate at 99% confidence, so we must treat the value accordingly. The point is that neither CM nor PM can never ever produce a poolside hashrate over time that matches their displayed hashrates.

Sorry for a long rant to your simple question, the bigger point I'm trying to make is this: unless miners start accepting that CM and PM are bullshitting their displayed hashrates, "comparing" CM/PM/TRM/Ethminer is pointless, you'll just be stating that CM and PM are much better than what they really are.