Bitcoin Forum

Hello,

currently ccminer is the fastest miner for MTP and the cheapest ;D

* 2.5MH/s on 1070
* 3.9MH/s on 1080ti with OhGodAPill (3.55MH/s without)

* 5.5MH/s on 2080ti

latest release:
new sgminer version released:
(improved stability)
https://github.com/zcoinofficial/sgminer/releases/tag/0.1.3

new ccminer version released:

https://github.com/zcoinofficial/ccminer/releases/tag/1.2.0

*better handling of miner/pool connection and packet losses in case of bad connection
solve various crash problem due to pool sending empty data

sliglty improved speed on 20x cards
This release should solve most of the crash which was encountered on the previous version.

performance:

2080ti gets now 5.5MH/s

1080ti 3.55MH/s
3.9MH/s with OhGodAPill

1070 at 2.5MH/s
1660 at 2.06MH/s

implement a non mandatory donation system (default 0.25% 1 share over 400)
This donation can be turned off by using --no-donation flag
%age donated can be changed by using flag --donation N (in per cent)

you can find binaries for windows (ccminer.exe)
and for linux:
* ccminer-linux-cuda101 (binaries for linux compiled with cuda 10.1
* ccminer-linux-cuda100 (binaries for linux compiled with cuda 10.0
* ccminer-linux-cuda92 (binaries for linux compiled with cuda 9.2

example of bat file:  RUN-ZCOIN-MTP.cmd


new version of sgminer has been released:
(no fee... too painfull to implement in sgminer  ;D, I'll probably add one, if I beat teamred on vega )

https://github.com/zcoinofficial/sgminer/releases/tag/0.1.2

Improved hashrate on both mtp.cl and mtp_vega.cl

mtp.cl for RX5xx and RX4xx

1.69MH @1250MH/z on RX580
do not use this kernel for vega performance are ridiculous Grin

mtp_vega.cl
1.685MH @1250MHz on RX580
3.1MH/s @1350MHz on Vega 56
currently this is on my RX580  around 400kh/s faster than teamred and it run at a lower frequency (100MHz lower for some reason...)
and 70kh/s slower than teamred on vega (same frequency)
use sgminer.conf to pass kernels/pool etc...

cheers,
djm34

I love your miner and its nice watching how you improved it, but its not the fastest.

I didnt check the 1xxx Series, but on the 2080 (running just under 1800 Mhz) the

T-Rex gets 4.173 Mhash and CCMiner only 3.5 Mhash.

CCMiner detects 11304960 Cuda Threads, 46 Threads per Block 320

Any improvement with manual settings possible?

Yes for the moment, T-rex is still faster on the 20x serie (which I don't own, will change when I will get my hand on one)
But as far as the 10x serie is concerned it is the fastest (especially with the help of OhGodAPill for the models using gdd5x).

In the latest release, you can vary the intensity.

I don't understand the 46Threads per block thing... can you elaborate ?

This is the report of your Miner, when it detects a 2080.

x miner threads startet, using the ´mtp´ algorithm.
Gpu #0: Intensity set to 23.3477, 11304960 cuda threads number of.....
Gpu #1: Intensity set to 23.3477, 11304960 cuda threads number of.....

So the autodetect might not be optimized for the 2080.
Can i set it manual?

--cuda-schedule 12000000

didnt work for me.

I don't think there is a cuda-schedule command in ccminer... what are you trying to attempt ?
if you mean to set the intensity, -i 20 is probably your example.

Why warning msg at the top of page.Djm one of the best miner coder i ever seen.Will try miner soon.

what warning ? (don't see any)

Warning: One or more bitcointalk.org users have reported that they strongly believe that the creator of this topic is a scammer. (Check their trust page to see the detailed trust ratings.) While the bitcointalk.org administration does not verify such claims, you should proceed with extreme caution.

wow... ;D
seriously... if it is related to trust rating, it is a random guy 4 years ago, who put a -1 trust over a sarcastic comment I made on some shitcoin  ;D

Hi djm34,

I appreciate your contributions; here is some feedback for your consideration.
I haven't been able to mine successfully with this release.
Hashrate appears competitive with t-rex, but all my shares are rejected (Nicehash pool).

- 7x 1070ti
- 8GB RAM, 80GB virtual RAM
- Afterburner settings: PL 72%, Core +200, Mem +0

My .BAT string:

ccminer -a mtp -o stratum+tcp://mtp.usa.nicehash.com:3374 -u WALLET.USER -p x

sorry but for the moment there is no support for nicehash

good improvement vs previous version, I get 4 MHh/s with 1080 ti and pill @85% power on mintpond, much higher than others...
(would be good to have nicehash, they sometimes pay more than regular mining!)

and 2.2 MH/s on 1070 @ 85% power, also better than other miners & previous version

It seems no effect if I use the ohmygod pill or I'm using a wrong pill. I have old ethereum pill from ohmygod from github before it's working in ethereum but when I try to use ohmygodpill in Zcoin mining it doesn't seem to work?

This is the complete name "OhGodAnETHlargementPill-master" can you provide the working for MTP?


What version of driver you currently installed with 1080ti?

The one I use is called "OhGodAnETHlargementPill-r2.exe"
You can probably google it (I prefer not to give a link because there are quite a few and none of them are linked to OhGodAGirl...)

I currently use drivers 430.86 the gaming version

driver is 430.64

What intensity to use for 1080ti and what oc?

The default one seems to give the best result (-i 20).
Regarding OC, you'll get a substantial hash increase by increasing core clock (or power limit... but obviously it depends a lot on electricity cost)
+150 on core does nicely

I've got 4.2mhs at 220 watt (gtx1080ti). Nice!

I have a few rigs with 3 or 4 1080ti, they work perfectly. But for rigs with 7x 1080ti, ram usage spikes to 99% within 10s of running the miner, hanging the whole system. Do I need more ram or page size, or is the issue due to something else?

Specs:

7x 1080ti FE at 70% PL
G4560
4GB Ddr4
67gb virtual ram

1600w psu


The other 3/4 1080ti rigs are doing 3.9 - 4.1mh/s each.

hmm ram usage ? or cpu usage ? (cpu with only 2 threads may have some difficulties in some case)
ram usage by ccminer is pretty low around 4-500Mb virtual ram, with 67Gb of virtual ram you should be ok (the 7 cards shouldn't use more than than 31Gb of swap). what you could try is to run 2 instances.

was thinking, this could be also an issue with difficulty, if your difficulty is too low (ie you are sending tons of 245kb shares, this might increase ram usage), you might need to increase the difficulty

I heard about the mining on invidia cards long before but actually I thought it is not profitable.
I will surely check it all out.

it was said to be not profitable in 2013 ;D

djm, no update planned for your AMD sgminer?

yes working on it (although would be nice if I could be on par with t-rex (or better) for the 20x serie first)

Why this error?

Need cuda 10.1 installed

Has anybody tested this on 'regular' 1080's by any chance? Is it actually faster than TT-miner and CryptoDredge at all?...

yes it is faster if you combine with OhGodAPill since the 1080 also use gddr5x

I don't know for other algo but as far as mtp is concerned, nicehash is not supported as nicehash is still considered as a non-coin friendly pool  (since it may have huge effect on coin value by the way it proceeds) and this ccminer release is the official zcoin release...  

new release:
 https://github.com/zcoinofficial/ccminer/releases/tag/1.1.21

hashrate on 20x is now on par with t-rex

hashrate on 2080ti 5.5MH/s
address connection problems (force the program to exit instead of leaving stuck in some bad state)

Well, that doesn't really answer my question... You can combine TT-miner, CryptoDredge and T-Rex with Ohgodapill too, heh! ;D

Your ccminer isn't available on HiveOS (yet?). I'd test it if it were... (hint)

sure you can try using OhGodApill with cryptodredge or t-rex, but you don't get any additional benefit to it while when you do it with ccminer you get for the 1080ti an additional +300kh/s (so it is very likely the same happens for the 1080... I don't have the number in mind, may-be you'll find something on zcoin discord channel, mining thread, this is where usually problem/performance are reported)

HiveOS is just a linux distribution you can probably already test it if you want by uploading the correct linux binaries (depending on the nvidia driver version used in HiveOs)

Well done!

2080 - 1920 Mhz --> 4.35 - 4.4 Mhash

Ok, gotcha. Earlier versions of TT-miner responded better to the ETHlargement pill as well. Less so now. I'll have to give your new ccminer a go somehow (my Linux knowledge is... rusty.)

If you can open a console on hiveos, you can probably use wget. (example:  wget https://github.com/zcoinofficial/ccminer/releases/download/1.1.21/ccminer-linux.cuda101 will download ccminer compiled with cuda 10.1 into the directory where you were when the command has been issued, you probably need to put it at the same place as the other ccminer release are)

Thanks for the heads up.
I'll give it a go as soon as I'm done reaping (raping?) the amazing profits given to us these days by Grin and Beam.
;D

so is the latest build the fastest miner on MTP now, havent had time to test it yet  ???

pretty much :smile: within 1% of t-rex on 2080ti and faster everywhere else ;D

 I got 1.9Mh/s  with gtx 1070  (CUDA 10)  with last version of miner . No 2.5Mh/s

TDP : 125 Watt
Core +110
Mem : No OC (Default)

...And any DevFEE  applying on this miner ?

what is the default tdp of your card (I mean the 100%) looks particularly small what you report.

All the number I report are default clock and setting... (I mean you understand, if you lower tdp, you won't get what I report and I can't report for every setting used)

ps: I did a rapid check with 83% tdp and +110 on core, you should get around 2.5MH/s indeed (my card does)
So you should probably reboot and/or _make sure_ you used the latest release:

https://github.com/zcoinofficial/ccminer/releases/tag/1.1.21

Ok, now  done.  I didn't use %100  TDP  .  (175-190 watt Average)

And What about DevFEE  ?

there is a donation of 0.25% (1 share over 400 goes to dev)

new release: https://github.com/zcoinofficial/ccminer/releases/tag/1.1.22

solved issue which were causing lost of connection and/or connection with pool, causing the miner stuck in bad state.
This problem doesn't happen anymore.

performance:

2080ti gets now 5.5MH/s

1080ti 3.55MH/s
3.9MH/s with OhGodAPill

1070 at 2.5MH/s

Does not seem to be compatible with Nicehash. In 5 minutes of running, I got 6 rejected shares. No accepted shares at all :/

Using a 1080 Ti. This is not an issue when using trex.

it isn't compatible with nicehash... fyi... you'd get more by mining xzc and selling them yourself

Looking forward to your AMD MTP miner...

he already has one: https://github.com/zcoinofficial/sgminer/releases (https://github.com/zcoinofficial/sgminer/releases)
I get 1.7 Mh/s with it on rx580 8GB, but also waiting for an update...

yes but I am planning some updates

1.1.22 is still crashing randomly for me unfortunately.

Sometimes
- miner stops completely / script loop not working because the process is still alive
- miner is flooded with stratum errors / no accepts
- miner is flooded with increasing nonce / no accepts

6x1080ti 430.39

Mining on 2miners.
Second rig is running ubuntu/t-rex and not experiencing any issues.

Thanks for your development of free ccminer

do you have a log file ? (I can probably force it crashes for the remaining issues)

getting 100% reject on nicehash

2x1080ti win10x64  driver 430.86

it does not support nicehash (yet ? requires zcoin team approval)

Not right now, but I am happy to create/provide one.
Didnt find a native --log switch though.

--debug, after you can just use >> log & (on linux)

There may be a memory leak. I see an increase of RAM and swap usage in 1.1.22. I saw the same thing in some early version.

I am still seeing Trex being faster for my 1660, 2060 and 1070 GPU's under linux.  Especially pool side.

I did a rapid check over several cycle (initialization, mining, change of block etc...) I don't see any memory leak. The amount of swap and RAM vary along a cycle however it is always freed before a new initialization. The only case which could cause subtantial increase of RAM would be running at very low difficulty where you would be solving solution faster than you send them to the pool (but again, once it is sent to the pool, the memory is freed). If it is the case, you should probably increase the difficulty

I watched a memory leak after several hours of stable mining. I'll try to make screenshots next time.

yes would be good. How big was the memory leak ?

yes, for some reason ccminer is a slower on the xx60 models (doesn't make lots of sense to me... I will probably get a sample to check this out and correct that)
For the 1070, I can't tell much on linux version, but the windows version is between faster and on par with t-rex.
What kind of speed do you get on the 1070 ? (please mention PL, core and mem... linux tends to run on a much slower mem clock this could have an impact somehow)

RAM and swap usage increases until all memory is full

was there a problem when it happens like a lost of connection ? (this really doesn't happen in normal condition)

I haven't logs and screenshots now, but very similar like here:

I think I have corrected the bulk of these problems, however for the remaining, I will force the miner to crash, so it can be restarted. I will publish an update tonight

Thanks for the development.

Can't run miner on 1066, see error message. Can't run more than 4 gpu to work....
Tested new t-rex - it works fine with 12 gpu rig and does more hashes.

I get only 1.1 Mh/s with Vega 56 and this miner

can you show me your command line or config ?
For vega, you need to use the kernel mtp_vega and use a worksize of 64

what kind of error message are you getting ?
will get a 1066 next week... in anycase for now the 1066 is faster on t-rex
4 gpu's is a little strange, you should get 6 without any problem, after you just need to run 2 instances...

screenshot:
http://oi66.tinypic.com/24qqn9i.jpg

cmd:
--device 0,1,2 --kernel mtp_vega -o stratum+tcp://zcoin.mintpond.com:3000  -u  aDn7MMYjVQqenT11VFDYHfFdwXmSTRUTak.worker -p 0,strict,verbose,d=700 --intensity 18 --worksize 64

config:
{
  "pools": [
    {  
      "url": "stratum+tcp://zcoin.mintpond.com:3000",
      "user": "aDn7MMYjVQqenT11VFDYHfFdwXmSTRUTak.worker",
      "pass": "0",
      "no-extranonce": true
    }
  ],
  "profiles": [],
  "failover-only": true,
  "algorithm": "mtp_vega",
  "device": "0,1,2",
  "intensity": "22",
  "worksize": "64",
  "temp-cutoff": "95,95",
  "temp-overheat": "90,90",
  "temp-target": "80,80",
  "gpu-memdiff": "0,0",
  "shares": "0",
  "api-mcast-port": "4028",
  "api-port": "4028",
  "expiry": "28",
  "failover-switch-delay": "60",
  "gpu-dyninterval": "7",
  "gpu-platform": "0",
  "hamsi-expand-big": "4",
  "keccak-unroll": "0",
  "log": "5",
  "no-pool-disable": true,
  "no-client-reconnect": true,
  "queue": "1",
  "scan-time": "7",
  "tcp-keepalive": "30",
  "temp-hysteresis": "3",
  "watchpool-refresh": "30"
}

looks ok to me, you probably need to let it stabilizes a bit

what MTP hashrate is normal for vega 56? vega 64?

1.7/1.8  (the best amd card for the moment for mtp is the radeon Vii which is 3.something)

new release: https://github.com/zcoinofficial/ccminer/releases/tag/1.1.23

attempt to solve problem with 6+ gpu's on 2 core/thread cpu's
force the miner to crash in case of a loss of correction (this was removed in the previous version as the problem had been solved, however, it appears some issues may remain).
therefore in case it happens again, the miner will crash so it can be restarted in a loop

I have the same problem. Solved it by running 7 instances of 1 gpu each.

If I run 7 gpu in a single instance, the memory leak fills up my 4gb ram to 99% within 15 seconds, then hangs the rig.

thanks for development.
Got 2 more crashes on 22, first one even caused 2 gpus to be "dropped" from system.
Power cycle brings em back.
https://imgur.com/Y3poYFQ
https://imgur.com/7cusMOZ

Second one I have seen for the first time.
Started running .23 just now.

My running line is

:RUN

ccminer -a mtp -o stratum+tcp://xzc.2miners.com:8080 -u XXX.XXX -p x -i 21

timeout /t 5
goto RUN

Rig is corei5/8gb

~23 mh/s

80% tdp

cudaErrorInvalidValue - can't run even 1 gpu - looks like problem with indexation ( used command -d 4 ) in 7 gpu rig. 7 gpu's runs ok but slower than t-rex

which version ? actually the indexation has been re-arranged in the latest version (however this is transparent...). The main problem is with cpu with 2 threads

.23 looking good so far

in case you still haven't noticed... this thread isn't about eth mining (and the messages you answered not about amd)

.23 running fine for 2 days now, no issues at all so far.
Just for the record rig stats
6x MSI 1080ti AERO /w10/ 430.39 / PL 80 / i5 /8gb
with pill ~23mh/s
Thank you very much for your work good sir, I will gladly leave donation enabled.

Will try .23 on ubuntu / 8x 2080 rig

awesome miner build, featured it in my latest gpu mining rig build video!
https://www.youtube.com/watch?v=RfstD1G58eU
https://i.imgur.com/sT1uE7il.png

Getting approx 2.5 MH/s per GTX 1080 with the pill. Sorry, that's not faster than TT-miner, T-rex or CryptoDredge I'm afraid.

yeah but it is cheaper ;D

which version is this ? and how much are you getting ?

GPU #5: Gigabyte GTX 1080, 2850.31 kH/s

1080Ti 3900 gigabyte aorus  PL80 core +125 mem -400 + pill
1080ti EVGA -4200 PL80 core +125 mem -400 +pill

PL-80
MEM -400
CORE - +130

Pill - yes

WIN 10

ccminer 1.1.22 OK

I have to run one program instance for each card, otherwise it falls

 - the last version can't run me, it keeps restarting

T-REX gives similar results

Nice work djm34 thx

thanks
can you try the version 1.1.23, just to see if you can run more card per instance (in principle it should be ok... actually saw that today on discord, some of the problem were disapearing with more ram... even though it isn't used)

I'd like to know how you manage 2.8 MH/s on a 1080.
What intensity?
At the settings you write (80PL, mem -400, core +130, +pill) I get 2.55-ish on 1.1.23.
That's in HiveOS btw.
Is any specific driver supposed to be faster? I'm on 418.74.

it is possible that there is a difference between linux and windows. for some reason the nominal memory frequency is usually lower than on windows

drivers - 430.86

intensity 22

5x1080ti + 1x 1080 if I start 1.1.23, the miner is still restarting ...
I can only run one GPU .... another instance, it will restart the miner


1.1.22 is OK

WIN 10, 4GB RAM, pagefile 100GB, G4400


I am sorry for my English :-)

*** ccminer 1.1.23-djm34 for nVidia GPUs by djm34 ***
    Built with VC++ 2015 and nVidia CUDA SDK 10.1

  Originally based on Christian Buchner and Christian H. project based on tpruvot 1.8.4 release
  Include algos from alexis78, djm34, sp, tsiv and klausT.
  *** News (07/06/2018): MTP algo for ZCoin

  MTP algo based on krnlx kernel

  BTC donation address: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze (djm34)
  ZCoin donation address: aChWVb8CpgajadpLmiwDZvZaKizQgHxfh5 (djm34)

[2019-07-04 08:51:09] POOL 0: xzc.2miners.com:8080 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[2019-07-04 08:51:09] Starting on stratum+tcp://xzc.2miners.com:8080
[2019-07-04 08:51:09] NVML GPU monitoring enabled.
[2019-07-04 08:51:09] NVAPI GPU monitoring enabled.
[2019-07-04 08:51:09] 6 miner threads started, using 'mtp' algorithm.
[2019-07-04 08:51:13] Stratum difficulty set to 0.125
[2019-07-04 08:51:13] GPU #4: Intensity set to 22.0938, 4587520 cuda threads number of multiproc 28
[2019-07-04 08:51:13] GPU #1: Intensity set to 22.0938, 4587520 cuda threads number of multiproc 28
[2019-07-04 08:51:13] GPU #0: Intensity set to 22.0938, 4587520 cuda threads number of multiproc 28
[2019-07-04 08:51:13] GPU #2: Intensity set to 22.0938, 4587520 cuda threads number of multiproc 28
[2019-07-04 08:51:13] GPU #3: Intensity set to 22.0938, 4587520 cuda threads number of multiproc 28
[2019-07-04 08:51:13] GPU #5: Intensity set to 21.5625, 3276800 cuda threads number of multiproc 20
cudaErrorMemoryAllocation
cudaErrorMemoryAllocation
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088
[2019-07-04 08:51:15] GPU #5: result for 00000000 does not validate on CPU!
[2019-07-04 08:51:15] GPU #5: Gigabyte GTX 1080, 1417.62 kH/s
[2019-07-04 08:51:15] GPU #5: out of memory
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088
[2019-07-04 08:51:15] GPU #5: result for 00000000 does not validate on CPU!
[2019-07-04 08:51:15] GPU #5: out of memory
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088
[2019-07-04 08:51:15] GPU #5: result for 00000000 does not validate on CPU!
[2019-07-04 08:51:15] GPU #5: out of memory
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088
[2019-07-04 08:51:15] GPU #5: result for 00000000 does not validate on CPU!
[2019-07-04 08:51:15] GPU #5: out of memory
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088
[2019-07-04 08:51:15] GPU #5: result for 00000000 does not validate on CPU!
[2019-07-04 08:51:15] GPU #5: out of memory
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088
[2019-07-04 08:51:15] GPU #5: result for 00000000 does not validate on CPU!
[2019-07-04 08:51:15] GPU #5: out of memory
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088
[2019-07-04 08:51:15] GPU #5: result for 00000000 does not validate on CPU!
[2019-07-04 08:51:15] GPU #5: out of memory
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088
[2019-07-04 08:51:15] GPU #5: result for 00000000 does not validate on CPU!
[2019-07-04 08:51:15] GPU #5: out of memory
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088
[2019-07-04 08:51:15] GPU #5: result for 00000000 does not validate on CPU!
[2019-07-04 08:51:15] GPU #5: out of memory
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088
[2019-07-04 08:51:15] GPU #5: result for 00000000 does not validate on CPU!
[2019-07-04 08:51:15] GPU #5: out of memory
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088
[2019-07-04 08:51:15] GPU #5: result for 00000000 does not validate on CPU!
[2019-07-04 08:51:15] GPU #5: out of memory
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088
[2019-07-04 08:51:15] GPU #5: result for 00000000 does not validate on CPU!
[2019-07-04 08:51:15] GPU #5: out of memory
False positive. Nonce=00000000 Hash:3a4e747477c8870403ceb34684eaf2b49692efe256005da69f8888d62d575088

--------------------------------------------------------------------------------------------------------------------------------------------

if I run one card -d 5

*** ccminer 1.1.23-djm34 for nVidia GPUs by djm34 ***
    Built with VC++ 2015 and nVidia CUDA SDK 10.1

  Originally based on Christian Buchner and Christian H. project based on tpruvot 1.8.4 release
  Include algos from alexis78, djm34, sp, tsiv and klausT.
  *** News (07/06/2018): MTP algo for ZCoin

  MTP algo based on krnlx kernel

  BTC donation address: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze (djm34)
  ZCoin donation address: aChWVb8CpgajadpLmiwDZvZaKizQgHxfh5 (djm34)

[2019-07-04 08:58:05] POOL 0: xzc.2miners.com:8080 USER xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[2019-07-04 08:58:05] Starting on stratum+tcp://xzc.2miners.com:8080
[2019-07-04 08:58:05] NVML GPU monitoring enabled.
[2019-07-04 08:58:05] NVAPI GPU monitoring enabled.
[2019-07-04 08:58:05] 1 miner thread started, using 'mtp' algorithm.
[2019-07-04 08:58:09] Stratum difficulty set to 0.125
[2019-07-04 08:58:09] GPU #5: Intensity set to 21.5625, 3276800 cuda threads number of multiproc 20
restart miner...
*** ccminer 1.1.23-djm34 for nVidia GPUs by djm34 ***
    Built with VC++ 2015 and nVidia CUDA SDK 10.1

may-be it could be due to the low ram... If you could try with 8Gb may-be it could help

sadly have to report another crash with version .23

https://i.imgur.com/UyUGC1a.png

the version will crasg in case of the error you get (instead of getting stuck) you need to put the exe within a loop, so it can be restarted

On what pool are you running ? JCTheminer (Mintpond) confirmed beginning of the week that he did do some tweak which may cause this kind of problems if you have a bad ping with that pool

it is on a script loop.
Doesnt work though, process is stuck until you click away the message.

Mining on 2miners eu server

I don't get any message to click on my pc... there is probably a setting on your computer to change

very well, I disabled Windows Error Reporting and UI.

HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting

Thanks

Please compile for windows cuda 9.2. Driver >417.35 on gpu 1070 low hashrate on some algo.

ok I have added a version of ccminer compiled with cuda 9.2

btw, this miner is optimized only for mtp, for other algo I would suggest different miners

Thank. Lower hashrate other miners and algo with driver> 417.35.

All shares rejected(boooo), win10, i5, 2x1070, 417.35, f2pool, mintpond...

nicehash isn't supported, by the way why don't you upgrade your driver ?

On the GPU 1070 there is a decrease in the hashrate on drivers newer than 417.35 on other miners and algo.

what algo ?
and can you give numbers... (in my dreams... ;D )

Equihash+Scrypt(VDS), gminer 1.47, bminer beta 15.6.7.
GTX 1070 417.35 and older = 22300 sol/s
GTX 1070 417.71-430.86 = 21000 sol/s -6%

This version of ccminer is only for MTP... If you want to mine VDS you should rather use another miner

any updates coming soon?

had another issue.
Miner was flooded with "stratrum thread error" and not qutting.
Process is running in a script loop wich ofc didnt take hold because process was still alive.

ok will had another exception...

much appreciated

MTP algorithm requires 16gb of system RAM in order to run full rig, but is the type of memory relevant? For example DDR3 DDR4?

Overnight I keep getting stratum errors now, originally the miner was fine and ran for a few days. Now it’s incredibly unreliable, any advice?

no mtp doesn't require 16Gb of ram.
it requires 450Mb (although for some system it is better to have 8Gb). It doesn't matter the type of memory which is used

hi DJM any input on my above question

& to clarify you say for some systems 8gb is better, could you explain that as well?

well say you have a 6+ GPU rig with a shitty cpu (2cores/2 thread) and 4Gb ram... you might have problem...
It will be a lot better and more stable with a 2 cores/4threads and 8Gb

Don't think it really matter for smaller rigs

for those who were asking for sgminer: :)
(no fee... too painfull to implement in sgminer  ;D )

https://github.com/zcoinofficial/sgminer/releases/tag/0.1.2

Improved hashrate on both mtp.cl and mtp_vega.cl

mtp.cl for RX5xx and RX4xx

1.69MH @1250MH/z on RX580
do not use this kernel for vega performance are ridiculous ;D

mtp_vega.cl
1.685MH @1250MHz on RX580
3.1MH/s @1350MHz on Vega 56
currently this is on my RX580  around 400kh/s faster than teamred and it run at a lower frequency (100MHz lower for some reason...)
and 70kh/s slower than teamred on vega (same frequency)
use sgminer.conf to pass kernels/pool etc...

win  ???

sgminer.zip in the release for windows.
for linux... you need to compile the source

Hi DJM wondering if you could help me troubleshoot my miner, its a stable rig, just not stable w/ your latest miner on MTP -- it continues to randomaly crash ~6-48+ hours after initiating. Added more info onto your github.

I am working on it, thanks for your help

The machine restarts at five to ten minutes intervals.
it continues to randomaly crash.
6x1070ti
ubuntu 16.04
Nvidia Driver Version: 418.56

gtx1060 running on the same version also no problem.

as I asked you on github:
what pool are you using ?
(can you try another pool and see if you have the same problem, pool with high ping are more likely to get these sort of problem... assuming it is a problem related to connection)

there shouldn't be any difference between 1070ti and 1060, the problem is probably more with your rig. From my experience, 1070ti may require somewhat better cpu to be more stable
on linux. try to check if nvidia-smi works correctly, if it is hanging, then it can be the problem with cpu

i have an error:
the launch timed out and was terminated

GTX 1080 Ti, driver - 431.36
tdp 60%, core and mem clock - stock

do you have support for nicehash yet?... teamred supports nicehash  :D :D

sorry no support for nicehash.
This is zcoin official miner and nicehash is not considered as crypto friendly (price dumping, I think anyone who was around, when nicehash got hacked, saw price of crypto and mining profitability increased... just saying ;D ), hence the miner doesn't support nicehash.
Furthemore, if you do your own calculation, you should realize that mining zcoin and selling it yourself will be more profitable to you too.
Also the upcoming new platform of nicehash is not supporting mtp either... 

new ccminer version released:

https://github.com/zcoinofficial/ccminer/releases/tag/1.1.24

better handling of miner/pool connection:
In case a pool connection problem, the miner restart the stratum_thread on the current pool.
if a failover has been set, it will restart on the failover

solve various crash problem due to pool sending empty data

sliglty improved speed on 20x cards
This release should solve most of the crash which was encountered on the previous version.

may-be try the new version. However if it is a launch time out, it is probably more related to memory or some bad communication with the gpu or gpu somehow hanging.
60% tdp seems a little low...

on what system are you ?

I mine eight different pools.  nicehash is the most profitable of the pools i mine for  mtp.  I mine the most profitable algo.  In order for me to mine mtp as you suggest, then mtp has to be more profitable on all coins on all exchanges all the time...  which isn't the case.

granted you don't like nicehash, but you are removing the choice the user can make.   I'll stick with the other miners that do support a choice of other pools such as nicehash.

and i was part of the hacked nicehash also... they are paying back. also thier fees are put into my calculations, and it's still more profitable for me.

but i understand.  You won't support nicehash.  I won't bring it up again and i won't comment in your thread anymore.

Windows 10 LTSB. i use ver 1.1.23

may-be try the latest version 1.1.24 (released today)
how much memory and what cpu is there on your machine ?

your choice...  and sgminer doesn't have a dev fee, so...  up to you to chose to pay all the fee along the line you chose or mostly none ;D
regarding nicehash, it can't be profitable to miner, since people who buy coins through nicehash, do it that way to get their coin below the price they would get on an exchange.
Which basically cause the value of the coins to go down on exchange.
So really you can't say it is more profitable on nicehash, because in the way it works it isn't true.
And selling yourself your coin on an exchange allows you to sell when it is more profitable for you to sell.

I'm not so negative about Nicehash, they provide an open market with willing participants on both sides
with them, as brokers, in the midle taking a cut. The effects on the overall crypto market are due to the actions of
their users more than their presence. However, they do tend to act like the elephant in the room at times by
making their own rules. That attitude never seemed to hurt Microsoft despite the anti-Microsoft cults.

The main market effect of Nicehash is the same as any auto-exchange pool. It tends to hurt altoins due
to persistent dumping for BTC. But it creates opportunities at the other end where altcoin specuators can
pick them up more cheaply when the pools dump them.

But I digress.

What is this Nicehash support issue? Did they do something stupid that requires specific miner support?

why source code dated 20 may 2019

 ;Dthe code is kept hidden for the moment...

they require some modifications in stratum (in xtranonce I think)

new release  https://github.com/zcoinofficial/ccminer/releases/tag/1.1.26

* rearrange how the cards are assigned to threads. this should correct the issue described here in issue #4
the previous release (not announced here) were correcting:
* correct more crash issues...
These crash were occurring when the pool stop sending data or is unable to send data.

When this happen, the stratum thread is restarted.
In case of vardiff, the last difficulty is used when the thread is restarted.

new ccminer release: https://github.com/zcoinofficial/ccminer/releases/tag/1.2.0

* better handling of eventual packet losses when the connection to the pool is less than optimal
=> no more pool disconnect

new sgminer release:  https://github.com/zcoinofficial/sgminer/releases/tag/0.1.3

improved connection between pool and miner in case of high latency connection

win 7 for nvidia is very slow not win 10 how come ?

current cuda version are developped around win10, also it is 64bit code which has always been slower (for some reason) on win 7

According to my personal observations, windows 7 work with miners much better than windows 10. For example, grimm mining, the makeup of my 6 gigabyte video cards is not enough for mining on windows 10, and on windows 7 everything works fine. Windows 7 consumes less video memory.

I'm having a hell of a problem getting ccminer to work.

CPU: Ryzen7 1700
OS: Ubuntu 18.04
Cuda: 9.1 from repo
GPUs: GTX-1080ti, GTX-970
Source: https://github.com/zcoinofficial/ccminer/archive/1.2.2.tar.gz
Makefile: compute 5.2, 6.1  (removed 7.5)

There's nothing unusual with my setup, it works fine for other ccminer forks.

ccminer-1.2.2 segfaults on stratum thread startup. It looks like the URL wasn't set.
Previous versions have other problems.

The stratum crash noted above is fixed in v1.2.3,  and the 1080ti hashes fine and
submits valid shares. Thanks.

Edit2: Nevermind the following, the 970 ony has 4 GB mem.


But ccminer exits on GTX970. Makefile has compute 5.2 so I assume Maxwell is supported.


I tried setting a lower intensity but it always reported the same intensity and threads. Not sure if it's
related to the crash or a seperate issue.

Anything I can do to help?

Edit: tried the Windows version, same problem. It looks like Maxwell isn't supported after all.

Any plans to optimize for rtx cards?

yes indeed that problem has been fixed in the latest version.
Maxwell is supported as long as there are more than 4Gb of vram. So could in principle concerns some titan model (and stuff like that).
However performance aren't stellar, and cheaper Pascal/Turing model will most likely beat these one.

Edit: perhaps the following can be ignored for now as I was using v1.2.3. I'll upgrade to
v1.3.1 and see how it goes.

---

I had 2 instances of ccminer-1.2.3 being killed by the kernel.

The only message to the console is "Killed".

The first time on Windows with a gtx 1070, the second was on Linux with a 1080ti.

There is a possibility that ccminer is a victim of the OOM killer. I have experience
where the process denied memory was not the source of the leak. Considering
the two incidents occurred on different OSes makes that unlikely. The only
other common application is Firefox so that is the only plausible cause of the leak
assuming ccminer was in fact a victim.

The only other common factor is both were using Pascal GPUs with sm6.1 but this doesn't look
like a GPU issue to me (I'm certainly not a Cuda expert)

The problem is very intermittant (only happened to me twice) and isn't realated to session length.
I have had sessions run for over 24 hours on both systems but one of the two incidents happened
after only 14 minutes run time. That is not a s low leak.

There appears to be a trigger that requires a rare set of circumstances, but once triggered memory is
exhausted quickly.

It would be reasonable to conclude the memory issue is related to code specific to MTP. I haven't seen
this with any other forks of ccminer I've used.

The infrequent nature of the problem and lack of precise coonnection between the trigger event and the
termination of the process make it virtually impossible to troubleshoot.

Then again the infrequent nature makes the problem less serious. But I thought I'd document what I could
just in case my analysis leads to some inspiration.

Edit Nov 7:

I have seen one instance of "killed" on v1.3.1 Linux.
I now suspect the trigger may not be ccminer, but another application that pushes mem over the edge.
I also suspect the edge is close because of the 45-49 GB VM used by ccminer.
The amount of VM apparently used greatly exceeds the amount of VM in my system: 16G RAM + 2 GB swap file.

Edit Nov 11:

Another revision. I have seen the problem with v1.3.1 on Windows, no console error message but a pop-up
saying essentially the same thing.

The high VM usage seems to be a non-issue as it is also observed using tpruvot fork with different algo.

Current speculation is an intermittant leak, likely in conditional code related to MTP.

sorry for the delay in replying (haven't checked that post in a while).
'Killed' usually means that the program was killed by the system as the system was running out of memory (ie: memory leak).
These problem have been addressed recently, using the most recent release on github should solve that issue.

2Gb of swap file might be a bit tight, on mtp, each gpu requires at least 4.5Gb of swap per gpu.
The high VM usage is a consequence of 2 nvidia drivers releases which were released around that time (roughly), you need to upgrade to the most recent drivers where this issue hasn't been noticed.

im on ubuntu 16.04, 6x 1080ti, ccminer 1.3.1, nvidia driver 440.44 and seeing 100% cpu (i5 quad)

edit:
I sorta fixed it for now by setting --cpu-affinity=0x1
no hit on hash rate

I have been trying your version of CCMiner for a bit now.  Normally I use Trex as many do, but thought it does not hurt to give it a try.  I won't know too much for an hour or 2 while the switch stabilizes and hash levels.  I do have some questions though, so I figured maybe I should ask here if that is alright.

I mine with a partner (my oldest nephew) and he is in a different part of the country.  The last 3 days we have been solo mining Zcoin at 2Miners.com.  We jump around like most miners do I suppose, but for Zcoin we always comeback to 2Miners.  Anyway, this question is specific to solo mining Zcoin and Luck. In a nutshell, my partner has found 3 blocks in these 3 days, and I have not found any.  I am actually hashing higher with about 60Mh/s and he is about 45Mh/s. Since no ones luck is that good, with less to work with. I am trying to figure it out.  Our equipment is the same, he just has less GPUs then me.  We use the same mining software (Minerstat) with as I said, the same hardware.  The single difference I can think of is networking.  He is on super fast full fiber optic at 250 Mb/s up and down.  I am on 100 Mb/s down and only 10 Mb/s up.  Since sending shares is what a miner does, his share must move like lightning and my like a slow freight train.  I think this is the reason.  What is your thoughts.

This other question I hope is right up your alley. Would you know if there is any possibility of integrating multiple GPUs where mining software sees multiple GPUs cores as if a single entity.  My though here is if that were possible, there should be a great advantage solo mining as the processing time per share should be divisible by the number of GPUs in the cluster, not considering difficulty level changes.  I admit, this is out of my somewhat shallow experience in shared computing using data/task parallelism, but if it were possible, I would have to think it may actually be quit significant in all of mining as well, not just solo mining.

That's about it.  Thanks for providing and working to improve your version of CCMiner to us miners.

-Rodger

100mb/s is good for mining  i not think it different about 100-250/mb in  this case is not about internet speed maybe you try other port(or choose sever to near you) in 2miners.com

mining need network stable go to check how long ping to sent to server and it have reject or not.

 

i hope this can help you.

False assumption. Just because you didn't ever win the loterry it doesn't mean no one has.

There is a whole branch of math that can tell you exactly the odds of what happened.

As long as the miner submits valid shares at a normal rate (pooled mining) you're in the game, just unlucky.

Hi,

Below are the error from my log file. FYI i am using GTX 1050 4g(This is my spare GPU solely use for mining purpose only), using the latest GPU drivers(Also tried rollback many previous drivers up to drivers released in 2019) and Win10 are also updated as well. And i'm mining from a 6 core laptop with 20gb of ram.


*** ccminer 1.3.0-djm34 for nVidia GPUs by djm34 ***
    Built with VC++ 2015 and nVidia CUDA SDK 10.1

  Originally based on Christian Buchner and Christian H. project based on tpruvot 1.8.4 release
  Include algos from alexis78, djm34, sp, tsiv and klausT.
  *** News (07/06/2018): MTP algo for ZCoin

  MTP algo based on krnlx kernel

  BTC donation address: 1NENYmxwZGHsKFmyjTc5WferTn5VTFb7Ze (djm34)
  ZCoin donation address: aChWVb8CpgajadpLmiwDZvZaKizQgHxfh5 (djm34)

[2020-07-26 14:58:00] POOL 0: 178.63.61.138:55486 USER xxxxxxxxxxxxxxWALLETxxxxxxxxxxxxxx.F6QDXC9 -s 30
[2020-07-26 14:58:00] Starting on stratum+tcp://178.63.61.138:55486
[2020-07-26 14:58:00] NVML GPU monitoring enabled.
[2020-07-26 14:58:00] NVAPI GPU monitoring enabled.
[2020-07-26 14:58:00] 1 miner thread started, using 'mtp' algorithm.
[2020-07-26 14:58:04] MESSAGE FROM SERVER: Welcome to the European Zcoin stratum.
[2020-07-26 14:58:04] Stratum difficulty set to 0.03125
[2020-07-26 14:58:05] MESSAGE FROM SERVER: Optimizing difficulty may take several minutes.
[2020-07-26 14:58:11] GPU #0: Intensity set to 19.5625, 819200 cuda threads number of multiproc 5
cudaErrorInvalidValue
Sleep 3000 msec

Appreciate any kind soul help. Thks

You need a GPU with more than 4 GB.

So most other cards will work? ...

As long as 4GB RAM is available for processing?

#crysx