Claymore's ZCash/BTG AMD GPU Miner v12.6 (Windows/Linux)

[Puffy23]

Hey guys, just wondering what your hashrates were for a 1070? I hear they hash at about 100 watts, but I can't seem to get a solid figure on hashrate.

With my RX 480's (on Clay's 9.1 miner), I'm doing about 230 sol/s at 1333/2100 with a decent under-volt.

So I'm thinking of building a new rig, and so I'm wondering if I should go with maybe 2 1070's. My power is already cheap, but at current zcash price, it takes me about 4 months to ROI on an RX 480. So would 1070's ROI faster?

What is your guys' hashrates with a 1070 on Claymore 9.1, and approx what is your power consumption? Thanks so much!

I believe you can get 300 H/s at 100W or 370 at 150W. I can't confirm as I don't own any. Also, Claymore is AMD only.

[1714506493]

1714506493

[1714506493]

1714506493

[1714506493]

1714506493

[1714506493]

1714506493

[BitJunkie556]

I believe you can get 300 H/s at 100W or 370 at 150W. I can't confirm as I don't own any. Also, Claymore is AMD only.

Yeah, that probably sounds more realistic... If that is the case, it would seem the 1070 is only a little more efficient than the RX 480.

RX 480: 100 watt consumption / 230 sols = .43 sol per watt...

GTX 1070: 150 watt consumption / 370 sols = .41 sol per watt...

Now, I guess for someone with a huge power bill, that would make sense for multiple rigs. But on my end... With only about 4 cents per kilowatt hour, I would need to get a 1070 for $350 or less to meet the same ROI as an RX-480. Plus, I only have two rigs.

I guess for multiple rigs, high power cost etc, it makes sense to go with 1070's. Less power consumption, more hashing power on a single rig (less boards, CPU and RAM to buy, etc... Not so much for me though, at least at the moment... Though if I could find a 1070 for $350, I'd buy several in a heartbeat considering all those factors...

[yun9999]

Claymore,

what is causing this issue?  I'm seeing this problem on multiple rigs with V9 and V9.1

19:20:52:148   13fc   srv: remove pck 4
19:20:52:148   13fc   srv bs: 4
19:20:52:148   13fc   srv buf: \r\n
19:20:52:148   13fc   sent: 151
19:20:55:149   c5c   Cannot get Overdrive capabilities for adapter 0
19:20:55:149   c5c   Cannot get Overdrive capabilities for adapter 6
19:20:55:149   c5c   Cannot get Overdrive capabilities for adapter 12
19:20:55:321   c5c   Cannot get Overdrive capabilities for adapter 18
19:20:55:321   c5c   Cannot get Overdrive capabilities for adapter 24
19:20:55:321   c5c   Cannot get Overdrive capabilities for adapter 0
19:20:55:321   c5c   Cannot get Overdrive capabilities for adapter 6
19:20:57:866   1568   recv: 54
19:20:57:867   1568   srv pck: 50
19:21:05:139   c5c   Cannot get Overdrive capabilities for adapter 12
19:21:05:156   c5c   Cannot get Overdrive capabilities for adapter 18
19:21:05:324   c5c   Cannot get Overdrive capabilities for adapter 24
19:21:05:325   c5c   em hbt: 15, fm hbt: 93,
19:21:05:326   c5c   watchdog - thread 0, hb time 103218
19:21:05:372   c5c   WATCHDOG: GPU 0 hangs in OpenCL call, exit
19:21:05:374   c5c   watchdog - thread 1, hb time 103281
19:21:05:481   c5c   WATCHDOG: GPU 0 hangs in OpenCL call, exit
19:21:05:482   c5c   watchdog - thread 2, hb time 103078
19:21:05:588   c5c   WATCHDOG: GPU 0 hangs in OpenCL call, exit
19:21:05:589   c5c   watchdog - thread 3, hb time 103156
19:21:05:710   c5c   WATCHDOG: GPU 0 hangs in OpenCL call, exit
19:21:05:711   c5c   watchdog - thread 4, hb time 103843
19:21:05:747   c5c   WATCHDOG: GPU 1 hangs in OpenCL call, exit
19:21:05:749   c5c   watchdog - thread 5, hb time 104093
19:21:05:805   c5c   WATCHDOG: GPU 1 hangs in OpenCL call, exit
19:21:05:807   c5c   watchdog - thread 6, hb time 104031
19:21:05:861   c5c   WATCHDOG: GPU 1 hangs in OpenCL call, exit
19:21:05:887   c5c   watchdog - thread 7, hb time 103328
19:21:05:924   c5c   WATCHDOG: GPU 1 hangs in OpenCL call, exit
19:21:05:925   c5c   watchdog - thread 8, hb time 104171
19:21:05:957   c5c   WATCHDOG: GPU 2 hangs in OpenCL call, exit
19:21:05:958   c5c   watchdog - thread 9, hb time 104062
19:21:05:993   c5c   WATCHDOG: GPU 2 hangs in OpenCL call, exit
19:21:05:994   c5c   watchdog - thread 10, hb time 104218
19:21:06:034   c5c   WATCHDOG: GPU 2 hangs in OpenCL call, exit
19:21:06:035   c5c   watchdog - thread 11, hb time 104109
19:21:06:072   c5c   WATCHDOG: GPU 2 hangs in OpenCL call, exit
19:21:06:073   c5c   watchdog - thread 12, hb time 103125
19:21:06:111   c5c   WATCHDOG: GPU 3 hangs in OpenCL call, exit
19:21:06:113   c5c   watchdog - thread 13, hb time 102578
19:21:06:151   c5c   WATCHDOG: GPU 3 hangs in OpenCL call, exit
19:21:06:164   c5c   watchdog - thread 14, hb time 102687
19:21:06:224   c5c   WATCHDOG: GPU 3 hangs in OpenCL call, exit
19:21:06:226   c5c   watchdog - thread 15, hb time 102468
19:21:06:288   c5c   WATCHDOG: GPU 3 hangs in OpenCL call, exit
19:21:06:289   c5c   watchdog - thread 16, hb time 103328
19:21:06:348   c5c   WATCHDOG: GPU 4 hangs in OpenCL call, exit
19:21:06:349   c5c   watchdog - thread 17, hb time 104078
19:21:06:386   c5c   WATCHDOG: GPU 4 hangs in OpenCL call, exit
19:21:06:387   c5c   watchdog - thread 18, hb time 104031
19:21:06:428   c5c   WATCHDOG: GPU 4 hangs in OpenCL call, exit
19:21:06:429   c5c   watchdog - thread 19, hb time 103843
19:21:06:444   c5c   WATCHDOG: GPU 4 hangs in OpenCL call, exit
19:21:06:496   1568   Cannot get Overdrive capabilities for adapter 0
19:21:06:500   1568   Cannot get Overdrive capabilities for adapter 6
19:21:06:505   1568   Cannot get Overdrive capabilities for adapter 12
19:21:06:510   1568   Cannot get Overdrive capabilities for adapter 18
19:21:06:514   1568   Cannot get Overdrive capabilities for adapter 24
19:21:06:516   1568   srv: remove pck 4
19:21:06:517   1568   srv bs: 4
19:21:06:518   1568   srv buf: \r\n
19:21:06:519   1568   sent: 151
19:21:06:572   c5c   Cannot get Overdrive capabilities for adapter 0
19:21:08:491   c5c   Cannot get Overdrive capabilities for adapter 6
19:21:08:491   c5c   Cannot get Overdrive capabilities for adapter 12
19:21:08:507   c5c   Cannot get Overdrive capabilities for adapter 18
19:21:08:507   c5c   Cannot get Overdrive capabilities for adapter 24
19:21:09:539   c5c   Restarting OK, exit...

[rpg]

Alert: doing an audit at dwarf shares to find they were not being counted. Set mport to zero and restarted the miner. Now the count is right on. Either my mport was hacked claymore has a overnight job or dwarf is ignoring shares. Any idea?

[Xardas2014]

can any one tell me what does this red text means?

i think it means if the miner has not been active for a full hour or more and is an estimate

i may be wrong tho....

http://dwarfpool.com/faq/#hashrate

[QuintLeo]

i have a very old HD7790 cards

ZEC: GPU0 85.628 H/s, GPU1 85.425 H/s

 Pretty much in line with my pair of single-card  HD7870 rigs - 1024 cores instead of 896, 105 sol/s appx with v8 (haven't gotten v9.1 to work but seems to be a "not enough system ram" issue with v9.x on the systems they're in, and v9 just does not work on ANYTHING I've tried it on to date).

 HD 7750s at 512 cores but only 800/1125 clocks manage 45ish sol/s with v8

[QuintLeo]

EWBF miner 300 h/s 1080 61 C.... total power 73 %

So what...? With the price a 1080 cost I could get 3-4 rx470 so 600 to 800 sols/s  

1070 can do 300 sol with 100watt, or 370 sol with 150watt, that is better than any amd out there, i'm still laughing thinking that there are poeple that believe amd is better...

AMD is better in terms of $/hash, that's all they have right now until Vega comes out. I don't consider nVidia to be a better option, just too expensive for nothing. They will be easier to resell, though.

 I like my 1070s, but I didn't buy them to mine with because they aren't a good choice on a $/hash basis for pretty much any profitable cryptocoin (the ONE exception isn't anywhere near as profitable as the current basket of ETH/ZEC/ETC).

 I just mine with them 'cause RIGHT NOW they're more profitable to do that with then what I bought them FOR.

[beIbox]

Something wrong with dwarfpool
0 workers, 0 hashrate
https://i.imgur.com/z6toNFy.png

[e46btc]

This happens sometimes, but usually all shares counted and it will be recalculated later.  At least no isses with recalc for this year on Dwarf (ETH).

[ol92]

EWBF miner 300 h/s 1080 61 C.... total power 73 %

So what...? With the price a 1080 cost I could get 3-4 rx470 so 600 to 800 sols/s  

1070 can do 310 sol with 100watt, or 370 sol with 150watt, that is better than any amd out there, i'm still laughing thinking that there are poeple that believe amd is better...

1080 is doing 350 with oc with 150w, amd fury x is doing the same with undervolting without oc at around the same wattage.
1080 refurbished can be bought at around 550 euros, fury x around 350 euros.
Both are good. But the fury x was mining at better speed since a few weeks...

[rpg]

This happens sometimes, but usually all shares counted and it will be recalculated later.  At least no isses with recalc for this year on Dwarf (ETH).

I hope you're right. Sent email to support and no reply yet.

[oldisoft]

Added more samples to OP for encrypted connection:

miningpoolhub SSL/TLS connection (this pool detects encryption automatically so it uses same port as for unencrypted connection):
   ZecMiner64.exe -zpool ssl://us-east.equihash-hub.miningpoolhub.com:20570 -zwal YourLogin.YourWorkerName -zpsw YourWorkerPassword

 coinmine SSL/TLS connection:
   ZecMiner64.exe -zpool ssl://zec.coinmine.pl:7017 -zwal YourLogin.YourWorkerName -zpsw YourWorkerPassword

On this topic. What pool do people see the most consistent earning with? Seems flypool has ran on 'bad luck' (if you believe that) for weeks now. Getting sort of tired of it.

I think that zec.nanopool.org absolutely not bad and it is working properly

[ffthomas]

Claymore,

what is causing this issue?  I'm seeing this problem on multiple rigs with V9 and V9.1

19:20:52:148   13fc   srv: remove pck 4
19:20:52:148   13fc   srv bs: 4
19:20:52:148   13fc   srv buf: \r\n
19:20:52:148   13fc   sent: 151
19:20:55:149   c5c   Cannot get Overdrive capabilities for adapter 0
19:20:55:149   c5c   Cannot get Overdrive capabilities for adapter 6
19:20:55:149   c5c   Cannot get Overdrive capabilities for adapter 12
19:20:55:321   c5c   Cannot get Overdrive capabilities for adapter 18
19:20:55:321   c5c   Cannot get Overdrive capabilities for adapter 24
19:20:55:321   c5c   Cannot get Overdrive capabilities for adapter 0
19:20:55:321   c5c   Cannot get Overdrive capabilities for adapter 6
19:20:57:866   1568   recv: 54
19:20:57:867   1568   srv pck: 50
19:21:05:139   c5c   Cannot get Overdrive capabilities for adapter 12
19:21:05:156   c5c   Cannot get Overdrive capabilities for adapter 18
19:21:05:324   c5c   Cannot get Overdrive capabilities for adapter 24
19:21:05:325   c5c   em hbt: 15, fm hbt: 93,
19:21:05:326   c5c   watchdog - thread 0, hb time 103218
19:21:05:372   c5c   WATCHDOG: GPU 0 hangs in OpenCL call, exit
19:21:05:374   c5c   watchdog - thread 1, hb time 103281
19:21:05:481   c5c   WATCHDOG: GPU 0 hangs in OpenCL call, exit
19:21:05:482   c5c   watchdog - thread 2, hb time 103078
19:21:05:588   c5c   WATCHDOG: GPU 0 hangs in OpenCL call, exit
19:21:05:589   c5c   watchdog - thread 3, hb time 103156
19:21:05:710   c5c   WATCHDOG: GPU 0 hangs in OpenCL call, exit
19:21:05:711   c5c   watchdog - thread 4, hb time 103843
19:21:05:747   c5c   WATCHDOG: GPU 1 hangs in OpenCL call, exit
19:21:05:749   c5c   watchdog - thread 5, hb time 104093
19:21:05:805   c5c   WATCHDOG: GPU 1 hangs in OpenCL call, exit
19:21:05:807   c5c   watchdog - thread 6, hb time 104031
19:21:05:861   c5c   WATCHDOG: GPU 1 hangs in OpenCL call, exit
19:21:05:887   c5c   watchdog - thread 7, hb time 103328
19:21:05:924   c5c   WATCHDOG: GPU 1 hangs in OpenCL call, exit
19:21:05:925   c5c   watchdog - thread 8, hb time 104171
19:21:05:957   c5c   WATCHDOG: GPU 2 hangs in OpenCL call, exit
19:21:05:958   c5c   watchdog - thread 9, hb time 104062
19:21:05:993   c5c   WATCHDOG: GPU 2 hangs in OpenCL call, exit
19:21:05:994   c5c   watchdog - thread 10, hb time 104218
19:21:06:034   c5c   WATCHDOG: GPU 2 hangs in OpenCL call, exit
19:21:06:035   c5c   watchdog - thread 11, hb time 104109
19:21:06:072   c5c   WATCHDOG: GPU 2 hangs in OpenCL call, exit
19:21:06:073   c5c   watchdog - thread 12, hb time 103125
19:21:06:111   c5c   WATCHDOG: GPU 3 hangs in OpenCL call, exit
19:21:06:113   c5c   watchdog - thread 13, hb time 102578
19:21:06:151   c5c   WATCHDOG: GPU 3 hangs in OpenCL call, exit
19:21:06:164   c5c   watchdog - thread 14, hb time 102687
19:21:06:224   c5c   WATCHDOG: GPU 3 hangs in OpenCL call, exit
19:21:06:226   c5c   watchdog - thread 15, hb time 102468
19:21:06:288   c5c   WATCHDOG: GPU 3 hangs in OpenCL call, exit
19:21:06:289   c5c   watchdog - thread 16, hb time 103328
19:21:06:348   c5c   WATCHDOG: GPU 4 hangs in OpenCL call, exit
19:21:06:349   c5c   watchdog - thread 17, hb time 104078
19:21:06:386   c5c   WATCHDOG: GPU 4 hangs in OpenCL call, exit
19:21:06:387   c5c   watchdog - thread 18, hb time 104031
19:21:06:428   c5c   WATCHDOG: GPU 4 hangs in OpenCL call, exit
19:21:06:429   c5c   watchdog - thread 19, hb time 103843
19:21:06:444   c5c   WATCHDOG: GPU 4 hangs in OpenCL call, exit
19:21:06:496   1568   Cannot get Overdrive capabilities for adapter 0
19:21:06:500   1568   Cannot get Overdrive capabilities for adapter 6
19:21:06:505   1568   Cannot get Overdrive capabilities for adapter 12
19:21:06:510   1568   Cannot get Overdrive capabilities for adapter 18
19:21:06:514   1568   Cannot get Overdrive capabilities for adapter 24
19:21:06:516   1568   srv: remove pck 4
19:21:06:517   1568   srv bs: 4
19:21:06:518   1568   srv buf: \r\n
19:21:06:519   1568   sent: 151
19:21:06:572   c5c   Cannot get Overdrive capabilities for adapter 0
19:21:08:491   c5c   Cannot get Overdrive capabilities for adapter 6
19:21:08:491   c5c   Cannot get Overdrive capabilities for adapter 12
19:21:08:507   c5c   Cannot get Overdrive capabilities for adapter 18
19:21:08:507   c5c   Cannot get Overdrive capabilities for adapter 24
19:21:09:539   c5c   Restarting OK, exit...

Try to connect a display or a dummy plug to one of the PCI-E cards.

It seems to me that you use for primary graphics the onboard gpu and the miner (or ATI driver) can't control the fan speed, target temperature, etc. A display or a dummy plug will solve this problem. You need to connect the plug for only a few seconds.

Maybe that cause the crash too.

[xeridea]

Claymore,

what is causing this issue?  I'm seeing this problem on multiple rigs with V9 and V9.1

19:20:52:148   13fc   srv: remove pck 4
19:20:52:148   13fc   srv bs: 4
19:20:52:148   13fc   srv buf: \r\n
19:20:52:148   13fc   sent: 151
19:20:55:149   c5c   Cannot get Overdrive capabilities for adapter 0
19:20:55:149   c5c   Cannot get Overdrive capabilities for adapter 6
19:20:55:149   c5c   Cannot get Overdrive capabilities for adapter 12
19:20:55:321   c5c   Cannot get Overdrive capabilities for adapter 18
19:20:55:321   c5c   Cannot get Overdrive capabilities for adapter 24
19:20:55:321   c5c   Cannot get Overdrive capabilities for adapter 0
19:20:55:321   c5c   Cannot get Overdrive capabilities for adapter 6
19:20:57:866   1568   recv: 54
19:20:57:867   1568   srv pck: 50
19:21:05:139   c5c   Cannot get Overdrive capabilities for adapter 12
19:21:05:156   c5c   Cannot get Overdrive capabilities for adapter 18
19:21:05:324   c5c   Cannot get Overdrive capabilities for adapter 24
19:21:05:325   c5c   em hbt: 15, fm hbt: 93,
19:21:05:326   c5c   watchdog - thread 0, hb time 103218
19:21:05:372   c5c   WATCHDOG: GPU 0 hangs in OpenCL call, exit
19:21:05:374   c5c   watchdog - thread 1, hb time 103281
19:21:05:481   c5c   WATCHDOG: GPU 0 hangs in OpenCL call, exit
19:21:05:482   c5c   watchdog - thread 2, hb time 103078
19:21:05:588   c5c   WATCHDOG: GPU 0 hangs in OpenCL call, exit
19:21:05:589   c5c   watchdog - thread 3, hb time 103156
19:21:05:710   c5c   WATCHDOG: GPU 0 hangs in OpenCL call, exit
19:21:05:711   c5c   watchdog - thread 4, hb time 103843
19:21:05:747   c5c   WATCHDOG: GPU 1 hangs in OpenCL call, exit
19:21:05:749   c5c   watchdog - thread 5, hb time 104093
19:21:05:805   c5c   WATCHDOG: GPU 1 hangs in OpenCL call, exit
19:21:05:807   c5c   watchdog - thread 6, hb time 104031
19:21:05:861   c5c   WATCHDOG: GPU 1 hangs in OpenCL call, exit
19:21:05:887   c5c   watchdog - thread 7, hb time 103328
19:21:05:924   c5c   WATCHDOG: GPU 1 hangs in OpenCL call, exit
19:21:05:925   c5c   watchdog - thread 8, hb time 104171
19:21:05:957   c5c   WATCHDOG: GPU 2 hangs in OpenCL call, exit
19:21:05:958   c5c   watchdog - thread 9, hb time 104062
19:21:05:993   c5c   WATCHDOG: GPU 2 hangs in OpenCL call, exit
19:21:05:994   c5c   watchdog - thread 10, hb time 104218
19:21:06:034   c5c   WATCHDOG: GPU 2 hangs in OpenCL call, exit
19:21:06:035   c5c   watchdog - thread 11, hb time 104109
19:21:06:072   c5c   WATCHDOG: GPU 2 hangs in OpenCL call, exit
19:21:06:073   c5c   watchdog - thread 12, hb time 103125
19:21:06:111   c5c   WATCHDOG: GPU 3 hangs in OpenCL call, exit
19:21:06:113   c5c   watchdog - thread 13, hb time 102578
19:21:06:151   c5c   WATCHDOG: GPU 3 hangs in OpenCL call, exit
19:21:06:164   c5c   watchdog - thread 14, hb time 102687
19:21:06:224   c5c   WATCHDOG: GPU 3 hangs in OpenCL call, exit
19:21:06:226   c5c   watchdog - thread 15, hb time 102468
19:21:06:288   c5c   WATCHDOG: GPU 3 hangs in OpenCL call, exit
19:21:06:289   c5c   watchdog - thread 16, hb time 103328
19:21:06:348   c5c   WATCHDOG: GPU 4 hangs in OpenCL call, exit
19:21:06:349   c5c   watchdog - thread 17, hb time 104078
19:21:06:386   c5c   WATCHDOG: GPU 4 hangs in OpenCL call, exit
19:21:06:387   c5c   watchdog - thread 18, hb time 104031
19:21:06:428   c5c   WATCHDOG: GPU 4 hangs in OpenCL call, exit
19:21:06:429   c5c   watchdog - thread 19, hb time 103843
19:21:06:444   c5c   WATCHDOG: GPU 4 hangs in OpenCL call, exit
19:21:06:496   1568   Cannot get Overdrive capabilities for adapter 0
19:21:06:500   1568   Cannot get Overdrive capabilities for adapter 6
19:21:06:505   1568   Cannot get Overdrive capabilities for adapter 12
19:21:06:510   1568   Cannot get Overdrive capabilities for adapter 18
19:21:06:514   1568   Cannot get Overdrive capabilities for adapter 24
19:21:06:516   1568   srv: remove pck 4
19:21:06:517   1568   srv bs: 4
19:21:06:518   1568   srv buf: \r\n
19:21:06:519   1568   sent: 151
19:21:06:572   c5c   Cannot get Overdrive capabilities for adapter 0
19:21:08:491   c5c   Cannot get Overdrive capabilities for adapter 6
19:21:08:491   c5c   Cannot get Overdrive capabilities for adapter 12
19:21:08:507   c5c   Cannot get Overdrive capabilities for adapter 18
19:21:08:507   c5c   Cannot get Overdrive capabilities for adapter 24
19:21:09:539   c5c   Restarting OK, exit...

Try to connect a display or a dummy plug to one of the PCI-E cards.

It seems to me that you use for primary graphics the onboard gpu and the miner (or ATI driver) can't control the fan speed, target temperature, etc. A display or a dummy plug will solve this problem. You need to connect the plug for only a few seconds.

Maybe that cause the crash too.

GPU hang is 100% hardware issue.  Either GPUs too undervolted, too overclocked, or PSU is unstable, or has bad ripple suppression.

As far as dummy plug, this only affects temperature control, and possibly stuck idle clocks, it would not cause a crash. Attempting to mine with onboard graphics will crash, but this shows every card in rig crashing pretty much at same time, indicating a big hardware issue.

[ffthomas]

Claymore,

what is causing this issue?  I'm seeing this problem on multiple rigs with V9 and V9.1

....

Try to connect a display or a dummy plug to one of the PCI-E cards.

It seems to me that you use for primary graphics the onboard gpu and the miner (or ATI driver) can't control the fan speed, target temperature, etc. A display or a dummy plug will solve this problem. You need to connect the plug for only a few seconds.

Maybe that cause the crash too.

GPU hang is 100% hardware issue.  Either GPUs too undervolted, too overclocked, or PSU is unstable, or has bad ripple suppression.

As far as dummy plug, this only affects temperature control, and possibly stuck idle clocks, it would not cause a crash. Attempting to mine with onboard graphics will crash, but this shows every card in rig crashing pretty much at same time, indicating a big hardware issue.

I meant that maybe the cards are overheated and that caused the crash. Anyway it is good to know these values and can control the fans and target temp.

Of course if you use to much overclock and/or undervolt that is the main problem.

[QuintLeo]

V9.1 with my HD7990's i get 201H/S per chip (400-405 in total, MSI brand), really good increase!

That's it? I have a MSI 7950 heavy overclocked doing stable 220-225

 Can't push the 7990s as hard due to twice the heat generation (almost) in the same space.

[QuintLeo]

Hey guys, just wondering what your hashrates were for a 1070? I hear they hash at about 100 watts, but I can't seem to get a solid figure on hashrate.

With my RX 480's (on Clay's 9.1 miner), I'm doing about 230 sol/s at 1333/2100 with a decent under-volt.

So I'm thinking of building a new rig, and so I'm wondering if I should go with maybe 2 1070's. My power is already cheap, but at current zcash price, it takes me about 4 months to ROI on an RX 480. So would 1070's ROI faster?

What is your guys' hashrates with a 1070 on Claymore 9.1, and approx what is your power consumption? Thanks so much!

 Per my limited testing on the new eqm version, I can get my 1070s *which are NOT the good memory type* to about 300 sol/s at 108 watts, no mods Afterburner set to 60% TDP +500 mem clock -200 core clock.

 I suspect someone that played more with settings could better that efficiency some, especially on 1070 models with better memory.

 Optimal settings for me *so far* net a bit over 330 sol/s on 140ish watts, 80% TDP +500 mem stock core clock in Afterburner.

 My pair of RX 470s manage a little over 200 sol/s each on v9.1 (one is at 201 the other 206), which is quite nice for a pair of cards that cost me $332 with shipping (less than ANY f my single 1070s).

[majorlee]

V9.1 with my HD7990's i get 201H/S per chip (400-405 in total, MSI brand), really good increase!

That's it? I have a MSI 7950 heavy overclocked doing stable 220-225

 Can't push the 7990s as hard due to twice the heat generation (almost) in the same space.

yes im on stock bios and settings too, these babies are my winter handwarmers!

used to overclock them years back on other algos and nearly paid the price of melted power PCI-E cables! (not riser)

[Amph]

I believe you can get 300 H/s at 100W or 370 at 150W. I can't confirm as I don't own any. Also, Claymore is AMD only.

Yeah, that probably sounds more realistic... If that is the case, it would seem the 1070 is only a little more efficient than the RX 480.

RX 480: 100 watt consumption / 230 sols = .43 sol per watt...

GTX 1070: 150 watt consumption / 370 sols = .41 sol per watt...

Now, I guess for someone with a huge power bill, that would make sense for multiple rigs. But on my end... With only about 4 cents per kilowatt hour, I would need to get a 1070 for $350 or less to meet the same ROI as an RX-480. Plus, I only have two rigs.

I guess for multiple rigs, high power cost etc, it makes sense to go with 1070's. Less power consumption, more hashing power on a single rig (less boards, CPU and RAM to buy, etc... Not so much for me though, at least at the moment... Though if I could find a 1070 for $350, I'd buy several in a heartbeat considering all those factors...

370 at 150 watt is not the good choice, do 300 sol at 100 watt, that is 0.3 sol per watt, actually i'm not sure about the 150watt with 370 sol, it could be less, my gpu can't reach that speed you need a palit

[c2n14]

Something wrong with dwarfpool
0 workers, 0 hashrate
https://i.imgur.com/z6toNFy.png

Yes, I confirm. I woke up and I saw on the dwarf page that my worker is @ 0 sols....
I checked the miner and I saw that the connection with dwarf's EU server went down from 78ms yesterday to 3000ms now

That's why I have request:

@Claymore

Could you make a new switch that the connection could be change to failover if the lag is over some threshold (like in my case above)?
Thanks.