We probably need to get a service request opened for this to debug it further. In general, AMI models can be somewhat problematic because they are DLLs and since these DLLs are running inside of HyperLynx, if the model crashes, it can cause HyperLynx to crash. We're working on a new implementation that will isolate the AMI model from HyperLynx so if it crashes, HyperLynx will keep running but that won't be available till our next release. It sounds like a different issue here though, and we need to investigate.
Would you mind opening an SR?
I opened a SR upon your suggestion. The problem was confirmed and will be fixed in next release.
Thanks for submitting the SR so we could identify the issue and get it resolved.