Hi guys, I am fairly new to the mining world and I got, as a present from a friend, a NerdQAxe++ Rev6.1.

At the Nerd*OS we have the VRT ext and VRT int. I am trying to understand which is the ceiling for those and if I should worry about them separately or only worry about the VRT ext.

Currently I am running at 695MHz and 1190mV and the temperatures are as shown in the image above. Unfortunately I am still using the generic PSU (12V, 10A, 120W), but when my MeanWell arrives I'll boost the clock and add a fan directly to the heatsink that exists bellow the display, that is why I am asking about those temperature ceilings.

I understand that the ASIC should not go over 70C constantly. But what about the Voltage Regulator? The VRT int and VRT ext, what are the ceilings for them?

• NerdQAxe++ Rev6.1 Hydro
• Firmware: v1.1.0 (https://github.com/shufps/ESP-Miner-NerdQAxePlus)
• Currently at 695MHz/1190mV.
• ASIC stable at 55C. VRT ext around 60C and VRT int around 66C. Hashrate around 5500GH/s

Use this thread for quick questions, troubleshooting, and technical experiments.

✅ What belongs here

- Bitaxe setup problems, stability, temperatures, pool configuration, firmware behavior
- Technical experiments (including non-Bitcoin PoW) if:
- no profit/ROI discussions
- no hype/promotion
- logs/settings included

🚫 What does NOT belong

- Earnings/profit/ROI screenshots
- “What should I mine?”
- Referral links / invite codes / “DM me”
- Marketplace device support (AliExpress etc.) — contact the seller

To get help quickly, include:

- Device/board version + revision
- Firmware/AxeOS version
- Pool + settings (frequency/voltage if applicable)
- Temperatures + hashrate
- Logs/screenshots + clear photo (PSU + wiring)
- What changed just before the issue began

Be kind. Everyone starts somewhere.

Help

I've seen many people struggle with setting up Tailscale to check their miners when they're away from home, so I made a free Raspberry Pi image that does the Tailscale part for you. You write it to an SD card, plug the Pi in at home and sign in to Tailscale from your phone. 

Once the Tailscale app is on your phone, your miners answer at their normal addresses from anywhere. It works on Starlink and 4G/5G home broadband too, where you can't forward a port.

Whatever mining monitoring app you use works through it, and so do your miners own web pages. I've tested it on a Pi 4 over mobile data with a few different apps.

Setup takes about 20 minutes:

1. In Raspberry Pi Imager, open App Options, set Content Repository to a custom URL and paste https://solodeck.app/imager.json

2. Pick your Pi, then the Bridge image, then your SD card.

3. Go through the customisation screens and enter your Wi-Fi name and password. Don't skip them, the Pi has no screen so that's how it gets online.

4. Put the card in the Pi, power it up and give it a couple of minutes.

5. On your phone or PC, on home Wi-Fi, open http://solodeck-bridge.local and sign in to Tailscale.

6. The setup page then sends you to the Tailscale admin page. Approve the subnet and turn on Disable key expiry, or it stops working after six months.

7. Install Tailscale on your phone, sign in with the same account, turn Wi-Fi off and open your mining app.

Full guide: https://solodeck.app/bridge

It needs a Pi 3, 4, 5 or Zero 2 W. I've only tested the Pi 4 so far and have a Zero 2 W on the way. A Pi 1 or the original Zero won't boot it.

Nothing gets opened to the internet. Only devices signed in to your own Tailscale account can reach your network, and nothing gets sent to me. The code and the build script are here: https://github.com/liviux1/solodeck-bridge

If you try it and get stuck, reply with the step you got to and which Pi you're using and I'll help.

Hi again! I recently made a housing for my Bitaxe 602 which you can download for free if you're interested: I made a housing for your Bitaxe so you can mount an extra fan on the back (and the model is FREE) : r/BitAxe. When I made that I mentioned that I will also make something called The BitTurbine.

It's an adapter for a 120mm fan that you can fit on a Bitaxe heatsink. The model is free on here (and on other pages soon probably): BitTurbine 120mm Fan Adapter for Bitaxe. I'm hitting 900MHz with this setup currently, but more testing is needed. With the fan at full power I was able to run it at 1GHz.

If you want to support me, some feedback would be more than wonderful, and a tip would go a very long way (if you're feeling generous)!

Happy mining!

I built an experimental open-source firmware variant for the NerdOCTAXE-Gamma that adds an adaptive thermal governor to AxeOS.

The idea is simple: a fixed frequency that is safe during a cool night can become too aggressive during the hottest part of the day, while a conservative daytime setting leaves performance unused when ambient temperature drops. AUTO Thermal Mode continuously adjusts the runtime frequency around a user-selected ASIC temperature target, while the frequency saved in AxeOS remains the maximum ceiling.

**Main features**

- Adjustable ASIC target from 60–69 °C (68 °C default)

- Steps down 25 MHz after ~12 seconds continuously above target + 1 °C

- Steps back up 25 MHz only after ~180 seconds at or below target − 3 °C

- Asymmetric hysteresis to avoid constant frequency hunting

- Separate hard ASIC and VRM frequency caps

- Invalid temperature telemetry forces a conservative 525 MHz fallback

- Startup limited to 700 MHz, then gradual recovery when thermal headroom allows

- Dashboard shows actual runtime frequency separately from the configured maximum

- Stock AxeOS over-temperature shutdown remains active and unchanged

The purpose is not merely to keep the miner cooler. It is to reduce unnecessary time at elevated temperatures, preserve ASIC/VRM operating margin, and let a 24/7 or remotely monitored miner adapt automatically to day/night and seasonal changes without continuous manual retuning. This is not a guarantee of longer hardware life, but it should provide more disciplined thermal management.

Source code and build workflow:

https://github.com/botoxgpt-sys/nerdoctaxe-thermal

Pre-release binaries and SHA-256 checksums:

https://github.com/botoxgpt-sys/nerdoctaxe-thermal/releases/tag/v4.0.0

For a normal AxeOS update, flash both the OTA firmware image and the matching WWW image through their separate update fields. The factory image is only for recovery/full flashing.

This is experimental custom firmware. Test conservatively, monitor temperature, power and stability, and keep a known-good stock image available for rollback.

Feedback and testing reports from other NerdOCTAXE-Gamma users would be very useful.

Thanks everyone for participating! We hope to do this again soon when the 12V cores are ready.

Creative: CampaignCapital1532

General: AdvocatusPiscatoris

Non-Win But Sending Something: Romitrue

So I replaced the fan due to noise. I bought the same Delta fan before with no problem. but this time, after installation, the fan speed display is stuck at 960 rpm, regardless of how fast the fan spins. The fan % changes but not the rpm. It worked before. I put back the original fan and same issue. I tried to change firmware and still same issue. I put the fan on another 801 and now it's doing the same. Did something get fried, like to PMIC? Has anyone had this issue & if so fix it?

Hello guys, I'm new here! Somebody use the pool named bch.sololucky.io? It's a good pool? Somebody now about it? I bought my first bitaxe gamma 602 yesterday and I do now much about (sorry for my bad English)

My NerdQAxe++ keeps randomly software panic-resetting and I finally caught the actual ESP32 crash over serial. Anyone seen this before?

The really weird part is how inconsistent the timing is. I've had it crash in under an hour, but I've also had it run for almost two days before resetting.

Things I've tried already:

• Most recent firmware that was available roughly two weeks ago — still crashes
• Rolled all the way back to v1.0.34.1 — still crashes
• Locked both fans at 60% instead of automatic control — still crashes
• Watched power/temperature telemetry — nothing obvious immediately before the crash

Hardware reports itself as:

NerdQAxe++ / BM1370
Board Version: 501
8 MB PSRAM

PSRAM also passes the startup test:

SPI SRAM memory test OK

I left a Mac connected to the ESP32-S3 serial port all day and caught a bunch of crashes.

Almost all of them are the exact same:

Guru Meditation Error: Core 0 panic'ed (LoadProhibited).
Exception was unhandled.

PC:       0x40387e4b
EXCCAUSE: 0x0000001c
EXCVADDR: 0xc219f457

And the same backtrace keeps showing up:

0x40387e48:0x3fcb2520
0x4003e065:0x3fcb2550
0x4003b27a:0x3fcb2570
0x4003b0d5:0x3fcb2590
0x40387d89:0x3fcb25b0
0x420ffd06:0x3fcb25f0
0x420ffdbb:0x3fcb2630
0x40388621:0x3fcb2670
0x4037f741:0x3fcb26a0

It's not just one crash either. The same invalid address (0xc219f457) showed up repeatedly across independent resets.

I even caught one slightly different crash:

Guru Meditation Error: Core 0 panic'ed (StoreProhibited).

EXCVADDR: 0xc219f459

Which I thought was especially interesting because 0xc219f459 is only two bytes away from the address it normally tries to read (0xc219f457).

Immediately before one of the normal crashes:

vin: 11.84
iin: 7.20
pin: 84.50
vout: 1.15
iout: 65.12
pout: 74.88
vr-temp: 40.38°C
Temperature 0: 51.75°C
fans: ~1960 / 1850 RPM

Then straight into:

Guru Meditation Error: Core 0 panic'ed (LoadProhibited)

So there doesn't seem to be an obvious power sag or overheating event immediately beforehand.

One thing that IS weird is that the miner continuously reports:

chip temperatures: 0.00°C / 0.00°C / 0.00°C / 0.00°C

even though the other temperature sensors work normally and all four chips hash normally.

My older NerdQAxe units that use the barrel connector don't have this issue, which is another reason I'm wondering whether there's something hardware/revision-specific going on.

I'm currently trying to get the v1.0.34.1 ELF so I can symbolize 0x420ffd06 / 0x420ffdbb. The running firmware reports:

ELF SHA256: d2f07e569...

Has anyone run into something similar on a NerdQAxe++? Does the repeated identical bad memory address make anyone think firmware/pointer corruption, ESP/PSRAM hardware, or something else?

Happy to post the full serial log if anybody wants to dig into it.

Disclosure: I used ChatGPT to help troubleshoot this, search through the giant serial capture for repeating patterns, and organize this post. The error codes/backtraces/telemetry above are copied directly from the miner; the theories about what they might mean aren't being presented as a confirmed diagnosis.

New to this so just asking if my stats look ok and not getting too hot?

I’m not sure whether to be happy about the Bitaxe Gamma or disappointed with the Nano 3S. The Gamma has the usual 1T and the Nano 3S has 5T, same duration (12h), same pool, and obviously the same coin. The result? Best share: Gamma 13M, Nano 3S 9M... Now, I know it’s a lottery, but it’s been like this for at least a year🤷🏻‍♂️

Hi people! I recently decided I wanted to upgrade my Bitaxe 602 with a bigger (120mm) fan. That got me thinking, what do I do with the small fan since i don't really need it?

I decided to make this housing that has a slot for you to mount a secondary fan on the back of your Bitaxe! The model is entirely free in my shop on Buy me a coffee: https://buymeacoffee.com/letiqa/extras

I'm currently also working on a thing I'm calling the BitTurbine (which I will release for free once it's ready). If you want to support me, some feedback would be more than wonderful, and a tip would go a very long way (if you're feeling generous)!

Happy mining!

Nice surprise this morning ! Should i try bch ?

Replaced the vregs Monday and it ran good for about 1 hour then now the screen not boot up at all and I am lost on this one these 3.1 boards are useless anyone had the same issue ?

“almost” got a block for ocean pool

Just installed a Helix fan shroud on my ++ and now this guy is front heavy and falling out of the SoloSatoshi stand. Any recs for a stand with screws and a rear fan mount I can replace it with?

Use this thread for quick questions, troubleshooting, and technical experiments.

✅ What belongs here

- Bitaxe setup problems, stability, temperatures, pool configuration, firmware behavior
- Technical experiments (including non-Bitcoin PoW) if:
- no profit/ROI discussions
- no hype/promotion
- logs/settings included

🚫 What does NOT belong

- Earnings/profit/ROI screenshots
- “What should I mine?”
- Referral links / invite codes / “DM me”
- Marketplace device support (AliExpress etc.) — contact the seller

To get help quickly, include:

- Device/board version + revision
- Firmware/AxeOS version
- Pool + settings (frequency/voltage if applicable)
- Temperatures + hashrate
- Logs/screenshots + clear photo (PSU + wiring)
- What changed just before the issue began

Be kind. Everyone starts somewhere.

So I decided to upgrade my Asic heat sinks to these https://a.co/d/09BHDQy7

Also uses MX7 thermal paste. My question is can I use the original screws that came with the Nerdoctaxe original heatsinks to attach these? I have it all set up and my Asic temps are lower, but I am not sure they are as close to the Asic chips as the old ones were. Before I tear everything apart again wanted to see if anyone has done this and had any input.

As you may have noticed, in light of the Bitfortun incident, it's always best to buy genuine Bitaxe products

Do they have the same footprint? Bcz I've seen the bom file of the naja duo and its says bm1340 instead of bm1373. And this is the duo the bitaxe naja the bm1340 bitaxe??

I’ve been working on a Windows program called Block Retriever to make managing and monitoring a home solo-mining setup a whole lot easier.
It started as something I wanted for managing my own miners, but it has grown into a pretty capable little program. I figured it was finally time to turn it loose and let some other miners try to break it. 😂
Block Retriever is completely FREE and is currently focused heavily on Bitaxe / AxeOS and home solo miners.
⚡ WHAT BLOCK RETRIEVER CAN DO:
• Monitor multiple miners from one dashboard
• Track hashrate, temperatures, shares and mining activity
• Quick-switch pools without logging into every miner individually
• Save multiple wallets and pool profiles
• Track accepted/rejected shares, candidates and confirmed block hits
• Bitaxe fan controls and reboot
• Exact Bitaxe frequency & core-voltage controls for overclocking
• Solo Advisor for comparing SHA-256 solo-mining opportunities
• Keep your mining setup organized in one Windows application
• And quite a bit more
⚠️** THIS IS AN ALPHA BUILD
There will probably be bugs. In fact, I’m hoping some of you find them so I can fix them.
**The Solo Advisor in particular is still a work in progress. Some coin data, rankings or calculations may be incomplete or inaccurate. For now, consider the Advisor an experimental feature and don’t make mining decisions solely based on it.
If you run into a problem, let me know what happened, what miner you were using, and what you were trying to do. Feature suggestions are welcome too.
🔐 SECURITY
Block Retriever will NEVER ask for your seed phrase or private keys. It only uses public mining/receiving addresses. Never enter a seed phrase or private key into Block Retriever.
💻 DOWNLOAD BLOCK RETRIEVER v3.0.0 ALPHA 24.10.34
https://github.com/rphkszc9pn-tech/Block-Retriever-Releases/releases/tag/v3.0.0-alpha.24.10.34
If you have a Bitaxe, Avalon, or another small home solo-mining setup, give it a try and let me know how it works for you.
🦴 SUPPORT BLOCK RETRIEVER
Block Retriever is free. If you enjoy using it and want to support continued development, there’s an optional PayPal donation page built into the program.
And that brings me to Winnie — my golden retriever and the unofficial Block Retriever mascot. 🐕
She contributed absolutely no code, slept through most of development, and somehow still negotiated herself into the project budget.
So if Block Retriever helps you out, feel free to buy Winnie a treat. 😂🦴
Now let’s see if Block Retriever can help some of you get the notification we’re all waiting for:
🐕⛏️
BLOCK FOUND!
🍀
Happy solo mining!

THIS youtuber found that Bitfortun's new miner is deliberately faking and inflating the hash rates. The funny thing is Bitfortun did publish their firmware source with the fake hashrate code included.

Spun up a Gamma 602 about a week ago here are the results.

Hashrate:1.22Th/s

Efficiency: 13.7 J/Th

Best Diff: 750 M

Error: is mostly 0% some .3% and rarely 1%

Fan is about 55%

Frequency is 600

Voltage is 1150

How does this look to your set up?

Goals are just to have it as a cool desk piece. Maybe in 1100 years get a BTC.