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?
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?
You also could do nothing and just let it hash at 402GHs. The extra 30GHs isn't probably worth the downtime and effort. 30GHs is worth $0.46 per day at the current difficulty/price.
freq 212.5 takes 2 minutes with a ssh in. It has done wonders for my 2 machines
see charts I have stayed at 430gh
note that drop off was a power outage last night due to a T-Storm. These 2 units are in an office building. I have no direct access during non business hours. what I love about s-1's and s-3's
is they reboot and fire back up working after black outs no attention or effort on my part. Note after the blackout I am back to 430gh
I'm going to try the 212.5 freq as you suggest. I see over 8 hours or so they slip to 430. If that's where they want to be then I don't want to waste the extra power trying to keep them at a speed they can't handle.