Skip to content

We're upgrading our operations to serve you better. Orders ship as usual from Laval, QC. Questions? Contact us

Bitcoin accepted at checkout  |  Ships from Laval, QC, Canada  |  Expert support since 2016

ERR_LOW_HASHRATE Warning

Antminer L7 – Low Hashrate

Realized Scrypt hashrate falling more than 10-15% below the Antminer L7's bin nameplate (8.3 / 8.5 / 8.8 / 9.05 / 9.16 / 9.3 / 9.5 Gh/s), usually driven by a dying BM1496 chip, an aged APW12 PSU sagging under heat-soak, a lost PIC I2C handshake, a firmware autotune regression, or dried thermal paste.

Warning — Should be addressed soon

Affected Models: Antminer L7 (all bins: 8.3, 8.5, 8.8, 9.05, 9.16, 9.3, 9.5 Gh/s)

Symptoms

  • Realized Scrypt hashrate is 10-40% below bin nameplate (L7 ships 8.3-9.5 Gh/s; check the chassis sticker, not the marketing page)
  • ASIC status page shows chips reading `X` instead of a frequency on one or more chains
  • `kern.log` / cgminer shows `ChipSetting_get_addr_LTC detect 0 chips` on boot
  • `kern.log` shows `check_asic_number_with_power_on: Chain[X]: find 0 asic` or `Chain X only find Y ASICs, will power off hash board X`
  • Per-chain Gh/s rollup is wildly uneven — e.g. chain 0 at 3.1 Gh/s, chain 1 at 3.0 Gh/s, chain 2 at 1.2 Gh/s
  • Hashrate collapses when ambient rises above 28-30 °C at intake (firmware rolls frequency back before throwing `ERROR_TEMP_TOO_HIGH`)
  • `fail to read pic temp for chain X` in `kern.log` — PIC16F1704 lost its I2C handshake with control board, chain is capped in limp mode
  • Intermittent drops that recover after a minute and return — silent chip-reset pattern on aging `BM1496` silicon
  • `APW12` PSU fan ramps hard at steady-state low load — primary-side capacitor aging
  • Realized Scrypt hashrate at the pool is 5-15% below what the miner dashboard reports — pool-side rejection stacking
  • Hashrate dropped immediately after firmware flash or autotune run and didn't recover — regression or wrong-version flash
  • `V:1` prompt or `ERROR_POWER_LOST` preceded the drop — voltage-sense wire or PSU handshake broken
  • Runs clean for an hour then hashrate tanks; recovers after 15 minutes off — classic `APW12` heat-soak sag

Step-by-Step Fix

1

Cold-boot at the breaker for 60 seconds, then power back up. Scrypt-pipeline ASIC drivers occasionally wedge after firmware updates or PSU dips, and a full cold boot clears driver state. Soft-reboot from the UI does not; physical power-off is required. If hashrate recovers to within 5% of your bin nameplate after the cold boot, you are done — log the date so you can catch a recurring pattern.

2

Revert to stock (no autotune, no OC) firmware profile and observe for 15 minutes. Some autotune builds for the L7 generation have shipped with aggressive bin assumptions that cause silent deration on older silicon. If hashrate returns to nameplate, stay on stock or flash DCENT_OS — its autotune is more conservative and exposes per-chip numbers so you can see what is actually happening.

3

Shop-vac the chassis intake, wipe the front grille, and verify that nothing is within 15 cm of the air intake. L7 generation chassis airflow is marginal at the best of times; dust on the filter or a curtain across the intake adds 3-5 °C to inlet temperature and triggers firmware-side frequency rollback long before you see `ERROR_TEMP_TOO_HIGH`.

4

Verify intake air temperature with an IR thermometer or cheap thermocouple at the front grille itself — not room-middle, not the hallway. Target is `≤ 30 °C`; above that, the L7 starts rolling frequency back. If you are running a summer deployment in a garage or shed with no active cooling, this is the most common single cause of the complaint.

5

Check the Bitmain downloads portal (`service.bitmain.com/support/download`) for your specific L7 hardware revision. L7 shipped across at least three hardware revisions with non-interchangeable firmware. If you are on a known-buggy autotune build for your revision, roll one version forward or back — but verify the target version matches your hardware ID before flashing, or you will brick the control board.

6

Measure `APW12` output at the PSU-to-hashboard 6-pin connector under load, using a multimeter on DC with the miner hashing at full throttle. Target `≥ 14.2 V` sustained. Below that and the PSU is tired — primary-side electrolytic caps have dried and the rail droops under sustained L7 draw (~3425 W at the 9.5 Gh/s bin). Swap the `APW12` with a known-good unit. If hashrate returns to nameplate, you had a sagging PSU; mark the old `APW12` for recap or retirement.

7

Verify wall input voltage under load: `200-240 V AC` measured at the outlet while the miner is hashing. L7 on a 110 V circuit will boot but cap at roughly 50-60% of nameplate — the firmware detects the reduced input envelope and derates. If the outlet reads below `200 V AC` under load, fix the electrical feed (dedicated 240 V circuit is strongly preferred) before replacing any miner hardware.

8

Power off at the breaker, pull each hashboard, and re-seat every data ribbon and power connector. Inspect contacts for corrosion, blackening, or bent pins — L7 ribbon connectors in humid environments oxidize within 12-18 months. Clean pins with 99% isopropyl alcohol on a lint-free wipe; do not use contact cleaner on the ribbon-side contacts. If ribbons show wear, swap in a fresh set — replacement L7 ribbons run `$10 – $25 CAD`.

9

Swap hashboards between the three slots. Label slots 0/1/2 with tape. Move the short-count board to a slot that was known-good before. Power up and observe 10 minutes. If the fault follows the board, the board itself is the problem — proceed to Tier 3. If the fault stays in the slot, the control-board signal path or power delivery is the problem — inspect that slot's power harness and ribbon connector, then proceed to Tier 3 for firmware-level diagnostics.

10

Verify fan RPMs match nameplate under load. L7 chassis fans should hit `5500-6000 RPM` at steady state on stock firmware; under-spinning fans push intake and chip temps up, which triggers frequency rollback that presents as low hashrate. Replace any fan reading under `4000 RPM` — cheap noise-optimised aftermarket fans are a common cause of silent thermal throttling on L7 units bought second-hand.

11

Flash DCENT_OS — D-Central's own open-source Antminer firmware, built by the Mining Hackers with per-chip HW%, conservative autotuning, and tuning controls you cannot get on stock. Alternatives: Vnish or LuxOS where they publish an L7 build. All expose per-chip statistics via their dashboards, which is the single biggest diagnostic upgrade available on an L7. Let the miner stabilize 20 minutes after flash, then record the worst chip positions on each chain — that tells you whether you are chasing 1-2 bad chips or a whole-domain failure.

12

Reflow the worst-performing chip. Preheat the bottom of the board to `~150 °C`, flux the target BGA, apply top-side hot air at `~310 °C` for `~30 s`, let cool naturally, re-apply thermal paste, reassemble. `BM1496` tolerates a reflow cycle well in practice. If one or two chip positions were dragging the chain, reflow recovers ~40% of short-count faults. Two failed reflows on the same chip = replace the chip; one-chip replacement on an L7 board at D-Central runs `$85 – $150 CAD`.

13

Replace thermal paste on all chips with Arctic MX-6 or Thermal Grizzly Kryonaut. Uniform thin layer, don't glop it on. Pay particular attention to the voltage-domain ICs and the PCH — thermal pads on those parts degrade faster than chip paste on L7 hardware, and a dried pad drives drift that looks exactly like silicon aging. Full re-paste job takes ~45 minutes per miner and frequently recovers 5-10% hashrate on a unit that has been in service for 18+ months with no thermal service.

14

Visually inspect the voltage-domain capacitors and MLCCs around the PMIC on each hashboard. Bulging electrolytics, cracked MLCCs, or any discolouration is a replace-on-sight signal. This is a soldering-iron + hot-air job, not a reflow job, and is within DIY range if you are comfortable with surface-mount rework. If you are not, stop here and ship to D-Central — installing the wrong capacitor value is worse than leaving a dried one in place.

15

Roll firmware to the last-known-good version for your specific L7 hardware revision. Verify the hardware table on Bitmain's downloads portal before flashing — wrong firmware for a late-rev L7 bricks the control board and the SD-card recovery path on some L7 revisions is eMMC-only, which means a brick is a ship-to-bench event. Back up any config before the roll.

16

Stop DIY when any of these are true: per-chip data isolates the same chip position on two different boards in the same rig (PCB-level issue, not chip), PMIC or voltage-domain IC damage is suspected, a second reflow on the same chip fails within 30 days, capacitor bulging or a burnt-component smell is present, or the `fail to read pic temp` fault persists after ribbon swap. You are now in test-fixture and PIC-reflash territory. Book a D-Central ASIC Repair slot.

17

D-Central bench process: Scrypt-chain test fixture with programmable load, per-chip isolation using official Bitmain Scrypt test binaries, `BM1496` chip replacement from graded salvage or new-old-stock, official Bitmain PIC re-flash tool, reflow + reseal, 24-hour full-load burn-in at nameplate before ship-back. Canadian turnaround: 5-10 business days. US and international accepted.

18

Ship safely: hashboards in anti-static bags, double-boxed with `≥ 5 cm` foam on every side. Include a note with exact observed symptoms, firmware version, hardware revision, and contact info. Every minute of bench diagnostic time saved is money saved — we charge by the hour once past triage, and a clean symptom description is the single biggest factor in keeping your repair bill at the low end of the CAD range.

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.