Hi,
Also I think you are looking for this in the wrong place, i suspect something different and has to do with memory allocation, like using broken FastMove, or something else.
I suggest to build the EXE with
RTL debug
dcu, only then you might get closer or finer look where the
exception is raised, this
exception is hardware one and should be easier to catch and locate as it is limited to illegal operation.