Search
Search titles only
By:
Search titles only
By:
Log in
Register
Search
Search titles only
By:
Search titles only
By:
Menu
Install the app
Install
Forums
New posts
All threads
Latest threads
New posts
Trending threads
Trending
Search forums
What's new
New posts
New ads
New profile posts
Latest activity
Free Ads
Latest reviews
Search ads
Members
Current visitors
New profile posts
Search profile posts
Contact us
Latest ads
Power Lifting Lever Belt
SkullVamp
Updated:
Saturday at 10:32 PM
Ad icon
port.lk Domain for sale
Lankan-Tech
Updated:
Saturday at 3:55 PM
Colombo
Kaduwela - Two Storey House for Sale
dilrasan
Updated:
Thursday at 2:23 PM
Ad icon
Wechat qr verification
Pawan2005
Updated:
Thursday at 1:28 AM
🚀 GOOGLE AI PRO 18 MONTHS ACTIVATION 🚀
sayuru bandara
Updated:
Jun 10, 2026
Electronics
Vehicles
Property
Search
Reply to thread
Forums
General
ElaKiri Help
Help ekak one ...
Get the App
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="gnate3_2009" data-source="post: 4397073" data-attributes="member: 169898"><p>Complete memory dump</p><p>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. </p><p></p><p>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).</p><p></p><p>If a second problem occurs and another complete memory dump (or kernel memory dump) file is created, the previous file is overwritten.</p><p></p><p>Note 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. </p><p></p><p>For more information, click the following article number to view the article in the Microsoft Knowledge Base:</p><p>274598 Complete memory dumps are not available on computers that have 2 or more gigabytes of RAM</p><p>Back to the top</p><p>Kernel memory dump</p><p>A kernel memory dump records only the kernel memory. This speeds up the process of recording information in a log when your computer stops unexpectedly. Depending on the RAM in your computer, you must have between 150MB and up to 2GB of pagefile space available based on server load and the amount of physical RAM available for page file space on the boot volume.</p><p></p><p>This dump file does not include unallocated memory or any memory that is allocated to User-mode programs. It includes only memory that is allocated to the kernel and hardware abstraction layer (HAL) in Windows 2000 and later, and memory allocated to Kernel-mode drivers and other Kernel-mode programs. For most purposes, this dump file is the most useful. It is significantly 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.</p><p></p><p>If a second problem occurs and another kernel memory dump file (or a complete memory dump file) is created, the previous file is overwritten.</p><p>Back to the top</p><p>Small memory dump</p><p>A small memory dump records the smallest set of useful information that may help identify why your computer stopped unexpectedly. This option requires a paging file of at least 2 MB on the boot volume and specifies that Windows 2000 and later create a new file every time your computer stops unexpectedly. A history of these files is stored in a folder.</p><p></p><p>This dump file type includes the following information:</p><p>The Stop message and its parameters and other data</p><p>A list of loaded drivers</p><p>The processor context (PRCB) for the processor that stopped</p><p>The process information and kernel context (EPROCESS) for the process that stopped</p><p>The process information and kernel context (ETHREAD) for the thread that stopped</p><p>The Kernel-mode call stack for the thread that stopped</p><p>This kind of dump file can be useful when space is limited. However, because of the limited information included, errors that were not directly caused by the thread that was running at the time of the problem may not be discovered by an analysis of this file.</p><p></p><p>If a second problem occurs and a second small memory dump file is created, the previous file is preserved. 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.</p><p>Back to the top</p><p>Configure the dump type</p><p>To configure startup and recovery options (including the dump type), follow these steps.</p><p></p><p>Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.</p><p>Click Start, and then click Control Panel.</p><p>Click Performance and Maintenance, and then click System.</p><p>On the Advanced tab, click Settings under Startup and Recovery.</p><p>Back to the top</p><p>Tools for the various dump types</p><p>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.</p><p></p><p>Load small memory dumps by using Dumpchk.exe. Dumpchk.exe is included with the Support Tools for Windows 2000 and Windows XP. You can also use Dumpchk.exe to verify that a memory dump file has been created correctly. </p><p></p><p>For more information about how to use Dumpchk.exe in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:</p><p>315271 How to use Dumpchk.exe to check a memory dump file</p><p>For more information about how to use Dumpchk.exe in Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base:</p><p>156280 How to use Dumpchk.exe to check a memory dump file</p><p>For more information about Windows debugging tools, visit the following Microsoft Web site:</p><p><a href="http://www.microsoft.com/whdc/devtools/debugging/default.mspx" target="_blank">http://www.microsoft.com/whdc/devtools/debugging/default.mspx</a></p><p>Back to the top</p><p>Definitions</p><p>Boot volume: The volume that contains the Windows operating system and its support files. The boot volume can be, but does not have to be, the same as the system volume.</p><p>System volume: The volume that contains the hardware-specific files that you must have to load Windows. The system volume can be, but does not 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.</p><p>Back to the top</p><p>Registry values for startup and recovery</p><p>The following registry value is used:</p><p>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl</p><p></p><p>CrashDumpEnabled REG_DWORD 0x0 = None</p><p>CrashDumpEnabled REG_DWORD 0x1 = Complete memory dump</p><p>CrashDumpEnabled REG_DWORD 0x2 = Kernel memory dump</p><p>CrashDumpEnabled REG_DWORD 0x3 = Small memory dump (64KB)</p><p>Additional registry values for CrashControl:</p><p>0x0 = Disabled</p><p>0x1 = Enabled</p><p></p><p>AutoReboot REG_DWORD 0x1</p><p>DumpFile REG_EXPAND_SZ %SystemRoot%\Memory.dmp</p><p>LogEvent REG_DWORD 0x1</p><p>MinidumpDir REG_EXPAND_SZ %SystemRoot%\Minidump</p><p>Overwrite REG_DWORD 0x1</p><p>SendAlert REG_DWORD 0x1</p><p>Back to the top</p><p>Test to make sure that a dump file can be created</p><p>For more information about how to configure your computer to generate a dump file for testing purposes, click the following article number to view the article in the Microsoft Knowledge Base:</p><p>244139 Windows feature lets you generate a memory dump file by using the keyboard</p><p>Back to the top</p><p>Default dump type options</p><p>Windows 2000 Professional: Small memory dump (64 KB)</p><p>Windows 2000 Server: Complete memory dump</p><p>Windows 2000 Advanced Server: Complete memory dump</p><p>Windows XP (Professional and Home Edition): Small memory dump (64 KB)</p><p>Windows Server 2003 (All Editions): Complete memory dump</p><p>Windows Vista (All Editions): Kernel memory dump</p><p>Windows Server 2008 (All Editions): Complete memory dump</p></blockquote><p></p>
[QUOTE="gnate3_2009, post: 4397073, member: 169898"] Complete memory dump 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. 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). If a second problem occurs and another complete memory dump (or kernel memory dump) file is created, the previous file is overwritten. Note 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, click the following article number to view the article in the Microsoft Knowledge Base: 274598 Complete memory dumps are not available on computers that have 2 or more gigabytes of RAM Back to the top Kernel memory dump A kernel memory dump records only the kernel memory. This speeds up the process of recording information in a log when your computer stops unexpectedly. Depending on the RAM in your computer, you must have between 150MB and up to 2GB of pagefile space available based on server load and the amount of physical RAM available for page file space on the boot volume. This dump file does not include unallocated memory or any memory that is allocated to User-mode programs. It includes only memory that is allocated to the kernel and hardware abstraction layer (HAL) in Windows 2000 and later, and memory allocated to Kernel-mode drivers and other Kernel-mode programs. For most purposes, this dump file is the most useful. It is significantly 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. If a second problem occurs and another kernel memory dump file (or a complete memory dump file) is created, the previous file is overwritten. Back to the top Small memory dump A small memory dump records the smallest set of useful information that may help identify why your computer stopped unexpectedly. This option requires a paging file of at least 2 MB on the boot volume and specifies that Windows 2000 and later create a new file every time your computer stops unexpectedly. A history of these files is stored in a folder. This dump file type includes the following information: The Stop message and its parameters and other data A list of loaded drivers The processor context (PRCB) for the processor that stopped The process information and kernel context (EPROCESS) for the process that stopped The process information and kernel context (ETHREAD) for the thread that stopped The Kernel-mode call stack for the thread that stopped This kind of dump file can be useful when space is limited. However, because of the limited information included, errors that were not directly caused by the thread that was running at the time of the problem may not be discovered by an analysis of this file. If a second problem occurs and a second small memory dump file is created, the previous file is preserved. 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. Back to the top Configure the dump type To configure startup and recovery options (including the dump type), follow these steps. Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps. Click Start, and then click Control Panel. Click Performance and Maintenance, and then click System. On the Advanced tab, click Settings under Startup and Recovery. Back to the top Tools for the various dump types 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. Load small memory dumps by using Dumpchk.exe. Dumpchk.exe is included with the Support Tools for Windows 2000 and Windows XP. You can also use Dumpchk.exe to verify that a memory dump file has been created correctly. For more information about how to use Dumpchk.exe in Windows XP, click the following article number to view the article in the Microsoft Knowledge Base: 315271 How to use Dumpchk.exe to check a memory dump file For more information about how to use Dumpchk.exe in Windows 2000, click the following article number to view the article in the Microsoft Knowledge Base: 156280 How to use Dumpchk.exe to check a memory dump file For more information about Windows debugging tools, visit the following Microsoft Web site: [url]http://www.microsoft.com/whdc/devtools/debugging/default.mspx[/url] Back to the top Definitions Boot volume: The volume that contains the Windows operating system and its support files. The boot volume can be, but does not have to be, the same as the system volume. System volume: The volume that contains the hardware-specific files that you must have to load Windows. The system volume can be, but does not 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. Back to the top Registry values for startup and recovery The following registry value is used: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\CrashControl CrashDumpEnabled REG_DWORD 0x0 = None CrashDumpEnabled REG_DWORD 0x1 = Complete memory dump CrashDumpEnabled REG_DWORD 0x2 = Kernel memory dump CrashDumpEnabled REG_DWORD 0x3 = Small memory dump (64KB) Additional registry values for CrashControl: 0x0 = Disabled 0x1 = Enabled AutoReboot REG_DWORD 0x1 DumpFile REG_EXPAND_SZ %SystemRoot%\Memory.dmp LogEvent REG_DWORD 0x1 MinidumpDir REG_EXPAND_SZ %SystemRoot%\Minidump Overwrite REG_DWORD 0x1 SendAlert REG_DWORD 0x1 Back to the top Test to make sure that a dump file can be created For more information about how to configure your computer to generate a dump file for testing purposes, click the following article number to view the article in the Microsoft Knowledge Base: 244139 Windows feature lets you generate a memory dump file by using the keyboard Back to the top Default dump type options Windows 2000 Professional: Small memory dump (64 KB) Windows 2000 Server: Complete memory dump Windows 2000 Advanced Server: Complete memory dump Windows XP (Professional and Home Edition): Small memory dump (64 KB) Windows Server 2003 (All Editions): Complete memory dump Windows Vista (All Editions): Kernel memory dump Windows Server 2008 (All Editions): Complete memory dump [/QUOTE]
Insert quotes…
Verification
Hath warak paha keeyada? (hatha wadikireema paha)
Post reply
Top
Bottom