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

[dstm]

hi DSTM

please help me.

with reference to two rigs of mine that do over 3000 sols each.  

almost every morning when i wake up i notice no hashrate on pool monitor for these two rigs.  i then check miner and see  -  
connection closed by server   r 0
reconnecting


what do i do ?
i have done much troubleshooting with no luck.


regards



note:  i have other rigs under 3000sols on the same network that dont do this

What OS/zm-version are you on?
I'm getting similar reports recently, not sure why, are you on 0.5.8?

To make sure I'm understanding you right - zm doesn't start to mine and the last message is 'reconnecting' right?
ZM stops the GPUs during connection loss/reconnection periods to save energy, so if your system isn't stable (e.g. overclocked / unstable power supply) it's likely to fail on phases where GPUs are stopped and restarted again - the fact that your other rigs reconnect without issues seems to support this.

[1714519039]

1714519039

[1714519039]

1714519039

[1714519039]

1714519039

[1714519039]

1714519039

[dstm]

do you mean difficulty should be mapped to a smaller range such that it's easier to read? Float is a datatype representing real numbers it's not related to the radix/base that's used for representation.

What I mean is that pools expect difficulty configuration as a number, so even I know where my performance sweet spot is - I cannot just paste it as a hint to the pool.
I am not sure if that is possible, but it would be appreciated.

I see, will add.

- Current log makes little sense without further tools. (I would appreciate more details)

What details are you missing? And how is it related to tools you would not need otherwise?

The idea of logging change is to make it easier to spot problems. The log right now has the information you need, it is just clumped together.
For example I switched to mining pool hub and performance dropped 5-10% - I used python to split the information and found out they are seemingly randomly changing difficulty back to 0001....
I checked the shares and found out the coin switching is not nicely implemented by the pool.
Other card had performance problems due to fan not scaling (For some reason the fan speed was not scaled on temperature in 2D mode).
 - Here might be a good innovation. If you can read PerfCap Reason and accordingly to it would be better rather than temperature.
 - I suspect targeting a temperature will be a good workaround
Now I am trying to find sweet spots for Sol/W, because going as fast as possible is not always the best efficiency.

Yes, it seems reasonable to change the logfile format to something that's event based and easier to parse, thx for pointing this out. It's on my notes now.

Anyway I am looking forward to new versions, but I am sticking with 0.5.7. Performance on 0.5.8 is worse for me CPU wise.

Now that's is a very useful information. If there are any regressions between the versions - pls report them - I can't fix them otherwise and they might appear in later versions too. How much did the cpu load increase for you?

Since you took the time to respond, I took the time to replicate my original problem.
Unfortunately I was not able to. I am now running at 0.5.8

[dstm]

Hello all.

What happens when "contime" reset but uptime continue count?

Contime means time from last disconnect from pool server?

When appeared "error recv failed: 10054 " ? Due overclocking ?

I having exactly the same ZEC mining error "# recv failed: 10054" It disconnect every minute, Don't know what to do. Don't know why? Please help.

There is something wrong with your network. Are you on Wifi? You could also try a different pool.

[dstm]

@ DSTM:
 I noticed that in case network is off ( router restart ) miner goes to loop "retrying"  even after network is back. Can you make it try several ( i.e: 5 or 10 times ) than just restart?

I'm testing this case for every release, zm reconnects properly for me in exactly the same situation (router restart).
In general: issues should be fixed properly - not by workarounds - otherwise you'll end up with tons of workaround-configuration options.
What version are you on? I'll run the test again for it.

[bigfootnz]

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

This looks strange - does this also happen on 0.5.8?

I'm not using 0.5.8, still all my rigs are running 0.5.7. So far this happened only once.

Any idea what can be problem here? Thanks

[1gek]

Hi, i'm a total newby in mining, so i need some reference about performance.

I'm using my workstation an old Precision Dell T7500 Xeon 6Core 24gb 1xPNY-GTX-1070, mining at miningpoolhub. This weekend i'm going to build a rig with 4xGB-GTX1070

This are my rig numbers, working with Equihas-dstm (zm.exe) :

485 sol/s 3.84 sol/w
Are this numbers good enough?

AfterBurner OC settings:

Core + 190(GPU-Z 1830 Avg)
Memory + 775 (GPU-Z 2288 Avg)
PW 84%
Temp. 57ºC

Thanks

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.

[Biggen1]

Just wanted to say keep up the good work dstm. I'm at 30 days uptime with Ubuntu on my 8
GPU rig and it works flawless. Not a single crash in a month. Rig is on autopilot.

[AzzAz]

@ DSTM:
 I noticed that in case network is off ( router restart ) miner goes to loop "retrying"  even after network is back. Can you make it try several ( i.e: 5 or 10 times ) than just restart?

I'm testing this case for every release, zm reconnects properly for me in exactly the same situation (router restart).
In general: issues should be fixed properly - not by workarounds - otherwise you'll end up with tons of workaround-configuration options.
What version are you on? I'll run the test again for it.

5.8. Last Nvidia driver(.77). W10pro64 updated fully. 1070, 1070Ti's,z370mobo/i3 8100... will test again and wait longer ( other rigs connected 10 min before i stopped waiting )

[gigglegrass]

hey, just switched from ewbf miner earlier, but i noticed that for some reason there is no command like -d # or --cuda_devices #, like every other miner has, to designate which gpu i want to mine on. So is there actually no command? or was it just not written in this thread

[nazzer]

hey, just switched from ewbf miner earlier, but i noticed that for some reason there is no command like -d # or --cuda_devices #, like every other miner has, to designate which gpu i want to mine on. So is there actually no command? or was it just not written in this thread

I literally answered this question on the previous page:

Is it possible to use just 1 device with the miner? I have 2 cards but I sometimes like to game with one so being able to shut off the miner from using one at some points would be nice, even if it requires a separate .bat

Yes.

Code:

 Options:
    --help           Print this help
    --dev            Space separated list of cuda devices
    --list-devices   List available cuda devices

How do I use this? I have done "--dev 1" "--dev 980ti" what is the correct variable?

Code:

$ ./zm --list-devices
Device: 0    GeForce GTX 1070         MB: 8119  PCI: 1:0
Device: 1    GeForce GTX 1070         MB: 8119  PCI: 3:0
Device: 2    GeForce GTX 1070         MB: 8119  PCI: 4:0
Device: 3    GeForce GTX 1070         MB: 8119  PCI: 5:0
Device: 4    GeForce GTX 1070         MB: 8119  PCI: 6:0
Device: 5    GeForce GTX 1070         MB: 8119  PCI: 7:0

Devices are numbered as per --list-devices

e.g.

Code:

$ ./zm --dev 0 1 3 5

[CarlOrff]

Hi, i'm a total newby in mining, so i need some reference about performance.

I'm using my workstation an old Precision Dell T7500 Xeon 6Core 24gb 1xPNY-GTX-1070, mining at miningpoolhub. This weekend i'm going to build a rig with 4xGB-GTX1070

This are my rig numbers, working with Equihas-dstm (zm.exe) :

485 sol/s 3.84 sol/w
Are this numbers good enough?

AfterBurner OC settings:

Core + 190(GPU-Z 1830 Avg)
Memory + 775 (GPU-Z 2288 Avg)
PW 84%
Temp. 57ºC

Thanks

Your numbers are not too bad, but you will probably get better with some changes.
With a 1070, you can be around the 4 sol/W
You have probably to decrease your power usage, near 70/75% to catch the 4 sol/W.
You can decrease the memory overcock to 400/350.

[maxlumnar]

mining equihash on 980ti overclocked : 498-512Sol/s
but its so damn hot, i had to improvise auxiliary cooling on top of it (drops temp by 7deg), now at 72c

its been doing this for over a week now, stable, how long till it will burn out?

core +160
mem +0
overvolt +0.037v

anyone any assumptions? Thanks

[DenJohn]

72 is ok-ish. Try to undervolt if you want to lower the temperature.

[Andrey09]

mining equihash on 980ti overclocked : 498-512Sol/s
but its so damn hot, i had to improvise auxiliary cooling on top of it (drops temp by 7deg), now at 72c

its been doing this for over a week now, stable, how long till it will burn out?

core +160
mem +0
overvolt +0.037v

anyone any assumptions? Thanks

How much sol/w. Do you have with 980ti? Try increase memory clock and you will get more sols.

[lamqtaspaska]

From today i got "protocol version 01000030 not supported"

# zm 0.5.8
#  GPU0 + GeForce GTX 1070         MB: 8112  PCI: 2:0
#  GPU1 + GeForce GTX 1070         MB: 8114  PCI: 5:0
#  GPU2 + GeForce GTX 1070         MB: 8114  PCI: 6:0

#  telemetry server started
#  server set difficulty to: 001000000000000000000000...
protocol version 01000030 not supported

[Snow_Dog]

Is there a better way to temporarily stop one card in your rig from mining than running one instance of the miner specifying all cards that you want running all the time and another instance running just the card you sometimes want to stop?  I know in Claymore you can just use the number keys to toggle a specific card.

[Smoreno]

Hi, i'm a total newby in mining, so i need some reference about performance.

I'm using my workstation an old Precision Dell T7500 Xeon 6Core 24gb 1xPNY-GTX-1070, mining at miningpoolhub. This weekend i'm going to build a rig with 4xGB-GTX1070

This are my rig numbers, working with Equihas-dstm (zm.exe) :

485 sol/s 3.84 sol/w
Are this numbers good enough?

AfterBurner OC settings:

Core + 190(GPU-Z 1830 Avg)
Memory + 775 (GPU-Z 2288 Avg)
PW 84%
Temp. 57ºC

Thanks

Your numbers are not too bad, but you will probably get better with some changes.
With a 1070, you can be around the 4 sol/W
You have probably to decrease your power usage, near 70/75% to catch the 4 sol/W.
You can decrease the memory overcock to 400/350.

Thanks, I will reduce the power to 75% and test the results in Precision T7500.
Finally I built 4x 1070 Gigabytes last weekend. My numbers are a little different:
1970 Sol/s (492.5 for GTX1070)
3.30 W/Sol

But Sh(ares) only 2.2-2.5 for the four graphics cards.

I'm happy, but ready to improve the efficiency.

[calculatorduck]

I'm also seeing some sort of failure or disconnection recently on both of my rigs. I've been using this miner for a couple of months now and never had this issue but over the last week it's happened 3 times where the miner just disconnects and closes. I tried running it through Awesomeminer as well and it looks like Awesomeminer will try multiple times to restart it but each time it will fail to connect and then close/crash. If I wait a minute and try again manually it will work as normal. I didn't have logging enabled (but I do now) so I can't say much more than that, but this is the first time this has been happening to me.

When it happens, it happens on both of my nvidia rigs running DSTM. My AMD rig running claymore shows a disconnect, but it recovers. So it's definitely a connection issue with the pool or network connection since claymore shows it too, but DSTM doesn't recover for whatever reason. I've seen DSTM work fine after a pool error or disconnect before though, so I'm not sure what changed.

[cryptowhore]

Hi there,

I'm looking for a nice miner where i can build a nice (Progressive Web) App for. But i don't get this json rpc thingy to work.

To what URL i should post, i added --telemetry 192.168.2.210 and i can view my stats on http://192.168.2.210:2222/ so i know for sure that part is working.

First i want to try getting the data in postman, so i found this simple example:
https://i.imgur.com/XJB4b6V.png

I tried posting:

Code:

{"id":1, "method":"getstat"}

and

Code:

{"jsonrpc": "2.0", "id":1, "method":"getstat"}

To:

Code:

192.168.2.210:2222

and

Code:

192.168.2.210:2222/jsonrpc

But all i get is a 404, any suggestions i should look into. (I do send Content-Type application/json)

Would be great if someone can help me with this, then i can build an app to show you the stats of al rigs on the network and ofcourse will make the app available for everyone.

[kahlid74]

Getting this with a Titan V:

#  zm 0.5.6
#  GPU0 + TITAN V                  MB: 12288 PCI: 1:0

#  GPU0  connected to: eu1-zcash.flypool.org:3333
#  GPU0  server set difficulty to: 0004189374bc6a7ef9db22d0...
gpu_id 0 0 0 invalid argument
gpu 0 unresponsive - check overclocking
cudaMemcpy 1 failed
#  recv failed: 10038
#  reconnecting

Me too.  EWBF works for Titan V but DSTM does not.  bminer does not work either.