Antminer S19 – Low Hashrate (Missing ASIC Chips)
Warning — Should be addressed soon
Symptoms
- Miner status / kern.log shows `Chain[X]: find NN asic, expect YY` with NN < YY
- One or more chip positions render as `x` / `X` / red square in the per-chip grid
- Realized hashrate reads 5-25% below nameplate while miner reports online
- Pool-side accepted hashrate trends below dashboard-reported hashrate
- Missing-chip count stable across reboots (hardware) or drifts between boots (cable / intermittent)
- `cgminer` / `bmminer` log contains repeated `check_asic_number_with_power_on` lines on the affected chain
- One chain reports lower chip count than the other two (e.g. 76/76, 76/76, 74/76 pattern)
- Per-chain temperature on the affected board climbs 2-5 C vs its siblings
- Two adjacent chip positions missing together (domain-boundary pattern, e.g. positions 37 + 38)
- DCENT_OS / Braiins OS+ / LuxOS / Vnish flags Pattern NG or elevated HW% on the missing chip's immediate neighbours
- Chain count changes after firmware update or profile change (points at software / tuning, not hardware)
Step-by-Step Fix
Hard power-cycle the miner: kill power at the breaker or unplug the PSU for 30 seconds, not 5. Power back up and wait 3 minutes for chain enumeration to complete. Check `kern.log` for the new chip count. Cold-boot enumeration glitches clear on the next power-on roughly 12% of the time on S19-class hardware per D-Central's repair-queue data. This is the cheapest, fastest first move and costs nothing - always try it before opening the lid.
Revert to stock firmware profile: no overclock, no undervolt. Reset to factory defaults in web UI -> Configuration -> Advanced. Reboot. Observe `kern.log` for 15 minutes. Aggressive overclock or undervolt can push a marginal chip below its detection threshold at boot; clearing the profile brings it back. If this restores the chip count, rebuild tuning slowly with +100 MHz increments, stopping one step before any chip drops.
Check for firmware updates on the Bitmain support portal or your third-party firmware's release page. If you are on a known-buggy build for your hardware revision, update. If you are already current and the chip-drop is recent, roll back one version - firmware regressions on S19-class boards are real. Always verify hardware-revision compatibility before flashing; wrong-revision firmware bricks the control board.
Verify intake ambient temperature with an IR thermometer at the front grille, not room center. Target <= 35 C. High ambient pushes marginal chips past their detection margin at boot. Clean the intake filter, clear obstructions within 15 cm of the front, and if the miner is in a hot room, relocate or ventilate before moving on. Sounds dumb - works surprisingly often on summer-season chip dropouts.
Document the exact pre-repair state: per-chain chip counts, firmware version, dashboard hashrate, and a photo of the per-chip map. You are about to open the miner and make changes - write down the baseline so you can verify improvement after each step rather than chasing a ghost.
Power off at the breaker, open the lid, and reseat every ribbon cable between control board and hashboards. Inspect contacts for corrosion (green/black tint), bent pins, or blackening. Clean with 99% isopropyl alcohol on a lint-free wipe. Reseat firmly - listen for the click. Reassemble, boot, recheck. Connector oxidation is one of the top-two failure causes on miners kept in humid basements or unheated garages.
Swap ribbon cables between the short chain and a known-good chain on the same miner. Label them first. Boot. If the missing-chip count moves to the chain where you swapped the cable to, the cable is bad - replace with a known-good. This is a $0 diagnostic if you have a spare S19 or a spare cable on the shelf.
Label the three hashboard slots 0 / 1 / 2 with tape. Physically remove the suspect hashboard and install it in a known-good slot, moving the corresponding cables with it. Power up. Fault follows the board -> the board is the problem. Fault stays in the slot -> the control board or slot connector is the problem. This 10-minute test narrows the field dramatically before you commit to chip-level work.
Multimeter on DC, measure PSU output at the hashboard power connector under full hashing load, not at idle. Expect 13.8 V sustained on the standard S19 rail. Sag below spec points at a tired PSU, undersized circuit, or low line voltage - any of which can cause domain instability that presents as missing chips. Swap PSU with a known-good unit to isolate.
Re-tune any custom overclock from stock in small steps: +100 MHz at a time with a 10-minute stability window, watching `kern.log` for chain-count drops. Stop at the step before a chip drops out. That is this specific miner's silicon-lottery ceiling. No two S19s have the same ceiling, and pushing past it is the direct cause of missing chips at boot on tuned rigs.
Flash DCENT_OS - D-Central's open-source Antminer firmware, the Mining Hackers' option. Per-chip HW%, per-domain voltage readouts on supported revisions, tuning and autotuning, Stratum V2. Alternatives: Braiins OS+, LuxOS, Vnish. All four expose per-chip and per-domain diagnostics that stock firmware hides. Let the miner stabilize 20 minutes after flashing and open the per-chain chip map - dead chips render as red or grey, flaky chips show elevated HW%.
Multimeter to the 0.36 V domain test points (silkscreened on the board, or per the Antminer S19 hashboard repair guide dichotomy method - probe RO and 1.8 V between the 38th and 39th chip on a 76-chip / 38-domain S19 board). A healthy domain reads 0.33-0.38 V under load. A collapsed domain reads 0 V or wanders. Collapsed domain = MLCC / electrolytic / boost diode / PMIC failure in that domain - bench repair territory.
Reflow the flagged chip: preheat bottom-side to ~150 C, apply flux to the target BGA, hot air top-side at 310-330 C for ~30 seconds, let it cool naturally, re-paste the heatsink with Arctic MX-6 or Thermal Grizzly Kryonaut, reassemble. BM1398 / BM1362 / BM1368 tolerate a single reflow cycle well. Roughly 50% of Pattern NG failures fix with a clean reflow; the other 50% need the chip swapped.
If two adjacent chip positions dropped together (e.g. 37 + 38 on a standard S19 board), inspect the shared voltage-domain components: MLCCs near the domain cap bank, the boost diode, and the domain PMIC. Bulging or discoloured caps = replace. Cracked MLCCs = replace. Use a hot-air station and leaded solder to minimize risk to adjacent BGAs - lead-free reflow temps can reflow nearby chips unintentionally.
Reflash the hashboard EEPROM with Bitmain's hash board code editor if `kern.log` hints at `ERROR_EEPROM_INFO`. Back up the existing EEPROM dump first. Verify your exact hardware revision against the firmware hardware table - wrong-version flash bricks the board. If you are not 100% confident on hardware matching, ship to D-Central instead of flashing blind.
Stop DIY when: the same chip position fails on two different boards after a clean reflow (PCB-level fault, not chip-level), a voltage-domain IC or PMIC is suspected and you lack a PT2 fixture, you see capacitor bulging or a burnt-component smell, or the fault stayed in the slot during the board-swap test. Any of these means professional bench diagnosis costs less than the parts you are about to damage. Book a D-Central ASIC Repair slot.
At the D-Central bench the board goes on a PT2-class test fixture with programmable load, per-chip isolation runs against Bitmain's official test binaries, failing chips are replaced with graded BM1398 / BM1362 / BM1368 from salvage and new-old-stock inventory, the board gets a full reflow and reseal, and we run a 24-hour nameplate-load burn-in before shipping back. This is the work you cannot replicate on a kitchen table.
Ship safely: anti-static bag per board, double-box with at least 5 cm of foam on every side. Include a note with observed symptoms, firmware version, chain count pattern (e.g. `Chain[1]: find 74 asic, expect 76`), and your contact info. Detailed symptoms shave diagnostic time off the bench clock, which directly reduces your repair bill. Canada-wide shipping; US and international welcomed.
When to Seek Professional Repair
If the steps above do not resolve the issue, or if you are not comfortable performing these repairs yourself, professional service is recommended. Attempting advanced repairs without proper equipment can cause further damage.
Related Error Codes
Still Having Issues?
Our team of Bitcoin Mining Hackers has been repairing ASIC miners since 2016. We have seen it all and fixed it all. Get a professional diagnosis.
