Article ID: 319931 - View products that this article applies to.
This article was previously published under Q319931
This article has been archived. It is offered "as is" and will no longer be updated.
After you start your Windows 2000-based computer, you may receive the following entry in the System Event log:
You may also experience failures in Device Manager for devices that cannot allocate memory that is needed to function properly.
Event ID: 49
Description: Configuring the Page file for crash dump failed. Make sure there is a page file on the boot partition and that is large enough to contain all physical memory.
This problem is caused by a bug in the Memory Manager when it tries to allocate a contiguous run of free memory.
Service Pack InformationTo resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/260910/EN-US/ )How to Obtain the Latest Windows 2000 Service Pack
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.
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, submit a request to 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:
http://support.microsoft.com/contactus/?ws=supportNote 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. The English version of this fix should have the following file attributes or later:
Date Time Version Size Filename ----------------------------------------------------------- 01-Apr-2002 16:07 5.0.2195.5505 1,687,296 Ntkrnlmp.exe 01-Apr-2002 16:08 5.0.2195.5505 1,686,912 Ntkrnlpa.exe 01-Apr-2002 16:08 5.0.2195.5505 1,707,584 Ntkrpamp.exe 01-Apr-2002 16:07 5.0.2195.5505 1,665,024 Ntoskrnl.exe
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.
IMPORTANT: Although the error in the Event Log may indicate that this is a general error message, you must apply this hotfix to critical systems such as computers that are running Windows 2000 Datacenter Server. Memory dumps are generally used by Microsoft Support to determine the root cause, if possible, of a failing system. Without the installation of this hotfix, it may be impossible to determine why a system has generated a bug check.
On startup, system devices request memory allocations that are managed by the Memory Manager. In some cases, these allocations must be contiguous. If Memory Manager cannot grant a contiguous request, the system may generate an Event ID 49.
For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:
265173For additional information about how to install multiple hotfixes with only one reboot, click the article number below to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/265173/EN-US/ )The Datacenter Program and Windows 2000 Datacenter Server Product
(http://support.microsoft.com/kb/296861/EN-US/ )Use QChain.exe to Install Multiple Hotfixes with One Reboot
Article ID: 319931 - Last Review: February 27, 2014 - Revision: 2.7
Contact us for more help