SystemRequires admin/root
Minidump Files
Windows writes small crash dump files to %WinDir%\Minidump after a blue screen or system-level fault so the stop code, loaded drivers, kernel stack, and selected memory pages can be analyzed later in WinDbg or by support tools. These .dmp files are not an active cache used for normal operation; they are post-crash diagnostic artifacts that accumulate over time after BSODs, driver failures, and kernel crashes. Kudu removes old minidump files from the Minidump folder without touching personal files, accounts, settings, or passwords.
Why clean Minidump Files?
- Repeated blue screens can leave behind dozens or hundreds of .dmp files, and the visible symptom is unexpectedly high space usage in C: \Windows even though everyday documents have not grown
- Minidumps are only useful for debugging a crash that already happened, so once the issue is fixed they become stale evidence that keeps consuming disk space with no benefit during normal boot or app use
- Very full system drives make Windows updates, hibernation, and pagefile growth less reliable, and accumulated crash dumps can contribute to low-disk warnings and failed feature updates
- Support and diagnostic scans that enumerate crash dumps take longer when years of old minidumps are present, so users may notice slower analysis in cleanup or troubleshooting tools
- Minidump folders often preserve reports from obsolete driver versions, which can confuse troubleshooting because users see many old crash dates and stop codes that no longer match the current problem
- On shared or managed PCs, crash dumps can expose process names, loaded modules, and fragments of memory state to administrators or support staff, so clearing outdated files reduces leftover diagnostic data after the crash has been investigated
What gets cleaned
Cache paths Kudu targets
Windows
%WinDir%/Minidump |
Frequently asked
Common questions about Minidump Files
Related cleaners
Free & open source
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.