1) So they were at 930-950gh.  How much did they decline?  What is the total hashing at this moment?

2) Focus on the GH/S (avg) numbers from the Antminer WRT 'miner status' tab.  The website info isn't as accurate and constantly changes.  The 5 sec hashrate reading also constantly jumps around.

3) Look at and check the ASIC chip status under the 'miner status' tab.  They should read 00000000 00000000 00000000 00000000 .  If there are any x's, x0000000 00x00x00 00x0xx00 00000000, try rebooting the unit.  If there are still any x's after the reboot, or if multiple x's keep appearing after a short amount of time (hrs to overnight), try reflashing the unit with the latest .bin file from bitmain.  That solved my asic problems.  Here is my post on how to do this:

          https://bitcointalk.org/index.php?topic=602592.msg6654028#msg6654028

4) I've only been running my four units for about a month.  In the past few days the outside temp in central PA has been in the 80's.  It has been humid and significantly hotter in the room with my S1's.  Their avg hashrate has decreased a little.  The one unit went from 200 gh/s avg to 197gh/s avg.  From my brief 1 month of experience, I conclude that heat causes them to run slower and can cause asic chip errors.  Did you try to set up extra cooling? Even a cheap box fan for some extra air flow should help cool them down.  Mine are all overclocked and usually run at a temp of 43-47, but on the hot days I've seen 49-51.  You can also try cleaning out the heat sinks with some compressed air to get the accumulated dust out of there.

Let us know if any of this helped!

I bought four S1's a month ago and had a similar problem.  The good news is that it wasn't too difficult to fix!  I ran my four units over night and checked them in the morning only to find multiple x's on my asic chips and the one unit was running at around 100 gh/s.  I did a little research and downloaded the latest .bin file from bitmain which you can install/flash to each S1.  It said that this new version eliminated false asic chip errors and guess what... It actually solved my problems!  I went from xxxxxxox ooxxxoxxo xoxoxoxox to all 00000000 in my asic chip status.  Only one unit got an x again and it went away and stayed "o" after a reboot.  Reflashing a new .bin file wasn't that difficult to do so here are the steps.

1) Download the latest .bin file (antMiner_openwrt20140207.bin) and save it to your computer.  I made a folder called "mining" to keep the new and backed up files in it. You can find the .bin file here:

          https://www.bitmaintech.com/support.htm?pid=00720140411033846942qQqjOD460695

2) Log into the antminer interface by typing the IP address into a web browser.  

          Mine is 192.168.1.201    ... Username root, password root.

3) Click on the System tab, then click on the Backup / Flash Firmware tab.

4) Make a backup of the current configuration file by clicking 'generate archive', and save it to your mining folder.  (Just in case you need to revert to your old settings)

          I used 'save as' so I could name the first backup with a 201 at the end for my unit that ends in .201

5) Now install the new .bin file by clicking the browse button under the 'flash new firmware image' section.  Locate the file downloaded in step one (antMiner_openwrt20140207.bin) and select it.  Click the 'flash image' button directly to the right of browse.  It will take a few seconds (mine took 15-20) to upload and a new page should appear that verified your new image.  Click proceed and you're on your way.

6) Repeat this process for each of your units.  Run them for a day and report back to us to see if your problems were solved.  

This solved all my asic chip problems.  I check each unit every couple days to make sure that they are all 00000000 00000000 00000000 0000000.  I got an occasional x0000000, but it went away after a reboot.  Feel free to tip if this solves your problem or if you find this useful.  BTC Address:  1HyBKPMAQKag3vGyHaa9TwkEzu5CCFWXAC

Here is a link to another one of my posts that describes my S1's problems.

https://bitcointalk.org/index.php?topic=579769

Let me know if this helped!  I spent a lot of time troubleshooting and doing research to fix these problems!

Here is my update since the original post.

I bought a new Western Digital N900 dual-band router which arrived at my door an hour ago.  It should be a lot better than my 5 year old Linksys WRT120N.  I went with the Western Digital N900 because it comes with 7 gigabit Ethernet ports, compared to the standard 4 (something you might want to consider if you're a fellow miner).  I configured the new router and continued to run all 4 units through the switch, which is plugged into 1 router port.  HW errors popped up almost instantly on all four units at the same rate as the old router.  So just for fun, I tried plugging unit 4 directly into the router.  It had the same HW error % as it did through the switch.  So my old router/networking doesn't seem to be the problem.

          - I'd also like to note that both the green and orange Ethernet port lights blink intermittently on units 1, 2, and 4.  The orange light on unit 3 stays solid.  All three of my buddy's S1's also had solid orange.
          - Unit 3 is still slower with a higher HW % than unit 4, even though the orange light on unit 4 blinks.

The temperature on the units normally run between 43-47, but I've seen them as high as 49 on warmer days.  Is that an acceptable temperature range?  (I know that video cards can run a lot hotter than that).  They are directly next to a window with great air circulation, so I still don't believe that over heating is the issue here.  Ambient room temperature is 65-75 degrees depending on the outside temperature.  I have the units set up in the guest bedroom on the dresser and just keep the window open.  Haha

I also increased the timeout from 35ms to 36ms and saw no difference.  I guess i'll try 37 and 38 to see if that helps, but I don't think that's going to do anything.

So basically after all of the methodical troubleshooting, I'm back to number 5 on my list from the original post.
          
          "5) I know the S1's are rated at 180-205 gh/s depending on the frequency with a +/- 5% rating. Are units 1 and 2 just slower?

           -192 and 196 gh are within that -5%.  But I doubt that's the issue considering I'm getting lots of hw error."

I guess all S1's are not created equally and it's the luck of the draw.  My buddy must have been really lucky because he's up to 9 units and only one of them gets HW errors like all 4 of mine.  I'm not a BTC veteran by any means, but I hope this troubleshooting process helps other S1 owners and newer miners out there.  Here is some other useful information for everyone:

1)  You can run three overclocked S1 units at 400 MHz off of one Corsair atx1200i platinum Power Supply.  My buddy uses this setup and has three PSU's for nine S1's.  His units run better than mine...

2)  Slush's Pool has significantly outperformed BTC Guild over the 3 week period in which I've been mining.  I have two S1's on each pool and my total rewards are as follows.
          - .59 BTC from Slush's Pool
          - .49 BTC from BTC Guild

Once again, I hope this thread is helpful.  I'd still appreciate any help or possible solutions to my problems.  I'll post another update in the future to let you know if cleaning the heatsinks helped any of my S1 issues.  If I somehow helped you in any way and would like to tip, or if you're just a mining kingpin baller making 100's of BTC a day and want to throw some at me; Here is my wallet address:

1HyBKPMAQKag3vGyHaa9TwkEzu5CCFWXAC

Thanks!


          

So I bought 4 Antminer S1's and have been running them for about a week.  They are all version 1.5 with a date of 2013/12/16. All 4 are plugged into one switch which is plugged into 1 router port. Each pair is connected to a brand new corsair rm1000 gold 80 PSU. The first thing that I did was overclock them to 400mhz and let them run for a full day. I got multiple asic chip errors on 3 out of the 4 units.  So I then reflashed them with the newest .bin file which claimed to have bug fixes for asic chip errors and hw errors.  That seemed to work because now I have all 00000000 on all four units. I let them run for another day and this is what I found:

Unit 1   196 gh avg   hw errors 5%
Unit 2   188 gh avg   hw errors 9%
Unit 3   200 gh avg   hw errors 2%
Unit 4   200 gh avg   hw errors 2%        I'm using the formula (Hw / DiffA+DiffR+Hw) * 100 to get the percentage.

This HW error rate seems to be unacceptable.  My buddy is running 3 S1's at 400mhz and all are at or over 200 gh avg and has next to 0 HW errors - like 30 after running them for 9 days opposed to my 50,000 - 500,000 hw depending on the machine.  So I have a lot of questions for any experienced people out there, but I want to first tell you what I did.

So unit 2 was giving me the most problems (hw error).  So what I did was back it down to 393 MHz, then I got a 191 gh avg with 4% hw error.  Then after another day, I backed it down to 387mhz and got roughly a 191 gh avg with 3% hw error.  Then repeated the process again and ran it at 381 mhz and got a 192 gh avg with about 2% hw error.  If it's only going to run at 192 gh, I might as well run it at 381 MHz opposed to any of the higher frequencies.  I also lowered unit 1 to 393mhz and I'm still getting a 196 gh avg with about 2.5% hw error.  So now for all the fun questions...

1) What does the hex frequency actually do? I mean the first line when changing the frequency. '0781' or '5f81' ect.

     -I was told that some people keep that the same for frequencies between 350mhz and 400mhz.  Can a bad combo be causing my problems? I used this combo on all 4 units at first.
     #option 'freq_value' '4f81' #205GH
     #option 'chip_freq' '400'
     #option 'timeout' '35'

2) I have an older router which is about 4-5 years old.  I know that it randomly resets at times.  I'm sure that this can lead to hw errors.  But wouldn't it affect all 4 machines equally, not just units 1 and 2? 

      -I tried plugging unit 2 directly into the router instead of the switch and still got a 188 gh avg at 400mhz, so I've ruled out a bad switch.

3) Units 1 and 2 are setup to run on Slush's Pool while units 3 and 4 are setup on BTC Guild.  Does a pool affect hw error?

     -I'm assuming that it is just a coincidence that units 1 and 2 are running slower, the pool prob isn't doing it because my buddy's S1 on slushes pool has low hw errors .01% and good hashrate 200+

4) Units 1 and 2 are hooked up to their own brand new PSU and units 3 and 4 are on their own brand new PSU.  Both came from newegg and seem to be running just fine.  Is the PSU for units 1 and 2 worse than the other one? Can this be the problem?

     -I doubt that the PSU is the problem.  All my cables are connected properly.

5) I know the S1's are rated at 180-205 gh/s depending on the frequency with a +/- 5% rating. Are units 1 and 2 just slower?

     -192 and 196 gh are within that -5%.  But I doubt that's the issue considering I'm getting lots of hw error.
     -My temperatures are all between 43-47, so I don't think that overheating is the issue.

6) When logging into the antminer interface, auto refresh is on. The only screen that doesn't seem to auto refresh is the miner status screen. How can I fix this?

     -This is just a pain, because I have to click the tab each time that I want to see the new numbers.  The auto refresh at the top left is not present next to the load numbers (only on the miner status tab!). So I can't even change it to on/off. (all 4 units have this prob)

I'm basically new to the whole btc mining game and would appreciate any advice from seasoned veterans out there.  As you can see I've done my homework and know a good amount about computers, but I need your help on this one.  Thanks!