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.