Topic: CryptoDredge 0.27.0 — CUDA Miner - page 14. (Read 85990 times)
CD is not bugged. Reduce your overclocking and CD will run 100% stable.
MTP algo is incredibly unstable.. You're going to put an algo out there with lots of bugs and then charge 2%? Come on bruh...
+1
I have a 12x1080ti linux rig mining during a hole year different algos with a lot of miner software without problem.
Cryptodredge 0.16, with CUDA 10.0 and driver version 410.78 always crashes after 14-16 hours of MTP mining (default parameters).
Regards.
Same here, have 12x 1080ti Rig running on server PSU-s (2400w as main + 2x 750w) on Linux (SMOS), for the past year this rig mined ether and more recently ravencoin, went on for weeks without restarts. With CD this rig crashes and restarts once every 40 min. I have even downclocked memory, still no change.
I have 8 other rigs, with 1070ti-s and 1070-s, those are stable for past 24 hours.
Same problem with my 9x RIGS !!! all of them with 8x 1080s have problem with CD... miner restarts , crushes . This rigs mined with no problem 1 year all kind of diferend algos with no problems. And now CD with MTP algo problems all the time !!! The miner is buged !!! FIX IT ASAP !!!
Is there a way to make MTP require only 4gb vram? I'd wish to use P104 with this miner on MTP.
my GPU's work best at +500 memory both dagger hashimoto and MTP algo using pill, with memory 1000 they lose stability and crash, and i prefer to use TDP 70%, never had any problems on any other algos as well, both memory or core intensive, mining since last may and they're rock stable, this algo give quite good profit even at those settings, around 0.0013-0.0014 bitcoin per day, let's see how long those kind of incomes last, grin and beam coins should do good as well
CD 0.16.1 cuda 10 works more than fine on my rig using MTP algo:
memory +500 and some core oc + pill with TDP 70%, it uses around 26gb pagefile (just 4gb ram and celeron G1840), i use mintpool, it's rock stable:
memory +500 and some core oc + pill with TDP 70%, it uses around 26gb pagefile (just 4gb ram and celeron G1840), i use mintpool, it's rock stable:
u should be getting more on 1080s
core+150 & power 80% & mem +1000 i'm getting ~2780KH/S (MSI GTX 1080)
CD 0.16.1 cuda 10 works more than fine on my rig using MTP algo:
memory +500 and some core oc + pill with TDP 70%, it uses around 26gb pagefile (just 4gb ram and celeron G1840), i use mintpool, it's rock stable:
memory +500 and some core oc + pill with TDP 70%, it uses around 26gb pagefile (just 4gb ram and celeron G1840), i use mintpool, it's rock stable:
Heloo !!
Is the software optimized for Maxwell architecture (GTX 980 TI) or only Pascal (GTX 1070, etc...) ?
That's how it looks with me:
Hashing in other algorithms 980 TI and 1070 is similar.
v0.16.1 released
- Fix MTP issue related to many rejected shares
Is the software optimized for Maxwell architecture (GTX 980 TI) or only Pascal (GTX 1070, etc...) ?
That's how it looks with me:
Code:
[19:50:46] INFO - GPU0 Gigabyte GTX 1070 : 2003KH/s (Avr 1689KH/s) : 16,20KH/W : T=54C Fan=26%
[19:50:46] INFO - GPU1 Gigabyte GTX 1070 : 2003KH/s (Avr 1978KH/s) : 17,88KH/W : T=53C Fan=25%
[19:50:46] INFO - GPU2 Gigabyte GTX 980 Ti : 260,7KH/s (Avr 257,8KH/s) : 2353H/W : T=58C Fan=31%
[19:50:46] INFO - GPU3 Gigabyte GTX 980 Ti : 253,5KH/s (Avr 250,3KH/s) : 1994H/W : T=60C Fan=31%
[19:50:46] INFO - GPU4 Zotac GTX 980 Ti : 252,1KH/s (Avr 249,9KH/s) : 2013H/W : T=58C Fan=0%
[19:50:56] INFO - 12/0 Accepted : diff=0.0993187 : 4431KH/s
[19:50:46] INFO - GPU1 Gigabyte GTX 1070 : 2003KH/s (Avr 1978KH/s) : 17,88KH/W : T=53C Fan=25%
[19:50:46] INFO - GPU2 Gigabyte GTX 980 Ti : 260,7KH/s (Avr 257,8KH/s) : 2353H/W : T=58C Fan=31%
[19:50:46] INFO - GPU3 Gigabyte GTX 980 Ti : 253,5KH/s (Avr 250,3KH/s) : 1994H/W : T=60C Fan=31%
[19:50:46] INFO - GPU4 Zotac GTX 980 Ti : 252,1KH/s (Avr 249,9KH/s) : 2013H/W : T=58C Fan=0%
[19:50:56] INFO - 12/0 Accepted : diff=0.0993187 : 4431KH/s
Hashing in other algorithms 980 TI and 1070 is similar.
Each algorithm will hash differently.
I'm losing hashrate after devfee session on MTP. after devfee session hashrate is down about 3.5% right after user session begins, about 100 blocks later hashrate is still about 2.2% lower than before devfee..... what is going on? I have to resrtart miner to get hash back up to normal
you're not losing any hashrate. the miner shows you your effective hashrate without dev fee time. no, that doesn't make sense, i was coming here to report the same problem, to find that u guys already talking about it.
dev fee sessions starts for 1-2 minutes many times, idk may be like 2 minutes for each 100 minutes online (2% for mtp).
u can see that on the miner (dev session starts) and 1-2 minutes after it stops and followed by ( user session started)
but after this KH/s drops from 2800 to about 2600 and keep rising up by 1kh untill it reach about 2670 , and it keep on that rate till the next dev session
What they are saying is you're looking at an average hashrate in the miner and when it cuts out for the dev session, of course that number would appear to drop. Given enough time running, the reported hashrate in the miner should normalize.
The problem I see isn't the hashrate... it's the shares submitted. I notice that it becomes sporadic after a dev fee session.
Heloo !!
Is the software optimized for Maxwell architecture (GTX 980 TI) or only Pascal (GTX 1070, etc...) ?
That's how it looks with me:
Hashing in other algorithms 980 TI and 1070 is similar.
v0.16.1 released
- Fix MTP issue related to many rejected shares
Is the software optimized for Maxwell architecture (GTX 980 TI) or only Pascal (GTX 1070, etc...) ?
That's how it looks with me:
Code:
[19:50:46] INFO - GPU0 Gigabyte GTX 1070 : 2003KH/s (Avr 1689KH/s) : 16,20KH/W : T=54C Fan=26%
[19:50:46] INFO - GPU1 Gigabyte GTX 1070 : 2003KH/s (Avr 1978KH/s) : 17,88KH/W : T=53C Fan=25%
[19:50:46] INFO - GPU2 Gigabyte GTX 980 Ti : 260,7KH/s (Avr 257,8KH/s) : 2353H/W : T=58C Fan=31%
[19:50:46] INFO - GPU3 Gigabyte GTX 980 Ti : 253,5KH/s (Avr 250,3KH/s) : 1994H/W : T=60C Fan=31%
[19:50:46] INFO - GPU4 Zotac GTX 980 Ti : 252,1KH/s (Avr 249,9KH/s) : 2013H/W : T=58C Fan=0%
[19:50:56] INFO - 12/0 Accepted : diff=0.0993187 : 4431KH/s
[19:50:46] INFO - GPU1 Gigabyte GTX 1070 : 2003KH/s (Avr 1978KH/s) : 17,88KH/W : T=53C Fan=25%
[19:50:46] INFO - GPU2 Gigabyte GTX 980 Ti : 260,7KH/s (Avr 257,8KH/s) : 2353H/W : T=58C Fan=31%
[19:50:46] INFO - GPU3 Gigabyte GTX 980 Ti : 253,5KH/s (Avr 250,3KH/s) : 1994H/W : T=60C Fan=31%
[19:50:46] INFO - GPU4 Zotac GTX 980 Ti : 252,1KH/s (Avr 249,9KH/s) : 2013H/W : T=58C Fan=0%
[19:50:56] INFO - 12/0 Accepted : diff=0.0993187 : 4431KH/s
Hashing in other algorithms 980 TI and 1070 is similar.
I'm losing hashrate after devfee session on MTP. after devfee session hashrate is down about 3.5% right after user session begins, about 100 blocks later hashrate is still about 2.2% lower than before devfee..... what is going on? I have to resrtart miner to get hash back up to normal
you're not losing any hashrate. the miner shows you your effective hashrate without dev fee time. no, that doesn't make sense, i was coming here to report the same problem, to find that u guys already talking about it.
dev fee sessions starts for 1-2 minutes many times, idk may be like 2 minutes for each 100 minutes online (2% for mtp).
u can see that on the miner (dev session starts) and 1-2 minutes after it stops and followed by ( user session started)
but after this KH/s drops from 2800 to about 2600 and keep rising up by 1kh untill it reach about 2670 , and it keep on that rate till the next dev session
I'd love a command that tells the miner to mine the Dev fee for a 24 hour period all at once. Every miner that I've ever used that splits out for a dev fee always suffers what appears to be a submitted share decline after it returns to the user session. It will just about get back to speed and then goes right back into the dev fee schedule.
Also, a command to either lengthen the interval of GPU Info or to subdue it altogether would be splendid.
Perhaps, if you could quantify a "lifetime member" fee, one that would "unlock" the miner to be free from the dev session, that might be a thing too.
Great miner! Keep up the great work!
Also, a command to either lengthen the interval of GPU Info or to subdue it altogether would be splendid.
Perhaps, if you could quantify a "lifetime member" fee, one that would "unlock" the miner to be free from the dev session, that might be a thing too.
Great miner! Keep up the great work!
ok makes sense
I'm losing hashrate after devfee session on MTP. after devfee session hashrate is down about 3.5% right after user session begins, about 100 blocks later hashrate is still about 2.2% lower than before devfee..... what is going on? I have to resrtart miner to get hash back up to normal
you're not losing any hashrate. the miner shows you your effective hashrate without dev fee time. 
I'm losing hashrate after devfee session on MTP. after devfee session hashrate is down about 3.5% right after user session begins, about 100 blocks later hashrate is still about 2.2% lower than before devfee..... what is going on? I have to resrtart miner to get hash back up to normal
what version you use?
CryptoDredge 0.16.1 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
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
My rig has CUDA 9.1 installation. (HiveOS) I want to upgrade it to CUDA 9.2 installation. I used the command “nvidia-driver-update”. But it is the same. How could I update to CUDA 9.2 ?
The required CUDA version is 9020 or later (current is: 9010)
Rig shows Driver Version: 390.59
The required CUDA version is 9.1
The required CUDA version is 9020 or later (current is: 9010)
Rig shows Driver Version: 390.59
The required CUDA version is 9.1
Here you go....but I'm not sure about HivesOS.
https://developer.nvidia.com/cuda-92-download-archive
My rig has CUDA 9.1 installation. (HiveOS) I want to upgrade it to CUDA 9.2 installation. I used the command “nvidia-driver-update”. But it is the same. How could I update to CUDA 9.2 ?
The required CUDA version is 9020 or later (current is: 9010)
Rig shows Driver Version: 390.59
The required CUDA version is 9.1
The required CUDA version is 9020 or later (current is: 9010)
Rig shows Driver Version: 390.59
The required CUDA version is 9.1
MTP algo is incredibly unstable.. You're going to put an algo out there with lots of bugs and then charge 2%? Come on bruh...
Open Afterburner or similar and check why your rig is unstable. Very easy to address... CD is running smooth without any problems.
Only the 5% rejected rate is a little bit arrrgh, but I thing CD will work this out.
to reduce the rejects, change to fix diff, d=512 or d=1024
(but CD is still unstable on 1080ti, while stable on 1070)
surely CD team will fix problem with 1080ti soon
v0.16.1 released
Please add support for failover pools in command line
Hello CryptoDredge,
Thanks again for the great updates. We have been enjoying mining a variety of hot new coins on PiMP OS, and your API is rock solid.
Here is an example of our miner.farm stats application using cryptodredge:
Getting 740 to 790 h/s on the example config for cryptodredge in PiMP OS. Always a decision whether to update or go for those 100+ day uptimes Stability is the name of the game for the best profits - less labor costs. So thank you for putting stability first!
~ melt
getpimp.org | miner.farm
Thanks again for the great updates. We have been enjoying mining a variety of hot new coins on PiMP OS, and your API is rock solid.
Here is an example of our miner.farm stats application using cryptodredge:
Getting 740 to 790 h/s on the example config for cryptodredge in PiMP OS. Always a decision whether to update or go for those 100+ day uptimes
Stability is the name of the game for the best profits - less labor costs. So thank you for putting stability first!~ melt
getpimp.org | miner.farm
Jump to: