PhoenixMiner 6.2c: fastest Ethereum/Ethash miner with lowest devfee (Win/Linux)

[sergioheadache]

hello,

i have to say, i like this miner very much, but have 1 problem.

i have rig with 12 x rx580 cards,

i set parameter -minfan 90  , but it doesnt work, fans still work as default

any advice ?

thanks

[1656862723]

1656862723

[1656862723]

1656862723

[murgorx]

hello,

i have to say, i like this miner very much, but have 1 problem.

i have rig with 12 x rx580 cards,

i set parameter -minfan 90  , but it doesnt work, fans still work as default

any advice ?

thanks

Try with -fanmin 90 -fanmax 95 and see if it does anything, but it should resolve the issue. Watch out for the syntax!

[Kgonla]

Hello, I'm using 2 RX 580 GPUs

When I use -clKernel 0
The hash rate moves up & down, most of time it is showing 64 MH/s, sometimes go down to 58 MH/s
The average 5 min. is just above 58 MH/s

When I use -clKernel 1
The hash rate is more stable, most of the time is 60 MH/s sometimes go down to 59.7 or so
The average 5 min. is about 59.8

With kernel 0, looking at it, the average appears to be over 62 MH/s
What I must believe the 5min. average or what I see on the screen?
Could the average 5 min. with kernel 0 be wrong?

& why just after starting miner it tell me the 5 min. average when I have been only mining for 1 min. or even less?

Thank you.

https://fotos.subefotos.com/33477a907623ed0d4f1ae7651beadd54o.jpg

[pinamalina]

hello,

i have to say, i like this miner very much, but have 1 problem.

i have rig with 12 x rx580 cards,

i set parameter -minfan 90  , but it doesnt work, fans still work as default

any advice ?

thanks

According to the documentation: "Hardware control options (AMD cards only; use comma to specify different values for each GPU):"
We might therefore assume that single value stands for all cards.
I have observed that "-tt 60" option does not work and got it working with setting an individual value for each card like: "-tt 60,60,60,60,60,60,60,60" on the 8 AMD rig.
Not sure if this is a "bug" or intended behavior; the supplied readme.txt (the documentation) is not clear on the details.

My understanding of the temperature management in PhoenixMiner is that you need to setup a target temperature (-tt) before you can utilise other temperature parameters such as -fanmin, -fanmax, -tmax...

So give next options a try (taking into the account you have 12 amd GPUs):
-tt 60,60,60,60,60,60,60,60,60,60,60,60,
-fanmin 90,90,90,90,90,90,90,90,90,90,90,90

BTW: Using -fanmin 90 is in my opinion not the best approach in keeping the temperature as steady as possible. It will introduce higher than optimal temperature fluctuation which is bad for the hardware. The "default" is in my opinion optimal -fanmin 0 and -fanmax 100 leaving the miner a full flexibility on managing the target temperature of the GPUs using the build in temperature/fan curve. PH does not document how it does the temperature management so we do not know what exactly will the "-fanmin 90" do in terms of temperature management.

[pinamalina]

Hello, I'm using 2 RX 580 GPUs

When I use -clKernel 0
The hash rate moves up & down, most of time it is showing 64 MH/s, sometimes go down to 58 MH/s
The average 5 min. is just above 58 MH/s

When I use -clKernel 1
The hash rate is more stable, most of the time is 60 MH/s sometimes go down to 59.7 or so
The average 5 min. is about 59.8

With kernel 0, looking at it, the average appears to be over 62 MH/s
What I must believe the 5min. average or what I see on the screen?
Could the average 5 min. with kernel 0 be wrong?

& why just after starting miner it tell me the 5 min. average when I have been only mining for 1 min. or even less?

Thank you.

Over time the higher the average the more shares you find. You can also use "-dcri" to optimise your hashing rate. In PH 3.0 this will be automatically tuned for best param like in the Claymore - a promised feature of the PH developer. For now do it manually. It might increase your hash even further and bring more stable hash rate on default kernel.

High hash rate fluctuation (several MH/s) is an indication of overclocked setup. The card is attempting to compute at the maximum speed but at times it throttles down due to the increased temperature or other factors internally managed by the GPU bios. There are quite few things you can do to address this. Rig cooling - add external fans, reduce core/mem clocks, manage ambient and rig (gpu) temperature ...

When you start the miner the average is calculated with the available data. In the first few minutes that is less than 5 minutes of data regardless of the listed "(5 min)".

[starmax]

Decided to try this out on 1 GTX 1070ti today.  ETH-only mining with Claymore was giving me a consistent 34.2 Mh/s, Phoenix is reporting 34.6 Mh/s so I'm going to let it run for a day or 2 and compare shares, but this looks like a winner to me.  Thank you!!

[drgrog]

Uh ..

Eth: Accepted shares 49778 (276 stales), rejected shares 3 (0 stales)
Eth: Incorrect shares 4 (0.01%), est. stales percentage 0.55% 
Eth: Maximum difficulty of found share: 33297.4 TH (!!!)

Max share difficulty of 33000?  So 10x the network difficulty of 3200 TH?
There is a very very very slim chance that rig found a block, but 33297 seems more like a software calculation error :/

[pinamalina]

Decided to try this out on 1 GTX 1070ti today.  ETH-only mining with Claymore was giving me a consistent 34.2 Mh/s, Phoenix is reporting 34.6 Mh/s so I'm going to let it run for a day or 2 and compare shares, but this looks like a winner to me.  Thank you!!

When making a final judgement make sure that you account for all the contributing factors such as luck, long enough testing period...

Stats from some of my rigs (all 13 GPU rigs 8GB, both RX580 and nvidia 1070 8GB):
Rig 2: Eth speed: 404.844 MH/s, shares: 41520/1/3, time: 115:23, shares per min: 5,895215107
Rig 4: Eth speed: 407.562 MH/s, shares: 120660/1/49, time: 337:48, shares per min: 5,953226761
Rig 1: Eth speed: 409.197 MH/s, shares: 98235/0/31, time: 274:26, shares per min: 5,965929795
Rig 3: Eth speed: 411.097 MH/s, shares: 122320/2/17, time: 337:44, shares per min: 6,036320568
...
The running time is several days for each of the above rigs.
The higher the hash rate the higher the number of shares per minute. As it should be.
But this only become right after several days of running time. For the first few days it was almost random...

[matmator]

hashrate with gtx 1070 ?

[Stihlus]

hashrate with gtx 1070 ?

Hi,
From the beginning .. sorry for my bad English

I have:
Asus Z-270A
Gigabyte 1070 G1 Gaming (Micron ...but wasn't my choice)
Nvidia Inspector for OC

TDP: 60% - 65% (more stable with 65%)
Core Clock:-200
Memory Clock: +800
Fan: 60%

For lower Memory Clock (~750) you will still have 32-33 Mh/s.

With 7 x 1070:
Claymore 11.6: ~226+ Mh/S
Phoenix Miner 2.9e: ~231-232+ Mh/s
I'm waiting for other coins/algo to be added...and dual mining I hope in the future

Regards,
Radu

[matmator]

With 7 x 1070:
Claymore 11.6: ~226+ Mh/S



seriousely ?

[pinamalina]

hashrate with gtx 1070 ?

These are my stable settings:
Driver: 391.01
Using MSI Afterburner set as:
  Core Voltage (%): 0
  Power Limit (%): 55
  Temp Limit (%): 83 (linked with Power Limit)
  Core Clock (MHz): -200
  Memory Clock (MHz): 635

Note: The power limit is set in cmd (as admin) using next commands:

Code:

cd C:\Program Files\NVIDIA Corporation\NVSMI
nvidia-smi --id=0 --power-limit=100
nvidia-smi --id=1 --power-limit=105
nvidia-smi --id=2 --power-limit=100
...

A draw can be checked by:

Code:

C:\Program Files\NVIDIA Corporation\NVSMI>nvidia-smi --query | find "Power Draw" | find /v "1911" | find /v "N/A"
        Power Draw                  : 100.11 W
        Power Draw                  : 104.22 W
        Power Draw                  : 99.06 W
        Power Draw                  : 99.08 W

I figured when reducing the power limit further down it would had an effect on hash rate (reduced). Found a min limit point at witch the hash was maximised at given settings manually by trial.
Note that the settings above only work stable for me when the power limit was reduced. With the power limit at 100% the settings were note stable at all.

Stats from PhoenixMiner:
GPU1: GeForce GTX 1070 (pcie 1), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU2: GeForce GTX 1070 (pcie 2), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU3: GeForce GTX 1070 (pcie 6), CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU4: GeForce GTX 1070 (pcie , CUDA cap. 6.1, 8 GB VRAM, 15 CUs
GPU1: 54C 27%, GPU2: 57C 34%, GPU3: 52C 25%, GPU4: 53C 26%
GPUs: 1: 31.755 MH/s (3367) 2: 31.774 MH/s (3365) 3: 31.733 MH/s (3267) 4: 31.754 MH/s (3395/3)

Did push memory freq. further but it did not run stable for long.

[Stihlus]

With 7 x 1070:
Claymore 11.6: ~226+ Mh/S



seriousely ?

I don't lie ... this picture it's from my brother rig's, he still mine ETH on Nanopool with both rig's (AMD and Nvidia).
People say that Nvidia it's not for eth but...with 60% TDP you have ~ 100W / GPU and 33Mh/s.
Me I'm with LUX for the moment...
https://preview.ibb.co/hxbWEH/Capture.png

212 - from 7 RX580 XFX / Asus Z270-A
196.5 - from 6 x 1070 G1 Gaming / Asus Z-270A / TDP 60% Core Clock 0 and Memory Clock +800 (MSI Afterburner).

I'm not sure about nvidia driver, I'm the one who take care that 2 rig's, he is not so good on computers.
Today just changed the driver with the oldest one ... 391.35 (on my rig's).

If you want it's something HERE about Nvidia driver.

Regards,
Radu

[lesjokolat]

Hi just tried new amd driver 18.4.1. I get error errors on vega 64;

windows 10 pro

2018.04.30:19:12:24.575: GPU1 build: Failed to GPU1 program: clBuildProgram (-11)
2018.04.30:19:12:24.575: GPU1 GPU1: Failed to load kernels: clCreateKernel (-46)

tried using
-clKernel 0 and 1 no luck.

[deksite]

Hello Admin

-stales <n> not working in new version.

Reported Hashrate 0

[sergioheadache]

hello,

i have to say, i like this miner very much, but have 1 problem.

i have rig with 12 x rx580 cards,

i set parameter -minfan 90  , but it doesnt work, fans still work as default

any advice ?

thanks

Try with -fanmin 90 -fanmax 95 and see if it does anything, but it should resolve the issue. Watch out for the syntax!

thanks! that did it! now i put all 5 home rigs on phoenixMiner!
good job developers!

[sergioheadache]

hi,

there is one more problem,
for pausing a single gpu, i press 1..9, but what if i have more then 10 gpus, and i need to pause #12 ?

thanks

[UnclWish]

hi,

there is one more problem,
for pausing a single gpu, i press 1..9, but what if i have more then 10 gpus, and i need to pause #12 ?

thanks

Shift + #. For 12 GPU you need to press Shift+2.

[j2james]

Hi PM developers. I have caught 719 error again two times

2018.04.30:18:28:55.438: main *** 67:17 ***************************************************
2018.04.30:18:28:55.438: main Eth: Mining ETH on eth-eu1.nanopool.org:9999 for 67:17
2018.04.30:18:28:55.438: main Eth speed: 192.436 MH/s, shares: 4483/0/0, time: 67:17
2018.04.30:18:28:55.438: main GPUs: 1: 32.080 MH/s (759) 2: 32.077 MH/s (728) 3: 32.071 MH/s (742) 4: 32.076 MH/s (742) 5: 32.071 MH/s (772) 6: 32.061 MH/s (740)
2018.04.30:18:28:55.438: main Eth: Accepted shares 4483 (0 stales), rejected shares 0 (0 stales)
2018.04.30:18:28:55.438: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.04.30:18:28:55.438: main Eth: Maximum difficulty of found share: 437.9 TH (!!!)
2018.04.30:18:28:55.438: main Eth: Average speed (5 min): 192.436 MH/s
2018.04.30:18:28:55.438: main Eth: Effective speed: 185.05 MH/s; at pool: 185.05 MH/s
2018.04.30:18:28:55.438: main 
2018.04.30:18:29:00.508: main Eth speed: 192.436 MH/s, shares: 4483/0/0, time: 67:17
2018.04.30:18:29:00.508: main GPUs: 1: 32.080 MH/s (759) 2: 32.078 MH/s (728) 3: 32.070 MH/s (742) 4: 32.076 MH/s (742) 5: 32.071 MH/s (772) 6: 32.061 MH/s (740)
2018.04.30:18:29:02.221: GPU3 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:18:29:02.255: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:18:29:02.262: GPU3 GPU3 search error: unspecified launch failure
2018.04.30:18:29:02.262: GPU2 GPU2 search error: unspecified launch failure
2018.04.30:18:29:02.271: GPU6 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:18:29:02.271: GPU6 GPU6 search error: unspecified launch failure
2018.04.30:18:29:02.319: GPU1 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:18:29:02.319: GPU1 GPU1 search error: unspecified launch failure
2018.04.30:18:29:02.319: GPU5 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:18:29:02.319: GPU5 GPU5 search error: unspecified launch failure
2018.04.30:18:29:02.326: GPU4 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:18:29:02.326: GPU4 GPU4 search error: unspecified launch failure
2018.04.30:18:29:02.832: wdog Thread(s) not responding. Restarting.
2018.04.30:18:29:03.566: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.30:18:29:03.639: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x883fa91730edc42848c2f91f1a5945dc86876f0ee669a2484b39733c2662cd06","0xee63422e92cf28183646f59a751579cce4e676242da40ec068bf1c3a940099b9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.30:18:29:05.656: main Eth speed: 192.435 MH/s, shares: 4483/0/0, time: 67:17
2018.04.30:18:29:05.656: main GPUs: 1: 32.081 MH/s (759) 2: 32.078 MH/s (728) 3: 32.069 MH/s (742) 4: 32.076 MH/s (742) 5: 32.071 MH/s (772) 6: 32.061 MH/s (740)

2018.04.30:23:54:18.043: main *** 5:24 ***************************************************
2018.04.30:23:54:18.043: main Eth: Mining ETH on eth-eu1.nanopool.org:9999 for 5:24
2018.04.30:23:54:18.043: main Eth speed: 192.454 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:18.043: main GPUs: 1: 32.077 MH/s (55) 2: 32.079 MH/s (65) 3: 32.077 MH/s (55) 4: 32.079 MH/s (60) 5: 32.075 MH/s (46) 6: 32.069 MH/s (63)
2018.04.30:23:54:18.043: main Eth: Accepted shares 344 (0 stales), rejected shares 0 (0 stales)
2018.04.30:23:54:18.043: main Eth: Incorrect shares 0 (0.00%), est. stales percentage 0.00%
2018.04.30:23:54:18.043: main Eth: Maximum difficulty of found share: 338.2 TH (!!!)
2018.04.30:23:54:18.043: main Eth: Average speed (5 min): 192.450 MH/s
2018.04.30:23:54:18.043: main Eth: Effective speed: 176.88 MH/s; at pool: 176.88 MH/s
2018.04.30:23:54:18.043: main 
2018.04.30:23:54:18.823: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.30:23:54:18.823: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xb788eab","0xdc186dc6449f3ed8555c0ee3383c94cfb7efe302fed5427f9733ac049b2035cd"]}

2018.04.30:23:54:18.873: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x983050918378fb6f287be2d4985c47405b9cef936795b53105fca0ae77b70e91","0xee63422e92cf28183646f59a751579cce4e676242da40ec068bf1c3a940099b9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.30:23:54:23.113: main Eth speed: 192.454 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:23.113: main GPUs: 1: 32.077 MH/s (55) 2: 32.078 MH/s (65) 3: 32.077 MH/s (55) 4: 32.079 MH/s (60) 5: 32.075 MH/s (46) 6: 32.068 MH/s (63)
2018.04.30:23:54:23.519: main GPU1: 46C 47%, GPU2: 47C 48%, GPU3: 46C 48%, GPU4: 44C 47%, GPU5: 51C 51%, GPU6: 44C 47%
2018.04.30:23:54:26.085: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x1fb12e5947b11e66a63fbcf2ead58235be455f6c1a40ba3ffca0c5fb55045028","0xee63422e92cf28183646f59a751579cce4e676242da40ec068bf1c3a940099b9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.30:23:54:26.085: eths Eth: New job #1fb12e59 from eth-eu1.nanopool.org:9999; diff: 10000MH
2018.04.30:23:54:28.183: main Eth speed: 192.453 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:28.183: main GPUs: 1: 32.077 MH/s (55) 2: 32.078 MH/s (65) 3: 32.078 MH/s (55) 4: 32.078 MH/s (60) 5: 32.075 MH/s (46) 6: 32.067 MH/s (63)
2018.04.30:23:54:28.838: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.30:23:54:28.887: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x1fb12e5947b11e66a63fbcf2ead58235be455f6c1a40ba3ffca0c5fb55045028","0xee63422e92cf28183646f59a751579cce4e676242da40ec068bf1c3a940099b9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.30:23:54:33.253: main Eth speed: 192.455 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:33.253: main GPUs: 1: 32.076 MH/s (55) 2: 32.078 MH/s (65) 3: 32.078 MH/s (55) 4: 32.079 MH/s (60) 5: 32.075 MH/s (46) 6: 32.069 MH/s (63)
2018.04.30:23:54:38.323: main Eth speed: 192.453 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:38.323: main GPUs: 1: 32.076 MH/s (55) 2: 32.078 MH/s (65) 3: 32.077 MH/s (55) 4: 32.078 MH/s (60) 5: 32.075 MH/s (46) 6: 32.069 MH/s (63)
2018.04.30:23:54:38.853: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.30:23:54:38.853: eths Eth: Send: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0xb788e1f","0xdc186dc6449f3ed8555c0ee3383c94cfb7efe302fed5427f9733ac049b2035cd"]}

2018.04.30:23:54:38.902: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x1fb12e5947b11e66a63fbcf2ead58235be455f6c1a40ba3ffca0c5fb55045028","0xee63422e92cf28183646f59a751579cce4e676242da40ec068bf1c3a940099b9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.30:23:54:43.393: main Eth speed: 192.453 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:43.393: main GPUs: 1: 32.077 MH/s (55) 2: 32.078 MH/s (65) 3: 32.077 MH/s (55) 4: 32.078 MH/s (60) 5: 32.075 MH/s (46) 6: 32.068 MH/s (63)
2018.04.30:23:54:48.463: main Eth speed: 192.452 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:48.463: main GPUs: 1: 32.077 MH/s (55) 2: 32.078 MH/s (65) 3: 32.077 MH/s (55) 4: 32.078 MH/s (60) 5: 32.074 MH/s (46) 6: 32.068 MH/s (63)
2018.04.30:23:54:48.868: eths Eth: Send: {"id":5,"jsonrpc":"2.0","method":"eth_getWork","params":[]}

2018.04.30:23:54:48.918: eths Eth: Received: {"jsonrpc":"2.0","id":0,"result":["0x1fb12e5947b11e66a63fbcf2ead58235be455f6c1a40ba3ffca0c5fb55045028","0xee63422e92cf28183646f59a751579cce4e676242da40ec068bf1c3a940099b9","0x000000006df37f675ef6eadf5ab9a2072d44268d97df837e6748956e5c6c2116"]}
2018.04.30:23:54:51.610: GPU3 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:23:54:51.614: GPU4 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:23:54:51.629: GPU1 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:23:54:51.645: GPU5 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:23:54:51.653: GPU4 GPU4 search error: unspecified launch failure
2018.04.30:23:54:51.653: GPU5 GPU5 search error: unspecified launch failure
2018.04.30:23:54:51.653: GPU3 GPU3 search error: unspecified launch failure
2018.04.30:23:54:51.653: GPU1 GPU1 search error: unspecified launch failure
2018.04.30:23:54:51.676: GPU2 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:23:54:51.676: GPU2 GPU2 search error: unspecified launch failure
2018.04.30:23:54:51.692: GPU6 CUDA error in CudaProgram.cu:264 : unspecified launch failure (719)
2018.04.30:23:54:51.692: GPU6 GPU6 search error: unspecified launch failure
2018.04.30:23:54:51.912: main GPU1: 45C 47%, GPU2: 47C 48%, GPU3: 45C 48%, GPU4: 43C 46%, GPU5: 51C 51%, GPU6: 44C 47%
2018.04.30:23:54:52.316: wdog Thread(s) not responding. Restarting.
2018.04.30:23:54:53.533: main Eth speed: 192.452 MH/s, shares: 344/0/0, time: 5:24
2018.04.30:23:54:53.533: main GPUs: 1: 32.077 MH/s (55) 2: 32.078 MH/s (65) 3: 32.077 MH/s (55) 4: 32.079 MH/s (60) 5: 32.074 MH/s (46) 6: 32.068 MH/s (63)

I use PM 2.9e with the following params

set miner_params=-nvidia -cdm 2 -cdmport 3333 -cdmpass 123 -minRigSpeed 188 -rmode 2 -tstop 65 -tstart 40 -logsmaxsize 0

Rig configuration in my footer.

[DireWolfM14]

hashrate with gtx 1070 ?

These are my stable settings:
Driver: 391.01
Using MSI Afterburner set as:
  Core Voltage (%): 0
  Power Limit (%): 55
  Temp Limit (%): 83 (linked with Power Limit)
  Core Clock (MHz): -200
  Memory Clock (MHz): 635

Is your core clock set to negative 200 mhz?  I'm getting similar hash rates with my MSI GTX 1070s, (just two for the time being.)  Here are my afterburner settings:

Core Voltage: 0%
Power: 65%
Temp: 67 degrees Centigrade (linked with power)
Core Clock: +99
Mem Clock: +650