Author

Topic: ANTMINER S3+ Discussion and Support Thread - page 166. (Read 710164 times)

sr. member
Activity: 312
Merit: 250
September 22, 2014, 02:16:35 PM
Just got my first two S3s. They're both running at about 455 GH out of the box, but GH.io is showing that one of them is sending about 200,000 duplicate shares per hour. Anybody ever see this before and know how to fix?

I think if you set the worker stratum difficulty to 256 on GHASH.IO Workers page, it will fix this.  256 works great for all of my S3's.  None have duplicates, and also the stale count is very low.
hero member
Activity: 569
Merit: 500
September 22, 2014, 02:11:17 PM
I know that 250 runs about 500 watts...and that three S3+s will cause a EVGA 1300 to shutdown.



 then that is a defective s-3+  my s-3+   that will run at freq 250 and keep the gh at 500gh use 390 watts on a platinum psu.


 I own a gold 1300 evga and it can run 3 at 243.75 no worries  1110 watts.

Since I only have 1 s-3 + that runs at 250/500gh I can not see if 3 will work on the evga.

 I suspect no.  as the evga ran  3-s-1's using 1215 watts   and doing 600 gh for about a month.  then did not want to continue at that clocking. I had to back off a bit.



yeah those numbers are a bit off... 250 should net u 505gh/s of course this is what a non overheating unit does. 38c/40c averages.
I highly doubt its drawing 500watts as my 750's are no hotter than the ones running some s1's
243.75 gets me 492gh/s on the ones that wont do 250
full member
Activity: 242
Merit: 100
Blockchain-based Financial Ecosystem
September 22, 2014, 01:18:41 PM
Does an x mean that the chip has shut down?  Or is it burning up? Wink

Likely means that it's completely shut down.  Not sure what the "-" means as a comparison.  I've found that completely turning off the miner and letting it cool generally gets an x to revert to an o.

Just rebooting works for me..

Just tried that and an x was changed to a -.  Wonder if they ever change to an o without a reboot or restart.
weird, then try and shut them off for a while. If the "-" still appears, you've gotta do an RMA... But I think Bitmain will just send you a new chain board.
soy
legendary
Activity: 1428
Merit: 1013
September 22, 2014, 01:12:22 PM
Does an x mean that the chip has shut down?  Or is it burning up? Wink

Likely means that it's completely shut down.  Not sure what the "-" means as a comparison.  I've found that completely turning off the miner and letting it cool generally gets an x to revert to an o.

Just rebooting works for me..

Just tried that and an x was changed to a -.  Wonder if they ever change to an o without a reboot or restart.

...the auto reboot for low hashrate by cgminer-avg-monitor at the half hour didn't clear the -.
full member
Activity: 242
Merit: 100
Blockchain-based Financial Ecosystem
September 22, 2014, 12:59:18 PM
Does an x mean that the chip has shut down?  Or is it burning up? Wink

Likely means that it's completely shut down.  Not sure what the "-" means as a comparison.  I've found that completely turning off the miner and letting it cool generally gets an x to revert to an o.

Just rebooting works for me..
soy
legendary
Activity: 1428
Merit: 1013
September 22, 2014, 12:53:11 PM
Does an x mean that the chip has shut down?  Or is it burning up? Wink

Likely means that it's completely shut down.  Not sure what the "-" means as a comparison.  I've found that completely turning off the miner and letting it cool generally gets an x to revert to an o.
legendary
Activity: 1022
Merit: 1010
September 22, 2014, 12:49:44 PM
Does an x mean that the chip has shut down?  Or is it burning up? Wink
soy
legendary
Activity: 1428
Merit: 1013
September 22, 2014, 12:37:08 PM
Yes, this is better.  Before it barely got up to 435GH/s with the low hashing board on the right side when looking at the RJ45 connector end.  The right side is the top chain and generally has the higher temperature and faster fan.  In this case it had lower temperature and slower fan than the lower chain.  So, taking the end plates and their fans, swapping ends and moving the controller board, put it back the way it was shipped, the questionable board on the cooler side.  

Almost right away the average went above 441GH/s and has remained above 440GH/s for the last 3h 23m and is presently 442.04 tho the utility is only 15.  No hardware errors in that time.  It was started as the afternoon cooled.  It remains to be seen what happens tonight as the humidity increases.

Oh well.  A minor improvement over yesterday morning and there's even greater humidity as it rained.  This morning the problem S3 is hashing at 434.15GH/s.  A nice improvement over finding it down at 419GH/s in the AM.  Guess I'll just have to settle with this hashrate.  The good S3 immediately next to it is at 440.85.


...1½ hrs after running /etc/init.d/cgminer stop, it restarts automatically after a minute or two, the hashrate of the problem is up to 442.18GH/s(avg).  It restarts with a fresh Elapsed duration.  So, I'll schedule this to run middle of the night and again in the AM.

Okay, I see this problem has been address in message #482 this forum with cgminer-avg-monitor script.  Kudos.

Okay, have written/modified the scripts and changed scheduled tasks.  By the time I was done the hashrate was down to 435.09GH/s  So, in about 22 minutes the script will run and it should restart leaving a record in /usr/bin/avg.log.  Nah, will try running from the command line...failed, typing errors I presume.

Okay, the lower case L was actually a one.  Runs fine.

darn, restarted with an x at position 8 of the 16 representing the problem board.


A cold reboot with the machine off a minute allowed it to wake to 441.05GH/s and the x gone.  An x in the 8 position can only be in the center of the board if upper left ASIC is 1, lower far left ASIC is 2, second upper left ASIC is 3, etc.  This would put the eighth position of the chain at the center left bottom ASIC.  Next time I take it one apart I'll look at the component numbering and finding a component common to each ASIC, see how they progress.  Who knows, the ASICs themselves might be numbered.

Up 11 minutes and there's an x in a different position, now in the #2 position of the top chain.
soy
legendary
Activity: 1428
Merit: 1013
September 22, 2014, 12:24:32 PM
Sorry I don't mean to seem lazy, but I have looked and can't find it. Can someone kindly post where the instructions are to set the frequency setting above/outside what is listed on the drop down menu using the new firmware?

I know some of you have had decent results with frequency settings above 250. ie. 262.5.

Would like to give it a shot.

Thanks!

Strato

Miner Configuration, you'll see a gray'd out Advanced Setting to the right of General Settings.
legendary
Activity: 1022
Merit: 1010
September 22, 2014, 12:19:58 PM
Sorry I don't mean to seem lazy, but I have looked and can't find it. Can someone kindly post where the instructions are to set the frequency setting above/outside what is listed on the drop down menu using the new firmware?

I know some of you have had decent results with frequency settings above 250. ie. 262.5.

Would like to give it a shot.

Thanks!

Strato
soy
legendary
Activity: 1428
Merit: 1013
September 22, 2014, 12:09:29 PM
Yes, this is better.  Before it barely got up to 435GH/s with the low hashing board on the right side when looking at the RJ45 connector end.  The right side is the top chain and generally has the higher temperature and faster fan.  In this case it had lower temperature and slower fan than the lower chain.  So, taking the end plates and their fans, swapping ends and moving the controller board, put it back the way it was shipped, the questionable board on the cooler side.  

Almost right away the average went above 441GH/s and has remained above 440GH/s for the last 3h 23m and is presently 442.04 tho the utility is only 15.  No hardware errors in that time.  It was started as the afternoon cooled.  It remains to be seen what happens tonight as the humidity increases.

Oh well.  A minor improvement over yesterday morning and there's even greater humidity as it rained.  This morning the problem S3 is hashing at 434.15GH/s.  A nice improvement over finding it down at 419GH/s in the AM.  Guess I'll just have to settle with this hashrate.  The good S3 immediately next to it is at 440.85.


...1½ hrs after running /etc/init.d/cgminer stop, it restarts automatically after a minute or two, the hashrate of the problem is up to 442.18GH/s(avg).  It restarts with a fresh Elapsed duration.  So, I'll schedule this to run middle of the night and again in the AM.

Okay, I see this problem has been address in message #482 this forum with cgminer-avg-monitor script.  Kudos.

Okay, have written/modified the scripts and changed scheduled tasks.  By the time I was done the hashrate was down to 435.09GH/s  So, in about 22 minutes the script will run and it should restart leaving a record in /usr/bin/avg.log.  Nah, will try running from the command line...failed, typing errors I presume.

Okay, the lower case L was actually a one.  Runs fine.

darn, restarted with an x at position 8 of the 16 representing the problem board.
soy
legendary
Activity: 1428
Merit: 1013
September 22, 2014, 12:06:13 PM
One of my new S3+ shows 0 temp and high fan speed. Has someone an idea were the sensor is located? Still mines flawless. RMA would take too much time and efforts.

The LM75A is in the center of the ASICs, halfway between the upper and lower rows.  I'd guess a connector fault and would try swapping ribbon cables to see if the problem changes chains.
legendary
Activity: 1167
Merit: 1009
September 22, 2014, 12:05:25 PM
Just called on a problem blade they were offering to do an RMA but phone call dropped
newbie
Activity: 1
Merit: 0
September 22, 2014, 11:32:36 AM
One of my new S3+ shows 0 temp and high fan speed. Has someone an idea were the sensor is located? Still mines flawless. RMA would take too much time and efforts.
hero member
Activity: 924
Merit: 1000
Watch out for the "Neg-Rep-Dogie-Police".....
September 22, 2014, 11:24:52 AM
Does anyone have info for UK bitmain support?

PM'd ya  Wink
hero member
Activity: 927
Merit: 1000
฿itcoin ฿itcoin ฿itcoin
September 22, 2014, 11:23:12 AM
As another heads up - Bitmain have recently upgraded their support capabilities, locations etc.. I'd had the pleasure to use their support services recently and I couldnt be happier, they were brilliant

More details on their new support contacts (if anyone else needs them) :
****************************
Bitmain Technologies
Warranty Department
3700 Quebec Street Suite 100239
Denver, Colorado 80226
USA

Telephone number: 1-844-248-6246

or for the European Region

Bitmain Technologies
department 119,
143 kingston road,
London, SW19 1LJ,
United Kingdom

Telephone Number: +44-020-30024099

For US customers Please include our telephone number 1-844-248-6246 on the shipping label.

and for the European Region

Please include our telephone number +44-020-30024099 on the shipping label.
These are just mail forwarding addresses btw.
member
Activity: 74
Merit: 10
September 22, 2014, 11:21:28 AM
As another heads up - Bitmain have recently upgraded their support capabilities, locations etc.. I'd had the pleasure to use their support services recently and I couldnt be happier, they were brilliant

More details on their new support contacts (if anyone else needs them) :
****************************
Bitmain Technologies
Warranty Department
3700 Quebec Street Suite 100239
Denver, Colorado 80226
USA

Telephone number: 1-844-248-6246

or for the European Region

Bitmain Technologies
department 119,
143 kingston road,
London, SW19 1LJ,
United Kingdom

Telephone Number: +44-020-30024099

For US customers Please include our telephone number 1-844-248-6246 on the shipping label.

and for the European Region

Please include our telephone number +44-020-30024099 on the shipping label.
hero member
Activity: 927
Merit: 1000
฿itcoin ฿itcoin ฿itcoin
September 22, 2014, 11:00:42 AM
5 days in and my antminer s3+ caught fire!



This literally just happened like 5 minutes ago.
Rig went offline, went out to see what's what and try and give it a power cycle, no go.. So I swapped the psu for a brand new one and went to turn it on and was met with a huge cloud and smoke and an adrenaline rush. (all cables correct etc, I have 9 others from the same batch running on the same corsair rm1000 PSUs with uptimes of 5 days, no overclocking involved)


Does anyone have info for UK bitmain support?
soy
legendary
Activity: 1428
Merit: 1013
September 22, 2014, 10:50:09 AM
Yes, this is better.  Before it barely got up to 435GH/s with the low hashing board on the right side when looking at the RJ45 connector end.  The right side is the top chain and generally has the higher temperature and faster fan.  In this case it had lower temperature and slower fan than the lower chain.  So, taking the end plates and their fans, swapping ends and moving the controller board, put it back the way it was shipped, the questionable board on the cooler side.  

Almost right away the average went above 441GH/s and has remained above 440GH/s for the last 3h 23m and is presently 442.04 tho the utility is only 15.  No hardware errors in that time.  It was started as the afternoon cooled.  It remains to be seen what happens tonight as the humidity increases.

Oh well.  A minor improvement over yesterday morning and there's even greater humidity as it rained.  This morning the problem S3 is hashing at 434.15GH/s.  A nice improvement over finding it down at 419GH/s in the AM.  Guess I'll just have to settle with this hashrate.  The good S3 immediately next to it is at 440.85.


...1½ hrs after running /etc/init.d/cgminer stop, it restarts automatically after a minute or two, the hashrate of the problem is up to 442.18GH/s(avg).  It restarts with a fresh Elapsed duration.  So, I'll schedule this to run middle of the night and again in the AM.

Okay, I see this problem has been address in message #482 this forum with cgminer-avg-monitor script.  Kudos.
legendary
Activity: 4256
Merit: 8551
'The right to privacy matters'
September 22, 2014, 09:40:36 AM
I know that 250 runs about 500 watts...and that three S3+s will cause a EVGA 1300 to shutdown.



 then that is a defective s-3+  my s-3+   that will run at freq 250 and keep the gh at 500gh use 390 watts on a platinum psu.


 I own a gold 1300 evga and it can run 3 at 243.75 no worries  1110 watts.

Since I only have 1 s-3 + that runs at 250/500gh I can not see if 3 will work on the evga.

 I suspect no.  as the evga ran  3-s-1's using 1215 watts   and doing 600 gh for about a month.  then did not want to continue at that clocking. I had to back off a bit.

Jump to: