Skip to content

We're upgrading our operations to serve you better. Orders ship as usual from Laval, QC. Questions? Contact us

Bitcoin accepted at checkout  |  Ships from Laval, QC, Canada  |  Expert support since 2016

WM_610 / Error 610 / high-profile fallback / power_mode downgraded Info

Whatsminer Error 610 – High Profile Mode Temperature Fallback

BTMiner firmware raises Error 610 when it decides the high-power profile target is no longer sustainable - intake ambient drifting into the 28-34 C band, PSU input voltage sagging under load, PSU internal temp climbing, or per-board thermal asymmetry - and auto-downclocks one profile step (high to normal, or normal to low). The miner stays online and keeps hashing at the safer profile, with realized hashrate 8-22% below the high-profile target depending on model.

Informational — Monitor and address as needed

Affected Models: Whatsminer models that expose the high-power / turbo profile in BTMiner: M30S++, M50, M50S, M50S+, M50S++, M53, M53S, M56, M56S, M60, M60S, M60S+, M63, M63S, M66, M66S. Older M20S/M21S/M30S/M31S generations do not carry the Error 610 profile-fallback flag and instead surface intake or chip-level thermal faults directly (Error 600 / Error 800 / TEMP_OVER).

Symptoms

  • WhatsMinerTool or dashboard displays Error Code 610 with a variant message (high-power profile fallback / high-profile mode unavailable / auto-downclock active / power profile downgraded)
  • btminer.log contains power_mode, profile_fallback, high_profile_off, or code 610 entries with a target-vs-actual wattage delta
  • API get_miner_status returns a power_mode field that flipped from high to normal (or normal to low) without operator change, plus a fault object with code 610
  • Realized hashrate 8-22% below the high-profile target, sitting at the normal-profile target instead - typically 10% drop on M30S++/M50S++ class, 15% on M60S/M60S+, 18-22% on M66/M66S
  • Wall power draw drops in lockstep with hashrate, confirming the firmware actually downshifted (not that hashboards are missing)
  • Drop-to-low-profile happens at a predictable time of day - late afternoon in summer, or minutes after a neighbour's A/C / dryer / shared-circuit appliance cycles
  • Intake-ambient reading sits in the 28-34 C band - high enough to scare the firmware but below the Error 600 ceiling
  • PSU input voltage sags below 230 V on a 240 V circuit, or below 200 V on 208 V commercial, under full load
  • PSU internal temp climbs past 60-70 C while the rest of the miner is otherwise nominal - PSU is the headroom-limiting device
  • Operator runs the miner intentionally on high-power profile (not stock) and the firmware will not let the profile stay engaged for more than 30-60 minutes
  • Error 610 pairs with Error 600 (intake warning) or Error 275 (PSU over-temp warning) on the same dashboard - 610 is the response, those are the trigger inputs

Step-by-Step Fix

1

Manually drop to the normal power profile via the dashboard or WhatsMinerTool and let the miner stabilize for 15 minutes. This is half a diagnosis and half a fix - if normal-profile runs clean and stays clean, you have confirmed the issue is high-profile sustainability rather than a deeper hashboard or firmware fault. Many home installs simply cannot sustain Whatsminer high-power mode year-round; the right move is to design around the normal profile and use high-power as a winter-only bonus when intake ambient is low and the wall feed is rock-solid.

2

Measure actual intake ambient with an external IR thermometer at the front grille while the miner is hashing. Hold the IR 5 cm from the grille slats. If you read 28-34 C, you have found the trigger - 610's sweet-spot ambient band sits below the Error 600 ceiling, so you can hit 610 in a room that looks fine by Error 600 standards. Below 25 C is the comfort zone for high-profile. Above 34 C and you should be seeing Error 600 first.

3

Open a door, install an exhaust fan, or redirect ducting to drop intake below 25 C. Watch the dashboard - if 610 clears within 10 minutes of intake dropping below the 25 C line, ambient was the sole cause. Build a permanent intake fix (cold-air plenum, dedicated exhaust) before the next warm season. In a Canadian climate this is trivial October-April; June-August it requires planning.

4

Verify physical clearance and check for exhaust recirculation in multi-miner installs. At least 30 cm in front of the intake, at least 15 cm behind the exhaust, and no other miner's exhaust pointed at this one's intake. A neighbour miner's roughly 65 C exhaust will push your intake reading up 5-10 C and trigger 610 even in an otherwise cool room. Cold aisle / hot aisle layout solves this for racks.

5

Hard power-cycle the miner if 610 ghosts after install conditions improve. Pull the cord for 60 seconds, reconnect. Some BTMiner builds hold 610 in the fault map across a soft reboot even after the trigger condition resolves - a cold boot clears the ghost. If the miner comes up on the high profile and stays there for an hour, you are back in business.

6

Measure wall voltage at the outlet under load with a multimeter on AC. Probe the hot-to-neutral pair (or hot-to-hot on 240 V split-phase) while the miner attempts high-profile. Targets: at least 235 V on 240 V split-phase, at least 205 V on 208 V commercial, at least 215 V on 220 V industrial. If voltage sags below those numbers, your power feed is the cause - 610 is the firmware protecting the PSU from undervolt operation. Move the miner to a dedicated circuit at the right voltage and amperage rating.

7

Log 24 hours of dashboard hashrate and power_mode readings at 5-minute intervals. Export from MinerTool, or scrape get_miner_status to CSV. Plot the series. A 610 event at the same time of day every day points at HVAC circuit loading or solar-driven ambient swing. A random 610 pattern points at marginal hardware (PSU ripple, single-board thermal, intermittent connector). The pattern tells you which branch to chase.

8

Move the miner to a dedicated 240 V (or 208 V / 220 V industrial) circuit and confirm voltage holds steady under load. Whatsminer high-profile mode on 120 V is borderline-unsupported on most models - the PSU works harder, voltage sags more, and 610 becomes a daily occurrence. A dedicated 240 V circuit at the rated amperage (20 A minimum for most M50/M60-class miners; 30 A for the high-density M66/M66S) is the foundation for sustainable high-profile operation. One-time install cost, pays back in months.

9

Service the intake - vacuum the grille, replace or rinse the foam pre-filter, deep-clean the heatsink front faces visible through the grille. A dust-loaded intake raises the boundary-layer temp at the environment thermistor and reduces actual airflow through the heatsinks - both push the firmware toward 610. Soft-brush vacuum attachment, light touch, no compressed air from inside-out (you just push dust back where you cleaned).

10

Check per-board chip-temp readings and identify any single board running 5-10 C hotter than its siblings. Open the dashboard's per-board telemetry. If one board is hot while two are cool, that board's heatsink seating, thermal paste condition, or slot airflow is the problem - and the firmware downshifts the whole miner to keep the one board safe. Resolve the hot-board issue (paste refresh, fan check, slot-swap diagnostic) and 610 clears.

11

Measure PSU output ripple under load with a scope. Probe the DC output to the hashboards while the miner is on the high profile. Healthy: low-tens of mV ripple at the switching frequency. End-of-life: hundreds of mV, or visible droop under load transients. If ripple is high, the PSU output filter caps are dried - PSU swap (or cap-bank rework at D-Central) is the only real fix. Running on a high-ripple PSU also shortens hashboard chip life.

12

Reseat the PSU-to-control-board harness and the PSU-to-hashboard busbar/cables. Power off, disconnect each harness, inspect for oxidation or burn marks, reseat firmly. A high-resistance contact in any of those paths shows up as voltage sag under load - exactly what triggers 610. On bus-bar designs, torque the screws to spec; loose busbar screws are a documented cause of intermittent voltage-sag faults on the M50/M60-class miners.

13

Roll BTMiner one version back (or forward to a known-stable build) via MinerTool. Verify hardware revision compatibility against MicroBT's build table on support.whatsminer.com/downloads before flashing - the wrong air firmware on a hydro board, or vice versa, bricks the control board. Wired flash only, never wireless, never while hashing. Document the working build on a sticker inside the chassis. A known regression on M50S++/M60S+ minor builds tightened the high-profile envelope without changelog notes; rolling back restores the older threshold.

14

Refresh thermal paste on the hottest hashboard if step 10 identified a single hot board. Remove the heatsink, clean the chip and heatsink mating surfaces with 99% IPA and lint-free wipes, apply a uniform thin layer of Arctic MX-6 or Thermal Grizzly Kryonaut, reassemble with the original spring/screw torque. Dried paste is the most-common cause of single-board thermal asymmetry on Whatsminers older than 2 years.

15

Inspect the PSU internal heatsink, fan, and cap bank for end-of-life signs. Open the PSU shell with mains disconnected and capacitors discharged. Look for bulged or vented electrolytics, dried paste on the FET heatsinks, dust loading on the PSU intake fan, blackening on board traces near the input rectifier. Any visible damage means retire or rework. The PSU is the most-replaced component on a Whatsminer aged 3+ years, and 610 is often the first symptom of its decline.

16

Stop DIY and ship to D-Central when ambient is confirmed at or below 25 C, wall voltage is in spec, per-board thermals match within plus-or-minus 3 C, firmware has been rolled across at least two builds with no improvement, and 610 still raises within the first hour of high-profile operation. You are now looking at a control-board ADC drift, a thermistor lying about ambient or PSU temp, or a hashboard voltage-domain regulator pulling more current than expected - all of which need a bench scope and the MicroBT service manual to isolate. Book a D-Central ASIC Repair slot at d-central.tech/services/asic-repair.

17

D-Central bench process for Error 610 escalations: PSU output ripple verification under controlled load, cap-bank rework or full PSU replacement from our matched-spec inventory, control-board ADC reference verification with a calibrated source, environment + PSU thermistor verification against a calibrated reference, per-board voltage-domain current draw measurement, full BTMiner reflash against MicroBT's master build table for your hardware revision, and a 24-hour burn-in at high-profile in a controlled 25 C environment to confirm the fault is fully cleared before the miner ships back.

18

Pack for shipping. Anti-static bag on the control board if shipping it separately; if shipping the full miner, double-box with at least 5 cm of foam on every side. Include a printed diagnostic note with: BTMiner firmware build, exact 610 fault message as it appeared on the dashboard, intake ambient logged at the time of the fault, wall voltage under load, per-board chip-temp readings, install photos showing clearance and airflow, the dedicated-circuit specs for your power feed, and every Tier 1-3 step you have already run. Better notes equal faster and cheaper repair.

When to Seek Professional Repair

If the steps above do not resolve the issue, or if you are not comfortable performing these repairs yourself, professional service is recommended. Attempting advanced repairs without proper equipment can cause further damage.

Related Error Codes

Still Having Issues?

Our team of Bitcoin Mining Hackers has been repairing ASIC miners since 2016. We have seen it all and fixed it all. Get a professional diagnosis.