Skip to content
littleden.blogEvidence-led Windows troubleshooting, without the guesswork
FixesError codesComponentsCommandsWindows updatesWindows 11
Research statusMethodology
Diagnostics & reliability · reviewed troubleshooting

Find Windows crash dump files: Minidump vs MEMORY.DMP and what each tells you

Locate the dump that matches a Windows stop error and verify dump configuration before assuming Windows failed to capture the crash.

Applies to: Windows 11Change risk: LowReviewed: 2026-09-17
Do this first
  1. Record the stop code and crash time before looking for a dump.
  2. Check C:\Windows\Minidump for timestamped small dump files.
  3. Check C:\Windows\MEMORY.DMP for kernel/automatic/complete dump output.
  4. Open Advanced system settings > Startup and Recovery to confirm Write debugging information is enabled if repeated crashes are not producing useful dumps.

What this problem usually means

Microsoft documents several Windows crash-dump types. Small dumps are normally kept under %SystemRoot%\Minidump, while kernel, automatic and complete memory dumps normally use %SystemRoot%\MEMORY.DMP. The configured dump type, paging-file state, disk space and whether Windows completed dump writing all affect what exists after a crash.

Ordered repair path

Work from the narrowest fix to the broader one.

1

Match the dump file to the crash time

Low risk

Why this belongs here: Analyzing an older dump can send troubleshooting down the wrong driver or stop-code branch.

  1. Compare the dump modification time with Event ID 1001 and the restart timeline.
  2. Prefer the dump from the exact incident being investigated.
  3. Keep the original dump unchanged before copying it for analysis.
2

Verify dump configuration when no usable file is produced

Low risk

Why this belongs here: Microsoft’s stop-error guidance recommends Automatic memory dump for general collection and documents the standard dump locations.

  1. Open Startup and Recovery settings.
  2. Confirm an appropriate debugging-information option is selected.
  3. Keep the page file system-managed unless a specific supported configuration requires otherwise.
  4. Ensure the system drive has enough free space for the configured dump type.
Stop condition

When this guide stops being the right path

Do not deliberately crash a normal production PC just to create a dump unless you are following a controlled expert support procedure. Do not upload dump files publicly without considering that they may contain process/memory data.

If the problem is still not fixed

Use the exact stop-code record first; use WinDbg or qualified debugging only when the dump is needed to identify the responsible driver/module or call stack.

Evidence

Sources reviewed for this page

Primary technical guidance is preferred. A source supports the scope stated here; it does not imply that every possible cause is covered.

Related authority records

Continue with the same failing system

These links share the same component or repair context; they are not generic keyword suggestions.

GuideNo memory dump after a Windows blue screen: verify capture settings before blaming the crash

A missing MEMORY.DMP or Minidump can reflect dump configuration, paging-file requirements, disk space or an incomplete write—not proof that no bugcheck occurred.

GuideFind repeated app crashes with Reliability Monitor before reinstalling everything

Use the Windows reliability timeline to identify when failures began and whether they line up with a specific app, driver, update or installation.

CommandPowerShell — read CrashControl settings

Read the main Windows crash-dump configuration values without changing them, useful when a real bugcheck is not producing the expected dump file.

ErrorEvent ID 1001 — WER-SystemErrorReporting bugcheck: preserve the stop code and dump path

When Event ID 1001 says the computer rebooted from a bugcheck, the useful evidence is the exact bugcheck code, parameters and saved dump.

GuideApplication keeps crashing in Windows 11: correlate Event ID 1000 with WER and the faulting module

Use repeated Application Error/WER records to identify the failing process, module and exception before reinstalling Windows or unrelated drivers.

GuideCapture a user-mode app dump with Task Manager in Windows 11

Preserve a crashing or hung application state for vendor or debugger analysis without crashing the whole PC.