CryptoDredge 0.8.0 — NVIDIA GPU Miner [obsolete]

[Thanhtamtg]

I have very specific overlocking with constant voltage and my PSU works on 80% of their power with my overlocking, when Dev's session starts it makes my PSU work on 100% and it crash everything. Why don't you just make dev's sessions in the same algorithm as users session ? It will resolve any issues.

p.s I'll try i 5 but I guess my suggestion will be much better

p.p.s : Same picture with -i 5 https://ibb.co/eac4rd and https://ibb.co/jBqqWd

Please make it finally fixed. Your miner is the best but this thing makes me using ccminer...

VOTE: just make dev's sessions in the same algorithm as users session

[1713291596]

1713291596

[1713291596]

1713291596

[1713291596]

1713291596

[Ogionion]

Hello, could we connect CryptoDredge to Awesome Miner? who already connected help

[N0VESKE]

   
CryptoDredge 0.6.0
It great and high-performance for my 1080Ti
phi2 LUX

[ztaz]

   
CryptoDredge 0.6.0
It great and high-performance for my 1080Ti
phi2 LUX

this if it was stable and took off in 5 minutes after launch  ... and the developers responded to tickets ... ccminer 2.3 is stable in my rigs, this is not.

[Drifttap]

Not sure why but I get slower results with 0.6.0. I also had to add --cpu-priority 5 to the command line in order for my miner to last a few seconds.
Ended up crashing on a 2 card pc and a 5 card 1080ti rig.
Reverted back to 0.5.1, have had to reduce clocks because of "dev fee crash" but i'm seeing the best results but also at a higher total power consumption.
Stable overclocks for 1080ti will range on any miner for ph2 go for -500 memory clock, then start at +50 core clock and slowly work your way up.

[Mikanoshi]

Instead of resetting power limit and crashing/burning🔥 users' rigs just make 2% devfee instead of 1% if you don't get enough.

[kamak]

So as many people that use CD (CryptoDrgedge) are aware the dev fee is being mined on an algo, with a power curve, that is completely out of alignment with the PHI2 algo. This is causing pp rigs to crash, if they are not aware of what is happening and prepared to adjust their gpus, for it, This is an unacceptable practice by CD, in my opinion., as this prevents pp from adjusting for maximised PHI2 production, at lowest PL, due to having to or wishing to power limit their gpus for power conservation. Likewise, also limiting the use of -i Intensity, due to the Dev fee algo, causing over-driving of the gpu's. I am conducting a back to back comparison test with CD (CryptoDredge) Miner and ZE (Z-Enemy) miner, on identical rigs, for a one week period on Icemining.ca pool to determine luxcoin production. The fact that I can not use an intensity factor greater than the default CD set, is only proving that CD has limitation under this Dev fee algo practice.

[cryptodredge]

So as many people that use CD (CryptoDrgedge) are aware the dev fee is being mined on an algo, with a power curve, that is completely out of alignment with the PHI2 algo. This is causing pp rigs to crash, if they are not aware of what is happening and prepared to adjust their gpus, for it, This is an unacceptable practice by CD, in my opinion., as this prevents pp from adjusting for maximised PHI2 production, at lowest PL, due to having to or wishing to power limit their gpus for power conservation. Likewise, also limiting the use of -i Intensity, due to the Dev fee algo, causing over-driving of the gpu's. I am conducting a back to back comparison test with CD (CryptoDredge) Miner and ZE (Z-Enemy) miner, on identical rigs, for a one week period on Icemining.ca pool to determine luxcoin production. The fact that I can not use an intensity factor greater than the default CD set, is only proving that CD has limitation under this Dev fee algo practice.

The fix will be available in next release. Stay tuned.

[jugger1028]

So as many people that use CD (CryptoDrgedge) are aware the dev fee is being mined on an algo, with a power curve, that is completely out of alignment with the PHI2 algo. This is causing pp rigs to crash, if they are not aware of what is happening and prepared to adjust their gpus, for it, This is an unacceptable practice by CD, in my opinion., as this prevents pp from adjusting for maximised PHI2 production, at lowest PL, due to having to or wishing to power limit their gpus for power conservation. Likewise, also limiting the use of -i Intensity, due to the Dev fee algo, causing over-driving of the gpu's. I am conducting a back to back comparison test with CD (CryptoDredge) Miner and ZE (Z-Enemy) miner, on identical rigs, for a one week period on Icemining.ca pool to determine luxcoin production. The fact that I can not use an intensity factor greater than the default CD set, is only proving that CD has limitation under this Dev fee algo practice.

There are reports that CD has a much higher power use output compared to the other miners as well, which would probably lead to more hashrate. Can you check that as well?

[shubham412302]

1080ti hashrate on lyra2v2- 83.5mh/s +180core, -500 mem, 80%power. GTX 970 hashrate - 25.2mh/s, +188core, -500 mem, 84% power. Overall 16% improvement over alexis miner. Miner used to crash on dev fee. Now its working fine.

[dragonmike]

Any lyra2z hashrates from 1080 users out there?

[HonestAbeX1]

Any lyra2z hashrates from 1080 users out there?

With CD 0.6, I am getting on a 1080 with 60% pwr +125/-200 core/mem oc about 2.8 Mh/s.  On ccminer 2.3 a similar 1080 tops out at 2.4 Mh/s.

[Mikanoshi]

There are reports that CD has a much higher power use output compared to the other miners as well, which would probably lead to more hashrate. Can you check that as well?

"Power use output", contradictory
Obviously power usage will be higher if miner is optimized to use cores as much as possible.

Any lyra2z hashrates from 1080 users out there?

Palit with gamerock premium BIOS on stock (2GHz/9.5GHz) ~2.7 MH/s.
P.S. Still don't understand why everyone is posting +core/-mem, those values are useless. + and - from what?
It's like all 1080 have the same frequencies in BIOS and same chip quality :facepalm:

[jugger1028]

If only I could scour the internet for messages that are clear but not exactly as I'd like them to appear, then I too could act like a grammar Nazi while living in my mom's basement..

[Frankie001]

There are reports that CD has a much higher power use output compared to the other miners as well, which would probably lead to more hashrate. Can you check that as well?

"Power use output", contradictory
Obviously power usage will be higher if miner is optimized to use cores as much as possible.

Any lyra2z hashrates from 1080 users out there?

Palit with gamerock premium BIOS on stock (2GHz/9.5GHz) ~2.7 MH/s.
P.S. Still don't understand why everyone is posting +core/-mem, those values are useless. + and - from what?
It's like all 1080 have the same frequencies in BIOS and same chip quality :facepalm:

I see your point but at least it's a rough estimate where to stop where to stop with the oc from stock, the final tweaks we can do ourselves, it does make it a bit easier.

[kamak]

We await your adjustments to this miner, for further testing and comparison.

[kukucumber]

Linux?

[dbalz]

When do you expect to fix the bug related to the dev fee mining an algo with a power curve causing rigs to crash?

[Mirovoy]

Just tried out your miner, the hashrate is indeed better than ccminer2.3 on phi2, but during mining the cards produce this annoying clicking sound (kind of like if you put an ice cube into a glass and shake it around). Is there any way to fix it myself? If not, I hope you, the developer, will sometime soon. If you'd like any additional information I'm more than happy to provide it.

[Neat]

Hello,

My rig restarted when mining lyra2rev2 with CryptoDredge through Awesomeminer and I got this error on event viewer,

Code:

Faulting application name: CryptoDredge.exe, version: 0.0.0.0, time stamp: 0x5b38d8df
Faulting module name: CryptoDredge.exe, version: 0.0.0.0, time stamp: 0x5b38d8df
Exception code: 0xc0000005
Fault offset: 0x00000000000c9a21
Faulting process ID: 0x1df4
Faulting application start time: 0x01d41624adfaf1cf
Faulting application path: C:\Users\blah\AppData\Local\AwesomeMiner\cryptodredge_0.6.0_1\CryptoDredge.exe
Faulting module path: C:\Users\blah\AppData\Local\AwesomeMiner\cryptodredge_0.6.0_1\CryptoDredge.exe
Report ID: 2ab02e86-3361-4dd6-bb72-cb962981fd41
Faulting package full name:
Faulting package-relative application ID: