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

legendary

Activity: 1092

Merit: 1004

Quote from: Vann on June 18, 2017, 06:54:13 AM

Quote from: gnom4o on June 18, 2017, 06:48:47 AM

Hello,

i got following error when i try to start the miner:

OpenCL initializing...

AMD Cards available: 1
GPU #0: Hawaii, 3072 MB available, 44 compute units
GPU #0 recognized as Radeon 290X
POOL/SOLO version
Cannot build OpenCL program for GPU 0
Segmentation fault (core dumped)

I am running Ubuntu server 16.10 with installed version of amdgpu-pro-17.10-414273 and AMDSDK 3.0.
Please if anyone could give me a hint to resolve the problem.
Thank you very much for the assistance.

Hawaii cards are GCN 2 cards. The AMDGPU PRO drivers are only compatible with GCN 3 or newer cards. You need to use the Catalyst 15.12 or 15.9 drivers with GCN 1 or GCN 2 cards in Linux.

https://wiki.archlinux.org/index.php/Xorg#AMD

AMD PRO drivers do not require AMDSDK 3.0. Just, try them with the AMD PRO drivers. Try Ubuntu 16.04LTS, try an earlier version of Claymore miner, etc.

myname703

newbie

Activity: 2

Merit: 0

Quote from: myname703 on June 18, 2017, 06:08:42 AM

Hey Guys, Im kind a newbie in this, i planning buy RX560 2GB since all RX470/RX570 and RX 480/RX580 gone or rocketed price, i just curious in this version 9.5 :
1. The requirement to run 2GB card is at least 8GB of RAM and virtual memory set to 16GB?
2. What is it mean when it's stated "No DAG File"?
3. is it true with this claymore dual all the memory will be redirected to memory system?

Thanks all the master of bitcoin. need your guidance.

Anyone?

Vann

hero member

Activity: 1036

Merit: 606

Quote from: gnom4o on June 18, 2017, 06:48:47 AM

Hello,

i got following error when i try to start the miner:

OpenCL initializing...

AMD Cards available: 1
GPU #0: Hawaii, 3072 MB available, 44 compute units
GPU #0 recognized as Radeon 290X
POOL/SOLO version
Cannot build OpenCL program for GPU 0
Segmentation fault (core dumped)

I am running Ubuntu server 16.10 with installed version of amdgpu-pro-17.10-414273 and AMDSDK 3.0.
Please if anyone could give me a hint to resolve the problem.
Thank you very much for the assistance.

Hawaii cards are GCN 2 cards. The AMDGPU PRO drivers are only compatible with GCN 3 or newer cards. You need to use the Catalyst 15.12 or 15.9 drivers with GCN 1 or GCN 2 cards in Linux.

https://wiki.archlinux.org/index.php/Xorg#AMD

Genoil

sr. member

Activity: 438

Merit: 250

Quote from: sofianeelec on June 18, 2017, 06:49:25 AM

Quote from: Genoil on June 18, 2017, 06:39:30 AM

Quote from: sofianeelec on June 18, 2017, 06:32:20 AM

Hashrate Drop Every New DAG with RX480 8G this tack effect on last 3 dag ago

what can I do ??

This is most likely a hardware related issue caused by the DAG being over 2GB now. This causes something like the DAG now being spread over multiple banks of memory, slowing down access. The bigger the DAG gets, the more often the memory controller has to switch banks, the slower it responds. In reality it probably is a little bit different/nuanced, but I guess it comes down to the same thing. The most important question is; how much are the 290/390's affected? Because when they have it too, the majority is in the same sinking ship, so it's not that big of a deal. Good news for Pascal owners though, they should be fine as a similar issue was fixed when that hit the market last year.

I repeate I use RX 480 8G

you can't do anything. just calculate your losses or sell the damn thing right away. they go like hot cakes these days.

sofianeelec

newbie

Activity: 22

Merit: 0

Quote from: Genoil on June 18, 2017, 06:39:30 AM

Quote from: sofianeelec on June 18, 2017, 06:32:20 AM

Hashrate Drop Every New DAG with RX480 8G this tack effect on last 3 dag ago

what can I do ??

This is most likely a hardware related issue caused by the DAG being over 2GB now. This causes something like the DAG now being spread over multiple banks of memory, slowing down access. The bigger the DAG gets, the more often the memory controller has to switch banks, the slower it responds. In reality it probably is a little bit different/nuanced, but I guess it comes down to the same thing. The most important question is; how much are the 290/390's affected? Because when they have it too, the majority is in the same sinking ship, so it's not that big of a deal. Good news for Pascal owners though, they should be fine as a similar issue was fixed when that hit the market last year.

I repeate I use RX 480 8G

gnom4o

newbie

Activity: 1

Merit: 0

Hello,

i got following error when i try to start the miner:

OpenCL initializing...

AMD Cards available: 1
GPU #0: Hawaii, 3072 MB available, 44 compute units
GPU #0 recognized as Radeon 290X
POOL/SOLO version
Cannot build OpenCL program for GPU 0
Segmentation fault (core dumped)

I am running Ubuntu server 16.10 with installed version of amdgpu-pro-17.10-414273 and AMDSDK 3.0.
Please if anyone could give me a hint to resolve the problem.
Thank you very much for the assistance.

rednoW

legendary

Activity: 1510

Merit: 1003

Quote from: Genoil on June 18, 2017, 06:39:30 AM

This is most likely a hardware related issue caused by the DAG being over 2GB now. This causes something like the DAG now being spread over multiple banks of memory, slowing down access. The bigger the DAG gets, the more often the memory controller has to switch banks, the slower it responds. In reality it probably is a little bit different/nuanced, but I guess it comes down to the same thing. The most important question is; how much are the 290/390's affected? Because when they have it too, the majority is in the same sinking ship, so it's not that big of a deal. Good news for Pascal owners though, they should be fine as a similar issue was fixed when that hit the market last year.

Hawaii will drop only 2mhs on 199 epoch, polaris will drop 12-14 mhs
I have no Fiji cards but users say it will drop less then Hawaii.
So coming Vega will not have this issue.

Genoil

sr. member

Activity: 438

Merit: 250

Quote from: sofianeelec on June 18, 2017, 06:32:20 AM

Hashrate Drop Every New DAG with RX480 8G this tack effect on last 3 dag ago

what can I do ??

This is most likely a hardware related issue caused by the DAG being over 2GB now. This causes something like the DAG now being spread over multiple banks of memory, slowing down access. The bigger the DAG gets, the more often the memory controller has to switch banks, the slower it responds. In reality it probably is a little bit different/nuanced, but I guess it comes down to the same thing. The most important question is; how much are the 290/390's affected? Because when they have it too, the majority is in the same sinking ship, so it's not that big of a deal. Good news for Pascal owners though, they should be fine as a similar issue was fixed when that hit the market last year.

sofianeelec

newbie

Activity: 22

Merit: 0

Hashrate Drop Every New DAG with RX480 8G this tack effect on last 3 dag ago

what can I do ??

arwani1985

hero member

Activity: 817

Merit: 506

how to change port clymore ?

myname703

newbie

Activity: 2

Merit: 0

Hey Guys, Im kind a newbie in this, i planning buy RX560 2GB since all RX470/RX570 and RX 480/RX580 gone or rocketed price, i just curious in this version 9.5 :
1. The requirement to run 2GB card is at least 8GB of RAM and virtual memory set to 16GB?
2. What is it mean when it's stated "No DAG File"?
3. is it true with this claymore dual all the memory will be redirected to memory system?

Thanks all the master of bitcoin. need your guidance.

Crypto_Future

member

Activity: 72

Merit: 10

guys what is the suggested -dcri to not loose eth mining speed? 10 or 20?

Hcx

newbie

Activity: 5

Merit: 0

Hi, i have nvidia 970 and mine 3mh/s , on driver set all good, what can i do more ? how can i open the setting of mining ? sorry i am new for this basic questions.

sofianeelec

newbie

Activity: 22

Merit: 0

Quote from: rednoW on June 18, 2017, 12:46:09 AM

Quote from: adaseb on June 17, 2017, 07:29:12 PM

For the 1 millionth time.

NO HASHRATE DOESN'T DROP EVERY NEW DAG. IT ONLY DROPS ON OLD GPUS LIKE 270X / 280X / 7970. [/b][/size][/color]

You are absolutely wrong.
Hashrate is dropping heavily for polaris cards 0.1-0.2 mhs every new epoch. This is stared 2 epochs ago. With epoch 199 you'll get only 17mhs with rx480. Just use --benchmark 199 option of claymore miner.

Yes Thanks my freind you are absolutley reason I use rx 480 8G and that is not un old gpu like he said

so what is the solution my freind ??

Koreenium

newbie

Activity: 2

Merit: 0

Quote from: adaseb on June 18, 2017, 02:19:22 AM

Quote from: rednoW on June 18, 2017, 12:46:09 AM

Quote from: adaseb on June 17, 2017, 07:29:12 PM

For the 1 millionth time.

NO HASHRATE DOESN'T DROP EVERY NEW DAG. IT ONLY DROPS ON OLD GPUS LIKE 270X / 280X / 7970. [/b][/size][/color]

You are absolutely wrong.
Hashrate is dropping heavily for polaris cards 0.1-0.2 mhs every new epoch. This is stared 2 epochs ago. With epoch 199 you'll get only 17mhs with rx480. Just use --benchmark 199 option of claymore miner.

From my claymore logs

This is epoch #127

04:42:23:683   15cc   ETH - Total Speed: 83.277 Mh/s, Total Shares: 119, Rejected: 0, Time: 01:36
04:42:23:683   15cc   ETH: GPU0 28.012 Mh/s, GPU1 27.981 Mh/s, GPU2 27.839 Mh/s

Current epoch #129

13:40:17:925   708   ETH - Total Speed: 83.535 Mh/s, Total Shares: 76, Rejected: 0, Time: 01:09
13:40:17:926   708   ETH: GPU0 27.865 Mh/s, GPU1 27.900 Mh/s, GPU2 27.771 Mh/s

So it looks like it dropped about 0.05MH/s per epoch. So I retract what I wrote before.

However this isn't as bad as it was for Tahiti. Tahiti was like 0.15MH/s per epoch.

I have RX 480 Nitro+ 8gb and with every new epoch it drops by 0.2 mh/s.

I am currently mining ETC at 29.8 mh/s (epoch 131) but I can mine ETH at 30.2 mh/s (epoch 129).

patricken

newbie

Activity: 47

Merit: 0

Quote from: adaseb on June 18, 2017, 02:19:22 AM

Quote from: rednoW on June 18, 2017, 12:46:09 AM

Quote from: adaseb on June 17, 2017, 07:29:12 PM

For the 1 millionth time.

NO HASHRATE DOESN'T DROP EVERY NEW DAG. IT ONLY DROPS ON OLD GPUS LIKE 270X / 280X / 7970. [/b][/size][/color]

You are absolutely wrong.
Hashrate is dropping heavily for polaris cards 0.1-0.2 mhs every new epoch. This is stared 2 epochs ago. With epoch 199 you'll get only 17mhs with rx480. Just use --benchmark 199 option of claymore miner.

From my claymore logs

This is epoch #127

04:42:23:683   15cc   ETH - Total Speed: 83.277 Mh/s, Total Shares: 119, Rejected: 0, Time: 01:36
04:42:23:683   15cc   ETH: GPU0 28.012 Mh/s, GPU1 27.981 Mh/s, GPU2 27.839 Mh/s

Current epoch #129

13:40:17:925   708   ETH - Total Speed: 83.535 Mh/s, Total Shares: 76, Rejected: 0, Time: 01:09
13:40:17:926   708   ETH: GPU0 27.865 Mh/s, GPU1 27.900 Mh/s, GPU2 27.771 Mh/s

So it looks like it dropped about 0.05MH/s per epoch. So I retract what I wrote before.

However this isn't as bad as it was for Tahiti. Tahiti was like 0.15MH/s per epoch.

I only use Tahiti for ZEC mining.

deadsix

hero member

Activity: 751

Merit: 517

Fail to plan, and you plan to fail.

Hey Claymore, I love that you upgraded EthMan to be so much more powerful. I think its time for some improvements to the watchdog too. Far too many times in the recent versions does the miner just hangs for long periods. The watchdog does nothing untill I connect to the system and do an activity like a right-click or a down-arrow on the mining window itself. Thats when the watchdog finally wakes up and performs whatever task its been setup to perform.

Merlig

member

Activity: 143

Merit: 11

Hi guys,

I am encountering problems with Claymore and was wondering if anyone can make more from the logfile than me...

Started normal, not many args:

Code:

23:49:25:991 11bc args: -epool eu2.ethermine.org:4444 -ewal 0x968425821DEB1A37E274Df372f8603038cFA3BFe.RX570 -epsw x
23:49:25:991 11bc
23:49:25:991 11bc ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
23:49:25:991 11bc º Claymore's Dual ETH + DCR/SC/LBC/PASC GPU Miner v9.5 º
23:49:26:007 11bc ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ¼
23:49:26:007 11bc

It did recognize my cards:

Code:

23:49:27:460 11bc AMD Cards available: 6
23:49:27:476 11bc GPU #0: Ellesmere, 4096 MB available, 32 compute units
23:49:27:476 11bc GPU #0 recognized as Radeon RX 470/570
23:49:27:476 11bc GPU #1: Ellesmere, 8192 MB available, 32 compute units
23:49:27:491 11bc GPU #1 recognized as Radeon RX 470/570
23:49:27:491 11bc GPU #2: Ellesmere, 4096 MB available, 32 compute units
23:49:27:507 11bc GPU #2 recognized as Radeon RX 470/570
23:49:27:507 11bc GPU #3: Ellesmere, 4096 MB available, 32 compute units
23:49:27:507 11bc GPU #3 recognized as Radeon RX 470/570
23:49:27:523 11bc GPU #4: Ellesmere, 8192 MB available, 32 compute units
23:49:27:523 11bc GPU #4 recognized as Radeon RX 470/570
23:49:27:523 11bc GPU #5: Ellesmere, 4096 MB available, 32 compute units
23:49:27:538 11bc GPU #5 recognized as Radeon RX 470/570
23:49:27:538 11bc POOL/SOLO version
23:49:27:538 11bc b351
23:49:27:538 11bc Platform: Windows
23:49:27:601 11bc start building OpenCL program for GPU 0...
23:49:28:273 11bc done
23:49:28:507 11bc start building OpenCL program for GPU 1...
23:49:28:757 11bc done
23:49:28:976 11bc start building OpenCL program for GPU 2...
23:49:29:273 11bc done
23:49:29:507 11bc start building OpenCL program for GPU 3...
23:49:29:773 11bc done
23:49:29:992 11bc start building OpenCL program for GPU 4...
23:49:30:242 11bc done
23:49:30:460 11bc start building OpenCL program for GPU 5...
23:49:30:710 11bc done
23:49:30:945 11bc GPU #0: algorithm ASM
23:49:30:960 11bc GPU #1: algorithm ASM
23:49:30:976 11bc GPU #2: algorithm ASM
23:49:31:007 11bc GPU #3: algorithm ASM
23:49:31:023 11bc GPU #4: algorithm ASM
23:49:31:039 11bc GPU #5: algorithm ASM
23:49:31:039 11bc cudaGetDeviceCount failed (35, CUDA driver version is insufficient for CUDA runtime version), probably no CUDA devices
23:49:31:054 11bc No NVIDIA CUDA GPUs detected.
23:49:31:054 11bc Total cards: 6

Worked fine until:

Code:

01:51:32:900 13dc ETH: 06/19/17-01:51:32 - New job from eu2.ethermine.org:4444
01:51:32:900 13dc target: 0x0000000112e0be82 (diff: 4000MH), epoch #129
01:51:32:900 13dc ETH - Total Speed: 155.995 Mh/s, Total Shares: 265, Rejected: 0, Time: 02:01
01:51:32:915 13dc ETH: GPU0 26.001 Mh/s, GPU1 25.011 Mh/s, GPU2 26.993 Mh/s, GPU3 27.001 Mh/s, GPU4 24.997 Mh/s, GPU5 25.992 Mh/s
01:51:34:900 11bc GPU0 t=77C fan=40%, GPU1 t=70C fan=41%, GPU2 t=69C fan=44%, GPU3 t=63C fan=36%, GPU4 t=57C fan=22%, GPU5 t=53C fan=24%
01:51:34:900 11bc em hbt: 0, fm hbt: 31,
01:51:34:900 11bc watchdog - thread 0 (gpu0), hb time 297
01:51:34:916 11bc watchdog - thread 1 (gpu0), hb time 156
01:51:34:916 11bc watchdog - thread 2 (gpu1), hb time 328
01:51:34:916 11bc watchdog - thread 3 (gpu1), hb time 156
01:51:34:916 11bc watchdog - thread 4 (gpu2), hb time 172
01:51:34:916 11bc watchdog - thread 5 (gpu2), hb time 0
01:51:34:931 11bc watchdog - thread 6 (gpu3), hb time 125
01:51:34:931 11bc watchdog - thread 7 (gpu3), hb time 282
01:51:34:931 11bc watchdog - thread 8 (gpu4), hb time 141
01:51:34:931 11bc watchdog - thread 9 (gpu4), hb time 313
01:51:34:931 11bc watchdog - thread 10 (gpu5), hb time 313
01:51:34:947 11bc watchdog - thread 11 (gpu5), hb time 172
01:51:39:463 13dc ETH: checking pool connection...

Then it started to go wrong it seems:

Code:

01:51:54:949 11bc Failed to get fan info
01:51:54:980 11bc Cannot get Overdrive capabilities for adapter 6
01:51:54:980 11bc Cannot get Overdrive capabilities for adapter 12
01:51:54:980 11bc Cannot get Overdrive capabilities for adapter 18
01:51:54:996 11bc Cannot get Overdrive capabilities for adapter 24
01:51:55:168 11bc Cannot get Overdrive capabilities for adapter 30
01:51:58:559 11bc Cannot get Overdrive capabilities for adapter 0
01:51:58:559 11bc Cannot get Overdrive capabilities for adapter 6
01:51:58:559 11bc Cannot get Overdrive capabilities for adapter 12
01:51:58:559 11bc Cannot get Overdrive capabilities for adapter 18
01:51:58:574 11bc Cannot get Overdrive capabilities for adapter 24
01:51:58:574 11bc Cannot get Overdrive capabilities for adapter 30
01:51:59:496 13dc ETH: checking pool connection...

only 3 cards working

Code:

01:52:01:215 13dc ETH: 06/19/17-01:52:01 - New job from eu2.ethermine.org:4444
01:52:01:215 13dc target: 0x0000000112e0be82 (diff: 4000MH), epoch #129
01:52:01:215 13dc ETH - Total Speed: 76.929 Mh/s, Total Shares: 265, Rejected: 0, Time: 02:02
01:52:01:215 13dc ETH: GPU0 26.027 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 24.949 Mh/s, GPU5 25.954 Mh/s
01:52:01:903 11bc Cannot get Overdrive capabilities for adapter 0
01:52:01:903 11bc Cannot get Overdrive capabilities for adapter 6
01:52:01:903 11bc Cannot get Overdrive capabilities for adapter 12
01:52:01:903 11bc Cannot get Overdrive capabilities for adapter 18
01:52:01:919 11bc Cannot get Overdrive capabilities for adapter 24
01:52:01:919 11bc Cannot get Overdrive capabilities for adapter 30

only 2 cards working:

Code:

01:52:07:544 13dc ETH: 06/19/17-01:52:07 - New job from eu2.ethermine.org:4444
01:52:07:544 13dc target: 0x0000000112e0be82 (diff: 4000MH), epoch #129
01:52:07:560 13dc ETH - Total Speed: 52.016 Mh/s, Total Shares: 265, Rejected: 0, Time: 02:02
01:52:07:560 13dc ETH: GPU0 26.030 Mh/s, GPU1 0.000 Mh/s, GPU2 0.000 Mh/s, GPU3 0.000 Mh/s, GPU4 0.000 Mh/s, GPU5 25.986 Mh/s
01:52:08:576 11bc Cannot get Overdrive capabilities for adapter 0

no cards working:

Code:

01:52:27:531 13dc ETH: 06/19/17-01:52:27 - New job from eu2.ethermine.org:4444
01:52:27:531 13dc target: 0x0000000112e0be82 (diff: 4000MH), epoch #129
01:52:27:531 13dc ETH - Total Speed: 0.000 Mh/s, Total Shares: 265, Rejected: 0, Time: 02:02
01:52:27:531 13dc 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

until here:

Code:

01:53:16:333 11bc watchdog - thread 0 (gpu0), hb time 58797
01:53:16:333 11bc watchdog - thread 1 (gpu0), hb time 58953
01:53:16:333 11bc watchdog - thread 2 (gpu1), hb time 81985
01:53:16:348 11bc WATCHDOG: GPU 1 hangs in OpenCL call, exit
01:53:16:348 11bc watchdog - thread 3 (gpu1), hb time 81828
01:53:16:364 11bc WATCHDOG: GPU 1 hangs in OpenCL call, exit
01:53:16:364 11bc watchdog - thread 4 (gpu2), hb time 81406
01:53:16:364 11bc WATCHDOG: GPU 2 hangs in OpenCL call, exit
01:53:16:364 11bc watchdog - thread 5 (gpu2), hb time 81141
01:53:16:380 11bc WATCHDOG: GPU 2 hangs in OpenCL call, exit
01:53:16:380 11bc watchdog - thread 6 (gpu3), hb time 80407
01:53:16:380 11bc WATCHDOG: GPU 3 hangs in OpenCL call, exit
01:53:16:380 11bc watchdog - thread 7 (gpu3), hb time 80563
01:53:16:395 11bc WATCHDOG: GPU 3 hangs in OpenCL call, exit
01:53:16:395 11bc watchdog - thread 8 (gpu4), hb time 79109
01:53:16:395 11bc WATCHDOG: GPU 4 hangs in OpenCL call, exit
01:53:16:411 11bc watchdog - thread 9 (gpu4), hb time 78953
01:53:16:411 11bc WATCHDOG: GPU 4 hangs in OpenCL call, exit
01:53:16:411 11bc watchdog - thread 10 (gpu5), hb time 58734
01:53:16:411 11bc watchdog - thread 11 (gpu5), hb time 58578
01:53:16:442 11bc Cannot get Overdrive capabilities for adapter 0
01:53:16:442 11bc Cannot get Overdrive capabilities for adapter 6
01:53:16:442 11bc Cannot get Overdrive capabilities for adapter 12
01:53:16:442 11bc Cannot get Overdrive capabilities for adapter 18
01:53:16:458 11bc Cannot get Overdrive capabilities for adapter 24
01:53:16:458 11bc Cannot get Overdrive capabilities for adapter 30
01:53:18:067 11bc Restarting OK, exit...

When I woke up this morning, there was no claymore running anymore and Windows Device Manager showed all my 6 cards with a yellow exclamation mark...

Does anyone have a clue what might have gone wrong?

Edit: I just found out that it seems, Windows did install something at around the time it started to mess up: Advanced Micro Devices, Inc. - Graphics Adapter WDDM1.1, Graphics Adapter WDDM1.3, Graphics Adapter WDDM2.0 - Radeon (TM) RX 470 Graphics

adaseb

legendary

Activity: 3808

Merit: 1723

Quote from: rednoW on June 18, 2017, 12:46:09 AM

Quote from: adaseb on June 17, 2017, 07:29:12 PM

For the 1 millionth time.

NO HASHRATE DOESN'T DROP EVERY NEW DAG. IT ONLY DROPS ON OLD GPUS LIKE 270X / 280X / 7970. [/b][/size][/color]

You are absolutely wrong.
Hashrate is dropping heavily for polaris cards 0.1-0.2 mhs every new epoch. This is stared 2 epochs ago. With epoch 199 you'll get only 17mhs with rx480. Just use --benchmark 199 option of claymore miner.

From my claymore logs

This is epoch #127

04:42:23:683   15cc   ETH - Total Speed: 83.277 Mh/s, Total Shares: 119, Rejected: 0, Time: 01:36
04:42:23:683   15cc   ETH: GPU0 28.012 Mh/s, GPU1 27.981 Mh/s, GPU2 27.839 Mh/s

Current epoch #129

13:40:17:925   708   ETH - Total Speed: 83.535 Mh/s, Total Shares: 76, Rejected: 0, Time: 01:09
13:40:17:926   708   ETH: GPU0 27.865 Mh/s, GPU1 27.900 Mh/s, GPU2 27.771 Mh/s

So it looks like it dropped about 0.05MH/s per epoch. So I retract what I wrote before.

However this isn't as bad as it was for Tahiti. Tahiti was like 0.15MH/s per epoch.

americandesi

hero member

Activity: 518

Merit: 500

BTC < > INR & USD

Hey guys..

Am mining using GTX 1070 at ~29 MHs ETH / ~290 Mhs SC (Claymore Dual Mine (ETH/SC). My AfterBurner settings are below.

Can you advise on the following:

1) Do you think the OC settings are high and I might risk frying my GPU?
2) What are the ideal afterburner settings for ETH/SC dual mining using GTX 1070
3) I know a few people on the forums are getting ~32 mhs on GTX 1070. Any suggestions on how to optimize/improve hashrate? (Please provide the GPU AfterBurner settings?)

My Settings are below:

CPU Clock ~1550 mhz
Memory Clock ~ 4400 mhz

Core voltage - 0
Power Limit - 80
Temp Limit - 75
Core Clock ~ 100
Memory Clock ~600
Fan Speed - Auto

Topic: Claymore's Dual Ethereum AMD+NVIDIA GPU Miner v15.0 (Windows/Linux) - page 811. (Read 6590718 times)