For the record, there is nothing to "click" here - the daemon Actiniumd crashes, and does not post crash information in debug log. The software is not acting normally, it is crashing / quitting. This is not an annoyance; rather, the software is not functioning at all. Just thought I would further clarify, I thought it was clear in the original bug report.
And again, this is a Segwit-enabled tag, with no existing blockchain. This happens on initial sync. This also happened with an existing chain.
Following your instructions, and the FAQ instructions, poses the same problem: the software still crashes, it is still unusable.
Attempting to load with bootstrap.dat, Actiniumd still continues to crash at 64521 height reliably.
Please see the bug report I posted, and let me know if there is anything further I can try / debug. I am competent and willing, do not fear using technical language or tools.
I did not originally notice any instructions regarding this situation, thus my post. I do see now the FAQ entry "My wallet is crashing with a weird message!" but I did not notice because it was not the error message, I am not expecting to look for "weird message" for this issue. Considering the software will not work with the live chain at all (at least on my platform), this seems serious enough to warrant a larger notification surface than the last "FAQ" entry, or figuring out what anomaly is present here.
I know that there is no "click" in daemon. I was simply writing for all possible cases (daemon, GUI).
Also, please, try to start the daemon without Actinium.conf and all the flags set I gave you in the example.
I had the same issue on one of my servers and it helped to sync the chain.
Of course it is a segwit-enabled tag, but as I said, there were mining pools that activated the SegWit option (in their pool software, YIIMP, which has nothing to do with Actinium) and this provoked generation of blocks with a different "magic".
The FAQ is available in the Release Notes, in our Discord, and as a separate Wiki entry. I think this is enough to make the information as broadly available as possible.
Also, there is always a possibility to open an Issue on GitHub.