Avalon 1246 – Low Hashrate
Warning — Should be addressed soon
Symptoms
- CGMiner API `GHSmm` vs `GHSavg` divergence > 8% sustained 30+ minutes (theoretical vs actual hashrate per Canaan avalon10-docs)
- Pool-reported 24-hour hashrate is 10-40% below nameplate (85-90 TH/s) despite miner UI showing close-to-nameplate
- One of three `MW0` / `MW1` / `MW2` arrays shows fewer than 26 entries or median count below `3000`
- `ECHU[0 0 0]` reads all zero (no hashboard comms failure) but realized hashrate is low — rules out comm fault
- `PVT_T` per-chip temperature array shows one or more A3206 chips ≥ `90 °C` while board median sits `75-85 °C`
- `PVT_V` per-chip voltage array shows scatter > ±`30 mV` across a board — voltage domain drift
- AUC3 LED solid green, `SYSTEMSTATU = 3`, but realized TH/s is flat and low — quiet-failure signature
- Chassis inlet air at the front mesh is > `30 °C` even with room A/C running
- Controller log shows intermittent `CODE_MMCRCFAILED` warnings without full AUC dropout — marginal AUC3 IIC bus
- Controller log shows `mm_work_send_timeout` or `asic_freq_set_fail` on one specific MM slot
- Hashrate degrades gradually over weeks (thermal paste dry-out, capacitor aging) rather than dropping suddenly
- Stock PSU fan duty above 80% at steady state even though ambient is normal — AC input sagging
- Hashrate drops every evening at the same time (6-10 PM neighbourhood peak) and recovers overnight — line voltage sag
- Rig has been running 18+ months since last thermal paste refresh
- Hashrate dropped immediately after firmware flash or autotune change and did not recover
Step-by-Step Fix
Hard power-cycle at the PDU for 5 minutes. Not a soft reboot from the UI — a full power-off so the hashboard capacitors fully discharge and the AUC3 / MM controllers re-initialize cleanly. Clears wedged driver state that survives a warm reboot, resets any firmware-side frequency throttle that latched during an earlier transient, and is a 2-minute diagnostic that closes a surprising percentage of overnight-drop tickets before any tool comes out of the drawer.
Shop-vac the intake mesh, front grille, and fan blades. Dust build-up on the A1246 intake is the single most common mystery low-hashrate cause in D-Central's Avalon queue. 30 days of dust equals 5-10% hashrate drop per CryptoMinerBros field data and matches our own intake measurements. Make this monthly — it is the highest-ROI maintenance action on the entire rig, and it is not listed in Canaan's user manual.
Measure intake air temperature with an IR thermometer at the front mesh itself, not room-middle, not the hallway. Target `≤ 30 °C`. Canadian garage deployments in July can push `35 °C` at the intake even with the door open; the A1246 silently caps frequency above that threshold before any OVER_TEMP alarm fires. If inlet is > `30 °C`, improve ventilation before chasing any other cause — you will fix half of summer hashrate tickets here.
Pull the CGMiner API stats on port 4028 and record a baseline: `echo -n '{"command":"stats"}' | nc <miner-ip> 4028`. Save the output. You will compare against this after each subsequent fix step to know whether you are making progress. Without the API baseline, every later step becomes a guess. The A1246 UI alone does not expose `MW0`/`MW1`/`MW2`, `PVT_T`, `PVT_V`, or `ECHU` in actionable form — the API does.
Verify firmware matches your A1246 hardware revision. Look at the sticker on the MM3v2 control board, cross-reference avalonminer.org/firmware-document/, and confirm you are not running firmware from a different A12-series revision (A1246I vs A1246 standard). Mismatched firmware silently caps hashrate and cannot be cleanly rolled back because Canaan's bootloader is signature-locked on most A1246 batches.
Change miner DNS to `1.1.1.1` or `8.8.8.8`. Stock Canaan firmware defaults to `114.114.114.114` — a Chinese public DNS that resolves unreliably outside China. Symptom: stratum flapping, jagged pool-side dashboards, hashrate that looks fine on the miner but bad at the pool. This is a literal one-field fix, documented nowhere in the English A1246 manual — entirely community knowledge via Zeus Mining and BitcoinTalk.
Measure AC input voltage at the PSU under full load with a multimeter on AC, probing the PSU input while the miner is hashing at nameplate. Canaan spec: `180-264 V AC`. Real-world nameplate performance: `≥ 220 V AC` sustained. Anything below `220 V` drops hashrate silently because the chip frequency table derates. If you see `< 220 V`, fix the electrical feed (dedicated 240 V split-phase or commercial 208 V+ with balanced load) before replacing any miner hardware.
Measure DC rail at each PSU-to-hashboard connector under load. Record all three rails and compare. One rail materially below the others (drift greater than ~`50 mV` at the connector) equals PSU or cable fault on that specific board. Pay attention to connector oxidation: the A1246 power connectors in humid environments (coastal BC, Maritimes, basements) oxidize within 12-18 months and add resistance that looks exactly like PSU sag.
Swap hashboards between the three MM slots. Label slots 0/1/2 with tape. Move the underperforming board (identified from MW arrays in Step 4) to a known-good slot. Power up, stabilize 10 minutes, re-pull API stats. Fault follows the board = board-level problem, proceed to Tier 3. Fault stays in the slot = control board / AUC / cable path problem; inspect that slot's harness and ribbon, proceed to Tier 3 for bus tuning.
Re-seat every cable with the system powered off at the PDU. Pull each hashboard data and power cable, visually inspect pins for oxidation, blackening, or bent pins. Clean contacts with 99% isopropyl alcohol on a lint-free wipe. Reseat the AUC3 USB cable at both ends and replace it with a short shielded cable if the run exceeds `1 m`. A poorly-seated connector adds resistance, drops rail voltage under load, and caps hashrate with no named fault.
Run cgminer with conservative AUC bus settings: add `--avalon7-aucspeed 200000 --avalon7-aucxdelay 24000` to the cgminer launch command. Undocumented by Canaan, canonical in the cgminer ASIC-README. Conservative values double the IIC bus headroom, eliminate intermittent `CODE_MMCRCFAILED` retries, and in D-Central's Avalon repair queue recover 2-4% of effective hashrate on units with marginal AUC3 hardware without any physical repair.
Verify fan RPMs match nameplate under load via API `estats`. A1246 twin-bay fans should hit `4500-6000 RPM` at steady state under full load. Under-spinning fans push intake and chip temps up, triggering frequency rollback that presents as low hashrate. Replace any fan reading < `4000 RPM` — dust-laden or bearing-worn fans are a common silent cause of summer-only hashrate loss on units bought second-hand or deployed in dusty environments.
Refresh thermal paste on all three hashboards with Arctic MX-6 or Thermal Grizzly Kryonaut. Remove each heatsink, clean old paste with 99% IPA and lint-free wipes, apply a uniform thin layer (do not glop), reassemble with correct heatsink torque per the Canaan A1246 service guide. 18+ month old paste accounts for `2-5 °C` of junction-temp headroom. Full re-paste takes ~60 minutes and frequently recovers 3-8% hashrate on an untreated unit. Single highest-impact Tier 3 action for drift-style low-hashrate complaints.
Reflow the worst-performing A3206 chip identified from `PVT_T` / `PVT_V` outliers. Remove heatsink, flux the target BGA, preheat the bottom of the board to `~150 °C`, apply top-side hot air at `~310-330 °C` for `~30 s`, let cool naturally, re-apply thermal paste, reassemble. A3206 BGAs tolerate a single reflow cycle well. If one or two chip positions dominated the loss, reflow recovers ~40% of short-count faults. Two failed reflows on the same chip = replace the chip; single-chip A3206 replacement at D-Central bench runs `CAD $95 – $170`.
Roll firmware one version back or forward from avalonminer.org/firmware-document/, using a build confirmed by the BitcoinTalk Avalon A12 thread as good for your specific hardware revision. Canaan publishes no changelog, so community A/B testing is your de facto reference. Canaan's signed bootloader blocks firmware downgrade on many A1246 batches; if the current build is a regression and rollback is blocked, document the build version, flag the unit for bench recovery, and proceed to professional repair. Do not attempt unsigned firmware flashes — bricking via signature mismatch is a ship-to-bench event.
Inspect and replace voltage-domain capacitors on any hashboard showing `PVT_V` drift or > `30 mV` spread across chips. Bulging electrolytics, cracked MLCCs, or discolouration near the PMIC is a replace-on-sight signal. Iron + hot-air rework + correct-value capacitor stock. Continuous `80 °C+` operation drifts stock capacitors in 2-3 years. This is not a reflow job — it is SMD rework — and if you are not comfortable with component-level replacement, stop here and ship to D-Central. Installing the wrong capacitor value is worse than leaving a drifted one in place.
Swap the AUC3 with a known-good unit. If you have cleared every other layer and bus tuning did not help, the AUC3 itself may be dying. FTDI USB-bridge silicon ages poorly in the Avalon chassis fan-vibration and ESD-exposed environment. A replacement AUC3 is cheap insurance at `CAD $40 – $90` and is a 5-minute swap. If a fresh AUC3 restores hashrate, retire the old one — do not shelve it as probably fine.
Stop DIY and ship to bench when any of these are true: PVT_T / PVT_V isolates three or more failing chips on the same board, a PMIC or voltage-domain IC is suspected, a second reflow on the same chip fails within 30 days, capacitor bulging or a burnt-component smell is present, Canaan's signed firmware blocks a rollback you need for recovery, or a known-good AUC3 swap did not restore performance. Book a D-Central ASIC Repair slot. D-Central bench process on an A1246: programmable load plus Canaan factory test binary to map each chip individually, chip replacement from graded A3206 salvage or NOS stock, voltage-domain capacitor audit, full reflow and reseal, 24-hour full-load burn-in at nameplate with API logging to confirm the fix before ship-back. Canadian turnaround: 5-10 business days. Include your API stats dump in the shipment note.
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.
