How to troubleshoot my Bitmain Antminer if it shows 0 hashrate on one board?

Power Supply Verification

1. Measure voltage at the input terminal of the affected hashboard using a calibrated multimeter; values must remain within ±5% of nominal 12V under load.

2. Inspect PSU fan operation and output rail ripple—exceeding 150mV peak-to-peak indicates capacitor degradation or rectifier failure.

3. Cross-test with a known-good PSU rated for at least 10% higher wattage than the miner’s specified requirement.

4. Confirm that all 12V connectors are fully seated and free from bent pins or carbonized contact surfaces.

5. Observe whether other boards exhibit synchronized power-down events during high-load cycles, signaling insufficient total current delivery.

Physical Connection Integrity

1. Remove and reseat the flat ribbon cable connecting the faulty board to the control board, ensuring alignment marks match precisely.

2. Examine gold-plated edge connectors for oxidation or micro-scratches using 10x magnification; clean gently with isopropyl alcohol and lint-free swab if needed.

3. Check for mechanical stress on the cable near bends or routing clips—kinked or compressed sections disrupt signal integrity on SPI and UART lines.

4. Verify that no adjacent heatsink fins obstruct proper mating of board-to-backplane interfaces.

5. Replace the flat cable with a certified Bitmain replacement unit if continuity testing reveals intermittent opens in any conductor lane.

Thermal Behavior Assessment

1. Monitor real-time die temperature of the BM1387 ASIC chip via BMC telemetry or infrared thermal imaging; sustained readings above 85°C trigger automatic thermal throttling.

2. Inspect thermal paste application uniformity—dry spots, air gaps, or uneven thickness cause localized hotspots despite acceptable average surface temps.

3. Confirm that airflow velocity across the board exceeds 2.5 m/s using an anemometer placed 1 cm above the ASIC surface.

4. Evaluate heatsink mounting pressure by checking screw torque consistency—deviations beyond ±10% from 0.15 N·m specification induce poor interfacial contact.

5. Identify dust accumulation inside fin stacks using borescope inspection; blocked passages reduce effective heat dissipation area by up to 40%.

Firmware and Communication Diagnostics

1. Access the miner’s web interface and navigate to System → Logs to search for “PIC error”, “SPI timeout”, or “hashboard X offline” entries.

2. Execute telnet into the miner and run sudo cat /tmp/sysinfo | grep -i “hashboard” to validate enumeration status and firmware version per board.

3. Compare reported firmware revision strings against official Bitmain release notes for known regressions affecting specific board IDs.

4. Initiate a controlled reboot while monitoring serial console output for early-stage initialization failures tied to bootloader or FPGA configuration handshake.

5. Disable auto-tuning features temporarily to isolate whether dynamic voltage/frequency scaling logic misinterprets sensor inputs from the affected board.

Component-Level Electrical Testing

1. Probe VDD_CORE and VDD_IO test points adjacent to the BM1387 die with oscilloscope; unstable regulation or excessive noise implies LDO or MOSFET failure.

2. Test continuity between ground plane and chassis earth point—resistance exceeding 0.5Ω suggests grounding loop issues compromising signal reference stability.

3. Measure resistance across fuse links marked F1–F4 on the hashboard; open circuits indicate overcurrent events not logged in BMC.

4. Validate clock signal integrity at XTAL oscillator output using 100MHz+ bandwidth probe; jitter exceeding 5% RMS correlates strongly with hash rejection spikes.

5. Perform diode-mode checks on all DC-DC converter ICs to detect internal shorting or leakage paths draining bias current from critical rails.

Frequently Asked Questions

Q: Can a single damaged MOSFET on the hashboard cause complete hashrate loss?A: Yes. A failed high-side MOSFET in the core voltage regulator circuit prevents stable 0.85V delivery to the BM1387, halting all cryptographic operations.

Q: Does humidity exposure affect hashboard recognition even without visible corrosion?A: Absolutely. Relative humidity above 75% induces parasitic capacitance shifts on PCB traces, degrading timing margins for 20MHz SPI clock signals and causing intermittent enumeration failures.

Q: Why does the miner report full voltage but zero hashrate on one board?A: Voltage presence does not guarantee correct sequencing or regulation quality. Ripple amplitude, transient response lag, or phase misalignment between power rails can prevent ASIC logic state transitions despite nominal DC levels.

Q: Is it safe to swap hashboards between different Antminer models like S9 and S15?A: No. Pinout assignments, voltage domains, and communication protocols differ significantly—even physically compatible boards will fail to initialize or draw destructive current.