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

[Rhyn0]

I did not fing any setting about handling crashes. Miner does not autorestart at default. So how to handle it.. that is question.

Use this: https://bitcointalk.org/index.php?topic=2071108.0

great script, takes care of absolutely everything for you.

[1714190057]

1714190057

[1714190057]

1714190057

[1714190057]

1714190057

[1714190057]

1714190057

[1714190057]

1714190057

[SatyrA]

I did not fing any setting about handling crashes. Miner does not autorestart at default. So how to handle it.. that is question.

Use this: https://bitcointalk.org/index.php?topic=2071108.0

great script, takes care of absolutely everything for you.

Thanks.

[KpoBb1989]

OS: Windows 10
Mining rig: GTX 1070 TI x5, GTX 1070 x1

Very often the application is crashed with the following errors (copied from log file).
After the crash mining is not working anymore. So it requires to reload the application manually.
Could you take a look at it?

2018-02-28 15:10:34|   GPU1  46C  Sol/s: 529.1  Sol/W: 3.11  Avg: 529.1  I/s: 283.4  Sh: 1.94   0.99 57  ++
2018-02-28 15:10:35|   GPU2  47C  Sol/s: 440.5  Sol/W: 2.91  Avg: 445.4  I/s: 238.7  Sh: 1.60   0.99 47 
2018-02-28 15:10:42|#  connection closed by server r:2
2018-02-28 15:10:42|#  reconnecting
2018-02-28 15:11:02|#  eu1-zcash.flypool.org:3333 not responding
2018-02-28 15:11:12|#  eu1-zcash.flypool.org:3443 not responding
2018-02-28 15:11:22|#  eu1-zcash.flypool.org:3333 not responding
2018-02-28 15:11:32|#  eu1-zcash.flypool.org:3443 not responding
2018-02-28 15:11:42|#  eu1-zcash.flypool.org:3333 not responding
2018-02-28 15:11:52|#  eu1-zcash.flypool.org:3443 not responding
2018-02-28 15:12:02|#  eu1-zcash.flypool.org:3333 not responding
2018-02-28 15:12:12|#  eu1-zcash.flypool.org:3443 not responding
2018-02-28 15:12:22|#  eu1-zcash.flypool.org:3333 not responding
2018-02-28 15:12:32|#  eu1-zcash.flypool.org:3443 not responding
2018-02-28 15:12:32|#  connected to: eu1-zcash.flypool.org:3333 [1/2]
2018-02-28 15:12:35|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:12:38|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:12:41|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:12:43|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:12:45|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:12:49|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:12:51|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:12:53|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:12:56|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:12:58|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:00|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:04|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:06|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:08|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:11|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:13|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:15|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:18|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:20|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:23|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:26|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:28|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:31|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:34|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:36|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:38|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:41|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:43|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:45|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:48|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:51|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:53|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:56|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:58|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number

[dstm]

OS: Windows 10
Mining rig: GTX 1070 TI x5, GTX 1070 x1

Very often the application is crashed with the following errors (copied from log file).
After the crash mining is not working anymore. So it requires to reload the application manually.
Could you take a look at it?

2018-02-28 15:10:34|   GPU1  46C  Sol/s: 529.1  Sol/W: 3.11  Avg: 529.1  I/s: 283.4  Sh: 1.94   0.99 57  ++
2018-02-28 15:10:35|   GPU2  47C  Sol/s: 440.5  Sol/W: 2.91  Avg: 445.4  I/s: 238.7  Sh: 1.60   0.99 47 
2018-02-28 15:10:42|#  connection closed by server r:2
2018-02-28 15:10:42|#  reconnecting
2018-02-28 15:11:02|#  eu1-zcash.flypool.org:3333 not responding
2018-02-28 15:11:12|#  eu1-zcash.flypool.org:3443 not responding
2018-02-28 15:11:22|#  eu1-zcash.flypool.org:3333 not responding
2018-02-28 15:11:32|#  eu1-zcash.flypool.org:3443 not responding
2018-02-28 15:11:42|#  eu1-zcash.flypool.org:3333 not responding
2018-02-28 15:11:52|#  eu1-zcash.flypool.org:3443 not responding
2018-02-28 15:12:02|#  eu1-zcash.flypool.org:3333 not responding
2018-02-28 15:12:12|#  eu1-zcash.flypool.org:3443 not responding
2018-02-28 15:12:22|#  eu1-zcash.flypool.org:3333 not responding
2018-02-28 15:12:32|#  eu1-zcash.flypool.org:3443 not responding
2018-02-28 15:12:32|#  connected to: eu1-zcash.flypool.org:3333 [1/2]
2018-02-28 15:12:35|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:12:38|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:12:41|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:12:43|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:12:45|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:12:49|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:12:51|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:12:53|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:12:56|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:12:58|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:00|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:04|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:06|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:08|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:11|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:13|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:15|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:18|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:20|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:23|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:26|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:28|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:31|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:34|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:36|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:38|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:41|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:43|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:45|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:48|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:51|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2018-02-28 15:13:53|#  connected to: ssl://eu1-zcash.flypool.org:3443 [2/2]
2018-02-28 15:13:56|authorization failed [20,"Work not yet ready!"]
2018-02-28 15:13:58|SSL_connect failed r:1 error:1408F10B:SSL routines:ssl3_get_record:wrong version number

Thx for reporting.
Flypool servers are having issues recently.
However zm should reconnect after they respond properly again.
I'm looking into this.

[silviocorrea]

What I would love to know.... is how to disable a GPU... For whatever reason, this miner just never starts. It keeps saying that "GPU 1" is unresponsive... I'd love to at least TRY this miner on my 1070ti but can't do so if it won't even let me disable a GPU that isn't working with it... and no, I'm not just removing the card... the computer the cards are in is the computer i'm using to type this message.... as in, i use the computer and it just mines when its idle..... or at least would if this worked....

[xpulse]

Version 0.6
- failover pool support

- introduce intensity option

Failover pool support and intensity option does not work from the command line

i.e...

zm.exe --dev 0 1 2 3 4   --server equihash.hk.nicehash.com --user name.worker --pass x --port 3357 --server equihash.in.nicehash.com --user name.worker --pass x --port 3357 --server equihash.jp.nicehash.com --user name.worker --pass x --port 3357 --server equihash.usa.nicehash.com --user name.worker --pass x --port 3357 --server equihash.br.nicehash.com --user name.worker --pass x --port 3357 --server equihash.eu.nicehash.com --user name.worker --pass x --port 3357 --telemetry=127.0.0.1:4004 --color --time --intensity 1

zm.exe: unknown option -- intensity
2018-03-03 15:21:33|#  zm 0.6
2018-03-03 15:21:33|#  GPU0 + GeForce GTX 1060 3GB     MB: 3072  PCI: 1:0
2018-03-03 15:21:33|#  GPU1 + GeForce GTX 1060 3GB     MB: 3072  PCI: 2:0
2018-03-03 15:21:33|#  GPU2 + GeForce GTX 1060 3GB     MB: 3072  PCI: 3:0
2018-03-03 15:21:33|#  GPU3 + GeForce GTX 1060 3GB     MB: 3072  PCI: 5:0
2018-03-03 15:21:33|#  GPU4 + GeForce GTX 1060 3GB     MB: 3072  PCI: 7:0
2018-03-03 15:21:33|
2018-03-03 15:21:33|#  pool1 equihash.eu.nicehash.com:3357
2018-03-03 15:21:33|
2018-03-03 15:21:33|#  color mode not supported
2018-03-03 15:21:33|#  telemetry server listening on 127.0.0.1:4004
2018-03-03 15:21:33|#  connected to: equihash.eu.nicehash.com:3357 [1/1]

Same thing: SMOS

============ Starting Miner ===============
/root/miner/dstm-v0.6.0/zm: unrecognized option '--intensity'

[korenchkin]

xpulse:why do you use intensity 1?its the default,there is no turboboost or rocket fuel,it will not go faster,intensity is used to limit power,not add,why on earth would you limit dedicated computer(like smos)?

[dvince]

I have 6×1080 and 1× 1080 Ti in my mining rig.

I got recognized only 6×1080, the last 1080 Ti doesnt work.
Any ideas how to enable the 7th GPU??

Other miners works with 7 gpus.

[xpulse]

xpulse:why do you use intensity 1?its the default,there is no turboboost or rocket fuel,it will not go faster,intensity is used to limit power,not add,why on earth would you limit dedicated computer(like smos)?

Probably valid question "why", just want to see the difference for new feature, otherwise you will never know all functionality of miner program.

[jpl]

What I would love to know.... is how to disable a GPU... For whatever reason, this miner just never starts. It keeps saying that "GPU 1" is unresponsive... I'd love to at least TRY this miner on my 1070ti but can't do so if it won't even let me disable a GPU that isn't working with it... and no, I'm not just removing the card... the computer the cards are in is the computer i'm using to type this message.... as in, i use the computer and it just mines when its idle..... or at least would if this worked....

In msi Afterburner you can turn off 'synchronize settings for all processors',. then go to that gpu and lower its clock settings. 
..
but.. I just added an msi 1070ti, here,.. and lowered the hell out of it.. and it kept freezing up my computer.   Not sure about those cards

[fittsy]

Use this: https://bitcointalk.org/index.php?topic=2071108.0

great script, takes care of absolutely everything for you.

We need something like this for Linux. Any ideas?

[hwextreme]

Hi guys


I have been using ZEC's EWBF  miner for months now and it works fine, but I have never managed to get DSMT miner to connect to any of the pools that I can use with ZEC EWBF

running it in a cmd window I can see that it is erroring due to "connect failed"  but I know the config is correct as it taken from a working EWBF miner.

I have a hardware firewall and the ports are open for the pools Im mining on and very little else, I have looked to see if DSTM is making a system call to dial home and cannot see any attempt to connect elsewhere and I also cannot sea any blocked packets on the firewall so Im lost as to what address is failing to connect to.

I have tried 0.58 and 0.6 and tried to connect to several pools that work with other miners so it is something DSTM is trying to connect to but fails, does anyone know what IP address or port I need to open, Im guessing this is for it to send the dev fee?

[crypper]

I have been using EWBF for a while and has never crashed on me.  I decided to give DSTM a try and noticed that in the last few days, every few hours (no specific amount of time) it crashes and I get this error:

2018-03-05 11:32:45 AM|   GPU1  56C  Sol/s: 718.8  Sol/W: 3.60  Avg: 718.4  I/s: 384.9  Sh: 1.61   1.00 159 +
2018-03-05 11:32:47 AM|   GPU3  58C  Sol/s: 697.7  Sol/W: 3.52  Avg: 700.7  I/s: 375.2  Sh: 1.62   1.00 156 *
2018-03-05 11:32:47 AM|   GPU4  55C  Sol/s: 714.8  Sol/W: 3.60  Avg: 716.6  I/s: 383.9  Sh: 1.62   1.00 157
2018-03-05 11:32:49 AM|   GPU0  59C  Sol/s: 701.1  Sol/W: 3.56  Avg: 707.6  I/s: 378.9  Sh: 1.59   1.00 140
2018-03-05 11:32:59 AM|>  GPU2  60C  Sol/s: 712.1  Sol/W: 3.59  Avg: 714.0  I/s: 382.1  Sh: 1.65   1.00 157
2018-03-05 11:33:00 AM|#  connection closed by server r:0
2018-03-05 11:33:00 AM|#  reconnecting
2018-03-05 11:33:47 AM|NVML: couldn't find device 0
------<snip>------
2018-03-05 3:52:59 PM|>  GPU0  58C  Sol/s: 704.3  Sol/W: 3.56  Avg: 708.0  I/s: 379.2  Sh: 1.69   1.00 156
2018-03-05 3:53:02 PM|   GPU1  56C  Sol/s: 679.7  Sol/W: 3.50  Avg: 684.2  I/s: 365.2  Sh: 1.63   1.00 157 +
2018-03-05 3:53:04 PM|#  connection closed by server r:0
2018-03-05 3:53:04 PM|#  reconnecting
2018-03-05 3:53:30 PM|NVML: couldn't find device 0

Has anyone else run into this before and if so what's the solution?  TIA

My rig is:
Windows 10
6 x GTX1080Ti

Many people find DSTM not stable (although do expect 3-5 post right after this post claiming that DSTM is rock solid for them and they never had any issues). From my experience the only solution is to lower clocks to the point it is stable, but then you can find that at those lower clocks DSTM becomes less profitable than EWBF, so you will want to get back to EWBF. Moreover since you are running 1080TI DSTM I believe gives no advantage over EWBF in terms of hashrate (may be wrong though).

[Bimmber]

I had lot of stability issues with DSTM, kept crashing my rigs every few hours.

[Atronoss]

Hi guys


I have been using ZEC's EWBF  miner for months now and it works fine, but I have never managed to get DSMT miner to connect to any of the pools that I can use with ZEC EWBF

running it in a cmd window I can see that it is erroring due to "connect failed"  but I know the config is correct as it taken from a working EWBF miner.

I have a hardware firewall and the ports are open for the pools Im mining on and very little else, I have looked to see if DSTM is making a system call to dial home and cannot see any attempt to connect elsewhere and I also cannot sea any blocked packets on the firewall so Im lost as to what address is failing to connect to.

I have tried 0.58 and 0.6 and tried to connect to several pools that work with other miners so it is something DSTM is trying to connect to but fails, does anyone know what IP address or port I need to open, Im guessing this is for it to send the dev fee?

It used to always try to connect to Flypool to mine for a dev, if this failed, the miner didn't work. Few peoples complained, that when Flypool has issues, the miner doesn't work anymore, so maybe he added some more pools, but at least make sure that the Flypool is reachable.

[Andrey09]

Hello DSTM.

Could you please change GPU sorting method ? We need what GPUs are sorted by physical bus index (it matches AfterBurner list of GPUs)

[coinzzzpro]

Thank you!

My GTX 1080 TI LIGHTNING Z:

Code:

GPU0  56C  Sol/s: 802.6  Sol/W: 3.25  Avg: 795.4  I/s: 423.6  Sh: 12.48  1.00 325 +++

[Elange]

On one of my Linux rigs dstm's messes up GPU ordering, like this:

#  zm 0.6
#  GPU0 + GeForce GTX 980          MB: 4038  PCI: 7:0
#  GPU1 + GeForce GTX 970          MB: 4036  PCI: 1:0
#  GPU2 + GeForce GTX 970          MB: 4037  PCI: 2:0
#  GPU3 + GeForce GTX 970          MB: 4037  PCI: 4:0

Whereas nvidia-smi, my bash scripts etc number GPUs according to PCIE numbering (1:0, 2:0, 4:0, 7:0).
This causes a lot of confusion while overclocking and checking temperatures.

Is there a way to fix it? Strangely, this happens only on one of my rigs out of ~ 10.
Drivers are the latest release 390.30.

thanks!

[ruphus]

I have 6×1080 and 1× 1080 Ti in my mining rig.

I got recognized only 6×1080, the last 1080 Ti doesnt work.
Any ideas how to enable the 7th GPU??

Other miners works with 7 gpus.

Try updating your driver. I've read, that older nvidia-drivers didn't support the 1080 ti. Support started somewhere 384 or 387 I guess.

[WaveRiderx]

love the updated color scheme, so much better