Dumpchk Windows Server 2012



-->

Aug 01, 2016 Hi Mussa, Your original PowerShell statement is on the right track, however, you need to understand that disk space won't be reclaimed unless you also use the '-Remove' parameter. Apr 27, 2012 Put a check mark in the 'Write an event to the system log' box. Put a check mark in the 'Send an administrative alert' box. Uncheck the 'Automatically restart' box. In the Write debugging information section, choose: Small memory dump (64 KB) Set the Small dump directory to:%SystemRoot% Minidump.

Start here for an overview of Debugging Tools for Windows. This tool set includes WinDbg and other debuggers.

Install Debugging Tools for Windows

You can get Debugging Tools for Windows as part of a development kit or as a standalone tool set:

  • As part of the WDK

    Debugging Tools for Windows is included in the Windows Driver Kit (WDK). To get the WDK, see Download the Windows Driver Kit (WDK).

  • As part of the Windows SDK

    Debugging Tools for Windows is included in the Windows Software Development Kit (SDK). To download the installer or an ISO image, see Windows 10 SDK on Windows Dev Center.

  • As a standalone tool set

    You can install the Debugging Tools for Windows alone, without the Windows SDK or WDK, by starting installation of the Windows SDK and then selecting only Debugging Tools for Windows in the list of features to install (and clearing the selection of all other features). To download the installer or an ISO image, see Windows 10 SDK on Windows Dev Center.

Get started with Windows Debugging

To get started with Windows debugging, see Getting Started with Windows Debugging.

To get started with debugging kernel-mode drivers, see Debug Universal Drivers - Step by Step Lab (Echo Kernel-Mode). This is a step-by-step lab that shows how to use WinDbg to debug Echo, a sample driver that uses the Kernel-Mode Driver Framework (KMDF).

Debugging environments

If your computer has Visual Studio and the WDK installed, then you have six available debugging environments. For descriptions of these environments, see Debugging Environments.

All of these debugging environments provide user interfaces for the same underlying debugging engine, which is implemented in the Windows Symbolic Debugger Engine (Dbgeng.dll). This debugging engine is also called the Windows debugger, and the six debugging environments are collectively called the Windows debuggers.

Note

Visual Studio includes its own debugging environment and debugging engine, which together are called the Visual Studio debugger. For information on debugging in Visual Studio, see Debugging in Visual Studio. For debugging managed code, such as C#, using the Visual Studio debugger is often the easiest way to get started.

Windows debuggers

The Windows debuggers can run on x86-based, x64-based, or ARM-based processors, and they can debug code that is running on those same architectures. Sometimes the debugger and the code being debugged run on the same computer, but other times the debugger and the code being debugged run on separate computers. In either case, the computer that is running the debugger is called the host computer, and the computer that is being debugged is called the target computer. The Windows debuggers support the following versions of Windows for both the host and target computers.

  • Windows 10 and Windows Server 2016
  • Windows 8.1 and Windows Server 2012 R2
  • Windows 8 and Windows Server 2012
  • Windows 7 and Windows Server 2008 R2
2012

Symbols and symbol files

Symbol files store a variety of data that are not required when running the executable binaries, but symbol files are very useful when debugging code. For more information about creating and using symbol files, see Symbols for Windows debugging (WinDbg, KD, CDB, NTSD).

Blue screens and crash dump files

If Windows stops working and displays a blue screen, the computer has shut down abruptly to protect itself from data loss and displays a bug check code. For more information, see Bug Checks (Blue Screens). You analyze crash dump files that are created when Windows shuts down by using WinDbg and other Windows debuggers. For more information, see Crash dump analysis using the Windows debuggers (WinDbg).

Tools and utilities

In addition to the debuggers, Debugging Tools for Windows includes a set of tools that are useful for debugging. For a full list of the tools, see Tools Included in Debugging Tools for Windows.

Additional documentation

For additional information related to Debugging Tools for Windows, see Debugging Resources. For information on what's new in Windows 10, see Debugging Tools for Windows: New for Windows 10.

The dumpchk command allows users to view the Windows minidump files created when Windows stops unexpectedly.

Availability

Dumpchk is an external command that is available for the following Microsoft operating systems as dumpchk.exe.

  • Windows 2003

This command is available for Windows XP, however, it requires that the Windows XP Support Tools are installed on the computer. The Support Tools can be downloaded from Microsoft's website, or, if you have your Windows XP CD, in the SupportTools directory.

Windows 2003 also supports this file but needs the Windows 2003 Support Tools to be installed.

Tip

If the Support Tools are installed, but this command is not working go into the C:Program FilesSupport Toolsdirectory and run the command. If this works, you can update your path to this directory, so it works in the future.

Note

Although dumpchk was available in the Windows 7 beta, it is no longer include with Windows. If you need debug utilities, use WinDbg.

Dumpchk syntax

Usage: DumpCheck [y <sympath>] <Dumpfile>

Windows XP syntax

Dumpchk Windows Server 2012
-pPrints the header only (with no validation).
-vSpecifies verbose mode.
-qPerforms a quick test.

Windows 2000 syntax

-pPrints the header only (with no validation).
-vSpecifies verbose mode.
-cDo dump validation.
-xExtra file validation. Takes several minutes.
-eDo dump exam.
-y <Path>Set the symbol search path for dump exam. If the symbol search path is empty, the CD-ROM is used for symbols.
-b <Path>Set the image search path for dump exam. If the symbol search path is empty, <SystemRoot>system32is used for symbols.
-k <File>Set the name of the kernel to File.
-h <File>Set the name of the hal to File.

Dumpchk examples

Windows

Dumpchk Windows Server 2012 R2 Download Iso

Display debug information.

Dumpchk Windows Server 2012 Download

Additional information

  • See our dump definition for further information and related links on this term.




Comments are closed.