Topic: CryptoDredge 0.27.0 — CUDA Miner - page 12. (Read 86186 times)

I have 5,5 on C29 in avg. Gminer gives 7.

After updating to 0.17 lyra2rev3 algo stopped working on Nicehash, had to roll back to 0.16.2

CryptoDredge -a cuckaroo29 -o stratum+tcp://grin29.f2pool.com:13654 -u . -p x

CryptoDredge 0.17.0 added to https://www.minermonitoring.com/



Join our discord https://discord.gg/aGGaeqq



also, you can check the speed of the miner on different rigs using the benchmark page: https://minermonitoring.com/benchmark

Need example for GRIN???

Is there an example of a bat file GRIN coin for f2pool ?

here's my result https://i.imgur.com/ig2stBm.png (my rig operates around 14.7mh.sec without using teamviewer) i haven't tried maximum core oc (without any memory oc) maybe it's has even higher hashrates without altering miner stability, now i'm mining gricoin on f2pool, maybe later i switch to mtp algo again on mintpool, it has lower fee (3% VS 0.9%) as well as european server VS chinese with lower ping, lower payment threshold (3 grins vs 1 zcoin), mtp algo needs around 2-3gb less virtual memory per one 8-11gb nvidia GPU than c29 algo and at the moment according to whattomine miner calculator zcoin pays more in bitcoins than grincoin with c29 algo (using bminer), electricity costs and gpu temps (well mining gpu with mtp algo maybe 2-3 degrees celcius warmer than grin using more or less same oc and TDP settings) should be more or less same using TDP 70% and some memory and core oc, i used default intensity -6, stability was perfect without any miner resets and driver crashes, i haven't seen any hashrate increases either for mtp nor c29 algos later, maybe it's highest that miner devs can achieve at the moment without breaking stability, or they need more time to make more optimizations, also zcoin price is more stable than grincoin and there's less price fluctuations at the moment

well i did some more oc on core i got following results:

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

maybe i could achieve even higher results with more oc on core (memory oc +500 gives very low hashrate increase as well as using pill, maximum around 0.5mh/sec in total) i think around 13.85mh/sec is achievable
lol with intensity -8 i got 14mh/sec, pretty good results:

https://i.imgur.com/8epHBCx.png

maybe it's better to use higher intensity (8 instead of default 6) + only core oc (memory oc 0 + pill) with intensity 8 i think 14.10-14.15mh/sec is easily achievable with maximum stable core oc and TDP 70% in that case average daily income would increase from 0.00115-0.0012 bitcoin to 0.0012-0.00125 and temp increase should be only 1-2 degrees Celcius
so it seems that maximum intensity for CD miner is 8 and not 6 (at least for mtp algo), when i set intensity -9 it run only on 8, as for miner droping hashrate after dev fee i think that it calculates average hashrate with dev fee time as well, so average hasrate is lower after dev fee ends, but in reality it's same than before dev fee started, more important is pool average daily hashrate

it would be nice if CD had C29-31 algo support as well for mining grincoin

lower intensity on at least one card to reduce system lag or overtaxing of the os
you can set the intensity like this    -d 0,1  -i 3,6        a batch file using 2 cards with diff intensities  may look like the one below

CryptoDredge  -a skunk  -d 0,1  -i 3,6 -o stratum+tcp://us.bsod.pw:2560 -u KRJdqqsTebT66sUj7T1duP64AB6pP7rQfj -p m=solo

or 10 cards may look like this

t-rex -a skunk  -d 0,1,2,3,4,5,6,7,8,9   -i 18,20,20,20,20,20,20,21,21,21  -o stratum+tcp://us.bsod.pw:2560 -u KRJdqqsTebT66sUj7T1duP64AB6pP7rQfj -p m=solo

remember the more cards the more ram youl need. for 10 gtx 1080 tis = 88gigs ram plus your ram add the total  = in vram to reduce possibility of crashing.

cheers i hope this helps

0.16.2 on MTP algo working bad, rigs everytime restarting and hang out.

on 0.16.1 i'm using 30 seconds timeout and i never saw that error.
it only happen on 0.16.2 with 300 Sec (5 min) timeout, and i tried 1200 (20 min) and still getting the error
i'll just keep using 0.16.1

The default timeout is 300. Try to increase it by --timeout e.g.: --timeout 3000

thanks for new update

this is the 4th time i get this error on 0.16.2
while i'm having my other rig working fine on 0.16.1 (same algo same pool)
algo mtp

v0.16.2 released

• Support GINcoin on X16RT algorithm
• Fix P2Pool for Lyra2REv3
• Add CNFastv2 (Masari and Stellite) algorithm
• Add CNSuperFast algorithm
• Other minor fixes

Download: https://cryptodredge.org/#download
Mirror: https://github.com/technobyl/CryptoDredge/releases/tag/v0.16.2

Happy mining!
The CryptoDredge Team 🐰

Ok, ty, trying it. So far with 4x1070ti and 6x1070 console reports 17.5mh/s. +125 core and power limited to 60% (power isn't exactly cheap at my place).

Core

Hence I'm quite new to MTP: what are the recommended OC settings, should I OC Mem or rather Core?

Ok, so it crashed again... this time, CMOS indicated it shut down because of surge protection. I turned that off. I wonder if that's been the culprit all along.

Back to running the test. Now I'm absolutely *determined* to get this to stabilized.

Without a waterblock, getting 58c while mining is *stellar* in my experience, especially considering the OC you have on it. I'd be very happy with those temps.

mine temp 58 @ fan speed 85-88, i'll try to test lower mems & core