Bitmain Antminer Common Error Codes & Troubleshooting - Beginner’s Guide

Recently, many customers reported small issues with their machines. This is a concise troubleshooting summary to help you quickly identify and fix common Antminer errors.

1. Hardware Errors

ERROR_FAN_LOST — Fan Lost

Symptoms: Abnormal fan RPM or fan stopped; log shows fan lost error.

Causes: Loose fan connector, broken cable, fan motor failure, or control board fault.

Troubleshooting:

  • Check that the fan connector is firmly seated and the cable is intact.
  • Swap in a known-good fan to test. If still failing, replace the control board.
  • If multiple fans report errors, try restoring factory defaults.

 

ERROR_POWER_LOST — Power Lost

Symptoms: Miner fails to start or suddenly powers off; logs show power lost.

Causes: Loose power-control cable, faulty PSU, or loose busbar screws.

Troubleshooting:

  • Reseat power-control cables and check busbar screws are tightened.
  • Update firmware or test with another PSU.

 

ERROR_ASIC_LOSS — ASIC/Chip Loss

Symptoms: Hash board detects missing chips; logs report ASIC loss.

Causes: Unstable power, poor grounding, or physical chip damage.

Troubleshooting:

  • Try a different power supply and verify proper grounding.
  • If the issue persists, return the unit for factory repair.

 

ERROR_EEPROM_INFO — EEPROM Error

Symptoms: Miner fails to boot; logs show EEPROM exception.

Causes: Corrupted board firmware or hardware fault on the hash board.

Troubleshooting:

  • Attempt a firmware upgrade or card-flash recovery.
  • If unsuccessful, send the hash board to factory service.

 


2. Network Errors

WARN_NET_LOST / NET Err — Network Lost

Symptoms: Miner cannot connect to the pool; logs show network errors.

Causes: Loose cable, switch failure, incorrect network config, or LAN restrictions.

Troubleshooting:

  • Ensure the Ethernet cable is firmly connected; try another cable or switch port.
  • Check network settings (IP, DNS) and local LAN port rules.
  • Try another pool or contact your network administrator.

 

IP Conflict or Network Configuration Error

Symptoms: Miner cannot obtain IP or disconnects frequently.

Causes: IP conflicts, incorrect pool info, or ISP/port restrictions.

Troubleshooting:

  • Change the miner’s IP to avoid conflicts.
  • Verify pool URL, port, and worker name are correct.
  • Contact ISP to confirm whether required ports are blocked.

 


3. Temperature & Cooling Errors

High-Temperature Protection Triggered

Symptoms: Miner auto-shuts down; logs show overheating.

Causes: Dust-clogged heatsinks, intake air temperature too high, or blocked exhaust.

Troubleshooting:

  • Clean heatsinks and fans; ensure intake air is within 5–35°C.
  • Make sure exhaust is unobstructed; add extra cooling if necessary.

 

read temp sensor failed — Temperature Sensor Read Failed

Symptoms: Miner cannot read temperature data; logs show sensor error.

Causes: Faulty temperature sensor or overheating chip.

Troubleshooting:

  • Check for high-temperature operation; attempt card-flash recovery.
  • If the problem persists, try replacing the PSU or send for factory repair.

 


4. Firmware / Configuration Errors

ERROR_SOC_INIT — Initialization Failed

Symptoms: Miner fails to boot; logs show init error.

Causes: Loose ribbon cable, firmware corruption, or incorrect multi-board (daisy-chain) connection.

Troubleshooting:

  • Reseat ribbon cables and try card-flash recovery.
  • Check whether multiple hash boards are correctly connected.

 

Configuration Errors Preventing Mining

Symptoms: Miner connects to pool but reports zero hashrate; no earnings despite no obvious log errors.

Causes: Incorrect worker name, wrong pool settings, or factory-reset without reconfiguration.

Troubleshooting:

  • Verify the worker name format (no spaces, correct punctuation and character type).
  • Restore factory settings and re-enter pool details carefully.

 


5. General Troubleshooting Workflow (Recommended)

  1. Check logs first: Login to the miner backend (via IP) and review the Kernel Log to locate the first error.
  2. Stepwise elimination: Tackle problems in order — Hardware (fan, PSU, chips) → Network (cables, settings, pool) → Temperature/Cooling.
  3. Firmware and card flashing: Try firmware upgrade or card-flash recovery, following proper procedures (avoid bending boards).
  4. Factory repair: If physical damage is suspected (chip short, control board fault), contact a professional for RMA/repair.

Quick Checklist

  • Are all connectors and screws tight (fans, power, busbar)?
  • Is the network cable and pool configuration correct?
  • Is the ambient temperature within recommended range (5–35°C)?
  • Have you checked Kernel Log for the first error occurrence?
  • Have you tried a firmware update or card-flash recovery?

Support & Repair

If hardware damage is confirmed, please contact our team or Bitmain support. For step-by-step remote assistance, provide the miner model, serial number, Kernel Log output, and the exact error code.

Note: This guide is for common, non-destructive troubleshooting. If you are not confident, please seek professional repair to avoid voiding warranty or causing further damage.
Back to blog