All tag results for ‘Dump’
December 5th, 2008 · No Comments · 865 views
In Windows Server 2008-based or Windows Vista Service Pack 1 (SP1)-based systems, if the system partition is a mirrored volume, and a system-critical issue occurs, the following behavior occurs:
- A blue screen is not displayed.
- A memory dump file is not generated.
Additionally, the following event is logged in the System log:
Log Name: System
Source: volmgr
Event ID: 45
Task Category: None
Level: Error
Keywords: Classic
Description:
The system could not successfully load the crash dump driver.
September 30th, 2008 · No Comments · 562 views
Consider the following scenario on a Windows Vista-based or Windows Server 2008-based computer:
- You configure the computer to generate a complete memory dump file when the system crashes.
- You use the DedicatedDumpFile registry entry to specify the location for the dump file.
In this scenario, after the system crashes, the memory dump file may not be successfully generated. Instead, you find a file that is named dump.tmp file at the location that you specified for the dedicated dump file.
This problem occurs if both following conditions are true:
- The dedicated dump file and the system memory dump file are in the same volume.
- The free space on the volume that you specified for the dedicated dump file is less than two times the physical memory size of the computer.
June 11th, 2008 · No Comments · 591 views
Consider the following scenario:
- You configure the system to generate a full memory dump file when fatal system errors occur on a computer that is running Windows Server 2008 or Windows Vista.
- The dump file and the paging file are configured to reside on the same volume.
- Sufficient free disk space is available on the volume for the dump file. For example, 10 gigabytes (GB) of free disk space is sufficient to save a full memory dump file on a computer that has 8 GB of physical memory.
In this scenario, a memory dump file may not be generated when a fatal system error occurs. However, you find a DumpXXX.tmp file in the location that you specified to save the dump file.
This problem does not occur if the free disk space is larger than two times the size of the physical memory. Additionally, this problem does not occur if the Memory.dmp file already exists.
May 5th, 2008 · No Comments · 525 views
Consider the following scenario:
- On a computer that is running Windows Server 2008 or Windows Vista, you have more than 4 gigabytes (GB) of physical memory installed.
- The system is configured to generate a full memory dump file.
- The DedicatedDumpFile and DumpFileSize registry values are created. The value of the DumpFileSize parameter is larger than 4096.
In this scenario, the generated dump file is unexpectedly truncated to 4 GB.
Note: To deploy, troubleshoot, and service large memory platforms, OEM partners and customers may have to create large dump files.
April 24th, 2008 · No Comments · 508 views
Consider the following scenario:
- You are running a Windows Vista-based computer.
- An Intelligent Platform Management Interface (IPMI)-compliant baseboard management controller (BMC) is installed on the computer.
- Under the following registry subkey, you set the NMICrashDump registry entry to 1:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl
- The system receives a nonmaskable interrupt (NMI) that is generated for the BMC watchdog timer (WDT).
In this scenario, you expect the system to automatically restart. Instead, the system stops responding. Additionally, the IPMI driver does not save the stop event records on the BMC, and no memory dump file is generated.
Note: The NMICrashDump registry entry is an NMI switch that specifies whether the system performs standard software error-processing when a hardware error generates an NMI. When this registry entry is set to 1, the system should perform standard software error-processing. For example, the system might display a Stop error message in this situation.
April 4th, 2008 · No Comments · 1,224 views
-
Dr. Watson is not included in Windows Vista. The replacement for Dr. Watson is Problem Reports and Solutions. However, you cannot use Problem Reports and Solutions to create a full user-mode dump file.
-
This article describes how to contact a Microsoft Product Activation Center to activate installations of Windows XP, Windows Vista, and Microsoft Office suites and programs.
Keep reading →
April 4th, 2008 · No Comments · 487 views
Dr. Watson is not included in Windows Vista. The replacement for Dr. Watson is Problem Reports and Solutions. However, you cannot use Problem Reports and Solutions to create a full user-mode dump file. Keep reading →