It's hard to comment on this without seeing your source code.
Does it make sense to you that the crash keeps looping? Is the COM method that raises the crash called repeatedly? E.g. by timer or something?
Generally structured exception handling works like this: When a crash occurs, the nearest try..except block gets activated. If the try..except block resolves the exception, the thread continue execution directly after the try..except block. Otherwise, the next nearest try..except block gets activated etc. madExcept just reports the crashes, madExcept does not really has much influence on where the thread continues execution. It's more your code that is reponsible for that.
The Com Server gets an Access violation.
Without MadExcept the Com Client gets an "External Exception" once.
So i would expect MadExcept to send a bug report for the Access Violation.