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

[chuck732]

Hi,
  So what is the real difference between v0.5.6 vs v0.5.8 ?

[1714079802]

1714079802

[1714079802]

1714079802

[1714079802]

1714079802

[1714079802]

1714079802

[1714079802]

1714079802

[CarlOrff]

Hi,
  So what is the real difference between v0.5.6 vs v0.5.8 ?

Are you serious ?
Read the OP :

Version 0.5.8
con: add support for protocol v.01000020                                                                                      
link openssl statically

@DSTM : when 0.6 version will be ready ? I'm very impatient to improve my hashrate :-)

[Valter84]

Hello dstm,

Thank you for your great work. I have been using your software to mine for a while.
I would like to ask, if it possible to make your software "restart" after a cuda memory fail on a gpu.
I have several rigs running and I am not always checking on them, it`s not nice to see that I had one rig not working for a entire night or day because there was a error.
This happens more in rigs where I have 6 different gpu`s from nvidia, it`s not easy to find the best OC. So if, a error happens, it should be logged and the mining should restart. That way I would check for the logs and know that I should reduce a OC on a gpu but i wouldn`t lost several hours of mining.

Thank you very much and keep the good work.

Sorry about my poor english.

[CarlOrff]

Hello dstm,

Thank you for your great work. I have been using your software to mine for a while.
I would like to ask, if it possible to make your software "restart" after a cuda memory fail on a gpu.
I have several rigs running and I am not always checking on them, it`s not nice to see that I had one rig not working for a entire night or day because there was a error.
This happens more in rigs where I have 6 different gpu`s from nvidia, it`s not easy to find the best OC. So if, a error happens, it should be logged and the mining should restart. That way I would check for the logs and know that I should reduce a OC on a gpu but i wouldn`t lost several hours of mining.

Thank you very much and keep the good work.

Sorry about my poor english.

There is no Cuda errors here, but an overclok issue..
It is not a DSTM miner issue but an overclock issue.
If you want no overclock issue and don't have to lost entire nights or days of mining, you know and have the solution : reduce you or stop your overclok.

[Atronoss]

Hello dstm,

Thank you for your great work. I have been using your software to mine for a while.
I would like to ask, if it possible to make your software "restart" after a cuda memory fail on a gpu.
I have several rigs running and I am not always checking on them, it`s not nice to see that I had one rig not working for a entire night or day because there was a error.
This happens more in rigs where I have 6 different gpu`s from nvidia, it`s not easy to find the best OC. So if, a error happens, it should be logged and the mining should restart. That way I would check for the logs and know that I should reduce a OC on a gpu but i wouldn`t lost several hours of mining.

Thank you very much and keep the good work.

Sorry about my poor english.

You can use this command line script to let it run in loop:

Code:

:mine
timeout 60
cd dstm
zm --server ssl://eu1-zcash.flypool.org --port 3443 --user t1N1eJnRtQuyai6ewvQsaJe3ACWAvHykqhu --time
cd..
echo DSTM MINER RESTARTED AT %TIME% %DATE% >> dstm_log.txt
goto mine

It is for Windows, miner is in folder "dstm" and bat file is one level up.

[chuck732]

What is protocol v.01000020 ? I did an basic search on this forum and found nothing.

Hi,
  So what is the real difference between v0.5.6 vs v0.5.8 ?

Are you serious ?
Read the OP :

Version 0.5.8
con: add support for protocol v.01000020                                                                                      
link openssl statically

@DSTM : when 0.6 version will be ready ? I'm very impatient to improve my hashrate :-)

[michalss]

Found out that your telemetry webserver does not work Can you pls fix it ? Thx

[calculatorduck]

Ok, so it happened again today that there was a disconnect and my AMD rig mining on Claymore recovered, but both my nvidia machines hard crashed DSTM so mining stopped. This is really weird as I had been running DSTM for a couple of months and this behavior only started in the last week or so.

I was previously mining on suprnova, so I switched to nicehash to see if the pool was the issue but no, it still happened.

All I see in the log is below:

Code:

2018-02-10 5:00:18 AM|#  connection closed by server r:0
2018-02-10 5:00:18 AM|#  reconnecting
2018-02-10 5:00:28 AM|#  connected to: equihash.usa.nicehash.com:3357
2018-02-10 5:00:30 AM|stratum subscribe failed

That was the last thing recorded before the crash.

[ZenFr]

Is DSTM 0.5.8. compatible with CUDA 9.0 and CUDA 9.1 ?

If it is, what are the expecting hashrate improvments with these two CUDA news versions compared to CUDA 8.0 version ?
It is for a use with GTX 750, 960, 1050Ti, 1070 and 1080Ti.

Or any benchmark link (not found with a quick search in Google) ?

[wetblanket]

I would also like to know what protocol v.01000020 is?

What is protocol v.01000020 ? I did an basic search on this forum and found nothing.

Version 0.5.8
con: add support for protocol v.01000020                                                                                      
link openssl statically

[WaveRiderx]

quick question, why do GPUs show out of order?  On some rigs they post 0,1,2,3,4,5,6,7 then others they list out for example; 4,5,7,3,2,1,0,6

Not really important just curious.

[calculatorduck]

Ok, so it happened again today that there was a disconnect and my AMD rig mining on Claymore recovered, but both my nvidia machines hard crashed DSTM so mining stopped. This is really weird as I had been running DSTM for a couple of months and this behavior only started in the last week or so.

I was previously mining on suprnova, so I switched to nicehash to see if the pool was the issue but no, it still happened.

All I see in the log is below:

Code:

2018-02-10 5:00:18 AM|#  connection closed by server r:0
2018-02-10 5:00:18 AM|#  reconnecting
2018-02-10 5:00:28 AM|#  connected to: equihash.usa.nicehash.com:3357
2018-02-10 5:00:30 AM|stratum subscribe failed

That was the last thing recorded before the crash.

Just crashed again, this time:

Code:

protocol version 01000030 not supported

right before the crash.

I'm not sure why this is happening all of the sudden as it's been really stable for awhile.

[agismaniax]

Hi dstm, I had problem on my one rig. Your miner has just stopped with error disconnected from server and stop working. It didn't try to reconnect or anything. On this location I've 3 rigs and only this one had this error. Can you please explain what is this error and why your miner didn't reconnect automatically? Thanks
http://i68.tinypic.com/295pmco.jpg

Could you share your 1060 brand, vram and afterburner's setings?

[1gek]

Another newb here.  I'm not able to get anywhere near these sol/s numbers with my 1070.  Same algo, similar oc on core and mem.  My numbers are maxing at ~160 sol/s in the miner window.  I'm running win 10 (performance mode cpu), z270 mobo and msi 1070.  Am I missing an OS setting or something else?

Thanks.

I'm failing on attaching a screen capture here (is it enabled?) but it seems like the initial numbers are what I'd expect e.g. ~475 sol/s for the 1070 (~120)...unfortunately they drop VERY quickly to considerably less.  Any help/pointers on fixing this would be appreciated.

Thanks.

[WaveRiderx]

Another newb here.  I'm not able to get anywhere near these sol/s numbers with my 1070.  Same algo, similar oc on core and mem.  My numbers are maxing at ~160 sol/s in the miner window.  I'm running win 10 (performance mode cpu), z270 mobo and msi 1070.  Am I missing an OS setting or something else?

Thanks.

I'm failing on attaching a screen capture here (is it enabled?) but it seems like the initial numbers are what I'd expect e.g. ~475 sol/s for the 1070 (~120)...unfortunately they drop VERY quickly to considerably less.  Any help/pointers on fixing this would be appreciated.

Thanks.

If it's one GPU on your main rig, then it's sharing it's resources with everything on that computer.  The other thing is it could be overheating or if the power limit is too low.  Either one of those will cause hash to start normal and then decline as both will lower the core frequency.  What are your afterburner settings?  What are the temps?  Are you watching videos or anything else taxing the gpu?  Is the CPU taxed?  How much RAM?

[Smoreno]

Another newb here.  I'm not able to get anywhere near these sol/s numbers with my 1070.  Same algo, similar oc on core and mem.  My numbers are maxing at ~160 sol/s in the miner window.  I'm running win 10 (performance mode cpu), z270 mobo and msi 1070.  Am I missing an OS setting or something else?

Thanks.

I'm failing on attaching a screen capture here (is it enabled?) but it seems like the initial numbers are what I'd expect e.g. ~475 sol/s for the 1070 (~120)...unfortunately they drop VERY quickly to considerably less.  Any help/pointers on fixing this would be appreciated.

Thanks.

Try 1stminingrig.com win 10 tweaks.

[bracinac]

It happen too often with in random rigs:

2018-02-11 10:53:22 AM|# send timeout
2018-02-11 10:53:24 AM|# send timeout
2018-02-11 10:55:40 AM|recv: Connection timed out
2018-02-11 10:55:40 AM|# reconnecting

Rig stops, no restart, no reconnect.

Any solution for this? (SMOS)

And:

2036-02-07 09:32:34 AM|# connected to: eu1-zcash.flypool.org:3333
2036-02-07 09:32:37 AM|SSL_connect failed r:2 error:1416F086:SSL routines:tls_process_server_certificate:certificate verify fail
ed

[gruvalex]

Trying to get some stats from my miner and noticed the JSON-RPC interface is broken.

$ curl http://192.168.1.6:2222 -X POST -D '{"id":1, "method":"getstat"}' -v
* Rebuilt URL to: http://192.168.1.6:2222/
*   Trying 192.168.1.6...
* TCP_NODELAY set
* Connected to 192.168.1.6 (192.168.1.6) port 2222 (#0)
> POST / HTTP/1.1
> Host: 192.168.1.6:2222
> User-Agent: curl/7.57.0
> Accept: */*
>
{"id":1,"result":[{"gpu_id":0,.....cutting some useless stuff here....rsion":"0.5.8","error": null}
* Connection #0 to host 192.168.1.6 left intact

The reply is there, but the reply is not valid HTTP ('HTTP/1.0 200 OK' is missing from reply). Therefore most http-libs and browsers will not be able to use the data.

Can you please add the 'HTTP/1.0 200 OK' line to the json-rpc please?

Thanks for your work on the miner! Appeciate ya!

[chrysophylax]

Interesting miner.

We would be interested in a chat if you are interested in working privately also.

#crysx

[volapyk]

Any way to run DSTM on GPU 0,1 and 2 and disable mining on 3, 4 and 5?