Antminer T19 – Low Hashrate
Warning — Should be addressed soon
Symptoms
- Realized hashrate 5-20 TH/s below the 84-88 TH/s nameplate, sustained
- Dashboard ASIC count shows 74/76, 75/76, 0/76, or any chain-level shortfall
- `kern.log` / cgminer shows repeated `check_asic_number_with_power_on: Chain[X]: find N asic` with N<76
- One hashboard chain runs several degrees cooler than the others (stone-cold chain is usually a dead chain)
- Pool reports share rate 10-20% below healthy fleet peers on the same firmware and config
- Intermittent hashrate dips correlated with ambient temperature rising in the afternoon
- Miner boots, passes self-test, then drops a chain after 5-30 minutes of hashing (thermal cutoff on a marginal chip)
- `cgminer` API returns elevated `HW` count on the failing chain even though share acceptance looks OK
- Fan RPM ramping to 6000+ on one zone while hashrate still undershoots nameplate
- After a firmware update, hashrate dropped and hasn't recovered (firmware/hardware-revision mismatch)
- Cold-start hashrate is fine; hashrate degrades over 10-20 minutes as the board heats (virtual-solder / dried-paste)
Step-by-Step Fix
Hard power-cycle the miner for 60 seconds at the breaker (not a soft reboot — full power removal). Clears any wedged driver state from firmware updates and forces a clean chain re-initialization on boot. Observe dashboard hashrate and per-chain ASIC count for 10 minutes after restart. If hashrate recovers to nameplate and holds, the fault was transient driver state; log the incident and monitor.
Open the stock dashboard and count ASICs per chain. Healthy T19 shows `76/76` on each of the 3 chains. Any chain reading `<76` is your failing chain — note its number and prioritize the Tier 2 reseat and swap procedure for that specific board. Screenshot the per-chain display for your records and for the D-Central repair intake form if the fault persists past Tier 2.
Revert to stock frequency (550 MHz on most T19 revisions) and stock voltage in the miner configuration. Remove any overclock, underclock, or undervolt profile. Let the miner run 15 minutes on stock, then record realized hashrate. If it recovers to nameplate, your tuning profile was the problem — rebuild it slower in Tier 2 step 10. If hashrate stays low, continue to step 4.
Shop-vac the intake filter, wipe the intake grille with a dry lint-free cloth, and verify no dust, furniture, curtains, or obstruction within 15 cm of the front of the miner. Dust restricts airflow, raises inlet temp, raises chip junction temp, and drops hashrate. This alone fixes roughly 1 in 5 low-hashrate tickets and takes under 5 minutes with no tools.
Verify intake air temperature with an IR thermometer at the front grille — not across the room. Target `≤ 35 °C` at the intake. If ambient is walking up into summer, relocate the miner, add intake ducting, or add a summer exhaust fan. T19s lose hashrate measurably above 35 °C intake and the degradation is not recoverable until ambient comes back down.
Multimeter on DC, probe at the APW12 output buses while the miner is fully hashing at nameplate load — not at idle. Expect `14.1–14.5 V` sustained; anything below `13.8 V` under load means a tired APW12 or an undersized circuit. Swap PSU with a known-good APW12 (or APW12-V) and re-measure. A sagging PSU is the single most common non-chip cause of T19 low hashrate.
Power off at the breaker. Re-seat every hashboard data ribbon, power connector, and signal cable. Inspect each contact for corrosion, blackening, or bent pins before reconnecting. Listen for the positive click on each seat. A single loose ribbon on a T19 will drop a chain cleanly — reseating is the cheapest Tier-2 diagnostic and fixes a meaningful percentage of tickets outright.
Label the 3 hashboard slots 0/1/2 with masking tape. Swap the suspect-bad board into a known-good slot and the known-good into the suspect slot. Reboot and observe 15 minutes. If the fault follows the board, the board is bad — proceed to Tier 3. If the fault stays in the slot, the control-board path or ribbon cable is bad — replace the ribbon first, then consider control board.
Measure line voltage at the wall under full load, not at idle. Expect 235–245 V on 240 V split-phase and 202–212 V on 208 V commercial. If line voltage sags below spec under load, the circuit is undersized or shared with another high-draw load (HVAC, dryer, kiln, EV charger). Move the T19 to a dedicated 240 V/20 A circuit or escalate to an electrician. Firmware cannot fix a tired panel.
Rebuild overclock from stock in 25 MHz steps with a 10-minute stability window between steps. Log hashrate and HW% at each step. Stop at the last step before HW% crosses 1.5% or chain temp crosses 90 °C. That step is your T19's silicon-lottery ceiling — it is per-miner and unique. Save the profile. Do not push 'just one more step' — the chip ages visibly faster past its ceiling.
Flash DCENT_OS — D-Central's open-source Antminer firmware — via SD card or network upgrade path. Recommended for T19 per-chip HW% visibility and real-time chip-failure mapping; built by Mining Hackers, fully open-source, maintained in public at github.com/DCentralTech/DCENT_OS. Alternatives: Braiins OS+, LuxOS, Vnish. Stabilize 20 minutes, then record the worst chip positions. This step alone clarifies roughly 60% of mystery low-hashrate tickets.
Replace thermal paste on all chips of the suspect board with Arctic MX-6 or Thermal Grizzly Kryonaut. Clean old paste with 99% isopropyl and a lint-free wipe — no paper towel, no cotton swab fibers. Apply a uniform thin layer on each BM1398 die. Pay particular attention to the PCH and voltage-domain ICs — dried pads there cause progressive hashrate drift that masquerades as chip failure and is cheap to fix if caught early.
Reflow the worst-performing chip position identified in Step 11. Remove heatsink, apply flux around the BGA perimeter, preheat the bottom side of the board to ~150 °C, top-side hot air at 310–330 °C for ~30 seconds, pause, cool naturally for 5 minutes. Re-paste and reassemble. BGA BM1398 packages tolerate a single reflow well; second reflows on the same chip have materially lower success rates — plan to replace if the first reflow doesn't hold.
Inspect electrolytic capacitors on the voltage-domain regulators, particularly the bulk caps adjacent to each PMIC. Bulging tops, cracked cases, leaking electrolyte, or visibly discolored MLCCs near a domain regulator indicate drift or failure. Replace with equivalent rating from the silkscreen. This is a soldering-iron + hot-air job, not a reflow job. If you are not comfortable identifying cap values from PCB silkscreen, stop and ship to D-Central.
Roll firmware to the last-known-good version for your specific T19 hardware revision. Verify against the hardware build-date sticker on the control board before flashing — wrong firmware for a late-revision T19 can brick the control board. Keep the SD-card recovery image on hand before you start. After flash, observe 30 minutes and record hashrate baseline; if the regression is firmware-related you will see immediate improvement.
Stop DIY when any of the following is true: per-chip diagnostics isolate the same failing chip position on two different boards in the rig; a voltage-domain IC or PMIC is suspected; a second reflow on the same chip fails within 30 days; you see capacitor bulging, burnt-component odor, or visible heat damage. Shipping to D-Central is cheaper than damaging adjacent parts. Book an ASIC Repair slot at d-central.tech/services/asic-repair/.
D-Central bench process on T19-class boards: PT2 or equivalent test fixture with programmable load, per-chip isolation using official Bitmain test binaries, short-RO and inter-chip voltage probing (Zeus Mining's documented '1V8 between 38/39th chip' dichotomy method), chip replacement with graded BM1398 stock, PMIC/regulator replacement where indicated, full reflow, and post-repair 24-hour burn-in at nameplate before return shipping.
Ship hashboards in anti-static bags, double-boxed with at least 5 cm of foam on every side. Include a written note with observed symptoms (cold-start behaviour, chain number, firmware version, any per-chip failure map from Step 11), and contact info. This cuts 30-60 minutes off the diagnostic phase and directly reduces your repair cost. Canada / US / international shipping accepted at the D-Central repair queue.
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.
