why is everyone thinking 20XX series will mine better? Drivers will be new and unpolished, but more importantly, wasn't there some hashing advantage to using GDDR5 like in the 1070 series? or am I missing something? Dollar per MH/s the 10XX series seems to be the way to go...

me too. but 11.9 is still churning away.. if we ain't broke... i mean if IT ain't broke.

i like this, but it seems that the TDP would be highly variable and create more stress on the GPUs... right? i suppose this is just nicehash 2.0?

are you referring to any particular auto-switching mining platform or just setting to mine BTG in the .bat file? It seems like a lot of work to have to switch to what is doing best each week and nobody knows if BTG will sustain at a higher earning ratio than ETH. I do hope you can correct me here though...

i had to look it up too... near the same efficiency im getting with GPUs... but wouldnt you rather have GPUs instead of these screaming loud fans?

I also have a couple rigs that restart every 4-6 hours. Is there a log file in win7 that would give insight as to whether specifically AB or other driver was at fault? I've been assuming it was just an OC/ temp thing, but hard to figure out which card is at fault so I end up lowering OC on all of them.

tried to add stratum+ssl:// to my us1 server address (where I point to ethermine network) and it didn't work. is this only for eu1 server? Also aren't peeps having issues with ssl for 11.X ?

made the move today on my win7 rig from claymore v10.1 to v11.8 and robinh00d driver to 18.6.1 drivers. There seems to be no love for new driver on my rx 470s. I'm going to try again after cleaning with DDU. But it should be good right? thx.

running win10 (upgraded from win7) with rx 470 (19Mh/s) and rx 580 (22.4Mh/s) with 18.1 drivers (compute mode) and strap timings adjusted on the 470. claymore 10.5 crashes after 2-6 hours of running. Tried 10.1 and the same thing happens. System does not reboot after claymore crash it just waits for me to manually start claymore again. It was working fine under win7 (16.10.2 drivers and only rx 470)... anything I'm missing or is there a log I could check to see why claymore crashed? Thanks.

just upgraded to win10 from win7. my rx 470 4gb would not take aug 23 blockchain drivers. After that, I tried recent 18.1 drivers too. System recognizes rx 470 in device manager (with alert (!) ) but will not pair either of the previously mentioned drivers with the rx 470. I have strap timings changed on my 470 but that is all. Anyone have a suggestion besides more DDU uninstall (which is what I will try next).

eth only on claymore... shouldn't need the +200 core , right? also anyone know if any of the previous drivers work on the 1070 ti or only the most recent?

haven't seen any extra information on this. i use PPLNS on antpool and am curious what their new payout types actually mean that are advertised on their homepage.

PPS+, PPLNS+, PPS -3

they claim it will increase revenue 3-8%. whats the catch?

edit: I'm guessing its just a ploy to get people who ordered all the new s9s shipping in March to be sure to point at antpool (where they are keeping TX fees for themselves). then after a month or two they will remove the promotion. I say this because I've seen the PPS and solo fees adjusted before.

I'm looking at my stats on ckpool for an underclocked s7 at 2.86 Th/s. It has been running about 12 hours and I wanted to know if my invalids are reasonable. It says stale: 28,290/10 ; duplicate: 2,829/1. For a total invalid rate of 0.206%. I think this is reasonable but if anyone can confirm I would appreciate it. The overall pool rate for invalids is higher.

I too do not understand this. I assume you are talking about using a trade exchange (tx) instead of a wallet like coinbase? So coinbase might take 1% to consolidate (or when you move to cold storage/buy something with these BTC) because the transactions are so small (by design small BTC transactions have a higher fee percentage to prevent spam). But you are suggesting sending these smaller payouts to an exchange and then consolidate them before sending these to cold storage?

Hi I'm trying to dial in my settings on the CKPool kano.is pool. I have my s7s underclocked to 3Th/s. Should I set a minimum Diff for my worker to 4096 or 8192? Or should I just leave it at 0 (auto) and CKPool will feed me what it needs. I have left it at 0 (auto) and I get a lot of Diff 1024 or 1536. Just wanted to make sure I am optimizing workload because antpool was giving me Diff 4096 and 8192. Appreciate any advice.

Is there a way to add something which will prevent a reboot if "N" reboots attempted in "M" minutes? If the s7 fails to achieve boards over 55 degrees then a reboot is a good practice. If the s7 fails to achieve boards over 55 degrees after 5 reboots in 20 minutes then a "do not reboot" is a good practice. This is because too many consecutive reboot loops without hashing is a waste of power. If the 5th reboot does not start hasing then there is a good chance the 6th reboot will not either.  Or additionally a "do not reboot for "H" hours after "N" consecutive reboot loops" would take that notion a step further.

I'm not sure this is possible just throwing it out there.

sweet. I'm not very good at reading the code but you are saying that the script will restart the miner when it shows 0 hash and starts beeping or will it restart cgminer when either of those situations happen. meaning it would restart when beeping for any reason (internet loss, too hot, other beep reason).

also does anyone know what makes the individual hashing boards start back up again? I have tried some of the lower value PIC settings at 400 mhz on a single board and when it drops it will not try to come back up and start hashing again. The same board at more modest 630mV/550 settings will come back up and start hashing again after 5-8 minutes if it drops out.

i tried out a lower RPM fan with manual knob and tach line. I only had one to test so I kept one original s7 fan at the rear. Manual knob fan worked fine, but I noticed that rather than start at low/quiet RPM for original s7 fan (as it typically does for about 45 seconds before linux/cgiminer initializes), the stock s7 fan starts at max RPM immediately after power up. I'm guessing that machine recognizes one fan is not stock and so it defaults to max spin on the fan that is stock.

Are people still doing this one controller and 6 blade or 9 blade hack? I'm confused as some of the above comments make me think its not a good idea. I have a batch 7 that has 9 18 pin slots but came with the 162 chip board. Can I take the 162 chip boards out and put in 6 135 chip boards as long as I have enough PSU?