Whatsminer Error 5070-5072 – Water Velocity Abnormal
Warning — the miner is still running, the BTMiner firmware is throttling or pre-emptively shutting down one hashboard to protect silicon because it cannot confirm coolant flow
Warning — Should be addressed soon
Symptoms
- MinerTool / WhatsMinerTool fault log shows `Error Code 5070`, `5071`, or `5072` — a specific hash module (`SM0` / `SM1` / `SM2`) is named
- The literal error message in the miner log reads `SMx water velocity is abnormal` where `x` is `0`, `1`, or `2`
- Dashboard `Hashrate Real-Time (GHS)` drops to roughly two-thirds of nameplate (one hashboard throttled to zero) rather than a gradual sag
- Inlet / outlet temperature delta widens from the normal `~10 °C` (Normal mode) or `~14 °C` (High-Performance mode) to `>18 °C`, or it collapses to near-zero if the loop is stopped entirely
- Outlet temp climbs toward `65-70 °C` while inlet stays in spec — a tell-tale sign of flow loss on the miner side
- Audible whine or cavitation sound from the primary pump, or a visible change at the sight glass (bubbles, turbulence, or a slowing flow indicator)
- The other two `SMx` modules are unaffected — only one module is flagging, which points at the quick-connector / sensor on that specific board, not the whole loop
- Inlet pressure reads below `200 kPa` at the miner or the `4 bar` pressure-relief valve is venting
- LED on the front panel shows a slow red / amber blink pattern rather than a full red fault — the miner is degraded, not fully down
- Freshly-commissioned miner, never hashed at full power since install — strongly suggests airlock / unbled cold plate rather than a real flow fault
- BTMiner journal shows `hydro flow sensor timeout` or `water velocity below threshold` lines repeating every `30-120 s`
- Problem is worse in summer / during high-load hours — points at loop capacity, cooling-tower fouling, or upstream heat-exchanger fouling, not the miner itself
Step-by-Step Fix
Confirm the error code in WhatsminerTool / dashboard logs. The exact code controls the diagnostic branch.
Hard power-cycle for 60 seconds at the breaker. Bulk caps fully discharge, control board re-enumerates.
Verify ambient intake temperature ≤30 °C and clear the intake of dust, curtains, or stacked exhaust.
Check pool config and network path: ping pool host, telnet stratum port, and confirm worker credentials.
Update to the latest BTMiner stable firmware. Roll back one version if the error appeared after a recent update.
Re-seat all hashboard ribbon cables and PSU output connectors with chassis powered down at the breaker.
Measure PSU output voltage at the busbar under full load. Expected band depends on model — see spec sheet.
Swap suspected hashboard into another slot. Fault-follows-board = bad board; stays in slot = control path issue.
Pull WhatsminerTool log bundle (Remote Ctrl → ExportLog) and inspect upfreq_test.log + power.log + miner.log for sub-codes.
If on Hydro variant: verify coolant level, flow direction, and seal integrity before powering back on.
Reset to factory via WhatsminerTool (Remote Ctrl → Restore Miner). Wait 10-15 minutes for rebuild.
If software fixes have failed, escalate to bench: D-Central ASIC Repair has the test fixture and donor parts.
Ship hashboards in anti-static bags, double-boxed with foam. Include a note with observed codes and firmware version.
Include current SSH access and your contact info — saves diagnostic time which saves repair cost.
Plan a 5-10 business day turnaround for Canadian shipping; international add transit time.
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.