IceRiver Error 110/111/120/121 Fan Speed Abnormal Fix

Hard power cycle from the rear rocker. Full disconnect for 60 seconds, then power back up. Not a soft reboot from the web UI - the IceRiver controller needs a true cold start to clear latched fan-governor state. Roughly 1 in 6 fan errors clear here and don't return. If the same code returns within an hour, you have a real hardware fault - don't keep rebooting and hoping, you're cooking the `1004LV100` chips on the hashboards every minute the airflow is compromised. One reboot, one chance. If it recurs, tear in physically.

Check intake and exhaust obstructions. Walk to the miner. Front grille: anything within 30 cm blocking it? A wall, another miner stacked above, a curtain, dust accumulation around the perimeter? Same check rear grille. Both fans need clear airflow paths - IceRiver's chassis was designed for free air on both sides. Cleared the obstructions and the codes still fire? Continue. But if you skipped this in the rush to tear in, you may have just spent two hours diagnosing a curtain or a dust-bunny drift.

Verify ambient at the intake with an IR thermometer or shop thermometer at the front grille - not room-middle. IceRiver KS-series spec a `0-35 °C` operating envelope, with `40 °C` as the absolute limit. If your basement or garage is at `38 °C` in July and one fan is already marginal, the controller can flag `110` because the marginal fan can't keep `Temp1` in spec. Verify ambient first before chasing electrical faults. If ambient is borderline, fix that first - ventilation, A/C, summer duct - and re-test.

Roll firmware back to last-known-good. If the codes appeared immediately after an IceRiver firmware update - common on KS5L / KS5M post-2024 builds with sensor-polling regressions - pull the prior firmware from https://www.iceriver.io/firmware-download/. Match firmware variant exactly to your model (KS3M, KS3L, KS5L, KS5M, etc.). Wrong-model firmware bricks the controller. Verify-flag: third-party `xyys` / `tswift` overclock firmwares for KS0 are out of scope - revert to stock IceRiver firmware first before diagnosing fan errors.

Open the chassis and inspect both fans visually. Kill power at the rear rocker. Remove the top cover (six Phillips #2 screws standard, two extra on KS5L / KS5M rear bracket). Try to spin each `12038` fan impeller by hand - both should spin freely with no grind, rattle, or catch. A stiff fan = bearing failure. A fan that spins fine but is dead under power = electrical fault. This single 60-second check splits your whole diagnostic tree, and it's the step every IceRiver field guide skips.

Blow out both fans with canned air. Upright can, short bursts. Hold each impeller still with a plastic probe while blasting - letting canned air backspin the fan induces back-EMF that stresses an already-tired bearing. Dust caked on the hub is a common cause of a `12038` that reads `0 RPM` but looks visually clean. Pet hair, basement carpet drift, garage workshop dust - any of these doubles bearing wear inside 6 months. Blow them out, blow out the heatsink fins downstream, blow out the front grille filter (if installed).

Reseat both fan connectors at the IceRiver control board. Power off, wait 60 s for caps to bleed. Locate the two 4-pin headers on the controller - silkscreen typically reads `FAN_F` (front) and `FAN_R` (rear), positions vary across KS3M / KS3L / KS5L / KS5M revisions. Disconnect each, visually inspect the shells for bent pins or a crushed latch, reseat firmly until you feel the positive click. Apply a trace of dielectric grease. Vibration backed the connector out once over 6-18 months - it'll do it again without help. This single step clears a meaningful fraction of `110/111` field tickets.

Measure `+12 V` at each fan header under load. Multimeter on DC volts, probe `V+` to `GND` on each fan header while the miner is powered on and commanded to spin the fans. Expect `11.8-12.2 V` steady on both. Below `11 V` or zero on the suspect side = control-board rail fault, go to Tier 3. Pulsing means the PWM driver is glitching, also Tier 3. Healthy `12 V` with a still-dead fan = fan or harness fault, continue. This split-test is the difference between a `$15` fix and a `$120` fix.

Continuity-test the fan harness end-to-end. Multimeter on continuity (beep) mode. Unplug the harness both ends. Probe `TACH`, `PWM`, `GND`, `+12 V` across the length of the cable. Any wire that doesn't beep = broken conductor, typically at the strain-relief bend point near the control board. Replace the harness - IceRiver uses standard 4-pin JST-PH on most KS-series revisions, but verify yours before ordering. A broken `TACH` alone throws `110` even if the fan and rail are healthy.

Swap the suspect fan into the opposite header (front <-> rear). Four-minute test, zero parts. Power off, unplug both fans, swap their physical positions on the controller (front fan to rear header, rear fan to front header), power on. If the error code migrates with the fan (e.g. `110` becomes `111`), the fan is dead and followed itself - order a `12038` replacement. If `110` stays on the front-header side regardless of which fan is plugged in, the board-side rail is the problem - go to Tier 3. This is the single most decisive diagnostic in the whole tree.

Replace the failed `12038` fan. IceRiver KS-series fans are `120 x 120 x 38 mm`, `12 V`, 4-pin PWM, dual-ball-bearing axial - `DF1203812B2UN` (~6,000 RPM, ~140 CFM) is the OEM equivalent that fits across KS1 / KS2 / KS3 / KS3L / KS3M / KS5L. Do NOT substitute a `120 x 120 x 25 mm` consumer PC fan - most top out at `2,000 RPM / 80 CFM`, the IceRiver heatsink stack needs more static pressure than a Noctua-class fan can deliver. You will be back at this diagnostic in two weeks. Verify-flag: confirm exact part number against your specific model and revision before ordering.

Replace the fan-rail SMD fuse on the IceRiver control board. If Step 8 showed `+12 V` dead on the suspect fan's header while the other rail was healthy, a fast-blow SMD fuse popped when the previous fan seized and drew stall current. The fuse is typically a `1206`-package fast-blow in the `2-4 A` range, sitting between the `12 V` supply trace and the suspect fan header. Identify by following the rail back from the dead header with a continuity probe. Hot-air rework station at `290 °C`, Kapton-tape adjacent plastics, lift the failed fuse, place the replacement, reflow. Verify rail returns to `12 V` before reconnecting a real fan.

Rework the PWM driver MOSFET on the IceRiver controller. Each fan header is fed by a small MOSFET that the controller toggles at `25 kHz` for PWM duty. A failed MOSFET reads either permanently-on rail (fan spins 100% always) or a dead rail (fan stays off, throws `110/120`). Identify the offending part by visual match against the nearest transistor footprint to the suspect fan header. Hot-air remove, clean pads with solder braid, reflow a matching replacement. Verify-flag: IceRiver does not publish controller schematics - D-Central identifies these MOSFETs by cross-reference against salvaged KS-series control boards. Without a salvaged reference unit, escalate to Tier 4.

Replace the `1004LV100`-adjacent thermal pad if cascaded heat damage is suspected. If the fan failure ran for hours and `Temp2` peaked above `80 °C`, the thermal pad between the `1004LV100` ASIC die and the heatsink can dry out or migrate. Symptom: even after you fix the fan, `Temp2` stays high. Tier 3 thermal service: lift the heatsink, clean residue with isopropyl 99% and lint-free wipes, apply fresh `0.5 mm` thermal pad or Arctic MX-6 paste depending on the original mount style, reassemble. Verify-flag: KS5L / KS5M heatsinks use a slightly different mount than KS3M - check before disassembly.

Re-flash the IceRiver firmware via SD card recovery if sensor subsystem is flaky or controller is bricked from a bad firmware update. Pull the correct image from https://www.iceriver.io/firmware-download/, write to a microSD with BalenaEtcher, insert into the controller's SD slot, power-cycle, watch for the recovery LED pattern (varies by model). Wrong image variant bricks the board permanently. DCENT_OS is NOT applicable here - IceRiver runs on completely different silicon (Kaspa kHeavyHash) and DCENT_OS is Bitmain-Antminer-only. Stick with IceRiver's official firmware archive.

Stop DIY when any of these are true: `+12 V` rail dead on both fan headers (not just one), visible heat damage or discoloration on the IceRiver controller, two fan failures within 30 days on the same unit (points upstream to PSU/grounding/ambient), fan failure paired with hashboard going dark or chip-count-mismatch errors, you attempted SMD rework and lifted a pad, or all four codes report simultaneously after a clean firmware reflash. That's D-Central repair-bench territory. Book a slot at https://d-central.tech/services/asic-repair/. Western English-language IceRiver repair authority - Canadian / US / international welcomed.

What D-Central does at the bench for IceRiver fan errors. Diagnosis against a known-good KS-series reference rig, component-level controller repair including SMD fuse and MOSFET replacement, fan harness remake with dielectric-greased connectors, full hashboard thermal service if overheat events cascaded from the fan fault, `1004LV100` chip-level rework if cooling failure damaged the silicon, and 24-hour nameplate burn-in (KS3M ~6 TH/s @ ~3,400 W; KS5L ~12 TH/s @ ~3,400 W; KS5M ~15 TH/s @ ~3,400 W) with both fans monitored via continuous polling before we ship the unit back. Verify-flag: nameplate hashrate / power values are directional.

Ship the whole miner, not the fan alone. The IceRiver fan assembly is fiddly to pack safely separated from the chassis. Double-box the full unit, remove and separately wrap the hashboards in anti-static bags, include a printed note with the dashboard error codes, firmware version, observed symptoms, and ambient operating conditions. That saves diagnostic hours on our side, which saves repair dollars on yours. Canadian customers ship to our Quebec bench and have the miner back in 5-10 business days. US and international welcomed - contact the repair desk for international shipping paperwork.