Skip to content

Commit e67e039

Browse files
authored
update as Aarti
1 parent f4ad6df commit e67e039

File tree

1 file changed

+6
-15
lines changed

1 file changed

+6
-15
lines changed

support/developer/webapps/iis/site-behavior-performance/process-termination-crash.md

Lines changed: 6 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Troubleshoot a Process Crash in an IIS Application Pool
33
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
55
ms.custom: sap:Site Behavior and Performance\Process termination (crash)
66
ms.reviewer: khgupta, v-sidong
77
---
@@ -56,18 +56,9 @@ Take note of the following fields:
5656

5757
## Data collection
5858

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.
6060

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
7162

7263
To take crash dumps using Debug Diagnostic Tool, follow these steps:
7364

@@ -103,7 +94,7 @@ To take crash dumps using Debug Diagnostic Tool, follow these steps:
10394

10495
:::image type="content" source="media/process-termination-crash/userdump-count-column.png" alt-text="Screenshot of the Userdump Count column.":::
10596

106-
#### ProcDump
97+
### ProcDump
10798

10899
ProcDump is a simpler way to take a memory dump of a process. To take crash dumps using ProcDump, follow these steps:
109100

@@ -145,7 +136,7 @@ If the error code is `C00000FD`, and you aren't able to take a memory dump, foll
145136
Procdump -u
146137
```
147138
148-
#### Windows Error Reporting
139+
### Windows Error Reporting
149140
150141
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.
151142
@@ -155,7 +146,7 @@ To take crash dumps using Windows Error Reporting, follow these steps:
155146
1. Check the directories mentioned in the Windows Error Reporting events.
156147
1. Locate files with the extension `.mdmp` (mini dump) or `.hdmp` (heap dump) in the mentioned directories.
157148
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.
159150
- If you don't have them, follow these steps to set up WER:
160151
161152
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

Comments
 (0)