the new update is very helpful, the new stats, bus reorder and clean shutdown is nice.

however, one of my rig which is mixed 13 rx570 is having hard time achieving its max hashrate at startup. (unlike previous miner, sometimes, at startup, max hashrate is already achieved). it needed dirty tricks which is disabling and enabling lan.

another 13 gpu rig which is identical, all samsung is fine.

anyway, hope you wont change anything in the code about my issue, it seems that i like it better than the old miner.

i only need to dirty tricks my mixed rig once, than multiple times before this update.

Hi jazz1984,

I'm afraid we only support newer GCN cards, so the 7970 is not supported.
As for the 470, it seems that the driver might be too old.  What OS and driver version are you running?

Im using windows 7 64-bit and river adrenaline 18.5.1 when trying to run teamredminer. Next ill try 0.3.7 with 18.6.1 and report here.

You know, I just got another report from someone else running windows 7 and having issues.  Unfortunately all of our test rigs are running windows 10 and Ubuntu 18.04.
Do let us know if the 18.6.1 driver behaves any differently though.  Also you can try to select just the 470 card with the -d option.

thanks ku4eto,  7+7 for my 470/480/570/580 4G is ok
v0.3.7 in auto = bsod or 0h/s
v0.3.6 auto = ok .

no card  monitor connected .

Yep, you got it.  The 7+7 and 7+8 configs are usually best for 4GB cards.  8GB cards can sometimes do well with 8+8.

Hi! The power draw behavior of this miner is a little special. We have a good plan for addressing it, but it will be a while before we get there. The power draw over time is as low as you can get for CNv8 right now, but during small periods of the execution we need to go full throttle, drawing more power than the rest of the time. It seems to me one of your psus isn't really happy about those ramp-ups after a while.

Have you tried balancing your Vegas a little differently across the psus, assuming you have the raw capacity in watts? It might be the case that one of your psus is more sensitive to the changes in power draw than the other. Or, if it's possible and simple enough, switch the roles of 5 Vega vs 4 Vega+system between the two psus.

This is so annoying. We had an invalid assumption that we finally could reproduce and nail down and has gotten reports from a lot of users with issues earlier that it's now working fine, but now we have regression issues with other rigs.

Is this random, or the same failure 100% of the time?

I've checked with the latest TRM miner the following pools:
wownero.ingest.cryptoknight.cc
graft.ingest.cryptoknight.cc
xmr-eu1.nanopool.org
europe.cryptonight-hub.miningpoolhub.com
gulf.moneroocean.stream

I've get the same error with SRB miner. With Stak-XMR everything works fine. I've tried with turned off Defender and FW also.

Hi! We will add all variants, all time has gone to work in stability and small features since release. We kicked things off with v8, it felt like the natural first choice.

Did you run the latest 0.3.7 version? It added cpu verification of shares, so low diff shares shouldn't really be sent to the pool. Many pools have crap implementations themselves though and say low diff when the share really was for a previous job.

Watchdog functionality, as well as temps/fans monitoring, are on the TODO list.