Quote from: atledenin on July 29, 2014, 02:05:00 PM

Quote from: Duce on July 29, 2014, 01:37:32 PM

Quote from: atledenin on July 29, 2014, 12:41:06 PM

I'm also having the issue with the S3 hashrate dropping off. It generally starts around 435Gh but drops to around 390-400GHs. I'm at work now and I'm looking at my S3 on Slush's pool and I'm currently showing -

Total average hash rate in last 60 minutes: 381070 Mhash/s Shocked

Has anyone found a solution to this or had word from BitMain?

Some units do and some don't, try a lower clock such a 212.5 as others have identified. I have one that runs steady at 218.5 and another that does not like the stock clock but runs fine at 212.5, and is reliable at that speed.

Quote from: philipma1957 on July 29, 2014, 01:50:49 PM

Quote from: Duce on July 29, 2014, 01:37:32 PM

Quote from: atledenin on July 29, 2014, 12:41:06 PM

I'm also having the issue with the S3 hashrate dropping off. It generally starts around 435Gh but drops to around 390-400GHs. I'm at work now and I'm looking at my S3 on Slush's pool and I'm currently showing -

Total average hash rate in last 60 minutes: 381070 Mhash/s Shocked

Has anyone found a solution to this or had word from BitMain?

Some units do and some don't, try a lower clock such a 212.5 as others have identified. I have one that runs steady at 218.5 and another that does not like the stock clock but runs fine at 212.5, and is reliable at that speed.

this is the way to go. my 2 units run at 212.5 very well

look at my charts solid at 430gh and 212.5 Note that dip was a T-storms caused blackout. gear auto -booted back to normal and 430gh

http://imagize[Suspicious link removed]ageshack.us/v2/1280x1024q90/745/dtIArs.png

Thanks guys

I'll give that a whirl this evening!

Thanks Duce and philipma1957, clocking down to 212.5 works great. Hashing at 410 atm but at least its stable and doesn't end up at 380-390Ghs!

Do you think it would be worth engaging Bitmain about this? Would really like that extra 30Ghs!