Thanks for the updates!
The coredump points to the laswp MAGMA function, which seems to trigger the illegal memory access, and is called by linalg_inv.
@xwang233 has been working with others on using cuSOLVER instead of MAGMA (e.g. as we’ve seen such memory violations in MAGMA before), but based on this comment batched inputs seem to still call into MAGMA for performance reasons.
Are you seeing the memory violation only, if the exception would have been caught?