Dumps after CHECKDB error
Defragmenting indexes when those indexes are stored on Flash/SSD is close to pointless.  I'd recommend performing the reindex far less frequently.  See Paul's answer here regarding page density and fill factor for mitigating the effects of index fragmentation.

Updating statistics, on the other hand, will provide important clues to the query optimizer.  If auto-update-stats is disabled for the given database, ensure you are updating statistics via a nightly job.  

Ensure you run DBCC CHECKDB as often as possible to ensure corruption does not negatively affect your RPO.  You may consider offloading DBCC CHECKDB to a non-production instance.  This consists of automated backup-and-restore to the non-production instance, then automatically running DBCC CHECKDB on that non-production instance.  You'll probably need to license the machine where you run DBCC CHECKDB since it would be dealing with production data, however I'd check with your Microsoft rep to be certain.

If you're seeing SQL Server creating memory dumps, that indicates a problem with SQL Server that should be brought to the attention of Microsoft Tech Support - they may either have a hotfix available to resolve the issue, or they may offer some further advice about how to resolve that issue.  The problem may indeed be a bug that needs to be fixed.