这篇文章快速浏览了 Windows 10/8/7崩溃转储文件中的物理内存限制，^{(Physical Memory Limits in Crash Dump files)}并使用了Windows Sysinternals工具RamMap，该工具可用于确定系统上物理内存范围的数量。

故障转储^{(Crash Dump)}文件中的物理内存限制^{(Memory Limits)}

所有Windows操作系统都配置为在发生停止错误或系统崩溃时捕获有关其状态的信息，并将它们保存为 .dmp 故障转储文件。在系统崩溃的情况下可以捕获三种类型的转储：完整内存转储、内核内存转储和小内存转储。^{(Complete Memory Dump, Kernel Memory Dump, and Small Memory Dump.)}

故障转储格式限制为 42（64 位）和 86（32 位）物理地址范围。在某些系统上，BIOS固件内存映射可能包含超过此数量的非连续区域。在此系统上生成转储文件时，只会将前 42 个（64 位）或 86 个（32 位）内存区域保存到文件中。  Windows系统的^(Windows)内核^(Kernel)和完整^(Complete)内存转储可能不包含系统的所有内存。

有时，在使用Windows调试工具^{(Debugging Tools)}(windbg.exe)打开在某些系统上生成的内存转储文件时，您可能会收到一条错误消息：

WARNING: Dump header physical memory block has been truncated. Some valid physical pages may be inaccessible.

为防止该问题，受影响系统的OEM将需要修改固件内存映射，以确保暴露给操作系统的物理连续物理内存区域的数量不超过前面提到的限制，KB2510168状态。

Sysinternals RamMap

Sysinternals工具RamMap可用于确定系统上物理内存范围的数量。下载并执行RamMap.exe后，单击Physical Ranges选项卡。计算列出的范围数将验证特定系统上的物理范围数。

RAMMap是适用于Windows Vista^{(Windows Vista)}及更高版本的高级物理内存使用分析实用程序它在几个不同的选项卡中以不同的方式显示使用信息：

• 使用计数：按类型和分页列表的使用摘要
• 进程：进程工作集大小
• 优先级摘要^{(Priority Summary)}：优先的备用列表大小
• 物理页面：所有物理内存的每页使用
• 物理范围：物理内存地址
• 文件摘要^{(File Summary)}：按文件存储在RAM中的文件数据
• 文件详细信息：按文件的单个物理页面
• 使用 RAMMap^{(Use RAMMap)}了解Windows管理内存的方式、分析应用程序内存使用情况或回答有关如何分配RAM的具体问题。^(RAM)

RAMMap将告诉Windows如何分配物理内存，在^(Windows)RAM中缓存了多少文件数据，或者内核和设备驱动程序使用了多少RAM 。

您可能还会对这些链接感兴趣：

1. Windows 中的机器内存转储收集器
2. Windows 中的物理内存分配和内存状态。

Physical Memory Limits in Crash Dump files for Windows 10

This post has а quick look at Physical Memory Limits in Crash Dump files for Windows 10/8/7 and using the Windows Sysinternals tool RamMap, which can be used to determine the number of physical memory ranges on a system.

Physical Memory Limits in Crash Dump files

All Windows operating systems are configured to capture information about its state, in the event of a stop error or system crash, and save them as .dmp crash dump files. There are three types of dumps that can be captured in case of a system crash: Complete Memory Dump, Kernel Memory Dump, and Small Memory Dump.

The crash dump format has a limit of 42 (64-bit) and 86 (32-bit) physical address ranges. On certain systems, the BIOS firmware memory map may contain more than this number of non-contiguous regions. When a dump file is generated on this system, only the first 42 (64-bit) or 86 (32-bit) memory regions will be saved to the file.  Kernel and Complete memory dump from a Windows system may not contain all the memory from the system.

On occasions, when opening a memory dump file generated on certain systems using the Debugging Tools for Windows (windbg.exe), you may receive an error message:

WARNING: Dump header physical memory block has been truncated. Some valid physical pages may be inaccessible.

To prevent the issue, the OEM of the affected system would need to modify the firmware memory map to ensure the number of physical contiguous physical memory regions exposed to the Operating System does not exceed the limits previously noted, states KB2510168.

Sysinternals RamMap

The Sysinternals tool RamMap can be used to determine the number of physical memory ranges on a system. After downloading and executing RamMap.exe, click the Physical Ranges tab. Counting the number of ranges listed will verify the number of physical ranges on a particular system.

RAMMap is an advanced physical memory usage analysis utility for Windows Vista and higher. It presents usage information in different ways in its several different tabs:

• Use Counts: usage summary by type and paging list
• Processes: process working set sizes
• Priority Summary: prioritized standby list sizes
• Physical Pages: per-page use for all physical memory
• Physical Ranges: physical memory addresses
• File Summary: file data in RAM by file
• File Details: individual physical pages by file
• Use RAMMap to gain an understanding of the way Windows manages memory, to analyze application memory usage, or to answer specific questions about how RAM is being allocated.

RAmMap will tell how Windows is assigning physical memory, how much file data is cached in RAM, or how much RAM is used by the kernel and device drivers.

These links may also interest you:

1. Machine Memory Dump Collector in Windows
2. Physical memory allocation and memory status in Windows.

Related posts

• 如何手动创建一个Windows 10 Crash Dump file

• 如何在 Windows 10 中读取内存转储文件

• 如何在 Windows 10 中分析内存转储文件 (.dmp)

• 如何检查哪个应用程序在Windows 10中使用更多RAM

• Windows 10计算机Error 0164，Memory size下降 - RAM issue

• 无法连接到Xbox Live; Windows 10中的Fix Xbox Live Networking issue

• Analyze Windows Memory Dump .dmp带WhoCrashed的文件

• Best免费Molecular Modeling software的Windows 10

• 如何执行Google SafeSearch在Microsoft Edge在Windows 10

• Taskbar在Windows 10上的Hide or Show Windows Ink Workspace Button

• 免费Battery Limiter software用于Windows 10

• Event ID 158错误 - 同磁盘GUIDs assignment在Windows 10

• Windows 10上的Fix NVIDIA Drivers Constantly Crash

• Windows 10中的启用包是什么

• 如何修复 Windows 10 上的“您的计算机内存不足”错误

• 如何修复 Windows 10 内存泄漏

• 使用MyLauncher为Windows 10计算机启动文件

• 创建Keyboard Shortcut以在Windows 10中打开您最喜爱的Website

• Mz Ram Booster用于Windows 10 tweaks system设置RAM

• Windows 10 Lock Screen Make Firefox display Media Controls Lock Screen