w3wp had stopped working during profiling IIS application

Symptoms:

When getting a snapshot, the w3wp process was stopped and the snapshot could never be finished.

Cause:

IIS monitors the health of the worker process for your application pool to ensure that it is responding to requests. When you press the Get Snapshot button in dotMemory, the profiler starts to collect application data and might slow down your application. As a result, the worker process might not respond in time, and IIS terminates the process.

Solution:

Please disable Worker Process Pinging for an Application Pool or change the maximum response time. How to do it you can read in Error: Web site worker process has been terminated by IIS article.