Show Posts
|
Pages: [1] 2 »
|
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.
|
|
|
Hello
i got problems with few miners.... they occasionally get this problem. Before v11 the rigs were stable and never had problems. Any ideas? :
13:09:30:629 1638 ETH: 03/07/18-13:09:30 - New job from eth-eu1.nanopool.org:9999 13:09:30:629 1638 target: 0x000000006df37f67 (diff: 10000MH), epoch 173(2.35GB) 13:09:30:629 1638 ETH - Total Speed: 188.924 Mh/s, Total Shares: 18, Rejected: 0, Time: 00:12 13:09:30:629 1638 ETH: GPU0 31.803 Mh/s, GPU1 31.572 Mh/s, GPU2 31.756 Mh/s, GPU3 31.795 Mh/s, GPU4 31.770 Mh/s, GPU5 30.229 Mh/s 13:09:36:895 1638 got 243 bytes 13:09:36:895 1638 buf: {"jsonrpc":"2.0","id":0,"result":["0x9535d44aa03ed3044af9ec36125bd117575459f1f19323e8af46520446b9f05e","0x4e2977c9152afafb8ea63ea5434ada0692b481b8ad37d05391c3a7738d63eb5d","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
13:09:36:895 1638 parse packet: 242 13:09:36:895 1638 ETH: job changed 13:09:36:895 1638 new buf size: 0 13:09:36:895 1638 ETH: 03/07/18-13:09:36 - New job from eth-eu1.nanopool.org:9999 13:09:36:895 1638 target: 0x000000006df37f67 (diff: 10000MH), epoch 173(2.35GB) 13:09:36:895 1638 ETH - Total Speed: 190.483 Mh/s, Total Shares: 18, Rejected: 0, Time: 00:12 13:09:36:895 1638 ETH: GPU0 31.789 Mh/s, GPU1 31.716 Mh/s, GPU2 31.765 Mh/s, GPU3 31.730 Mh/s, GPU4 31.732 Mh/s, GPU5 31.751 Mh/s 13:09:39:614 1638 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x8fa29ef", "0x00000000000000000000000000000000000000000000000000000000c2d74293"]}
13:09:39:692 18d8 GPU0 t=43C fan=49%, GPU1 t=45C fan=50%, GPU2 t=47C fan=56%, GPU3 t=47C fan=56%, GPU4 t=51C fan=64%, GPU5 t=40C fan=48% 13:09:40:333 1638 ETH: checking pool connection... 13:09:40:333 1638 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
13:09:40:380 1638 got 243 bytes 13:09:40:380 1638 buf: {"jsonrpc":"2.0","id":0,"result":["0x9535d44aa03ed3044af9ec36125bd117575459f1f19323e8af46520446b9f05e","0x4e2977c9152afafb8ea63ea5434ada0692b481b8ad37d05391c3a7738d63eb5d","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
13:09:40:380 1638 parse packet: 242 13:09:40:380 1638 ETH: job is the same 13:09:40:380 1638 new buf size: 0 13:09:40:536 378 em hbt: 16, fm hbt: 94, 13:09:40:536 378 watchdog - thread 0 (gpu0), hb time 47 13:09:40:536 378 watchdog - thread 1 (gpu0), hb time 172 13:09:40:536 378 watchdog - thread 2 (gpu1), hb time 47 13:09:40:536 378 watchdog - thread 3 (gpu1), hb time 172 13:09:40:536 378 watchdog - thread 4 (gpu2), hb time 78 13:09:40:536 378 watchdog - thread 5 (gpu2), hb time 203 13:09:40:536 378 watchdog - thread 6 (gpu3), hb time 78 13:09:40:536 378 watchdog - thread 7 (gpu3), hb time 203 13:09:40:536 378 watchdog - thread 8 (gpu4), hb time 94 13:09:40:536 378 watchdog - thread 9 (gpu4), hb time 219 13:09:40:536 378 watchdog - thread 10 (gpu5), hb time 203 13:09:40:536 378 watchdog - thread 11 (gpu5), hb time 78 13:09:50:349 1638 ETH: checking pool connection... 13:09:50:349 1638 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
13:09:50:396 1638 got 243 bytes 13:09:50:396 1638 buf: {"jsonrpc":"2.0","id":0,"result":["0x9535d44aa03ed3044af9ec36125bd117575459f1f19323e8af46520446b9f05e","0x4e2977c9152afafb8ea63ea5434ada0692b481b8ad37d05391c3a7738d63eb5d","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
13:09:50:396 1638 parse packet: 242 13:09:50:396 1638 ETH: job is the same 13:09:50:396 1638 new buf size: 0 13:09:50:661 10b0 GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure 13:09:50:661 10b0 GPU 0, GpuMiner kx failed 1 13:09:50:661 10b0 Set global fail flag, failed GPU0 13:09:50:661 10b0 GPU 0 failed 13:09:50:661 18bc GPU 0, GpuMiner cu_k1 failed 4, unspecified launch failure 13:09:50:661 18bc GPU 0, GpuMiner kx failed 1 13:09:50:661 18bc Set global fail flag, failed GPU0 13:09:50:661 18bc GPU 0 failed 13:09:50:677 a64 GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure 13:09:50:677 a64 GPU 4, GpuMiner kx failed 1 13:09:50:677 a64 Set global fail flag, failed GPU4 13:09:50:677 a64 GPU 4 failed 13:09:50:677 20 GPU 4, GpuMiner cu_k1 failed 4, unspecified launch failure 13:09:50:677 20 GPU 4, GpuMiner kx failed 1 13:09:50:677 20 Set global fail flag, failed GPU4 13:09:50:677 20 GPU 4 failed 13:09:50:708 eb8 GPU 5, GpuMiner cu_k1 failed 4, unspecified launch failure 13:09:50:708 eb8 GPU 5, GpuMiner kx failed 1 13:09:50:708 eb8 Set global fail flag, failed GPU5 13:09:50:708 eb8 GPU 5 failed 13:09:50:708 648 GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure 13:09:50:708 648 GPU 3, GpuMiner kx failed 1 13:09:50:708 648 Set global fail flag, failed GPU3 13:09:50:708 648 GPU 3 failed 13:09:50:708 1008 GPU 5, GpuMiner cu_k1 failed 4, unspecified launch failure 13:09:50:708 1008 GPU 5, GpuMiner kx failed 1 13:09:50:708 1008 Set global fail flag, failed GPU5 13:09:50:724 1008 GPU 5 failed 13:09:50:724 1864 GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure 13:09:50:724 1864 GPU 2, GpuMiner kx failed 1 13:09:50:724 1864 Set global fail flag, failed GPU2 13:09:50:724 1864 GPU 2 failed 13:09:50:724 2b8 GPU 3, GpuMiner cu_k1 failed 4, unspecified launch failure 13:09:50:724 2b8 GPU 3, GpuMiner kx failed 1 13:09:50:724 2b8 Set global fail flag, failed GPU3 13:09:50:724 2b8 GPU 3 failed 13:09:50:724 11c4 GPU 2, GpuMiner cu_k1 failed 4, unspecified launch failure 13:09:50:724 11c4 GPU 2, GpuMiner kx failed 1 13:09:50:724 11c4 Set global fail flag, failed GPU2 13:09:50:724 11c4 GPU 2 failed 13:09:50:771 b54 GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure 13:09:50:771 b54 GPU 1, GpuMiner kx failed 1 13:09:50:771 b54 Set global fail flag, failed GPU1 13:09:50:771 b54 GPU 1 failed 13:09:50:771 a5c GPU 1, GpuMiner cu_k1 failed 4, unspecified launch failure 13:09:50:771 a5c GPU 1, GpuMiner kx failed 1 13:09:50:771 a5c Set global fail flag, failed GPU1 13:09:50:771 a5c GPU 1 failed 13:09:59:599 1638 got 243 bytes 13:09:59:599 1638 buf: {"jsonrpc":"2.0","id":0,"result":["0xe9e46efc3420221902c1014737fab8f50d03aada3ab84095d8e013cb07d960e8","0x4e2977c9152afafb8ea63ea5434ada0692b481b8ad37d05391c3a7738d63eb5d","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
13:09:59:599 1638 parse packet: 242 13:09:59:599 1638 ETH: job changed 13:09:59:599 1638 new buf size: 0 13:09:59:599 1638 ETH: 03/07/18-13:09:59 - New job from eth-eu1.nanopool.org:9999 13:09:59:599 1638 target: 0x000000006df37f67 (diff: 10000MH), epoch 173(2.35GB) 13:09:59:599 1638 ETH - Total Speed: 0.000 Mh/s, Total Shares: 18, Rejected: 0, Time: 00:13 13:09:59:599 1638 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 13:09:59:631 1638 send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x00000000000000000000000000000000000000000000000000000000c2d74293"]}
13:10:00:365 1638 ETH: checking pool connection... 13:10:00:365 1638 send: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
13:10:00:412 1638 got 243 bytes 13:10:00:412 1638 buf: {"jsonrpc":"2.0","id":0,"result":["0xe9e46efc3420221902c1014737fab8f50d03aada3ab84095d8e013cb07d960e8","0x4e2977c9152afafb8ea63ea5434ada0692b481b8ad37d05391c3a7738d63eb5d","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
13:10:00:412 1638 parse packet: 242 13:10:00:412 1638 ETH: job is the same 13:10:00:412 1638 new buf size: 0 13:10:03:740 1638 got 243 bytes 13:10:03:740 1638 buf: {"jsonrpc":"2.0","id":0,"result":["0x215e3b5366dc0ad70a3c94e90f89aef730f523866a9b70cc5b584d22eb40563c","0x4e2977c9152afafb8ea63ea5434ada0692b481b8ad37d05391c3a7738d63eb5d","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
13:10:03:740 1638 parse packet: 242 13:10:03:740 1638 ETH: job changed 13:10:03:740 1638 new buf size: 0 13:10:03:740 1638 ETH: 03/07/18-13:10:03 - New job from eth-eu1.nanopool.org:9999 13:10:03:740 1638 target: 0x000000006df37f67 (diff: 10000MH), epoch 173(2.35GB) 13:10:03:740 1638 ETH - Total Speed: 0.000 Mh/s, Total Shares: 18, Rejected: 0, Time: 00:13 13:10:03:740 1638 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
|
|
|
guys forget about blake2s and XVG. Switch to keccak with SMARTcash. Online wallet, 100% working 0% fee official pool only problem with exchange - need to make account www.coinexchange.io and change to BTC (eventually to ETC later for withdrawal)
|
|
|
you cannot mine CREA it's keccak-c. dont bother keccak there is no PROFITABLE coin.
i mined MAX here: max.thecoin.pw. WTM said 0 profits.
Actually SMART is Keccak and SMART is more profitable than XVG - at least for RX480. Also SMART pools are much more stable as there are official ones. where to mine SMART and where to sell? Whattomine shows no exchanges? is there online wallet ?
|
|
|
Has anyone found a way to mine keccak? Whatever coin I try to mine, on whatever pool, i get 100% rejected shares on keccak. Why is that?
Same question with no answer. All night I was tried and no success. Last houpe was Smart Cash, but last night they went down with pool, and it seems that its some shady project. Lots of people complaining. How I figure out, Keccak and Blake is a fork from Sha256. All coins are old from 2013-14,... and pools are too long closed. Maybe we need Algo to mine ERC ICO tokens  you cannot mine CREA it's keccak-c. dont bother keccak there is no PROFITABLE coin. i mined MAX here: max.thecoin.pw. WTM said 0 profits.
|
|
|
i just tried MAX coin on max on pool: max.thecoin.pw
but the hashrate is 1215 MH/s on 6xrx580, and WTM shows me only 1.1 USD extra on 6xRX580 this makes no sense.
VERGE was 4 USD... not is 2.5 USD still makes sense to do it but below 2 usd is useless.
|
|
|
nlpool works ok now.. i got work etc. unfortunately massive orphans makes us work for nothing... hoprefully a good block now.
|
|
|
yes but we need something to dualming with ETH
So not so much algos.
|
|
|
total net hash has grown SO MUCH that a block comes up every 1-2 hours so need to be patient. P.S last 2 blocks were ORPHANS unfortunately  verge network is just too big for all the NODEs to handle. anyone got info on keccak coins ?
|
|
|
NLPOOL was stable... for 2 days. Everything was GREAT. 1st day i got AS MUCH XVG as unimining 2.5 DAYS!
Now nlpool has been probable DDOSed by other pools that steal... or it just grow so much that cannot handle.. but that's not sure.
Cause the pool was ok for some time with 13 TH/s. Now it's 9-10 and there is problems so i guess attacks from others.
NO OTHER POOL IS OK (maybe antmine now.. was overloaded but i dont know about payments).
DONT USE OXO! 100% STEAL of hashpower.
|
|
|
i think we need a new topic for NLPOOL - XVG pool.
This is gettting to much info here that is not realted directly with Claymore's miner.
The pool works now, it was down for 10 or so minutes - probably service.
The pool has grown quite a bit and i think admin need to reconfigure - add some power...
EVEN with 20% downtime is much better to mine with it than unimining that takes 50% ;-)
|
|
|
NLPOOL - this is LEGIT and NICE!
Please tell me why ORPHAN blocks came up? what might be the reason?
|
|
|
ahaspool is not good - cause you can just set the algo - blake2s.
But the ahash send you diffrent coin work - not only XVG, sometimes TAJ, soetimes neva... but this coin is worthless. They should send the work that is most profitable but when they switch to those coins my BTC earn indicator went flat.. instead of rise.
That's the problem, i not accusse of steal.
I used to mine with algo switching on ahashpool was ok, but no when zec / eth i back in game makes no sense (and the stability wasnt so good, with 300+ gpu's i need stability)
|
|
|
Hey guyS!
it's 24h since i switched to nlpool.nl for blake2s.
THIS IS much better than ahash, and DEFINATELY than unimining!
i got 470 XVG from 30 amd RX GPUs (40-42 GH)! The pool is big now almost 9 TH!
On unimining i got 360 IN 2.5 DAYS!!!!!!! THAT JUST PLAIN THEFT!
HAIL to nlpool ;-)
|
|
|
Please read: https://bitcointalk.org/index.php?topic=1433925.msg30398663#msg30398663Again, i am very sorry that some blocks were lost, however this is solved now. I would appreciate it if we could make it up to you ;-) Also, i would like to say that looking at the miners dashboard is see people mining XVG with the wrong password settings. -p c=XVG-blake2s <<< This is incorrect -p c=XVG,ID=004_RX580_4 << Incorrect -p x << Incorrect. The correct password for verge is c=XVG nothing more, nothing less ;-) oooh that sucks... i changed all to just c=XVG. I need to have my miners on diffrent position - cause i need to see if they all mine the same etc. I used ID= from ahash and on unimining and it worked... i also get all sucess shares from your pool... do not know much about pool admin but should work imho anyway switched and we will see.
|
|
|
YES - Mine with NLPOOL KOREPOOL - switch all to NLPOOL. too much of small pools.
We need 2-5 TH, and then we have 1-2 blocks per hour, which is quite ok.
I just put 40 GH on nlpool. Works fine, i could suggest to start with higher diff - at least 10 or so. Cause in the beggining there was a flood of shares ;-)
now the diff adjusted and is beetween 35 and 56.
What we need now is more hashpower so we can catch some blocks.
|
|
|
with dual mine on XVG and XSH the hashrate is not very stable with dcri 44-45. any one has reach a decent drci so the ETH is stale like with DCR. Thanks
Please inform on your equipment. There is a 200-250W extra power drain using DUAL with XVG, so either you are too low on POWER settings, or your PSU cannot provide. I have seen that with RX470 i put -5 power instead of -10 power and got extra hash on eth and XVG also with higher DCRI.
|
|
|
Hi there i mined 2,5 days on unimining (with new address) 5 rigs of 6 RX cards (5x RX580 and 1xrx470), hashrate on claymore around 41000. The pool always says less but that just not accurate. I assumed let it be 35000, with What to mine and highest ever difficulty from today (but 3 days average is much lower) it said should be 200 XVG per day. I mined barely 150/day and put 35000 only in the calculator. So honestly i should get 230 at least with 30 GPU's.  i switched to antmine now and will get back with info.
|
|
|
Hello
i recently switched all my GTX 1070/1070ti to ETH due to ZEC price drops etc. I find some rigs work ok (stable) and on some the hashrate is fluctuating.
may this be realted to drivers? are there drivers ok ?
385.41 for 6x1070 rigs
and 388.59 fo 6x1070ti rigs? or claymore requires the newest nvidia drivers?
i use v10.5 version.... the HASHRATE is ok at the start, but then after some time fluctuates. I check on nanopool for 6hr average and find some rigs only have 170 MH/s avg.
settings differ cause i try...
1070: power 75 (high but i want stability, not really low power), core -200 (some -190 now), mem +680 (some +690). the rigs are very cool temps around 38-42 deg.
i put -r 120 so the client restarts (i find this give better hash?)
MY RX580 rigs are 100% stable there is no fluctiation but nvidia with ETH gives me headache plz help ;-)
ETH: 02/03/18-13:29:46 - New job from eth-eu1.nanopool.org:9999 ETH - Total Speed: 191.148 Mh/s, Total Shares: 87, Rejected: 0, Time: 01:22 ETH: GPU0 31.876 Mh/s, GPU1 31.869 Mh/s, GPU2 31.899 Mh/s, GPU3 31.850 Mh/s, GPU4 31.756 Mh/s, GPU5 31.900 Mh/s ETH: 02/03/18-13:30:11 - New job from eth-eu1.nanopool.org:9999 ETH - Total Speed: 184.847 Mh/s, Total Shares: 87, Rejected: 0, Time: 01:22 ETH: GPU0 31.192 Mh/s, GPU1 29.779 Mh/s, GPU2 31.177 Mh/s, GPU3 30.376 Mh/s, GPU4 31.250 Mh/s, GPU5 31.073 Mh/s GPU0 t=39C fan=69%, GPU1 t=42C fan=69%, GPU2 t=41C fan=69%, GPU3 t=38C fan=69%, GPU4 t=32C fan=69%, GPU5 t=48C fan=69% ETH: 02/03/18-13:30:27 - New job from eth-eu1.nanopool.org:9999 ETH - Total Speed: 174.012 Mh/s, Total Shares: 87, Rejected: 0, Time: 01:23 ETH: GPU0 23.557 Mh/s, GPU1 30.301 Mh/s, GPU2 30.699 Mh/s, GPU3 30.942 Mh/s, GPU4 30.857 Mh/s, GPU5 27.655 Mh/s ETH: 02/03/18-13:30:35 - New job from eth-eu1.nanopool.org:9999 ETH - Total Speed: 146.193 Mh/s, Total Shares: 87, Rejected: 0, Time: 01:23 ETH: GPU0 22.078 Mh/s, GPU1 22.095 Mh/s, GPU2 31.022 Mh/s, GPU3 22.006 Mh/s, GPU4 26.825 Mh/s, GPU5 22.167 Mh/s ETH: 02/03/18-13:30:43 - New job from eth-eu1.nanopool.org:9999 ETH - Total Speed: 189.880 Mh/s, Total Shares: 87, Rejected: 0, Time: 01:23 ETH: GPU0 31.674 Mh/s, GPU1 31.843 Mh/s, GPU2 31.833 Mh/s, GPU3 31.756 Mh/s, GPU4 31.142 Mh/s, GPU5 31.633 Mh/s GPU0 t=39C fan=69%, GPU1 t=43C fan=69%, GPU2 t=43C fan=69%, GPU3 t=38C fan=69%, GPU4 t=32C fan=69%, GPU5 t=48C fan=69% ETH: 02/03/18-13:30:50 - New job from eth-eu1.nanopool.org:9999 ETH - Total Speed: 191.070 Mh/s, Total Shares: 87, Rejected: 0, Time: 01:23 ETH: GPU0 31.879 Mh/s, GPU1 31.858 Mh/s, GPU2 31.790 Mh/s, GPU3 31.868 Mh/s, GPU4 31.859 Mh/s, GPU5 31.816 Mh/s ETH: 02/03/18-13:30:51 - New job from eth-eu1.nanopool.org:9999 ETH - Total Speed: 190.558 Mh/s, Total Shares: 87, Rejected: 0, Time: 01:23 ETH: GPU0 31.838 Mh/s, GPU1 31.822 Mh/s, GPU2 31.588 Mh/s, GPU3 31.853 Mh/s, GPU4 31.816 Mh/s, GPU5 31.641 Mh/s ETH: 02/03/18-13:31:12 - New job from eth-eu1.nanopool.org:9999 ETH - Total Speed: 189.109 Mh/s, Total Shares: 87, Rejected: 0, Time: 01:23 ETH: GPU0 31.362 Mh/s, GPU1 31.209 Mh/s, GPU2 31.028 Mh/s, GPU3 31.851 Mh/s, GPU4 31.836 Mh/s, GPU5 31.823 Mh/s
|
|
|
|