CryptoDredge 0.8.0 — NVIDIA GPU Miner [obsolete]

[revbones]

I'm not sure if this is the same "dev fee" crash that others are getting, but whenever the dev fee starts everything else is killed.  

I run Awesome Miner and an app that I wrote myself to monitor the temperatures on each card and step the power down for a card if its temp gets over a certain amount.  Once it cools, it steps the power back up.  Whenever the dev fee starts, both my app and Awesome Miner are both closed but the CryptoDredge window keeps running.

Is CryptoDredge purposely killing other running applications or applications that might be polling the GPU's when it starts dev fee mining?

Editted to add: 
It's apparently the same as the "dev fee" crash.  I started my monitoring app back up immediately after it was closed, and all the temps were rising because the tdp was set to 100% for the dev fee mining.

I can't abide by software doing shady stuff like that.  Closing my apps, setting my tdp to 100% (even temporarily) and potentially crashing my system. I can get the same hashrate elsewhere. 

[1714123832]

1714123832

[1714123832]

1714123832

[1714123832]

1714123832

[1714123832]

1714123832

[1714123832]

1714123832

[cryptodredge]

v0.7.0 released

• Improve defvee mechanism
• Add --retries, --retry-pause, and --timeout options. Check Readme for more information
• Build first Linux version
• Other minor fixes

Windows download
Linux download

[Dragstar]

Miting with these algos  beter than mining  eth?

[dafuzz_rsa]

v0.7.0 released

• Improve defvee mechanism
• Add --retries, --retry-pause, and --timeout options. Check Readme for more information
• Build first Linux version
• Other minor fixes

Linux version! yes! thanks. Will test

[YumiFis]

Can you Add Tribus Algo ?

[AD_Miner]

How to set the intensity for per GPU? It is installed for all at once.

[revbones]

v0.7.0 released

• Improve defvee mechanism
• Add --retries, --retry-pause, and --timeout options. Check Readme for more information
• Build first Linux version
• Other minor fixes

Can you explain how the improved devfee mechanism operates?  Given that it was closing or causing the closure of software and maxing out the tdp to 100% while mining the devfee, I think many including myself would rather know what is going on behind the scenes than take risks assuming the devfee mining works like every other miner's devfee mining and nothing shady is going on. 

Other software just mines 1% of the time for the devfee - and doesn't try to max power or close other applications.  Why does yours and is that removed in this version?

[rgzrgz]

Error. GTX 1080 TI phi 2 algo
The required CUDA version is 9020 or later (current is: 9010)
WARN - NVML is disabled
version 0.6 is working

[oberrz]

It's finally stable while dev's fee, thanks a lot !
https://ibb.co/bVyCry

[KL1000]

It's finally stable while dev's fee, thanks a lot !
https://ibb.co/bVyCry

Why 120% power? just to test?

[cryptodredge]

Error. GTX 1080 TI phi 2 algo
The required CUDA version is 9020 or later (current is: 9010)
WARN - NVML is disabled
version 0.6 is working

Use latest GeForce driver

[oberrz]

It's finally stable while dev's fee, thanks a lot !
https://ibb.co/bVyCry

Why 120% power? just to test?

No, that's my type of overlocking, I have fixed Voltage though

[cryptodredge]

v0.7.0 released

• Improve defvee mechanism
• Add --retries, --retry-pause, and --timeout options. Check Readme for more information
• Build first Linux version
• Other minor fixes

Can you explain how the improved devfee mechanism operates?  Given that it was closing or causing the closure of software and maxing out the tdp to 100% while mining the devfee, I think many including myself would rather know what is going on behind the scenes than take risks assuming the devfee mining works like every other miner's devfee mining and nothing shady is going on. 

Other software just mines 1% of the time for the devfee - and doesn't try to max power or close other applications.  Why does yours and is that removed in this version?

The devfee problem was resolved in v0.7.0. We are hard working to improve our product. Thanks for understanding.

[cryptodredge]

How to set the intensity for per GPU? It is installed for all at once.

No way. As a workaround for this issue, you might use a few CryptoDredge instances with -d option.
e.g.:

Code:

CryptoDredge -a <ALGO> -o stratum+tcp://<POOL> -u <WALLET_ADDRESS> -p <OPTIONS> -d 0,1,2 -i 5

CryptoDredge -a <ALGO> -o stratum+tcp://<POOL> -u <WALLET_ADDRESS> -p <OPTIONS> -d 3,4,5 -i 4

[cryptodredge]

Can you Add Tribus Algo ?

If there are many requests for this

[somaton]

So, no more cryptodredge for me. They released new version without even telling us that new version is cuda 9.2 only. I was waiting for new version with "fixed" devfee and now we have it, but now they force us to use cuda 9.2, but I want to use stable cuda 9.1 drivers. No choice - no cryptodredge

[revbones]

v0.7.0 released

• Improve defvee mechanism
• Add --retries, --retry-pause, and --timeout options. Check Readme for more information
• Build first Linux version
• Other minor fixes

Can you explain how the improved devfee mechanism operates?  Given that it was closing or causing the closure of software and maxing out the tdp to 100% while mining the devfee, I think many including myself would rather know what is going on behind the scenes than take risks assuming the devfee mining works like every other miner's devfee mining and nothing shady is going on. 

Other software just mines 1% of the time for the devfee - and doesn't try to max power or close other applications.  Why does yours and is that removed in this version?

The devfee problem was resolved in v0.7.0. We are hard working to improve our product. Thanks for understanding.

That doesn't explain anything.  Why would you close applications and max power?  Is that removed in the current version?  What does "resolved" even mean in relation to those questions?

[cryptodredge]

1. Could you check an another port or the firewall settings.
2. We'll try to resolve issue with "-b localhost:4444"

1. Firewall settings is default.
 Connection established. Command sended normally. Readed answer as `null`. No exceptions.

powershell code work with any ccminer:

Code:

$Client =[Net.Sockets.TcpClient]::new("127.0.0.1", "4444")
$Stream = $Client.GetStream()
$Writer = [IO.StreamWriter]::new($Stream)
$Reader = [IO.StreamReader]::new($Stream)

$Writer.WriteLine("summary")
$Writer.Flush()
$result = $Reader.ReadLine() # $Reader.ReadToEnd() same $null
Write-Host "Answer: $result"

2. Thanks.

Please, try $Writer.Write("summary"), because WriteLine sending "summary\r\n". We'll fix it

> Please, try $Writer.Write("summary"), because WriteLine sending "summary\r\n". We'll fix it

When???

Please check v0.7.0

[UselessGuru]

1. Could you check an another port or the firewall settings.
2. We'll try to resolve issue with "-b localhost:4444"

1. Firewall settings is default.
 Connection established. Command sended normally. Readed answer as `null`. No exceptions.

powershell code work with any ccminer:

Code:

$Client =[Net.Sockets.TcpClient]::new("127.0.0.1", "4444")
$Stream = $Client.GetStream()
$Writer = [IO.StreamWriter]::new($Stream)
$Reader = [IO.StreamReader]::new($Stream)

$Writer.WriteLine("summary")
$Writer.Flush()
$result = $Reader.ReadLine() # $Reader.ReadToEnd() same $null
Write-Host "Answer: $result"

2. Thanks.

Please, try $Writer.Write("summary"), because WriteLine sending "summary\r\n". We'll fix it

> Please, try $Writer.Write("summary"), because WriteLine sending "summary\r\n". We'll fix it

When???

Please check v0.7.0

Fixed, thank you!
Miner ready for testing with MultiPoolMiner (www.multiPoolMiner.io)

[cryptodredge]

v0.7.0 released

• Improve defvee mechanism
• Add --retries, --retry-pause, and --timeout options. Check Readme for more information
• Build first Linux version
• Other minor fixes

Can you explain how the improved devfee mechanism operates?  Given that it was closing or causing the closure of software and maxing out the tdp to 100% while mining the devfee, I think many including myself would rather know what is going on behind the scenes than take risks assuming the devfee mining works like every other miner's devfee mining and nothing shady is going on. 

Other software just mines 1% of the time for the devfee - and doesn't try to max power or close other applications.  Why does yours and is that removed in this version?

The devfee problem was resolved in v0.7.0. We are hard working to improve our product. Thanks for understanding.

That doesn't explain anything.  Why would you close applications and max power?  Is that removed in the current version?  What does "resolved" even mean in relation to those questions?

What does "close applications" mean? Does it mean OS freezing? Actually, CryptoDredge is unable to close your apps. "resolved" means "max power" problem was fixed