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_M53_AIRLOCK Warning

Whatsminer M53 – Hydro Loop Airlock Preventing Startup

Air pocket trapped in the M53 hydro coolant loop after a fill, top-up, QD re-couple, coolant change, or relocation. Pump cavitates against a compressible gas spring, flow drops to a fraction of nameplate, hashboard coldplates stay heat-soaked, and within 5-15 minutes MicroBT firmware trips a temp-sensor or flow-velocity alarm (300/301/302/350/5070/5071/5072) and de-energizes the hashboards. The fix is a documented tilt-and-bleed procedure with the pump running and the miner unpowered — not a pump replacement.

Warning — Should be addressed soon

Affected Models: Whatsminer M53 (228-262 TH/s); same coldplate manifold and QD design family: M33S+, M33S++, M53S, M53S+, M53S++, M63, M63S, M63S+, M64 Hydro

Symptoms

  • Recent loop event: fill, refill, top-up, drain, QD disconnect-and-reconnect, or chassis relocation/tilt within the last 48 hours
  • Pump runs and sounds healthy at idle (steady low whine present), but coolant return temperature stays near ambient even after 5-10 minutes of attempted hashing
  • MinerTool dashboard / `btminer.log` shows `300` / `301` / `302` (hashboard SMx temp sensor abnormal) or `350` (hashboard high-temp protection) within 5-15 minutes of power-on
  • Concurrent `5070` / `5071` / `5072` `SMx water velocity is abnormal` log lines on one or more hashboard manifolds
  • Reservoir / CDU level keeps dropping over the first 15-30 minutes after fill with no visible leak — air being driven out leaves void behind
  • Audible cavitation tick from the pump — a high-frequency rhythmic clicking that tracks pump speed, distinct from the steady motor whine
  • Touch-test on the QD return line: return-line coolant feels cold or near-ambient even though the miner has been ostensibly hashing for 5+ minutes — heat is not making it out of the coldplate
  • One hashboard's temp climbs faster than the others and trips first — typically the topmost board or the board fed by the longest manifold leg
  • Hashrate falls progressively (not instantly) over the first 5-15 minutes from nameplate (~228-262 TH/s depending on M53 sub-model) toward 0 GH/s as the firmware thermal-caps and de-energizes
  • Tapping the chassis with a fingertip changes the dashboard temperature trend within 30-60 seconds — bubble dislodging momentarily, flow restored briefly, temp drops, then bubble re-settles
  • Bench test of the pump alone (inlet in jug A, outlet in jug B, energized at spec voltage) shows healthy flow — eliminates pump as the failure
  • No `WATER_LEAK` alarm — moisture sensor reads dry, chassis floor is dry, drip tray is dry; this is an airlock, not a leak

Step-by-Step Fix

1

Stop trying to power-cycle the miner to clear the alarm. MicroBT firmware will keep tripping `300`/`301`/`302`/`350` as long as flow is starved at any hashboard, and each cycle dumps another thermal pulse into a stagnant coldplate. Cut miner power at the PDU (trip the breaker or pull the C19 from the PSU) and leave it off until you have completed the bleed sequence in Tier 2.

2

Document the event before touching anything. Photograph the dashboard, screenshot the `btminer.log` error lines, note the time-to-trip, and list every loop action in the last 48 hours: fill, refill, top-up, QD re-couple, relocation, coolant change, hose swap. Airlocks have a recent-event signature; without one, you may be chasing a slow leak that lost prime instead, and the diagnostic path changes.

3

Reservoir / CDU level visual check. Walk to the reservoir or CDU sight gauge. If the level is at or below `MIN`, top to `MAX` with deionized water or your loop's spec coolant. An under-filled loop airlocks the moment thermal expansion or any flow-direction change moves coolant around. This single Tier-1 step solves a meaningful fraction of M53 thermal trips without further work.

4

Environmental sanity check. Verify a clear 30 cm of intake/outflow space front and back of the M53; verify ambient is within MicroBT spec (consult your sub-model's operation guide); verify the rack isn't packed so tight that adjacent equipment is heating the M53's air path. Hydro servers reject less waste heat into the room than air-cooled units, but a packed rack still raises coolant return temperature and increases cavitation risk.

5

Do NOT loosen QDs as a bleed shortcut. Whatsminer hydro QDs are designed for closed-loop hot-swap, not atmospheric venting. Cracking a QD pulls air in, contaminates the coolant, and risks tripping `WATER_LEAK` from drips at the QD face. Bleed via the reservoir cap, which is designed for this — there is no faster legal shortcut.

6

Cut miner power at the PDU; verify the coolant pump stays energized. Trip the M53's dedicated breaker or pull the C19 from the PSU. Confirm the coolant pump (internal pump on standalone M53s, CDU pump on rack-mounted hydro deployments) keeps running. If pump and miner are on the same power rail, fix this wiring during the repair so future bleeds work without scrambling for a separate supply. Wait 5 minutes after miner power-off before any further work.

7

Run the documented tilt-and-bleed sequence with pump running and miner unpowered. Tilt the M53 chassis through four orientations, 60 seconds each, in this order: front-up, back-up, left-side-up, right-side-up. As coolant level drops in the reservoir / CDU (air being driven out leaves void behind), top up with deionized water (D-Central's hydro guide is explicit: never tap, never automotive antifreeze) or your loop's spec coolant. Repeat the four-orientation cycle until reservoir level holds steady through a full cycle and the sight glass shows zero bubbles for 2 continuous minutes. Most M53 airlocks clear in 10-15 minutes of disciplined bleeding.

8

Slow-leak inspection with paper towel and flashlight. Wipe every fitting, every QD, every barb, every hose joint. Look for moisture that returns within 60 seconds of wiping — that's a working weep. Pay special attention to QDs that have been hot-swapped in the last week, fittings on the operator-side CDU loop, and the reservoir cap. Slow leaks under 1 drop per hour don't trip `WATER_LEAK` but they bleed prime and seed repeat airlocks. Found one → tighten, replace seal, or replace fitting. None found → continue.

9

Coolant level audit against operator log. Compare today's reservoir level to last week's reading in your maintenance log. A measurable drop of 50 mL or more per server per week with no recorded top-ups is a slow-leak signature, not just an airlock. The bleed will clear today's symptom; the leak hunt is what stops the next one. If you don't keep an operator log, start one — three lines per maintenance event is enough.

10

Pump bench test. If repeat airlocks persist after a clean bleed and a leak inspection, the pump itself may be on its way out — a partially blocked impeller cavitates harder than a clean one. Disconnect pump from the loop, energize on a bench `12 V` or `24 V` supply (verify pump spec), run inlet from a jug into outlet to a measuring jug, time 30 seconds of flow. Compare to nameplate flow rate (typically ~600-1500 L/h on Whatsminer hydro pumps — verify per model). Below 60% of nameplate → pump is the deeper cause; replace.

11

Coolant chemistry sample check. Draw 10 mL from the reservoir into a clean container. Inspect: clarity (cloudy = biological growth or mineral precipitation), colour (rust-tinged = internal corrosion), pH using a test strip or meter (target ~7-9 on most hydro coolants — acidic = inhibitor depletion or contamination). Degraded coolant gases out faster than fresh coolant under cavitation events, which is why old loops airlock more readily than new ones. Fail any check → drain and refill at Step 13.

12

Full loop drain (Tier 3). Close any farm-side isolation valves, uncouple QDs over a 10 L drip tray, expect 0.5-1.5 L of back-drained coolant per server (volume varies by sub-model and CDU loop length). Cap both QD ports with the supplied dust caps to keep contamination out. Move the server to a clean bench with drip-tray coverage. This is the precondition for everything in Tier 3.

13

Flush and refill with fresh spec coolant. Reverse-flush the loop with 2-3 L of fresh deionized water until discharge runs clear of any prior-coolant colour or particulate. Then refill with MicroBT-spec hydro coolant (propylene-glycol / DI-water blend at the concentration specified for your M53 sub-model, with corrosion inhibitor — verify against MicroBT support article 485). Document the refill date in your maintenance log; next replacement is 12 months out.

14

Pressurized leak test at nameplate. Before re-energizing, pressure-test the loop with a bench pump or your CDU's prime mode at nameplate pressure (typically 0.15-0.25 MPa on Whatsminer hydro — verify against your sub-model's spec sheet) for 15 minutes. Inspect every fitting, QD, and coldplate gasket edge. If you have a UV fluorescein dye kit (~$40 CAD for an automotive A/C kit), add 5-10 ppm of food-grade fluorescein to the loop and inspect under a 365 nm UV lamp — localizes any weeping seam in under 20 minutes.

15

Re-couple to the production loop and run the full bleed (Step 7) for 15-20 minutes minimum. Watch for cavitation tick, watch the sight glass, top up reservoir as needed. Verify zero bubbles for 2 continuous minutes before energizing the miner. Skipping this final bleed after a Tier 3 drain-and-refill is the most common reason a server returns to the bench with the same symptom within a week.

16

Energize the miner and run a 30-minute burn-in. Watch all three hashboard temps. Healthy M53 thermal signature: hashboards stabilize at ~55-70 °C (varies by sub-model and ambient), coolant return at ~30-45 °C, no `5070`/`5071`/`5072` codes, no `300`/`301`/`302`/`350` codes, hashrate locked to nameplate within ±2%. Burn-in clean for 30 minutes → return to production. Any code returns → airlock structural cause unaddressed; ship to a hydro-capable bench.

17

Stop DIY and ship to D-Central when: two consecutive full-bleed cycles fail to hold flow under load, one hashboard repeatedly trips first regardless of orientation, pump bench-test is below 60% of nameplate, coolant chemistry is degraded with no spec replacement on hand, the loop won't hold nameplate pressure for 15 minutes, chassis shows heat damage near the coldplate region, or you lack a calibrated 1-20 N·m torque wrench. These conditions require bench-level diagnostics.

18

D-Central bench process for hydro airlock work: full chassis teardown with loop drained; internal manifold inspection under bore-scope for debris, scale, biological growth, or coldplate intake clogs; coldplate-to-hashboard joint inspection (gasket integrity, torque audit); bench pump validation under programmable load; pressure-and-dye test of the entire server-side loop at nameplate pressure for 30 minutes; coolant chemistry replacement to MicroBT spec; re-assembly with calibrated torque on every fastener (every coldplate bolt's torque value goes into the service record); final bleed-and-burn-in for 24 hours at nameplate hashrate; per-board flow validation to confirm all three hashboards see equal coolant velocity.

19

Shipping prep — drained, only. Drain the server completely. Blow out residual coolant with low-pressure compressed air (`0.05 MPa` maximum — never exceed nameplate pressure into a drained loop). Cap both QDs with supplied dust caps. Double-box with at least 5 cm of foam on every side. Never ship a hydro server with coolant in it — transit vibration tears hoses and turns a repairable airlock into a chassis-wide flood. Label the outer box `HYDRO ASIC — DRAINED — FRAGILE`. Include a diagnostic note: observed symptoms, time-to-trip, log excerpts (`5070`/`300`-series), firmware version, coolant age, recent maintenance history. This detail saves D-Central bench time and saves you money.

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.