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

WM_M20S_VOID Warning

Whatsminer M20S – Hashboard Chip Void Repair Procedure

Whatsminer M20S hashboard chip void — BGA solder voids on aging KF1921 chips cause intermittent enumeration failures, hot-spot drift, and progressive hashrate loss; surfaces in btminer.log as Error 530/540/550 cluster.

Warning — Should be addressed soon

Affected Models: Whatsminer M20S (68 TH/s), M20S+ (rebadged 70 TH/s units sharing the KF1921 board topology)

Symptoms

  • M20S is 3+ years old and has run 24/7 in a non-immersion environment
  • Realized hashrate has dropped 5-25% below 68 TH/s nameplate with no firmware or pool changes
  • `get_error_code` returns intermittent `540`, `541`, or `542` (per-chip UART enumeration fail) on one slot
  • Cold-boot enumeration shows fewer than 105 chips on a slot (e.g. 73/105, 89/105) but recovers after 10-20 minutes hot
  • One voltage domain reports a different temperature than its peers by ≥5 °C under load
  • `btminer.log` shows `RXD` voltage drift mid-chain (1.8 V at U1, drifting toward 0 V before U105)
  • Thermal camera shows isolated hot spots — 1-3 chip positions running >10 °C above neighbours
  • PSU is healthy (P21/P21E rails in spec) but slot still reports `Error 550` (`bad chips detected`) on warm reboot
  • Board has been previously reflowed once; symptoms returned within 60-120 days
  • No visible damage — no burn, no bulged caps, no smell — just degrading numbers
  • Reseating the slot adapter does not change behaviour (rules out 300/301/302 cable cluster)
  • Hashrate degrades faster on hot-ambient days vs. cool-ambient days

Step-by-Step Fix

1

Cold-soak the M20S for 30 minutes at the breaker. Cold-boot. Pull `get_error_code` immediately and again at 5, 15, and 30 minutes. Log every code returned. This baseline is the single most important data point in the workflow — a board that enumerates clean cold and dirty hot is fundamentally different from one dirty in both states.

2

Reseat the hashboard ribbon and power adapters with the miner powered off. Inspect contacts visually for blackening or oxidation under bright light, reconnect firmly, listen for the click. About 10% of suspected void symptoms turn out to be flaky 300/301/302 adapter cables — five-minute rule-out.

3

Reflash the latest stable BTMiner firmware for your hardware revision via MicroBT's official channel. Some old M20S firmware builds had stratum-handling bugs that surface as apparent enumeration faults. Do not flash third-party firmware — original Vnish builds for this generation are abandoned and DCENT_OS does not yet support MicroBT silicon.

4

Per-slot temperature audit under load. With the miner hashing 20 minutes at full power, pull all four per-slot temp sensor readings via API. Healthy M20S sits at 78-88 °C top-side under load with ≤4 °C inter-slot spread. Anything above 8 °C inter-sensor spread on one slot means current is concentrating where it shouldn't — your X-ray target.

5

Power-rail measurement at the slot under load. Multimeter on DC, probe the 12 V power adapter feeding each slot under steady-state hashing. Expect 11.7-12.3 V sustained. Sag below 11.5 V means the slot is drawing more current than spec — consistent with high-resistance joints — or your `P21`/`P21E` PSU is failing. Outlier slot is your suspect.

6

`RXD`/`TXD`/`CLK` signal trace along the bad slot. Power the slot, attempt enumeration, probe `RXD` at U1 and walk the chain in 10-chip increments toward U105. Per Zeus M20S service docs: `RXD`/`TXD` should sit at `1.8 V` logic high, `CLK` at `0.9 V`. The chip position where voltage starts drifting down is your prime suspect.

7

Adapter-cable swap test. Swap the slot's adapter cable with a known-good cable from another slot or a spare. Re-run enumeration. Fault clears = cable was the issue (write it off). Fault stays = the board is the problem and you're confirmed for Tier 3.

8

Set up the rework bench: Quick 861DW or equivalent hot-air rework station, T-862 or IR-650 bottom preheater, anti-static mat, SAC305 paste/wire, no-clean tacky flux, IPA 99%, microscope, aluminum foil shield for adjacent chips. Full new-bench kit is $800-$1,500 CAD — this is a real investment, not a screwdriver-and-hope job.

9

Thermal-camera the board hot. Bring the board to 60 °C top-side without the heatsink (use the bottom preheater on its lowest setting). Image with FLIR ONE Pro or comparable. Mark the 2-4 hottest chip positions with a sharpie tick on the PCB silkscreen — those are your reflow targets. Cool the board fully before continuing.

10

Localized SAC305 reflow profile: bottom preheater steady at 150 °C. Top hot air on the suspect chip — ramp 1-2 °C/sec to 200 °C (preheat), hold 60 seconds. Then ramp to peak 235-245 °C with TAL (above 217 °C) of 30-60 seconds. Dwell at peak ≤30 seconds. Cool slowly back through 217 °C — no fan-blast. Profile re-melts SAC305; surface tension closes existing voids. Do not use leaded-solder profiles on a SAC305 board.

11

Post-reflow cooldown and inspection. Let the board return to ambient over 5+ minutes. Inspect the reflowed chip(s) under magnification for visible squeeze-out, lifted package, or paste skip. If the chip is tilted vs. neighbours, the joint is misaligned — that's a replace, not a reflow win.

12

Re-paste and reassemble. Clean flux residue with IPA 99% and lint-free wipes. Apply fresh thermal paste (Arctic MX-6 or Thermal Grizzly Kryonaut) to the chip die before re-mounting the heatsink. Reassemble the slot, reinstall, cold-boot, re-run the Step 1 baseline. A successful reflow shows clean 105/105 enumeration cold and hot for ≥72 hours of burn-in.

13

If reflow fails or symptoms return within 90 days, do NOT reflow that chip again. Package thermal budget is finite — every reflow cycle damages chip die marginally and PCB substrate significantly. Two reflows on the same chip is the absolute limit. Move to Tier 4.

14

Tier 4 trigger — book D-Central ASIC Repair when: no rework bench access, Tier 3 reflow returned within 90 days, X-ray shows >50% voids on signal balls of multiple chips, the `KF1921` package itself is suspect (not just its joint), or you have multiple boards showing the same fleet-wide pattern. https://d-central.tech/services/asic-repair/

15

What D-Central does at the bench: 2D X-ray confirmation of void distribution; programmable preheat plus hot-air rework with a tested SAC305 profile per chip position; `KF1921` chip replacement from salvaged-grade inventory pulled from end-of-life M20S boards (only sourcing path — MicroBT doesn't sell chips into channel); reball with SAC305 preforms when chip-source joints aren't transferable; programmable-load test fixture for post-repair signal-integrity verification; 24-hour burn-in at nameplate before ship-back.

16

Decision: repair vs. replace board vs. retire miner. Salvaged-grade M20S hashboard runs $180-$320 CAD. D-Central component-level repair runs $95-$245 CAD per board. Below `$0.07 CAD/kWh` with displaced heating value, repair is materially profitable for another 18-36 months. Above `$0.13 CAD/kWh` straight grid, economics tip toward retirement and migration to current-gen 18 J/TH hardware.

17

DCENT_OS roadmap note: D-Central's open-source firmware ships today on Bitmain hardware. MicroBT (Whatsminer) support is on the DCENT_OS roadmap but is NOT yet available — for M20S firmware in 2026 you stay on MicroBT BTMiner stock. If you operate an M20S fleet at scale and want a vote in DCENT_OS prioritization, comment on the DCENT_OS GitHub: https://github.com/DCentralTech/DCENT_OS

18

Ship safely. Anti-static bag per board, double-box with ≥5 cm foam every side. Include a printed note: serial number, observed `get_error_code` history, suspected slot, what Tier 1-3 work you've completed, and contact info. Boards arriving with no documentation cost an extra hour of bench diagnostic — billable time you don't need to pay for.

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.