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

HW_ERR Warning

Antminer S21 – ASIC Chip HW Errors

ASIC Chip Hardware Error Rate — BM1370/BM1380 chips returning nonces that fail re-verification at the control board; healthy S21 sits under 1.5% per chain, escalates to 3-8% without intervention.

Warning — Should be addressed soon

Affected Models: Antminer S21, S21 Pro, S21+, S21 Hydro, S21+ Hydro, S21 XP, T21

Symptoms

  • Dashboard HW% or per-chain Hardware Errors reads above 2% sustained for 30+ minutes
  • Realized hashrate is 5-15% below nameplate (200 TH/s stock, 234 TH/s Pro, 335 TH/s XP)
  • `kern.log` / cgminer shows repeated `HW error` or `chain X nonce error` lines
  • One of the three hashboards reports per-chain HW% clearly higher than the other two
  • Pool dashboard shows rejected or stale shares climbing while stratum is otherwise stable
  • Per-chain temperature drifting up 3-5 °C with no change in ambient
  • Audible high-frequency coil whine or tick from a specific hashboard during hash bursts
  • On DCENT_OS/Braiins OS+/LuxOS/Vnish: one or more chip positions flagged red or >15% HW%
  • HW% pattern: sudden after profile/firmware change, or gradual over weeks (aging/paste/caps)
  • Cyclical HW% spikes every evening (grid sag) or on warm afternoons (ambient creep)
  • Control-board log shows autotune adjust / freq-down loops that don't stabilize
  • Running on old S19-era 16A power cord or PDU (S21 requires new P13 20A standard)

Step-by-Step Fix

1

Cold-boot the miner: 30 seconds off at the breaker, not a UI restart. Clears wedged autotune state that S21 stock firmware can get stuck in after a profile change. Wait a full 4 minutes for the boot cycle to complete before reading HW%. This is genuinely different from a soft reboot — the S21 retains runtime autotune state across soft reboots, and the breaker cold-boot is the only reliable way to force a clean cold start of the firmware.

2

Revert to stock profile — remove all OC and UV adjustments. On stock Bitmain firmware: System → Miner Configuration → Restore Default. On DCENT_OS / Braiins OS+ / LuxOS / Vnish: load the factory-default preset. Observe 15 minutes of steady-state hashing. If HW% drops under 1.5%, your tuning crossed the silicon-lottery cliff — rebuild slower in Tier 2. If it stays elevated, the cause is downstream of tuning.

3

Clean the intake: shop-vac the front grille and filters, wipe with a dry microfiber cloth, verify the front 15 cm of the miner is clear of obstructions, curtains, or dust buildup. Dust on the intake raises inlet temp, which raises junction temp, which raises HW% on S21-class chips specifically — because they run closer to their Tj cliff than the previous generation. Check again at 90-day intervals as preventive maintenance.

4

Verify ambient temperature with an IR thermometer held 5 cm from the intake grille during steady-state hashing. Not room-middle. Not the hallway. At the intake. Target: ≤ 30 °C for standard S21; ≤ 35 °C for S21 Hydro. S21 tolerates higher ambient than S19 on paper but its HW% cliff is closer to the ambient limit — conservative ambient pays off on this generation.

5

Check firmware version. Note your exact Bitmain stock build. Cross-check against `service.bitmain.com/support/download` for newer or older stable builds for your specific hardware revision. Some early S21 builds shipped with autotune regressions that read as elevated HW%. If you're on a known-buggy build, roll forward (or back) to the next stable version — S21 firmware release notes are on the Bitmain support portal.

6

Measure PSU output under load. Multimeter on DC volts, probes at the PSU-to-board output connector while the miner is fully hashing at nameplate. Expect ≥ 13.5 V sustained on an S21 at stock frequency. Below that is PSU sag — either the unit is tired or the circuit/cord/PDU is undersized. Swap PSU with a known-good APW12-class unit and re-test. If the known-good PSU also sags, the issue is upstream at the outlet, PDU, or breaker.

7

Verify the P13 20A power cord and PDU — the S21-specific trap. S21 ships with a new P13 20A cord, not the 16A cord the S19 used. Running an S21 on an old S19 PDU outlet or cord causes steady-state voltage sag that mimics silicon HW%. Replace with correct-rated 20A cord and matching PDU. Bitmain's adaptation notice: `support.bitmain.com/hc/en-us/articles/27522322154521`. In D-Central's data, a meaningful share of S21 HW% tickets are actually cord undersizing.

8

Re-seat every hashboard cable: power off at the breaker, wait 60 seconds for caps to discharge, disconnect ribbon data cables and power connectors on all three hashboards, inspect contacts for oxidation or blackening with a loupe, reconnect firmly until you hear the click. Oxidized contacts raise resistance, which causes voltage sag at the board, which surfaces as HW%. Fixes a surprising share of intermittent cases.

9

Swap hashboards between slots. Label the three slots 0/1/2 with painter's tape. Move the suspect-bad board to a known-good slot. Run 20 minutes at stock frequency, re-read per-chain HW%. If the fault follows the board it's a bad board — proceed to Tier 3. If the fault stays in the slot it's a bad control path, ribbon, or slot connector — proceed to Step 6 logic for that slot.

10

Rebuild OC conservatively from stock. Start at -50 MHz from nameplate with +10 mV. Every 15 minutes of stable HW% under 1.5%, add +25 MHz. Stop at the step before HW% crosses 2%. That frequency is this specific miner's silicon-lottery ceiling on the BM1370/BM1380 lottery — it varies per die, no two S21s have the same ceiling. Save the profile with a specific name so you can fall back if a firmware update resets autotune state.

11

Check line voltage at the panel. Multimeter across the breaker under load. Expect 235-245 V on 240 V split-phase; 202-212 V on 208 V commercial. Low line voltage means the PSU pulls more current, which causes more sag, which causes more HW%. A cheap plug-in voltage logger at the outlet for 24 hours catches evening / peak-load sag that a one-shot measurement misses. Residential grid sag 6-10 PM is a classic pattern.

12

Flash DCENT_OS — D-Central's open-source Antminer firmware (`https://d-central.tech/dcent-os/`). Per-chip HW% visibility, closed-loop autotune, stratum v2, open-source, no licensing fees. The single biggest diagnostic upgrade on an S21-class miner. Alternatives: Braiins OS+, LuxOS, Vnish. Let the miner stabilize 20 minutes post-flash, then record the worst 3 chip positions across all 3 boards. On stock Bitmain firmware you're flying blind — per-chip is mandatory for Tier 3 work.

13

Reflow the worst chip. If one or two chip positions dominate HW%, remove the heatsink, clean paste residue with 99% IPA, flux the BGA, reflow with preheat-plus-hot-air: bottom preheat 150 °C, top-side hot air 310-330 °C for approximately 30 seconds. Let it cool naturally, re-paste with Arctic MX-6 or Kryonaut, reassemble. BM1370/BM1380 BGA packages tolerate one reflow cycle well; a second reflow on the same chip is diminishing returns — replace the chip instead.

14

Re-apply thermal paste and replace pads. Arctic MX-6 or Thermal Grizzly Kryonaut, thin uniform layer, don't glop. Pay specific attention to voltage-domain ICs and the PCH — dried pads on the voltage regulator stack are a documented cause of S21 HW% drift over time. This is also the moment to inspect and replace any thermal pads that look compressed, cracked, or discoloured. Full paste refresh every 18 months for standard S21, 12 months for Hydro.

15

Inspect voltage-domain capacitors and MLCCs. Bulging electrolytics or cracked MLCCs near the PMIC and voltage-domain ICs indicate cap aging under continuous thermal load — they lose capacitance, the rail gets noisier, the ASIC misbehaves. Replace with equivalent-spec parts. This is a soldering-iron and hot-air job, not a reflow job — different temperature profile, different risk class. If you haven't done cap-level work before, stop and ship to D-Central.

16

Firmware rollback / roll-forward, deliberately. S21 stores its OS on eMMC, not SD — so you flash via Bitmain's official updater from `service.bitmain.com/support/download`. Verify the image matches your hardware revision before clicking, because a wrong-hardware-rev firmware flash on S21 can soft-brick the control board. Flash one stock version back, observe 30 minutes. Flash one version forward. If HW% tracks a specific firmware, that's your answer.

17

Stop DIY when: per-chip HW% isolates the same chip position across two different hashboards (PCB or design issue, not chip-level), or PMIC / voltage-domain IC damage is suspected (visible heat damage, measurable short, PMIC sanity check failing), or a second reflow on the same chip fails within 30 days, or capacitor bulging / burnt-component odor is present. You are in test-fixture territory — book a D-Central ASIC Repair slot at `d-central.tech/services/asic-repair/`.

18

D-Central bench process: test fixture with programmable load to isolate each chip under realistic draw; per-chip comms test using official Bitmain test binaries; chip replacement with BM1370/BM1380-class chips from graded stock; full reflow and re-seal; 24-hour burn-in at nameplate before the board ships back. Control-board eMMC cloning is available for boards where storage has worn out — this is the S21-specific recovery path that DIY can't replicate without a test fixture.

19

Ship safely. Hashboards in anti-static bags, double-boxed with at least 5 cm of foam on every side. Include: observed symptoms, current firmware build string, your contact info, and whatever per-chip HW% logs you can export from DCENT_OS / Braiins OS+ / LuxOS / Vnish. Good logs save diagnostic bench time, which saves you money. Shipping from Canada: direct to D-Central. From US/international: we accept shipments — see the repair service page for current import handling.

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.