Hello!

I used to have a version of zm_0.6_win and this version worked, I stopped my farm for 6 months, after which I moved to another city. When I tried to use zm_0.6_win, I had a problem with SSL, then I downloaded a new version of v0.6.2, and when I started start.bat my farm is freezes.
What to do Help me please!

P.S. Windows 10, Nvidia driver 416.81. Cuda. Visual Studio.

Intensity does not adjust the GPU load
GPU load remains 100% regardless of intensity,
LAtest version, Win8.1, GTX1080

Are you going to relase public 144_5?
What's your speed compared to EWBF?

I have posted this before but I'm having ZERO issues on Linux (Ubuntu Server) with 0.6.1 on a eight GTX1070TI rig.  I don't understand why others are having issues.  I'm seeing the slight speed increase dstm said we would and have never had one single crash since I started using his miner back in December.

So I don't know what is up with other problems reported.  I agree with chaostic in that most of the issues are user error and not setting up the Linux environment correctly.  I've been using Linux since 1997 so perhaps that is why I don't have issues.

I have the exact same issue going on. just updated Awesome Miner. Looks like part of that update was to update to the new DSTM 0.6.1 Now the only thing updating in my miner is the server difficulty changes. Only running 3 1050TI's on it at the moment.

After adding 1080ti this miner is constantly crashing after some short time (10-30 minutes).
Tried without OC, stock settings even lower power limit with no OC, it's allwats crashed.

Other miners works perfectly, even Bminer works 24/7 without single problem (with average OC).

Previously when I had just 5x 1080 it works OK, but after swapping one with 1080ti I can't use this miner.
Power supply is rock solid and have enough room left (loaded on 60% capacity), mining rig sistem is stable 100%

OS: Windows Server 2016 Standard (v 1607)
Driver Version: 397.64

Here are the clocks:
1080ti

1080


Event Viewer:


Also error report crash file (hope it can help).
https://mega.nz/#!y9VUwDrI!rleo2LMXiWaawMXqfE9thAIi7b9iHrbqYsltKoi9S4A

How do I get 0.6.1 to work with nicehash legacy miner 1.9.0.2? On windows 10


something changed from 0.5.8 to 0.6.1 as nhml does not want to benschmark. Betchmark fails



log from DSTM zm 0.6.1
2018-05-26 03:48:53|# zm 0.6.1
2018-05-26 03:48:53|# GPU0 - GeForce GTX 1080 Ti MB: 11264 PCI: 2:0
2018-05-26 03:48:53|# GPU1 - GeForce GTX 1080 Ti MB: 11264 PCI: 3:0
2018-05-26 03:48:53|# GPU2 - GeForce GTX 1080 Ti MB: 11264 PCI: 6:0
2018-05-26 03:48:53|# GPU3 + GeForce GTX 1070 MB: 8192 PCI: 5:0
2018-05-26 03:48:53|
2018-05-26 03:48:53|# pool1 equihash.eu.nicehash.com:3357
2018-05-26 03:48:53|
2018-05-26 03:48:53|# telemetry server listening on 127.0.0.1:4005
2018-05-26 03:48:54|# connected to: equihash.eu.nicehash.com:3357 [1/1]
2018-05-26 03:48:56|# server supports extranonce
2018-05-26 03:49:02|# server set difficulty to: 4.24999189 [0001e1e1e1e00000000000000000000...]
2018-05-26 03:49:22|> GPU3 50C 49% | 481.6 Sol/s 481.6 Avg 256.5 I/s | 3.84 S/W 126 W | 0.00 . .

log form zm 0.5.8
2018-05-26 03:45:37|# zm 0.5.8
2018-05-26 03:45:37|# GPU0 - GeForce GTX 1080 Ti MB: 11264 PCI: 2:0
2018-05-26 03:45:37|# GPU1 - GeForce GTX 1080 Ti MB: 11264 PCI: 3:0
2018-05-26 03:45:38|# GPU2 - GeForce GTX 1080 Ti MB: 11264 PCI: 6:0
2018-05-26 03:45:38|# GPU3 + GeForce GTX 1070 MB: 8192 PCI: 5:0
2018-05-26 03:45:38|
2018-05-26 03:45:38|# telemetry server started
2018-05-26 03:45:38|# connected to: equihash.eu.nicehash.com:3357
2018-05-26 03:45:40|# server supports extranonce
2018-05-26 03:45:46|# server set difficulty to: 0001e1e1e1e0000000000000...
2018-05-26 03:46:06|> GPU3 46C Sol/s: 472.5 Sol/W: 3.81 Avg: 472.5 I/s: 257.5 Sh: 0.00 . .
2018-05-26 03:46:27| GPU3 50C Sol/s: 469.2 Sol/W: 3.71 Avg: 470.9 I/s: 255.3 Sh: 0.00 . .

im sure I need to change something in MinerOptionPackage_dtsm.json but not what

{
"Name": "dtsm",
"Type": 19,
"GeneralOptions": [
{
"Type": "dtsm_time",
"ShortName": "--time",
"LongName": "--time",
"Default": null,
"FlagType": 0,
"Separator": ""
},
{
"Type": "dtsm_noreconnect",
"ShortName": "--noreconnect",
"LongName": "--noreconnect",
"Default": null,
"FlagType": 0,
"Separator": ""
},
{
"Type": "dtsm_temp-target",
"ShortName": "--temp-target",
"LongName": "--temp-target",
"Default": null,
"FlagType": 1,
"Separator": ""
}
],
"TemperatureOptions": []
}

In Claymore miner for (AMD) you can set parameter (example: -tt 75").

The miner will then adjust the fan speed to try to hold the tempature stable.

This will save the fans alot, since they run as low as they need. Insted of setting a static fan speed.

You also have another parameter equal to dstm's temp-target.

Can you implement this feature/parameter for DSTM? (Refering to the -tt parameter)

--

My fans speed and the noice are much lower with this feature, and your fans will last longer.

Hi DSTM,

I noticed quite a difference in CPU usage between 0.6.0 and 0.6.1 running on vanilla Debian 9.4 (Stretch).
Here it goes: https://imgur.com/a/lNtcqlC

I measured the CPU usages with top over a period of time (around 1 minute or so) and took the average.
The behaviour of 0.6.1 running on my miner is that the last GPU (GPU4) is running at 75% of its capacity.
This rig has 4 GTX 1070 and 1 GTX 1080.  One of the 1070s is GPU4.
That's quite odd (considering the high CPU usage of kworker and some IRQs as well with 0.6.1).
GPU Overclock, memory clock, power limit have been kept identical in the two runs (0.6.0 vs 0.6.1).
The only actual difference is zm executable version.

Hope it helps.  Meanwhile, I reverted to 0.6.0 that uses less CPU and provides a higher combined hashrate on my rig.

Thanks for your good work! Cheers!

DSTM, thanks for the new version.  I haven't had any issues with latency on MiningPoolHub, ZPool or NiceHash using Windows 10. However, I do have a quick question regarding latency.  Is 1.0  the default value?  Based on my limited testing, I am assuming it is as any lower value reduces the hash rate, but I would like a quick confirmation of that. Thanks.

So i get a strange thing happening in 6.1.  I have two 1080ti's on my comp and when i run my second card by itself the output shows only the first line of hash info and then stops displaying any info except for difficulty changes.  The card is hashing and is reporting on the pool but the output display just shows the difficulty changes. If i run my first card by itself and if i run the two cards together they output fine just how they are suppose to.. Must be a little glitch with running dev 1 only i guess. Anyone else running into this?   Great miner by the way..  https://imgur.com/a/BP5ulKB

very buggy release. i am using hiveos. dstm 0.6.1.

1. gtx1080ti has hashrate around 200 sols
2. ping problem (already reported here before)

Hi, i have a problem, zm_0.6.1.tar.gz SHA1 not match.

Cheers W_M

DSTM

The web interface still shows average card performance values. This is very inconvenient, because the current values are important. The cards sometimes falls a hashrate and your averaged values in the WEB and the interface do not allow this to be seen. You have to constantly monitor the log file to see the current actual data, and they are important. You can at least make this parameter functional; the average values make it difficult to quickly see the state of the hashrate right now. At the moment, I'm fine with everything your miner, but the average values interfere with normal monitoring of current performance. Here is a typical example, web monitoring shows a large hash, but the farm really needs to be rebooted urgently, because I saw the log file on time. Please make a display in the web monitor of the CURRENT hashrate.

You apply 2 queue per GPU, right? Make please option for switch between old/new modes for selected card. For example - like "dev=0,1,2" for old mode and "dev=0,0,1,2,2" for new mode (card 0 and 2 - 2 thread/GPU, card 1 - 1 thread/GPU)

Also, with v6.1:
gtx750 - SM5.0 - same performance, +1..2 sols/sec
gtx950 - SM5.2 - yes, +2% faster
gtx1050ti - SM6.1 - 1-2% SLOWER 

Rollback to v6.0