Topic: S7 Batch 8 miner not hashing 100% (Read 2364 times)

I have S7 Batch 8 with the identical problem.
Do you have any updates, guys

Hey guys,

I had exactly the same problems as described here.  I have one S7 Batch 8 and 2 S7 Batch 9.  It is one of my Batch 9s that was causing me the trouble.  After a lot of diagnostic tech support with Bitmain I decided to create a little diagnostic page to help figure out if you have a bad hashing board or not, and if so which one.

You can view the guide, with pictures here:

http://stevegrundy.blogspot.com/2016/06/antiminer-s7-issues-and-diagnostics.html

I also think batch 8 may be bad too, I do have 2 x S7`s from batch 7 and the be hashing great, no problems, my 3 x S7`s from batch 8 are different story, 1st S7 averages at 4.40 TH which is more than the 5% variance stated on Bitmain`s website, 2nd S7 is the problem one with chain 2 which started crashing cgminer and affecting other chains so switched the miner off, waiting for the hosting company to goto the DC to see if the 2 other chains are now "faulty" too , 3rd S7 hashes fine to which is making up for lower hash of the 2nd one to make average for the 2 within the 5% variance.

I have emailed Bitmain and received a quick reply literally within 5 minutes requesting order #, screenshot of miner status and psu details to which i replied but now as its holiday there so have to wait till Monday. My support tickets is still unanswered.

Will see if the frequency change works, to confirm "overclocking" for batch 8 would be saving the frequency higher than 700, so if it was saved at 675/650, saved, rebooted and then changed to 700 that would not be classified as "overclocking", is that correct?

You should email Bitmain ( [email protected] ) and see what they advise, unfortunately sounds like you may need to RMA you unit 

Alright i will keep all of this in mind in the following weeks, i ordered a B8. I hope to be able to do some good tests and to get a reliable unit, but we'll see.

yes i believe it could be a "bad" batch or it could just be random bad luck for me & others.

I had 2xs7 b8, both of them were mining fine for abt 8 hrs or so but then"

1 of them showed 0 temp & 30 ASIC chips with dashes

the other hashrate dropped & lots of HW errors appeared

solution, i manage to identify which board that was giving me problems & unplugged them from the controller & PCIE (PSU)

the board with 0 temp is easy to identify, the other board that have a low hashrate with lots of HW error was tested individually by just powering each board.

both problematic board were on chain #1 (far right) from front of the miner (LAN jack)

snapped pix with diagnostics by BMT, emailed them but waiting for reply.

I had a b5 board that went nuts too, got a reply within 24hrs, authorised to remove the board to check & send it back to BMT (china). It took about 11 days to reach them due to holidays & weekends + china customs delay.

tried couple of things like phil mentioned. all my psu's are in great working conditions but i even swapped them around n tested them.

if you think that u might have a bad s7, i'd suggest to try to identify them by just plugging only 1 board to the controller & PCIE (PSU) REMOVE the other 2 controller cable & PCIE (PSU).

3 of my s7's (1 b5 & 2x b8) are running with 2 boards & they're running great.

also if you see lesser ASIC chips after a hard or soft reboot, goto miner config page, change the freq, hit save & apply, the chips would be back then change it again to your desired freq. (OC'ing VOIDS your warranty)

hope this helps others too.

This post right here honestly worries me. There are quite a lot of S7 problem being reported and i'm looking into buying some. When that get combined with delay, mining time lost, extra cost to ship part back and poor communication/high delays on Bitmain's part, i am wondering if this is a sound investment.

Maybe Batch 8 itself is simply a bad batch?

I opened a support ticket but still no reply yet, will try emailing them.

Thanks for the tips

I had the same problem when i changed the payment type.. I tried more than ten times turning off and turning it on again..
Try to reset the miner..

okay I do not see any images.

but 1 simple question what is your psu?

Hello i have a similar problem

I recently bougth a Antminer S7 Batch #8 this miner have been instaled just a few days ago and i have serious troubles operating it.

When i recived it, the hash rate success the 4700 GH/s but latter that day it dropped to 3900 GH/s, this is almost 1000 GH/s below the indicated. Then i move the miner to another location there the hash rate was even lower around 2900 GH/s. In view of this i decided return it to the firts location where it was and i reset to default the antminer in the panel of control but my problem was scalating and now the miner is working below 1300 GH/s.

I have noticed in the miner status the temperature of the hash boards 1 and 3 es really low, below of the 40 degrees each (img1 attached). Also attach images of the miner instaled

I have tried to change the PSU unit and the cables of the PSU but nothing seems to work.

I would appreciate any help or guidance you can provide me to solve my problems.

Phil gave great instructions on trouble shooting.  I would also suggest putting in a ticket or email to Bitmain to get ball rolling incase you do need a replacement hashing board.

I would guess they send a list to do aswell. If you wait on getting it to them you might have longer down time (that is if it cannot be fixed which hopefully it can without needing a new hashing board).

well hopefully it is your psu or your psu pcie cables.

This type of problem indicates a non working board.

Needs a hands on fix.


1) pcie cable worked loose on s-7 side easy to fix >>>>>>>>>>>>>>>>reseat it
2) pcie cable worked loose on the psu side easy to fix. >>>>>>>>>>>>> reseat it
3) the psu is atx multi rail and a rail died  >>>>>>>>>>>>>>>>>>>>> need a better psu
4) the server psu has a defect in the break out panel>>>>>>>>>>>>>>> need a new breakout  panel
5) the 18 pin cable from board to controller worked loose  easy to fix >>>> reseat it
6) a bad pcie cable >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> replace it
7) a bad 18 pin cable >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> replace it ------- BTW I have an extra one

8 ) bad controller jack you are  in need of an rma

9) bad hash board you  are in need of an rma ---------- I believe j4bberwock would buy the board he is in France and has mad skills in electronics

link to his profile

https://bitcointalksearch.org/user/j4bberwock-206446

Hello
I have a problem with a S7 from batch8 and was hoping someonce can help?
My 1 miner was initially mining fine on Antpool at the expected hashrate, I then changed it to Cadence`s P2Ppool and the hashing was really bad so changed back to Antpool, but now the miner is only hashing at about 3TH instead of around 4.73TH.

Have updated the firmware and power cycled the miner numerous times, miner is at a remote DC so checking if a power off for short while and power back on has been done and will update this thread once I know, below is from the log, chain 1 and 3 are working fine, on chain 2 only 31 chips are live  .

  559.496729] chain2 reg crc_r{0x16}crc{0x13} Err ret{0x80d1c2ff}
[  559.502998] asic cmd return 80d1c2ff
[  559.506741] chain2 reg crc_r{0x16}crc{0x13} Err ret{0x80d1c2ff}
[  559.512931] asic cmd return 80d1c2ff
[  559.516676] chain2 reg crc_r{0x16}crc{0x13} Err ret{0x80d1c2ff}
[  559.522862] asic cmd return 80d1c2ff
[  559.526609] chain2 reg crc_r{0x16}crc{0x13} Err ret{0x80d1c2ff}
[  559.532804] asic cmd return 80d1d189
[  559.536555] chain2 reg crc_r{0x1f}crc{0x64} Err ret{0x80d1d189}
[  559.542742] asic cmd return 80d1d189
[  559.546489] chain2 reg crc_r{0x1f}crc{0x64} Err ret{0x80d1d189}
[  559.553708] asic cmd return 80d1d189
[  559.557496] chain2 reg crc_r{0x1f}crc{0x64} Err ret{0x80d1d189}
[  559.563686] asic cmd return 80d1d189
[  559.567433] chain2 reg crc_r{0x1f}crc{0x64} Err ret{0x80d1d189}
[  559.573610] asic cmd return 80d1d189
[  559.577351] chain2 reg crc_r{0x1f}crc{0x6c} Err ret{0x80d1d189}
[  559.583550] ch2-as33: dev->task_buffer_wr{0x00000923}rd{0x00000d23}ret
work_id{0x8d11} don't match task_buffer_match{0x0d11}
[  559.596043] ch2-as33: dev->task_buffer_wr{0x00000923}rd{0x00000d23}ret
work_id{0x8d14} don't match task_buffer_match{0x0d14}
[  559.607863] ch2-as8: dev->task_buffer_wr{0x00000923}rd{0x00000d23}ret
work_id{0x8cf3} don't match task_buffer_match{0x0cf3}
[  559.619713] asic cmd return 80117e0f
[  559.623482] chain2 reg crc_r{0x1d}crc{0x2b} Err ret{0x80117e0f}