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

Error 600 / env_temp_high / ambient out of range Warning

Whatsminer Error 600 – Environment Temperature Too High

BTMiner firmware raises Error 600 when the dedicated environment (intake ambient) thermistor crosses the warning ceiling - typically 35 C on M30S-family and 40 C on M50/M60/M66-class builds. The miner is still hashing but is one step away from the chip-level Temperature Too High trip or an Error 610 auto-downclock.

Warning — Should be addressed soon

Affected Models: All Whatsminer models running BTMiner firmware with the Error 600 fault map: M20S, M21S, M30S, M30S+, M30S++, M31S, M31S+, M32, M33, M50, M50S, M50S+, M50S++, M53, M53S, M56, M56S, M60, M60S, M60S+, M63, M63S, M66, M66S. Both air and hydro chassis are covered; hydro and M60/M66-class run tighter intake envelopes (typically 30 C ceiling vs 35 C on older air models).

Symptoms

  • WhatsMinerTool or dashboard displays Error Code 600 with a variant message (env temp too high / environment temperature too high / intake temperature high / ambient out of range)
  • btminer.log or kern.log contains env_temp, ambient, or code 600 entries with a Celsius reading
  • API get_miner_status returns a fault object with code 600 and a msg string naming the ambient sensor
  • Front-panel status LED flashes orange/yellow (model-dependent) without the solid-red critical pattern
  • Miner is still hashing - at nameplate or already auto-downclocked 5-15% if Error 610 also fired
  • Dashboard PSU internal temp climbs alongside the ambient reading, confirming the intake air is actually warm (not a sensor lie)
  • External IR thermometer at the front grille reads 30 C or higher under load
  • Event recurs at a predictable time of day - late afternoon in summer, or minutes after a dryer/A-C/heater cycle on the same HVAC circuit
  • All fans pegged at or near 100% duty for more than 10 minutes
  • Chip-level PCB temp / Chip temp readings climb in lockstep with ambient, not ahead of it
  • Dashboard intake-ambient reading disagrees with external IR by more than 5 C (indicates sensor drift, not a real ambient problem)

Step-by-Step Fix

1

Hard power-cycle the miner - pull the cord for 60 seconds to let bulk capacitors drain, then reconnect. Some BTMiner builds hold Error 600 across a soft reboot, and a full cold boot clears transient ghost faults. If the miner comes up clean and stays clean for an hour, you caught a transient event (intake air spike, HVAC event, brief sun on the chassis). Log the timestamp and monitor for 24 hours before declaring victory.

2

Measure the actual intake ambient with an external IR thermometer. Hold the probe or IR 5 cm from the front grille while the miner is hashing at full load. Compare that reading to the dashboard's intake-ambient display. If the two agree within plus-or-minus 2 C, the thermistor is honest and you have a real ambient problem - go to step 3. If the miner reads more than 5 C higher than your external IR, the sensor or its ADC path is lying and you should skip ahead to Tier 3 thermistor diagnostics.

3

Vacuum the front intake grille, intake shroud, and the front face of the heatsinks visible through the grille slots. Use a shop-vac soft-brush attachment, light touch. Do not blow compressed air from the chassis interior toward the room - you just blow dust back onto the front face you are trying to clean. Run the vacuum across the full grille area for 60 seconds. On M50/M60/M66 class, remove the front grille entirely if it is tool-less. Dust-packed grilles are D-Central's single most-resolved Error 600 root cause in the retail repair queue.

4

Confirm physical clearance. At least 30 cm in front of the intake, at least 15 cm behind the exhaust, nothing within 15 cm blocking or redirecting airflow. Pull furniture back, move cardboard, confirm no pet bed is feeding lint into the intake. In a multi-miner install, verify no other miner's exhaust is aimed at this one's intake - collected hot exhaust should leave the install space, not recirculate.

5

Verify the room ambient against spec. M30S-family air: 35 C ceiling at the intake. M50/M60/M66-class air and any hydro intake: 30 C ceiling. If the room itself is out of spec, you have an HVAC or ventilation problem before you have a miner problem. Open a door, install an exhaust fan, redirect a duct, or move the miner to a cooler corner. You cannot fix an ambient envelope issue at the miner.

6

Log 24 hours of dashboard intake-ambient readings at 5-minute intervals. MinerTool can export this, or scrape the get_miner_status API every 300 seconds to CSV. Plot the series. If Error 600 fires at the same time of day, you are looking at HVAC circuit loading (neighbour's A/C, your own dryer, a shared utility circuit). If the pattern is random, you are looking at a sensor or airflow problem. The pattern tells you which branch to pursue next.

7

Install or service a washable foam pre-filter on the intake. D-Central recommends a thin foam pre-filter on every Whatsminer install - it catches dust before it loads the grille and heatsinks, and you can rinse it in a sink in seconds. Without a pre-filter you rely on the grille and fins themselves to catch debris, which is exactly the failure mode step 3 fixes. This is a 25 to 60 CAD retrofit that pays for itself in one avoided hashboard clean.

8

Measure line voltage at the outlet under load. 240 V split-phase expect 235-245 V; 208 V commercial expect 202-212 V; 220 V industrial expect 215-225 V. Low line voltage forces the PSU to draw more current, which heats PSU internals, which can leak heat into the intake plenum on some Whatsminer chassis. Low line voltage can indirectly cause Error 600 via PSU thermal coupling - fix the feed first, then reassess.

9

Re-check fan tach readings on the dashboard. Confirm all four (or six on M53/M56/M63/M66 air) fans are spinning within 10% of each other. A single stalled or slow fan cuts intake air velocity by roughly 25%, and the environment thermistor reads the moving air at the intake - when air stops moving, the reading climbs even in a cool room. If any fan is low, resolve the Error 110 / 111 / 120 / 130 fan fault first before continuing to chase 600.

10

Reseat the PSU-to-control-board harness. A loose PSU harness can cause the control board's ADC reference to drift slightly, which skews all thermistor readings - including the environment channel - on the high side. Power off, disconnect the harness, inspect both halves for oxidation, reseat firmly until you hear or feel the click. This is a cheap, fast check before opening anything deeper.

11

Open the chassis and locate the environment thermistor. On M30S-family boards it is typically soldered to the control board near the front intake edge, or mounted on a short harness with a 2-pin JST connector to a through-hole header. On M50/M60-class the thermistor is usually on a harness. Compare the physical placement to the service doc for your specific model on support.whatsminer.com - MicroBT publishes air/hydro/immersion manuals that call out the sensor location and harness pinout.

12

Inspect the thermistor connector for oxidation. Green-tinged corrosion on the pins is a direct cause of high-biased readings - common on humid basement or coastal installs. Pull the connector, clean both halves with 99% isopropyl alcohol on a lint-free wipe, let dry for 60 seconds, reseat firmly and confirm the latch clicks. Re-test with an external IR at the grille vs the dashboard reading. If they now agree within plus-or-minus 2 C, you are done.

13

If the reading is still high against external IR after connector clean and reseat, the thermistor itself or its ADC path on the control board is the problem. Desolder the NTC part (typical package: 0603 SMT or through-hole 5 mm bead), measure its resistance at a known reference temperature against the NTC's datasheet R-T curve, replace if out of spec. Most operators stop here and swap the control board or ship to D-Central - the NTC part costs a few dollars but the test/replace cycle takes hours without a scope and the manufacturer's R-T data.

14

Flash a known-good BTMiner firmware build via MinerTool. MicroBT's firmware portal is support.whatsminer.com/downloads. Verify your hardware revision against the build compatibility table before flashing - the wrong air firmware on a hydro board or vice versa bricks the control board and costs you a board swap. Never flash over wireless; wired only. Never flash while the miner is hashing. Record the build version on a sticker inside the chassis for next-time reference.

15

If a new BTMiner build is misbehaving, roll one version back. A documented regression between minor builds has caused transient Error 600 ghost faults on M30S++ and M50S units - the fault fires, clears, and leaves a ghost on the dashboard. Rolling back to the previous working build clears it. Your working build is your working build; note the exact version string and do not chase releases for their own sake.

16

Stop DIY and ship to D-Central when: external IR confirms the thermistor is lying by more than 5 C even after clean and reseat; firmware rollback and forward-flash both fail to clear; the control board ADC reference is suspected; visible damage to the thermistor, its harness, or adjacent components (burnt trace, lifted pad, green corrosion, cracked MLCC). You are now in bench territory - book a D-Central ASIC Repair slot at d-central.tech/services/asic-repair.

17

D-Central bench process: per-channel thermistor verification against a calibrated reference, ADC input check with a scope, thermistor replacement from our matched-R-T NTC stock for your specific model, connector rework if oxidation is present, full BTMiner reflash against MicroBT's master build table for your hardware revision, and a 24-hour burn-in at nameplate hashrate in a 25 C controlled environment to confirm the fault is fully cleared before the miner goes back in the shipping box.

18

Pack for shipping. Anti-static bag on the control board; 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 fault message as it appeared on the dashboard, external IR reading at the grille vs the miner's own reading, ambient in your install space, install photos showing clearance and airflow, 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.