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 S17 – Low Hashrate

Realised hashrate sustained below 85% of nameplate — typically a missing chip on a chain, APW9 PSU sag, thermal throttle from dried paste, or a lost PIC microcontroller on a hashboard.

Warning — Should be addressed soon

Affected Models: Antminer S17, S17 Pro, S17+, S17e

Symptoms

  • Dashboard hashrate sustained below 85% of nameplate — S17 53 TH/s, S17 Pro 50/53 TH/s, S17+ 70-73 TH/s, S17e 60-64 TH/s
  • ASIC status page shows `X` instead of frequency on one or more chip positions
  • `kern.log` contains `check_asic_number_with_power_on: Chain[X]: find 0 asic` or `Chain X only find Y ASICs, will power off hash board X`
  • Per-chain hashrate is uneven — e.g. chain 0 at 17 TH/s, chain 1 at 12 TH/s, chain 2 at 2 TH/s
  • Intermittent hashrate drops that recover after a minute and return (silent chip-reset pattern)
  • Hashrate collapses above 28-30 °C ambient — PCB approaching `> 80 °C` throttle threshold
  • `kern.log` shows `fail to read pic temp` next to the low-hashrate lines (PIC microcontroller I2C handshake lost)
  • APW9 / APW9+ PSU fan ramping hard while miner hashes well under nameplate
  • Hashrate dropped immediately after firmware flash or SD recovery (profile reset to Normal on S17 Pro, or wrong-rev firmware)
  • Realised pool hashrate 5-15% below the miner's local dashboard reading
  • Audible click, pop, or burnt-electrolyte smell preceded the drop — stop, do not power back up
  • Chip counts fluctuate between reboots — ribbon cable or I2C on the edge of failure

Step-by-Step Fix

1

Hard power-cycle at the breaker for 60 seconds. Not a soft reboot. S17 firmware wedges bmminer state across warm restarts more often than newer firmware does, and a true cold boot clears it. Let the miner fully sit dark, then bring the breaker back up. Watch the first 5 minutes of the UI — if hashrate climbs to nameplate, you are done.

2

Verify the tuning profile is what you expect. On S17 and S17 Pro, Turbo is the 50+ TH/s mode; Normal is ~40 TH/s. If the miner came back from an SD recovery, it has reset to Normal. Open Miner Configuration → Profile, select Turbo on S17 Pro or confirm the single profile on S17+/S17e, save, and reboot. Observe 15 minutes before deciding the profile was not the cause.

3

Clean the intake filter and confirm ambient air at the grille is `≤ 35 °C`. A dust-packed filter on a miner this old is effectively a heat blanket. Shop-vac the filter, wipe the grille, pull anything within 15 cm of the front of the miner out of the way. Use an IR thermometer at the face of the intake — not room-middle. Anything over 35 °C and the board firmware clips frequency to protect the chips.

4

Check the installed Bitmain firmware version against known-buggy builds on service.bitmain.com/support/download for your hardware revision (sticker on the control-board shield). If you are on a deprecated build, roll one version forward or backward and re-test. Legacy S17 firmware shipped at least one stratum-handling regression that surfaced as phantom low hashrate with no other symptom. Always flash the correct version for the board revision — wrong-rev flashes brick the control board.

5

Confirm the pool is healthy. Sometimes 'low hashrate' is a pool-side rejection problem, not a miner problem. Cross-check realised hashrate at the pool against the miner's local dashboard. If the pool is 15%+ below local, test against a second pool (e.g. OCEAN, Braiins, Solo CK) for 30 minutes. Rules out pool-side share acceptance issues before you open the case.

6

Measure APW9 / APW9+ output under load. Multimeter on DC, probe at the PSU-to-hashboard 6-pin connector while the miner is hashing at full power. Expected `≥ 13.6 V` sustained on a standard S17, `≥ 13.8 V` on S17+. Anything below and the PSU is tired or the circuit is starving it. Swap in a known-good APW9+ and re-test. A single PSU swap resolves a surprising share of S17+ low-hashrate tickets because the original APW9 design aged poorly.

7

Re-seat every hashboard cable. Power off at the breaker, disconnect PSU. Pop each hashboard's data ribbon and power connectors. Visually inspect contacts for blackening, oxidation, or bent pins. Wipe with 99% isopropyl on a lint-free wipe if you see residue, let dry, then reconnect firmly until you hear the click. Cable issues on S17 boards are more common than people think because the ribbons are fragile and the housings lose tension over three summers of thermal cycling.

8

Swap hashboards between slots. Label the three slots 0/1/2. Move the board showing short ASIC count to a known-good slot. Move a known-good board into the suspect slot. Power up and observe ASIC status for 10 minutes. If the short-count follows the board, the board is the problem — continue to Tier 3. If the short-count stays in the slot, the control-board connector or ribbon is the problem — swap ribbons next.

9

Replace the ribbon / data cable set. A new set of S17 signal/data ribbons runs `$10-$25 CAD` and takes 15 minutes to swap. Do this before you condemn a board. While you are in there, inspect the small silver washers under the board standoffs — corroded or over-tightened standoffs can short the board's ground plane to chassis and produce identical symptoms. Torque to hand-tight plus a quarter turn; no more.

10

Check line voltage at the outlet under load. On a dedicated 240 V circuit, expect 235-245 V. On a shared residential circuit, it can sag to 215 V during neighbourhood peak (6-10 PM) and that sag cascades into the PSU. If you see significant dip, the circuit is undersized — a dedicated 240 V run to the miner will likely resolve hashrate complaints that only appear in evenings. S17+ requires 200-240 V; do not run on 110 V.

11

Flash `DCENT_OS` — D-Central's own open-source Antminer firmware. Per-chip HW% visibility, closed-loop autotune, stratum v2, frequency stepping on a per-chain basis, no licensing fees. On S17-class miners this is the diagnostic upgrade that changes the game: you stop guessing which chip is dragging the chain down and start seeing it. Alternatives if you prefer: Braiins OS+ (S17 support is limited in newer builds — check current matrix), LuxOS, or Vnish. Let the miner stabilise 20 minutes after flashing, then read the per-chip view.

12

Identify chip positions from the fault pattern. On S17+ the community has repeatedly flagged chip positions 13, 15, 23, 63 as high-failure-rate locations (Zeus Mining S17+ fault logs). Read the log and the per-chain view for your specific fault. If one or two chip positions dominate the HW% and the chain count is short by 1-2 chips, you are in chip-replacement territory. Mark the bad positions on a photo of the board so you do not lose track during rework.

13

Reflow the worst chip. Remove the heatsink from the affected BM1397 chip. Flux the BGA. Preheat the bottom side to ~150 °C, then top-side hot air at 300-315 °C for ~30 seconds. Let it cool naturally. Re-apply thermal paste (Arctic MX-6 or Thermal Grizzly Kryonaut). Re-seat the heatsink. Boot and watch ASIC status. Reflow is the lowest-risk chip-level fix on S17 generation and about 40% of short-count faults are reflow-responsive; the rest need outright chip replacement.

14

Re-paste every chip on the board at the same time. If you have the heatsink off and the board out, replace thermal paste on every chip — not just the target. S17 boards almost always need a full paste refresh after 18-24 months of continuous operation and doing it now saves you the same teardown six months later. Pay attention to the small domain-voltage ICs and the PCH — dried pads there are a top cause of temperature-sensor drift that looks like 'low hashrate' at the firmware layer.

15

Inspect and replace aged electrolytic caps near the voltage domain. S17 boards accumulated heat stress on the primary-side electrolytics. Any bulging, leakage, or brown staining = replace. Stock values are marked on the cap silkscreen. This is a soldering-iron + low-temp hot-air job and is quick once you have identified the bad part — skip if no visible damage. Always discharge the board before probing high-side caps.

16

Re-flash the PIC microcontroller if `fail to read pic temp` is in the log. This requires the Bitmain PIC re-flash tool (distributed to authorised repair partners via service.bitmain.com) or a functionally equivalent rig. D-Central maintains both. If you do not have the tool, package the board and ship it — it is an hour of bench time, not a destructive repair. PIC re-flash on S17 brings the board back from a 'limp mode' state where the firmware capped the chain because it lost the temperature-sense handshake.

17

Stop DIY here and book D-Central ASIC Repair when: (a) two different hashboards in the same rig show the same failing chip position (PCB-layer issue); (b) per-chain HW% is spread evenly across all 48/65 chips with no outlier (voltage-domain or PMIC); (c) you have reflowed a chip twice and it fails again within 30 days; (d) you see burnt-electrolyte odour, capacitor bulging, or visible PCB discolouration. Link: https://d-central.tech/services/asic-repair/ — 5-10 business days, Canada + US + international.

18

At the D-Central bench: PT2 fixture test with programmable load; per-chip isolation using the Bitmain factory test binary; chip replacement with graded BM1397 donor chips (we stock them); full reflow + re-paste; APW9 / APW9+ PSU bench test or replace; PIC re-flash using the official tool; 24-hour nameplate burn-in on a PT2 stand before the board ships back. Component-level repair is $85-$225 per board; full-miner refurb is $280-$550 depending on scope.

19

Ship hashboards correctly. Anti-static bag per board. Double-box with `≥ 5 cm` of foam on every side. Include a note listing observed symptoms, firmware version, fault log excerpts, and the owner's contact — the diagnostic time we save goes straight into your repair cost. Do not tape directly to the PCB; keep fasteners in a separate bag to avoid scratch damage in transit.

20

Consider retirement into a Bitcoin space heater before you scrap the miner. An S17 at ~2500 W outputs roughly 8500 BTU/h of heat; an S17+ at ~2800 W outputs ~9500 BTU/h — respectable supplemental heat for a Canadian garage or basement October through April. A working S17 with 1-2 dead chips on one chain is still a viable space heater: drop the dead chain, run on two boards, take the hashrate hit, collect the heat. D-Central's space-heater conversion line was built for exactly this: https://d-central.tech/product-category/bitcoin-space-heaters/

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.