Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

A Windows Server 2003-based computer becomes unresponsive because of a large memory allocation request


View products that this article applies to.

Symptoms

A Windows Server 2003-based computer becomes unresponsive for several seconds up to two minutes. During this time, all applications and services on the computer stop working.

When you monitor the working set size of a process, you may find that the working set size of the process decreases. This information indicates that the memory manager is trimming all processes on the computer to satisfy a large memory allocation request.

Typically, the trimming operation is triggered by the following functions:
  • MMAllocateContiguousMemory
  • MmAllocateContiguousMemorySpecifyCache
  • MmEmptyAllWorkingSets
Unfortunately, you cannot determine the driver or the module that triggers the large memory allocation request.

↑ Back to the top


Resolution

A hotfix is available to help you troubleshoot this issue. After you install this hotfix, tracing can be enabled at the MmEmptyAllWorkingSets function so that you can determine the exact driver or the module that triggers the large memory allocation request.

Hotfix information for Windows Server 2003

A 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 the problem described in this article. 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.

Prerequisites

To apply this hotfix, the computer must run Windows Server 2003 Service Pack 1 or Service Pack 2.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information


This hotfix replaces the hotfixes that are described in the following Microsoft Knowledge Base articles:
938486 A Windows Server 2003-based computer becomes unresponsive because of a memory manager trimming operation that is caused by an indeterminate module that requests lots of memory
This hotfix has been superseded by another hotfix. For more information about the new hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
956572 MS09-012: Description of the security update for Windows Service Isolation: April 2009


Note If you already have 956572 (GDR version) installed, you will want to uninstall 956572, restart the computer, and then reinstall MS09-012 (956572, QFE version) with the /B:SP2QFE switch.

Registry information

There are no prerequisites for installing this hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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 item in Control Panel.
Windows Server 2003 SP1, x86-based version
File nameFile versionFile sizeDateTimePlatformSP requirement
Ntkrnlmp.exe5.2.3790.32852,468,86421-Jan-200912:17Not ApplicableSP1
Ntkrnlpa.exe5.2.3790.32852,281,47221-Jan-200911:25x86SP1
Ntkrpamp.exe5.2.3790.32852,321,40821-Jan-200911:26Not ApplicableSP1
Ntoskrnl.exe5.2.3790.32852,427,90421-Jan-200912:17x86SP1
Windows Server 2003 SP2, x86-based version
File nameFile versionFile sizeDateTimePlatformSP requirement
Ntkrnlmp.exe5.2.3790.44492,498,56020-Jan-200914:30Not ApplicableSP2
Ntkrnlpa.exe5.2.3790.44492,309,63220-Jan-200913:21x86SP2
Ntkrpamp.exe5.2.3790.44492,350,59222-Jan-200905:50Not ApplicableSP2
Ntoskrnl.exe5.2.3790.44492,457,08820-Jan-200914:30x86SP2
Windows Server 2003 SP1, Itanium-based version
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Ntdll.dll5.2.3790.31911,636,35222-Jan-200905:39IA-64SP1Not Applicable
Ntkrnlmp.exe5.2.3790.32856,543,36022-Jan-200905:39IA-64SP1Not Applicable
Wntdll.dll5.2.3790.3191765,95222-Jan-200905:39x86SP1WOW
Windows Server 2003 SP2, Itanium-based version
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Ntdll.dll5.2.3790.43541,636,86422-Jan-200905:45IA-64SP2Not Applicable
Ntkrnlmp.exe5.2.3790.44496,578,17622-Jan-200905:45IA-64SP2Not Applicable
Wntdll.dll5.2.3790.4354766,46422-Jan-200905:45x86SP2WOW
Windows Server 2003 and Windows XP, x64-based version
File nameFile versionFile sizeDateTimePlatformSP requirement
Hal.dll5.2.3790.3191280,06422-Jan-200905:39x64SP1
Ntkrnlmp.exe5.2.3790.32854,654,59222-Jan-200905:39x64SP1
Ntoskrnl.exe5.2.3790.32854,507,13622-Jan-200905:39x64SP1
Windows Server 2003 SP2 and Windows XP SP2, x64-based version
File nameFile versionFile sizeDateTimePlatformSP requirement
Hal.dll5.2.3790.4354280,06422-Jan-200905:48x64SP2
Ntkrnlmp.exe5.2.3790.44494,611,58422-Jan-200905:48x64SP2
Ntoskrnl.exe5.2.3790.44494,537,85622-Jan-200905:48x64SP2

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
938486 A Windows Server 2003-based computer becomes unresponsive because of a memory manager trimming operation that is caused by an indeterminate module that requests lots of memory
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: kbautohotfix, kbexpertiseadvanced, kbfix, kbsurveynew, kbqfe, KB956341

↑ Back to the top

Article Info
Article ID : 956341
Revision : 6
Created on : 10/8/2011
Published on : 10/8/2011
Exists online : False
Views : 307