Comprehensive reference for all Whatsminer fault codes including hardware faults (1xx), temperature faults (2xx), power faults (3xx), and network faults (4xx). Includes causes, fixes, and diagnostic procedures for M30S, M50, M56S, M60 series.
Whatsminer ASIC miners use a numeric fault code system to report errors. Unlike Antminer's text-based error messages, Whatsminer codes follow a structured numbering scheme where the first digit indicates the error category:
1xx — Hardware faults (hashboard, chips, EEPROM)2xx — Temperature faults (overheating, sensor failures)3xx — Power faults (PSU, voltage, current)4xx — Network and communication faults5xx — Firmware and system faults6xx — Security and configuration faults
This guide covers every documented Whatsminer fault code with causes, diagnostics, and fixes. It applies to all Whatsminer models including M30S series, M50 series, M56S, and M60 series.
WhatsMiner Tool Web UI SSH (btminerlog)
The WhatsMiner Tool (Windows application) is the primary diagnostic interface:
Download WhatsMiner Tool from the official MicroBT website
Open the application and scan your network for miners
Select the miner showing errors
Click "Log" to view error history
The fault code appears in the "Status" column
The WhatsMiner Tool also allows batch management and firmware updates across multiple miners.
Navigate to the miner's IP address in a web browser
Log in (default credentials vary by firmware version — commonly admin / admin)
Navigate to "Status" or "Hash Board Status"
Active fault codes appear in the status display
Check "Log" page for historical errors
# Connect via SSH ssh root@ < miner-i p > # View the main miner log cat /tmp/btminerlog # Filter for fault codes grep -i "fault\|error\|code" /tmp/btminerlog # View real-time log tail -f /tmp/btminerlog # Check system log cat /var/log/messages | tail -100 # Check hashboard status cat /tmp/hashboard_status 2> /dev/null Whatsminer miners use LED patterns to indicate operational status:
LED State Meaning Action Solid Green Normal operation, mining actively No action needed Blinking Green Booting or initializing Wait 5–8 minutes Solid Red Critical fault — mining stopped Read fault code from web UI or WhatsMiner Tool Blinking Red Warning-level fault Check status; miner may still be mining at reduced capacity No LED No power to control board Check PSU, power cable, inlet fuse Alternating Red/Green Firmware flashing in progress Do NOT power off Rapid Blink (any color) Network/IP error or boot failure Check network; may need firmware recovery
Code 110 Severity Critical Meaning A hashboard has a general hardware fault and cannot operate Common Causes Board not detected, power delivery failure on the board, major component failure Diagnostics Check which board slot reports the error. Reseat connectors. Swap the board to a different slot to isolate board vs. slot. Fix If the error follows the board, inspect for burnt components, check for shorts on the power input, and verify EEPROM readability. If the error stays on the slot, check the control board port and cable. Related Guide Hashboard Not Detected
Code 111 Severity High Meaning One or more ASIC chips on a hashboard failed their self-test or are not responding Common Causes Failed ASIC chip, broken signal trace, voltage domain failure affecting a group of chips Diagnostics Check the hashboard status page for chip count — compare to expected count for your model. Identify which chips are missing. Fix If a small number of chips are missing (1–5), the board may continue mining at reduced hashrate. For repair, locate the failed chip position and replace it. Related Guide Missing Chips Troubleshooting
Code 112 Severity High Meaning Chips are detected but not responding to work assignments within the expected time Common Causes Chip frequency set too high (unstable), voltage too low for frequency, degraded chip, signal integrity issue Diagnostics Check if the error is consistent or intermittent. Check chip temperature — overheating can cause response delays. Fix Reduce operating frequency. If on custom settings, revert to factory defaults. If persistent at stock frequency, the chip may need replacement.
Code 113 Severity Warning Meaning A hashboard is producing significantly less hashrate than expected Common Causes Missing chips, thermal throttling, frequency not reaching target, voltage domain underperforming Diagnostics Compare per-board hashrate. Check chip count, temperatures, and frequency settings. Fix Address the root cause — see Low Hashrate Troubleshooting .
Code 114 Severity High Meaning One or more chips failed the hardware hash verification test during startup Common Causes Damaged chip producing incorrect hash results, voltage instability during test Diagnostics Note which board and which chip position failed. Check voltage domain for that chip group. Fix If voltage is correct, the chip is producing wrong results and needs replacement.
Code 120 Severity High Meaning The control board cannot establish stable communication with a hashboard Common Causes Loose data connector, damaged communication cable, control board port failure, signal integrity issue Diagnostics Reseat connectors. Swap boards between slots. Try a new cable. Fix If the error follows the cable, replace it. If it follows the board, check the signal path from the connector to the first chip. If it stays on the slot, the control board port is faulty.
Code 130 Severity Critical Meaning The EEPROM on a hashboard cannot be read or contains invalid data Common Causes EEPROM chip failure, I2C bus fault, data corruption, connector issue affecting I2C lines Diagnostics Try reseating the connector (I2C lines pass through it). Check if the EEPROM can be read with an external I2C tool. Fix Replace and reprogram the EEPROM if the chip has failed. If the data is corrupt but the chip is functional, reprogram with correct data. Related Guide EEPROM Chips
Code 131 Severity High Meaning EEPROM data does not match the expected format or model identifier Common Causes Board was in a different miner model, EEPROM partially overwritten, wrong firmware for board revision Diagnostics Read the EEPROM contents and compare to a known-good dump for your model. Fix Reprogram EEPROM with correct model data. Ensure firmware matches the hardware revision.
Code 140 Severity Critical Meaning The hashboard management/security chip is not responding Common Causes Management chip failure, I2C bus fault, power issue on the management chip rail Diagnostics Check for voltage on the management chip power pins. Verify I2C bus continuity. Fix Replace the management chip if confirmed failed. Requires model-specific replacement component.
Code 150 Severity Warning Meaning The target operating frequency could not be set on one or more chips Common Causes Frequency exceeds chip capability at current voltage, PLL lock failure, chip degradation Diagnostics Check if the error occurs on specific chips or all chips. Review frequency and voltage settings. Fix Reduce frequency to stock value. If stock frequency fails, the chip's PLL may be damaged.
Code 200 Severity Critical (causes shutdown) Meaning Chip or board temperature has exceeded the maximum safe threshold Common Causes Insufficient cooling, dust-clogged heatsinks, failed fans, degraded thermal paste, high ambient temperature, overclocking Diagnostics Check temperatures immediately after restart before they climb again. Check fan operation, heatsink cleanliness, and ambient conditions. Fix Address cooling issue — clean heatsinks, replace failed fans, reapply thermal paste, improve ventilation. Related Guide High Temperature Troubleshooting
Code 201 Severity High Meaning A temperature sensor returned an invalid reading or did not respond Common Causes Failed sensor IC, broken I2C trace to sensor, sensor desoldered, connector issue Diagnostics Check which board reports the error. If other sensors on the same board read normally, the specific sensor IC has failed. Fix Replace the failed temperature sensor IC. Common sensor types: LM75, TMP451, NCT218.
Code 202 Severity Warning Meaning The temperature difference between the inlet and outlet (or between boards) exceeds the expected range Common Causes Uneven airflow, one board's heatsinks are more clogged than others, fan partial failure, uneven thermal paste application Diagnostics Compare temperatures across all boards and sensors. Identify which area is abnormally hot or cold. Fix Clean heatsinks on the hotter board. Ensure fans are all running at similar speeds. Check for airflow obstructions on one side of the miner.
Code 210 Severity Warning Meaning The inlet (ambient) temperature sensor reads above the recommended operating range (typically 40°C+) Common Causes Hot environment, recirculating exhaust air, nearby heat source Diagnostics Measure ambient temperature with an independent thermometer. Check for hot air recirculation. Fix Improve facility ventilation. Add intake cooling if operating in a hot climate. Separate miners to prevent exhaust recirculation.
Code 211 Severity Warning Meaning The inlet temperature is below the minimum operating threshold (typically below 0°C or 5°C) Common Causes Cold weather operation without preheating, outdoor installation in winter Diagnostics Verify ambient temperature. Cold air can cause condensation inside the miner which leads to short circuits. Fix Preheat the environment or use intake air heating. Never start a miner that has been below freezing without allowing it to reach room temperature first (condensation risk).
Code 220 Severity Critical (immediate shutdown) Meaning Temperature is rising uncontrollably despite throttling — a dangerous condition Common Causes Complete fan failure while under load, heatsink detached from chips, catastrophic thermal paste failure Diagnostics After shutdown, inspect all fans and heatsink attachments before restarting. Fix Resolve the cooling failure completely before powering on again. This code indicates a near-dangerous thermal event.
Fault code 220 is serious. If you see this code, do not restart the miner until you have identified and fixed the cooling failure. Thermal runaway can damage chips permanently and, in extreme cases, pose a fire risk.
Code 231 Severity High Meaning A fan is not reaching expected RPM or is not detected Common Causes Fan motor failure, loose fan connector, blocked fan, bearing worn out Diagnostics Visually verify all fans are spinning. Check fan connectors. Try swapping fans between positions. Fix Replace the failed fan. Use OEM or compatible replacements with matching RPM, CFM, and connector specifications. Related Guide Fan Error Troubleshooting
Code 232 Severity Warning Meaning A fan is running but at an unexpected speed (too slow or reporting unrealistic RPM) Common Causes Aging fan motor losing speed, incorrect replacement fan model, tachometer signal noise Diagnostics Compare RPM readings across all fans. A fan reading significantly different from others is suspect. Fix Replace the fan if RPM is consistently low. Check the fan connector for secure contact if RPM reading is erratic.
Code 301 Severity Critical Meaning The PSU has reported a fault or the miner detected a power delivery anomaly Common Causes PSU overcurrent protection tripped, PSU overtemperature, PSU internal failure, input voltage out of range Diagnostics Measure PSU output voltage. Check PSU input voltage. Listen for clicking (OCP tripping). Check PSU temperature. Fix Test with a known-good PSU. If the error persists with a good PSU, a hashboard may be causing overcurrent. Test with boards removed one at a time. Related Guide Power Issues Troubleshooting
Code 302 Severity High Meaning A voltage domain on a hashboard is reading outside the acceptable range Common Causes Failed voltage regulator, shorted ASIC chip, damaged power trace, PSU voltage droop Diagnostics Identify which board reports the error. Measure voltage domains with a multimeter. Fix See Abnormal Chip Voltage for detailed diagnostic and repair procedures.
Code 303 Severity Critical Meaning A voltage regulator on the hashboard has failed — specific to the regulator circuit rather than a general voltage reading Common Causes Regulator IC failure, input/output capacitor failure, inductor fault, thermal damage Diagnostics Locate the failed regulator — check for physical damage, measure input and output voltages. Fix Replace the voltage regulator IC and verify all surrounding passive components (capacitors, inductor, feedback resistors).
Code 310 Severity Critical Meaning Current draw exceeds the safe maximum — may indicate a short circuit Common Causes Shorted ASIC chip, shorted capacitor, damaged power trace causing arc, PSU delivering excessive voltage Diagnostics Remove hashboards one at a time to identify which board is drawing excessive current. Measure resistance across board power input. Fix Find and repair the short circuit on the offending board.
Code 320 Severity Warning Meaning The calculated J/TH (joules per terahash) is outside the expected range Common Causes PSU efficiency degradation, voltage regulator inefficiency, chips running at non-optimal voltage/frequency point Diagnostics Compare reported power consumption to actual wall power. Check PSU efficiency at current load level. Fix Usually informational. If PSU is old, consider replacement. Verify voltage settings are at optimal levels.
Code 350 Severity Critical Meaning General power delivery failure — the hashboard cannot establish proper power delivery Common Causes Power connector issue, blown input fuse or trace, bulk capacitor failure, multiple voltage domains failed Diagnostics Check power connector. Measure input voltage at the board. Check for burnt components near the power input. Fix Inspect and repair the power delivery path from the connector through the input filtering to the voltage regulators.
Code 351 Severity High Meaning The input voltage to the hashboard (from the PSU) is below the minimum threshold Common Causes PSU droop under load, long or thin power cables, corroded connector, PSU capacitor degradation Diagnostics Measure PSU output voltage at the connector under full load. Fix Replace PSU if output is low. Replace power cables if they are long or thin gauge. Clean connectors.
Code 352 Severity High Meaning Input voltage exceeds the maximum rating for the hashboard Common Causes PSU overvoltage, wrong PSU model for the miner, PSU voltage regulation failure Diagnostics Measure PSU output voltage immediately. Fix Shut down immediately if voltage is significantly above spec. Replace the PSU.
Code 400 Severity Warning Meaning General network connectivity error Common Causes Ethernet cable disconnected or damaged, switch/router port failure, DHCP failure Diagnostics Check Ethernet cable and link LED on the miner. Ping the miner from another device. Check DHCP lease. Fix Replace Ethernet cable. Verify switch/router port. Assign static IP if DHCP is unreliable. Related Guide Network Problems Troubleshooting
Code 401 Severity Warning Meaning The miner cannot connect to any configured mining pool Common Causes Incorrect pool URL or port, pool server down, DNS failure, firewall blocking, ISP blocking mining traffic Diagnostics Verify pool URL and port are correct. Try a different pool. Test DNS resolution: nslookup <pool-hostname> from the miner. Fix Correct pool settings. Try using the pool's IP address instead of hostname. Ensure firewall allows outbound connections on the stratum port (typically 3333, 25, or 443).
Code 402 Severity Warning Meaning The miner cannot resolve DNS hostnames Common Causes DNS server unreachable, incorrect DNS configuration, ISP DNS issues Diagnostics Check DNS settings on the miner. Try pinging a known IP address (8.8.8.8) to verify basic connectivity vs. DNS-specific failure. Fix Configure public DNS servers (8.8.8.8, 1.1.1.1). Or use pool IP addresses directly.
Code 410 Severity Warning Meaning The miner connected to the pool but received an unexpected response — protocol mismatch Common Causes Wrong port (connecting Stratum V1 to V2 port or vice versa), pool proxy misconfigured, incorrect authentication Diagnostics Verify the stratum port matches the protocol version your miner supports. Check worker name and password format. Fix Use the correct port for your stratum version. Verify worker name format matches pool requirements.
Code 420 Severity Warning Meaning Latency to the mining pool exceeds the acceptable threshold, causing stale shares Common Causes Geographically distant pool server, congested network, bad routing, ISP throttling Diagnostics Ping the pool server from the miner to measure latency. Compare with connecting to a pool server in a closer region. Fix Use a pool server in a closer geographic region. If latency is high to all destinations, check local network infrastructure.
Code 430 Severity Low Meaning The management API received an invalid request or authentication failure Common Causes Incorrect API credentials, WhatsMiner Tool version mismatch, unauthorized access attempt Diagnostics Verify API credentials. Update WhatsMiner Tool to the latest version. Fix Update management tools. Reset API password if needed.
Code 500 Severity Critical Meaning General firmware error — the mining software has encountered a fatal condition Common Causes Firmware corruption, incompatible firmware version, flash storage failure Diagnostics Check if the error appeared after a firmware update. Try reflashing firmware. Fix Reflash with a known-good firmware version for your exact model. Use USB recovery if the web UI is inaccessible.
Code 501 Severity High Meaning The system watchdog timer triggered a reset because the firmware became unresponsive Common Causes Firmware bug, memory leak, hardware issue causing software hang Diagnostics Check how frequently the watchdog triggers. If consistent timing, likely a firmware bug. If random, may be hardware. Fix Try a different firmware version. If persistent across versions, suspect hardware. Related Guide Frequent Restarts
Code 510 Severity High Meaning The control board's flash storage has errors Common Causes Flash wear-out, power loss during write, manufacturing defect Diagnostics Check system log for NAND or flash errors. Reflash firmware to remap bad blocks. Fix Reflash firmware. If errors persist, the flash chip may need physical replacement.
Code 520 Severity Warning Meaning Miner configuration is invalid or corrupt Common Causes Power loss during config save, storage error, manual config file edit with syntax error Diagnostics Try factory reset to regenerate default configuration. Fix Factory reset and reconfigure pool URLs, worker name, and network settings.
Code 600 Severity Warning Meaning Login authentication failed — incorrect password or locked account Common Causes Forgotten password, brute-force lockout, firmware changed default credentials Diagnostics Try default credentials. Check if the account is locked due to too many failed attempts. Fix Factory reset to restore default credentials. Change password immediately after reset for security.
Code 610 Severity High Meaning The miner detected a potential security issue — unauthorized firmware modification or configuration change Common Causes Modified firmware, unauthorized API access, tampered configuration Diagnostics Review access logs. Verify firmware integrity. Fix Reflash official firmware. Change all passwords. Review network security (is the miner accessible from the internet?).
Code Name Severity Category First Action 110 Hashboard Error Critical Hardware Reseat connector, swap slots 111 Chip Error High Hardware Check chip count 112 Chip Response Timeout High Hardware Reduce frequency 113 Hashrate Abnormal Warning Hardware Check chip count, temps 114 Hash Test Failure High Hardware Check voltage domain 120 Communication Error High Hardware Reseat connector, try new cable 130 EEPROM Error Critical Hardware Reseat connector, reprogram 131 EEPROM Data Mismatch High Hardware Reprogram EEPROM 140 Management Chip Error Critical Hardware Check I2C bus, replace chip 150 Frequency Setting Error Warning Hardware Use stock frequency 200 Temperature Too High Critical Temperature Clean, check fans 201 Temperature Sensor Error High Temperature Replace sensor IC 202 Temp Differential High Warning Temperature Clean heatsinks 210 Environment Temp High Warning Temperature Improve ventilation 211 Environment Temp Low Warning Temperature Preheat environment 220 Thermal Runaway Critical Temperature Fix cooling, do NOT restart 231 Fan Error High Temperature Replace fan 232 Fan Speed Abnormal Warning Temperature Check fan, reseat connector 301 Power Supply Error Critical Power Test PSU output 302 Voltage Out of Range High Power Measure domain voltages 303 Voltage Regulator Failure Critical Power Replace regulator 310 Overcurrent Critical Power Find short circuit 320 Power Efficiency Abnormal Warning Power Check PSU age 350 Power Delivery Fault Critical Power Check connector, input path 351 Input Voltage Low High Power Check PSU under load 352 Input Voltage High High Power Shut down, check PSU 400 Network Error Warning Network Check cable 401 Pool Connection Failed Warning Network Verify pool URL 402 DNS Resolution Failure Warning Network Set public DNS 410 Stratum Protocol Error Warning Network Check port/protocol 420 Network Latency High Warning Network Use closer pool server 430 API Access Error Low Network Update tools 500 Firmware Error Critical System Reflash firmware 501 Watchdog Reset High System Try different firmware 510 Storage Error High System Reflash, may need chip 520 Configuration Error Warning System Factory reset 600 Authentication Error Warning Security Factory reset 610 Security Violation High Security Reflash official firmware
Whatsminer may report multiple fault codes simultaneously. When this happens, address them in the following priority order:
Power issues can cascade into other errors. A voltage problem can cause chip errors (111), temperature errors (200), and hashrate errors (113) all at once. Fix the power issue and the other codes may clear automatically.
If power is OK, address temperature faults next. Overheating causes chip errors and hashrate reduction. Fix cooling before investigating chip-level issues.
With power and temperature resolved, remaining hardware faults point to actual component failures that need repair.
Network and firmware issues do not damage hardware and can be addressed after hardware faults are resolved.
Fault code 220 (Thermal Runaway) : If you cannot identify the cooling failure, do not attempt to restart without professional inspectionFault code 303 (Voltage Regulator Failure) : Regulator replacement requires soldering skills and model-specific partsFault code 310 (Overcurrent) with no visible damage : The short may be internal to an ASIC chip, requiring thermal camera diagnosticsMultiple 1xx codes on the same board : Indicates a systemic board failure that may not be economically repairableFault code 510 persistent after reflash : The flash chip itself is failing and needs physical replacementAny fault code after a lightning strike or power surge : Multiple components may be damaged in ways that are not immediately obvious
Most fault codes clear automatically after a successful restart. If a code persists after the underlying issue is fixed, try a full power cycle (disconnect PSU from mains for 30 seconds) followed by restart. Some codes require a factory reset to clear the fault log.
The numbering scheme is consistent across models (1xx = hardware, 2xx = temperature, etc.), but some codes are model-specific. Newer models (M50/M60 series) may report additional codes not present on older models (M30S). The codes in this guide cover all currently documented fault codes.
Warning-level codes (113, 202, 210, 232, 320, 420) typically do not prevent mining but indicate a condition that will degrade performance or lead to a critical failure if not addressed. You can continue mining while planning maintenance, but do not ignore warnings indefinitely.
MicroBT publishes fault code documentation with each new model release. Check the MicroBT support portal, the documentation included with WhatsMiner Tool updates, and the user manual that ships with your miner.
Some firmware versions introduce new codes. Check the firmware release notes for your specific version. Contact MicroBT support with the exact fault code, model number, and firmware version for identification. You can also check community forums (BitcoinTalk, Reddit) where other operators may have encountered the same code.