Skip to content

We're upgrading our operations to serve you better. Orders ship as usual from Laval, QC. Questions? Contact us

Bitcoin accepted at checkout  |  Ships from Laval, QC, Canada  |  Expert support since 2016

ERR_TEMP_HIGH Critical

Antminer S21 – Temperature Too High

over max temp / Temperature is too high, please check — S21 controller defensively halts hashing when chip, PCB, inlet, or (on Hydro) coolant sensors cross the stock ceiling.

Critical — Immediate action required

Affected Models: Antminer S21, S21 Pro, S21 Hydro, S21+ variants

Symptoms

  • Web UI banner reads `over max temp` or `Temperature is too high, please check`
  • `kern.log` / `bmminer.log` shows `ERROR_TEMP_TOO_HIGH`, `Fatal Error: Temperature is too high`, or `fail to read pic temp chain X`
  • Miner auto-shuts within 30-180 seconds of reaching target frequency, then power-cycles defensively
  • Both fans pin to ~7000 RPM / 100% duty within seconds of boot and never back off
  • Realized hashrate collapses from ~200-234 TH/s nameplate to 0 TH/s on one or more chains
  • Dashboard reports chip temps crossing 95 C chip / 90 C PCB (air-cooled) or 60 C outlet water (Hydro) before shutdown
  • Red fault LED on the control board; network LED still green
  • Miner boots, hashes a few minutes, trips, reboots, hashes again — a repeating thermal loop
  • IR thermometer reads > 32 C at the front intake grille under load
  • One hashboard's reported temp sits 8-15 C hotter than the other two
  • Audible fan rattle, grinding, or RPM dip visible in the dashboard graph
  • Hydro variant: coolant flow or water-temp alarm precedes the thermal trip
  • Rack cabinet walls hot to the touch after 10 minutes — exhaust is recirculating
  • On DCENT_OS / Braiins OS+ / LuxOS / Vnish: one or more chip positions flagged red or running 8+ C hotter than neighbours

Step-by-Step Fix

1

Power off at the breaker and wait 15 minutes before doing anything else. A hot S21 reports inflated sensor values and a hot fin stack doesn't shed dust cleanly, so diagnosing a hot miner wastes your time. This single Tier 1 step will often clear a one-shot `ERR_TEMP_HIGH` caused by a transient ambient spike, and it prevents the PIC chip from lying to you while you work. Confirm the chassis is merely warm to the touch before proceeding.

2

Take the miner outside or over a tarp and blast every fin stack, both fan blades, and the intake grille with compressed air. Hit the fans at 90 degrees to the blades, then both sides of the fin stack, then the exhaust face. Dust falls out in sheets from a neglected S21 — budget 3-5 minutes per side and go thorough. Never use a shop-vac in suction mode on an unpowered hashboard because static can kill the PIC. Canned compressed air or a filtered bench compressor only.

3

Verify ambient is at or below 30 C at the intake grille — not the middle of the room — using an IR thermometer while the miner is running. Closet, shelf, and against-a-wall installs run 5-10 C hotter at the intake than room-middle because exhaust recirculates back into the intake. Relocate the miner to an open space, add active exhaust ventilation, or duct the intake to an outside air source.

4

Restart the miner and monitor dashboard chain temps and fan RPMs for 30 minutes under full hash load. If all three chains settle under 80 C chip and 80 C PCB, and fans hold under 95% duty, you fixed it with Tier 1. If the miner re-trips within 30 minutes, move to Tier 2 — don't keep rebooting it.

5

Check your firmware version against Bitmain's S21 archive at `support.bitmain.com/downloads`. If you are on a build known for tightened thermal thresholds without a corresponding cooling improvement, roll one version back. Verify the build matches your exact hardware revision before flashing — wrong firmware on a late-rev S21 control board is a bricking risk because S21 uses eMMC recovery, not SD-card recovery.

6

Re-seat every hashboard data and power cable. Kill power at the breaker first. Disconnect each cable, inspect contacts for blackening, corrosion, or bent pins, then reconnect until you feel the click. Oxidized data connectors raise chain communication error rate, and the controller defensively throws `ERR_TEMP_HIGH` when it can't trust a chain's readings. This five-minute check catches 15-20% of repeating thermal faults that survive a Tier 1 clean.

7

Label the three hashboard slots 0/1/2 with tape. Swap the hottest-running board into a known-good slot and observe for 30 minutes of full-load hashing. If the hot temp follows the board, the board has a specific problem (paste, fin contamination, or a failing chip). If the hot temp stays in the slot, chassis airflow in that zone is compromised or the fan feeding that slot is sagging. This is the single most informative half-hour you'll spend on a thermal-fault S21.

8

Swap fans. S21 fans are 12 V, 4-wire PWM axial — verify the exact form factor on your specific batch before ordering because S21 production has shipped variations. Install known-good replacement fans, reboot, re-observe the RPM graph and chain temps. If the thermal trip clears with fresh fans, the old fan was faulty even if its dashboard RPM looked close enough on the graph. The controller sees a lot more than the dashboard shows.

9

Measure PSU output at the hashboard connector with a multimeter on DC while the miner is fully hashing. Healthy S21: at least 13.8 V sustained on the hashboard rail. A sagging rail under load means a tired PSU, an undersized circuit, or a dying output capacitor. Swap the PSU with a known-good APW12 or a verified S21-compatible third-party PSU and re-test. Do not skip this step — PSU sag is a top-five cause of S21 thermal creep.

10

Measure line voltage at the panel under load: 235-245 V expected on 240 V split-phase, 202-212 V on 208 V commercial. Low line voltage forces the PSU to pull more current to hold output, increasing dissipation at both the PSU and the hashboard voltage domain, which shows as creeping chip temp. If you are on 120 V you are on the wrong voltage for an S21 — install a 240 V circuit or move the miner to one. No S21 should run on residential 120 V.

11

Refresh thermal paste on all three hashboards. Remove heatsinks, clean old paste with 99% isopropyl and lint-free wipes until the BM1398 die and heatsink base are mirror-clean. Apply Arctic MX-6 or Thermal Grizzly Kryonaut in a thin, uniform layer — no dome, no X-pattern theatre, no glop. The BM1398 is a single-die package where pressure distribution matters more than geometry. Reinstall heatsinks with even torque. Expect a 5-10 C drop at the same load on a miner whose paste was genuinely dry.

12

Inspect and replace thermal pads on PCH and voltage-domain ICs. S21 hashboards carry secondary pads bridging the PCH and voltage-domain ICs to the heatsink frame. These fail faster than the ASIC paste because they run hotter with less margin. Replace with equivalent-thickness 3M, Arctic, or Thermal Grizzly pads — match original thickness exactly, not close-enough. Wrong-thickness pads create air gaps worse than dried original pads.

13

Cross-flash DCENT_OS (https://d-central.tech/dcent-os/) for per-chip thermal visibility. DCENT_OS is D-Central's own open-source Antminer firmware — per-chip temperature, HW%, tuning, autotuning, and Stratum V2 features, Mining-Hacker-maintained, no licensing fees. Alternatives if you prefer: Braiins OS+, LuxOS, Vnish. All four surface per-chip temps that stock Bitmain firmware hides behind chain-level rollups. After flashing, stabilize 20 minutes and identify chip positions running hot relative to neighbours. This single step saves more S21 boards than any other intervention.

14

Reflash the PIC chip if `fail to read pic temp` was the trigger. You'll need a PIC programmer (PICkit 4 or equivalent), the correct Bitmain PIC firmware image for your S21 hardware revision, and a steady hand on the ISP pads. This is not a first-time soldering project. If you've never reflashed a PIC chip before, skip to Tier 4 and ship the board to D-Central — the bench cost is lower than the cost of a second board you accidentally brick.

15

Roll firmware back to the last-known-good version for your exact S21 hardware revision. Match your build date against Bitmain's compatibility table before flashing. Wrong firmware on a late-rev S21 control board equals a bricked eMMC, which equals Tier 4 bench recovery — there is no 5-minute SD-card shortcut on most S21 production batches. Read the compatibility table twice, flash once.

16

Hydro variant only: flush and refill the coolant loop. Drain, flush with distilled water until runoff is clear, inspect heat-exchanger fins for biofilm or fouling, refill with Bitmain-specified coolant (or a verified equivalent — never substitute automotive coolant). Bleed air thoroughly. A neglected S21 Hydro loop can lose 20-30% of thermal capacity to biofilm and dissolved-gas bubbles without any visible damage to components.

17

Stop DIY and book D-Central ASIC Repair when: paste refresh + fan swap + PSU swap + firmware rollback all fail; per-chip temps isolate 3+ hot chips on one board; `fail to read pic temp` persists across slot swaps; the control board refuses to POST after a firmware attempt; you see capacitor bulging, discoloration, or burnt-component smell on any board. Book at https://d-central.tech/services/asic-repair/ — Canada-wide shipping, US/international welcomed.

18

What the D-Central bench does on an S21: test-fixture diagnostics with a programmable DC load, per-chip thermal imaging under controlled ambient, PIC reflash with official Bitmain binaries, paste and pad refresh using bench-grade materials, BM1398-family chip replacement where chips are genuinely dead, control-board eMMC recovery where SD-card recovery is unavailable, and a 24-hour post-repair burn-in at nameplate hashrate before the miner ships back. No guessing, no shortcuts.

19

Ship hashboards safely: anti-static bag each board, double-box with at least 5 cm of foam on every side, and include a note listing observed symptoms, exact log strings, current firmware version, and your contact. Thorough notes cut our diagnostic time, which cuts your invoice. Photograph the miner's current state if you can — a picture of the dashboard at the moment of trip is worth 30 minutes of bench reproduction.

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.