Complete Whatsminer Error Code Reference: Every Alert Explained

How to Read This Guide

This is the definitive Whatsminer error code reference. Whether you are staring at a blinking status LED on your M30S at 3 AM or trying to decode a five-digit error code in WhatsMinerTool, this guide will tell you exactly what is happening, why, and what to do about it.

MicroBT’s Whatsminer error reporting system is fundamentally different from Bitmain’s Antminer approach. Where Antminers bury diagnostic data in kernel logs and require SSH parsing, Whatsminers use a structured numeric error code system — every fault condition is assigned a specific code that appears in the web interface, WhatsMinerTool, and API responses. This makes Whatsminer diagnostics more systematic, but the sheer number of codes (150+) can be overwhelming without a proper reference.

This guide is organized by error code category — fan errors, power supply errors, temperature sensor errors, hashboard/chip errors, network/pool errors, firmware/system errors, and PSU hex codes. Each error entry follows a consistent format:

Throughout the guide, error codes are displayed in monospace orange, healthy values in green, and critical values in red.

This guide covers all major Whatsminer models including the M20S, M21S, M30S, M30S+, M30S++, M31S, M31S+, M50, M50S, M53, M56S, M60, M60S, M63, and M66 series. Where a code behaves differently on newer-generation hardware, model-specific notes are called out.

How Whatsminer Error Reporting Works

Before diving into individual codes, it is important to understand how MicroBT structures error reporting — because it is fundamentally different from how Bitmain does it.

Whatsminer vs. Antminer: Two Different Philosophies

Bitmain’s Antminers report errors primarily through kernel log messages — plain-text strings like Chain[2] only has 54 chips or over max temp. Diagnosing an Antminer means SSH-ing into the machine and parsing log files. The error messages are descriptive but inconsistent across firmware versions, and there is no standardized numbering system.

MicroBT’s Whatsminers take a more structured, database-driven approach. Every error condition is assigned a numeric code. The miner’s control board firmware maintains an internal error registry, and when a fault is detected, it logs the code with a timestamp. These codes are surfaced through three channels:

Understanding Slot Numbering: SM0, SM1, SM2

Many Whatsminer error codes include a slot suffix — for example, 530, 531, 532. The last digit identifies which hashboard slot is affected:

• SM0 (codes ending in 0) — Hashboard slot 0 (top slot in standard orientation)
• SM1 (codes ending in 1) — Hashboard slot 1 (middle slot)
• SM2 (codes ending in 2) — Hashboard slot 2 (bottom slot)

When you see Error 531: SM1 not found, it tells you that hashboard slot 1 (middle) is not being detected. This slot-level granularity is one of the advantages of MicroBT’s system — you immediately know which board to investigate.

How to Access Error Logs

There are three ways to view Whatsminer error codes. Use whichever is most convenient for your situation.

Method 1: WhatsMinerOS Web Interface

The simplest method. Every Whatsminer has a built-in web interface accessible from any browser on the same network.

1. Find the miner’s IP address on your router’s DHCP client list, or use a network scanner.
2. Open a browser and navigate to http://MINER_IP
3. Log in with the default credentials: username admin, password admin (change these immediately on a new miner)
4. Navigate to Status or System Status — active error codes are displayed here with timestamps
5. Navigate to Log or System Log for historical error entries

Method 2: WhatsMinerTool Desktop Application

WhatsMinerTool is MicroBT’s official desktop management application. It is the preferred method for managing multiple miners and provides the most detailed error reporting.

1. Download the latest WhatsMinerTool from whatsminer.com (Windows only)
2. Install and launch the application
3. Click Scan to discover miners on your network (or add IPs manually)
4. Select a miner — error codes appear in the status column with color-coded severity
5. Right-click a miner and select View Details for the full error log with timestamps

WhatsMinerTool also supports batch firmware updates, configuration changes, and error log export — making it essential for anyone managing more than a handful of miners.

Method 3: btminerapi (Port 4028)

For advanced users and monitoring scripts, the Whatsminer API provides programmatic access to error data. The API runs on TCP port 4028 and accepts JSON commands.

# Query miner status and error codes via API
echo '{"cmd":"summary"}' | nc MINER_IP 4028

# Get detailed statistics including per-slot data
echo '{"cmd":"edevs"}' | nc MINER_IP 4028

# Get error code list
echo '{"cmd":"get_error_code"}' | nc MINER_IP 4028

# Check PSU status and error codes
echo '{"cmd":"get_psu"}' | nc MINER_IP 4028

Fan Errors (1xx Series)

Whatsminer fan errors are among the most common codes you will encounter. Whatsminers are exceptionally sensitive to fan performance — even minor speed deviations trigger error codes. This is by design: MicroBT engineers the firmware to be aggressive about fan monitoring because inadequate cooling is the number one cause of hashboard damage.

A critical detail: Whatsminers use high-current fans (6–7A draw). Installing aftermarket or refurbished fans with lower current ratings (e.g., 2.7A) will immediately trigger errors 120/121 even if the fans physically spin. Always use original MicroBT-rated fans.

Power Supply Errors (2xx Series)

The 2xx series is the largest error code group and arguably the most misunderstood. Errors 233, 234, 235, 236, 237, 238, and 268 are the most common Whatsminer errors in the field. The critical insight from years of repair experience: in 95% of cases when these codes appear, the power supply itself is fine. The real culprit is almost always loose copper bus bar screws — the high-current bolted connections between the PSU and hashboards.

PSU Communication and Configuration (200–219)

PSU Protection Errors — The Copper Bus Bar Codes (233–275)

Temperature Sensor Errors (3xx Series)

The 3xx series covers temperature sensor hardware failures — not actual overheating (that is handled by the 6xx codes and the 35x protection codes). These errors mean the miner’s temperature sensors are failing to communicate, returning invalid readings, or triggering emergency thermal protection.

Hashboard & Chip Errors (4xx–5xx Series)

These are the codes that determine whether your miner needs professional repair. The 4xx series covers EEPROM (hashboard identification chip) errors, while the 5xx series covers chip-level detection, communication, and performance failures. Many 4xx errors can be resolved with cable reseating or firmware updates. Most 5xx errors — especially those ending in specific chip addresses — indicate board-level failures requiring repair equipment.

EEPROM Errors (4xx)

Hashboard Detection and Chip Errors (5xx)

Advanced Chip-Level Errors (50xx–56xx)

On newer Whatsminer firmware, more granular chip-level error codes appear in the format 5XYZ where X indicates the slot, Y indicates the error type, and Z provides additional detail. These are less commonly seen in the web UI (they appear primarily in WhatsMinerTool detailed logs) but are important for professional diagnostics.

Environment & Performance Errors (6xx Series)

The 6xx codes are environmental monitoring alerts — they tell you the miner’s operating environment is outside acceptable parameters. Unlike the 3xx codes (which indicate sensor hardware failure), 6xx codes mean the sensors are working correctly and are reporting genuinely bad conditions.

Control Board & Firmware Errors (7xx–8xx Series)

The 7xx and 8xx codes cover the miner’s brain — the control board hardware and the software running on it. Most errors in this group are resolved by updating firmware from the official MicroBT website. If standard firmware update via the web interface fails, SD card flash (Burn Image method) is the reliable fallback.

Network & Pool Errors (2xxx Series)

The 2xxx error codes cover mining pool connectivity and hash rate performance. These are typically the easiest errors to resolve because they are usually caused by configuration issues or network problems rather than hardware failure.

Special Error Codes (8xxx, 9xxx, 100xxx)

These error codes fall outside the standard categories and cover firmware versioning, tool compatibility, and security/integrity checks.

PSU Hex Error Codes (0x0001–0x2000)

In addition to the numeric 2xx error codes reported by the control board, the Whatsminer PSU itself reports errors using hexadecimal codes. These appear in the PSU status section of WhatsMinerTool and the API. They provide more specific information about what is happening inside the power supply unit.

Diagnostic Flowcharts

When you encounter an error, these decision trees will guide you to the root cause. Follow the path that matches your symptoms.

Flowchart: Hashboard Not Detected (Errors 530–532)

This is the most common hardware error. Follow these steps in order:

1. Tighten all copper bus bar screws. This resolves the issue in approximately 40% of cases. Power cycle and check. Resolved? Stop here.
2. Reseat the ribbon/flat cable between the adapter board and the control board for the affected slot. Power cycle. Resolved? Stop here.
3. Try a known-good ribbon cable in the affected slot. These cables are fragile and develop invisible fractures. Power cycle. Resolved? Replace the cable permanently.
4. Swap the affected hashboard into a different slot.
   • If the error follows the hashboard to the new slot → The hashboard itself is faulty. Proceed to step 6.
   • If the error stays on the original slot regardless of which board is installed → The control board’s slot circuit is faulty. Try replacing the control board.
5. Try a different control board (if available). If the hashboard is now detected with the new control board, your original control board needs repair or replacement.
6. If the hashboard is confirmed faulty: Inspect visually for burn marks, cracked solder, or damaged components near the power input connectors and the first chips in the chain. Professional repair is needed — the board likely has a failed power delivery circuit or a broken communication chain at the first chip.

Flowchart: PSU Error (Errors 200–275, 0x codes)

1. Is the mains voltage correct? Measure at the wall outlet with a multimeter. Must be 200–240V AC. If below 200V, you need a different circuit or voltage stabilizer. If above 250V, you have a grid problem — contact your electrician.
2. Is the error 233–238 or 268? If yes: tighten all copper bus bar bolts. Power cycle. Resolved in 95% of cases. If not resolved, continue.
3. Is the 4-pin data cable intact? This thin ribbon cable between the PSU and control board carries the communication signal. Replace it with a known-good cable. Power cycle.
4. Is this error 200 or 201? If 200: PSU communication failure — often the data cable. If 201: PSU model mismatch — verify you have the correct PSU for your miner model.
5. Can you test with a different PSU? If a known-good PSU resolves the error, your original PSU is faulty. Replace it.
6. Try a firmware update — some PSU communication bugs are fixed in newer firmware. Flash via web interface, or SD card if web update fails.
7. If all of the above fail: The PSU has an internal hardware fault (failed capacitor, blown MOSFET, dead fan, or controller failure). Replace the PSU or send for professional repair.

Flowchart: Overtemperature (Errors 350–360, 600, 610)

1. Check ambient temperature. Place a thermometer at the miner’s air intake. Must be below 35°C (standard mode) or 30°C (high-performance mode). If above, cool the room first — no amount of hardware troubleshooting will fix a hot room.
2. Check airflow. Ensure at least 30 cm (12 inches) clearance on intake and exhaust. Verify exhaust air is not recirculating back into the intake.
3. Check fans. Are all fans spinning? Is the RPM reading normal in the web interface? If any fan shows 0 RPM or significantly low RPM, replace that fan.
4. Clean the miner. Use compressed air to blow dust out of heatsinks, fan blades, and between hashboard components. Dust insulation is a major cause of overheating in home mining environments.
5. Check thermal paste. On M30S and newer models, the thermal interface between ASIC chips and heatsinks can degrade over time. If all of the above steps do not resolve overheating, the thermal paste may need replacement. This requires disassembly of the hashboard and heatsink — it is a more involved procedure but well within home miner capability with careful technique.
6. If the room is cool, fans are good, airflow is clear, and the miner still overheats: A temperature sensor may be providing false readings, or a specific hashboard region has localized overheating from a failing chip. Professional diagnostics recommended.

M30S / M30S+ / M30S++ Specific Notes

The M30 series (based on the Samsung 8nm ASIC) was MicroBT’s most widely deployed generation and remains a staple in home mining operations. Here are model-specific considerations:

M50S / M56S / M60S / M63S / M66S Specific Notes

The M50 and M60 series represent MicroBT’s newer generations, using advanced ASIC processes (TSMC 5nm for M60 series). These models introduce additional error codes and refined error reporting compared to the M30 series.

Whatsminer vs. Antminer Error Systems: Side-by-Side

If you operate both Whatsminers and Antminers (many home miners do), understanding the differences in error reporting helps you diagnose both platforms more effectively. For the complete Antminer error reference, see our companion guide: Antminer Error Code & LED Reference Guide.

When to DIY vs. Contact D-Central

Home miners can resolve many Whatsminer errors with basic tools and this guide. But some problems require professional equipment, specialized parts, and experienced hands. Here is a severity-based decision matrix.

What to include when contacting D-Central for repair:

1. Miner model and firmware version — e.g., “M30S+, firmware 20230815”
2. Error code(s) — the exact numeric codes from the web interface or WhatsMinerTool
3. When the error started — sudden onset vs. gradual degradation
4. What you have already tried — bus bar tightening, cable swaps, firmware flash, etc.
5. Slot isolation results — “Error follows SM1 hashboard to any slot” or “Error stays on slot 2 regardless of board”
6. Photos — any visible damage, burn marks, or corroded connections

Call us at 1-855-753-9997 or visit d-central.tech/asic-repair to request a quote.

Complete Error Code Quick Reference Table

Use this master table when you need to quickly identify an error code and take immediate action. For detailed troubleshooting, click through to the relevant section above.

Frequently Asked Questions