Hash Board Consolidation: Building Whole Miners From Partial Ones Without Wrecking Them

A site with forty miners each running on two boards is losing a third of its hash rate. Move the working boards around and you have twenty-six full machines and fourteen empty chassis waiting for repair — the same hardware, hashing better and drawing power more sensibly. That is consolidation, and it is a routine part of maintenance once you have enough units with similar parameters. The catch is that similar has a precise meaning, and getting it wrong produces error codes at best and burnt boards at worst.

Chip binning: why boards are not interchangeable

Chip binning is the quality-control step every semiconductor maker uses: after fabrication, chips are tested and sorted — binned — by performance, power efficiency and stability. Chips off the same wafer, made by the same process, do not all perform identically, and the bins let the maker sell them at different price points under different names. Intel's i9, i7, i5 and i3 are the familiar example.

ASIC miners are built the same way. A hash board is populated with chips from one bin, the boards in a unit are matched, and the firmware tunes the unit around that bin's frequency and voltage envelope. Put a board from a different bin next to two others and the firmware is tuning three boards to one target that only two of them can hit. Good consolidation considers the bin, not just the model.

Whatsminer: the matching checklist

Work down the list in order. Every line has to match before you move to the next; the last two are where most mistakes happen.

• Same model and variant — e.g. M30S++_VH10. See our machine types reference for why the variant is part of the name.
• Same ASIC type — e.g. 1960.
• Same chip count — from WhatsMinerTool or the board label; anywhere from 64 to 294 chips depending on the board.
• Same or similar terahash rating — from the machine label, e.g. 106T.
• Then check the chip BIN numbers match — a 1960-01D board goes with another 1960-01D of the same TH.

Reading the board: domains and chips per domain

The chip count is printed on the board itself. On the intake side, next to the boost controller, you will find a marking like 39x4 or 35x2 — domains × chips per domain. 39x4 is a 156-ASIC board; 35x2 is a 70-ASIC board. Two boards with different markings are not the same board, whatever the model says.

Reading chip_data

The firmware records each board's serial and chip batch. Pull it from the status page or the API and you get three pcb lines and three chip_data lines. A factory unit looks like this:

Three consecutive board serials and three identical chip batches — that is how a unit leaves MicroBT. Now two consolidated units, one done right and one done wrong:

In the good unit the boards came from three different batches — the prefixes and date codes all differ — but every one reads BINVE5. In the wrong unit, board 2 reads BINVE6. One character, and it is the character that matters: that unit is running a mixed bin and will show it in the error log sooner or later.

Out of warranty only

Verify the miners are out of warranty before consolidating. The serial-number check takes a minute per unit. And keep in mind that a Whatsminer board can be repaired about 98% of the time — consolidation is how you keep hashing while the bad boards go to the bench, not a reason to write them off.

Antminer: same idea, different label

Antminer consolidation follows the same logic with one extra reason to do it: on the aluminum-board models, a unit stops working completely if one board is faulty. There is no running on two boards — so moving a good board in is the quickest way to restore hash rate and balance site load.

• Out of warranty only — the same rule applies.
• Typically, swapping boards between the same model is sufficient. Check the model version on the machine label — BHB42601, for example — and match it.
• Mismatched models cause an error and the machine will not hash. It fails safe, which is better than the Whatsminer case, but it also means a wrong match is a wasted rack visit.
• Occasionally a technician needs a PICkit, a code editor and/or an ARC tester to make boards match up and start hashing — when the boards are physically compatible but their EEPROM data disagrees.

Reading the Antminer board

Bitmain prints what you need in the corner of the board and on its label:

• Chip layout — 38X3_Hashboard_V1.0 is 38 domains of 3 chips, 114 ASICs.
• BIN — the label carries it, e.g. S13X20BJ1Q BIN4. Match boards with like bins for stable performance.
• Temperature sensor type — e.g. TMP75A. Boards with different sensors report differently and should not be mixed.

Often it is one board in a unit that goes unstable and burns up. With enough machines and boards on site, that unit's two good boards are your consolidation stock.

A consolidation routine that works

• Pull chip_data (Whatsminer) or read the labels (Antminer) for every board on site once, and keep it in your records with the serial number.
• Group boards by model, variant, chip count and bin before anyone touches a chassis.
• Check warranty status on every unit you plan to open.
• Consolidate within a group only. Label the empty chassis with what came out of it.
• Send the removed boards for repair in a batch, with the records — it makes the quote faster and the turnaround shorter.

Boards that will not match, or a stack to repair?

Send us the chip_data or label photos and we will tell you which boards can go together and which need the bench. We repair Whatsminer and Antminer hash boards in Chicago, with a 30-day guarantee on the work — contact us.