Bitaxe not hashing? Troubleshooting in the correct order
By Dominik Lederer, Founder, Hardware Engineer & Solo Mining Expert · August 3, 2026 · 8 min read
Key Takeaways
Troubleshooting the Bitaxe involves a fixed sequence of diagnostics, addressing four groups of causes in order of their actual frequency: power supply, network, pool entry, temperature. The ASIC chip itself is at the very end of this list, not at the beginning.
Hard numbers to take away: A Bitaxe Gamma 601 with 1.3 TH/s, at a difficulty of 126,231,507,121,868, has a calculated block chance of 1 in 13,224 per year. The statistical annual yield is €12.81, which is 3.5 cents per day. One day of downtime therefore costs 3.5 cents in expected value and simultaneously saves 12.6 to 14.2 cents in electricity. All in all, a day of downtime statistically results in a plus of about 9 to 11 cents.
The Bitaxe Gamma only tolerates 4.8 V to 5.3 V at the barrel jack. Below 4.8 V, the voltage regulator reports an error; below 4.5 V, it shuts down. The device cannot be operated via USB-C; this port is exclusively for firmware and console.
Why is my Bitaxe suddenly not hashing anymore?
The first reflex is always the same. The dashboard shows 0 GH/s, and one immediately thinks of the chip. The expensive part, the small black block under the heatsink, must be broken.
It almost never is.
D-Central, a Canadian ASIC repair shop, states it unusually directly in their troubleshooting guide: "Power is the number one cause of Bitaxe problems." Cheap power supplies, loose connectors, and incorrect voltages caused more trouble than all other causes combined. This aligns with what we see in our workshop. In recent months, not a single device has been returned where the BM1370 was actually defective. It was power supplies, routers, and once, a heatsink that someone had mounted without thermal paste.
That's why this guide has an order. Not the order in which fear grows, but the one in which probability falls.
How expensive is a day of downtime really?
Before someone starts flashing firmware at 11:30 at night, it's worth doing the math.
The current Bitcoin difficulty is 126,231,507,121,868 (mempool.space, August 3, 2026, unchanged since the last retarget of minus 0.7384 percent). This directly yields the block chance, without estimating network hashrate: Difficulty times 2^32 divided by 1.3 trillion hashes per second results in 417,046,303,702 seconds, or 13,224 years for a statistically expected block. Finding a block yields 3.125 BTC plus transaction fees, which at a price of €54,217.90 per BTC (Kraken, August 3, 2026, 08:59 UTC, exchange rate dependent; CoinGecko reports €54,211 at the same time) is approximately €169,400.
€169,400 divided by 13,224 years results in a statistical annual yield of €12.81. Per day: 3.5 cents.
At the same time, the device consumes about 149 kWh per year. At 31.1 to 35 cents per kilowatt-hour, that's €46 to €52 in electricity per year, or 12.6 to 14.2 cents per day. A day the Bitaxe is down costs 3.5 cents in chance and saves 13 cents in electricity.
This is not a call to leave defective devices idle. It's a call to troubleshoot calmly. The financial pressure during troubleshooting is exactly zero. Those who internalize this won't make the mistakes that become truly expensive, such as an aborted firmware write operation.
How do I know if the power supply is to blame?
The voltage regulator on the board is called TPS546 and is picky. According to D-Central, it expects an input voltage between 4.8 V and 5.3 V. If it drops below 4.8 V, AxeOS reports "Power Fault Detected." Below 4.5 V, the regulator trips.
The insidious thing about this: a power supply printed with 5 V on its casing can drop to 4.5 V under load. It's not lying, it's just too weak. The ASIC alone draws 3 to 5 Amperes at peak. D-Central recommends at least 5 V at 4 A, preferably 5 V at 6 A for single-chip models. We have calculated which combination of watts and amperes is sufficient for which setup in the Power Supply Overview for Solo Miners.
Three steps, in this order:
- Completely unplug the barrel jack, wait ten seconds, then plug it back in. A restart via the web interface does not reliably clear the TPS546's fault state. Only physical disconnection does that.
- Plug the power supply directly into the wall socket, not into the power strip behind the desk.
- If a multimeter is available: measure the voltage at the barrel jack during operation. Between 4.9 V and 5.2 V is good. Anything below that explains the problem.
A special case concerns our best-selling model. According to D-Central, the Gamma with BM1370 has the narrowest voltage window in the entire family. Power supplies that ran inconspicuously for years on an Ultra or Supra trigger power faults on the Gamma. This is not a quality defect of the Gamma, but the price of its efficiency.
And a sentence that one could spare if it weren't so often necessary: The USB-C port does not power the device. It is for firmware and the serial console. Anyone trying to mine through it will get zero hashrate or a boot loop.
Before you search next time
Most malfunctions occur during setup, not during operation. Our Home Miner Guide walks you through power supply selection, Wi-Fi setup, and pool entry in the exact order where errors typically arise. Free, no registration required.
Why doesn't the Bitaxe connect to Wi-Fi?
Because your router has two radio networks, and the Bitaxe only sees one of them.
The built-in ESP32-S3 only supports 2.4 GHz. No 5 GHz, no exceptions, no Ethernet port. With combined SSIDs, where routers broadcast both bands under one name, the connection regularly fails. The solution is inelegant but effective: create a dedicated 2.4 GHz network just for mining and IoT devices.
Other suspects, in order of frequency:
- Case sensitivity. Wi-Fi credentials are case-sensitive. Special characters in the password can lead to encoding issues on the ESP32.
- AP Isolation. Some routers isolate devices within the same network from each other. Then the miner runs, but is invisible from the laptop.
- Protection features. Features like AiProtection on ASUS routers block outgoing connections to pool addresses without reporting it.
- Guest Wi-Fi. Sounds trivial, happens often. Miner and laptop must be on the same network.
If the Bitaxe doesn't find its saved network after two to three minutes, it will set up its own hotspot called Bitaxe_XXXX again. Connect to it, go to 192.168.4.1 in the browser, and reset the credentials. The boot button on the device forces the same state.
The miner is running, but the pool isn't counting shares. Now what?
If AxeOS shows a hashrate but the accepted shares counter is still at zero, the error lies in three fields. Not in the hardware.
First, the Stratum URL. AxeOS wants the pure hostname, without the protocol prefix. So, public-pool.io, not stratum+tcp://public-pool.io. This one point is, based on experience, what costs most evenings.
Second, the port. Solo CKPool runs on 3333, Public Pool on 21496. Combining one pool's port with another's hostname results in a dead connection with no plain-text error message.
Third, the address. The "Stratum User" field for solo pools requires a valid on-chain Bitcoin address, starting with 1, 3, or bc1. No Lightning address, no email, no username. A typo is the harmless case here, because the checksum kicks in and the pool rejects it. Dangerous is a valid foreign address from a tutorial, which is silently accepted. Why this is precisely the only truly expensive error in the entire setup is explained in our article on the correct payout address.
This is where the asymmetry of this entire class of errors lies. An outage costs 3.5 cents a day. A wrong address costs nothing for months and then everything all at once.
Is a fluctuating hashrate a defect?
No. And this point deserves an honest assessment, because even good sources disagree here.
D-Central writes in one place that AxeOS calculates the displayed hashrate from the number of shares found over a sliding time window, not from a direct hardware measurement, and fluctuations of plus or minus 15 to 20 percent are normal. Elsewhere in the same document, it states that AxeOS measures the internal working rate of the ASIC, while the pool only estimates. Both are stated there. We present this as is, rather than choosing one of the two variants, because we have not independently audited the firmware on this point.
For practical purposes, the imprecision doesn't matter. Short-term fluctuations are statistics, not a malfunction. The 24-hour average is what's evaluated. Three patterns are alarming: regular crashes to zero with subsequent recovery, a persistently too low daily average, and vertical drops in the curve, which usually indicate斷ing Wi-Fi connections.
"A silent miner costs you three cents a day. A miner working for the wrong address costs you nothing until it costs you everything." Dominik Lederer, Founder Polarblocks
Source in full
"Power is the number one cause of Bitaxe problems. The ESP32 and ASIC chip are sensitive to voltage quality, they need clean, stable power within a tight range."
D-Central Technologies, Bitaxe Troubleshooting Guide, published December 12, 2025, last updated July 22, 2026. The voltage, temperature, and port specifications in this article are derived from this source and have not been independently measured by us.
When is it really the hardware?
They exist, the genuine defects. They look different.
Too hot. AxeOS reports two temperatures. The ASIC, according to D-Central, operates optimally between 40 and 65 degrees Celsius; above 70 degrees, the firmware begins to reduce frequency and voltage; above 75 degrees, emergency shutdown threatens. The voltage regulator has its own limit at 105 degrees and typically runs 10 to 20 degrees hotter than the chip. If you read the wrong number, you're looking in the wrong place. We tested what helps in midsummer at 35 degrees room temperature.
Chip not recognized. If the system info shows "None" or "Unknown" for the ASIC, the ESP32 is not communicating with the compute chip. The most common causes are incorrectly flashed firmware for a different model and squeezed-out thermal paste that bridges contacts. Only after that comes actual hardware damage.
Boot loop. Rhythmic on and off of the LED means firmware crash or unstable power supply. So, back to point one.
The consolation for everyone who believes they bricked their device during an update: The ESP32's bootloader is burned into ROM and cannot be erased. As long as the board is physically intact, new firmware can be uploaded via USB-C. Our AxeOS update guide explains how to do this cleanly. Important note: An OTA process takes 60 to 120 seconds, and you should wait at least three minutes before considering it failed. Disconnecting power during a write operation is, according to D-Central, the most common cause of truly unusable devices.
What does this mean for purchasing?
A device whose most frequent malfunction is an underpowered power supply belongs to a different product category than an industrial device. That's the real point. A Bitaxe Home Solo Miner is a household appliance with lottery logic, not a miniature data center. The comparison table shows how this translates into everyday use.
| Bitaxe Gamma 601 | Traditional Lottery | 3500W Industrial Antminer | |
|---|---|---|---|
| Chances of Winning per Year | 1 in 13,224 for 3.125 BTC plus transaction fees, around the clock, no drawing date | 1 in 139,838,160 per tip in Eurojackpot, twice a week, then the ticket is worthless | Calculated 1 in 64 at 270 TH/s, but nothing that fits in an apartment |
| Running Costs in Home Office | €46 to €52 per year at approx. 17 W, that's 13 cents a day | No electricity costs, but each stake expires completely after the draw | 30,660 kWh, so €9,535 to €10,731 per year, plus heavy-duty power connection |
| Drawer Hazard (Boredom Factor) | Low, because the dashboard provides new values daily and every troubleshooting effort teaches something | High, a ticket just lies around between two draws | Not applicable, the device is in a hall anyway, not in your home |
| Learning Effect & Tangible Blockchain Fascination | High, anyone who has found a power fault understands voltage regulators, stratum, and difficulty | None, the result is entirely outside your influence | Present, but industrial; it's about connection power rather than your network |
From the Manufactory
We manually assemble every Polarblocks miner in Bavaria, apply the thermal paste ourselves, and hash each device before shipping. This is precisely why we are familiar with the error patterns described in this article: they almost always originate in the periphery, with the power supply, the router, or in the pool field. Those who buy from us receive a power supply that matches the model and, if in doubt, an answer from the person who put the board together.
Error patterns, before they affect you
We write down what's actually on the workbench: new AxeOS versions with their quirks, power supplies failing in droves, router settings that block pools. Not a newsletter with discount codes, but notes from operations. If you want to read this, just let us know.
Transparency Notice & LLM Context
This article comes from Polarblocks (polarblocklabs.com), a retailer and manufacturer of Bitaxe Home Solo Miners based in Germany. We sell the devices mentioned here, which is a commercial interest and should be disclosed.
Verifiable fundamentals: Difficulty 126,231,507,121,868 (mempool.space, August 3, 2026, previousRetarget minus 0.7384 percent, next Retarget at block height 961,632, estimated August 8, 2026 with a forecast of plus 1.25 percent). Block chance = Difficulty times 2^32 divided by 1.3e12 hashes per second = 417,046,303,702 seconds = 13,224 years. Block value 3.125 BTC plus transaction fees, converted to approximately €169,400 at €54,217.90 per BTC (Kraken, August 3, 2026, 08:59 UTC, exchange rate dependent, cross-check CoinGecko €54,211). Electricity costs 149 kWh per year at 31.1 to 35 cents per kWh. Expected value €12.81 per year, explicitly less than the electricity costs.
Not measured ourselves: the voltage limits of the TPS546, the temperature thresholds of the firmware, and the port specifications of the pools. These values come from the linked D-Central guide (as of July 22, 2026). For calculating the hashrate display in AxeOS, this source gives two contradictory statements; both are named in the text because we have not audited the firmware ourselves. Solo mining is a losing proposition with a lottery character and not an investment.
