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

hogwash.89m

newbie

Activity: 32

Merit: 0

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
https://i.imgur.com/e0zKzYe.png
1080
https://i.imgur.com/ZitgUgV.png

Event Viewer:

Code:

Event 1000, Application Error
Faulting application name: zm.exe, version: 0.0.0.0, time stamp: 0x00000000
Faulting module name: zm.exe, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000008fe12
Faulting process id: 0x77c
Faulting application start time: 0x01d3f47d2c462088
Faulting application path: C:\!Miners\zm_0.6.1_win\zm.exe
Faulting module path: C:\!Miners\zm_0.6.1_win\zm.exe
Report Id: f962065c-be3a-4153-aa85-df417e9e33bd
Faulting package full name:
Faulting package-relative application ID:

Code:

Event 1001, Windows Error Reporting

Fault bucket 1718476532690713038, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: zm.exe
P2: 0.0.0.0
P3: 00000000
P4: zm.exe
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: 000000000008fe12
P9:
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER20CD.tmp.WERInternalMetadata.xml

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_zm.exe_4c86bba33fda172b979fde4c3dad8d2c2d2ff5_237d25c2_061f1a69

Analysis symbol:
Rechecking for solution: 0
Report Id: f962065c-be3a-4153-aa85-df417e9e33bd
Report Status: 0
Hashed bucket: 11d893f0476cc87e17d9414d35dff9ce

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

blackjec

newbie

Activity: 20

Merit: 0

Quote from: artful on May 26, 2018, 10:59:44 AM

claymore / ethdcrminer64 sorted by physically bus-ID. nvidia-settings sorted by physically bus-ID

It's right way, but is exception, not rule =)

P.S. if I remember correctly - nvidia-settings under Windows (nvcplui.exe) sorted by name.
Under linux - as defined in sections "Device" in /etc/X11/xorg.conf, but I not sure. I check it later.

artful

newbie

Activity: 59

Merit: 0

Quote from: blackjec on May 24, 2018, 02:32:15 AM

Quote from: artful on May 23, 2018, 07:10:12 AM

error in linux in parametr --dev

why GPU 0 is free?? and GPU 2 is working ?

nvidia-smi show devices as is, sorted by physically bus-ID.
All know miners (and zm too) show devices sorted alphabetically by his NAME.

For example - I has 3 gtx - 750, 950 and 1050ti.

Code:

Look at columns 1 and 4 (ID and Bus-ID) - devices sorted by Bus-ID - 0:01 0:04 0:05

zm give next output -

Code:

2018-05-24 13:26:05|# zm 0.6
2018-05-24 13:26:05|# GPU0 + GeForce GTX 1050 Ti MB: 4040 PCI: 5:0
2018-05-24 13:26:05|# GPU1 + GeForce GTX 750 MB: 979 PCI: 1:0
2018-05-24 13:26:05|# GPU2 + GeForce GTX 950 MB: 2002 PCI: 4:0
2

Devices sorted by name - 1050 750 950

For some example -

Code:

NeoScrypt CUDAminer v1.0.1 compiled with GCC 4.8 using CUDA 6.5

GPU #0: SM 6.1 GeForce GTX 1050 Ti
GPU #1: SM 5.0 GeForce GTX 750
GPU #2: SM 5.2 GeForce GTX 950

claymore / ethdcrminer64 sorted by physically bus-ID. nvidia-settings sorted by physically bus-ID

Etherion

sr. member

Activity: 512

Merit: 260

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": []
}

dave_bbp

jr. member

Activity: 405

Merit: 3

Hi there.
I used version 0.6 for weeks and never had any problems. Today I updated to 0.6.1 and while the performance seems ok (at least at pool side) I have a strange phenomenon:
The miner output only occurs ONCE and then never again (tested on different pools, coins etc.), so my whole output looks like this:

Code:

2018-05-25 12:34:36|# server set difficulty to: 0.13281225 [003c3c3c3c3c3c3c3c3c3c3c3c3c3c3...]
2018-05-25 12:34:56|> GPU1 74C 53% | 299.7 Sol/s 299.7 Avg 156.5 I/s | 3.37 S/W 93 W | 11.98 100 36 ++++
2018-05-25 12:35:46|# server set difficulty to: 0.39843674 [0014141414141414141414141414141...]
2018-05-25 12:36:52|# server set difficulty to: 1.06249797 [0007878787878787878787878787878...]
2018-05-25 12:37:56|# server set difficulty to: 0.45021101 [0011c4f82b5f6776758143822497ee8...]
2018-05-25 12:39:02|# server set difficulty to: 0.22510550 [002389f056beceeceb028704492fdd0...]
2018-05-25 12:41:11|# server set difficulty to: 0.33348963 [0017fd1bd424589e05fd9e5c044476a...]
2018-05-25 12:42:16|# server set difficulty to: 0.10105746 [004f29a8a25c70263eeeb5f1a022254...]
2018-05-25 12:43:22|# server set difficulty to: 0.35370113 [00169e302e666749ef9b1d69bf9aac3...]
2018-05-25 12:44:26|# server set difficulty to: 0.88425282 [00090c1345c30470cc72110a5a62059...]

I'm currently mining with a single 1060 (3GB) under Windows 10. Is there any way to force the miner to output the status line (or manually do so like e.g. pressing "h" in xmrig)? Thanks for your help!

just for comparison: version 0.6 looks like this:

Code:

2018-05-25 13:05:04|# server set difficulty to: 003c3c3c3c3c3c3c3c3c3c3c...
2018-05-25 13:05:24|> GPU1 72C Sol/s: 295.1 Sol/W: 3.29 Avg: 295.1 I/s: 158.7 Sh: 14.88 1.00 53 +++++
2018-05-25 13:05:44| GPU1 73C Sol/s: 298.3 Sol/W: 3.29 Avg: 296.7 I/s: 156.8 Sh: 17.94 1.00 39 +++++++
2018-05-25 13:05:57|# server set difficulty to: 0012ee5c12ece860d8678811...
2018-05-25 13:06:04|> GPU1 74C Sol/s: 297.4 Sol/W: 3.28 Avg: 296.9 I/s: 156.8 Sh: 14.93 1.00 48 +++
2018-05-25 13:06:25| GPU1 75C Sol/s: 296.5 Sol/W: 3.27 Avg: 296.8 I/s: 156.9 Sh: 14.91 1.00 37 +++++
2018-05-25 13:06:45| GPU1 76C Sol/s: 290.6 Sol/W: 3.25 Avg: 295.6 I/s: 156.8 Sh: 12.52 1.00 38 +
2018-05-25 13:07:05| GPU1 76C Sol/s: 292.5 Sol/W: 3.25 Avg: 295.1 I/s: 156.9 Sh: 11.43 1.00 48 ++

blackjec

newbie

Activity: 20

Merit: 0

Quote from: artful on May 23, 2018, 07:10:12 AM

error in linux in parametr --dev

why GPU 0 is free?? and GPU 2 is working ?

nvidia-smi show devices as is, sorted by physically bus-ID.
All know miners (and zm too) show devices sorted alphabetically by his NAME.

For example - I has 3 gtx - 750, 950 and 1050ti.

Code:

Look at columns 1 and 4 (ID and Bus-ID) - devices sorted by Bus-ID - 0:01 0:04 0:05

zm give next output -

Code:

2018-05-24 13:26:05|# zm 0.6
2018-05-24 13:26:05|# GPU0 + GeForce GTX 1050 Ti MB: 4040 PCI: 5:0
2018-05-24 13:26:05|# GPU1 + GeForce GTX 750 MB: 979 PCI: 1:0
2018-05-24 13:26:05|# GPU2 + GeForce GTX 950 MB: 2002 PCI: 4:0
2

Devices sorted by name - 1050 750 950

For some example -

Code:

NeoScrypt CUDAminer v1.0.1 compiled with GCC 4.8 using CUDA 6.5

GPU #0: SM 6.1 GeForce GTX 1050 Ti
GPU #1: SM 5.0 GeForce GTX 750
GPU #2: SM 5.2 GeForce GTX 950

wi7chking

newbie

Activity: 2

Merit: 0

Quote from: artful on May 23, 2018, 07:10:12 AM

error in linux in parametr --dev

Code:

nvidia-smi
Wed May 23 14:05:25 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 396.26 Driver Version: 396.26 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 106... Off | 00000000:01:00.0 Off | N/A |
| 70% 58C P2 96W / 96W | 496MiB / 3018MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 106... Off | 00000000:02:00.0 Off | N/A |
| 70% 57C P2 94W / 96W | 502MiB / 6078MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 106... Off | 00000000:04:00.0 Off | N/A |
| 70% 32C P2 98W / 96W | 496MiB / 3019MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 106... Off | 00000000:0A:00.0 Off | N/A |
| 70% 59C P2 96W / 96W | 502MiB / 6078MiB | 100% Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 935 G /usr/lib/xorg/Xorg 5MiB |
| 0 18757 C /opt/mining/calcprofit/miner/zm/zm 479MiB |
| 1 935 G /usr/lib/xorg/Xorg 5MiB |
| 1 18735 C /opt/mining/calcprofit/miner/zm/zm 485MiB |
| 2 935 G /usr/lib/xorg/Xorg 5MiB |
| 2 18746 C /opt/mining/calcprofit/miner/zm/zm 479MiB |
| 3 935 G /usr/lib/xorg/Xorg 5MiB |
| 3 18724 C /opt/mining/calcprofit/miner/zm/zm 485MiB |
+-----------------------------------------------------------------------------+

ps aux | grep zm
root 18724 3.4 1.5 39197088 122900 pts/3 Sl 14:05 0:01 /opt/mining/calcprofit/miner/zm/zm --dev 1 --server equihash.eu.nicehash.com --port 3357
root 18735 3.6 1.5 39197088 122796 pts/3 Sl 14:05 0:01 /opt/mining/calcprofit/miner/zm/zm --dev 0 --server equihash.eu.nicehash.com --port 3357
root 18746 3.2 1.5 39197088 122880 pts/3 Sl 14:05 0:01 /opt/mining/calcprofit/miner/zm/zm --dev 3 --server equihash.eu.nicehash.com --port 3357
root 18757 3.0 1.5 39197088 123084 pts/3 Sl 14:05 0:01 /opt/mining/calcprofit/miner/zm/zm --dev 2 --server equihash.eu.nicehash.com --port 3357

me kill process 18757 (kill -9 18757 ) - it is DEVICE=2
after check nvidia-smi:

Code:

nvidia-smi
Wed May 23 14:08:34 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 396.26 Driver Version: 396.26 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 106... Off | 00000000:01:00.0 Off | N/A |
| 70% 31C P8 8W / 96W | 17MiB / 3018MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 106... Off | 00000000:02:00.0 Off | N/A |
| 70% 57C P2 96W / 96W | 502MiB / 6078MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 106... Off | 00000000:04:00.0 Off | N/A |
| 70% 46C P2 96W / 96W | 496MiB / 3019MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 106... Off | 00000000:0A:00.0 Off | N/A |
| 70% 61C P2 97W / 96W | 502MiB / 6078MiB | 100% Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 935 G /usr/lib/xorg/Xorg 5MiB |
| 1 935 G /usr/lib/xorg/Xorg 5MiB |
| 1 18735 C /opt/mining/calcprofit/miner/zm/zm 485MiB |
| 2 935 G /usr/lib/xorg/Xorg 5MiB |
| 2 18746 C /opt/mining/calcprofit/miner/zm/zm 479MiB |
| 3 935 G /usr/lib/xorg/Xorg 5MiB |
| 3 18724 C /opt/mining/calcprofit/miner/zm/zm 485MiB |
+-----------------------------------------------------------------------------+

root 18724 3.0 1.5 39197088 122900 pts/3 Sl 14:05 0:03 /opt/mining/calcprofit/miner/zm/zm --dev 1 --server equihash.eu.nicehash.com --port 3357
root 18735 3.2 1.5 39197088 122796 pts/3 Sl 14:05 0:04 /opt/mining/calcprofit/miner/zm/zm --dev 0 --server equihash.eu.nicehash.com --port 3357
root 18746 3.0 1.5 39197088 122880 pts/3 Sl 14:05 0:03 /opt/mining/calcprofit/miner/zm/zm --dev 3 --server equihash.eu.nicehash.com --port 3357

why GPU 0 is free?? and GPU 2 is working ?

Killing process 18757 ends up killing the zm process running on GPU 0 (being the process using it as reported by nivida-smi).
--dev option is using CUDA device ids that are not the same as the ones reported by nvidia-smi.

Hence, in your case:
* GPU 0 is CUDA dev 2.
* GPU 1 is CUDA dev 0.
* GPU 2 is CUDA dev 3.
* GPU 3 is CUDA dev 1.

artful

newbie

Activity: 59

Merit: 0

error in linux in parametr --dev

Code:

nvidia-smi
Wed May 23 14:05:25 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 396.26 Driver Version: 396.26 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 106... Off | 00000000:01:00.0 Off | N/A |
| 70% 58C P2 96W / 96W | 496MiB / 3018MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 106... Off | 00000000:02:00.0 Off | N/A |
| 70% 57C P2 94W / 96W | 502MiB / 6078MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 106... Off | 00000000:04:00.0 Off | N/A |
| 70% 32C P2 98W / 96W | 496MiB / 3019MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 106... Off | 00000000:0A:00.0 Off | N/A |
| 70% 59C P2 96W / 96W | 502MiB / 6078MiB | 100% Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 935 G /usr/lib/xorg/Xorg 5MiB |
| 0 18757 C /opt/mining/calcprofit/miner/zm/zm 479MiB |
| 1 935 G /usr/lib/xorg/Xorg 5MiB |
| 1 18735 C /opt/mining/calcprofit/miner/zm/zm 485MiB |
| 2 935 G /usr/lib/xorg/Xorg 5MiB |
| 2 18746 C /opt/mining/calcprofit/miner/zm/zm 479MiB |
| 3 935 G /usr/lib/xorg/Xorg 5MiB |
| 3 18724 C /opt/mining/calcprofit/miner/zm/zm 485MiB |
+-----------------------------------------------------------------------------+

ps aux | grep zm
root 18724 3.4 1.5 39197088 122900 pts/3 Sl 14:05 0:01 /opt/mining/calcprofit/miner/zm/zm --dev 1 --server equihash.eu.nicehash.com --port 3357
root 18735 3.6 1.5 39197088 122796 pts/3 Sl 14:05 0:01 /opt/mining/calcprofit/miner/zm/zm --dev 0 --server equihash.eu.nicehash.com --port 3357
root 18746 3.2 1.5 39197088 122880 pts/3 Sl 14:05 0:01 /opt/mining/calcprofit/miner/zm/zm --dev 3 --server equihash.eu.nicehash.com --port 3357
root 18757 3.0 1.5 39197088 123084 pts/3 Sl 14:05 0:01 /opt/mining/calcprofit/miner/zm/zm --dev 2 --server equihash.eu.nicehash.com --port 3357

me kill process 18757 (kill -9 18757 ) - it is DEVICE=2
after check nvidia-smi:

Code:

nvidia-smi
Wed May 23 14:08:34 2018
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 396.26 Driver Version: 396.26 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 106... Off | 00000000:01:00.0 Off | N/A |
| 70% 31C P8 8W / 96W | 17MiB / 3018MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 106... Off | 00000000:02:00.0 Off | N/A |
| 70% 57C P2 96W / 96W | 502MiB / 6078MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 106... Off | 00000000:04:00.0 Off | N/A |
| 70% 46C P2 96W / 96W | 496MiB / 3019MiB | 100% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 106... Off | 00000000:0A:00.0 Off | N/A |
| 70% 61C P2 97W / 96W | 502MiB / 6078MiB | 100% Default |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 935 G /usr/lib/xorg/Xorg 5MiB |
| 1 935 G /usr/lib/xorg/Xorg 5MiB |
| 1 18735 C /opt/mining/calcprofit/miner/zm/zm 485MiB |
| 2 935 G /usr/lib/xorg/Xorg 5MiB |
| 2 18746 C /opt/mining/calcprofit/miner/zm/zm 479MiB |
| 3 935 G /usr/lib/xorg/Xorg 5MiB |
| 3 18724 C /opt/mining/calcprofit/miner/zm/zm 485MiB |
+-----------------------------------------------------------------------------+

root 18724 3.0 1.5 39197088 122900 pts/3 Sl 14:05 0:03 /opt/mining/calcprofit/miner/zm/zm --dev 1 --server equihash.eu.nicehash.com --port 3357
root 18735 3.2 1.5 39197088 122796 pts/3 Sl 14:05 0:04 /opt/mining/calcprofit/miner/zm/zm --dev 0 --server equihash.eu.nicehash.com --port 3357
root 18746 3.0 1.5 39197088 122880 pts/3 Sl 14:05 0:03 /opt/mining/calcprofit/miner/zm/zm --dev 3 --server equihash.eu.nicehash.com --port 3357

why GPU 0 is free?? and GPU 2 is working ?

evehuu

brand new

Activity: 0

Merit: 0

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.

BogdanCo

hero member

Activity: 729

Merit: 513

Quote from: paranoid247 on May 22, 2018, 06:08:35 AM

anyone else found that the longer you run dstm 0.6.1 for linux, the average sol/w drops in linux. i have a a test rig with 2 Gigabyte G1 6GB GTX1060's running ubuntu 16.04 desktop. started out at avg 664.2 sol/s after the first hour, then roughly every hour the avg sol/w drops .1 sol/s. so after a week the avg is 647.4 sol/s(a lost of 16.8sol/s).

i left it run till the avg hit 640 sol/s, till i rebooted the system to install some system updates. Once again the avg goes back to 664 sol and slowly drops again.

I can confirm this issue. I also have to reboot the rigs constantly to keep the hash rate. Same dstm 0.6.1 and linux. With 0.6.0 there was not such issue.

digifarm

newbie

Activity: 13

Merit: 0

Hi

# connected to: zec.viabtc.com:3333 [1/1]
# SSL_connect failed r:2 error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed

Im consistently getting this error and have to reboot the rig to get it running again. Anyone knows whats the issue with this?

Biggen1

newbie

Activity: 64

Merit: 0

I'm not seeing any performance issues on Ubuntu Server 16.04.4. I am seeing performance increases however. Rig seems just as stable and CPU usage appears the same on DSTM 0.6.1 as it did on previous versions.

Eight GTX 1070Ti @ ~505 Sol/s each for a total of ~4050 Sol/s for the entire rig.

Cards are undervolted/underpowered via Nvidia-SMI and overclocked as per the norm for the 1070TIs.

paranoid247

newbie

Activity: 9

Merit: 0

anyone else found that the longer you run dstm 0.6.1 for linux, the average sol/w drops in linux. i have a a test rig with 2 Gigabyte G1 6GB GTX1060's running ubuntu 16.04 desktop. started out at avg 664.2 sol/s after the first hour, then roughly every hour the avg sol/w drops .1 sol/s. so after a week the avg is 647.4 sol/s(a lost of 16.8sol/s).

i left it run till the avg hit 640 sol/s, till i rebooted the system to install some system updates. Once again the avg goes back to 664 sol and slowly drops again.

Keko Fdez

jr. member

Activity: 108

Merit: 7

Quote from: kingmoneymastery on May 21, 2018, 02:40:31 PM

Hi may I ask what does I/s stand for and what do the last three column readings mean? Mine are 7.31, 100, 36

I am new to dstm miner.

Thank you

You have all the information in the Readme file that is why it is called Readme.

Anyway, here you have the information:

I/s: iterations per second done by the GPU

last 3 colums: , , .

Keko Fdez

jr. member

Activity: 108

Merit: 7

Hi guys!

I would like some help from DSTM and from anyone that could help.

Two days ago there was a power cut in the area where there miner lives (different from where I live). When the power was restored the miner went back to life and everything seemed normal in the pool (I could not access it via teamviewer because it gave me a black screen. After connecting an HDMI cable to the tv it worked again on Ipad, iphone and laptop so something weird about teamviewer I guess).

The issue is that the miner (DSTM 0.6.0) is no longer working the way it was. Before the power cut, miner was doing around 11.55 shares average in the console. My rig is 6 GTX 1070 Ti. After the power cut the miner is now doing 5.98 shares at the best though flypool reports the same share rate submitted and the payout hasn´t drop (it is pretty much the same and as we all know is changing with the difficulty itself).

I have tried few things to see if the miner would improve but it hasn´t so I decided to change to new version of DSTM 0.6.1. The new lay out is great and the miner works fine with a small improvement on the hashrate in windows as well (although DSTM said improvement was only for linux systems). The hashrate is not a problem but the share rate doesn´t look right to me now sitting at 4.0 shares in the console?

I have only been mining for 2 months so I am fairly new and there are still too many things beyond my knowledge but my guess is that the difficulty from the server has changed and gone up so the share rate is gone down but as they are more difficult to get the payout of those shares is higher. Am I right or wrong? Has anyone experience the same problem recently?? Any other explanation for the drop in shares from 11.55 down to 4??

I also notice a couple of days ago something unusual for my miner, it hit a record of 193 shares submitted, then 167 and so on. Something I had never seen before (I know the number changes with the difficulty but 193 and 167 for my 6 GTX 1070 Ti is of the scale and not normal unless the difficulty dropped below 6 Million which I didn´t see).

Does it have something to do with the drop in shares reported by the console?

DSTM: great miner and a small improvement in hashrate for windows too. I would say about 0.2-0.3% not much but better than nothing. So please keep working on it.

Thank you guys!!

Biggen1

newbie

Activity: 64

Merit: 0

Quote from: kingmoneymastery on May 21, 2018, 02:40:31 PM

Hi may I ask what does I/s stand for and what do the last three column readings mean? Mine are 7.31, 100, 36

I am new to dstm miner.

Thank you

Check the 1st post on the 1st page.

kingmoneymastery

jr. member

Activity: 61

Merit: 1

Join The Frontier

Hi may I ask what does I/s stand for and what do the last three column readings mean? Mine are 7.31, 100, 36

I am new to dstm miner.

Thank you

Aleksei_su

newbie

Activity: 2

Merit: 0

NO start DSTM miner for Linux Ubuntu - Help!?

dstm

full member

Activity: 350

Merit: 126

Thx for the reports related to performance issues on 0.6.1/linux.
I'm currently looking into it.

evehuu

brand new

Activity: 0

Merit: 0

Issues with dstm 6.1.0 - low hash on some GPU's

Hardware
MB: B250 mining expert
13x GPU: Nvidia Asus 1060 3 GB

OS: SMOS - NV 1173
Linux Kernel: 4.16.0-rc6-smos

OC:
Core: 0
Memory: 0
Power: 90w

(Tried different OC settings, same result)

--

Out of my 13 GPU's, 5 of them are running on 100-140 sol/s. The rest are fine (290 sol/s)

--

On dstm 6.0.0 - all GPU's running fine with no issues - 290 sol/s

Let me know if you need more info about hardware/software or logfiles.

Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) - page 10. (Read 224621 times)