OK, so one of my new S3 machines is hashing at 402.75Gh/s. Frequency is 218.75. One of the strings (if that is the word) is showing oooooxo-. Rebooting through the web interface, or physically power cycling doesn't fix it. Reading through this thread the suggestions are
1) Downclock to 212
2) Update firmware
3) Dismantle and replace thermal compound
Which of these is most likely to fix the hashing? Is there anything else I should try?
In order of what to do:
3 - clean it. Get rid of the crap thermal compound they spew all over the chips, screw holes and anywhere else on the PCB they can find to squirt the stuff. Properly apply good thermal compound to the ASICs and reassemble.
1 - clock it at 212. If after cleaning you restart your S3 and still get the "x" and "-", try taking a step down in the clocks. I have to do this with one of my S3s. It will not hash at anything about 212.5; however, it gets a solid 430GH/s at that clock.
2 - updating firmware will have no effect since the newest firmware only provided a fix of the random beeping problem.