Block checksum mismatch and Access Violation Errors

[BytePetter]

Describe the issue

Block checksum mismatch. Yes my hardware is fine.

What behavior did you expect?

I expected for the software to simply continue from the latest valid block checksum and restart from there. I instead just got additional block checksum mismatch errors at the same file when trying to restart the app. I pruned the blockchain to be 10GB big. I tried -reindex-chainstate, but this is just deleting the content of the chainstate folder and makes the app crash with an Access Violation error (0xc00000005) during splash which is not logged in the debug.log, but rather in the eventlog of windows.
Trying -reindex instead makes the app to verify the whole blockchain from start again, at which it is just a matter of time until the problem reappears again.

How reliably can you reproduce the issue, what are the steps to do so?

Try to make a 10GB pruned blockchain. Wait for the error to appear.

What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)?

V22, official website.

What type of machine are you observing the error on (OS/CPU and disk type)?

Windows 10, CPU shouldn't matter.

Can't provide debug.log info, as all the interesting parts were already deleted somehow. Probably because they got rotated away by my current attempt.