9.5 :
New X17 algorithm
New BitCore algorithm
Fix Exosis algorithm
Fix several bugs
Topic: CryptoDredge 0.27.0 — CUDA Miner - page 29. (Read 86186 times)
CryptoNightHeavy not work
Working well on my 1060 with 0.9.5 & 411.63.
CryptoNightHeavy not work
Just make a couple test for my 1030 (core +200, mem +750). Cryptodredge 0.9.5 cuda 9.1 got 177 H/s on cryptonight v8 with overclock.
So, 0.9.3 supports v8, can anyone share hashrate for gtx card?
Here is result for my gtx 1060 : 560 H/s on cryptonight v8, windows 7 x64 cryptodredge 0.9.3, 7,5 H/w (about 75 W consuption) 
WOOT! after 2 days of pulling my hair out and f&%*ing around, I have solved my problem. It was power distribution. The rig I was testing on has 1 750W power supply and a secondary 1200W server supply. I was stupidly powering a 1080 and 2 x 1070s on the 750W supply and only 1 x 1070 on the secondary. No wonder it was rebooting!
So now I am a Cryptodredge convert. Thank you Cryptodredge devs for a really great miner. I have an improvement of at least 20% mining cryptonight-heavy algo.
1070 cryptonight-heavy XMR-Stak 720-760 h/s CryptoDredge 870-900 h/s
1080 cryptonight-heavy XMR-Stak 670-690 h/s CryptoDredge 805-810 h/s
I can also easily run a cpu miner concurrently (which I wanted to achieve because XMR-Stak uses both CPU and GPUs) and I get another 150 h/s.
The whole rig measures around 500W. So that is about 3.6 kh/s for 500W. I wonder if those AMD vega miners can do that well? Also, XMR-Stak has a 2% dev fee (unless you compile yourself) and CryptoDredge is only 1%.
I think CryptyoDredge must officially be the best cryptonight variants miner for Nvidia GPUs. Thanks again devs - your miner is awesome!
So now I am a Cryptodredge convert. Thank you Cryptodredge devs for a really great miner. I have an improvement of at least 20% mining cryptonight-heavy algo.
1070 cryptonight-heavy XMR-Stak 720-760 h/s CryptoDredge 870-900 h/s
1080 cryptonight-heavy XMR-Stak 670-690 h/s CryptoDredge 805-810 h/s
I can also easily run a cpu miner concurrently (which I wanted to achieve because XMR-Stak uses both CPU and GPUs) and I get another 150 h/s.
The whole rig measures around 500W. So that is about 3.6 kh/s for 500W. I wonder if those AMD vega miners can do that well? Also, XMR-Stak has a 2% dev fee (unless you compile yourself) and CryptoDredge is only 1%.
I think CryptyoDredge must officially be the best cryptonight variants miner for Nvidia GPUs. Thanks again devs - your miner is awesome!
Nice. Yup CD seems to be the best right now for Nvidia GPUs on CN.
2 x Vegas can do 4+ kH/s @ 350w on cn and 3.1 Kh/s @ 340w on cn-heavy. An RX 580 8gb does 1.1-1.18 KH/s at 110w on CN-Heavy.
DAMN! I'm really disappointed 
This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy.
I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s.
I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400).
XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s
..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!!
WOOT! I said to myself - I've found my new favourite miner.
BUT as always seems to be the case it was too good to be true.
I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks.
I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak.
I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence.
Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out.
Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3.
This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy.
I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s.
I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400).
XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s
..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!!
WOOT! I said to myself - I've found my new favourite miner.
BUT as always seems to be the case it was too good to be true.
I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks.
I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak.
I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence.
Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out.
Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3.
xmr-stak 2.5.1 vs CD 0.9.2 on cnv7 (3300 vs 3580)
https://imgur.com/a/B9HubsI
this is what optimized xmr-stak can do in cnv8 (3200). 1080 Ti, 1080, 1070 Ti and 1070.
https://i.imgur.com/8e4cVeD.jpg
OK so what I can see from your info is that you have core clocks lowered considerably and memory clocks as high as possible.
I might try that but it seems that no matter what i do, XMR-Stak is stable and keeps running but with a much lower hash rate than CryptoDredge - but when I run CryptoDredge, even with all GPUs at factory settings, my system reboots.
I was wondering, does the CD watchdog cause reboot or just stop the miner.
I was also wondering if I should just install Ubuntu and run CD in linux to see if that stops the goddamn rebooting.
OK so something occurred to me. I was originally using this machine for gaming so the display was coming from the 1080. I have now gone into bios, activated the onboard graphics and I'm using that for display, so now all the GPUs are just running cryptodredge and the 1st GPU isn't trying to mine and provide display simultaneously.
I hope this may solve my reboot problems but I will let everyone know. Rookie mistake maybe? I know that when I used to mine ETH I always had onboard video disabled and used the 1st GPU for display and mining but I don't remember the rules for Nvidia and custom versions of ccminer like this one.
WOOT! after 2 days of pulling my hair out and f&%*ing around, I have solved my problem. It was power distribution. The rig I was testing on has 1 750W power supply and a secondary 1200W server supply. I was stupidly powering a 1080 and 2 x 1070s on the 750W supply and only 1 x 1070 on the secondary. No wonder it was rebooting!
So now I am a Cryptodredge convert. Thank you Cryptodredge devs for a really great miner. I have an improvement of at least 20% mining cryptonight-heavy algo.
1070 cryptonight-heavy XMR-Stak 720-760 h/s CryptoDredge 870-900 h/s
1080 cryptonight-heavy XMR-Stak 670-690 h/s CryptoDredge 805-810 h/s
I can also easily run a cpu miner concurrently (which I wanted to achieve because XMR-Stak uses both CPU and GPUs) and I get another 150 h/s.
The whole rig measures around 500W. So that is about 3.6 kh/s for 500W. I wonder if those AMD vega miners can do that well? Also, XMR-Stak has a 2% dev fee (unless you compile yourself) and CryptoDredge is only 1%.
I think CryptyoDredge must officially be the best cryptonight variants miner for Nvidia GPUs. Thanks again devs - your miner is awesome!
0.9.4 is available (windows version for now, linux coming soon).
Added bcd, c11, exosis and polytimos.
Improved performance of some algorithms:
Allium +3-5%
Phi1612 +16-20%
Skunk +18-25%
Added bcd, c11, exosis and polytimos.
Improved performance of some algorithms:
Allium +3-5%
Phi1612 +16-20%
Skunk +18-25%
Thanks again to the CryptoDredge team for the great work on 0.9.3 and getting the monero v8 support in right away for us! We also appreciate the great support in your discord and the solid API support so we can get the stats to miner.farm. The miner is rock solid and runs for weeks and hopefully months 
Hope that the support of all of the PiMP OS rigs keeps you turning out more updates all the time!
melt,
getpimp.org | miner.farm
Hope that the support of all of the PiMP OS rigs keeps you turning out more updates all the time! melt,
getpimp.org | miner.farm
OK so something occurred to me. I was originally using this machine for gaming so the display was coming from the 1080. I have now gone into bios, activated the onboard graphics and I'm using that for display, so now all the GPUs are just running cryptodredge and the 1st GPU isn't trying to mine and provide display simultaneously.
I hope this may solve my reboot problems but I will let everyone know. Rookie mistake maybe? I know that when I used to mine ETH I always had onboard video disabled and used the 1st GPU for display and mining but I don't remember the rules for Nvidia and custom versions of ccminer like this one.
I hope this may solve my reboot problems but I will let everyone know. Rookie mistake maybe? I know that when I used to mine ETH I always had onboard video disabled and used the 1st GPU for display and mining but I don't remember the rules for Nvidia and custom versions of ccminer like this one.
historically CD consumes more power than others miners I have used for same algo and same overclock settings.
Yes you don't need too high core for mining CN on Nvidia. The bottleneck of memory hits way before you hit the core so yea as high as the memory OC can take.
Typically 55-60% power is enough for most cards on CN.
ETH-pill gives a boost to GDDR5X cards in CN.
DAMN! I'm really disappointed
This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy.
I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s.
I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400).
XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s
..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!!
WOOT! I said to myself - I've found my new favourite miner.
BUT as always seems to be the case it was too good to be true.
I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks.
I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak.
I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence.
Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out.
Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3.
This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy.
I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s.
I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400).
XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s
..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!!
WOOT! I said to myself - I've found my new favourite miner.
BUT as always seems to be the case it was too good to be true.
I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks.
I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak.
I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence.
Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out.
Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3.
xmr-stak 2.5.1 vs CD 0.9.2 on cnv7 (3300 vs 3580)
https://imgur.com/a/B9HubsI
this is what optimized xmr-stak can do in cnv8 (3200). 1080 Ti, 1080, 1070 Ti and 1070.
https://i.imgur.com/8e4cVeD.jpg
OK so what I can see from your info is that you have core clocks lowered considerably and memory clocks as high as possible.
I might try that but it seems that no matter what i do, XMR-Stak is stable and keeps running but with a much lower hash rate than CryptoDredge - but when I run CryptoDredge, even with all GPUs at factory settings, my system reboots.
I was wondering, does the CD watchdog cause reboot or just stop the miner.
I was also wondering if I should just install Ubuntu and run CD in linux to see if that stops the goddamn rebooting.
OK so something occurred to me. I was originally using this machine for gaming so the display was coming from the 1080. I have now gone into bios, activated the onboard graphics and I'm using that for display, so now all the GPUs are just running cryptodredge and the 1st GPU isn't trying to mine and provide display simultaneously.
I hope this may solve my reboot problems but I will let everyone know. Rookie mistake maybe? I know that when I used to mine ETH I always had onboard video disabled and used the 1st GPU for display and mining but I don't remember the rules for Nvidia and custom versions of ccminer like this one.
DAMN! I'm really disappointed
This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy.
I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s.
I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400).
XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s
..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!!
WOOT! I said to myself - I've found my new favourite miner.
BUT as always seems to be the case it was too good to be true.
I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks.
I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak.
I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence.
Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out.
Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3.
This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy.
I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s.
I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400).
XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s
..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!!
WOOT! I said to myself - I've found my new favourite miner.
BUT as always seems to be the case it was too good to be true.
I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks.
I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak.
I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence.
Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out.
Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3.
xmr-stak 2.5.1 vs CD 0.9.2 on cnv7 (3300 vs 3580)
https://imgur.com/a/B9HubsI
this is what optimized xmr-stak can do in cnv8 (3200). 1080 Ti, 1080, 1070 Ti and 1070.
https://i.imgur.com/8e4cVeD.jpg
OK so what I can see from your info is that you have core clocks lowered considerably and memory clocks as high as possible.
I might try that but it seems that no matter what i do, XMR-Stak is stable and keeps running but with a much lower hash rate than CryptoDredge - but when I run CryptoDredge, even with all GPUs at factory settings, my system reboots.
I was wondering, does the CD watchdog cause reboot or just stop the miner.
I was also wondering if I should just install Ubuntu and run CD in linux to see if that stops the goddamn rebooting.
CryptoDredge 0.9.3 CryptoNight v8 (CNv2) Phi2 how many speed on this algo 1060 6gb?
DAMN! I'm really disappointed
This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy.
I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s.
I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400).
XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s
..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!!
WOOT! I said to myself - I've found my new favourite miner.
BUT as always seems to be the case it was too good to be true.
I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks.
I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak.
I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence.
Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out.
Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3.
This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy.
I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s.
I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400).
XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s
..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!!
WOOT! I said to myself - I've found my new favourite miner.
BUT as always seems to be the case it was too good to be true.
I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks.
I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak.
I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence.
Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out.
Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3.
xmr-stak 2.5.1 vs CD 0.9.2 on cnv7 (3300 vs 3580)
https://imgur.com/a/B9HubsI
this is what optimized xmr-stak can do in cnv8 (3200). 1080 Ti, 1080, 1070 Ti and 1070.
https://i.imgur.com/8e4cVeD.jpg
DAMN! I'm really disappointed
This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy.
I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s.
I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400).
XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s
..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!!
WOOT! I said to myself - I've found my new favourite miner.
BUT as always seems to be the case it was too good to be true.
I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks.
I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak.
I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence.
Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out.
Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3.
This miner was looking so promising. I have been using XMR-Stak for months now to mine (mostly) Loki using (mostly) cryptonight-heavy.
I am running Windows 8.1 X64 on a core i7 7700K, with 1 x gtx 1080 and 3 x gtx 1070s.
I have used Nvidia Profile inspector DmW to force P state 0 and I run all the cards at core +120 memory +500 (except the 1080 gets memory +400).
XMR-Stak gives me these hashrates: 1080 ~ 680 h/s 1070s 720-760 h/s
..so you can imagine my excitement when I tried CryptoDredge and immediately I see: 1080 ~ 800 h/s 1070s 880-900 h/s !!!
WOOT! I said to myself - I've found my new favourite miner.
BUT as always seems to be the case it was too good to be true.
I have a random system hard-reboot. Sometimes the miner runs for just a couple of minutes. Once it accepted about 100 shares and must have run for about 20 or 30 minutes. This was after my driver update but with my full original overclocks.
I have tried updating the Nvidia driver from a 397.xx version to a 398.xx version. I am avoiding going into the 4XX.xx drivers because I recently updated to 417.xx and saw a drop of 20% in XMR-Stak.
I have reverted back to P-state 2. I have lowered my overclocks a bit. Both of these tactics reduced the hash-rate advantage and actually seemed to make no difference to the reboot occurence.
Has anyone else seen anything similar? Any suggestions? XMR-Stak will run stable for days. If I had kind of stability and the hash-rates I see when it does run I would be a new convert and I would also go tell any Nvidia XMR-Stak users who would listen that they are missing out.
Unless this is a sudden coincidental hardware fault, it just seems to happen using CryptoDredge 0.9.3.
CryptoDredge 0.9.2, windows 10 pro x64
Mining CN-heavy, after the dev fee it seems to start the same job over & submits duplicate shares in the same order as the first time:
Edit: Yeah it did this repeatedly, eventually putting my reject rate at about 36%.
Edit 2: Issue solved with version 0.9.3
Mining CN-heavy, after the dev fee it seems to start the same job over & submits duplicate shares in the same order as the first time:
Edit: Yeah it did this repeatedly, eventually putting my reject rate at about 36%.
Edit 2: Issue solved with version 0.9.3
Would you mind sharing your 1070 settings to achieve ~900h/s?
Just a word of warning,
I updated my 1080ti from nvidia driver 398.36 to the latest one 416.16 and my hashrate on phi2 dropped from 10.5mh down to 6.0mh.
Uninstalled 416.16 with DDU and reinstalled 398.36 problem solved
Also Top job on making Cryptodredge well worth the dev fee.
On 0.92 My phi2 hashrate is double what it was using Zenemy 1.20
I tip my hat to you good sir (or madam ??)
I updated my 1080ti from nvidia driver 398.36 to the latest one 416.16 and my hashrate on phi2 dropped from 10.5mh down to 6.0mh.
Uninstalled 416.16 with DDU and reinstalled 398.36 problem solved
Also Top job on making Cryptodredge well worth the dev fee.
On 0.92 My phi2 hashrate is double what it was using Zenemy 1.20
I tip my hat to you good sir (or madam ??)
I experienced a very similar situation. I was using 397.xx and using xmr-stak to mine loki (cryptonight-heavy). When I "upgraded" to 416.xx I saw a drop of around 20-30%.
I am going to try this miner for a while to see how it does at mining cn-heavy in comparison to xmr-stak. If it does manage 760h/s from a 1070 as claimed that is slightly better than I am currrently doing with xmr-stak and with a 1% dev fee instead of 2%. I guess I will also run a CPU miner like XMrig for the 150h/s extra that xmr-stak adds by using cpu and gpus simultaneously.
I will report back on my results.
Thanks, my 1070i work on lyra2z at 3.6Mh/s
Great miner, I'm quite impressed by how much you've improved the phi2 hashrate over & over.
Anyone witness the odd fluctuation of power usage while mining on whatever choice algo?
I was testing on cryptonight v7 and fast and left open HWinfo monitor for like 45 minutes and power use for example on my 1060 went from 45w all the way up to 140w at MAX with a average of like 59ish. Why such large range of fluctuation? Power usage on MSI after burner also goes up and down from 40% to 110% and has a shark tooth type usage graphing(on all cards as well). Power in MSI is set to 65% TDP.
On Xmr stak mining same it only fluctuates between 25 watts with a average of 69W and goes up to Mid 80W usage MAX. Power usage graph is also more tame and seemingly normal range of fluctuation.
Should I be worried or not? I mined fine for several hours straight with no crashes or errors upon testing.
I was testing on cryptonight v7 and fast and left open HWinfo monitor for like 45 minutes and power use for example on my 1060 went from 45w all the way up to 140w at MAX with a average of like 59ish. Why such large range of fluctuation? Power usage on MSI after burner also goes up and down from 40% to 110% and has a shark tooth type usage graphing(on all cards as well). Power in MSI is set to 65% TDP.
On Xmr stak mining same it only fluctuates between 25 watts with a average of 69W and goes up to Mid 80W usage MAX. Power usage graph is also more tame and seemingly normal range of fluctuation.
Should I be worried or not? I mined fine for several hours straight with no crashes or errors upon testing.
Jump to: