The easiest way to check if the checksum are altered is to compare the bin, if the OS part have some corrections it might be the issue. They might have changed the start-end points of checksum calculation.

Still interested to see the bin in its corrupted state. Can you just save it ignoring the checksum message.

As a last resort try reading the pcm on a bench. If there is some ground issue or noise there, it can cause that kind of behaviour.