Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Format:Windows kernel crash dump

From ReverseEngineering.wiki
Format
Developer Microsoft
Magic 50 41 47 45 44 55 4D 50 ("PAGEDUMP") or 50 41 47 45 44 55 36 34 ("PAGEDU64") at offset 0
Extensions .dmp, memory.dmp, MEMORY.DMP
Endianness little
On this wiki Facts · Code · Notes · Topics

The memory.dmp file Windows writes on a bugcheck: a 4 KiB (32-bit, 'PAGEDUMP') or 8 KiB (64-bit, 'PAGEDU64') _DUMP_HEADER with the machine type, bugcheck code and parameters, the physical memory run list and the dump type, followed by the memory pages.

Identification

  • Offset 0: u32 Signature = 0x45474150 ("PAGE"); offset 4: u32 ValidDump = 0x504D5544 ("DUMP") for 32-bit dumps or 0x34365544 ("DU64") for 64-bit dumps. So the file starts PAGEDUMP or PAGEDU64. Do not confuse with user-mode Format:Minidump files, which start with MDMP.
  • Volatility 3's WindowsCrashDump32Layer / WindowsCrashDump64Layer check exactly these two constants and support DumpType 0x01 (full) and 0x05 (bitmap, kernel or full).

_DUMP_HEADER64 (0x2000 bytes)

Offsets from Volatility 3's crash64.json symbol table:

Offset Field
0x00 Signature, ValidDump (u32 each)
0x08 MajorVersion, 0x0c MinorVersion (u32 each; Unverified: MajorVersion is 0xF for free builds and 0xC for checked builds, MinorVersion is the build number)
0x10 DirectoryTableBase (u64, kernel CR3)
0x18 PfnDataBase
0x20 PsLoadedModuleList
0x28 PsActiveProcessHead
0x30 MachineImageType (u32; 0x8664 AMD64, 0x14c i386, 0xAA64 ARM64)
0x34 NumberProcessors
0x38 BugCheckCode (u32); 0x40 BugCheckCodeParameter[4] (u64 each)
0x60 VersionUser[32]
0x80 KdDebuggerDataBlock (u64; points to KDBG, which Volatility and WinDbg use to find the kernel base)
0x88 PhysicalMemoryBlockBuffer: u32 NumberOfRuns, u32 NumberOfPages, runs at 0x98 of {u64 BasePage, u64 PageCount}; the buffer field spans 0x88-0x347 (0x2C0 bytes), which bounds the run list
0x348 ContextRecord[3000] bytes (a CONTEXT of the bugcheck CPU; offset up to 0xf00)
0xf00 Exception: _EXCEPTION_RECORD64 (152 bytes)
0xf98 DumpType (u32): 1 full, 5 bitmap; Unverified: 2 kernel, 3 small (triage) in older dumps
0xfa0 RequiredDumpSpace (u64)
0xfa8 SystemTime (u64 FILETIME)
0xfb0 Comment[128]
0x1030 SystemUpTime (u64)
0x1038 MiniDumpFields, 0x103c SecondaryDataState, 0x1040 ProductType, 0x1044 SuiteMask, 0x1048 WriterStatus
0x104d KdSecondaryVersion (u8)

_DUMP_HEADER (32-bit, 0x1000 bytes)

Same idea with 32-bit pointers: DirectoryTableBase 0x10, PfnDataBase 0x14, PsLoadedModuleList 0x18, PsActiveProcessHead 0x1c, MachineImageType 0x20, NumberProcessors 0x24, BugCheckCode 0x28, parameters 0x2c (4 x u32), VersionUser 0x3c, PaeEnabled 0x5c, KdSecondaryVersion 0x5d, KdDebuggerDataBlock 0x60, PhysicalMemoryBlockBuffer 0x64 (runs at 0x6c, {u32 BasePage, u32 PageCount}), ContextRecord 0x320, Exception 0x7d0 (_EXCEPTION_RECORD32, 80 bytes), Comment 0x820, DumpType 0xf88, then MiniDumpFields 0xf8c ... RequiredDumpSpace 0xfa0, SystemUpTime 0xfb8, SystemTime 0xfc0.

Body

  • Full dump (DumpType 1): the pages follow the header (1 page for 32-bit, 2 for 64-bit) in the order of the run list; run i occupies PageCount * 0x1000 bytes at the file offset after the previous runs, and maps to physical address BasePage * 0x1000. Volatility builds its physical-memory layer from exactly this.
  • Bitmap dump (DumpType 5): a _SUMMARY_DUMP header follows the main header; its HeaderSize field is the offset of the page data, and a bitmap (one bit per physical page, bit set = page present) says which pages were saved; present pages are stored consecutively. Kernel-only and active-memory dumps use this layout.
  • The dump header, not the body, holds the processor context and the bugcheck data; WinDbg's .bugcheck, !analyze -v and Volatility's crashinfo read them. KdDebuggerDataBlock gives symbols for the kernel (match by PDB GUID of ntoskrnl.exe).

Tools and sources

Volatility 3 (volatility3/framework/layers/crash.py and symbols/windows/crash*.json) and WinDbg read these files. Unverified: ReactOS defines the same structures for its own bugcheck code (its headers were not located while writing this page); a full dump is about the size of RAM plus the header (compare with RequiredDumpSpace).

Code & repositories

  • https://github.com/volatilityfoundation/volatility3 @ 77ff0b1932d77527f850c8ced01d85805ea7bf97 · license: LicenseRef-VSL (declared by the contributor; GitHub's detector did not recognize LICENSE.txt)
    Volatility 3: crash.py layer and crash/crash64 JSON symbol tables with _DUMP_HEADER layouts (Volatility Software License, source-available)
    Tested on: source read, not run: read only, develop branch · checked 2026-10-18; last activity 2026-10-12; Note: the latest release ships binaries; the wiki links only the source, never the binaries

Evidence & references

volatilityfoundation/volatility3 (Volatility Software License, a source-available license: only constants and layouts are recorded here, no code); Unverified: MajorVersion/MinorVersion semantics and the dump type numbers other than 1 and 5.

See also Format:Minidump, Format:ELF (Executable and Linkable Format)/Core dumps, Format:GDB Remote Serial Protocol.