Quote from: RemiusRock on July 20, 2022, 07:31:38 PM

last lines of the logs:
-INFO - 22:22:31.469: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #455
-INFO - 22:22:32.047: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:493) Found next block after skipping 571124bytes
-INFO - 22:22:34.360: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #460
-INFO - 22:22:34.360: (e:\users\goat\code\armory3\cppforswig\databasebuilder.cpp:281) parsed block file #467

The blk.dat files can contain other data aside from blocks like orphan/stale blocks so this may not be the issue.

But if you want to check if it is Bitcoin's blockchain at fault, you can try to run Bitcoin Core with -reindex to see if there's some corruption in your blockchain.
It will take a while to finish but it will not re-download the blockhain.