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

[mewhoyou]

Guys,

Sorry to bring the bad news, but dual miner might be over in a few months.

Asic miners on the market are now spiking up the difficulty for LBC/DCR/PASC/SIA

Baikal Giant-B - Blake256R14/Blake256R8/Blake2B/Lbry/Pascal
https://www.baikalminer.com/product10.php

Antminer A3 - SIA
https://shop.bitmain.com/productDetail.htm?pid=00020180116164357365a2ljX8gx06D3

Dual mining maybe gone soon as GPUs cant compete with ASICs, you have have noticed rewards and payouts and difficulty and spike lately, Devs of claymore may need to reduce their fees. to help in a few months.

ETH asic also announced, release in coming weeks.

when it  happens ETH will go POS. The factory is already aware and might not proceed as it will kill themselves with ugly paper weight.

[wtfonly16]

pos is in late 2018... they wil have plenty of revenue.

[Metroid]

when it  happens ETH will go POS. The factory is already aware and might not proceed as it will kill themselves with ugly paper weight.

ETH devs will kill any asic if they see there are any within the network. I got a word from them. They are monitoring the network.

[greatauror28]

Guys,

Sorry to bring the bad news, but dual miner might be over in a few months.

Asic miners on the market are now spiking up the difficulty for LBC/DCR/PASC/SIA

Baikal Giant-B - Blake256R14/Blake256R8/Blake2B/Lbry/Pascal
https://www.baikalminer.com/product10.php

Antminer A3 - SIA
https://shop.bitmain.com/productDetail.htm?pid=00020180116164357365a2ljX8gx06D3

Dual mining maybe gone soon as GPUs cant compete with ASICs, you have have noticed rewards and payouts and difficulty and spike lately, Devs of claymore may need to reduce their fees. to help in a few months.

ETH asic also announced, release in coming weeks.

Do you even know the basics of ethash algorithm? it is so memory-intensive that it would be too hard to design an ASIC with that much memory, let alone a compact size (like the S9).This fact makes eth ASIC-proof.

Try again next time.

[heavyarms1912]

Guys,

Sorry to bring the bad news, but dual miner might be over in a few months.

Asic miners on the market are now spiking up the difficulty for LBC/DCR/PASC/SIA

Baikal Giant-B - Blake256R14/Blake256R8/Blake2B/Lbry/Pascal
https://www.baikalminer.com/product10.php

Antminer A3 - SIA
https://shop.bitmain.com/productDetail.htm?pid=00020180116164357365a2ljX8gx06D3

Dual mining maybe gone soon as GPUs cant compete with ASICs, you have have noticed rewards and payouts and difficulty and spike lately, Devs of claymore may need to reduce their fees. to help in a few months.

ETH asic also announced, release in coming weeks.

Do you even know the basics of ethash algorithm? it is so memory-intensive that it would be too hard to design an ASIC with that much memory, let alone a compact size (like the S9).This fact makes eth ASIC-proof.

Try again next time.

Heck even the 4GB GPU's wont be good after 2019 or so? I would like to see those "ETH" ASICs

On topic.

Does anyone know if the -mclocks -clocks works fine if remote desktop is used?
Also for me, -powlim isn't working with Aug 23rd. beta blockchain drivers.

[ganzocrypt]

Hello,

would like to have a suggestion on which coin to dual mine since SIA difficulty is getting really high due to the switch of algo and ASIC coming in.

I am using RX 580, 1060 and 1070 TI, which coin is the best fit?
Are other coins that can be dual mine other than Decred/Lbry/Pascal ?

thx

[wtfonly16]

Guys,

Sorry to bring the bad news, but dual miner might be over in a few months.

Asic miners on the market are now spiking up the difficulty for LBC/DCR/PASC/SIA

Baikal Giant-B - Blake256R14/Blake256R8/Blake2B/Lbry/Pascal
https://www.baikalminer.com/product10.php

Antminer A3 - SIA
https://shop.bitmain.com/productDetail.htm?pid=00020180116164357365a2ljX8gx06D3

Dual mining maybe gone soon as GPUs cant compete with ASICs, you have have noticed rewards and payouts and difficulty and spike lately, Devs of claymore may need to reduce their fees. to help in a few months.

ETH asic also announced, release in coming weeks.

Do you even know the basics of ethash algorithm? it is so memory-intensive that it would be too hard to design an ASIC with that much memory, let alone a compact size (like the S9).This fact makes eth ASIC-proof.

Try again next time.

it only takes 4gb to mine... PoS is coming late 2018
its coming, start selling ur rigs.

[valev1]

Hi Claymore,

I've received a few reports from users running Awesome Miner to monitor Claymore Ethereum miner about issues with larger number of GPU's. In some systems when you have a large number of GPU's, you get a timeout on the Claymore monitoring API - it simply doesn't respond within a reasonable time. If the user is starting the mining process with a few GPU's less, then it works fine again. So when you go above a certain number of GPUs, the monitoring API isn't working even if the mining itself is running fine.

Is this a know issue? Are there any workarounds?

Thanks!

Please send me some logs so I can check the reason.
...
Ok I see big delays now. What CPU do you have? What average CPU load in Task Manager?

No more PM, so I write here, after sending logs,
CPU model: Celeron G3930
CPU LOAD: 53%-56% normaly taken by EthDcrMiner64.exe, everything else is up to  5%
MB: ASRock H110 Pro BTC+
RAM: 4gb ddr4

[Swiped]

Hi,
I'm new here, I don't know if other have this problem.
Mining just ethereum work great, really stable for days at fast rate.
Dual with lbry make the rig crash/reboot every 2-5 minutes or so... max I got was 17 minutes
I also re-flash with original bios, without OC and it's still rebooting...
my rig:
-win 10
-Biostar Motherboard TB250-BTC Core
-4x sapphire nitro+ rx 570 8gb samsung
-2x sapphire nitro+ rx 570 8gb hynix
-4gb ram
-120G ssd
-virtual memory 20-60gb (I know it's excessive)

one thing I found interresting is when claymore dual is used by nicehash, the computer doesn't reboot.
I also tried the -ethi 2 option without change.
tried 10.0 10.3 and 10.4

I tried for many hours, but I'll mine just ethereum untill it's stable for me.
I can try things if you want. Will sure try the next version. But want to informe you in case it help.

here the last part of logfile...
thank you!

Code:

09:22:54:907	1ea0	ETH: checking pool connection...
09:22:54:907	1ea0	send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:22:55:017	1ea0	got 243 bytes
09:22:55:017	1ea0	buf: {"jsonrpc":"2.0","id":0,"result":["0x39fa8daae61ea9271acb4e190cfa33638ff5c908cded462db2fc75c7af23cc51","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

09:22:55:032	1ea0	parse packet: 242
09:22:55:032	1ea0	ETH: job is the same
09:22:55:032	1ea0	new buf size: 0
09:22:56:220	1e94	LBC: put share nonce 93a5ed enonce 98d
09:22:56:236	1e94	LBC round found 1 shares
09:22:56:251	1eb0	 LBC: 01/16/18-09:22:56 - SHARE FOUND - (GPU 4)
09:22:56:251	1eb0	send: {"params": ["bMwKZkz6R2qZ9by1f9cw9PM24amrCvh2K6.miner2", "9c20", "8d090000", "5a5e0aa2", "0093a5ed"], "id": 14, "method": "mining.submit"}

09:22:56:283	1eb0	got 37 bytes
09:22:56:283	1eb0	buf: {"id":14,"result":true,"error":null}

09:22:56:283	1eb0	parse packet: 36
09:22:56:283	1eb0	 LBC: Share accepted (16 ms)!
09:22:56:298	1eb0	new buf size: 0
09:23:04:924	1ea0	ETH: checking pool connection...
09:23:04:924	1ea0	send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:23:05:049	1ea0	got 243 bytes
09:23:05:049	1ea0	buf: {"jsonrpc":"2.0","id":0,"result":["0x39fa8daae61ea9271acb4e190cfa33638ff5c908cded462db2fc75c7af23cc51","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

09:23:05:049	1ea0	parse packet: 242
09:23:05:049	1ea0	ETH: job is the same
09:23:05:065	1ea0	new buf size: 0
09:23:10:346	1ea0	got 243 bytes
09:23:10:346	1ea0	buf: {"jsonrpc":"2.0","id":0,"result":["0xf52876b64c18f696f331750fa60d61aaa3735b479e57b81c6c3b09d48e4edf03","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

09:23:10:346	1ea0	parse packet: 242
09:23:10:346	1ea0	ETH: job changed
09:23:10:362	1ea0	new buf size: 0
09:23:10:362	1ea0	ETH: 01/16/18-09:23:10 - New job from eth-us-east1.nanopool.org:9999
09:23:10:362	1ea0	target: 0x000000006df37f67 (diff: 10000MH), epoch 163(2.27GB)
09:23:10:378	1ea0	ETH - Total Speed: 174.988 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:00
09:23:10:378	1ea0	ETH: GPU0 28.119 Mh/s, GPU1 29.672 Mh/s, GPU2 29.690 Mh/s, GPU3 29.692 Mh/s, GPU4 29.700 Mh/s, GPU5 28.115 Mh/s
09:23:10:378	1ea0	 LBC - Total Speed: 448.404 Mh/s, Total Shares: 6, Rejected: 0
09:23:10:378	1ea0	 LBC: GPU0 72.054 Mh/s, GPU1 76.034 Mh/s, GPU2 76.081 Mh/s, GPU3 76.086 Mh/s, GPU4 76.106 Mh/s, GPU5 72.043 Mh/s
09:23:10:596	1e84	LBC: put share nonce 6229b8 enonce e45
09:23:10:612	1e84	LBC round found 1 shares
09:23:10:628	1eb0	 LBC: 01/16/18-09:23:10 - SHARE FOUND - (GPU 2)
09:23:10:628	1eb0	send: {"params": ["bMwKZkz6R2qZ9by1f9cw9PM24amrCvh2K6.miner2", "9c20", "450e0000", "5a5e0aa2", "006229b8"], "id": 12, "method": "mining.submit"}

09:23:10:659	1eb0	got 37 bytes
09:23:10:659	1eb0	buf: {"id":12,"result":true,"error":null}

09:23:10:659	1eb0	parse packet: 36
09:23:10:659	1eb0	 LBC: Share accepted (32 ms)!
09:23:10:674	1eb0	new buf size: 0
09:23:14:003	1ea0	got 243 bytes
09:23:14:003	1ea0	buf: {"jsonrpc":"2.0","id":0,"result":["0x1db9a600cf7799c6d4f7a7e995fa3fa58f8d2d7f896eadf775ac40c15a60a415","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

09:23:14:003	1ea0	parse packet: 242
09:23:14:019	1ea0	ETH: job changed
09:23:14:019	1ea0	new buf size: 0
09:23:14:019	1ea0	ETH: 01/16/18-09:23:14 - New job from eth-us-east1.nanopool.org:9999
09:23:14:019	1ea0	target: 0x000000006df37f67 (diff: 10000MH), epoch 163(2.27GB)
09:23:14:034	1ea0	ETH - Total Speed: 173.727 Mh/s, Total Shares: 1, Rejected: 0, Time: 00:01
09:23:14:034	1ea0	ETH: GPU0 27.865 Mh/s, GPU1 29.571 Mh/s, GPU2 29.407 Mh/s, GPU3 29.407 Mh/s, GPU4 29.584 Mh/s, GPU5 27.893 Mh/s
09:23:14:034	1ea0	 LBC - Total Speed: 445.172 Mh/s, Total Shares: 7, Rejected: 0
09:23:14:050	1ea0	 LBC: GPU0 71.403 Mh/s, GPU1 75.776 Mh/s, GPU2 75.356 Mh/s, GPU3 75.354 Mh/s, GPU4 75.808 Mh/s, GPU5 71.475 Mh/s
09:23:14:675	1e24	em hbt: 15, dm hbt: 15, fm hbt: 62, 
09:23:14:675	1e24	watchdog - thread 0 (gpu0), hb time 140
09:23:14:691	1e24	watchdog - thread 1 (gpu0), hb time 94
09:23:14:691	1e24	watchdog - thread 2 (gpu1), hb time 16
09:23:14:706	1e24	watchdog - thread 3 (gpu1), hb time 109
09:23:14:706	1e24	watchdog - thread 4 (gpu2), hb time 78
09:23:14:706	1e24	watchdog - thread 5 (gpu2), hb time 15
09:23:14:706	1e24	watchdog - thread 6 (gpu3), hb time 78
09:23:14:722	1e24	watchdog - thread 7 (gpu3), hb time 31
09:23:14:722	1e24	watchdog - thread 8 (gpu4), hb time 125
09:23:14:722	1e24	watchdog - thread 9 (gpu4), hb time 62
09:23:14:722	1e24	watchdog - thread 10 (gpu5), hb time 47
09:23:14:737	1e24	watchdog - thread 11 (gpu5), hb time 141
09:23:14:894	1ea0	send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xa04a645", "0x000000000000000000000000000000000000000000000000000000004c5d5488"]}

09:23:14:941	1ea0	ETH: checking pool connection...
09:23:14:941	1ea0	send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:23:15:050	1ea0	got 243 bytes
09:23:15:066	1ea0	buf: {"jsonrpc":"2.0","id":0,"result":["0x1db9a600cf7799c6d4f7a7e995fa3fa58f8d2d7f896eadf775ac40c15a60a415","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

09:23:15:066	1ea0	parse packet: 242
09:23:15:066	1ea0	ETH: job is the same
09:23:15:112	1ea0	new buf size: 0
09:23:15:831	1e7c	LBC: put share nonce 1fedd4 enonce fe7
09:23:15:831	1e7c	LBC round found 1 shares
09:23:15:847	1eb0	 LBC: 01/16/18-09:23:15 - SHARE FOUND - (GPU 1)
09:23:15:847	1eb0	send: {"params": ["bMwKZkz6R2qZ9by1f9cw9PM24amrCvh2K6.miner2", "9c20", "e70f0000", "5a5e0aa2", "001fedd4"], "id": 11, "method": "mining.submit"}

09:23:15:878	1eb0	got 37 bytes
09:23:15:878	1eb0	buf: {"id":11,"result":true,"error":null}

09:23:15:878	1eb0	parse packet: 36
09:23:15:878	1eb0	 LBC: Share accepted (31 ms)!
09:23:15:894	1eb0	new buf size: 0
09:23:19:582	1e88	ETH: put share nonce ad68f22c0965c4a5
09:23:19:597	1e88	ETH round found 1 shares
09:23:19:613	1ea0	ETH: 01/16/18-09:23:19 - SHARE FOUND - (GPU 3)
09:23:19:613	1ea0	send: {"id":13,"method":"eth_submitWork","params":["0xad68f22c0965c4a5","0x1db9a600cf7799c6d4f7a7e995fa3fa58f8d2d7f896eadf775ac40c15a60a415","0xd23d945fd9c7ec7f2baa1449d9efb5184d3a56d4b8d101651bd763296c1f64cd"]}

09:23:19:738	1ea0	got 40 bytes
09:23:19:738	1ea0	buf: {"jsonrpc":"2.0","id":13,"result":true}

09:23:19:754	1ea0	parse packet: 39
09:23:19:769	1ea0	ETH: Share accepted (156 ms)!

09:23:19:769	1ea0	new buf size: 0
09:23:20:660	1eb0	got 649 bytes
09:23:20:660	1eb0	buf: {"id":null,"method":"mining.notify","params":["9c21","777aa9cb6e50a36f3870ee91bf56d240673fe4bcca0eaf59e414bb261ed2a8ad","dc093acdf48832de3c94cfd0c710b6f172d694488985161e332dca93af5d4fd1","01000000010000000000000000000000000000000000000000000000000000000000000000ffffffff1d0368ac0404d90a5e5a08","0a2f436f696e4d696e652f0000000001e07823c1080000001976a9140f67e4482043a67dc028142eba63ba77a509c3d388ac00000000",["a344233225b4abac438740605ccdd3fcfae183dc9b4d22c2504d0334e6440b39","86b4f6de38cbfebadf4f114144055ee66cf15c17f6c8c4066928cf8ed356de2d","4e8d54e9533c59653ec5edaaa85dae36f970d49e615374a3c2a9e4142c9c56ef"],"20000000","1a0aafc9","5a5e0ad9",false]}

09:23:20:660	1eb0	parse packet: 648
09:23:20:676	1eb0	new buf size: 0
09:23:20:676	1eb0	 LBC: 01/16/18-09:23:20 - New job from lbc.coinmine.pl:8787
09:23:20:676	1eb0	target: 0x00000000ffff0000 (diff: 4295MH)
09:23:21:504	1e94	LBC: put share nonce 39a53f enonce 39
09:23:21:504	1e94	LBC round found 1 shares
09:23:21:519	1eb0	 LBC: 01/16/18-09:23:21 - SHARE FOUND - (GPU 4)
09:23:21:519	1eb0	send: {"params": ["bMwKZkz6R2qZ9by1f9cw9PM24amrCvh2K6.miner2", "9c21", "39000000", "5a5e0ad9", "0039a53f"], "id": 14, "method": "mining.submit"}

09:23:21:551	1eb0	got 37 bytes
09:23:21:551	1eb0	buf: {"id":14,"result":true,"error":null}

09:23:21:551	1eb0	parse packet: 36
09:23:21:551	1eb0	 LBC: Share accepted (31 ms)!
09:23:21:566	1eb0	new buf size: 0
09:23:23:535	1e28	GPU0 t=61C fan=49%, GPU1 t=57C fan=42%, GPU2 t=55C fan=37%, GPU3 t=59C fan=47%, GPU4 t=58C fan=47%, GPU5 t=58C fan=43%
09:23:24:957	1ea0	ETH: checking pool connection...
09:23:24:957	1ea0	send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:23:25:067	1e90	LBC: put share nonce 20c96a enonce 158
09:23:25:082	1ea0	got 243 bytes
09:23:25:082	1ea0	buf: {"jsonrpc":"2.0","id":0,"result":["0x1db9a600cf7799c6d4f7a7e995fa3fa58f8d2d7f896eadf775ac40c15a60a415","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

09:23:25:098	1ea0	parse packet: 242
09:23:25:098	1ea0	ETH: job is the same
09:23:25:114	1ea0	new buf size: 0
09:23:25:114	1eb0	 LBC: 01/16/18-09:23:25 - SHARE FOUND - (GPU 4)
09:23:25:114	1eb0	send: {"params": ["bMwKZkz6R2qZ9by1f9cw9PM24amrCvh2K6.miner2", "9c21", "58010000", "5a5e0ad9", "0020c96a"], "id": 14, "method": "mining.submit"}

09:23:25:082	1e90	LBC round found 1 shares
09:23:25:145	1eb0	got 37 bytes
09:23:25:145	1eb0	buf: {"id":14,"result":true,"error":null}

09:23:25:145	1eb0	parse packet: 36
09:23:25:145	1eb0	 LBC: Share accepted (16 ms)!
09:23:25:160	1eb0	new buf size: 0
09:23:28:614	1e7c	LBC: put share nonce 8695b6 enonce 27f
09:23:28:614	1e7c	LBC round found 1 shares
09:23:28:630	1eb0	 LBC: 01/16/18-09:23:28 - SHARE FOUND - (GPU 1)
09:23:28:630	1eb0	send: {"params": ["bMwKZkz6R2qZ9by1f9cw9PM24amrCvh2K6.miner2", "9c21", "7f020000", "5a5e0ad9", "008695b6"], "id": 11, "method": "mining.submit"}

09:23:28:661	1eb0	got 37 bytes
09:23:28:661	1eb0	buf: {"id":11,"result":true,"error":null}

09:23:28:661	1eb0	parse packet: 36
09:23:28:661	1eb0	 LBC: Share accepted (32 ms)!
09:23:28:676	1eb0	new buf size: 0
09:23:30:317	1e84	LBC: put share nonce 66f32b enonce 311
09:23:30:317	1e84	LBC round found 1 shares
09:23:30:333	1eb0	 LBC: 01/16/18-09:23:30 - SHARE FOUND - (GPU 2)
09:23:30:333	1eb0	send: {"params": ["bMwKZkz6R2qZ9by1f9cw9PM24amrCvh2K6.miner2", "9c21", "11030000", "5a5e0ad9", "0066f32b"], "id": 12, "method": "mining.submit"}

09:23:30:364	1eb0	got 37 bytes
09:23:30:364	1eb0	buf: {"id":12,"result":true,"error":null}

09:23:30:364	1eb0	parse packet: 36
09:23:30:364	1eb0	 LBC: Share accepted (32 ms)!
09:23:30:380	1eb0	new buf size: 0
09:23:34:911	1ea0	send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xa543fb3", "0x000000000000000000000000000000000000000000000000000000004c5d5488"]}

09:23:34:974	1ea0	ETH: checking pool connection...
09:23:34:974	1ea0	send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

09:23:35:099	1ea0	got 243 bytes
09:23:35:099	1ea0	buf: {"jsonrpc":"2.0","id":0,"result":["0x1db9a600cf7799c6d4f7a7e995fa3fa58f8d2d7f896eadf775ac40c15a60a415","0xec6e8e0d8056cf9eb61046eaeb754b8e71f48e10a86c61f4d287b4ac5244653f","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}

09:23:35:115	1ea0	parse packet: 242
09:23:35:115	1ea0	ETH: job is the same
09:23:35:130	1ea0	new buf size: 0

Did you ever solve this?  I have 4 rigs running similar Sapphire 570 8g cards, (2X6) with Hynix, (1X6) with Micron, and (1X6) with Samsung, only the Samsung cards run stable and the other three are incredibly unstable.  I have purchased some new riser cards just to make sure I didn't get a bad batch.  I have tried every setting and bios change under the sun and can't get them stable.  They just hang in open cl and reset.  Never seen this in any of my other rigs, just on the Sapphire 570 8g cards.  I am beginning to believe it is just a lousy batch of cards.  I'll let you know if the risers make any difference.

Hi, are you talking about dual-mining? or is it unstable with ethereum only too? My 2 rigs (1-6xsamsung and 1-2hynix+4samsung) are really stable with ethereum only. I have put the "-asm 2" option, and I think it help. (It sure increase a bit the hashrate). What is your OC, I'm unable to oc a lot on these, but I'm satisfied with approx:29.6 mh. in dual mining, it's more stable for me with less OC, so I accept at the moment a drop of around 1mh in ethereum to dual-mine... Let me know if you need more info on my setup, if my hashrate is interresting for you. Happy mining!

Thanks for the feedback.  I quit dual mining this week since the overall value in the alt coin does not exceed the increase in eth production and the power reduction I get when I just mine eth.  I have gone from generating 300 LBC a day to 70 LBC a day in just 2 weeks, so the dual mining part of this is no longer more profitable than just mining eth as long as the price is over $1000/coin.  I have tried the asm 2 setting and I believe is has helped stabilize my Sapphire 570 8g rigs, so thank you for that idea.  Not sure I am going to figure out why the 570 8g cards are so unstable compared to my other rigs, but I have at least found a way to run them and be profitable.

[Piradoxlanieve]

What's the latest drivers from AMD we can use with 10.5, are we still stuck with blockchain drivers??

The latest adrenalin drivers work fine for me, but I don't use any of the temp or voltage controls in the miner so YMMV.

drivers adrenalin works with bios mod and DAG fix?

[PB_SilentMiner]

What's the latest drivers from AMD we can use with 10.5, are we still stuck with blockchain drivers??

The latest adrenalin drivers work fine for me, but I don't use any of the temp or voltage controls in the miner so YMMV.

drivers adrenalin works with bios mod and DAG fix?

I'm currently using 17.12.2 Adrenalin Drivers on CM10.4 with temp & voltage controls. W10 Pro x64 1703

Been working fine (Touch Wood)

With Compute mode turned on and BOIS mods with DAG fix

Knocking out 178-179MH/s on a 6 card rig of RX480 8GB at around 860w

[PB_SilentMiner]

-ethi   Ethereum intensity. Default value is 8, you can decrease this value if you don't want Windows to freeze or if you have problems with stability. The most low GPU load is "-ethi 0".
   Also "-ethi" now can set intensity for every card individually, for example "-ethi 1,8,6".
   You can also specify negative values, for example, "-ethi -8192", it exactly means "global work size" parameter which is used in official miner.

I have my rigs set to -ethi 16

What does it actually do with a higher number? Without stating the obvious!

From what I can see it gives a better hashrate but thats about it.

[ShadowKagaho]

-dpool dc.suprnova.cc:3252 -dwal ShadowKagaho.1 -dpsw x -allpools 1

In my DECRED mining is having problem please someone can help me to solve the problem! Thank you for your attention right now.

[Bael]

What's the latest drivers from AMD we can use with 10.5, are we still stuck with blockchain drivers??

The latest adrenalin drivers work fine for me, but I don't use any of the temp or voltage controls in the miner so YMMV.

drivers adrenalin works with bios mod and DAG fix?

Adrenalina 18.1.1, win10 1709, Claymore 10.5 va perfecto, recuerda poner en modo computo los drivers de amd o no funcionara.

[igotfits]

What's the latest drivers from AMD we can use with 10.5, are we still stuck with blockchain drivers??

The latest adrenalin drivers work fine for me, but I don't use any of the temp or voltage controls in the miner so YMMV.

drivers adrenalin works with bios mod and DAG fix?

Adrenalina 18.1.1, win10 1709, Claymore 10.5 va perfecto, recuerda poner en modo computo los drivers de amd o no funcionara.

Cool latest works with compute mode enabled? anyone else verify?

[igotfits]

Can anyone shed some light on possible failure, im running this rig on a wifi adapter as well.

Claymore just crashes and says this at the end:
1368   WATCHDOG: GPU error, you need to restart miner
1368   Rebooting



00:31:56:941   1c74   Set global fail flag, failed GPU6
00:31:56:941   19a4   GPU 1, CUDA error 11 - cannot write buffer for DAG
00:31:56:942   1c74   GPU 6 failed
00:31:56:942   1d7c   Setting DAG epoch #164 for GPU7
00:31:56:942   1d7c   GPU 7, CUDA error 11 - cannot write buffer for DAG
00:31:56:943   18b4   Setting DAG epoch #164 for GPU6
00:31:56:944   18b4   GPU 6, CUDA error 11 - cannot write buffer for DAG
00:31:56:947   1ccc   Set global fail flag, failed GPU3
00:31:56:949   1ccc   GPU 3 failed
00:31:56:949   1db8   Set global fail flag, failed GPU0
00:31:56:949   14bc   Setting DAG epoch #164 for GPU3
00:31:56:950   1db8   GPU 0 failed
00:31:56:948   1c7c   Set global fail flag, failed GPU5
00:31:56:950   14bc   GPU 3, CUDA error 11 - cannot write buffer for DAG
00:31:56:951   1c7c   GPU 5 failed
00:31:56:950   1d2c   Setting DAG epoch #164 for GPU0
00:31:56:951   1d2c   GPU 0, CUDA error 11 - cannot write buffer for DAG
00:31:56:953   1cb8   Setting DAG epoch #164 for GPU5
00:31:56:953   1cb8   GPU 5, CUDA error 11 - cannot write buffer for DAG
00:31:57:122   1d90   got 248 bytes

[Rickirs]

Try with -gser 1 , if that doesn't work, try with -gser 2

[igotfits]

Try with -gser 1 , if that doesn't work, try with -gser 2

This is my full line...

EthDcrMiner64.exe -epool stratum+tcp://us-west.pirlpool.eu:8004 -ewal WALLET -epsw x -allcoins -1 -eworker GTX1060s -gser 3 -minspeed 180 -r 1 -dcoin pasc -dpool mine.pasl.fairpool.cloud:4009 -dwal WALLET+GTX1060s -dpsw x -dcri 17

[rampage999]

Hi Claymore,

To disable dual mining on some cards,
use -mode 1-[card index]
is there a way to disable dual mining on card index >9?use abced?

Or maybe enable dual mining on some cards via -mode 0-[card index]?

[blue1984]

I use Linux ubuntu 16.04 - with the latest driver. the last weeks works everythink fine... now i get only 18. MHS per card (before 27.5) AMD 470

What is the problem? BIOS? DAG?