Passer au contenu

Nous améliorons nos opérations pour mieux vous servir. Les commandes sont expédiées normalement depuis Laval, QC. Questions? Contactez-nous

Bitcoin accepté au paiement  |  Expédié depuis Laval, QC, Canada  |  Soutien expert depuis 2016

ICERIVER_LOW_HASH Warning

IceRiver KS5L Hashrate Below 12T: Per-Board Diagnosis (4T/board)

IceRiver KS5L hashing below 12 TH/s nameplate. Per-board math: 12 TH/s = 3 hashboards x ~4 TH/s each. Below-spec hashrate without an explicit error code typically means thermal-interface degradation on one board (dried pads / paste pump-out), PSU rail sag, single-chip degradation in a chain, ambient-driven heat throttle, or firmware regression. Stock dashboard shows rig hashrate; per-board readout is the diagnostic that splits the tree.

Warning — Should be addressed soon

Affected Models: IceRiver KS5L (12 TH/s nameplate), KS5M (15 TH/s, same chassis family), KS5 (legacy, 12 TH/s)

Symptoms

  • IceRiver web UI dashboard reports rig hashrate sustained below `12 TH/s` (typical fault range: `7-11.5 TH/s`)
  • One of the three hashboards reports `< 3 TH/s` or reads `0` while the other two look healthy
  • All three boards report similar but reduced numbers (e.g. each at `3.0-3.5 TH/s`) - system-wide throttle, not single-board failure
  • `Temp1` (intake) sustained above `55 C`, or `Temp2` (exhaust / chip-side) above `65 C`
  • Per-board `Temp2` reading is `5-10 C` higher on the underperforming board than on the other two - thermal interface failure signature
  • Hashrate gradually declined over weeks or months (chip drift, paste dry-out) rather than sudden drop
  • Hashrate cliff appeared immediately after a firmware update - `Temp` and dashboard look fine but rig won't return to nameplate
  • Pool-side reported hashrate on Kaspa pool tracks `15-35%` below local dashboard
  • Both fans pinned at maximum (~`6,000 RPM`) without an `Error 110/111/120/121` firing - silent thermal throttle
  • PSU is running hot or you've confirmed line voltage sag at the wall during the fault window
  • Miner running in ambient `> 30 C` (basement summer, garage, attic) without supplemental cooling
  • Last thermal service was `> 12 months` ago, or unit was bought used with unknown service history
  • Dashboard `chip count` per board reads below nameplate (KS5L: `36 chips per board x 3 boards = 108 total`; verify-flag against your revision)
  • Effective payout on Kaspa pool dropped `15-35%` over the same window the local hashrate dropped - confirms silicon, not stratum

Step-by-Step Fix

1

Read per-board hashrate from the IceRiver web UI. This is the single most important diagnostic on a below-12T KS5L, and 90% of operators never click into it. Navigate the dashboard to the per-board / per-chain status pane. Each board should sit at `3.8-4.2 TH/s` sustained. Record all three. If one is conspicuously lower, you've isolated the failed chain in 30 seconds. If all three are evenly low, the fault is system-wide and your next stop is `Temp1`/`Temp2` and ambient. This step costs nothing, takes one minute, and tells you whether you're looking at single-board or system-wide.

2

Read `Temp1` and `Temp2` per board. Same dashboard, same minute. Look for per-board asymmetry - a `Temp2` that's `5-10 C` higher on one board than its siblings is the smoking gun for thermal-interface failure on that specific board. Healthy KS5L sits at `Temp1 = 45-55 C` and `Temp2 = 50-60 C` per IceRiver's official optimal range. Above `Temp2 = 65 C` on a board, the firmware is silently downclocking that board to protect silicon - your rig hashrate drops, but no error code fires. Record per-board values; they guide every subsequent step.

3

Verify ambient at the intake with an IR thermometer at the front grille - not room-middle. KS5L specs `0-35 C` operating envelope; the practical sweet spot for sustained `12 TH/s` is `<= 30 C` ambient. Above `30 C` and you're in heat-throttle territory before any other fault enters. If you're chasing a summer hashrate drop and your basement is at `32 C`, fix the ambient before tearing into the chassis. Window A/C, summer duct, or relocate the miner. Canadian basements in February run a KS5L at `12.5 TH/s` happily; a Texas garage in August won't sustain `10 TH/s`.

4

Hard power-cycle from the rear rocker. `60 second` disconnect, then power back up. Watch the boot self-test (~`2 minutes`), then log per-board hashrate for 15 minutes after warm-up. If the rig returns to `12 TH/s` on cold start but drops back over hours, the fault is thermal - silicon and pads getting up to operating temp and something giving. That points squarely at thermal-interface degradation (Tier 3 Step 11). If the rig stays low immediately after cold boot, the fault is upstream of thermal - PSU, firmware, or hard chip damage.

5

Clean both fans and the front grille filter. Canned air, short bursts, hold each `12038` fan impeller still with a plastic probe to avoid back-spin EMF on the bearing. Blow out heatsink fins downstream of the fans. Wipe the front grille filter (if installed). Pet hair, basement carpet drift, garage workshop dust - any of these halves effective airflow inside `6 months` and the controller silently downclocks to compensate. Single Tier 1 step that recovers a meaningful fraction of below-12T cases without any disassembly.

6

Roll firmware back to last-known-good. If hashrate cliff appeared right after a firmware update, this is your suspect. Pull prior KS5L-specific firmware from https://www.iceriver.io/firmware-download/ - match the variant exactly. KS3M firmware on a KS5L bricks the controller; KS5M firmware on a KS5L mis-clocks the boards. Flash through the dashboard updater (or SD-card recovery if dashboard is unstable), wait for reboot, observe per-board hashrate for 30 minutes after warm-up. If the rig returns to `12 TH/s`, firmware regression confirmed - pin to that build. Verify-flag: community reports of regression-prone 2024-2025 KS5L builds.

7

Probe the PSU output rail under full load. Multimeter on DC volts. Locate the PSU-to-controller / PSU-to-board power connectors. Probe `V+` to `GND` while the miner is hashing at full load - not at idle, not at boot. KS5L PSU expects `12 V` main rail with `11.8-12.2 V` sustained tolerance under continuous ~`3,400 W` draw (verify-flag against your specific PSU revision; KS5L PSUs documented as low-headroom per VoskCoin community). Below `11 V` sustained = PSU tired or circuit undersized. Above `12.4 V` = regulation drift, replace before damaging boards. `BP-H-3640` is the canonical IceRiver-spec replacement (verify-flag).

8

Verify line voltage at the wall outlet under load. Voltage logger on the outlet feeding the miner, log for 30+ minutes during steady-state mining. North American `120 V`: expect `115-125 V`. `240 V` split-phase: expect `235-245 V`. Line voltage sag is the single most-diagnosed mystery low-hashrate cause across the entire ASIC repair industry. Evening sag during neighbourhood peak (6-10 PM) tracks A/C and dryer cycles in North American residential. If your KS5L hashrate dips evening and recovers overnight, fix upstream wiring - dedicated 240 V circuit strongly preferred - before chasing any hardware fault.

9

Reseat all hashboard data and power connectors. Power off at the rear rocker, wait `60 s` for caps to bleed, remove the top cover. Each KS5L hashboard connects to the controller via a ribbon (data) and a heavier power connector. Disconnect each, visually inspect contacts for blackening, corrosion, bent pins, or oxidation, reseat firmly until you feel the positive click. Apply a trace of dielectric grease on the power connectors to immune them against chassis vibration backing them out over 12+ months. Partially-seated power connector causes voltage droop on that board only - exact symptom: one board reads `3.0-3.5 TH/s` while others are `~4 TH/s`.

10

Swap the suspect board into a known-good slot. Power off. Label the three KS5L hashboard slots `0/1/2` with tape. Move the underperforming board to a known-good slot, move a known-good board into the suspect slot. Power on, log per-board hashrate after warm-up. If the fault follows the board (previously-bad-board still reads low in its new slot), the board is the problem - Tier 3 thermal service or Tier 4 component-level repair. If the fault stays in the slot (a different board now reads low), the controller-side path (cable, connector, voltage rail to that slot) is the problem - Tier 4. Most decisive test in the whole tree, four minutes, zero parts.

11

Re-pad / re-paste the underperforming board's thermal interface. High-leverage Tier 3 fix for the 50%+ of below-12T cases driven by thermal-interface degradation. Power off, remove the top cover, lift the heatsink off the affected board (count and remove heatsink retention screws - KS5L typically `8`, KS5M `10`; verify-flag). Carefully separate heatsink from the `1004LV100` chip array. Clean residual thermal compound from chip dies and heatsink with isopropyl `99%` and lint-free wipes. Apply fresh `0.5 mm` graphite/silicone thermal pads (verify-flag - mount style varies by revision; some units ship paste-only), or apply Arctic MX-6 / Thermal Grizzly Kryonaut paste in a thin even layer across each die. Reassemble with even torque on retention screws - uneven mount pressure re-creates the same fault. Power on, observe per-board hashrate and `Temp2` for 30 minutes.

12

Inspect the `1004LV100` chip array for visible damage on the underperforming board. While the heatsink is off, inspect each chip with a magnifier. Look for: cracked package edges, lifted BGA corners, scorched solder mask near a chip, discolouration on the PCB substrate around a chip, or a chip visibly shifted from its footprint. Any of these = the chip is dead or dying, no thermal service will fix it. Document position of any damaged chip. Recovery path is either chip-level rework (preheat + hot-air at `310-330 C`, lift and replace with salvaged-grade `1004LV100` from D-Central parts inventory; verify-flag - IceRiver chip salvage market is thin compared to Bitmain BM1398) or full board swap from D-Central KS-series inventory at the bench.

13

Voltage-domain probe on the underperforming board. Power off, multimeter on DC volts. Each KS5L hashboard has a local voltage regulator chain converting the `12 V` main rail into `1004LV100`-required core voltage (verify-flag - exact core voltage varies; IceRiver does not publish board schematics, D-Central pattern-matches against analogous Kaspa hardware). Probe the local rail under load - sagging or pulsing `>=10%` below other boards' rail = local PMIC / inductor / regulator drift on that specific board, hot-air rework job. Territory between solo DIY and Tier 4 - parts ID requires either an IceRiver schematic (not published) or a salvaged reference board (D-Central has one). Most operators escalate to Tier 4 here.

14

SD-card firmware recovery flash for sensor-subsystem fault. If `Temp1`/`Temp2` are reading garbage values (`-10 C` style impossible readings), the controller's sensor subsystem is faulted and firmware is flying blind on thermal - manifests as bricked boards or wildly-throttled hashrate. SD-card recovery: pull official KS5L image from https://www.iceriver.io/firmware-download/, write to a microSD with BalenaEtcher, insert into controller's SD slot, power-cycle, watch for the recovery LED pattern. Wrong image variant bricks the controller permanently - confirm KS5L specifically before flashing. DCENT_OS is NOT applicable here - IceRiver runs `1004LV100` Kaspa silicon, completely different hardware than DCENT_OS targets. Stick with IceRiver's official firmware archive.

15

Stop DIY when any of these are true: visible heat damage / blistered solder mask / burnt-component odor on any board or controller; a second board on the same rig drops below spec within 30 days; suspected `1004LV100` chip-level damage on >1 chip per board; local voltage-domain regulator drift confirmed; thermal service attempted and board still won't return to `~4 TH/s`; per-board hashrate cliff after clean firmware reflash; you attempted SMD rework and lifted a pad; miner ran for hours with `Temp2 > 80 C`. Test-fixture territory. Book a D-Central ASIC Repair slot at https://d-central.tech/services/asic-repair/. Western English-language IceRiver repair authority - Zeus Mining (China) is the only competitor and their trust speaks for itself.

16

What D-Central does at the bench for KS5L below-12T faults. Diagnosis against a known-good KS5L reference rig with calibrated PSU and matched ambient - separates silicon-side from environment / supply faults inside an hour. Per-board hashrate isolation with a KS-series hashboard tester. `1004LV100` chip-level rework when a single failed chip is the cause - preheat plus hot-air, salvaged-grade or new-old-stock chip placement, full reflow and reseal. Full thermal service - paste / pad refresh on all three boards, controller reseat, fan inspection. Voltage-domain regulator replacement on the board if PMIC / local regulator drift is the cause. Controller swap from D-Central KS-series inventory if controller-side fault is diagnosis. 24-hour nameplate burn-in at `12 TH/s` (KS5L) or `15 TH/s` (KS5M) with both fans monitored and per-board hashrate logged before unit ships back. Verify-flag: nameplate values directional - confirm against exact SKU.

17

Ship the whole miner, not the boards alone. KS5L hashboards are fiddly to pack safely separated from the chassis - the `1004LV100` chips are cornerless and the heatsink-board sandwich can shift in transit. Double-box the full unit, optionally separate the boards into anti-static bags inside if you must ship hashboards-only. Include a printed note with the dashboard error context, current firmware version, observed per-board hashrate from your Tier 1 readout, ambient at the install site, and circuit voltage. That note saves D-Central diagnostic hours, which saves you repair dollars. Canadian customers ship to our Quebec bench, miner back in `5-10 business days`. US and international welcomed - repair desk handles international shipping paperwork.

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.