Topic: [ANN] dstm's ZCash / Equihash Nvidia Miner v0.6.2 (Linux / Windows) (Read 224621 times)
February 24, 2022, 10:54:36 PM
Are we paying Russian's with this miner? cough cough, gminer
May 06, 2021, 09:22:26 AM
Try other coin, Zcash is a ASIC coin, you don´t make any profit. And please take another miner, this miner is very outdated.
May 06, 2021, 09:12:54 AM
DSTM not updated in 3 years...run something else.
May 06, 2021, 05:34:34 AM
Sorry, i have this SSL problem but i dont find the 0.6.2 to download.
Is it normal?
Im a real newbee.
Thks.
I have download 0.6.2 for linux and still have problem Is it normal?
Im a real newbee.
Thks.
connected to: eu1-zcash.flypool.org:3333 [1/1]
# SSL_connect failed r:2 error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed
# connected to: eu1-zcash.flypool.org:3333 [1/1]
./zm --server eu1-zcash.flypool.org --port 3333 --user user
February 20, 2021, 12:06:55 AM
Hi everyone, I am using version 06-190 of hiveos but it is giving me this error (Root ##) when it is running linux, I have a 4gb rx570 cards, someone could help me how I solve this problem or where I can download the latest version of Hiveos
February 21, 2020, 05:58:07 PM
dstm wasn't updated for ages.
I would recommend GMiner, lolMiner or miniZ which are updated regularly.
You can use the app in my signature to get the latest version.
[/quote]
Many thanks.
I would recommend GMiner, lolMiner or miniZ which are updated regularly.
You can use the app in my signature to get the latest version.
[/quote]
Many thanks.
February 20, 2020, 04:29:09 AM
All of a sudden several of my Nvidia GPU won't work with 0.6.2, I click the bat file and it briefly shows the command prompt and disappears. Any suggestions?
dstm wasn't updated for ages.
I would recommend GMiner, lolMiner or miniZ which are updated regularly.
You can use the app in my signature to get the latest version.
February 19, 2020, 05:57:00 PM
All of a sudden several of my Nvidia GPU won't work with 0.6.2, I click the bat file and it briefly shows the command prompt and disappears. Any suggestions?
June 15, 2019, 05:32:37 PM
Just started running this software now to see if I can get it to work. It seems to have the same issue as EWBFs miner. Every share seem to be getting rejected. I cannot find any help on this subject.
Specs:
Running a ryzen 1600 with a gtx 1080 on Windows 10 64-bit and nothing is overclocked.
[ZM.CFG]:
[OUTPUT]:
Note: Nevermind just found out that at some point BTCZ started using an algorithm that DSTM doesn't support, so rip.
Specs:
Running a ryzen 1600 with a gtx 1080 on Windows 10 64-bit and nothing is overclocked.
[ZM.CFG]:
Code:
intensity=0:0.9
temp-target=0:65
[POOL]
server=mine-btcz-na.equipool.1ds.us
port=50063
user=address.gtx1080
pass=minpayout=500
temp-target=0:65
[POOL]
server=mine-btcz-na.equipool.1ds.us
port=50063
user=address.gtx1080
pass=minpayout=500
[OUTPUT]:
Code:
2019-06-15 5:16:55 PM|# zm 0.6.2
2019-06-15 5:16:55 PM|# GPU0 + GeForce GTX 1080 MB: 8192 PCI: 9:0
2019-06-15 5:16:55 PM|
2019-06-15 5:16:55 PM|# using configuration file zm.cfg
2019-06-15 5:16:55 PM|# pool1 mine-btcz-na.equipool.1ds.us:50063
2019-06-15 5:16:55 PM|
2019-06-15 5:16:55 PM|# GPU0 temperature target 65C
2019-06-15 5:16:55 PM|# GPU0 intensity 0.9000
2019-06-15 5:16:55 PM|
2019-06-15 5:16:55 PM|# telemetry server listening on 0.0.0.0:2222
2019-06-15 5:16:56 PM|# connected to: mine-btcz-na.equipool.1ds.us:50063 [1/1]
2019-06-15 5:16:57 PM|# server set difficulty to: 0.24999952 [0020000000000000000000000000000...]
2019-06-15 5:16:58 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:02 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:07 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:07 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:07 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:07 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:08 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:13 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:18 PM|> GPU0 55C 44% | 553.8 Sol/s 553.8 Avg 295.0 I/s | 3.08 S/W 174 W | 23.92 0.0 . ++++++++
2019-06-15 5:17:27 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:34 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:38 PM| GPU0 60C 49% | 520.4 Sol/s 537.1 Avg 278.6 I/s | 3.02 S/W 179 W | 14.95 0.0 . ++
2019-06-15 5:17:44 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:50 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:51 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:52 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:55 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:55 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:56 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:58 PM|> GPU0 63C 52% | 451.3 Sol/s 508.5 Avg 241.0 I/s | 2.88 S/W 175 W | 16.95 0.0 . +++++++
2019-06-15 5:17:59 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:00 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:08 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:12 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:16 PM|# GPU0 reached temperature target 65C
2019-06-15 5:18:16 PM|# GPU0 enabling temperature controller
2019-06-15 5:18:18 PM| GPU0 65C! 53% | 449.8 Sol/s 493.8 Avg 244.1 I/s | 2.81 S/W 179 W | 15.70 0.0 . ++++
2019-06-15 5:18:22 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:24 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:35 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:36 PM|# server set difficulty to: 0.83606398 [00099191924ae864000000000000000...]
2019-06-15 5:18:38 PM|> GPU0 65C! 55% | 476.9 Sol/s 490.4 Avg 252.1 I/s | 2.80 S/W 145 W | 14.36 0.0 . +++
2019-06-15 5:18:43 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:58 PM| GPU0 65C! 55% | 353.0 Sol/s 467.5 Avg 188.6 I/s | 2.74 S/W 144 W | 12.46 0.0 . +
2019-06-15 5:19:18 PM| GPU0 65C! 55% | 334.0 Sol/s 448.5 Avg 176.7 I/s | 2.70 S/W 148 W | 10.68 0.0 .
2019-06-15 5:19:21 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:16:55 PM|# GPU0 + GeForce GTX 1080 MB: 8192 PCI: 9:0
2019-06-15 5:16:55 PM|
2019-06-15 5:16:55 PM|# using configuration file zm.cfg
2019-06-15 5:16:55 PM|# pool1 mine-btcz-na.equipool.1ds.us:50063
2019-06-15 5:16:55 PM|
2019-06-15 5:16:55 PM|# GPU0 temperature target 65C
2019-06-15 5:16:55 PM|# GPU0 intensity 0.9000
2019-06-15 5:16:55 PM|
2019-06-15 5:16:55 PM|# telemetry server listening on 0.0.0.0:2222
2019-06-15 5:16:56 PM|# connected to: mine-btcz-na.equipool.1ds.us:50063 [1/1]
2019-06-15 5:16:57 PM|# server set difficulty to: 0.24999952 [0020000000000000000000000000000...]
2019-06-15 5:16:58 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:02 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:07 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:07 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:07 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:07 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:08 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:13 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:18 PM|> GPU0 55C 44% | 553.8 Sol/s 553.8 Avg 295.0 I/s | 3.08 S/W 174 W | 23.92 0.0 . ++++++++
2019-06-15 5:17:27 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:34 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:38 PM| GPU0 60C 49% | 520.4 Sol/s 537.1 Avg 278.6 I/s | 3.02 S/W 179 W | 14.95 0.0 . ++
2019-06-15 5:17:44 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:50 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:51 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:52 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:55 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:55 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:56 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:17:58 PM|> GPU0 63C 52% | 451.3 Sol/s 508.5 Avg 241.0 I/s | 2.88 S/W 175 W | 16.95 0.0 . +++++++
2019-06-15 5:17:59 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:00 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:08 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:12 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:16 PM|# GPU0 reached temperature target 65C
2019-06-15 5:18:16 PM|# GPU0 enabling temperature controller
2019-06-15 5:18:18 PM| GPU0 65C! 53% | 449.8 Sol/s 493.8 Avg 244.1 I/s | 2.81 S/W 179 W | 15.70 0.0 . ++++
2019-06-15 5:18:22 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:24 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:35 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:36 PM|# server set difficulty to: 0.83606398 [00099191924ae864000000000000000...]
2019-06-15 5:18:38 PM|> GPU0 65C! 55% | 476.9 Sol/s 490.4 Avg 252.1 I/s | 2.80 S/W 145 W | 14.36 0.0 . +++
2019-06-15 5:18:43 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
2019-06-15 5:18:58 PM| GPU0 65C! 55% | 353.0 Sol/s 467.5 Avg 188.6 I/s | 2.74 S/W 144 W | 12.46 0.0 . +
2019-06-15 5:19:18 PM| GPU0 65C! 55% | 334.0 Sol/s 448.5 Avg 176.7 I/s | 2.70 S/W 148 W | 10.68 0.0 .
2019-06-15 5:19:21 PM|# GPU0 rejected share: [20,"Error: Incorrect size of solution (2694), expected 202"]
Note: Nevermind just found out that at some point BTCZ started using an algorithm that DSTM doesn't support, so rip.
May 18, 2019, 09:40:58 AM
If the pool disconnects, when reconnecting the intensity setting seems to become forgotten and goes back to full intensity.
Also if gpu reaches temperature target, it will forget intensity setting and goes back to max intensity.
February 22, 2019, 12:37:25 AM
If the pool disconnects, when reconnecting the intensity setting seems to become forgotten and goes back to full intensity.
December 29, 2018, 04:26:43 AM
Price of zcash is really low. Did anything change?.. should I keep mining?
bear market + ASIC equihash miners happened...
It's your own chose to mine further but I already switched over to other algo's long ago.
December 29, 2018, 02:42:29 AM
Price of zcash is really low. Did anything change?.. should I keep mining?
December 27, 2018, 04:52:53 PM
Greed shouldn’t have any place in Crypto I do agree, and it’s such a pity... however it is and was to be expected as it’s a primarily hyped up dreams that are hyped up beyond reality most of the time.. and since the crypto space is generally a progressive area in life you can expect everyone to always be greedy, people should still be given the option to turn a miner dev fee off though, simply way to many options not to be, I have dev fee off (at least supposed to be) and if I thought it actually worked and the miner app was worth it, I’d definitely donate, however miners are not “ever” going to be jumping to throw away a percentage of cash we’ve already earned, we have transaction fees, pool fees, misc running costs, he’ll for some people 2% is a crazy number to just be handing over for nothing in return, that being said dstm was the best zcash miner I’ve ever used, to bad they don’t have minex algo...
December 26, 2018, 10:04:20 AM
Fee or nofee, open or closed source it wont make any difference because there is already open source cuda kernel, just noone is interested as of devs to improve it for free Smiley
Open source miners are dead.
Open source miners are dead.
Some will ...
Most won't. Show me ONE time where donations or incentives were given freely and actually made a difference to the developers of ANY miner. NONE! We have had this argument for YEARS, and me more than anyone has tried to get donations (look at the DBM system for example, or CWIgm that we attempted) to help these developers. A handful of miners will donate, whereas the vast majority won't. Mining has become a greed riddled practice, just like what Crypto has fast become. This was never the goal for us that DO work towards a better Crypto future, but the vast majority of those that mine, mine in the most greedy way, that I must admit that you make some very valid points.
The one thing I will totally disagree with you is the point of Open Source Miners being FAR from dead. They will exist, they will always be developed, but not many will be optimized for free any more due to the abovementioned reasons. Greed has no place here in Crypto, but has a huge effect on it. As can be seen almost everywhere you go in CryptoLand.
Pity!
#crysx
December 23, 2018, 12:14:05 PM
Fee or nofee, open or closed source it wont make any difference because there is already open source cuda kernel, just noone is interested as of devs to improve it for free Smiley
Open source miners are dead.
Open source miners are dead.
December 23, 2018, 05:29:35 AM
+1 for Windows version
Nvidia owners are too rich to bother setting up Linux although it's probably better than Windows.
Nvidia owners are too rich to bother setting up Linux although it's probably better than Windows.
Has nothing to do with Nvidia owners to rich lol, everything to do with Nix has "been" dead, why would someone install Nix so they can be locked down lol, people use windows cuz its just better and way more versatile, only thing unix/Linux have going for them, is the fact that its free, you get what you pay for.
Then this shows how little you know ...
Especially about mining/productivity.
Either way, for a little mining system, that has little future progress, then sure, brag about Windows and 'all' it can do (which almost any Linux distribution can also do BTW). But grow and expand to a level where it is a 'farming' venture? Then you have another issue on your hands, and it is NOT 'just' licensing and getting the OS for 'free'. Especially when you consider that most Windows users who mine don't pay for the OS. Some do, most don't. The issues become far more complex and only a Linux based system (depending on linux Distribution of course) can become scalable in any form as opposed to the complexity of Windows.
We are nVidia based, and one of the larger GPU farms (theFARM) in the Southern Hemisphere. We will never route our systems to use Windows. Instead, we use an OS and rollout system that is stable, reliable, easy to upgrade, highly scalable, and yes free, though our Linux of choice is used mainly because we have the flexibility of compiling to our own benefit and optimizations (which is a complete nightmare in Windows), and we can roll it out under one seventh the time that Windows takes and 100% less cost than Windows.
So when one has to spend time, effort and money, then Windows is the LAST OS we look at as being a worthy OS to work with.
Argue all you want, the worlds largest, most productive and highly scalable entities ALL use a flavour of Linux in one way or another, especially the HPC, Grid and Mining systems. That tells you something about the limitations of Windows, even though very few features (like GUI OC for example) is available because too many are too afraid of ONE LINE COMMANDS in a console to do the exact same thing in Linux.
#crysx
November 30, 2018, 01:31:50 PM
+1 for Windows version
Nvidia owners are too rich to bother setting up Linux although it's probably better than Windows.
Nvidia owners are too rich to bother setting up Linux although it's probably better than Windows.
Has nothing to do with Nvidia owners to rich lol, everything to do with Nix has "been" dead, why would someone install Nix so they can be locked down lol, people use windows cuz its just better and way more versatile, only thing unix/Linux have going for them, is the fact that its free, you get what you pay for.
November 12, 2018, 12:27:04 PM
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.
Do not use drivers newer than 399.xx until you mine on RTX 20x0I 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.
NVidia started downscaling GTX 10x0 series since new generation is out.
Even games (like Witcher 3) lost 8~15 fps and gained some freezes and stuff like that on GTX 1080 with those new drivers...
Google about it, there's even some comparison videos on YT proving that downscale.
Version 399.24 — works best for my GTX 1070/1080 (both: games and mining).
November 12, 2018, 12:01:19 PM
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.
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.
Is your whole rig freezing (i.e mouse pointer isn't moving etc.)?
You could try to start only 1 GPU (using the -dev option) to make sure there are no power supply issues.
Jump to: