You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can configure the following operating systems to write debugging information:
22
-
23
-
- Windows 7
24
-
- Windows Server 2012 R2
25
-
26
-
The debugging information can be written to different file formats (also known as memory dump files) when your computer stops unexpectedly because of a **Stop** error (also known as a _blue screen_, system crash, or bug check). You can also configure Windows not to write debugging information to a memory dump file.
21
+
Debugging information can be written to different file formats (also known as memory dump files) when your computer stops unexpectedly because of a **Stop** error (also known as a _blue screen_, system crash, or bug check). You can also configure Windows not to write debugging information to a memory dump file.
27
22
28
23
Windows can generate any one of the following memory dump file types:
A complete memory dump records all the contents of system memory when your computer stops unexpectedly. A complete memory dump may contain data from processes that were running when the memory dump was collected.
38
33
39
-
If you select the **Complete memory dump** option, you must have a paging file on the boot volume that is sufficient to hold all the physical RAM plus 1 megabyte (MB).
34
+
If you select the **Complete memory dump** option, you must have a paging file on the boot volume that is sufficient to hold all the physical RAM plus 257 megabyte (MB).
40
35
41
36
If the following conditions are true, the previous file is overwritten.
42
37
43
38
- A second problem occurs.
44
39
- Another complete memory dump (or kernel memory dump) file is created.
45
40
46
-
> [!NOTE]
47
-
>
48
-
> - In Windows 7, the paging file can be on a partition that differs from the partition on which the operating system is installed.
49
-
> - In Windows 7, you do not have to use the DedicatedDumpFile registry entry to put a paging file onto another partition.
50
-
> - The **Complete memory dump** option is not available on computers that are running a 32-bit operating system and that have 2 gigabytes (GB) or more of RAM. For more information, see [Specify what happens when the system stops unexpectedly](/previous-versions/windows/it-pro/windows-server-2003/cc778968(v=ws.10)).
51
-
52
41
## Kernel memory dump
53
42
54
43
A kernel memory dump records only the kernel memory. It speeds up the process of recording information in a log when your computer stops unexpectedly. You must have a pagefile large enough to accommodate your kernel memory. For 32-bit systems, kernel memory is usually between 150 MB and 2 GB.
55
44
56
45
This dump file doesn't include unallocated memory or any memory that's allocated to User-mode programs. It includes:
57
46
58
-
- Memory that's allocated to the kernel and hardware abstraction layer (HAL) in Windows 2000 and later.
47
+
- Memory that's allocated to the kernel and hardware abstraction layer (HAL) in the latest supported Windows version.
59
48
- Memory that's allocated to Kernel-mode drivers and other Kernel-mode programs.
60
49
61
50
For most purposes, this dump file is the most useful. It's smaller than the complete memory dump file. But it omits only those parts of memory that are unlikely to have been involved in the problem.
@@ -87,6 +76,10 @@ If the following conditions are true, the previous file is preserved.
87
76
88
77
Each additional file is given a distinct name. The date is encoded in the file name. For example, Mini022900-01.dmp is the first memory dump generated on February 29, 2000. A list of all small memory dump files is kept in the `%SystemRoot%\Minidump` folder.
89
78
79
+
## Active memory dump
80
+
81
+
For more information, see [Active memory dump](/windows-hardware/drivers/debugger/active-memory-dump).
82
+
90
83
## Configure the dump type
91
84
92
85
To configure startup and recovery options (including the dump type), follow these steps.
@@ -103,15 +96,7 @@ To configure startup and recovery options (including the dump type), follow thes
103
96
104
97
## Tools for the various dump types
105
98
106
-
You can load complete memory dumps and kernel memory dumps with standard symbolic debuggers, such as I386kd.exe. I386kd.exe is included with the Windows 2000 Support CD-ROM.
107
-
108
-
Load small memory dumps by using Dumpchk.exe. You can also use Dumpchk.exe to verify that a memory dump file has been created correctly.
109
-
110
-
## Volume definitions
111
-
112
-
- Boot volume: The volume that contains the Windows operating system and its support files. The boot volume can be, but doesn't have to be, the same as the system volume.
113
-
114
-
- System volume: The volume that contains the hardware-specific files that you must have to load Windows. The system volume can be, but doesn't have to be, the same as the boot volume. The Boot.ini, `Ntdetect.com`, and Ntbootdd.sys files are examples of files that are located on the system volume.
99
+
You can load complete memory dumps and kernel memory dumps with the [Windows debugger](/windows-hardware/drivers/debugger/).
115
100
116
101
## Registry values for startup and recovery
117
102
@@ -122,12 +107,10 @@ The following registry value is used under `HKEY_LOCAL_MACHINE\System\CurrentCon
@@ -142,21 +125,6 @@ Additional registry values for CrashControl:
142
125
143
126
For more information about how to configure your computer to generate a dump file for testing purposes, see [Windows feature lets you generate a memory dump file by using the keyboard](https://support.microsoft.com/help/244139).
144
127
145
-
## Default dump type options
146
-
147
-
- Windows 7 (All Editions): Kernel memory dump
148
-
- Windows Server 2012 R2 (All Editions): Automatic memory.dmp
149
-
150
128
## Maximum paging file size
151
129
152
-
Maximum paging file size is limited as follows:
153
-
154
-
|Limit|x86|x64|IA-64|
155
-
|---|---|---|---|
156
-
|Maximum size of a paging file|4 gigabytes (non-PAE)<br/>16 terabytes (PAE)|16 terabytes|32 terabytes|
## Technical support for x64-based versions of Windows
161
-
162
-
Your hardware manufacturer provides technical support and assistance for x64-based versions of Windows. Your hardware manufacturer provides support because an x64-based version of Windows was included with your hardware. Your hardware manufacturer might have customized the installation of Windows with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your x64-based version of Windows. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.
130
+
For more information, see [How to determine the appropriate page file size for 64-bit versions of Windows](../../windows-client/performance/how-to-determine-the-appropriate-page-file-size-for-64-bit-versions-of-windows.md).
0 commit comments