IceRiver Hashboard Repair Service: Pricing and Turnaround
Informational — Monitor and address as needed
Symptoms
- One or more hashboards report 0 hashrate or partial hashrate (4 T/s on a 12 T KS5L = one dead board)
- Dashboard reports a chip count of 9, 26, or partial value against a board that should report 52 (KS3 / KS5 series)
- Error codes 300 / 301 / 302 (temperature sensor fail) on a single board after re-seat and slot-swap
- Error codes 350 / 351 / 352 (overheat protection) recurring on the same board after thermal hygiene
- LDO voltage domain failure suspected - one or more 1.2 V / 0.65 V rails reading off-spec at the test pads
- Visible damage on the hashboard - burnt component, shorted MLCC, lifted pad, capacitor bulging
- Board no-power: D1 LED stays dark when the controller calls for hash, no current draw on the board's 12 V input
- Repeated Hashboard 0 / 1 / 2 faults that don't move with the board (controller-side, not a hashboard repair)
- PSU and ribbon cable already replaced and the fault persists on the hashboard
- Miner is out of warranty (third-party firmware flashed, IceRiver 1-year window expired, reseller without warranty pass-through)
Step-by-Step Fix
Confirm the fault is on the hashboard before shipping anything. Power down at the wall. On KS3 / KS5 series, slot-swap the suspect board into a known-good slot. Power up, observe 10 minutes. If the fault follows the board, you have a hashboard repair on your hands. If the fault stays in the slot, the controller, cable, or PSU is the problem and a hashboard repair will not help. KS0 / KS1 / KS2 are single-board - confirm via the diagnostic steps in their respective error pages instead.
Read the chip count and rail voltages from the dashboard. Note exact numbers: chip count (52 healthy / 9 / 26 / partial / 0), each board's reported Temp1 and Temp2, any error codes in the 300-302, 350-352, 710-712 ranges. This is your repair-quote input - every shop will ask. Photograph the dashboard with a phone and save the image.
Photograph the board top and bottom under bright light before shipping. Burnt components, lifted pads, and corrosion trails go on the photo log so you have proof of pre-shipping condition. Reputable shops will do their own intake photos; the gap between yours and theirs is the gap that matters in any later dispute.
Check the secondary-market price for your model's refurb hashboard right now. Kaspa Telegram groups, eBay completed listings, Reddit r/kaspa marketplace threads. Record the average closed price. If any repair quote you receive comes back at over 70% of that refurb price, the math says retire the board and buy a refurb instead of paying for the repair.
Multimeter the 12 V input rail at the board's input pads under load. Expect 11.8-12.2 V sustained. Below 11.5 V indicates PSU sag or upstream issue, not a hashboard problem. Document the reading for the repair-quote conversation - shops that are confident in their diagnosis will ask for it.
Visually inspect the board top and bottom under magnification: 10x loupe minimum, USB microscope ideal. Look for bulging electrolytic caps, cracked MLCCs, blackened components, lifted pads, corrosion trails, melted plastic on the input connector. Photograph any finding. Multiple visible faults push the repair into the LDO / multi-chip / catastrophic tier and change the math.
Re-seat the data ribbon and power connectors with the board out of the chassis. Inspect both header genders for bent pins. Reconnect, click home, retest. The IceRiver KB lists this as the #1 documented fix and it clears a meaningful share of tickets that look like a board fault but are actually a connector seating issue - costs you nothing and saves a diagnostic fee.
Check warranty status before paying for repair. IceRiver retail warranty is 1 year from dealer purchase. RMA goes back through the original dealer. If you are inside warranty, RMA is free; if you are outside, your only options are paid third-party repair or retire-and-replace. Third-party firmware flashing voids warranty - if you have flashed xyys / tswift, you are paid-repair only.
Build or buy a KS hashboard tester fixture before paying repeated diagnostic fees. D-Central stocks the universal KS tester and Zeus carries an equivalent. Probe chip count, rail voltages, and per-chain integrity outside the chassis. If you operate more than two KS-class miners, the fixture pays for itself by the third diagnostic visit avoided.
Identify the failed chip via thermal imaging on the test fixture. Power the board, wait 60 seconds for heat to develop, scan with a FLIR ONE Pro or equivalent IR camera. The dead chip is dead-cold; the over-stressed chip runs hotter than its neighbours. Mark the position with tape. This step replaces a $40-$120 CAD shop diagnostic with a one-time tool investment.
Hot-air the failed chip off the board. Preheat the PCB to ~120 C from below if a preheater is available, then top-side hot air at 300-320 C for ~30 seconds with a 13-15 mm nozzle on the chip. Lift cleanly with vacuum tweezers - no rocking, no scraping pads. Clean residual solder with braid. Match this exactly - over-temperature lifts adjacent components.
Install replacement chip. Source 1004LV100 (KS5 family) or KS3-family chip from a parts supplier (D-Central, Zeus, JinglMining). Apply solder paste or fresh solder balls, place chip with anti-static tweezers, reflow with hot air at the same profile. Let cool naturally - never force-cool, it cracks BGA joints. Clean with 99% IPA, re-test on the fixture for chip count and rail voltage.
Replace failed LDO and surrounding caps if the diagnostic points there. Same hot-air procedure, smaller package (typically SOIC-8 or DPAK). Match the original part number - IceRiver does not publish schematics, but Zeus's repair-parts catalog lists most LDOs by board revision. Reflow, clean, re-test. LDO failures are often paired with chip failures - inspect the surrounding domain before declaring the repair complete.
Replace failed temperature sensor for 300 / 301 / 302 codes. Cross-reference the I2C address using a logic analyzer probe on SDA / SCL if you have one; otherwise trust the part-number cross-reference from the board's silkscreen against an LM75A / TMP-series datasheet match. SOIC-8 or SOT-23-5 package depending on board revision. Reflow, clean, re-test.
Compute the break-even rule before authorizing any third-party repair. Total cost = diagnostic + repair line items + return shipping. If total exceeds 70% of the current refurb-board market price for your specific model (KS3 / KS3L / KS3M refurb at $220-$340 CAD; KS5 / KS5L / KS5M refurb at $280-$420 CAD), retire the board and buy refurb. The 30% margin covers downtime, post-repair reliability uncertainty, and your time managing the RMA.
Stop DIY and ship to a competent bench when: 3+ failed chips on the same board, LDO plus chip damage, water or corrosion past the chip footprint, burnt input section from a PSU plug melt-down, or you do not have hot-air rework + soldering capability. You are now in test-fixture-and-bench-tech territory. Confirm IceRiver scope on the D-Central ASIC Repair page before paying outbound shipping - KS-class coverage is being brought online; intake will direct you to ship or partner shop accordingly.
Ship safely. Hashboards in anti-static bags, double-boxed, at least 5 cm foam every side. Include a printed note: model and serial, observed chip count, rail voltage readings, error codes, exact firmware version, what you have already tried (cite step numbers from this page), and your contact information. The note saves diagnostic time, which saves you money on the final invoice. Insure the shipment for the refurb-replacement value, not the repair fee.
Ask three questions before authorizing any quote: (1) Does this include 24-hour burn-in at nameplate hashrate post-repair? (2) What is the warranty period on the repair (90 days is the mark of a confident shop; under 30 days is a signal to pick a different shop)? (3) If the repair fails within the warranty window, who pays the return shipping? A shop that answers these three cleanly is a shop you can trust with a $300+ CAD board.
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.
