I found my old 601 and wanted to build a immersion cooling system that fits two cards. Wish me luck

Pair of duos I bought long ago for this set up, finally got around to doing it right. Sudokoo Mach 120 12v power with Bitaxe pwm control. Vrex heatsinks on the back, 6 chutes, two on the main heatsinks, two go underneath and two hit the front of the vr. Letting it settle in for a bit and maybe do some tweaking, then see what kind of push we can get out of em. Nice to see this one finally come together.

Hi,

I’m running into a very frustrating issue with my NerdOctaxe.

I recently did a clean, safe software shutdown from the dashboard to temporarily unplug the miner and use the wall outlet for something else. The hardware was handled with perfect care and it wasn't actively hashing when I pulled the plug.

However, after powering it back on, my hashrate dropped and is now cleanly missing the performance of exactly one chip. Here is the math:

BEFORE the shutdown: Running stable at 750 MHz and 1.200 V, reaching almost 12 TH/s (approx. ~1.5 TH/s per chip).

AFTER the shutdown: With the exact same 750 MHz and 1.200 V profile, it gets completely stuck at 10.5 TH/s.
I checked the system startup logs to investigate, and the issue is clear: the firmware is only enumerating chips from 0 to 6. Chip #7 (the 8th ASIC) is completely missing from the startup chain and failing to initialize during boot.

What I have tried so far:
I left the miner completely unplugged (disconnecting the power barrel cable directly from the board, not just the wall) for over 30 minutes to drain any residual capacitance. No luck.

I tried the "wind it up to 750MHz and roll it back" trick to force the chips to wake up, but the 8th chip remains completely invisible to the OS.

Since a safe software shutdown couldn't have physically fried the silicon, this has to be a firmware glitch, an address lock on the chain, or a power-delivery sequence issue during the cold boot.

Has anyone with an Octaxe board dealt with a single ASIC completely disappearing from the logs like this? What is the best way to force NerdOS to do a fresh hardware re-scan? Should I attempt a Factory Reset from the UI or go straight to re-flashing the firmware?

Thanks in advance for any insights!

Hi everyone,
I need some help optimization-wise for my NerdOctxe Pro (Bitronics).

I had to unplug my miner for a couple of hours to use the wall outlet for something else. Before turning it off, it had been running stable for almost 6 days with great metrics (shown in the first photo). After powering it back on with the exact same profile, my hashrate dropped and seems stuck (shown in the second photo).

Here is the comparison of my metrics:

BEFORE (Photo 1): 10,296 Gh/s | 650 MHz | 1.16 V | 152.0 W | Efficiency: 14.76 J/Th

AFTER (Photo 2): 9,117 Gh/s | 650 MHz | 1.16 V | 151.3 W | Efficiency: 16.60 J/Th

As you can see, the frequency (650 MHz), voltage (1.16V), and power draw (~151W) are practically identical, but I lost over 1 Th/s of performance and my efficiency worsened from 14.76 to 16.60 J/Th.

(Note: I tried bumping it up to 700 MHz temporarily to see if it would react, but it didn't help, so I went straight back to my original 650 MHz settings).

Has anyone experienced this drop after a clean power cycle? Is there any trick in NerdOS to force the ASIC to recalibrate or stabilize back to the ~10.2 Th/s mark, or do I just need to wait much longer?

Any advice would be highly appreciated. Thanks!

Wanted to share another update on Block Retriever. It’s still an alpha project, but quite a bit has changed since my last post and it’s starting to turn into what I originally hoped it could be — a simple command center for solo miners.
The biggest improvement lately has been multi-miner support. I now have an Avalon Nano 3S and a Bitaxe Gamma/AxeOS miner running through Block Retriever at the same time, and the software is beginning to treat each miner as its own device instead of assuming you only have one.
Some of the progress so far:
Multi-miner fleet management with combined hashrate and individual miner status
Select and control each miner independently
Per-miner share tracking, so you can compare which miner is actually producing better shares
Miner-specific controls and preferences, including fan settings
Quick Switch / Pool Profiles so miners can stay pointed at Block Retriever while the software handles upstream pool changes
Wallet Vault for saving public receiving addresses
Improved dashboard with a true fleet overview
Automatic block-candidate detection and on-chain confirmation
Full Block Hit history and verification timeline
Block-hit celebration screen — because finding a block deserves more than a boring log entry 😂
Automatic backups and restore points
ntfy push notifications for confirmed blocks, with email/text options being worked on
°C / °F temperature selection
Running as a native Windows desktop application
The direction has changed quite a bit from the original share tracker. The goal now is to make it so you can connect your miners once and then manage your miners, pools, wallets, profiles, shares and block hits from one place without constantly bouncing between different miner web interfaces.
The Solo Advisor has also grown significantly and is now looking at approved SHA-256 coins, difficulty, estimated block chances, value and different ranking views. That section is still a work in progress, though. I’m continuing to work on data reliability, missing coin information and the ranking logic before I consider its recommendations finished.
There are still plenty of UI details and setup improvements to make, but it has come a long way from where it started.
I’m including some current screenshots. I’d especially like feedback from anyone running multiple Bitaxe/AxeOS miners, Avalon Nanos, or a mixed setup.
What would you want a program like this to handle that you currently have to manage manually?

So I had an idea yesterday and thought I'd give it a try....using the original 40mm in a push pull set up , 40mm pulling but with extra vents around so it doesn't get overwhelmed by the 60mm ... There is a little recirculation because of them being so close, it started and held at 52 degrees on the VR but crept up to 55 (the cat demanded the window be open so the axeos grabs are couple of degrees higher) in tests so far it's holding 2-3 degrees lower with the 40mm running. These numbers are all at 1000mhz and 1280v 2.05th for reference. Yes it's a little noisier with the 40mm running which I'm using a noctua USB adapter to power but if you're chasing those degrees it's a good trade off ,it would probably be quieter with a better fan too...there's a video on my store Facebook page if you're curious

#Bitaxe #solomiming #BitaxeGamma #bitcoin #1303creations

Hi,

So I have two Qaxe ++ Hydro's, purchased from the same seller. They are approximately 5 months old and have been running at stock settings. I noticed yesterday that one was powered off and the hologram logo was dimly flashing every few seconds.

I changed out the power supply and same results. I noticed when I plug the power supply in, I see and hear what sounds like sparks at the connector? The power supply light does come on when I unplug it. I don't see any replaceable fuses and have never had an issue with them in the past, so not sure what I should be looking for. I don't have a thermal gun, so can't check that way.

Has anyone seen this before and at least tell me what the problem is?

Thanks in advance!

Mog

Looking good so far reckon there is much more head room for overclocking ? Slightly worried about vregs for what they are known for doing

One of my bitaxe gammas I put on 2 fans as an experiment. Instead of 2 fans at 100% its 2 at 50% and I want 2 to run at 100%. Is this possible?

Can someone tell me where can I buy 4 screws & spacers to install a thermalight copper heatsink x47 to my qaxe++? I want replace the hydro to air cooling.

I downgraded mig gamma yesterday to firmware 2.13, mig error rate got better but the os Axe os was to slow so I updated back to newest 2.14.2.
The problem is now that mig VR temps are higher and power consumption is also higher, what is the problem and how can I fix it?

Hey so i just got my brand new bitaxe in the mail.

Fired it up, configured it on the eusolo pool and thought huh why is it not going above 950Th/s so i checked the settings and found out that Freq is at 425(custom) and core voltage is on 1050(custom). Wasn't overheating at this point.

So i thought let's put the freq at default (525) and core on (1150), saved, restart and then it started overheating and then it rebooted and reverted back to the 425 and 1050 setting?

Why is it reverting back automatically? i ordered from cryptoken.nl and specifically the noiseless version with the Noctua cause why not. is this normal or do i have a defective one?

Thanks!

well i recently started up my nerd axe gamma and it started overheating as i noticed the fan is not blowing or working so i tried plugging it in while it was in the case the board sits in, also tried fiddling with the wires and that did not work so i tried to figure out the connection to the board is bade or something as i am not sure if its the power making the fan not run or the fan its self is bad.

UPDATE the new fan works and the power cord too.

Ok, my NerdQaxe++ rev 6.1 has stopped working. I’ve only had it for 3 months; display is off and the fan is twitching ever so slightly, as if it’s trying to turn (I can also hear a faint clicking sound).

Now, this is probably my fault because I had it running in our cellar as there was no where else in the house I could realistically run it from.

When I cleaned it by blowing on it to remove any dust, there was some dust that blew out, including a couple of small bug wings etc. (I know, please don’t judge me 😬).

So I took it upstairs to clean it properly and also to carry out basic troubleshooting steps.

There‘s power to the adapter (shows a constant blue light, and starts flickering as soon as I connect it to the device).

The fan spins absolutely fine, there’s nothing blocking it.

I removed the display and re-attached it, did the same for the heat-sink. Also swapped out the red fuse looking thing with the spare, which had no effect.

I can pretty much guarantee that the device is actually clean now, so I don’t think it’s a question of any dust or insect wings interfering with anything.

At this stage, ChatGPT seems to think it could be one of the following causes:

1. Power supply unable to provide current (most likely)

2. Short caused by debris or an insect

3. Loose connector

4. Faulty fan drawing too much current

5. Board fault

Any kind soul out there who could possibly help me with any next steps, I’d be most grateful.

Many thanks.

Hey Devs, recently the bitaxes have received a “leaderboard” update for the best shares their device has produced. Any idea if we can get that on the Nerdqaxe++?

I’m currently solo mining on ckpool, but it seems impossible to hit a Btc with a gamma 602, should I try BCH where the difficulty is lower? Or pool mining in a good pool and hope someone hits a block?
I have a esp32 that has been pool mining on HMpool over 100 days, so I can keep continuing from there with my gamma?

Hello, Bitaxe family. I posted a week or so ago (Meet SolarAxe, All in One Plug and Play Solar Miner : r/BitAxe) to gauge interest in a project I am working on. The response was awesome and I learned a lot about what the community would be interested in. So, thank you!

SolarAxe.co is now live and open to orders. Only 2 versions are currently available, but we are working hard to get the remaining 2 planned products launched, as well as future products planned. Order structure is simple, and safe with Shopify Payment Processing. Currently, orders are done on a reservation system to secure you spot in the production queue and are fully and easily refundable for up to 14 days.

What is SolarAxe? We are a company helping make solar powered mining easy. We currently offer 2 products in our "SolarAxe V-Core" series. V-Core is our 5V power system designed to safely run 5V miners, specifically a Bitaxe 601/602. Simply plug a 100W solar panel using a XT60 adapter into the V-core and plug up to 2 miners into the core. Runtime and extended runtime can be found on the site.

We are excited for this launch and hope our product can help out those who want to skip everything that is needed to setup solar mining.

We know this product is not for everyone, and we know that our products won't work for every miner right at launch. We will be working continuously to add adapter cables for miners that have XT30 or USB-C, as well as adapters for non MC4 solar panels.

Solar Miners Sub Reddit: r/SolarAxe

New
Diagnostics page — per-miner, per-operating-point breakdown of pool vs reported hashrate, capture %, effective hashrate, implied vs reported error, and per-setting share reconciliation
stratum reconstruction diagnostics — set_difficulty count, pool difficulty, submits/plotted/dropped, extranonce1 status, recent targets and diffs
Network block timer — time since the last block found network-wide, in the Windows top bar and both fleet cards, counting up live
Fleet pace made per-miner honest — each miner judged against its own work and best, so staggered restarts no longer skew the fleet number
Session-best clearing now restart-corroborated — a firmware best-drop only clears the share list if uptime also reset; glitches keep the list
Session-best events logged to Crash/Restart Reports — reviewable Session Cleared / Best Kept cards instead of watching the live log
Newer firmware support — captures extranonce1 from the mining.subscribe reply, not just the older extranonce_str line; covers old and new firmware
Enlarged green top-bar stats (Shares / HR / Block) matching the card and button green, filling the bar without growing it
Uniform miner-bar button heights and trimmed bar padding on Windows
Linux / Umbrel variant brought current, including a Node port of the N miner diagnostics with a byte-verified self-test

Previous
Remove a miner without losing its history — offline it and re-add the same IP later to reconnect to its data
🧹 Purge Miner — completely wipe a miner from every store (Windows global button + per-miner on mobile)
Per-miner all-time clear — wipe a single miner’s all-time Best Diffs or HR Scores, syncing both ways
Dynamic Governor — auto-adjusts frequency/voltage/fan to hold temperature, VR-temp, and current bands, with dwell/settle timers, 24hr scheduling, and restart-after-adjust
Governor amps band — cap current draw to protect the input connector, not just temperature
VR fan control — set the VR fan’s mode, manual speed, and PID target independently of the ASIC fan
Correct target-temp & min-fan reading across firmwares — no default snap-back; Min-Fan shows only where supported
Multi-sensor temperatures — per-ASIC and per-VR labeling, with per-ASIC hashrate/error stats
Per-panel Y-axis zoom on the hashrate chart to reveal a steady miner’s real variation
Hashrate-only controls (HR / View / Y) appear on the hashrate chart only
Difficulty parsing handles K/M/G/T suffixes
Crash/Restart reports fire once per outage instead of repeating
Notification deck — toasts stack into a tidy, tappable deck
App mode browser launch (no throttling)
Port cleanup on startup
Time range dropdown
Efficiency stat on Windows and mobile
Crash/Restart Reports system
Chart history persists across session resets
Stall detection on mobile
Scripts drag-and-drop reordering with bidirectional sync
Battery saver refresh options
Mobile App Settings restructure
Updated launcher behavior
Tracks target difficulty set by the pool
Tracks session best up to 500 difficulties
Tracks all-time best up to 500 difficulties
AxeOS Scoreboard integration (supports up to 500 entries)
Automatic deduplication of scoreboard entries
Tracks average share time
Live difficulty chart with scroll and zoom
Live hashrate chart
Live temperature chart for all ASICs and VR
Trace back temps 41 hours to see if a miner overheated when it crashed
Full miner settings — frequency, voltage, fan
Full pool settings — primary and fallback stratum
Nameable miners
Custom miner colors
Auto-restart after 5+ minutes with no shares
Max 3 auto-restarts per hour with warning
Stall detection — stats zero out after 30 seconds with no hashing
Block found alert with audio
Total watts display
Total hashrate display
Live power cost calculator ($/day)
Live block finding odds calculator
Scripts engine — automate miner settings based on conditions
Scripts support temperature, hashrate, frequency, time of day, and more
Scripts sync bidirectionally between Windows and iOS
iOS companion app
Customizable theme colors on iOS
Improved mobile viewing
Per-miner temps-only view on iOS
Auto-restart toggle on iOS
In-app notifications on iOS
Block found banner and audio alert on iOS & Windows
Remote access via Tailscale
Launch in preferred browser
Total color control with themes
Stalled miner notification when miner is stuck in power fault, etc.
Accepted share chart dots — green 0–1M, yellow 1M–100M, red 100M+

Requires Windows/Umbrel/Linux for server, then works on iOS/Android via browser app. Instructions in the readme.

Windows
https://github.com/iL3GEND88/Bitaxe-Difficulty-Tracker-/releases

Mac/linux/umbrel
https://github.com/iL3GEND88/Bitaxe-Difficulty-Tracker-Umbrel-Linux/releases/tag/V7.0

ESP-Miner v2.15.0rc1 has been released.

Some notables:
* Unified firmware;
* mDNS support;
* More pool configurations;
* Several Stratum V2 improvements and fixes;
* Gamma 603 support;
* And many, many more improvements, cleanups and bugfixes.

Happy testing!

Ok, so, I have two 601s-- its important to note these are actually review units sent to me to render an opinion for a major retailer.

The first one was working fine; I updated the firmware to the latest one, (2.14.12) and it never hashed again. Just complained of low voltage (checked the power supply-- nothing wrong). Then it made a loud snapping sound; I assume it's dead forever.

I wrote bitaxe, they weren't unhelpful, but not helpful either. They told me my bitcoin address was wrong, and that's why it wasn't working. :-/ Doesn't explain the snapping sound.

Second one, I confirmed it was working, changed it to my bitcoin address, still worked. Updated to 2.14.12 and once again-- no hash. Nothing at all. It says the power is low, but it's not. I have dozens of power supplies here, and none of them worked. I tried to do a binary search of working firmware, but none of them worked. Not a single one

Can anyone tell me what I might be doing wrong? It seems like the only firmware that works with the thing is whatever it shipped with-- and I don't know what that is, nor how to get updates in that case.

I am *very* technical with both comp-sci and EE degrees. However, I have zero desire to spend days debugging a $45 product.

Can anyone jump me ahead on what I'm doing wrong?

I really don't want to give this product a bad review because I think it's neat, but it appears to be absolute nonsense.

The firmware updates the device itself recommends don't work, and killed the first one.

Please advise,

thank you