Passer au contenu

Nous améliorons nos opérations pour mieux vous servir. Les commandes sont expédiées normalement depuis Laval, QC. Questions? Contactez-nous

Bitcoin accepté au paiement  |  Expédié depuis Laval, QC, Canada  |  Soutien expert depuis 2016

ERR_LOW_HASHRATE Warning

Antminer S9 – Low Hashrate

Low Hashrate on the Antminer S9 — realized hashrate persistently below nameplate (`13.5 TH/s` stock), usually driven by missing ASICs on one or more chains (`Chain[X] find 62/58/0 asic`), dried thermal paste, dropped heatsinks, PSU rail sag, or degraded stock firmware profile. Stock Bitmain firmware under-reports the true cause; per-chip visibility via DCENT_OS or Braiins OS+ is the fastest diagnostic upgrade.

Warning — Should be addressed soon

Affected Models: Antminer S9, S9i, S9j, S9k, S9 SE — any S9-class control board running 3× BM1387 hashboards (63 chips per board, 189 total), paired with APW3 / APW3+ / APW3++ / APW5 / APW7 Bitmain PSUs

Symptoms

  • Dashboard realized hashrate 5-30% below nameplate (stock S9 target `13.5 TH/s`) sustained 30+ minutes
  • `kern.log` reports `Chain[X] find N asic` where N < 63, or `check_asic_number_with_power_on: Chain[X] find N asic` at startup
  • ASIC# grid on stock Bitmain dashboard shows red Xs or blanks on specific chip positions within a chain
  • One hashboard runs 5-10 °C cooler than the other two (dead chips produce no heat — counterintuitive but diagnostic)
  • One hashboard runs noticeably hotter than the other two (remaining chips compensating, or dropped heatsink / paste failure localized to that board)
  • Pool-reported hashrate lags local dashboard by >15% over a 24-hour window (stale shares from silently-failing chips)
  • Hashrate drops gradually over weeks or months (chip aging, thermal paste drift, voltage-domain cap degradation)
  • Hashrate drops suddenly after a power event, move, or firmware update (ribbon unseated, chip knocked loose, config corrupted)
  • Intermittent hashrate dips every evening or whenever another load starts on the shared circuit (PSU sag under load)
  • Heatsink visibly loose, rattling, or misaligned on one hashboard (shipping damage, thermal-cycling failure of adhesive)
  • Hashrate recovers at cold boot then decays within 20 minutes (thermal throttle driven by paste / airflow / ambient)
  • Fan RPMs maxed constantly even at ambient `≤25 °C` (firmware compensating for chips reporting abnormally high temps)
  • On DCENT_OS / Braiins OS+ / LuxOS (if flashed): chip positions flagged red or voluntarily disabled

Step-by-Step Fix

1

Hard power-cycle the miner. Switch the PDU off, wait 60 seconds for bulk caps to drain, switch back on. Not a soft reboot — a physical AC cut. Clears any wedged driver state that can follow a firmware update or a PDU trip. Watch the dashboard for 15 minutes afterward. If hashrate returns to nameplate, you were chasing a ghost and a clean power cycle fixed it. Zero tools, 90 seconds.

2

Revert the firmware profile to stock. Hold the physical reset button for 5 seconds within the first 2-10 minutes after boot, or reset to defaults via the UI. Stock S9 profile: 600-650 MHz frequency, ~1350 W wall target. Observe hashrate for 15 minutes. If it recovers to ≥13 TH/s, your previous config was over-tuning and you'll rebuild OC slowly in Tier 2. Costs nothing and rules out software before you touch hardware.

3

Clean the intake filter and blow out the chassis. 30-day dust buildup alone costs 5-10% hashrate via airflow restriction (CryptoMinerBros operator data). Shop-vac the intake, blast the hashboard fins with compressed air (keep the nozzle 15+ cm away — close-range air can spin fan blades fast enough to generate back-EMF that damages the fan controller), and wipe the intake grille. Monthly cadence is the cheapest hashrate insurance on the S9.

4

Verify intake ambient `≤30 °C`. Point an IR thermometer at the front of the miner, not the room middle. If ambient at the intake is above `30 °C` the miner is thermal-throttling whether you've noticed or not. Improve airflow, duct intake from a cooler room, or move the miner. This alone can recover 5-15% hashrate in a hot garage in summer.

5

Confirm pool + stratum config and verify pool-side hashrate. Log into your pool account. Compare its 24-hour reported hashrate against your dashboard. Clean miner gap is ≤2-3%. Verify stratum URL, port, worker name, wallet address. If you're pointed at a geographically distant pool (Canadian miner → Singapore server), switch to a regional endpoint — 200+ ms round-trip costs measurable shares (Solo Satoshi data).

6

Probe the 12 V rail under load. Multimeter on DC, yellow to probe red, black to probe black at a hashboard's 6-pin PCIe connector while the miner hashes at full power. Expect 12.0-12.6 V steady. Sag to 11.6-11.8 V = PSU tired, circuit undersized, or low line voltage. Measure panel voltage: 235-245 V on 240 V split-phase, 202-212 V on 208 V commercial, 110-125 V on 120 V. A 15 A 120 V circuit cannot reliably feed a 1350 W S9 under shared load.

7

Re-seat every ribbon, power connector, and the PSU signal cable. Power off at the PDU. Disconnect each 2×14-pin hashboard data ribbon, each 6-pin hashboard power cable, and the 6-pin PSU-to-control-board signal cable. Inspect for blackening, oxidation, bent pins. Wipe contacts with a cotton swab + 99% IPA, let flash off 30 seconds, reconnect firmly. Clears a large slice of 'mystery hashrate drop' tickets on the D-Central bench.

8

Re-seat or re-glue loose heatsinks. Open the chassis, visually inspect each hashboard's heatsink array. Any heatsink that moves under finger pressure, sits at an angle, or rattles when you shake the board: re-attach with Arctic Alumina Thermal Adhesive or equivalent. Let cure 24 hours before powering up. This single fix recovers 1-2 TH/s on boards where a heatsink sheared off a hot chip under shipping vibration — a well-documented S9 pattern.

9

Rebuild OC slowly. Start at stock 600-650 MHz. Increment +10 MHz per step. Observe hashrate + HW% for 10 minutes between steps. Stop one step before HW% crosses 2% or a chip position goes red. Each S9's BM1387 silicon-lottery ceiling is different — no two S9s tune identically. Past the sweet spot, effective hashrate DROPS despite higher reported MHz because errors cost more than clock gains produce.

10

Swap hashboards between slots to isolate board-vs-slot faults. Label slots 0/1/2 with tape. Move the suspect board (per Step 1's chip count or Step 4's thermal anomaly) to a known-good slot. If the fault follows the board = bad board, move to Tier 3 or 4. If the fault stays in the slot = control-board-side issue — check the ribbon connector on the CB end for damaged pins, burned traces, and confirm the 3.3 V rail is feeding that slot.

11

Refresh thermal paste on all 189 chips + re-pad the PCH and voltage-domain ICs. Pull each hashboard. Lift the heatsinks (they're glued — use a thin plastic shim, warm the board to 50-60 °C first to soften adhesive). Clean old paste with 99% IPA + lint-free wipes. Apply Arctic MX-6 or Thermal Grizzly Kryonaut: grain-of-rice dot per chip, heatsink replaced and clamped. Replace crumbled thermal pads on PCH and voltage-domain FETs with 1 mm silicone pads. Highest-value Tier-3 fix — 8-12% hashrate recovery typical on aging S9s.

12

Reflow the worst-offending BM1387 chip(s). If Diagnostic Step 1 identified missing chips and IR thermal showed hot-spots at those positions, flux the chip underside, preheat the board to 150 °C from below, hot-air the chip at 300-320 °C for 30 seconds. BM1387's QFN package tolerates a reflow cycle (Zeus Mining workflow). Re-paste, reinstall heatsink, retest. Reflow resurrects roughly 30% of 'dead' BM1387s that are actually cold solder joints rather than silicon failures.

13

Replace a dead BM1387 chip. If reflow doesn't restore the chain's `find 63 asic` count, desolder the dead chip with hot air (320-340 °C, plenty of flux), clean pads with solder braid + flux, drop a new BM1387 (salvaged `CAD $3-8`, new-old-stock `$15-25`), reflow at 300-320 °C, re-paste, reinstall. This is where Zeus's '1+ year QFN experience' gate earns its place — easy to damage adjacent chips or lift pads if new to QFN rework. Practice on scrap boards first.

14

Cap / MLCC audit on the voltage domain. Inspect the small MLCCs and electrolytics around the voltage-domain FETs on each hashboard. Any bulging electrolytic, cracked MLCC, or visibly burned component gets replaced with spec-matched parts (soldering iron + hot air). Voltage-domain cap failures cause silent hashrate drift months before the board gives up entirely — catching this during a paste refresh extends board life by years.

15

Refurbish the APW3++ PSU if Step 6 of Diagnostics showed sagging 12 V rail. Pop the PSU lid (6× Phillips #2 around the perimeter). DISCHARGE THE PRIMARY-SIDE BULK CAPS WITH A 1 kΩ RESISTOR BEFORE TOUCHING ANYTHING — they sit at 350-400 V DC for minutes after unplugging. Replace the two 450 V 220 µF bulk electrolytics with Rubycon YXF or Nichicon PW equivalents (same 450 V voltage, same-or-higher capacitance, 105 °C rated). Fixes the 'evening hashrate sag' pattern on 8-year-old APW3++ units.

16

When to stop DIY: you've isolated a bad hashboard to the board itself (fault follows the board across slots); per-chain chip count is `< 60` with multiple chips needing replacement; you see voltage-domain damage, burnt components, cracked MLCCs in bulk; or you're staring at a 450 V DC bulk cap with no bench gear to discharge it. Stop, bag the board, book D-Central ASIC Repair. BM1387 QFN rework without preheater + decent hot-air station costs more than it saves.

17

D-Central bench process: full thermal image of each hashboard under load, per-chip voltage and temperature scan, IR-guided failure-candidate identification, reflow-first policy (replace chips only if reflow fails a second pass). PSU work: load bank, ESR meter on every cap, thermal chamber burn-in. All repairs get a 24-hour nameplate burn-in before we sign off. Cost range CAD $85-225 per hashboard, CAD $85-175 per PSU, CAD $125-250 for hashboard replacement from salvaged-grade inventory.

18

Pack safely, include a ticket note. Anti-static bag each hashboard. Double-box with ≥5 cm of foam on every side. Include a printed note with observed symptoms, kernel-log excerpts (copy-paste from SSH), firmware version string, date last worked, and what you've already tried. Every line saves D-Central diagnostic time and your repair dollars. Intake form: d-central.tech/services/asic-repair/. Turnaround 5-10 business days from receipt. Canada / US / 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.