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.

Windows Server 2008 R2 cannot be installed or started on a computer that has 1 TB or more of RAM


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You install 1 terabyte or more of memory on a computer. For example, assume that you have 64 memory slots and that each slot has 16 gigabytes (GB) of RAM.
  • You try to install or start an x64-based version of Windows Server 2008 R2 on this computer.
In this scenario, you cannot install or start an x64-based version of Windows Server 2008 R2 on this computer.

↑ Back to the top


Cause

This issue occurs because the hardware stores information at some physical addresses that are beyond the 1 terabyte address. These physical addresses are more than 40 bits long. When these physical addresses are mapped to the page tables for Windows, they are truncated to 40 bits to comply with the definition for a page table entry. This behavior prevents the installation or startup process of an x64-based version of Windows Server 2008 R2.

↑ Back to the top


Resolution

Hotfix information

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, your computer must be running Windows Server 2008 R2.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
Important
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Setbcdlocale.dll6.1.7600.1638562,97614-Jul-200901:41x64
Bootmgr.efi6.1.7600.20642667,53612-Feb-201009:55Not Applicable
Winload.efi6.1.7600.20642640,91212-Feb-201009:55Not Applicable
Winload.exe6.1.7600.20642603,99212-Feb-201009:52x64
Winresume.efi6.1.7600.20642556,93612-Feb-201009:56Not Applicable
Winresume.exe6.1.7600.20642518,17612-Feb-201009:52x64
Wdsmgfw.efi6.1.7600.20642527,87212-Feb-201005:41Not Applicable
Bootmgfw.efi6.1.7600.20642671,11212-Feb-201009:55Not Applicable
Wdsmgfw.efi6.1.7600.20642527,87212-Feb-201005:41Not Applicable
Hal.dll6.1.7600.20642263,05612-Feb-201009:55x64
Ntoskrnl.exe6.1.7600.206425,485,45612-Feb-201009:55x64
Abortpxe.comNot Applicable7910-Jun-200921:44Not Applicable
Bootmgr.exe6.1.7600.20642523,14412-Feb-201020:19x86
Hdlscom1.comNot Applicable26,07610-Jun-200921:15Not Applicable
Hdlscom1.n12Not Applicable26,06010-Jun-200921:15Not Applicable
Hdlscom2.comNot Applicable26,07610-Jun-200921:15Not Applicable
Hdlscom2.n12Not Applicable26,06010-Jun-200921:15Not Applicable
Pxeboot.comNot Applicable25,77210-Jun-200921:15Not Applicable
Pxeboot.n12Not Applicable25,77210-Jun-200921:15Not Applicable
Wdsnbp.comNot Applicable31,12410-Jun-200921:44Not Applicable
Ntkrnlpa.exe6.1.7600.206423,954,06412-Feb-201020:19Not Applicable
Ntoskrnl.exe6.1.7600.206423,899,78412-Feb-201020:19Not Applicable

↑ 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 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

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-b..environment-windows_31bf3856ad364e35_6.1.7600.20642_none_c5df683abf7b830f.manifestNot Applicable6,89415-Feb-201019:16Not Applicable
Amd64_microsoft-windows-b..ore-bootmanager-efi_31bf3856ad364e35_6.1.7600.20642_none_e427b9e7cf10c00e.manifestNot Applicable4,11812-Feb-201021:08Not Applicable
Amd64_microsoft-windows-b..vironment-os-loader_31bf3856ad364e35_6.1.7600.20642_none_b7cd8b429f57c53e.manifestNot Applicable5,74512-Feb-201021:07Not Applicable
Amd64_microsoft-windows-bootenvironment-pxe_31bf3856ad364e35_6.1.7600.20642_none_49f9a51dc47b49bb.manifestNot Applicable3,83712-Feb-201021:13Not Applicable
Amd64_microsoft-windows-d..ices-boot-files-x64_31bf3856ad364e35_6.1.7600.20642_none_18ce40f8f0f5d3b2.manifestNot Applicable4,40212-Feb-201021:08Not Applicable
Amd64_microsoft-windows-hal_31bf3856ad364e35_6.1.7600.20642_none_07cfc3b48c5b1c4b.manifestNot Applicable7,54912-Feb-201021:08Not Applicable
Amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.20642_none_c8d732b0e6d3f75e.manifestNot Applicable15,29112-Feb-201021:17Not Applicable
Package_for_kb980598_rtm~31bf3856ad364e35~amd64~~6.1.1.0.mumNot Applicable2,94615-Feb-201019:16Not Applicable
X86_microsoft-windows-bootenvironment-pxe_31bf3856ad364e35_6.1.7600.20642_none_eddb099a0c1dd885.manifestNot Applicable9,87912-Feb-201020:45Not Applicable
X86_microsoft-windows-d..ices-boot-files-x64_31bf3856ad364e35_6.1.7600.20642_none_bcafa5753898627c.manifestNot Applicable9,82712-Feb-201020:37Not Applicable
X86_microsoft-windows-d..ices-boot-files-x86_31bf3856ad364e35_6.1.7600.20642_none_bcb178793896c86c.manifestNot Applicable9,82712-Feb-201020:50Not Applicable
X86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.20642_none_6cb8972d2e768628.manifestNot Applicable16,15112-Feb-201020:50Not Applicable

↑ Back to the top


Keywords: kbqfe, kbsurveynew, kbautohotfix, kbexpertiseinter, kbexpertisebeginner, kbexpertiseadvanced, kbbug, kbfix, kbhotfixserver, KB980598

↑ Back to the top

Article Info
Article ID : 980598
Revision : 2
Created on : 5/12/2010
Published on : 5/12/2010
Exists online : False
Views : 442