Agreed, but I would have hoped for the developer to own it and apologize if only to keep trustworthiness with users.  It'd be easy to just say it was on purpose and they didn't consider or understand the ramifications at the time.  Maybe it's been completely removed or the code is still there - as a developer my concern without a true statement of what was going on, is that the code is still in place and a bug could activate it, or that it might get turned on again in a subsequent release whether on purpose or accident.  Saying it was "fixed" or "resolved" just tries to sweep it under the rug.  Calling it a lie when it was easy to see, is just ridiculous.

Then explain how my gpu's were maxed out during the devfee but tdp was set at 80% prior to the devfee mining starting please.  They should not have gone above 80% or it would have automatically been throttled back down if it crept above the limit that was set - but the limit was changed to max.  They never should have gotten changed to 100% of max power.  That's all I'm asking

That doesn't sound right at all.  The power limit was changed to 100% when the devfee started. 

Yes, different algorithms use different amounts of power, but the tdp set would always be respected.  Are you trying to say that the algorithm used would change the tdp from 80% to 100%???  How exactly would that work?  Seriously, just admit you were greedy and trying to max out your devfee and modifying the settings.  Switching to another algorithm would not change the tdp. 

I'd like to hear them explain why.  My concern is that at 80% I run just under the safe limit for some of my power lines.  Jacking my power up to 100% is not only a fire hazard.  but at the very least it runs the risk of damage to my hardware, especially since my monitoring program closed every time it went into devfee mining.  I could easily see CryptoDredge raising my power to 100% and then leaving it or experiencing a bug that left it at 100%.  I'd rather not risk burning down my rigs or house.

Mostly I'd like them to own up to it, and hear that the software won't change any overclock settings or power at all anymore. Saying it's "fixed" or "resolved" doesn't say that it won't adjust your settings at all anymore or even admit to it. There's obviously code in the miner that was doing it. Is it just doing it less now?  Has that code been removed?  Why was it doing it in the first place?   Right now since they were caught doing that and won't even say more than "resolved" or "fixed", it's very hard to trust that program.  Very shady.

What does "fixed" mean?  Was it removed?  Will CryptoDredge leave the tdp\power settings alone now?  Or does it just increase it less than 100%?  You need to elaborate on what "fixed" means.

As stated earlier, whenever the devfee mining started, both Awesome Miner and my own mining monitor program would get killed and the tdp would be set to 100% regardless of whatever percentage I had it set to.  This happened every single time the devfee mining began.  Others noted the power spikes causing crashes as well.  If you are saying CryptoDredge doesn't have code to close other applications - then why would my application processes get silently killed whenever the devfee mining started but run fine otherwise? My monitoring program and rigs run for weeks without reboots or issues. The issues I reported only started when I switched to CryptoDredge.

I would appreciate hearing answers to the following:

• Why was CryptoDredge adjusting the tdp to 100% during the devfee mining?
• Does CryptoDredge adjust tdp at all anymore or will it leave it as the user set it?
• Are there any other settings that the user may have specifically configured that CryptoDredge will change behind the scenes that may cause crashes (overclocking, etc...)?
• Why would multiple application processes get killed whenever dev fee mining starts?

 

I'm sure you can appreciate that people don't want mining software sneakily changing the power usage behind the scenes causing crashes - or even potential damage.  Explaining why that was occurring and whether it will continue to any degree would go a long way toward firming up trust.

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?

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?

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. 

Translation:  probably obfuscate or encrypt code to further hide shady crap bminer will do on your machine.

I'm chill.

I want to be a supporter and miner of Zergpool. I dig the 0% fees.  I just want to understand the situation of my pending dropping enough to offset the chart with a little bit of a nosedive (whatever was being exchanged probably tanked by the time it made it through confirmations and got exchanged.  I'm also curious about what would seem like a slightly higher amount of slippage in the pending amounts.

I wrote a little app that checks my balance every few minutes just to compare.  Any while it may be apples to oranges in some regards, there definitely seems to be considerably more slippage at Zergpool right now than the others that I've tried.  Zpool comes next with smaller slippage, but still enough to be noticeable.  Others are more in line with what I would expect - some very slight slippage/gain based on exchange rates as coins are confirmed and exchanged - probably due to larger pools being able to complete blocks and therefore get to and complete the exchange process faster as well or even something like different coins taking longer/shorter for confirmations.

This says to me (and I'm just making a complete guess) that Zergpool is either not big enough yet to dump the exchange the coins fast enough to avoid the slippage, or suffering from some other aspect causing the higher than expected slippage.  It's still small numbers but after mining for a couple of hours and then stopping to watch the pending dwindle down over the next 90+ minutes, it was enough to be noticeable.  

I'm only comparing a small sample set of around ~6 pools and small time amounts, so it's not scientific or anything. I understand there's a myriad of factors that can influence it.  It'd just be nice to know - esp if there's a factor that we can change to our advantage such as picking a different coin more likely to get confirmed faster, or with a shorter TTF, or that Zergpool finds/processes faster.  

TLDR: I just like getting the whole picture.  

I've had much better luck with the previous BIOS update and not the latest.  I had some performance issues on the latest and quickly reverted back.

Glad you got it!

Also, double-check the instructions but if I remember correctly you have to have the same power supply plugged into all three (or at least the groups you're using).  I saw somewhere someone was trying different psu's in each or something.  Can't remember, but worth confirming in the instruction manual.

Check your cables.  Sounds like either the usb cable isn't running from the PCIe slot to the riser, the riser isn't powered, or the card isn't powered.  Also, make sure you're starting from group 1 of the PCIe slots.  My first B250 wouldn't boot if I didn't have the 4pin molex plugged in for each group even if I had the risers powered separately - so check the instructions on that, but you might have to plug it in as well.

pinpins - can you answer my question about why there was such a significant drop in pending?  I understand that there are market fluctuations, however I have never seen my pending drop by that much at any other pool.  Was there some delay in exchanging those coins that allowed the value to drop that much that before they were exchanged?

Wallet address in private message.

Yes it was pending, but I have not ever seen it drop like that on any other pool.  The dip is still visible on the 24h chart for a bit, and basically erased the equivalent of more than one 1080 Ti's workload for the day.  Is Zergpool unable to exchange coins quick enough to avoid such significant drops? Just asking because I don't see those drops at other pools so I wanted to know what would have caused it.

I also kept experiencing connection issues for the ports associated with Lyra2REv2 and Neoscrypt last night as well.  

Waiting for an answer on this myself...

Anyone else having issues connecting?  I keep getting dropped for Lyra2rev2 or Neoscrypt ports.

I have two PSU's connected to my B250.  The first has the CPU line ran to the board. It also has a molex running to the first set of PCIe slots and if I remember correctly, you are supposed to use the same PSU for all three of the molex slots by the PCIe slots - I'm using the same PSU 1 for that.   Then I have a second PSU that is plugged into the #2 PSU slot on the board and runs to gpu's not connected to the first psu.

Thanks pinpins!

Any word on new coin support?  Ninja, etc...?  How about BCTP?

The developer has admitted in this thread that bminer dials home for various things including licensing (which on free software doesn't make sense) as well as telemetry.  No other miner software does this. Why does bminer need to?  The developer has not been forthcoming about these things and I'm holding off until I get better answers.