[ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows)

[d0n4ald]

v.0.5.8 pool zen.suprnova.com
periodically i get such message in log
#  connection closed by server r:0
#  reconnecting
#  connected to: zen.suprnova.cc:3618
#  server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
#  connection closed by server r:0
#  reconnecting
#  connected to: zen.suprnova.cc:3618
share counter drops to 0
gpus getting cold for some minutes, then the process starts again until next reconnect.
is this a bad thing? never got share zero-drop with ewbf.

I have this exact same issue, every 3hrs my rigs get disconnected and reconnect for 5min before they start mining again. Internet is not the problem btw and the rigs dont have anti-virus or firewalls up.

the same issue, I get disconnected every 5 minutes with eu-ru01.miningrigrentals.com
but without disconnections to zec-eu1.nanopool.org
it is a pity, can't use with so many disconnections
Can it be an issue with low capacity of RAM? I have only 2gb Ram on my PC. Lan network.

I have the same problem on v0.5.8. Miner works for a day, and suddenly goes "zm.exe is not responding". At this point I must manually restart the Miner. This never happend to me on v0.5.7.

I've noticed that when too many recons happen then my mining client crashes. right now ive been mining 18hrs with only one reconnection and the rigs are running flawlessly. It's obviously an issue with maintaining a connection to the mining pool. Hopefully that gets sorted out soon enough. I've had this issue on 0.5.7 and 0.5.8 so rolling back to the previous version makes no difference. Right now I'll work on integrating this free open source watchdog script (https://bitcointalk.org/index.php?topic=2071108.0) that will reboot the mining client on crash and reboot my rigs on regular intervals just to manage the issue until the pool and client are working well together again.

im getting teh "zm.exe is not responding" error too, wonder if its my 1080ti settings of 150+ core too high?

[1714168436]

1714168436

[1714168436]

1714168436

[1714168436]

1714168436

[jpl]

Yep.. leave it at 140 to 145

[Deathman20]

v.0.5.8 pool zen.suprnova.com
periodically i get such message in log
#  connection closed by server r:0
#  reconnecting
#  connected to: zen.suprnova.cc:3618
#  server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
#  connection closed by server r:0
#  reconnecting
#  connected to: zen.suprnova.cc:3618
share counter drops to 0
gpus getting cold for some minutes, then the process starts again until next reconnect.
is this a bad thing? never got share zero-drop with 6x.

I have this exact same issue, every 3hrs my rigs get disconnected and reconnect for 5min before they start mining again. Internet is not the problem btw and the rigs dont have anti-virus or firewalls up.

the same issue, I get disconnected every 5 minutes with eu-ru01.miningrigrentals.com
but without disconnections to zec-eu1.nanopool.org
it is a pity, can't use with so many disconnections
Can it be an issue with low capacity of RAM? I have only 2gb Ram on my PC. Lan network.

I have the same problem on v0.5.8. Miner works for a day, and suddenly goes "zm.exe is not responding". At this point I must manually restart the Miner. This never happend to me on v0.5.7.

I've noticed that when too many recons happen then my mining client crashes. right now ive been mining 18hrs with only one reconnection and the rigs are running flawlessly. It's obviously an issue with maintaining a connection to the mining pool. Hopefully that gets sorted out soon enough. I've had this issue on 0.5.7 and 0.5.8 so rolling back to the previous version makes no difference. Right now I'll work on integrating this free open source watchdog script (https://bitcointalk.org/index.php?topic=2071108.0) that will reboot the mining client on crash and reboot my rigs on regular intervals just to manage the issue until the pool and client are working well together again.

im getting teh "zm.exe is not responding" error too, wonder if its my 1080ti settings of 150+ core too high?

I just switched to the dstm client and having zero issues with my 1080ti.  Actually Its OCed more and clocked higher than I have ever been before!  
Before using a different miner (EWBF) I managed around 700 H/sec with just a +100 on the core.  No benefit to clocking the memory or anything else higher.  Now I can run +200 Core / +500 Mem and even run at 90% TDP and get 752 H/sec!  If I run at 100% TDP I get around 770 H/sec at these settings.  I have yet to test it further but I'm sure I could tweak it even more.  So I'd say with this at v0.5.8 you can mine at higher speeds and better output.

[Canosgmk]

anyone having issues with good sol rates, but poor submitted shares? 

>  GPU0  55C  Sol/s: 500.0  Sol/W: 2.85  Avg: 464.7  I/s: 262.1  Sh: 1.33   1.00 469
>  GPU1  54C  Sol/s: 495.7  Sol/W: 2.95  Avg: 462.0  I/s: 259.6  Sh: 1.33   1.00 469 +
>  GPU2  57C  Sol/s: 489.2  Sol/W: 2.88  Avg: 466.1  I/s: 264.8  Sh: 0.67   1.00 469
>  GPU3  55C  Sol/s: 493.3  Sol/W: 2.89  Avg: 467.4  I/s: 263.9  Sh: 2.00   1.00 463 +
   ========== Sol/s: 1978.3 Sol/W: 2.89  Avg: 1860.2 I/s: 1050.4 Sh: 5.32   1.00 467
   GPU0  54C  Sol/s: 492.7  Sol/W: 2.87  Avg: 467.5  I/s: 263.5  Sh: 1.20   1.00 469
   GPU1  53C  Sol/s: 492.2  Sol/W: 2.96  Avg: 465.0  I/s: 259.7  Sh: 1.49   1.00 470 +
   GPU2  56C  Sol/s: 493.6  Sol/W: 2.91  Avg: 468.8  I/s: 265.0  Sh: 0.90   1.00 588 +
   GPU3  54C  Sol/s: 511.1  Sol/W: 2.92  Avg: 471.8  I/s: 264.0  Sh: 2.10   1.00 468 +
   ========== Sol/s: 1989.6 Sol/W: 2.92  Avg: 1873.2 I/s: 1052.1 Sh: 5.69   1.00 498
   GPU0  53C  Sol/s: 489.1  Sol/W: 2.89  Avg: 469.5  I/s: 258.5  Sh: 1.36   1.00 465 +
   GPU1  52C  Sol/s: 485.6  Sol/W: 2.97  Avg: 466.9  I/s: 259.7  Sh: 1.36   1.00 470
   GPU2  55C  Sol/s: 497.2  Sol/W: 2.92  Avg: 471.4  I/s: 265.0  Sh: 0.82   1.00 588
   GPU3  54C  Sol/s: 492.3  Sol/W: 2.93  Avg: 473.7  I/s: 264.1  Sh: 1.91   1.00 468
   ========== Sol/s: 1964.1 Sol/W: 2.93  Avg: 1881.4 I/s: 1047.2 Sh: 5.44   1.00 497
>  GPU0  53C  Sol/s: 473.2  Sol/W: 2.90  Avg: 469.8  I/s: 255.9  Sh: 1.25   1.00 465
>  GPU1  52C  Sol/s: 492.0  Sol/W: 2.98  Avg: 469.0  I/s: 259.8  Sh: 1.25   1.00 470
>  GPU2  55C  Sol/s: 495.1  Sol/W: 2.94  Avg: 473.4  I/s: 264.9  Sh: 0.75   1.00 588
>  GPU3  54C  Sol/s: 491.7  Sol/W: 2.94  Avg: 475.2  I/s: 264.2  Sh: 1.75   1.00 468


four Asus Strix GTX 1070 8GB OC (300, 1000).  Linux Ubuntu 16.04. 

Hahah 300/1000 hahah... try 0/0, "see the Light"...

Please explain.  You are saying to run the GPU stock speed because I need to see the light? 

The OC script I have run is very stable.  Mine ETH on Claymore for a month non-stop with a little lower speeds (claymore crashed anything above 100/1000). 

If needed, I can post my OC script if you think i'm BS'ing...

[Andrey09]

Hi Dstm, any performance improvements are planned in next release ?

[dstm]

Sorry for the newbie question, which might be already answered - dstm is for zcash, or all mineable coins with equihash algo, i mean can dstm be used for zclassic, or zencash for example? Thanks in advance.

Yes, zm can be used to mine zclassic / zencash.

[dstm]

v.0.5.8 pool zen.suprnova.com
periodically i get such message in log
#  connection closed by server r:0
#  reconnecting
#  connected to: zen.suprnova.cc:3618
#  server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
#  connection closed by server r:0
#  reconnecting
#  connected to: zen.suprnova.cc:3618
share counter drops to 0
gpus getting cold for some minutes, then the process starts again until next reconnect.
is this a bad thing? never got share zero-drop with ewbf.

Something on the network or the pool server-closed the connection, zm handles this by retrying till the pool-server is reachable again.

[dstm]

Will DSTM be adding additional algos?

I'm have currently no plans to add additional solvers.

[dstm]

Pool failover still on the books for the next release?

Yes, ofc. 0.6 should be ready in 1-2 weeks.

[dstm]

how to mine with ZM using only xyz GPU card?

If u have 5 GUPS and only want to use GPU 1-3

what is the syntax / command for this , please?

https://en.wikipedia.org/wiki/RTFM

[dstm]

Dear dstm,

When you write in your Change log:
"con: add support for protocol v.01000020"

What does the "con" mean ?
Do you use any other mysterious abbreviations ?

Also what protocol  v01000020 are you referring to?

It tags network related changes.

[dstm]

v.0.5.8 pool zen.suprnova.com
periodically i get such message in log
#  connection closed by server r:0
#  reconnecting
#  connected to: zen.suprnova.cc:3618
#  server set difficulty to: 000f0f0f0f0f0f0f0f0f0f0f...
#  connection closed by server r:0
#  reconnecting
#  connected to: zen.suprnova.cc:3618
share counter drops to 0
gpus getting cold for some minutes, then the process starts again until next reconnect.
is this a bad thing? never got share zero-drop with ewbf.

I have this exact same issue, every 3hrs my rigs get disconnected and reconnect for 5min before they start mining again. Internet is not the problem btw and the rigs dont have anti-virus or firewalls up.

the same issue, I get disconnected every 5 minutes with eu-ru01.miningrigrentals.com
but without disconnections to zec-eu1.nanopool.org
it is a pity, can't use with so many disconnections
Can it be an issue with low capacity of RAM? I have only 2gb Ram on my PC. Lan network.

I have the same problem on v0.5.8. Miner works for a day, and suddenly goes "zm.exe is not responding". At this point I must manually restart the Miner. This never happend to me on v0.5.7.

I've noticed that when too many recons happen then my mining client crashes. right now ive been mining 18hrs with only one reconnection and the rigs are running flawlessly. It's obviously an issue with maintaining a connection to the mining pool. Hopefully that gets sorted out soon enough. I've had this issue on 0.5.7 and 0.5.8 so rolling back to the previous version makes no difference. Right now I'll work on integrating this free open source watchdog script (https://bitcointalk.org/index.php?topic=2071108.0) that will reboot the mining client on crash and reboot my rigs on regular intervals just to manage the issue until the pool and client are working well together again.

It seems like supernova has/had some issues recently - judging by the recent reports.

Concerning the crashes 'on too many recons'. I have a test case for this: something like reconnect every 10sec for couple of hours - it's working fine for me. ZM 'shutdowns' the GPUs if the pool-server isn't reachable to reduce power consumption during this period. It starts all GPUs again after the server is reachable again. So if you have stability issues after reconnections it might be due to bad power supply (since starting GPUs puts some 'pressure' on power supplies) or overclocking.

[dstm]

Hi, dstm! Big thanks for your miner.
I gets a lot of RECV, farm reconnects and keep working, but I think, that shares a lost.
2018-01-08 7:44:12|   ========== Sol/s: 2326.0 Sol/W: 3.46  Avg: 2293.5 I/s: 1249.0 Sh: 7.86   0.99 178
2018-01-08 7:44:15|#  recv failed: 10054
2018-01-08 7:44:15|#  reconnecting
2018-01-08 7:44:26|#  connected to: eu1-zcash.flypool.org:3333

2018-01-08 0:58:46|nvmlDeviceGetTemperature failed (this is my farm goes to sleep! Fixed)
2018-01-08 7:31:52|>  GPU0  32C  Sol/s: 0.2    Sol/W: 3.45  Avg: 473.8  I/s: 0.1    Sh: 1.82   0.99 78 
2018-01-08 7:31:52|   GPU3  33C  Sol/s: 0.1    Sol/W: 3.29  Avg: 452.8  I/s: 0.0    Sh: 1.47   1.00 78 
2018-01-08 7:31:52|   GPU2  33C  Sol/s: 0.1    Sol/W: 3.39  Avg: 465.2  I/s: 0.1    Sh: 1.40   1.00 109
2018-01-08 7:31:52|>  GPU4  32C  Sol/s: 0.3    Sol/W: 3.87  Avg: 463.6  I/s: 0.2    Sh: 1.97   1.00 553
2018-01-08 7:31:52|   ========== Sol/s: 465.6  Sol/W: 3.48  Avg: 2324.2 I/s: 251.2  Sh: 8.32   1.00 179
2018-01-08 7:31:53|   GPU1  33C  Sol/s: 0.1    Sol/W: 3.39  Avg: 464.9  I/s: 0.1    Sh: 1.64   1.00 78 
2018-01-08 7:32:06|   GPU1  40C  Sol/s: 310.9  Sol/W: 3.38  Avg: 463.6  I/s: 169.5  Sh: 1.63   1.00 78 
2018-01-08 7:32:06|   GPU0  38C  Sol/s: 345.2  Sol/W: 3.45  Avg: 472.8  I/s: 183.6  Sh: 1.80   0.99 78 
2018-01-08 7:32:07|   GPU3  40C  Sol/s: 327.9  Sol/W: 3.29  Avg: 451.8  I/s: 176.5  Sh: 1.46   1.00 78 
2018-01-08 7:32:07|#  recv failed: 10054
2018-01-08 7:32:07|#  reconnecting
2018-01-08 7:32:18|#  connected to: eu1-zcash.flypool.org:3333
2018-01-08 7:32:21|#  server set difficulty to: 0004189374bc6a7ef9db22d0...
I changes overclocking for minimum (tdp 50%), but RECV still my guest.
Sorry for my bad english.

This is not due to overclocking, it's a network issue, are you on wifi?

Nope, recv failed: 10054 is a socket error. Please fix this issues, it seems that your miner is very good on the hashrate but need some fix on network side.

error code 10054:
Connection reset by peer - An existing connection was forcibly closed by the remote host.

So either your local internet connection was down or the pool-servers had some issues.

[mmatesic]

I am using 0.5.8 version with two GPUs and I am randomly getting this error.

See image:
https://ibb.co/e8hcU6

ZM does not crash,because everything is working OK, just this message appears a few times in a day.
Does anyone know the cause?

Thanks.

[Djokili]

Hello Dstm,

Can you add an optional column which shows the power consumption of the GPU that is equal (Sol/s / Sol/W).
Like the EWB miner has command "--pec"


thanks,

[somethingiswrong]

Is there a way to get the device name from API? I can see the device name while accessing the miner with a web browser, but it is not included if I perform a API call.

What API?
What exports this API function?

I'm trying to access the API of the dstm miner and parse the information about hashrates etc.
My question is: is it possible to get the device name of each individual GPU from the dstm API?
As I said, the device name is shown in the web interface of the miner, but when performing a API request I only get the GPU ID and not the name.

[AzzAz]

anyone having issues with good sol rates, but poor submitted shares? 

>  GPU0  55C  Sol/s: 500.0  Sol/W: 2.85  Avg: 464.7  I/s: 262.1  Sh: 1.33   1.00 469
>  GPU1  54C  Sol/s: 495.7  Sol/W: 2.95  Avg: 462.0  I/s: 259.6  Sh: 1.33   1.00 469 +
>  GPU2  57C  Sol/s: 489.2  Sol/W: 2.88  Avg: 466.1  I/s: 264.8  Sh: 0.67   1.00 469
>  GPU3  55C  Sol/s: 493.3  Sol/W: 2.89  Avg: 467.4  I/s: 263.9  Sh: 2.00   1.00 463 +
   ========== Sol/s: 1978.3 Sol/W: 2.89  Avg: 1860.2 I/s: 1050.4 Sh: 5.32   1.00 467
   GPU0  54C  Sol/s: 492.7  Sol/W: 2.87  Avg: 467.5  I/s: 263.5  Sh: 1.20   1.00 469
   GPU1  53C  Sol/s: 492.2  Sol/W: 2.96  Avg: 465.0  I/s: 259.7  Sh: 1.49   1.00 470 +
   GPU2  56C  Sol/s: 493.6  Sol/W: 2.91  Avg: 468.8  I/s: 265.0  Sh: 0.90   1.00 588 +
   GPU3  54C  Sol/s: 511.1  Sol/W: 2.92  Avg: 471.8  I/s: 264.0  Sh: 2.10   1.00 468 +
   ========== Sol/s: 1989.6 Sol/W: 2.92  Avg: 1873.2 I/s: 1052.1 Sh: 5.69   1.00 498
   GPU0  53C  Sol/s: 489.1  Sol/W: 2.89  Avg: 469.5  I/s: 258.5  Sh: 1.36   1.00 465 +
   GPU1  52C  Sol/s: 485.6  Sol/W: 2.97  Avg: 466.9  I/s: 259.7  Sh: 1.36   1.00 470
   GPU2  55C  Sol/s: 497.2  Sol/W: 2.92  Avg: 471.4  I/s: 265.0  Sh: 0.82   1.00 588
   GPU3  54C  Sol/s: 492.3  Sol/W: 2.93  Avg: 473.7  I/s: 264.1  Sh: 1.91   1.00 468
   ========== Sol/s: 1964.1 Sol/W: 2.93  Avg: 1881.4 I/s: 1047.2 Sh: 5.44   1.00 497
>  GPU0  53C  Sol/s: 473.2  Sol/W: 2.90  Avg: 469.8  I/s: 255.9  Sh: 1.25   1.00 465
>  GPU1  52C  Sol/s: 492.0  Sol/W: 2.98  Avg: 469.0  I/s: 259.8  Sh: 1.25   1.00 470
>  GPU2  55C  Sol/s: 495.1  Sol/W: 2.94  Avg: 473.4  I/s: 264.9  Sh: 0.75   1.00 588
>  GPU3  54C  Sol/s: 491.7  Sol/W: 2.94  Avg: 475.2  I/s: 264.2  Sh: 1.75   1.00 468


four Asus Strix GTX 1070 8GB OC (300, 1000).  Linux Ubuntu 16.04. 

Hahah 300/1000 hahah... try 0/0, "see the Light"...

Please explain.  You are saying to run the GPU stock speed because I need to see the light? 

The OC script I have run is very stable.  Mine ETH on Claymore for a month non-stop with a little lower speeds (claymore crashed anything above 100/1000). 

If needed, I can post my OC script if you think i'm BS'ing...

Just try lower clocks. Submitted vs reported will be closer.Equihash algo is a bit heavy on network side. Your network connection is important too, try other server/pool with lower ping/latency...

[Canosgmk]

anyone having issues with good sol rates, but poor submitted shares? 

>  GPU0  55C  Sol/s: 500.0  Sol/W: 2.85  Avg: 464.7  I/s: 262.1  Sh: 1.33   1.00 469
>  GPU1  54C  Sol/s: 495.7  Sol/W: 2.95  Avg: 462.0  I/s: 259.6  Sh: 1.33   1.00 469 +
>  GPU2  57C  Sol/s: 489.2  Sol/W: 2.88  Avg: 466.1  I/s: 264.8  Sh: 0.67   1.00 469
>  GPU3  55C  Sol/s: 493.3  Sol/W: 2.89  Avg: 467.4  I/s: 263.9  Sh: 2.00   1.00 463 +
   ========== Sol/s: 1978.3 Sol/W: 2.89  Avg: 1860.2 I/s: 1050.4 Sh: 5.32   1.00 467
   GPU0  54C  Sol/s: 492.7  Sol/W: 2.87  Avg: 467.5  I/s: 263.5  Sh: 1.20   1.00 469
   GPU1  53C  Sol/s: 492.2  Sol/W: 2.96  Avg: 465.0  I/s: 259.7  Sh: 1.49   1.00 470 +
   GPU2  56C  Sol/s: 493.6  Sol/W: 2.91  Avg: 468.8  I/s: 265.0  Sh: 0.90   1.00 588 +
   GPU3  54C  Sol/s: 511.1  Sol/W: 2.92  Avg: 471.8  I/s: 264.0  Sh: 2.10   1.00 468 +
   ========== Sol/s: 1989.6 Sol/W: 2.92  Avg: 1873.2 I/s: 1052.1 Sh: 5.69   1.00 498
   GPU0  53C  Sol/s: 489.1  Sol/W: 2.89  Avg: 469.5  I/s: 258.5  Sh: 1.36   1.00 465 +
   GPU1  52C  Sol/s: 485.6  Sol/W: 2.97  Avg: 466.9  I/s: 259.7  Sh: 1.36   1.00 470
   GPU2  55C  Sol/s: 497.2  Sol/W: 2.92  Avg: 471.4  I/s: 265.0  Sh: 0.82   1.00 588
   GPU3  54C  Sol/s: 492.3  Sol/W: 2.93  Avg: 473.7  I/s: 264.1  Sh: 1.91   1.00 468
   ========== Sol/s: 1964.1 Sol/W: 2.93  Avg: 1881.4 I/s: 1047.2 Sh: 5.44   1.00 497
>  GPU0  53C  Sol/s: 473.2  Sol/W: 2.90  Avg: 469.8  I/s: 255.9  Sh: 1.25   1.00 465
>  GPU1  52C  Sol/s: 492.0  Sol/W: 2.98  Avg: 469.0  I/s: 259.8  Sh: 1.25   1.00 470
>  GPU2  55C  Sol/s: 495.1  Sol/W: 2.94  Avg: 473.4  I/s: 264.9  Sh: 0.75   1.00 588
>  GPU3  54C  Sol/s: 491.7  Sol/W: 2.94  Avg: 475.2  I/s: 264.2  Sh: 1.75   1.00 468


four Asus Strix GTX 1070 8GB OC (300, 1000).  Linux Ubuntu 16.04. 

Hahah 300/1000 hahah... try 0/0, "see the Light"...

Please explain.  You are saying to run the GPU stock speed because I need to see the light? 

The OC script I have run is very stable.  Mine ETH on Claymore for a month non-stop with a little lower speeds (claymore crashed anything above 100/1000). 

If needed, I can post my OC script if you think i'm BS'ing...

Just try lower clocks. Submitted vs reported will be closer.Equihash algo is a bit heavy on network side. Your network connection is important too, try other server/pool with lower ping/latency...

Roger.  makes sense.  The rig is on a 100mb line for now because the new home i moved in too, cat5e network was installed with phone punch blocks, so we can only have hard lines in two rooms.  There is concert walls everywhere, so WiFi sucks.  this weekend, im rewiring the network box and installed a power switch port.  I have two serves.  100mb and a 500mb, so i'll switch the miner to the 500mb line this weekend too.

I did turn the clock way down (100/500) and got almost the same performance.  I did read on another facebook group that ya, i might lose 3%, but i will not wear out the cards as fast. 

Thanks!!

[roony94]

error code 10054:
Connection reset by peer - An existing connection was forcibly closed by the remote host.

So either your local internet connection was down or the pool-servers had some issues.

So if connection goes down the miner stop? no reconection (so that is what happen)....

[VoskCoin]

for those using 1070's w/ dstm . . what are the best OC/watt settings you've found?


Also if anyone's interested in what 1050 TI's can do on DSTM here's my latest 8 gpu mining rig buld guide

https://youtu.be/574KpZdpaVE



OC settings w/ DSTM miner 5.7