Capturing in-memory OLTP transaction aborted errors in SQL Server

In one of my SQL Server 2016 Enterprise instances, sp_BlitzFirst is reporting hundreds of aborted transactions per second in one of my in-memory OLTP databases. I've set up error logging with try/catch for all procedures in the DB but they've caught nothing yet. Similarly, an extended event set up to capture errors isn't showing anything related to aborted transactions. The sys.dm_xtp_transaction_stats and sys.dm_os_performance_counters DMVs only seem to provide a total number of transactions aborted but don't provide details regarding the procedure(s) causing the errors. It's probably an error related to the ones listed in this MS doc, but I have no way of knowing which one at the moment: https://learn.microsoft.com/en-us/sql/relational-databases/in-memory-oltp/transactions-with-memory-optimized-tables?view=sql-server-ver15#conflict-detection-and-retry-logic Is there any way to capture this type of error?