You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/developer/webapps/iis/site-behavior-performance/process-termination-crash.md
+6-15Lines changed: 6 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Troubleshoot a Process Crash in an IIS Application Pool
3
3
description: This article helps identify a process crash and provides methods to collect and analyze data for the crash.
4
-
ms.date: 02/27/2025
4
+
ms.date: 03/04/2025
5
5
ms.custom: sap:Site Behavior and Performance\Process termination (crash)
6
6
ms.reviewer: khgupta, v-sidong
7
7
---
@@ -56,18 +56,9 @@ Take note of the following fields:
56
56
57
57
## Data collection
58
58
59
-
The first thing you need to do is to understand whether you need a memory dump. Windows has a feature called [Windows Error Reporting](#windows-error-reporting) (WER) that collects information automatically for you.
59
+
To determine if you need a memory dump, start with the [Windows Error Reporting](#windows-error-reporting)(WER) feature that automatically collects information for you. Check the event logs related to WER to see if the information provided is sufficient to resolve the issue. If the information is sufficient, additional memory dumps aren't necessary. If it isn't, use the [Debug Diagnostic Tool](#debug-diagnostic-tool) or [ProcDump](#procdump) to collect crash dumps as described in the next section.
60
60
61
-
To determine if you need a memory dump, locate the event logs regarding WER and check if the information is sufficient to solve the issue.
62
-
63
-
- If yes, you don't need a memory dump.
64
-
- If not, jump to the [How to collect a crash dump](#how-to-collect-a-crash-dump) section.
65
-
66
-
### How to collect a crash dump
67
-
68
-
To collect a crash dump, you can use tools like [Debug Diagnostic Tool](#debug-diagnostic-tool), [ProcDump](#procdump), or [WER](#windows-error-reporting).
69
-
70
-
#### Debug Diagnostic Tool
61
+
### Debug Diagnostic Tool
71
62
72
63
To take crash dumps using Debug Diagnostic Tool, follow these steps:
73
64
@@ -103,7 +94,7 @@ To take crash dumps using Debug Diagnostic Tool, follow these steps:
103
94
104
95
:::image type="content" source="media/process-termination-crash/userdump-count-column.png" alt-text="Screenshot of the Userdump Count column.":::
105
96
106
-
####ProcDump
97
+
### ProcDump
107
98
108
99
ProcDump is a simpler way to take a memory dump of a process. To take crash dumps using ProcDump, follow these steps:
109
100
@@ -145,7 +136,7 @@ If the error code is `C00000FD`, and you aren't able to take a memory dump, foll
145
136
Procdump -u
146
137
```
147
138
148
-
#### Windows Error Reporting
139
+
### Windows Error Reporting
149
140
150
141
Windows Error Reporting is a built-in facility in Windows designed to collect information on issues that Windows can detect, such as application faults, kernel faults, and unresponsive applications, and report this information to Microsoft.
151
142
@@ -155,7 +146,7 @@ To take crash dumps using Windows Error Reporting, follow these steps:
155
146
1. Check the directories mentioned in the Windows Error Reporting events.
156
147
1. Locate files with the extension `.mdmp` (mini dump) or `.hdmp` (heap dump) in the mentioned directories.
157
148
158
-
- If you have these dump files, open a support ticket and upload them.
149
+
- If you have these dump files, provide them to Microsoft support if you create a support ticket.
159
150
- If you don't have them, follow these steps to set up WER:
160
151
161
152
1. Open the Windows Registry Editor (**regedit.exe**) and locate the key **HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps**. If this key isn't available, create it.
0 commit comments