Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 104. (Read 224961 times)

   GPU0  67C  Sol/s: 503.6  Sol/W: 4.35  Avg: 498.5  I/s: 267.5  Sh: 7.49  1.00 399 ++
   GPU1  65C  Sol/s: 263.0  Sol/W: 2.26  Avg: 266.1  I/s: 142.4  Sh: 7.48  1.00 400 ++++
   ======= Sol/s: 766.6  Sol/W: 3.31  Avg: 764.6  I/s: 409.9  Sh: 14.96 1.00 399
   GPU0  67C  Sol/s: 507.5  Sol/W: 4.35  Avg: 498.6  I/s: 267.6  Sh: 7.49  1.00 396 +++++
   GPU1  66C  Sol/s: 271.3  Sol/W: 2.26  Avg: 266.1  I/s: 142.5  Sh: 7.48  1.00 402 ++
   ======= Sol/s: 778.8  Sol/W: 3.31  Avg: 764.6  I/s: 410.1  Sh: 14.97 1.00 399

Update:
I was able to achieve 490-500+ ~ sol/s on my gtx 1080 using 112 - 117 watts on the card itself with this miner!

core clock ; +180
PL: 58%
Fan 40%

Asus Strix A8G

It seems like there was a misunderstanding. Periodical disconnects which happen often aren't 'normal'. The server or something in between e.g. your router closes the connection. Does this also happen on other servers for you?

ZM has the '--time' option, it enables output of timestamps.

ZM can't ignore a TCP FIN packet - it terminates a TCP connection.

It looks like you're cpu bound - zm has a higher cpu load.

ZM auto reconnects by default - however it has to exit if the server reports an unknown protocol.

I got problem with ZEN same as you.

Dev said what it's normal, said server sent packet which information to close connection, but could ZM ignore this packet? This packet got all card in the same time?  (8 my cards reconnects)

I have been running this miner in ethos for 24 hours.  It reports more sols than ewbf, but it seems to drop from the zen suprnova pool regularly.  I can see miners drop and reappear just staying logged in and watching.  Anyone else see this issue?  I plan to leave this running for more days, but curious if others are seeing this or if this may be normal.  ewbf didn't have this same behaviour on suprnova.

Can you make logfile with only error message? And need date and time for all lines.

I have problem with BTG on SUPRNova Pool time to time i get message error recv failed: 10054 and my contime timer resets, EWBF on same server work without reconnect.

It can happend afteer 5-10 hours of work ZM. Nothing major but may be ZM can ignore packet which make him recconect?  (Same was for ZEN on https://zenmine.pro/)

Nah, i don't think so, i have 2x seasonic 750w platinium, they're super rock solid, mining has been stable for a year with all those no issues at all, and remember it's across 10 rigs of the same configuration, i wouldn't think i have a PSU issue on everyone of them  , i think it's really related on how your miner work, with EWBF i had to set a certain PL and OC, and i just need to change this to please your miner, that's all there is, at least for this brand of card. And for now it seems to work very nicely. So all good

Maybe you could get a UPS and it will solve your issue

Could someone please write clock settings for 1080ti for getting over 750sols? I have asus strix gaming 1080ti.

Hi!

Thank you a lot for your miner, it works flawlessly on my 1070s. However the results are very poor with my 1080s (not Ti version). I am getting maximum 450 sol/s while with EWBF I am getting around 540 at 155W.

Please advise.

Thanks.

Thanks for great miner  
*********************

ZM 0.5.4 in nvOC

13x Asus Strix 1070
The rig is with AsRock H110 PRO BTC+ & Intel Pentim G4400 & 4GB RAM
Pulling 2080W from wall. With 2x 1200W ATX PSU
OS with 16GB class6 microSD card in USB adapter <--- some might say unrealiable but I have them plenty and ready provisioned for swap if fail. Done +2months no fail.

**********************

Fans at 50%

ZEC

   POWERLIMIT_WATTS=140
   
__CORE_OVERCLOCK=80
MEMORY_OVERCLOCK=1000

**********************

   GPU0 57C  Sol/s: 464.9  Sol/W: 3.36  Avg: 468.4  I/s: 250.1  Sh/s: 0.043  +
   GPU1 55C  Sol/s: 470.0  Sol/W: 3.38  Avg: 471.6  I/s: 251.5  Sh/s: 0.014
   GPU2 63C  Sol/s: 462.5  Sol/W: 3.33  Avg: 464.8  I/s: 246.8  Sh/s: 0.000
   GPU3 63C  Sol/s: 468.4  Sol/W: 3.32  Avg: 464.3  I/s: 246.7  Sh/s: 0.029
   GPU4 58C  Sol/s: 457.9  Sol/W: 3.35  Avg: 466.9  I/s: 249.4  Sh/s: 0.014
   GPU5 53C  Sol/s: 460.0  Sol/W: 3.30  Avg: 460.9  I/s: 247.7  Sh/s: 0.014
   GPU6 57C  Sol/s: 463.2  Sol/W: 3.31  Avg: 462.3  I/s: 248.2  Sh/s: 0.014
   GPU7 51C  Sol/s: 469.5  Sol/W: 3.35  Avg: 467.1  I/s: 249.1  Sh/s: 0.057
   GPU8 47C  Sol/s: 474.4  Sol/W: 3.43  Avg: 478.1  I/s: 254.1  Sh/s: 0.014
   GPU9 63C  Sol/s: 465.1  Sol/W: 3.30  Avg: 460.4  I/s: 245.4  Sh/s: 0.014
   GPU10 63C  Sol/s: 451.8  Sol/W: 3.26  Avg: 454.5  I/s: 244.7  Sh/s: 0.071  +
   GPU11 56C  Sol/s: 461.3  Sol/W: 3.34  Avg: 465.7  I/s: 249.0  Sh/s: 0.029  +
   GPU12 53C  Sol/s: 478.5  Sol/W: 3.37  Avg: 470.5  I/s: 251.5  Sh/s: 0.014
   ========= Sol/s: 6047.6 Sol/W: 3.34  Avg: 6055.5 I/s: 3234.3 Sh/s: 0.329

If I drop the powerlimit to 130W I get aroud 3.7 Sol/W ~5800sols with same OC settings, but I like 6000 sol more round number.


**********************

ZM 0.5.4 in nvOC

4x Asus Strix A 1070 TI
  
    POWERLIMIT_WATTS=130
  
__CORE_OVERCLOCK=120
MEMORY_OVERCLOCK=1200


   GPU0 62C  Sol/s: 501.2  Sol/W: 3.92  Avg: 508.6  I/s: 270.8  Sh/s: 0.030
   GPU1 58C  Sol/s: 503.2  Sol/W: 3.95  Avg: 511.4  I/s: 272.8  Sh/s: 0.090  +
   GPU2 56C  Sol/s: 508.3  Sol/W: 3.93  Avg: 509.5  I/s: 272.3  Sh/s: 0.050  +
   GPU3 53C  Sol/s: 505.1  Sol/W: 3.93  Avg: 509.5  I/s: 271.6  Sh/s: 0.040
   ========= Sol/s: 2017.8 Sol/W: 3.93  Avg: 2039.0 I/s: 1087.4 Sh/s: 0.210


The Asus "binned" TI GPU stand more OC and hashes ok with 130W too. Will make 13x TI rig next. Same powerdraw more sols per W. Should be ~6600 sols with 2kw.

Ok thanks, will do.  I've restarted the miner pointing to NiceHash.

Any plan to have "auto reconnect" command line option?

Ty
so far so good with this miner (6 hr running )

ZM didn't crash - it exits if it receives invalid data from the server. It looks like the server submitted an invalid protocol number. It might be something which won't happen again...  so pls report if this happens again.

Right, the '+' denotes one found share.

Right.

No it's not connected to overclocking. This happens if the remote host/server closes the connection - it might also happen if your local network goes down.