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

[spooky79]

after returning to v5.6 after 3 hours of work, the average profit increased to 0.59 ZEC ... how to explain it?

Which pool are you using? Suprnova ?

I found what on 0.5.7 Suprnova pool significantly increases the difficulty and my share rate (and hashrate) drop on 20 %.

flypool

[1714295029]

1714295029

[1714295029]

1714295029

[1714295029]

1714295029

[1714295029]

1714295029

[krial]

@dstm

It seems to be there is a problem that might be related to the miner code. Sometimes the latency would just jump and the router hang:

Code:

 GPU0  60C  Sol/s: 469.0  Sol/W: 3.15  Avg: 465.0  I/s: 249.3  Sh: 2.49   1.00 10141 +
   GPU1  65C  Sol/s: 466.1  Sol/W: 3.14  Avg: 464.2  I/s: 248.2  Sh: 1.49   0.67 40
   ========== Sol/s: 935.1  Sol/W: 3.15  Avg: 929.1  I/s: 497.6  Sh: 3.99   0.88 5090
   GPU0  61C  Sol/s: 466.0  Sol/W: 3.16  Avg: 465.1  I/s: 249.4  Sh: 2.14   1.00 10141
   GPU1  65C  Sol/s: 464.5  Sol/W: 3.14  Avg: 464.2  I/s: 248.1  Sh: 1.71   0.75 43  +
   ========== Sol/s: 930.6  Sol/W: 3.15  Avg: 929.3  I/s: 497.6  Sh: 3.84   0.90 5092
   GPU0  61C  Sol/s: 463.7  Sol/W: 3.15  Avg: 464.9  I/s: 249.5  Sh: 2.24   1.00 40  +
   GPU1  65C  Sol/s: 457.1  Sol/W: 3.13  Avg: 463.3  I/s: 248.3  Sh: 2.24   0.83 41  ++
   ========== Sol/s: 920.8  Sol/W: 3.14  Avg: 928.3  I/s: 497.8  Sh: 4.48   0.92 40
   GPU0  61C  Sol/s: 455.1  Sol/W: 3.15  Avg: 463.8  I/s: 249.4  Sh: 2.33   1.00 41  +
   GPU1  65C  Sol/s: 458.9  Sol/W: 3.12  Avg: 462.8  I/s: 248.3  Sh: 2.32   0.86 41  +

This happens to me only when using ZMiner (using flypool to mine). It can happen 1-2 times per day and would stop router to work properly - making the whole LAN unusable.

I have called to ISP service and they said during this break, the router would spam their equipment with errors.

I am not 100% sure ZM causes this though. I can only say, that using other miners/scripts/pools doesn't create this kind of problem - only happens while using ZM and flypool.

I was just tooling around looking to see if I was the only one; using 5.6 with luckpool. Disappointing, but nice to know it's not just me.

[PickAxe131]

I just wanted to add that I did a little experiment with drivers with the latest release.
0.5.7 is unstable with NVidia 388.xx drivers. It instant crashes for me and never restarts. I want to add that new games like PUBG did the same.

So I tried older drivers, I found that 384.94 works flawless with 0.5.7 and earlier release + I got increased hashrate compared to 388.xx drivers.
This was tested for my 3 rigs with 1080ti and 1070 on windows 10 with latest updates.

[poby]

I just wanted to add that I did a little experiment with drivers with the latest release.
0.5.7 is unstable with NVidia 388.xx drivers. It instant crashes for me and never restarts. I want to add that new games like PUBG did the same.

So I tried older drivers, I found that 384.94 works flawless with 0.5.7 and earlier release + I got increased hashrate compared to 388.xx drivers.
This was tested for my 3 rigs with 1080ti and 1070 on windows 10 with latest updates.

I'm using the latest 388.xx drivers on windows 10 with a mix of 1070 and 1070ti and it's been running for days without a hitch.

Weird that different people have such different outcomes.

[Blast77]

 

I am getting higher sysloads in ethOS after upgrading to 0.5.7... for 8x GTX 1080 and 8x GTX 1080ti rigs.  Any work being done to fix this?  With 8x 1060 and 8x 1070 the load is a little lower.

[vinjob642]

I switched my 1060x12 miner from ewbf to dstmv0.5.6. My hashrate significantly decrease from 34xx to 2500 sols/s while mining in flypool.Is anyone facing the same issue?

[topteam]

I switched my 1060x12 miner from ewbf to dstmv0.5.6. My hashrate significantly decrease from 34xx to 2500 sols/s while mining in flypool.Is anyone facing the same issue?

try 0.5.7, it's better for flypool

[VimanaRider]

I'm using the lastest version with the latest drivers. After I installed latest drivers my invalid shares increased like 7% with suprnova almost on every coin

[PickAxe131]

I just wanted to add that I did a little experiment with drivers with the latest release.
0.5.7 is unstable with NVidia 388.xx drivers. It instant crashes for me and never restarts. I want to add that new games like PUBG did the same.

So I tried older drivers, I found that 384.94 works flawless with 0.5.7 and earlier release + I got increased hashrate compared to 388.xx drivers.
This was tested for my 3 rigs with 1080ti and 1070 on windows 10 with latest updates.

I'm using the latest 388.xx drivers on windows 10 with a mix of 1070 and 1070ti and it's been running for days without a hitch.

Weird that different people have such different outcomes.

I forgot to mention that my 1080ti are overclocked with +200 mem and core. 1070 are overclocked with +100 mem and core. My post was more directed towards users that overclock and uses DTSM miner.

[poby]

I just wanted to add that I did a little experiment with drivers with the latest release.
0.5.7 is unstable with NVidia 388.xx drivers. It instant crashes for me and never restarts. I want to add that new games like PUBG did the same.

So I tried older drivers, I found that 384.94 works flawless with 0.5.7 and earlier release + I got increased hashrate compared to 388.xx drivers.
This was tested for my 3 rigs with 1080ti and 1070 on windows 10 with latest updates.

I'm using the latest 388.xx drivers on windows 10 with a mix of 1070 and 1070ti and it's been running for days without a hitch.

Weird that different people have such different outcomes.

I forgot to mention that my 1080ti are overclocked with +200 mem and core. 1070 are overclocked with +100 mem and core. My post was more directed towards users that overclock and uses DTSM miner.

My 1070ti's are overclocked with +200 core and +700 mem and my 1070's are overclocked with +120 core and +650 mem.  I am using DSTM 5.7 and have found it slightly better in every way than the excellent 5.6

I run a total of 17 cards. 8 1070ti and 8 1070 in rigs, and one 1070 in a laptop.  All running DSTM 24/7 and so far have not had any crashes or stability issues with DSTM.

[timbereagle]

I am happy with GTX 1060s performance with DSTM but need 2 things;

- GTX 1070 performance would be %2-3 better
-Dev fee of %2 is very high please make it %1.

[Dylmine]

Guys, I need an advice
Are 1080s notably faster than 1070 Tis for zcash with DSTM? I'am building another mining rig which constists mainly of 1070 Tis but I can buy few 1080s for like 3-4% more(compared to 1070Tis). So, what do you think? Should I buy few 1080s or GDDR5X is really bad?

[QuintLeo]

1080 ti is a lot faster than 1070 ti in ZEC mining.

 BUT

 At the total system level, depending on card prices, the 1080 ti will usually be a bit worse on a hash/$ basis and a HAIR worse on a hash/watt basis unless you can get one on a VERY good sale compared to a "same model" 1070 ti card
 On the POSITIVE side though, it's *close* on both, and the rig density is a lot better for the 1080 ti.
 Both choices are good ones, which one is "optimal" depends on what you're specifically looking for and YOUR available pricing on the cards.


 Comparing at efficient points for each card (60% of "default TDP" tends to be close to the most efficient point for ANY GTX 1070 / 1070 ti / 1080 / 1080 ti card):

 1070 ti will pull 465 sol/s at 106 watts (using ebwf OR dstm, I didn't see any noticeable improvement for dstm at that setting in my testing) at a Newegg cost $470 for a EVGA SC model (figure more like $520 at total system cost level).
 1080 ti will pull 620 sol/s at 150 watts (using ebwf, I've not tested dstm on a 1080 ti yet) at a Newegg cost of $770 for an EVGA SC model (figure $830 total system cost, you need MORE power supply to run the card other costs will be the same).


 Both cards are capable of much higher hash rates if you push the power draw up, but the hashrate goes up a LOT slower than the power draw once you get past about the 70% TDP level (126 watts for a 1070 ti, 175 for a 1080 ti).


 Note that when I talk about TDP as a percentage, I'm talking specifically about the EVGA SC model of each card, or other cards that have the SAME default TDP (180 and 250 watts respectively) like the Zotac "Mini" models and quite a few others.
 Some 1080 ti models have a higher than 250 watt "default" TDP, and a very few (so far) 1070 ti models have a higher "default TDP" than 180 watts.

 

[marti718]

If anyone is receiving "connection closed by server r:0" every few minutes while using version 5.6, update to version 5.7. The problem has been solved.

[henrynguyen]

Driver for mining 353.33 or lasted

[shibob]

Have anyone tested dstm's miner ver.0.5.7 with GTX 1060 3G? Also, please share your setting?
I could not purchase more P106-100, but there're some MSI GTX 1060 3G are available, so I'm still considering.

Thanks!

[sir_blacks]

Have anyone tested dstm's miner ver.0.5.7 with GTX 1060 3G? Also, please share your setting?
I could not purchase more P106-100, but there're some MSI GTX 1060 3G are available, so I'm still considering.
Thanks!

GPU: Gigabyte Windforce 2 NVIDIA GeForce GTX 1060 3GB (Samsung)
OS: Windows 7 Service Pack 1

Power Limit: 72% (around 82-90W)
Core Clock:  +160
VRam Clock:  680 (vram it can be push to 920-930 depend by algoritm & what miner it i use)
Video Driver: 388.59

Code:

GPU0  60C  Sol/s: 306.9  Sol/W: 3.45 - 3.50  Avg: 297.7  I/s: 159.8  Sh: 2.20

Mining speed it is around ~300 Sol/s with this miner, with other miner it betewen 270-300. Tuning done in MSI Afterburner it depend by each video card & be ware dstm it sems it will not work with same tuning use for exemple in excavator or in EWBF or in Ccminer, same each algo it have diferite requirement

i will add NeoScrypt: around 500-550 depend by what miner it use

hope it will help you but keep in mind value can variate from a brand to other & special what brand are video memory made. 1060 video card are decent for mining with good balance power consumtion > speed. i will add is better to aim for 6g Vram version because they will have a longer future usage see rising dificulty ...

cheers

[anhhoanggl]

if tool error i want restart tool, i will set config  is   --noreconnect  ?

#################################################
#  dstm's ZCash Cuda miner 
#################################################

I've written it initially for my own purpose. It performs pretty well - so here it is.
Compatible with devices having Compute Capability 5.0 and greater i.e. it should run fine on Maxwell/Pascal GPUs.
Supports every server using the stratum protocol. If you have issues with certain pools pls. report them here.
Contains 2% devfee.
Suggestions are welcome.


Performance:
1080Ti 725-740 Sol/s
1070   440-450 Sol/s
stock settings


UI:
Here is a sample output mining on a rig with 7 GPUs.
GPU0: 1080Ti
GPU1 - GPU6: 1070

Code:

>  GPU0 42°C  Sol/s: 739.0  Sol/W: 2.85  Avg: 739.0  I/s: 390.1  Sh: 54.00  1.00  29  ++++++++++++++++++
>  GPU1 44°C  Sol/s: 459.0  Sol/W: 2.91  Avg: 459.0  I/s: 243.5  Sh: 27.00  1.00  29  +++++++++
>  GPU2 46°C  Sol/s: 451.3  Sol/W: 2.77  Avg: 451.3  I/s: 243.5  Sh: 15.00  1.00  28  +++++
>  GPU3 43°C  Sol/s: 449.7  Sol/W: 2.83  Avg: 449.7  I/s: 242.8  Sh: 24.00  1.00  29  ++++++++*
>  GPU4 42°C  Sol/s: 449.0  Sol/W: 2.76  Avg: 449.0  I/s: 243.5  Sh: 36.00  1.00  28  ++++++++++++
   GPU5 43°C  Sol/s: 446.4  Sol/W: 2.79  Avg: 446.4  I/s: 243.6  Sh: 30.00  1.00  28  ++++++++++
   GPU6 42°C  Sol/s: 461.4  Sol/W: 2.84  Avg: 461.4  I/s: 243.8  Sh: 18.00  1.00  28  ++++++
   ========== Sol/s: 3455.8 Sol/W: 2.82  Avg: 3455.8 I/s: 1850.9 Sh: 204.00 1.00  28

Sol/s: solutions per second
Sol/W: efficiency - average Sol/s per Watt (Sol/J)
Avg: average solutions per second
I/s: iterations per second done by the GPU
Sh: <shares per minute> <accepted shares ratio> <network latency in ms>

> : indicates that a new job was received
+ : indicates one submitted share
*  : indicates one submitted devfee-share
= : sum of the stats if mining on multiple GPUs


Features:
To get help just start zm without any arguments

Code:

$ ./zm
ZM 0.5.4, dstm's ZCASH/Equihash Cuda Miner

Usage:
 zm --server hostname --port port_nr --user user_name
    [--pass password] [options]...

 Stratum:
    --server         Stratum server hostname
                     prefix hostname with 'ssl://' for encrypted
                     connections - e.g. ssl://mypool.com
    --port           Stratum server port number
    --user           Username / Workername
    --pass           Worker password

 Options:
    --help           Print this help
    --dev            Space separated list of cuda devices
    --list-devices   List available cuda devices
    --time           Enable output of timestamps
    --logfile        [=path] Append logs to the file named by 'path'
                     If 'path' is not given append to 'zm.log' in
                     current working directory.
    --noreconnect    Disable automatic reconnection on network errors.

    --temp-target    In C - If set, enables temperature controller.
                     The workload of each GPU will be continuously
                     adjusted such that the temperature stays around
                     this value. It is recommended to set your fan speed
                     to 100% when using this setting.

    --telemetry      [=ip:port]. Starts telemetry server. Telemetry data
                     can be accessed using a web browser(http) or by json-rpc.
                     If no arguments are given the server listens on
                     127.0.0.1:2222 - Example: --telemetry=0.0.0.0:2222
                     Valid port range [1025-65535]
 Example:
    zm --server servername.com --port 1234 --user username

BIG THANKS TO SWISSTRADER for providing access to hardware.



Dependencies                                                                                                                  
Linux:
 openssl 1.0

Windows:
 Visual C++ Redistributable for visual studio 2015 (VCRUNTIME140.dll)


Version 0.5.7
reduce cpu load
minor performance improvements
con: use single pool connection
con: ssl: clear session data before reconnect
nvml: handle invalid values

Linux x64:
sha1 e7a38b2771e2b8d976435a6b569053d103bc9465
https://drive.google.com/file/d/11e1fSA2cl14xRL8sMA9BA3AhBGQNn4e4

Win x64:
sha1 808dcfc440beb6af98c84420e1299b211033c8ce
https://drive.google.com/file/d/1WTJylr2uJYy_7-5isuja34ONu0WEBhin


Version 0.5.6
reduce cpu load
minor performance improvements

Linux x64:
sha1 ec26a36c131dcc28aaf747714b55a71ff0167836
https://drive.google.com/file/d/1Ql-hwlI0IsgOGZdOZQe45SfSMdpmgzE_

Win x64:
sha1 b9c818fedd53898cf010f129acefbd7be6fe8812
https://drive.google.com/file/d/1H6u2ZWKaQ4lGcvg2X-cqA0gP966e2-Bk


Version 0.5.5
con: handle failure of dev share pool
con: disable reconnect limit
logfile: disable buffering

Linux x64:
sha1 43e52e9494510f98d28152bf2a2e162b7381c379
https://drive.google.com/file/d/1USpxkXUd0Xs29XizG63OGf9w60UGl4Gf

Win x64:
sha1 4bf1cd44c1bfce6b95e0d6fd26139dcde5d818b2
https://drive.google.com/file/d/1Zmq6ZuOStO-bNjK-4XKacKpe66hk1Qwt


Version 0.5.4
fix: device selection
fix: latency reporting
add logfile support
add option to disable auto reconnect
handle disconnect periods in web/json stats
add basic GPU responsiveness infrastructure
ui: change timestamps to ISO 8601 format
webui: report: uptime contime server user port
json: report: uptime contime server user port version

Linux x64:
sha1 02816754ab46191109bed9f89f17c073000b0950
https://drive.google.com/file/d/12MmjEm-qIpdK7zc22jatQWD9WmAFIOLy

Win x64:
sha1 e4312b348a04348a6229b0098b7862a1306b0145
https://drive.google.com/file/d/1B7d6Qp9WzSPmCC6Yp0BgeyFQ9osdBTqq


Version 0.5.3
cpu: reduce cpu load
con: fix recon loop
con: network latency measurement
ui:  add accepted/rejected shares ratio
ui:  add network latency
ui:  add information about selected devices

Linux x64:
sha1 0583d59930a6160f80db612eae089c84712b5f44
https://drive.google.com/file/d/0B5QcL4Z6nYEPcHRuZk5LV3NXOUE

Win x64:
sha1 d20670a2f41834dfc0828946e187197c1c260992
https://drive.google.com/file/d/0B5QcL4Z6nYEPSm9yTmhDV1gwZ3c


Version 0.5.2
fix a race that might have corrupted shares
net: tcp: disable the Nagle algorithm
  which reduces network latency in some circumstances
net: lower keepalive for nat-networks

Linux x64:
sha1 6d07aee8134dcd122d68b2b35cf10886dccbbfb8
https://drive.google.com/file/d/0B5QcL4Z6nYEPSzRBU1hoQXp3elk

Win x64:
sha1 b57d667e0a4552d2a1a833b33f6aab94a43ecd8e
https://drive.google.com/file/d/0B5QcL4Z6nYEPWVl4bFVhbmhfQjg


Version 0.5.1
con: fix reconnection might have give up too early
con: enable TCP Keepalive to prevent nat-routers from
dropping the connection.
ui: output rejected shares
ui: optional output of timestamps
telemetry: make web ui mobile friendly + add share stats
telemetry: json: add more GPU stats

Linux x64:
sha1 98e52d1357187397f201a5379b4e42919e82c7a8
https://drive.google.com/file/d/0B5QcL4Z6nYEPNTdVUEYtbzA4Yjg


Version 0.5
con: support set_extranonce rpc
con: improve handling of temporary slow network conditions
con: add monitoring support using web browser
con: add monitoring support using json-rpc
mp: rebalance queue sizes - this improves the solution rate as
seen by the pools, especially on pools that submit new jobs often

Linux x64:
sha1 d4debdcf80b2b50c0ed06b55bcaa72262afe41bc
https://drive.google.com/file/d/0B5QcL4Z6nYEPQWgwbVl0Z0xOcGc


Version 0.4.5
fix: bad miner performance when using --temp-target
on systems with many GPUs
reduce temperature controller cpu usage

Linux x64:
sha1 e568c6d4353b35c45d25a00b3d172eda7c11ba11
https://drive.google.com/file/d/0B5QcL4Z6nYEPVGpuTkNCMXo2T2M


Version 0.4.4
fix: Sol/W might have produced wrong values
fix: Sum not shown if --dev was used
fix: memory leak on reconnection
improve stability

Linux x64:
sha1 60e0cad05e93f57330bf8271799d2a5417d904bc
https://drive.google.com/file/d/0B5QcL4Z6nYEPQjdYS2N5R1UyTkU


Version 0.4.3
stratum: support more pools
ui: flush stdout stream
con: improve reconnections
performance improvements 0.3-0.5 %

Linux x64:
sha1 d98792ad93b85f85df66d6e7ab9c2f00aec27cfd
https://drive.google.com/file/d/0B5QcL4Z6nYEPVlBrZmdndHE0VXc


Version 0.4.2
mp: more accurate time measurements
ui: calculate efficiency

Linux x64:
sha1 e53545c72c7a378a637962352b63498693f31f9e
https://drive.google.com/file/d/0B5QcL4Z6nYEPTGh5YUFfYUpGUjA

Version 0.4.1
improve performance

Linux x64:
sha1 4973ab1b90d2c31cc26671c71e71535727cc9e63
https://drive.google.com/file/d/0B5QcL4Z6nYEPaWlTa2VuTklMejQ


Version 0.4.0
temperature controller added
cpu: reduce CPU usage
con: improve pool support
minor performance improvement

Linux x64:
sha1 db0a9bcb7784686f0582d2c3f79be1bbc5be5be5
https://drive.google.com/file/d/0B5QcL4Z6nYEPRk5ITDMwck5jaWs


Version 0.3.2
mp:  improve stability
con: support more pools
con: more robust reconnection support for unreliable
  servers which often drop the connection                                                                                  
ui:  report GPU temperature

Linux x64:
sha1 cc8b83289055bfb659c57937f08f520e928c7fdc
https://drive.google.com/file/d/0B5QcL4Z6nYEPZFpHSzhDR1FSYnM


Version 0.3.1
cpu: reduce CPU usage

Linux x64:
sha1 7077d093b36b1183a80c53abc7b7268e
https://drive.google.com/file/d/0B5QcL4Z6nYEPWVNoS2dfcDdYdEU


Version 0.3
con: support encrypted connections

Linux x64:
sha1  58a36a30ea10d58731c5304a4941744de310be5d
https://drive.google.com/file/d/0B5QcL4Z6nYEPckdSYjF3QlJHN0U


Version 0.2.2
con: Miner reconnects automatically on connection loss now,
 e.g. on DSL-disconnects / public IP-changes
UI: report submitted devfee-shares

Linux x64:
sha1 04551d3f7c9369bccb8cec4bfe404bedee35cf45
https://drive.google.com/file/d/0B5QcL4Z6nYEPQUlVZUJ5LUVNOHM


Version 0.2.1
Performance improvements:                                                                                                      
- about 4% on Maxwell                                                                                                            
- about 1% on Pascal

Linux x64:
sha1 b7ae3a4b1f3567f3855f1b040fc48c253969a6f3
https://drive.google.com/file/d/0B5QcL4Z6nYEPeFVqLWxtNTVvS3M


Version 0.2
- Improved pascal perfromance.                                                                      
- Added support for concurrent mining on multiple GPUs.
- Be asynchronous where possible.
- Security work

Linux x64:
sha1 0ebdcce71fc3ed10f7c70b1d8818f051e2d91613
https://drive.google.com/file/d/0B5QcL4Z6nYEPOVJZd3JrVnR4aEU

[pubix]

I tried new version with my GTX 1060 cards - no hash speed improvements.

[shibob]

GPU: Gigabyte Windforce 2 NVIDIA GeForce GTX 1060 3GB (Samsung)
OS: Windows 7 Service Pack 1

Power Limit: 72% (around 82-90W)
Core Clock:  +160
VRam Clock:  680 (vram it can be push to 920-930 depend by algoritm & what miner it i use)
Video Driver: 388.59

Code:

GPU0  60C  Sol/s: 306.9  Sol/W: 3.45 - 3.50  Avg: 297.7  I/s: 159.8  Sh: 2.20

Mining speed it is around ~300 Sol/s with this miner, with other miner it betewen 270-300. Tuning done in MSI Afterburner it depend by each video card & be ware dstm it sems it will not work with same tuning use for exemple in excavator or in EWBF or in Ccminer, same each algo it have diferite requirement

cheers

Thank you very much!
300 sol/s with just 72% power limit is far from what I expect!
Be cause I've ever tested P106-100 6G for ZEC mining, it got 295sol/s with EWBF, but not this dstm's miner, then I move all P106-100 to mine ETH.
So, I will take a shot next week with MSI GTX 1060 3G, hope it works!