Whatsminer Error 111 – Fanout Detect Speed Error
Warning — Should be addressed soon
Symptoms
- BTMiner dashboard or `get_error_code` API returns `E111` with message `Fanout detect speed error`
- `btminer-cli status` shows outlet/rear fan at `0 RPM` while intake fans read normal (5,800-6,200 RPM on M30S class; 6,000-7,200 RPM on M50/M60 class)
- MinerTool or Whatsminer Manager flags the exhaust fan icon red while intake fan icon stays green
- Kernel / `dmesg` log shows repeated `fan tacho: fanout timeout` or `fan[3] speed=0` lines at ~1 Hz poll interval
- Rear chassis grille visibly shows one fan stationary while the front intakes spin normally
- Hashrate drops 8-20% below nameplate within 2-3 minutes as BTMiner throttles frequency
- Intake fans audibly ramp to 100% within 60-90 seconds compensating for lost exhaust airflow
- `Error 2210` (Hashboard temperature too high) or `Error 620` (Environmental temperature high) appears in log within 5-15 minutes
- Brief tick or wobble from rear fan at boot, then silence - classic ball-bearing seizure on 12038 fan class
- Power-supply fan (reports as `Error 253/254` or `Error 274` separately) is NOT flagged - narrows fault to outlet fan path specifically
- Warm burnt-dust smell near rear grille when chassis reopened after extended fault
- Swapping front and rear fan harnesses moves `Error 111` to `Error 110` - confirms fan good, board-side path faulted (or vice versa)
Step-by-Step Fix
Power down at the PDU for 60 seconds, then power back up. This clears any wedged firmware state from the fan polling routine. On M50/M50S/M60S-class miners running BTMiner builds between `20221202` and `20230315`, Error 111 can false-trip at cold boot and self-clear within 2 minutes - this reboot is both diagnostic and fix for that case. Record whether the error returns immediately, after a delay, or not at all.
Confirm physical airflow. Rear grille needs at least 20 cm clearance; a wall, curtain, or dust-blocked heatsink behind the exhaust can back-pressure the fan enough to drop RPM below BTMiner's detection threshold. Shop-vac the rear grille, pull lint from finstack if visible, verify no cardboard or insulation pushed against the miner.
Check firmware version via BTMiner API or MinerTool. If on a build between `20221202` and `20230315`, download current stable from the official Whatsminer firmware portal and flash forward. A known polling-interval bug in that band raises spurious `Error 111` on healthy fans at cold boot.
Verify intake air temperature with an IR thermometer at the front grille - not room-middle, not ceiling. Target ≤ 30 °C for M30S class, ≤ 35 °C for M50S/M60S class. A basement at 38 °C forces the outlet fan to 100% PWM continuously, exposing marginal bearings that would have lasted another year at cooler ambient.
Factory-reset the miner from the dashboard per your model's procedure (M30S: 5 s hold; M50S: 10 s; varies). Rebuilds firmware config, which clears the rare case where corrupted `fan_config` block raises `Error 111` on a healthy fan. Back up tuning settings first.
Power down at the PDU (not just the web UI), wait 60 seconds for PSU caps to bleed down, then open the chassis. Never open the chassis with AC connected - the PSU holds dangerous energy for ~30 seconds after AC-off.
Locate the outlet fan harness on the control board. Label orientation before disconnecting. The rear-fan header sits at the back edge of the control board, silkscreened typically `FAN_OUT` or `FAN2`. Twisted 4-conductor cable runs from the fan to this header.
Unseat, visually inspect, and firmly re-seat the outlet fan connector. Look for: bent pins inside the plastic shell, green oxidation on the metal, cable strain pulling the shell partway out, mechanical damage to either half. Re-seat with firm push until you feel the detent click. Re-route cable away from fan blades and heatsink fins before closing.
If connector looks OK, multimeter-check the `+12 V` rail at the header with the miner running. Black probe to chassis ground, red probe to the `+12 V` pin (typically pin 1 on 4-pin header - verify silkscreen). Expected: `11.8-12.4 V` sustained. Below `11 V` = rail sag or popped SMD fuse. Above `12.5 V` = PSU fault (stop, don't hash further).
Frequency-mode the multimeter or oscilloscope on the `TACH` pin (typically pin 3 on 4-pin Whatsminer fan headers). Healthy fan produces a square-wave at roughly `200 Hz` while spinning at 6,000 RPM. No signal with the fan visibly spinning = bad fan tach winding or broken TACH trace on the control board.
Swap intake and outlet fan harnesses to isolate the fault. If the physical fans are healthy and you can reach both headers, move the rear fan to the intake slot and vice versa. If Error 111 moves to Error 110, the fan itself was bad. If Error 111 stays, the control-board outlet path is the fault.
Clean the hashboard finstack. Pop the fan shrouds, vacuum dust out of the finstack on the outlet side, wipe fan blades. A 30%-blocked finstack raises back-pressure the outlet fan fights, which pushes marginal bearings over the edge. Use compressed air or a shop-vac - never a wet cloth.
Tune the miner to a lower power profile temporarily while sourcing a replacement fan. If running in High Performance mode, drop to Eco or Low Power via MinerTool or BTMiner API. Lower chip temp = lower demanded PWM = less stress on the marginal fan while you wait for parts.
Replace the outlet fan with an OEM-spec 12038 unit (`AFB1212SHE`, `YD12038B2G`, or verified `12 V / 2.7 A / 6,000 RPM` equivalent). DO NOT substitute an under-spec aftermarket fan - BTMiner's current-sensing will raise `Error 111` on a fan that spins visibly but draws less current than expected. If the miner has >18 months continuous duty, replace both intake and outlet fans as a matched pair - the companion is usually weeks away from the same failure mode.
If the `+12 V` rail at the header is dead, find and replace the outlet-path SMD fuse. Typically `F2` on the control board, `1206` package, `3 A` fast-blow rating - verify against your control-board revision silkscreen. In-circuit resistance: healthy ≈ `0 Ω`, blown = open. Reflow the new fuse with hot-air station at `300-320 °C` for 30-45 seconds. If the new fuse blows immediately on re-power, there's a downstream short - inspect harness for pinch damage before installing a replacement fan.
Re-check TACH response after fan swap. With the new fan installed, probe the TACH pin in frequency mode at the control board. A working OEM-spec fan should produce a stable square wave at `~200 Hz` at nominal RPM. If you still see no signal with a known-good fan in place, the control board's fan controller IC or TACH trace is the fault - Tier 4.
Flash BTMiner forward if the version check (Step 3) shows you're in the false-positive `Error 111` bug band. Pull the current stable from the Whatsminer official firmware portal and flash via MinerTool. Back up your config first - BTMiner upgrades sometimes reset `fan_config` and custom tuning profiles. Verify firmware signature matches MicroBT's published hash before flashing.
Document your preventive-maintenance interval. D-Central bench data shows Whatsminer outlet fans fail on a rough schedule: M30S class at `14-22 months` continuous duty, M50S class at `12-18 months` (higher heat). Add a calendar reminder to pull fans, inspect bearings, and replace preemptively at the low end of that band - cheaper than an emergency service call during a cold Canadian January.
Ship the control board to D-Central when Tier 1-3 is clean and Error 111 persists: (a) verified OEM-spec fan in known-good slot reads 0 RPM, (b) `+12 V` rail clean but TACH produces no signal with a working fan, (c) SMD fuse replaced and blows again immediately. Bench-level SMD work: chip-off replacement of fan controller IC, trace repair with jumper wire, or full control-board replacement from D-Central's graded inventory. Ship control board alone in anti-static bag, double-boxed with foam, include note listing observed symptoms, firmware version, and Tier 1-3 steps already run.
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.
