There are multiple ways to get a crash dump.
One of the easy approach is to use “DebugDiag 2.0 Collection” tool to capture the dump.
If not already installed, you can get it from http://www.microsoft.com/en-ca/download/details.aspx?id=40336
or
http://blogs.msdn.com/b/chaun/archive/2013/11/12/steps-to-catch-a-simple-crash-dump-of-a-crashing-process.aspx
Check Launch DebugDiag section
you may need to use the "Run as Administrator" option to avoid errors during launch.
Open “DebugDiag Collection” tool
- When asked which rule type to choose, keep the bullet beside "Crash" and click NEXT
- For "Select Target Type" You can select the below option based on your requirement.
- If you need to get a dump of a process like owstimer.exe or iexplore.exe or anything not related to IIS, you should probably select "A specific process."
- If you have a w3wp.exe that is crashing and you know which Application Pool it is associated with, you should probably go with "A specific IIS web application pool."
- If you have a w3wp.exe that is crashing and you don't know which AppPool it is associated with, you should probably go with "All IIS/Com+ related processes."
- Leave everything set to the default setting in the Advanced Configuration for now. Just click NEXT.
- Select Dump Location and Rule Name.
- Activate the rule when you're ready for the tool to start monitoring the process for a crash.
- Click Yes on the Debug Dianostic Tool Window where it points the "Symbol Search Path for Debugging"
- When the crash occurs, there will be dump file created on the location specified above.
