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

[costi.kocev]

Yes, that was. We need info from @Claymore.

The problem must be on pool side, but you can PM me the complete log file and I will check it to confirm.

@mastermerlin can you send to @Claymore the full log, because I don`t have it?

[Mexxme]

Yes, that was. We need info from @Claymore.

The problem must be on pool side, but you can PM me the complete log file and I will check it to confirm.

@mastermerlin can you send to @Claymore the full log, because I don`t have it?

I did send log to Claymore from my 6xGPU rig, maybe it can help

For me, simple restart of miner solved problem so maybe there is nothing to fix there.
Could be Ethermine pool issue?

[Claymore]

I've checked some logs, the problem on pool side, pool sends different epochs for some reason. You can ask their support why it happens.

[VictorGT]

Close and reopen the miner seems to fix the "128 epoch problem..." for me. Mining at ethermine.org

[DrLexer]

Close and reopen the miner seems to fix the "128 epoch problem..." for me. Mining at ethermine.org

only on some rigs, another - continue 128-139

[noviceminer]

I've checked some logs, the problem on pool side, pool sends different epochs for some reason. You can ask their support why it happens.

Any update for Windows 7 users using blockchain drivers that face issue of miner crashing as soon as it detects the cards ?

[Claymore]

I've checked some logs, the problem on pool side, pool sends different epochs for some reason. You can ask their support why it happens.

Any update for Windows 7 users using blockchain drivers that face issue of miner crashing as soon as it detects the cards ?

I cannot install these drivers on Windows7 at all, now I have to reinstall Windows after several attempts. Try any different OpenCL miner to confirm that the issue is related to my miner, because the reason can be drivers.

[Saltist]

To shed some light to the Win7 stuff:

I do run 3 570s on Win7 Home Premium 64 Bit.

This is my installation process:

DDU -> reboot -> install driver -> pixel clock patcher -> reboot

So previously I was running on 17.4.4, I then tried to install the blockchain driver from the AMD website. I did not use DDU. Something failed but I could use a restore point to get my rig back up running. Next attempt I did use DDU, installation took quite a while but in the end it finished. Starting Claymore (or even some other miners so it's a driver issue), Claymore just closed with the last message "start building OpenCL program for GPU 0".

So I tried the drivers that robinh00d posted some time ago because rumors said that it'd work on Win7. Surprise, it actually did work! I got from 74 MH/s to 79 MH/s but not for long! Overclocking in Claymore did indeed work but not quite well though. Memclock alternated between 1000 and the set frequency every 2-5s causing a significant hashrate drop. Also power usage (according to GPU-z) increased from around 75W to 110+W per card with the same core frequency.

Needless to say I did revert to 17.4.4 until the driver is fixed. I did also switch to an other Ethash coin with a lower epoch which gets me that 79 MH/s on the 17.4.4 drivers.

[hobbyminer67]

I've checked some logs, the problem on pool side, pool sends different epochs for some reason. You can ask their support why it happens.

Any update for Windows 7 users using blockchain drivers that face issue of miner crashing as soon as it detects the cards ?

I cannot install these drivers on Windows7 at all, now I have to reinstall Windows after several attempts. Try any different OpenCL miner to confirm that the issue is related to my miner, because the reason can be drivers.

Don't know if anyone cares but I was able to do the amd clean install with the win7 driver on an old win8.1 rig w/5 x 280x that normally run Claymore's ZCash to see if the dual ETH was any better. Took longer than normal to install, thought it locked up but it was not.  No real change so went back to ZCash also still the same.

[cas33]

Absolute record today - 133 TH and dificulty jumped dramatically. I am impressed of how people are desinformed of what is comming

could you please explain?

133 TH is the real total Ethereum hashrate globally with difficulty 1,860,352,697,067,784.00000000 which is about 10% more than yesterday.

You need to take a chill pill.

https://www.coinwarz.com/network-hashrate-charts/ethereum-network-hashrate-chart

https://www.coinwarz.com/difficulty-charts/ethereum-difficulty-chart

Hey,smarty,chill pill is for you all. Look at the pool not in statistic sites. Next time prepare your self before

[dollos]

Hi Claymore

Seems to be a problem with the miner, one rig of mine just ploughed through the epoch change but the others are battling and i just checked one now was mining on epoch 128!!!!??? dont even know how that was possible, and you have an issue where when there are more than 11 cards in rig and you have more than 3 amd cards inside you have to open 2 instances of the miner. it just hangs at algorithm ASM when you enable all cards in the miner, dual eth miner i am talking about, i hope you are aware of this and a fix can be found.
With regards to the epoch any suggestions?
Thanks

[fredeq]

Absolute record today - 133 TH and dificulty jumped dramatically. I am impressed of how people are desinformed of what is comming

could you please explain?

133 TH is the real total Ethereum hashrate globally with difficulty 1,860,352,697,067,784.00000000 which is about 10% more than yesterday.

You need to take a chill pill.

https://www.coinwarz.com/network-hashrate-charts/ethereum-network-hashrate-chart

https://www.coinwarz.com/difficulty-charts/ethereum-difficulty-chart

Hey,smarty,chill pill is for you all. Look at the pool not in statistic sites. Next time prepare your self before

Those charts look more sane than 133TH. Where did you get this value from?
IMO some service tried to extrapolate nethash from difficulty, but forgot to take block_time into account.

[Facinat]

Close and reopen the miner seems to fix the "128 epoch problem..." for me. Mining at ethermine.org

I had same problem my one rig today.

[bobben2]

I haven't kept up with this thread for a while so please bear with me if this has been commented on earlier..
Today one of my rigs started to misbehave where it kept reinitializing itself loading DAG for epoch 128...
Notice the increase in reported hashrate, too       I am using version 9.7 btw
See log excerpt below.

Code:

15:39:35:078	478	ETH: 08/22/17-15:39:35 - New job from eu1.ethermine.org:4444
15:39:35:078	478	target: 0x0000000112e0be82 (diff: 4000MH), epoch 128(2.00GB)
15:39:35:078	478	ETH - Total Speed: 105.144 Mh/s, Total Shares: 3652, Rejected: 17, Time: 40:32
15:39:35:078	478	ETH: GPU0 27.043 Mh/s, GPU1 25.258 Mh/s, GPU2 27.031 Mh/s, GPU3 25.812 Mh/s
15:39:35:110	af8	GPU 0 temp = 50, old fan speed = 35, new fan speed = 26 

15:39:35:110	af8	GPU 1 temp = 56, old fan speed = 36, new fan speed = 26 

15:39:35:125	af8	GPU 2 temp = 50, old fan speed = 35, new fan speed = 26 

15:39:35:125	af8	GPU 3 temp = 57, old fan speed = 36, new fan speed = 26 

15:39:35:250	87c	Setting DAG epoch #128...
15:39:36:888	87c	Setting DAG epoch #128 for GPU2
15:39:36:888	6dc	Setting DAG epoch #128 for GPU0
15:39:36:888	2e4	Setting DAG epoch #128 for GPU1
15:39:36:888	12c	Setting DAG epoch #128 for GPU3
15:39:38:432	af8	GPU 0 temp = 49, old fan speed = 35, new fan speed = 26 

15:39:38:432	af8	GPU 1 temp = 55, old fan speed = 36, new fan speed = 26 

15:39:38:432	af8	GPU 2 temp = 48, old fan speed = 35, new fan speed = 26 

15:39:38:432	af8	GPU 3 temp = 55, old fan speed = 36, new fan speed = 26 

15:39:40:897	87c	GPU2 DAG creation time - 3898 ms
15:39:40:897	87c	Setting DAG epoch #128 for GPU2 done
15:39:40:913	12c	GPU3 DAG creation time - 3893 ms
15:39:40:913	12c	Setting DAG epoch #128 for GPU3 done
15:39:40:944	6dc	GPU0 DAG creation time - 3899 ms
15:39:40:944	6dc	Setting DAG epoch #128 for GPU0 done
15:39:40:991	2e4	GPU1 DAG creation time - 3981 ms
15:39:40:991	2e4	Setting DAG epoch #128 for GPU1 done
15:39:41:740	af8	GPU 0 temp = 50, old fan speed = 35, new fan speed = 26 

15:39:41:740	af8	GPU 1 temp = 56, old fan speed = 36, new fan speed = 26 

15:39:41:740	af8	GPU 2 temp = 50, old fan speed = 35, new fan speed = 26 

15:39:41:755	af8	GPU 3 temp = 56, old fan speed = 36, new fan speed = 26 

15:39:45:062	af8	GPU 0 temp = 50, old fan speed = 35, new fan speed = 26 

15:39:45:062	af8	GPU 1 temp = 56, old fan speed = 36, new fan speed = 26 

15:39:45:062	af8	GPU 2 temp = 50, old fan speed = 35, new fan speed = 26 

15:39:45:062	af8	GPU 3 temp = 57, old fan speed = 35, new fan speed = 26 

15:39:46:654	478	send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x6d297c5", "0x0000000000000000000000000000000000000000000000000000000022a6a6be"]}

15:39:46:700	478	got 39 bytes
15:39:46:700	478	buf: {"id":6,"jsonrpc":"2.0","result":true}

15:39:46:700	478	parse packet: 38
15:39:46:700	478	new buf size: 0
15:39:48:370	af8	GPU 0 temp = 50, old fan speed = 35, new fan speed = 26 

15:39:48:370	af8	GPU 1 temp = 56, old fan speed = 36, new fan speed = 26 

15:39:48:370	af8	GPU 2 temp = 50, old fan speed = 35, new fan speed = 26 

15:39:48:385	af8	GPU 3 temp = 57, old fan speed = 35, new fan speed = 26 

15:39:48:666	478	got 248 bytes
15:39:48:666	478	buf: {"id":0,"jsonrpc":"2.0","result":["0xda266190a0e595bd3484b6e6025de12aeb0ececf7c7d686b873a1f78b5b362e1","0x7c4fb8a5d141973b69b521ce76b0dc50f0d2834d817c7f8310a6ab5becc6bb0c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3acbdb"]}

15:39:48:666	478	parse packet: 247
15:39:48:666	478	ETH: job changed
15:39:48:666	478	new buf size: 0
15:39:48:666	478	ETH: 08/22/17-15:39:48 - New job from eu1.ethermine.org:4444
15:39:48:666	478	target: 0x0000000112e0be82 (diff: 4000MH), epoch 128(2.00GB)
15:39:48:666	478	ETH - Total Speed: 114.458 Mh/s, Total Shares: 3652, Rejected: 17, Time: 40:32
15:39:48:666	478	ETH: GPU0 29.530 Mh/s, GPU1 27.405 Mh/s, GPU2 29.557 Mh/s, GPU3 27.967 Mh/s
15:39:50:741	478	ETH: checking pool connection...
15:39:50:741	478	send: {"id":3,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

15:39:50:788	478	got 248 bytes
15:39:50:788	478	buf: {"id":3,"jsonrpc":"2.0","result":["0xda266190a0e595bd3484b6e6025de12aeb0ececf7c7d686b873a1f78b5b362e1","0x7c4fb8a5d141973b69b521ce76b0dc50f0d2834d817c7f8310a6ab5becc6bb0c","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3acbdb"]}

15:39:50:788	478	parse packet: 247
15:39:50:788	478	ETH: job is the same
15:39:50:788	478	new buf size: 0
15:39:51:693	af8	GPU 0 temp = 51, old fan speed = 35, new fan speed = 26 

15:39:51:693	af8	GPU 1 temp = 56, old fan speed = 36, new fan speed = 26 

15:39:51:693	af8	GPU 2 temp = 50, old fan speed = 35, new fan speed = 26 

15:39:51:693	af8	GPU 3 temp = 57, old fan speed = 35, new fan speed = 26 

15:39:54:937	478	got 248 bytes
15:39:54:937	478	buf: {"id":0,"jsonrpc":"2.0","result":["0xb3a8247f1c8c554d9d329e4a13b68fd6f8fddd7d408511f09fbff14265eb7e94","0xc50f0eb9498c019d38f28db0aefec38f0a243f1bcbc67281ce622916ee182e4a","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3ff027"]}

15:39:54:937	478	parse packet: 247
15:39:54:937	478	ETH: job changed
15:39:54:937	478	new buf size: 0
15:39:54:937	478	ETH: 08/22/17-15:39:54 - New job from eu1.ethermine.org:4444
15:39:54:937	478	target: 0x0000000112e0be82 (diff: 4000MH), epoch 139(2.09GB)
15:39:54:937	478	ETH - Total Speed: 114.380 Mh/s, Total Shares: 3652, Rejected: 17, Time: 40:32
15:39:54:937	478	ETH: GPU0 29.480 Mh/s, GPU1 27.402 Mh/s, GPU2 29.536 Mh/s, GPU3 27.962 Mh/s
15:39:55:000	af8	GPU 0 temp = 50, old fan speed = 35, new fan speed = 26 

15:39:55:000	af8	GPU 1 temp = 56, old fan speed = 36, new fan speed = 26 

15:39:55:000	af8	GPU 2 temp = 50, old fan speed = 35, new fan speed = 26 

15:39:55:015	af8	GPU 3 temp = 57, old fan speed = 36, new fan speed = 26 

15:39:55:031	af8	GPU0 t=50C fan=35%, GPU1 t=56C fan=36%, GPU2 t=50C fan=35%, GPU3 t=57C fan=36%
15:39:55:031	af8	em hbt: 0, fm hbt: 16, 
15:39:55:031	af8	watchdog - thread 0 (gpu0), hb time 234
15:39:55:031	af8	watchdog - thread 1 (gpu0), hb time 94
15:39:55:031	af8	watchdog - thread 2 (gpu1), hb time 62
15:39:55:031	af8	watchdog - thread 3 (gpu1), hb time 218
15:39:55:031	af8	watchdog - thread 4 (gpu2), hb time 156
15:39:55:031	af8	watchdog - thread 5 (gpu2), hb time 0
15:39:55:031	af8	watchdog - thread 6 (gpu3), hb time 265
15:39:55:031	af8	watchdog - thread 7 (gpu3), hb time 125
15:39:55:078	6dc	Setting DAG epoch #139...
15:39:56:794	6dc	Setting DAG epoch #139 for GPU0
15:39:56:794	474	Setting DAG epoch #139 for GPU2
15:39:56:809	3c4	Setting DAG epoch #139 for GPU1
15:39:56:809	12c	Setting DAG epoch #139 for GPU3
15:39:58:323	af8	GPU 0 temp = 49, old fan speed = 35, new fan speed = 26 

15:39:58:338	af8	GPU 1 temp = 55, old fan speed = 36, new fan speed = 26 

15:39:58:338	af8	GPU 2 temp = 49, old fan speed = 35, new fan speed = 26 

15:39:58:354	af8	GPU 3 temp = 55, old fan speed = 36, new fan speed = 26 

15:40:01:006	474	GPU2 DAG creation time - 4081 ms
15:40:01:006	474	Setting DAG epoch #139 for GPU2 done
15:40:01:006	12c	GPU3 DAG creation time - 4077 ms
15:40:01:006	12c	Setting DAG epoch #139 for GPU3 done
15:40:01:037	6dc	GPU0 DAG creation time - 4082 ms
15:40:01:037	6dc	Setting DAG epoch #139 for GPU0 done
15:40:01:099	3c4	GPU1 DAG creation time - 4168 ms
15:40:01:099	3c4	Setting DAG epoch #139 for GPU1 done
15:40:01:661	af8	GPU 0 temp = 50, old fan speed = 35, new fan speed = 26 

[cyeedar]

Need some help with this error, rig hangs and the log shows it got some 'checkread timeout' before it hangs. Tried searching but nobody ever gave any answer to this.

22:46:08:974   1068   new buf size: 0
22:46:09:006   1068   Socket was closed remotely (by pool)
22:46:09:006   1068   ETH: Connection lost, retry in 10 sec...
22:46:19:022   1068   ETH: Stratum - connecting to 'asia1.ethermine.org' <139.99.8.158> port 14444
22:46:19:037   1068   send: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0x83F102145C5Df61C8046f99B94020a6F278785ac.vitalik_06", "x"], "id": 2, "method": "eth_submitLogin"}

22:46:19:037   1068   ETH: Stratum - Connected (asia1.ethermine.org:14444)
22:46:19:069   1068   got 39 bytes
22:46:19:069   1068   buf: {"id":2,"jsonrpc":"2.0","result":true}

22:46:19:069   1068   parse packet: 38
22:46:19:069   1068   ETH: Authorized
22:46:19:069   1068   send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}

22:46:19:069   1068   new buf size: 0
22:46:19:100   1068   got 248 bytes
22:46:19:100   1068   buf: {"id":3,"jsonrpc":"2.0","result":["0xf4f4b6e25d0504d3590bdcab878c302343b8b21d7cf104cea833ef5d0126a00e","0xc50f0eb9498c019d38f28db0aefec38f0a243f1bcbc67281ce622916ee182e4a","0x0112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x3ff0db"]}

22:46:19:100   1068   parse packet: 247
22:46:19:100   1068   ETH: job is the same
22:46:19:100   1068   new buf size: 0
22:46:23:819   1068   checkread timeout
22:46:28:538   1068   checkread timeout
22:46:33:241   1068   checkread timeout
22:46:34:507   330   GPU0 t=57C fan=30%, GPU1 t=58C fan=27%, GPU2 t=58C fan=34%, GPU3 t=57C fan=35%, GPU4 t=57C fan=34%, GPU5 t=58C fan=36%
22:46:34:507   330   em hbt: 15485, fm hbt: 0,
22:46:34:522   330   watchdog - thread 0 (gpu0), hb time 46
22:46:34:522   330   watchdog - thread 1 (gpu0), hb time 31
22:46:34:522   330   watchdog - thread 2 (gpu1), hb time 31
22:46:34:522   330   watchdog - thread 3 (gpu1), hb time 15
22:46:34:522   330   watchdog - thread 4 (gpu2), hb time 93
22:46:34:538   330   watchdog - thread 5 (gpu2), hb time 94
22:46:34:538   330   watchdog - thread 6 (gpu3), hb time 47
22:46:34:538   330   watchdog - thread 7 (gpu3), hb time 62
22:46:34:538   330   watchdog - thread 8 (gpu4), hb time 78
22:46:34:538   330   watchdog - thread 9 (gpu4), hb time 62
22:46:34:553   330   watchdog - thread 10 (gpu5), hb time 78
22:46:34:553   330   watchdog - thread 11 (gpu5), hb time 94
22:46:37:944   1068   checkread timeout
22:46:42:648   1068   checkread timeout

[cas33]

Absolute record today - 133 TH and dificulty jumped dramatically. I am impressed of how people are desinformed of what is comming

could you please explain?

133 TH is the real total Ethereum hashrate globally with difficulty 1,860,352,697,067,784.00000000 which is about 10% more than yesterday.

You need to take a chill pill.

https://www.coinwarz.com/network-hashrate-charts/ethereum-network-hashrate-chart

https://www.coinwarz.com/difficulty-charts/ethereum-difficulty-chart

Hey,smarty,chill pill is for you all. Look at the pool not in statistic sites. Next time prepare your self before

Those charts look more sane than 133TH. Where did you get this value from?
IMO some service tried to extrapolate nethash from difficulty, but forgot to take block_time into account.

I am mining in miningpoolhub pool and this morning Ethereum stats(dificulty and hashrate) were the value i shown. hours after that was dropped and for example now is 125TH hash rate and dificulty 1,750,349,913,261,137.00000000.  So i am talking about a record i see in hashrate in that moment. Hope you understand this time. 

[Haik]

What the bug? EthDcrMiner64.exe sometimes  load CPU to 90-100%, 2 different motherboard, one runs on WIndows 7, second on W10. After few hours of work, msi asfterburner shows cpu usage 70% and more and when i close MSI AB task, EthDcrMiner64 process closing with it. This is not a riser or videocard problem, tried everything. Msi AB can not work with this eth miner. Another mining software working fine.

[NavyCuda]

Anyone have any idea if those rumors of Vega hashing(in the future) 70-100MH/s has any merit?

[Shnikes101]

Anyone have any idea if those rumors of Vega hashing(in the future) 70-100MH/s has any merit?

So far - no. Best I've seen is mid 40's which has been unstable.

There are a few folks working on it now and making progress. You can search around for yourself and find plenty of hints.

[notbatman]

^^^ The modded rx480 goes faster! Whoever is running AMD needs to be fired, they're just driving that company straight into the ground.