Overview
Uses the Microsoft DMO sys.dm_server_memory_dumps to look for memory dumps
https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-server-memory-dumps-transact-sql
Next Steps
It is recommended that you contact Microsoft support if you have issues with memory dumps, there are however, a few resources that you might find useful if you want to diagnose them yourself;
Blog post from Adam Saxton - https://blogs.msdn.microsoft.com/psssql/2012/03/15/intro-to-debugging-a-memory-dump/
Blog post from Pythian - https://blog.pythian.com/analyze-sql-server-stack-dumps/
SQLBits session on using Windbg - https://sqlbits.com/Sessions/Event6/Photograph_SQL_Server_Crash_Dump_Analysis
Suggested remediation action
Create a Powershell action that takes the file, copies it to another machine with Windbg installed so it can be analysed.
The following Help file entry will assist you in using parameters in actions; https://docs.sentryone.com/help/system-parameters
Default Settings
Runs every 5 minutes
Marked as Critical
Max Instance count set to 100
Set to Highlight under SQL Server memory in red
Will only run on SQL Server versions 10 and above.