Reference

Error-Code Reference

Searchable library of miner error codes and suggested checks — plus a status-light guide for reading the machine before it ever shows a code.

Error codes Status-light guide No code yet? Troubleshoot by symptom →

246 matching codes and 27 status-light entries

Error codes

Antminer

Common kernel-log strings

Code	Meaning	Suggested checks
Chain X find 0 asic	A whole hashboard isn't communicating	Power off; reseat ribbon + power; swap ribbon to isolate; RMA board if it stays.
ERROR_FAN_LOST	A fan is at 0 RPM / out of range	Reseat/swap the fan; if a good fan still reads 0 on that header, swap the unit.
over max temp, pcb temp X chip temp Y	Thermal shutdown to protect the boards	Fix airflow/dust/ambient; if a sensor reads 255, swap the board.
fail to read pic temp / read temp error	Temp sensor or its data path failed	Reboot, reseat data cable, reflash; if it stays, swap the board.
EEPROM error / chip bin not found	Board ID/calibration unreadable	Reseat ribbon, reflash correct firmware; persistent -> RMA board.
DNS resolve failed / all pools dead	Miner's network path is down (not the pools)	Fix link/gateway/DNS (8.8.8.8); verify pool URL/worker.

Antminer

Full kernel-log error library

Code	Meaning	Suggested checks
Chain X only find 0 asic	Board sees no chips; firmware powers it off (~1/3 hashrate)	Reseat/swap data cable (one end), reflash; else swap board + RMA.
Chain 0 only find 47 asic	Fewer chips than designed (dead chips / marginal domain)	Check temps/PSU, reseat cable, stock freq; swap board if dropping.
fail to read pic temp	PIC (power-mgmt/monitor IC) comms abnormal	Reseat data cable, SD/firmware reflash; else swap board + RMA.
read temp error	Hashboard temp sensor faulty	Reseat cable, reflash; faulty sensor -> swap board + RMA.
ERROR_TEMP_TOO_HIGH / over max temp	Over safe temp (~90-95 °C); throttle/shutdown	Clean dust, confirm fans, check inlet/exhaust, re-paste.
ERROR_FAN_LOST / fan speed error	Fan not detected or < ~1500 RPM	Reseat/swap fan; multi-fan -> factory reset; else control board -> RMA.
ERROR_POWER_LOST / error PSU lost	PSU not detected / output fault	Tighten busbar/strap, check power-control cable, swap PSU.
ERROR_SOC_INIT	Control-board SoC init fail at boot	Power-cycle, SD-card recovery; won't init -> control board RMA.
V_IN abnormal / Voltage out of range	Input voltage out of ~12.0-12.6 V	Measure/reseat PSU, verify facility voltage; surviving swap -> RMA.
pic_disable_dc_dc_common failed	Power IC can't manage DC-DC domains	Reseat cables, reflash; else swap board + RMA.
get power type version failed	PSU ID/type mismatch	Confirm correct PSU model, reseat signal cable, swap matching PSU.
EEPROM error / load EEPROM error	Can't read/corrupt hashboard ID chip	Reseat cable, try another CB slot, reflash; corrupt -> RMA.
chip bin not found	No chip-bin/tuning for that revision (often after wrong firmware)	Reflash correct stock firmware for the exact model.
reg CRC error / nonce crc error	Chip/domain data fails checksum - signal integrity	Reseat cable, stock freq, check PSU/temps; persistent -> swap board + RMA.
nonce error / rising HW%	Invalid results - over-freq / heat / unstable power	Set stock frequency, check temps/PSU; stays high -> RMA.
Data load fail	Chip fails only under load (marginal/temp-dependent)	Reseat, stock freq, soak-monitor; intermittent -> swap + RMA.
dev init failed	Device init failed at startup	Power-cycle, SD reflash, check seating; else RMA.
no beeper	Buzzer self-test note (NOT a hashing fault)	Cosmetic - note it, don't RMA over it alone.
chip X disabled	Firmware disabled a dead/non-responsive chip	Monitor the trend; escalate/RMA if the count climbs.
socket connect failed / Stratum interrupted	Can't reach the pool (network/config)	Fix pool URL/port/worker, check Ethernet/internet, static IP, DNS.
cgminer not running	Mining daemon crashed	Reboot / SSH restart, check config, reflash if unstable.
Firmware update failed / boot loop	Flash didn't complete / can't boot	Never power off mid-flash; retry, else SD recovery with correct image; loops -> RMA.

Antminer

Web-dashboard fault codes (status page)

Code	Meaning	Suggested checks
J1 / J2 / J4 / J8	Chain suffix used across the J/L/R/F codes: J1 = chain 1, J2 = chain 2, J4 = chain 3, J8 = chain 4 (bit-encoded, so J:6 = chains 2+3).	Read the suffix to see which hashboard a code points at before you pull anything.
J1:2 (also J2:2 / J4:2 / J8:2)	Dashboard fault code: that chain detected fewer ASIC chips than designed (J1/J2/J4/J8 = chains 1/2/3/4).	Power down, reseat then replace the hashboard ribbon cables, reflash firmware. If the chip count stays low, swap the hashboard.
J1:5 (J2:5 / J4:5 / J8:5)	Dashboard fault code: PIC chip anomaly on that chain - the control board lost the hashboard's PIC controller.	Reseat then replace the data cable to that board; reflash. If unresolved, replace the hashboard.
J1:4 (J2:4 / J4:4 / J8:4)	Dashboard fault code: EEPROM file error on that chain's hashboard (the ID/config chip data is bad).	Re-run the factory test for that chain to rewrite the EEPROM. If it won't take, replace the board.
J1:1 (J2:1 / J4:1 / J8:1)	Dashboard fault code: that chain has a damaged ASIC chip.	Reflash firmware; test with a known-good PSU. If it persists, the hashboard/chip needs bench repair or swap.
L1:1 (L2:1 / L4:1 / L8:1)	Dashboard fault code: that chain's voltage or frequency is out of allowed limits.	Reflash the correct official firmware for the exact model. If it persists, factory/bench repair.
L1:2 (L2:2 / L4:2 / L8:2)	Dashboard fault code: that chain's voltage or frequency does not match the expected profile.	Reflash correct firmware; re-run factory test. If it persists, board repair.
R:1	Dashboard fault code: whole-miner average hashrate is too low.	Reflash firmware; check the PSU (a weak rail drags every chain). If still low, bench the boards.
R1:1 (R2:1 / R4:1 / R8:1)	Dashboard fault code: that chain's hashboard is damaged or its hashrate is too low.	Check cabling, reflash firmware; if the board stays low, replace it.
V:1	Dashboard fault code: power-supply initialization error or wrong output voltage.	Check PSU output lines/connectors and busbar screws; reflash. If output voltage is wrong, replace the PSU.
V:2	Dashboard fault code: power supply is uncalibrated.	Reflash firmware; if it stays, the PSU needs recalibration or replacement.
F1:1 (F2:1 / F4:1 / F8:1)	Dashboard fault code: that fan is not detected or is running below the RPM threshold.	Reseat the fan's 4-pin connector; swap in a known-good fan. If no fans read at all, suspect the PSU or control-board fan header.
J:6	Dashboard fault code: temperature-sensor failure.	Reseat the hashboard data cable, reflash. If the sensor stays dead, replace the hashboard.
J:8	Dashboard fault code: fewer hashboards detected than the model should have.	Power down, reseat then replace the missing board's ribbon cables; move it to a known-good port. Still missing = board fault.
P:1	Dashboard fault code: high-temperature protection tripped.	Drop inlet temp and improve airflow, clean heatsinks/fans, and check thermal-pad/gel contact on the boards.
P:2	Dashboard fault code: low-temperature protection - too cold to start safely.	Warm the room above freezing and let the unit soak before starting; do not cold-start a frozen miner.
M:1	Dashboard fault code: memory allocation error on the control board.	Reflash / SD-card recover the control board. If it recurs, replace the control board.
N:4	Dashboard fault code: network connection lost.	Check the Ethernet cable and switch port; confirm pool/network settings and that the miner holds an IP.
N:2	Dashboard fault code: frequency was reduced too much (firmware auto-downtuned the chains).	Reflash firmware; investigate why it down-tuned (heat or a weak PSU rail).
N:1	Dashboard fault code: measured hashrate far exceeds the rated/sales hashrate (usually a mismatched or overclock firmware flag).	Reflash the correct official firmware for the model.
ERROR_TEMP_TOO_LOW	Kernel-log guard: ambient/chip temperature too low (roughly below -20C) to start reliably; the miner refuses to boot the boards.	Warm the space above freezing and let the unit soak before powering; do not cold-start a frozen miner.
ERROR_NET_LOST	Kernel-log: network link lost (cable/switch/DHCP) - distinct from 'socket connect failed', which is a pool-level failure.	Check the patch cable and switch port; confirm the miner still holds an IP.

Vnish

Vnish firmware - flash & fault notes

Code	Meaning	Suggested checks
can not find signature (on flash)	Signed Bitmain control board (Jun/Jul-2019+ batch) with overwrite protection blocking the write.	Flash with the matching signature file (e.g. signature_31july), or do an SD-card flash first, then reflash Vnish.
Retune on chain break	Vnish auto-recovery option: when a chain drops, the miner re-tunes instead of halting the whole board.	Leave it on for uptime. If a board keeps re-tuning, the chain has a real hardware fault -> pull and inspect.
DevFee (dev fee)	Small hashrate skim to the firmware maker. Tampering historically triggers a fixed penalty.	Leave it configured as shipped. Don't zero or block it or the unit self-penalizes and underperforms.
Hardware-revision mismatch	Vnish build must match the EXACT hashboard hardware revision. Wrong rev won't tune or boot right.	Flash the build made for that model's exact board revision. Verify the rev before flashing a whole batch.
Autotune ramp (post-flash)	After a flash or reboot Vnish runs per-chip autotune. Hashrate climbs over several minutes, not instantly.	Let the tune finish before judging hashrate or repowering. A mid-tune reboot restarts the whole ramp.
Immersion mode	Setting that tells Vnish the unit is submerged, so it stops flagging fan/airflow faults on fanless immersion.	Enable it on tanked units. Leave it off on air-cooled units or you lose real fan-fault alarms.

Whatsminer

Immersion / Hydro codes (5070)

Code	Meaning	Suggested checks
5070 / 5071 / 5072	SM0/1/2 water/liquid velocity abnormal	Confirm pump, clear kinks/clogged filter, check level + QDs seated, verify 8-10 L/min; if flow normal, replace the velocity sensor.

Whatsminer

Full error-code list — fan & power (official MicroBT)

Code	Meaning	Suggested checks
100	Fan unknown error.	Check the fan connection; replace the fan or the PSU.
110	Intake-fan speed-detect error.	Check the fan connection; replace the fan or the PSU.
111	Exhaust-fan speed-detect error.	Check the fan connection; replace the fan or the PSU.
120 / 130	Intake-fan speed error (RPM deviation 2000+ / 3000+).	Check the fan connection; replace the fan or the PSU.
121 / 131	Exhaust-fan speed error (RPM deviation 2000+ / 3000+).	Check the fan connection; replace the fan or the PSU.
140	Fan running too high — firmware maxed the fans.	Lower the environment/inlet temperature and check airflow.
200	No power found (power-probe error).	Check the power output wiring; update firmware or replace the PSU.
201	Power supply and config file mismatch.	Fit the correct PSU for the model (or update firmware to match).
202	Power output-voltage error.	Upgrade firmware or check the PSU.
203	Power protecting (thermal).	Improve PSU cooling / lower the environment temperature.
204	Power current protecting.	Improve PSU cooling / lower the environment temperature.
205	Power current error.	Record the fault and operating conditions. Qualified, authorized electrical personnel must assess the supply against the exact model/PSU specifications and site design, using the applicable test procedure. Do not probe, adjust the supply or substitute a higher-rated PSU as a learner action. Use their findings for further equipment diagnosis.
206	Power input voltage is low.	Record the fault and operating conditions. Qualified, authorized electrical personnel must assess the supply against the exact model/PSU specifications and site design, using the applicable test procedure. Do not probe, adjust the supply or substitute a higher-rated PSU as a learner action. Use their findings for further equipment diagnosis.
207	Power input-current protecting.	Record the fault and operating conditions. Qualified, authorized electrical personnel must assess the supply against the exact model/PSU specifications and site design, using the applicable test procedure. Do not probe, adjust the supply or substitute a higher-rated PSU as a learner action. Use their findings for further equipment diagnosis.
208	Power output changing too much.	Replace the PSU.
209	Set-vs-actual voltage deviation jumped suddenly.	Replace the PSU.
210	Power error status.	Read the PSU fault code on the Errors page and act on that.
211	Power output-current (Iout) deviation too large.	Reboot; if it repeats, replace the PSU.
213	Power Iin / Vin / Pin do not match the power.	Reboot or replace the PSU.
217	Power set-enable error.	Reboot; if it repeats, replace the PSU.
218	Input voltage is below 230 V in high-power mode.	Record the fault and operating conditions. Qualified, authorized electrical personnel must assess the supply against the exact model/PSU specifications and site design, using the applicable test procedure. Do not probe, adjust the supply or substitute a higher-rated PSU as a learner action. Use their findings for further equipment diagnosis.
219	Power input current is incorrect.	Replace the PSU.
233 / 234 / 235	Power output over-temperature protection.	Improve PSU cooling / lower the environment temperature.
236 / 237 / 238	Power output over-current protection.	Improve cooling and check the copper-bar (busbar) screws are torqued down.
239	Power output over-voltage protection.	Record the fault and operating conditions. Qualified, authorized electrical personnel must assess the supply against the exact model/PSU specifications and site design, using the applicable test procedure. Do not probe, adjust the supply or substitute a higher-rated PSU as a learner action. Use their findings for further equipment diagnosis.
246	Severe power over-current.	Replace the PSU.
250 / 251	Power input under-voltage protection.	Record the fault and operating conditions. Qualified, authorized electrical personnel must assess the supply against the exact model/PSU specifications and site design, using the applicable test procedure. Do not probe, adjust the supply or substitute a higher-rated PSU as a learner action. Use their findings for further equipment diagnosis.
253 / 254	PSU fan detection error.	Check / replace the PSU fan (or the PSU).
257	Power primary-side input over-current.	Reboot or replace the PSU.
263 / 264	Power communication error.	Check the control-board mounting screws are tight; reseat the power comms.
270	Power over-voltage protection.	Record the fault and operating conditions. Qualified, authorized electrical personnel must assess the supply against the exact model/PSU specifications and site design, using the applicable test procedure. Do not probe, adjust the supply or substitute a higher-rated PSU as a learner action. Use their findings for further equipment diagnosis.
274	PSU fan warning.	Check the PSU fan isn't blocked.
275	Power over-temperature protection.	Improve the PSU temperature / cooling.
901	Power-rate (efficiency) error.	Investigate power draw vs. hashrate; check PSU and power mode.

Whatsminer

Full error-code list — temperature, EEPROM & hashboard (official MicroBT)

Code	Meaning	Suggested checks
300-303	Slot 0-3 temperature sensor not found.	Check the adaptor bridge and the connection ribbons to that board.
320-323	Slot 0-3 temperature-reading (comms) error.	Check the control-board mounting screws are tight; reseat the ribbon.
350-353	Slot 0-3 temperature protecting (over-temp).	Lower the hashboard temperature — improve cooling / airflow / coolant.
380-383	Humidity sensor not found / reading error / protecting.	Check the humidity sensor and the environment humidity.
400	EEPROM unknown error.	Reseat and reflash; if unresolved, bench or replace the board.
410-413	Slot 0-3 EEPROM detect error.	Check the adaptor bridge and connection ribbons.
420-423	Slot 0-3 EEPROM parse error.	Upgrade firmware.
430-433	Slot 0-3 chip-bin type error (bad EEPROM data).	Upgrade firmware; if it persists the board's EEPROM/board needs service.
440-443	Slot 0-3 EEPROM chip-number error.	Upgrade firmware; check the board.
450-453	Slot 0-3 EEPROM read/write (xfer) error.	Reseat, then replace the adaptor bridge or ribbon.
500	Hashboard unknown error.	Reseat and inspect the board.
510-513	Slot 0-3 miner-type mismatch (board doesn't match the model).	Fit the correct board for the model / flash matching firmware.
520-523	Slot 0-3 chip-bin type differs from the other boards.	Don't mix board bins — fit matching boards.
530-533	Slot 0-3 not found.	Power off; check the ribbon and power to that board, then slot-swap to see if the fault follows the board.
540-543	Slot 0-3 reading chip-ID error.	Replace the adaptor bridge or the ribbon to that board.
550-553	Slot 0-3 has bad chips.	Bench the board; the failing chip(s) need rework or the board is replaced.
560-563	Slot 0-3 loss of balance.	Replace the adaptor bridge or ribbon.
570-573	Slot 0-3 chip transfer (xfer) error.	Reseat / replace the ribbon; bench the board if it persists.
580-583	Slot 0-3 reset error.	Reseat and reflash; bench the board if it persists.
590-593	Slot 0-3 frequency too low.	Reboot; if it stays low, bench the board.
600	Environment temperature too high.	Lower the ambient temperature and improve ventilation.
610	Environment temperature too high for high-power mode.	Lower ambient, or drop out of high-power mode.

Whatsminer

Full error-code list — chip, pool, firmware & security (official MicroBT)

Code	Meaning	Suggested checks
700	MAC address invalid.	Rewrite the MAC or RMA the control board.
710 / 711 / 712	Control board rebooted / down-clocked as an exception.	Upgrade the firmware and re-tighten control-board screws; if it repeats, replace the control board.
800	btminer file checksum error.	Re-upgrade the firmware (SD-card flash if an OTA update won't clear it).
801	system-monitor file checksum error.	Re-upgrade the firmware.
802	remote-daemon file checksum error.	Re-upgrade the firmware.
2010	All pools disabled / unusable.	Check the network or change the pool configuration.
2020 / 2021 / 2022	Pool 1 / 2 / 3 connection failed (user or password error).	Fix the worker/username and password for that pool.
2030	Pool rejection rate too high.	Check the network or the pool configuration.
2040	Pool lacks an important feature.	Use a compatible / correctly-configured pool.
2110-2113	Slot 0-3 factory-test step did not pass.	Board came back short of factory spec — bench-verify before returning it to service.
2310 / 2320	Hashrate too low.	Reboot and re-check; if it stays low, work the low-hashrate path.
2340 / 2350	Hashrate loss.	Reboot and re-check; investigate the board that dropped.
5010-5013	Slot 0-3 chip voltage too low.	Bench the board / its power domain.
5020-5023	Slot 0-3 chip voltage changing.	Bench the board / its power domain.
5030-5033	Slot 0-3 chip temperature spread too large.	Check thermal contact / cooling; bench the board.
5040-5043	Slot 0-3 hottest-chip temperature spread too large.	Check thermal contact / cooling; bench the board.
5110-5113	Slot 0-3 up-frequency (ramp) timeout — the board didn't reach target frequency in time.	Reboot. If it repeats on the same slot, treat it as a hashboard fault: reseat the ribbon, torque the copper-bar screws, inspect / swap the board.
520000-523999	Per-chip nonce error (slot/chip encoded in the code).	Bench the board; the identified chip is returning bad nonces.
530000-533999	Per-chip too-few-nonces (slot/chip encoded).	Bench the board; a weak / failing chip.
540000-543999	Per-chip temperature protected (slot/chip encoded).	Improve cooling / thermal contact for that board.
8000	WhatsMinerTool version is too low.	Download the latest WhatsMinerTool.
8410	Firmware / hardware generation mismatch (e.g. M2x firmware on an M3x).	Flash the correct firmware for the miner's actual generation and model.
9999	Unknown error.	Reboot and re-check; escalate if it persists.
100000-100003	Security-module / signature error.	Re-flash official Whatsminer firmware; do not run modified images.
100100	Security: btminer was removed.	Re-flash official firmware.
110000	Security: illegal file.	Re-flash official firmware.
110001	Security: a virus was identified and removed.	Re-flash official firmware; only run official images.

Avalon

Canaan Avalon - codes & indicators

Code	Meaning	Suggested checks
LED green	Healthy / hashing normally	Nothing.
LED red	One of 7 fault classes - pull estats	Read estats (SYSTEMSTATU->ECMM->ECHU->PS->PVT) to classify.
BOOTBY 0x02	Rebooted by overheat	Clean/airflow, check PVT_T, verify ambient.
BOOTBY 0x03	Pool / DNS reboot	Switch pool, set DNS 1.1.1.1 / 8.8.8.8.
BOOTBY 0x11	No hashrate within 5 min	Reseat ribbons, slot-swap the board.
BOOTBY 0x12	Hashrate < 70% of nameplate	Check PVT/chips (TA vs nameplate), throttle.
ECHU[N 0 0]	Fault isolated to ONE board	Reseat ribbon + DC lug, slot-swap; follows board = board fault.
ECHU[N N N]	Controller / PSU / mains-environment fault	Check AUC/MM, PSU (PS bitmap), and input voltage.
PS bit 1 (Input_UV)	PSU input under-voltage	Raise/steady mains ≥195-200 V.
PS bit 64 (OC_out)	Output over-current - hashboard short	Output over-current can indicate a board or power-path fault; it does not prove a shorted board. Authorized technicians may isolate it using the model-specific service procedure. Never disconnect live: isolate all supplies, control stored energy and verify the safe state before each connection change; use a controlled return to service and re-isolate before any further change.
Toohot (PVT_T > 85 °C)	Chip over-temp	Clean, improve airflow, check pads/ambient.
No fan (RPM 0)	Fan not spinning	Replace the fan (or PSU fan).

Avalon

Reboot-cause (BOOTBY) & PSU error codes

Code	Meaning	Suggested checks
BOOTBY 0x01 (AM_BOOTBY_POWRON)	Hard restart or unknown-cause restart; this is also the normal code after a real power-cycle.	Expected if you just cut power. If it recurs on its own, chase a brownout: check the mains feed, breaker, and PSU for sags.
BOOTBY 0x04 (AM_BOOTBY_WEB)	Reboot triggered from the web dashboard / control-board backend.	Operator/UI-initiated. No action unless nobody restarted it; then check who has dashboard access.
BOOTBY 0x05 (AM_BOOTBY_API)	Reboot issued over the API (port 4028 / management tool).	Expected if your fleet tool or script sent a restart. If unexpected, audit what is hitting the API.
BOOTBY 0x21 (AM_BOOTBY_SOFTON)	Soft restart initiated by firmware (e.g. after a config or pool change).	Normal, no action.
BOOTBY 0x10	Watchdog-class reboot, in the field almost always overheat/hang related. Seen in real A1166/A1246 logs (e.g. BOOTBY[0x10.xxxxxxxx]) but not listed in Canaan's official 8-code table.	Treat as overheat/lockup: check PVT_T and that all fans spin, clean filters/refresh thermal pads, refresh firmware, and load-test the PSU.
PS error 2 / 4 / 8 (OT1 / OT2 / OT3)	PSU over-temperature, reported in three escalating stages (OT3 = shutdown imminent).	Improve airflow, drop ambient, and clean the PSU intake. On OT3 shut down and let it cool before restart; check the PSU fan.
PS error 16 (OC_Pri)	PSU input / primary-side over-current.	Record the fault and operating conditions. Qualified, authorized electrical personnel must assess the supply against the exact model/PSU specifications and site design, using the applicable test procedure. Do not probe, adjust the supply or substitute a higher-rated PSU as a learner action. Use their findings for further equipment diagnosis.
PS error 32 (UV_out)	PSU output (DC rail) under-voltage.	PSU sagging under load or load too high. Load-test the PSU; replace it if it cannot hold the rail.
PS error 128 (CS_error)	PSU current-sensor fault.	Internal PSU fault, not field-serviceable. Service or replace the PSU.
PS error 256 / 512 / 1024 (OC_IOSA / OC_IOSB / OC_IOSC)	Over-current on PSU output channel A / B / C.	A shorted or failing board is one possibility. Only authorized personnel may perform equipment-specific isolation/substitution: isolate every source, control stored energy and verify safe conditions before each connection change. Never disconnect live board power; use controlled return to service and re-isolate before further changes.
PS error 2048 (FAN_error)	PSU's internal fan has failed (distinct from the chassis/hashboard fans).	Replace the PSU fan (or the PSU). Do not run under load with a dead PSU fan; overheat/OT faults will follow.
WORKMODE[0] / WORKMODE[1]	Performance profile, not a fault: 0 = normal mode, 1 = high-performance mode.	Use it to confirm which profile is running when power draw or hashrate looks off vs. nameplate.
SYSTEMSTATU [Work ... Hash Board: N]	Runtime state plus the count of hashboards that enumerated. N below the model's board count (usually 3) means a board didn't come up.	If the board count is low, reseat that board's ribbon and power, then slot-swap to see if the fault follows the board.

SEALMINER

SEALMINER A2 fault codes (official manual)

Code	Meaning	Suggested checks
1	Control board initialize fail (firmware/model mismatch at boot)	Confirm the firmware matches this exact model; reflash the correct firmware
2	Control board does not support AsicBoost	Update to current firmware
3	Control board SN (serial) error	Contact Bitdeer after-sales (control board RMA)
4	Control board MAC address error	Contact Bitdeer after-sales
100-105	Fan 1-6 detect error (one code per fan position)	Check the fan cable/connector; if it stays dead, swap the fan
120 / 121	Air inlet (120) / outlet (121) fan speed too high	Check ambient/intake temp and airflow - fans are maxing out
125 / 126	Inlet (125) / outlet (126) fan pair RPM differ by more than 2000	One fan is lagging - check its connection or replace it
180	OLED initialize fail	Reseat the OLED ribbon; if still failed, replace the OLED
200-202	Hashboard 1-3 PCB temp sensor detect fail	Check/reseat that hashboard's signal cable
220-222	Hashboard 1-3 temp sensor communication error	Check/reseat the hashboard cable
240-242	Hashboard 1-3 PCB temperature too high	Check ambient temp and airflow
270-272	Hashboard 1-3 chip column count error	Contact after-sales (board RMA)
280-282	Hashboard 1-3 chip row count error	Contact after-sales
290-292	Hashboard 1-3 SN (serial) error	Contact after-sales
300-302	Hashboard 1-3 EEPROM communication error	Check/reseat the hashboard cable
310-312	Hashboard 1-3 Bin version parse error	Contact after-sales
320-322	Hashboard 1-3 Bin number parse error	Contact after-sales
330-336	Bin/board mismatch set: 330 Bin version mismatch, 331 Bin number mismatch, 332 Bin file missing, 333 Bin file parse error, 334 board column mismatch, 335 board row mismatch, 336 Bin number not tested	Usually a wrong/corrupt Bin - contact after-sales
400-402	Hashboard 1-3 clock (CLK) detect error	Contact after-sales
410-412	Hashboard 1-3 reset detect error	Contact after-sales
420-422	Hashboard 1-3 not detected / not inserted	Reseat the hashboard signal cable
430-432	Hashboard 1-3 communication test error	Power-cycle; if it stays, swap the board to another slot
440-442	Hashboard 1-3 initialize fail	Power-cycle; if it stays, swap the board slot
450-452	Hashboard 1-3 too many bad chips	Contact after-sales (board repair)
460-462	Hashboard 1-3 frequency configure fail	Power-cycle; if it stays, swap the board slot
470-472	Hashboard 1-3 low hashrate	Power-cycle; if it stays, try a different PSU
480-482	Hashboard 1-3 communication error (runtime)	Power-cycle; if it stays, swap the board slot
600	Boot-up ambient temperature too high	Cool the room/intake before starting
601	Boot-up time too long	Power-cycle; if it recurs, upgrade to the latest firmware
602	Miner throttling (reduced frequency) due to over-temperature	Check ambient temp and airflow
603	Miner throttling (reduced frequency) due to overload	Check ambient temp; verify PSU/load headroom
604	Miner over-temperature shutdown	Check ambient temp/airflow and clear any blockage before restart
700	Pool connection failed or disconnected	Check the network and pool configuration
701	Download Bin file failed	Check the network/internet connection
702	Pool does not support AsicBoost	Switch to an AsicBoost-capable pool
800	PSU detect fail	Check the PSU signal cable; if seated, replace the PSU
801	PSU communication failure	Check the PSU signal cable; replace the PSU
802	PSU voltage - no output	Check the PSU cable; replace the PSU
803	PSU overload	Check ambient temp; if it persists, replace the PSU
804	PSU error/fault detected	Check ambient temp; replace the PSU
805	PSU power-down fail	Check the PSU cable; replace the PSU
806	PSU set-voltage fail	Check the PSU cable; replace the PSU

Auradine

Teraflux status codes (API / FluxVision)

Code	Meaning	Suggested checks
LED status code 1 (NO_POWER)	No power detected to the miner/board.	Record the fault and operating conditions. Qualified, authorized electrical personnel must assess the supply against the exact model/PSU specifications and site design, using the applicable test procedure. Do not probe, adjust the supply or substitute a higher-rated PSU as a learner action. Use their findings for further equipment diagnosis.
LED status code 2 (NORMAL)	Miner is healthy and hashing normally.	No action.
LED status code 3 (LOCATE_MINER)	Identify/locate mode active - someone triggered Locate in FluxVision so the LED signals which unit it is.	Not a fault; clear Locate in FluxVision once you've found the machine.
LED status code 4 (TEMPERATURE)	Over-temperature condition; miner may throttle or shut down until it cools.	Check inlet/ambient temp and airflow, clean filters and heatsinks, verify all fans spin; improve cooling before resuming.
LED status code 5 (POOL_CONFIG)	Pool/stratum is misconfigured or no valid pool is set.	Verify stratum URL, worker, and password in FluxVision (/pools); fix and re-apply.
LED status code 6 (NETWORK)	Network/connectivity problem - miner can't reach pool or FluxVision.	Check Ethernet cable, switch port, and IP/DHCP; confirm the miner can route to the pool and management server.
LED status code 7 (CONTROL_BOARD)	Control-board fault.	Reboot; if it persists, reseat control-board connectors and re-flash or swap the control board.
LED status code 8 (HASH_RATE_LOW)	Hashrate is below expected.	Check for dead chips/domains, temperature throttling, and pool rejects; inspect hashboards and let the miner retune.
LED status code 9 (FAN_ISSUE)	Fan fault - stopped, under-speed, or unplugged.	Read fan RPM via the API, reseat the fan connector, clear obstructions, replace the failed fan.
LED status code 10 (HASHBOARD_ISSUE)	Hashboard fault - missing chips or a dropped voltage domain.	Reseat hashboard power/ribbon/data; if a board reports fewer chips than expected, service or swap that board.
LED status code 11 (PSU_ISSUE)	Power-supply fault.	Record the fault and operating conditions. Qualified, authorized electrical personnel must assess the supply against the exact model/PSU specifications and site design, using the applicable test procedure. Do not probe, adjust the supply or substitute a higher-rated PSU as a learner action. Use their findings for further equipment diagnosis.
LED status code 12 (TUNING)	Miner is auto-tuning/optimizing performance.	Transient - let it finish; hashrate settles after tuning.
LED status code 13 (STANDBY)	Miner is in standby/sleep mode (not hashing by design).	Take it out of standby (mode/sleep) to resume hashing.
LED status code 14 (RESETTING)	Miner is resetting/rebooting.	Transient - wait for it to come back up.
LED status code 15 (WARMING)	Warm-up phase right after start.	Transient - hashrate ramps as it warms; no action.
LED status code 16 (UPGRADING)	Firmware upgrade in progress.	Do NOT power off until it completes.
LED status code 19 (LOW_COOLANT)	Low coolant level (dual-phase immersion units only).	Check coolant level and the low-coolant sensor before resuming.
PSU status register non-0x00 (VoutStatus/IoutStatus/InputStatus/TemperatureStatus/FanStatus)	GET /psu returns these PMBus status bytes; 0x00 = healthy. A non-zero value flags a fault in that PSU domain - output voltage, output/over-current, AC input, PSU temperature, or PSU fan respectively.	Record the fault and operating conditions. Qualified, authorized electrical personnel must assess the supply against the exact model/PSU specifications and site design, using the applicable test procedure. Do not probe, adjust the supply or substitute a higher-rated PSU as a learner action. Use their findings for further equipment diagnosis.
Pool Status: Dead	Configured pool is unreachable / no connection.	Check network path, stratum URL and port, and firewall; confirm the pool host resolves and responds.
Pool Status: Rejecting	Pool is connected but rejecting submitted shares.	Verify worker/username and password, pool difficulty, and clock/time sync; check for hardware errors on the boards.

Delta VFD

Delta MS300 VFD fault codes (immersion / hydro pump & fan drives)

Code	Meaning	Suggested checks
ocA / ocd / ocn	Over-current during acceleration / deceleration / constant speed.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Check the motor/pump for a jam or short and the drive-to-motor wiring; lengthen the accel/decel ramp; verify the drive is sized for the load.
ocS	Over-current at stop.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Check the output wiring/motor for a short to ground; inspect the IGBT/drive if wiring is clean.
ovA / ovd / ovn / ovS	Over-voltage during acceleration / deceleration / constant speed / at stop.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: The DC bus is too high — assess deceleration settings and approved braking provisions; check incoming line voltage isn't high.
LvA / Lvd / Lvn / LvS	Low voltage during acceleration / deceleration / constant speed / at stop.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Check incoming supply voltage and connections; a sag or lost phase on the input starves the bus.
OrP	Input phase-loss protection.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Check all three incoming supply phases and the input fuses/breaker.
oPL1 / oPL2 / oPL3	Output phase loss (U / V / W).	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Check the drive-to-motor leads and terminals for that phase; check the motor winding.
GFF	Ground fault on the output.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Assess possible motor/cable insulation faults using the manufacturer procedure; this learner reference does not authorize insulation testing.
oH1 / oH2 / oH3	IGBT / heatsink / motor-PTC over-heat.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Check the drive's cooling fan and airflow, clear obstructions, and lower ambient; check the motor thermistor.
oL / oL3	Drive overload (also low-frequency overload).	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: The load exceeds the drive rating — check for a binding pump, reduce load, or verify drive sizing.
EoL1 / EoL2 / EoL3 / EoL4	Electronic thermal-relay motor overload.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Motor is running hot/overloaded — check the pump for binding and the thermal-relay settings.
ot1 / ot2 / ot3 / ot4	Over-torque detected.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Check the driven load (pump) for mechanical binding; review the torque-limit settings.
uC	Low current.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Load is far below expected — check for a decoupled pump, a broken coupling, or a lost output phase.
EF / EF1	External fault / emergency stop input.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: An external contact tripped the drive — check the E-stop, interlocks, and the external-fault wiring.
bb	External base block.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: The base-block input is active — check that interlock/enable signal before the drive will run.
CE1 / CE2 / CE3 / CE4 / CE10	Modbus / serial communication error or time-out.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Check the RS-485 wiring, termination, baud/parity settings, and the controller polling the drive.
Sto / STL1 / STL2 / STL3	Safe-Torque-Off active / safety-loop error.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Check the STO/safety-loop wiring and jumpers; the drive won't run until the safety loop is made.
AUE / AUE1 / AUE2 / AUE3	Auto-tuning error.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Re-run motor auto-tune with correct nameplate data and the motor connected/uncoupled as the manual specifies.
cF2	Memory read-out error.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Parameter memory fault — reload the parameter set; if it recurs, the drive needs service.
Pcod	Password error.	Record the code and operating conditions; refer to qualified, authorized drive personnel under the exact equipment procedure. Intrusive inspection requires all-source isolation, stored-energy control and verification; no trial resets. Specialist assessment: Enter the correct drive password (parameter 00-07/00-08) to unlock parameters.

Status-light guide

What the lights on the machine mean — for reading a unit before it hands you a code. Patterns can vary by model and generation; when in doubt, the numeric code is authoritative.

Antminer

Status lights

Indicator	Means	What to do
Green LED flashing, red LED off (during run)	Normal operation - the miner is hashing and reporting to the pool.	None. This is the healthy state.
Green LED solid / constantly on	Network fault - the miner failed to get an IP / has no network. It is NOT mining. (Note: solid green is a fault, flashing green is healthy - the reverse of some third-party charts.)	Check the Ethernet cable, switch port, and DHCP; confirm the miner pulls an IP. Assign a static IP if DHCP is unavailable.
Red LED flashing, green off (during run)	High-temperature alarm, or the miner was shut down by the pool/network.	Check inlet temp and airflow/fans first; if temps are fine, check pool config and the network for a drop or kick.
Both LEDs on together, steady, at power-up	The miner is initializing / booting.	Normal - wait 2-5 minutes. Green should start flashing once it is hashing.
Both LEDs off	No status - typically a dead cooling fan tripping shutdown, or a faulty/unpowered control board.	Confirm PSU output and control-board power; check the fans. If the board is powered but dark, the control board is bad.
Red LED flashing, green LED off (won't mine)	IP conflict - another device on the network has the same IP.	Give the miner a unique IP (fix the duplicate address or DHCP reservation).
Ethernet port lights both off	No network link - cable unplugged, dead switch port, or a bad control-board NIC. (Normal link = yellow solid + green flashing.)	Reseat/replace the patch cable, try another switch port; if the port stays dark, suspect the control board.

Whatsminer

Status lights

Indicator	Means	What to do
Green LED flickering (red LED may flicker faintly alongside it)	Normal - miner is booted and hashing. A flickering red LED next to the green is normal activity, NOT a fault.	None. Leave it running.
Green LED solid ON and Red LED solid ON (both steady, not flickering)	Miner is starting up / booting (firmware boot, hashboard enumeration and frequency ramp take ~2-5 min).	Wait 2-5 minutes for boot to finish. If it never leaves this state, power-cycle, then pull the log if it sticks again.
Green heartbeat flicker + red blinking at a ~1-second beat	Hashboard fault — a board is missing or not detected. The green LED keeps its fast heartbeat flicker; only the red carries the 1-second fault code.	Read the error code (e.g. 530/531/532). Reseat the ribbon cable and tighten the copper-bar screws; if a slot stays dead, swap the hashboard.
Green heartbeat flicker + red blinking at a ~2-second beat	Fan or program fault — a fan is dead/unplugged, or the mining program isn't running. The red carries the 2-second code; the green keeps flickering.	Check fan connectors and blades; replace the dead fan. If the program is hung, power-cycle and re-check.
Green LED flickering with Red LED solid ON	'Other' fault - pool/network disconnect, temperature-sensor fault, or overheating.	Read the error code; check pool/network settings, ambient temperature, and the temp sensors. Clear dust if it's a heat issue.
Red LED flashing during a microSD firmware flash, then Green LED goes solid when done	Firmware is being burned from the SD card; solid green means the burn finished.	Normal during an SD-card flash - wait for solid green before removing the card or power-cycling.

Avalon

Status lights

Indicator	Means	What to do
Status LED solid yellow / amber	System initializing: booting, enumerating hashboards, spinning up fans and PSU. Should turn green within about 5 minutes.	Normal at startup. If it stays yellow past ~5 min, a board/PSU/fan didn't come up; pull estats and check the SYSTEMSTATU board count.
Status LED solid white	Voltage is present and the control board is in early power-on / fan self-check, before mining starts.	Momentary at boot. If it stays white it never handed off to mining; power-cycle and verify the fans spin and the PSU has output.
Power-supply (PMU) board LED red or off	PSU output is abnormal, the PMU board has a fault, or the power connector is loose (green on this LED = normal output).	Reseat both power connectors, confirm the AC feed, then load-test or replace the PSU.
AUC / AUC3 controller LED green with a brief red flash about every 15 seconds	AUC controller is healthy and passing IIC traffic to the boards normally.	Normal. The periodic red blink is not a fault.
AUC / AUC3 controller LED solid red, off, or stuck on blue	AUC control-board fault or IIC/USB communication failure.	Reseat the AUC USB and IIC ribbon. If it stays red while the chassis LED is green, suspect the cable/IIC; otherwise replace the AUC.
Raspberry Pi controller red LED on with no green (split-controller models: 721/821/841/1047/1066)	The microSD/TF card is missing or corrupt.	Reseat or replace the TF card and reflash the controller firmware.

SEALMINER

Status lights

Indicator	Means	What to do
All control-board panel indicator lights OFF after power-on	Control board is getting no power	Check/reseat the power cable connections to the control board and PSU; confirm the PSU has output
Right-side control-board indicator light ON, but Ethernet port light off / green not flashing	Board has power but no network link	Check the switch, network cable, and cable quality; confirm the port shows link
Ethernet port green LED flashing	Normal - network link is up and passing traffic	None; if it stops flashing, check the switch/cable

Auradine

Status lights

Indicator	Means	What to do
Both status LEDs solid GREEN	Normal operation - miner is powered, healthy, and hashing (status code NORMAL).	None.
LED OFF / dark	No power to that indicator - unit or board is not powered (NO_POWER).	Record the fault and operating conditions. Qualified, authorized electrical personnel must assess the supply against the exact model/PSU specifications and site design, using the applicable test procedure. Do not probe, adjust the supply or substitute a higher-rated PSU as a learner action. Use their findings for further equipment diagnosis.
RED (solid or flashing)	A fault condition is flagged - over-temp, control board, hashboard, PSU, fan, or low-hashrate.	Query GET /led or check FluxVision to see which condition code is set, then service that subsystem.
YELLOW (solid or flashing)	Attention / transitional state - tuning, warming, standby, locate, or a low-severity warning.	Usually self-clears; if it persists, check the flagged condition in FluxVision.
Flashing LED (any color)	Locate/identify mode, or a transient state such as resetting, warming, tuning, or firmware upgrade.	If you triggered Locate in FluxVision this is expected; otherwise wait for the transient state to finish before servicing.