Skip to content

Commit e2d3629

Browse files
authored
Update Dumpchk usage instructions and formatting
1 parent 2b9a80a commit e2d3629

1 file changed

Lines changed: 17 additions & 33 deletions

File tree

Lines changed: 17 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Use Dumpchk.exe to check memory dump file
33
description: Describes how to check a memory dump file by using Dumpchk.
4-
ms.date: 01/15/2025
4+
ms.date: 03/10/2025
55
manager: dcscontentpm
66
audience: itpro
77
ms.topic: troubleshooting
@@ -18,45 +18,29 @@ _Original KB number:_   156280
1818

1919
## Summary
2020

21-
Dumpchk is a command-line utility you can use to verify that a memory dump file has been created correctly. If a memory dump file is corrupt, it cannot be analyzed in a debugger. Using dumpchk to verify a dump file is in a good state is helpful as it will save time and effort in uploading corrupt dump files to be analyzed by support professionals. Dumpchk does not require access to symbols.
21+
Dumpchk is a command-line utility you can use to verify that a memory dump file was created correctly. If a memory dump file is corrupt, it can't be analyzed in a debugger. Using Dumpchk to verify a dump file is in a good state is helpful. It saves time and effort in uploading corrupt dump files to be analyzed by support professionals. Dumpchk doesn't require access to symbols.
2222

23-
Dumpchk is part of the Windows Debugging Tools. There are two versions of the Windows Debugger.
23+
Dumpchk is part of the Windows Debugging Tools. There are two versions of the Windows Debugger. To use Dumpchk, you must install the version of the Windows Debugging Tools included in the [Windows SDK](https://developer.microsoft.com/en-us/windows/downloads/windows-sdk/):
2424

25-
You must install the version of the Windows Debugging Tools included in the Windows SDK - [Windows SDK - Windows app development | Microsoft Developer](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper.microsoft.com%2Fen-us%2Fwindows%2Fdownloads%2Fwindows-sdk%2F&data=05%7C02%7CWarren.Williams%40microsoft.com%7C50935613ca604985339808dd5bdf9a6a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638767738151340942%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=bFHDAUD4S%2Fr83YtkM47ejDZryVRp2VLfjioX1txssPI%3D&reserved=0).
25+
1. Download the SDK installer.
26+
2. Launch the installer, and then select **Windows Debugging Tools** with other components that you would like to install.
27+
3. After the installation completes, dumchk.exe is in the directory that you installed the Windows Debugging in. Use the version that matches your hardware platform.
2628

27-
1. Download the SDK installer
29+
When Dumpchk runs, it displays some basic information from the memory dump file, then verifies all the virtual and physical addresses in the file. There are many symbol errors if a symbol path isn't specified. Those errors can be ignored as we're checking the dump file for corruption. Dumpchk reports any errors that are found in the memory dump file.
2830

29-
1. Lauch the installer and select "Windows Debugging Tools" and anything else you would like to install
31+
If there's an error during any portion of the output displayed, the dump file is corrupted, and analysis can't be performed.
3032

31-
1. After the installation completes, dumchk.exe will be in the directory that you installed the Windows Debugging in. Use the version that matches your hardware platform.
32-
33-
When Dumpchk runs, it displays some basic information from the memory dump file, then verifies all the virtual and physical addresses in the file. You will see a lot of symbol errors if a symbol path is not specified but those can be ignored as we are checking the dump file for corruption. If any errors are found in the memory dump file, Dumpchk reports them.
34-
35-
If there is an error during any portion of the output displayed above, the dump file is corrupted, and analysis cannot be performed.
36-
37-
When dumpchk is finished it will display the stop code and any parameters.
38-
39-
40-
```
41-
BUGCHECK_CODE: 1e
42-
43-
BUGCHECK_P1: ffffffffc0000420
44-
45-
BUGCHECK_P2: fffff8004dbab02a
46-
47-
BUGCHECK_P3: 0 BUGCHECK_P4: fffff8003a6d5f20
48-
49-
SYMBOL_NAME: nt_symbols!72291DF0104D000
50-
51-
PROCESS_NAME: ntoskrnl.exe
52-
53-
IMAGE_NAME: ntoskrnl.exe
33+
When Dumpchk finishes, it displays the stop code and some parameters.
5434

35+
```output
36+
BUGCHECK_CODE: 1e
37+
BUGCHECK_P1: ffffffffc0000420
38+
BUGCHECK_P2: fffff8004dbab02a
39+
BUGCHECK_P3: 0 BUGCHECK_P4: fffff8003a6d5f20
40+
SYMBOL_NAME: nt_symbols!72291DF0104D000
41+
PROCESS_NAME: ntoskrnl.exe
42+
IMAGE_NAME: ntoskrnl.exe
5543
MODULE_NAME: <Module Name>
56-
5744
FAILURE_BUCKET_ID: <Bucket Id>
58-
5945
FAILURE_ID_HASH: {029f6661-9c67-6d47-23e5-a0398183d06e}
60-
6146
```
62-

0 commit comments

Comments
 (0)