madmax instability

[gWOLF3]

across many different machines (and users) madmax plotting will randomly fail (usually on phase 3) after hours of successful plotting.

i see many other users reporting here on the issues but they have gone unanswered.

i've seen some comments involving bottlenecking xmp memory speed but this seems silly as it will also arbitrarily lower plotting speed.

another solution is to simply wrap madmax process in something like PM2 to restart it on failure...

In light that many people have experienced this issue and made note of it - I would like to know if there are plans to formally address this issue? Or at least provide some official guidance as to how to best avoid random crash scenarios without handicapping plot speed.

Thanks - and nice work on this project; congrats on being incorporated into the official chia repo

[risner]

I'm running it 24/7, and I haven't had this issue. Can you tell me what error happens when it fails? Segmentation violation? Core dump?

[riktam]

I have this too windows 10:

Faulting application name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60e98444
Faulting module name: chia_plot.exe, version: 0.0.0.0, time stamp: 0x60e98444
Exception code: 0xc0000409
Fault offset: 0x000000000011141d

The Fault offset and the exception code is always the same.

[risner]

Looks like that exception code is associated with issues in windows. Things like corrupt Windows registry, virus/malware present, disk corruption due to improper shutdown, or corrupt system files.

I don’t use Windows any more, so I couldn’t tell you how to troubleshoot. But this link went over some basics:
https://www.fileinspect.com/blog/fix-windows-10-error-0xc0000409/