Skip to content
Small team, full backlog, zero orders dropped. Support replies are slower than we’d like. Read our status update → Zero orders dropped. Status → 📬 Check your spam folder — most of our replies land there. We do answer. Status update → 📬 Check your spam folder. Status →
ERR_TEMP_SENSOR Critical

Antminer S19 – Temp Sensor Failure

Temperature sensor read failed — control board cannot read temp_pcb or temp_chip on the affected hashboard; chain refuses to start hashing until a valid reading is restored.

Critical — Immediate action required

Affected Models: Antminer S19, S19 Pro, S19j Pro, S19 XP

Quick answer

Temperature sensor read failed — control board cannot read temp_pcb or temp_chip on the affected hashboard; chain refuses to start hashing until a valid reading is restored. First step: Power-cycle the miner at the breaker for 60 seconds.

Symptoms

  • Dashboard reports temp_pcb = 0 °C or -40 °C on one hashboard while the other two read normally
  • temp_chip shows 255 °C, -127 °C, or a blank/dash value on the affected chain
  • Miner enumerates 114 ASICs on the bad chain but refuses to start hashing — stuck at 0 H/s on that chain
  • kern.log shows repeated `temp sensor read failed`, `get_temperature: i2c read timeout`, `pic_read_temp error`, or `asic_temp_err chain[X]` lines
  • Both fans spin up to 100% duty even though the chassis is cool to the touch
  • Chain status page shows a yellow/red flag next to the temperature column, all other columns green
  • Swapping the hashboard into a known-good slot reproduces the bad read in the new slot (fault follows the board)
  • Stock Bitmain UI shows a `check hashboard temperature sensor` banner
  • Error started immediately after a firmware flash, dust cleaning session, or a physical move of the miner
  • External IR thermometer on the inlet face reads nowhere near 0 or -40 °C, confirming the sensor is lying rather than the chassis being actually cold
  • Error appears only on cold power-on in sub-5 °C ambient and clears after the miner warms up (cold-boot race)
  • Intermittent `i2c read timeout` events in kern.log correlated with neighbourhood peak electrical load (EMI / PSU noise pattern)

Step-by-Step Fix

1

Power-cycle the miner at the breaker for 60 seconds — not a soft reset, not a UI reboot, a full AC-off cycle. This drains the PIC's supply capacitors fully and clears any latched state from a transient I²C fault or cold-boot race. On cold days (sub-5 °C ambient), wait 5 minutes after first power-on before declaring the fault. Observe for 5 full minutes after power returns. If temp_pcb / temp_chip return to normal and stay there, you're done — re-baseline in 24 hours.

2

Update to the latest stock Bitmain firmware from support.bitmain.com/downloads for your specific hardware revision. Verify the build board code on the hashboard sticker before flashing — wrong firmware for a late-rev board will brick the control board. If you're already on latest, try rolling one version back; certain pre-2022-06 S19j Pro builds had a known BMminer regression that latched the sensor-failed flag even with healthy hardware.

3

Physically inspect intake/exhaust airflow and dust loading. Shop-vac both fan grilles, wipe the intake face, verify at least 15 cm of clearance front and back. A heavily-dusted heatsink can bake the PCB sensor area enough to push a marginal IC into reporting absurd values. Many intermittent-sensor-failure tickets turn out to be perfectly-working sensors reporting bogus numbers because the nearby PCB region is genuinely overheating.

4

Breaker off. Disconnect the PIC-to-control-board ribbon cable on the suspect chain. Inspect both headers under strong light — look for green/white oxidation, darkened contacts, bent pins, or cracked plastic. Apply a short burst of DeoxIT D5 or equivalent no-residue contact cleaner to the header pins. Let it flash off for 30 seconds. Reconnect firmly and listen for the retention-clip click. Humidity-driven oxidation is the #1 recoverable cause and clears a solid majority of first-time reports.

5

With the board out of the chassis, re-seat every connector: power terminals, chain-to-chain data cable, PIC programming header. Inspect for physical damage, melted plastic, or solder cracks around any large connector. Gently flex the ribbon cable end-to-end — if you hear or feel a crunch, the copper inside has fractured; replace the ribbon rather than debug it.

6

Swap the suspect hashboard into a different chassis slot. Label the 3 slots 0/1/2 with tape first. Boot and observe. If the sensor failure moves with the board, the fault is on the hashboard (sensor IC, PIC, or local I²C). If the failure stays in the same slot regardless of which board you install, the control board's ribbon connector or UART channel for that slot is the fault — Tier 4 control-board repair territory.

7

Multimeter in continuity mode, breaker off. Check continuity end-to-end on every conductor of the PIC-to-control-board ribbon cable. Any open circuit means the cable is dead — replace it. Ribbon cables for S19-family miners are CAD $15-30 from most ASIC parts suppliers; carry a spare in your bench kit.

8

Move to a firmware that reads temperature independently of the failed PCB sensor IC. A clean per-chip temperature read alongside a still-failed temp_pcb isolates the fault to the PCB sensor IC specifically — the easiest Tier-3 fix. Scope it to your model first. Of the four on this page, DCENT_OS publishes a downloadable image only for the Antminer S19j Pro on the Zynq/XIL control board (GPL-3.0 public beta, experimental), and no model has a published witnessed first-install route from stock firmware, so treat that image as a bench experiment, not a fix for this fault (https://d-central.tech/dcent-os/antminer-s19j-pro/). The S19 and S19 Pro are named in its platform record with no public image and no install route (https://d-central.tech/dcent-os/beta-status/); the S19 XP has no DCENT_OS image or install route at all. Braiins OS+, LuxOS and Vnish are the alternatives to check — verify your model on the image's own list before you write anything. Let the miner stabilize 20 minutes, then compare the per-chip temperature read against temp_pcb.

9

Probe the I²C bus at the PIC's SDA / SCL test pads with a multimeter (or scope, if you have one). At rest with the board powered, both lines should read 3.3 V DC from the pull-up resistors. 0 V on either line means the bus is shorted to ground or the sensor IC has failed short. Floating on either line means the pull-up resistor is dead. Replace the pull-up (typically 4.7 kΩ or 10 kΩ 0603 SMD — measure the silkscreen value before ordering). CAD $0.05 part; ~30 minutes of work.

10

Replace the PCB sensor IC. Desolder with hot-air at ~310 °C, clean pads with flux and braid, place a new IC with the correct footprint and part number. Bitmain has shipped at least three different sensor IC revisions on S19-family boards — verify the part number on your specific board's silkscreen before ordering. Reflash the PIC with stock PIC firmware after IC swap to ensure the I²C address table matches.

11

If both temp_pcb and temp_chip are dead on the same chain, suspect the PIC itself. Reflash the PIC using a PICkit 4 or equivalent programmer with Bitmain's official PIC binary for your hashboard revision. If reflashing fails or the PIC does not ACK on the programming header, the PIC is physically dead — replace it. This is small-pitch TQFP work and edges into Tier-4 territory if you are not experienced with it.

12

Inspect the 3.3 V rail feeding the PIC and sensor IC. Measure under load, not at idle. Sag below 3.15 V means a failing local regulator or a blown decoupling cap. Replace the regulator or bulk decoupling cap as indicated. This happens on boards that endured a PSU-side fault or lightning-adjacent event and is sometimes the real root cause behind a 'dead sensor' call.

13

Stop DIY when any of these are true: both temp_pcb and temp_chip are dead with the PIC not ACKing on its programming header; the I²C bus probes show hard shorts or missing pull-ups that you've already replaced without improvement; the ribbon connector on the control board itself is mechanically damaged; or you see burn marks, component discoloration, or a burnt-electronics smell anywhere on the board. Ship to D-Central — a test fixture with programmable load and scope-level I²C capture saves you more than further DIY at this point.

14

D-Central bench process for ERR_TEMP_SENSOR: full board inspection under microscope, I²C bus capture with a dedicated analyzer, sensor IC and PIC replacement with verified-genuine parts (we cross-reference part numbers against Bitmain's hardware table to avoid counterfeit sensor ICs, a real problem on aftermarket parts), 3.3 V rail integrity check, post-repair 24-hour burn-in at nameplate with live temperature logging.

15

Ship safely: hashboards in anti-static bags, double-boxed with at least 5 cm of foam on every side. Include a note listing the exact failure sentinel value (0 °C, -40 °C, -127 °C, 255 °C, blank), your firmware version, and your observed symptoms — that intel saves us diagnostic time, which saves you money. Canadian customers get domestic shipping rates; US and international shipments welcomed with clear customs documentation included.

Know your exact variant: S19-family fixes differ by sub-model and board revision. The Antminer S19 family hub decodes every variant, chip, and spec so you match the right procedure to the unit on your bench.

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.

Frequently Asked Questions

What does the ERR_TEMP_SENSOR error mean?

Temperature sensor read failed — control board cannot read temp_pcb or temp_chip on the affected hashboard; chain refuses to start hashing until a valid reading is restored. Commonly reported on: Antminer S19, S19 Pro, S19j Pro, S19 XP.

Can I fix the ERR_TEMP_SENSOR error myself?

This is an advanced repair best handled by someone experienced with ASIC hardware. Start with: Power-cycle the miner at the breaker for 60 seconds — not a soft reset, not a UI reboot, a full AC-off cycle. This drains the PIC's supply capacitors fully... If you are not equipped for board-level work, D-Central can diagnose and repair it at our Montreal bench.

How much does it cost to repair?

A DIY repair typically runs $20-$300 CAD depending on which part the fault traces to. D-Central can also diagnose and quote a mail-in bench repair.

What parts might I need to fix this?

Common replacement parts for this fault: LM75A, TMP75, Hashboard Thermal Paste (Cyan), MARTECH DF1203812B2UN 6000 PWM. The exact part depends on diagnosis - measure first.

Key Terms in This Fault

Jump to the full definition of the technical terms involved in this fault:

Related Error Codes

Decode this on your own terms — DCENT_OS

DCENT_OS is D-Central’s open-source, GPL-3.0 firmware effort for Antminer hardware — publishing guarded experimental artifacts for exact S9 XIL and S19j Pro XIL lanes; their install evidence remains incomplete. It is experimental and not production-ready, and it can brick a miner if you flash without a recovery path. We build on the shoulders of the open-firmware projects that came before us. Leave your email for build announcements from the firmware that surfaces and decodes faults like this one. This is a free public beta, never a pre-order — collection only, we will not email you anything else yet.

Printable quick-reference cards

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.