Memory-Dump Operation Does Not Complete on Computers with More Than 6 GB of RAM Installed
This article has been archived. It is offered "as is" and will no longer be updated.
When Windows unexpectedly stops responding (hangs) and is configured to write debugging information to the Memory.dmp file, the memory-dump operation may not complete successfully. Additionally, you may experience one or both of the following symptoms:
- The memory-dump operation stops responding when it is about 90-percent complete.
- Windows does not automatically restart after the memory-dump operation stops responding.
This problem may occur if you have more than 6 gigabytes (GB) of random access memory (RAM) installed in the computer.
The memory-dump process stops responding in a large memory-dump operation because the ScsiPortGetPhysicalAddress() routine in the Diskdump.sys file returns a value of 0xcb000 instead of 0x1000cb000 to the miniport adapter driver.
Hotfix InformationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesNo prerequisites are required to install this hotfix.
Restart RequirementYou must restart your computer to apply the changes after you install this hotfix. However, you do not have to restart the computer immediately after installing this hotfix. If you want to restart later, click to select the Do not restart now check box in the Windows Server 2003 KB822998 Setup Wizard, and then click Finish.
Hotfix Replacement InformationThis hotfix does not replace any other hotfixes.
File InformationThe English version of this fix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003
Date Time Version Size File name-----------------------------------------------------------23-Jun-2003 23:46 5.2.3790.66 17,920 Diskdump.sys
Windows Server 2003 64-Bit
Date Time Version Size File name-----------------------------------------------------------23-Jun-2003 23:46 5.2.3790.66 47,104 Diskdump.sys
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
This hotfix resolves this problem by using 64-bit arithmetic for the PHYSICAL_ADDRESS calculation.
Article ID: 822998 - Last Review: 01/10/2015 14:09:57 - Revision: 10.0
Microsoft Windows Server 2003, Enterprise Edition (32-bit x86), Microsoft Windows Server 2003, Enterprise x64 Edition
- kbnosurvey kbarchive kbautohotfix kbhotfixserver kbqfe kbbug kbfix kbwinserv2003presp1fix KB822998