Memory Limits for Windows and Windows Server Releases

his topic describes the memory limits for supported Windows and Windows Server releases.

Limits on memory and address space vary by platform, operating system, and by whether theIMAGE_FILE_LARGE_ADDRESS_AWARE value of the LOADED_IMAGE structure and 4-gigabyte tuning (4GT) are in use.IMAGE_FILE_LARGE_ADDRESS_AWARE is set or cleared by using the /LARGEADDRESSAWARE linker option.

4-gigabyte tuning (4GT), also known as application memory tuning, or the /3GB switch, is a technology (only applicable to 32 bit systems) that alters the amount of virtual address space available to user mode applications. Enabling this technology reduces the overall size of the system virtual address space and therefore system resource maximums. For more information, see What is 4GT.

Limits on physical memory for 32-bit platforms also depend on the Physical Address Extension (PAE), which allows 32-bit Windows systems to use more than 4 GB of physical memory.

Memory and Address Space Limits

The following table specifies the limits on memory and address space for supported releases of Windows. Unless otherwise noted, the limits in this table apply to all supported releases.

Memory type Limit in on X86 Limit in 64-bit Windows

User-mode virtual address space for each 32-bit process


2 GB

Up to 3 GB with IMAGE_FILE_LARGE_ADDRESS_AWAREand 4GT


2 GB withIMAGE_FILE_LARGE_ADDRESS_AWAREcleared (default)

4 GB withIMAGE_FILE_LARGE_ADDRESS_AWAREset


User-mode virtual address space for each 64-bit process


Not applicable


With IMAGE_FILE_LARGE_ADDRESS_AWAREset (default):

x64:  8 TB

Intel Itanium-based systems:  7 TB

Windows 8.1 and Windows Server 2012 R2:  128 TB

2 GB withIMAGE_FILE_LARGE_ADDRESS_AWAREcleared


Kernel-mode virtual address space


2 GB

From 1 GB to a maximum of 2 GB with 4GT


8 TB

Windows 8.1 and Windows Server 2012 R2:  128 TB


Paged pool


384 GB or system commit limit, whichever is smaller.

Windows 8.1 and Windows Server 2012 R2:  15.5 TB or system commit limit, whichever is smaller.

Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista:  Limited by available kernel-mode virtual address space. Starting with Windows Vista with Service Pack 1 (SP1), the paged pool can also be limited by the PagedPoolLimit registry key value.

Windows Home Server and Windows Server 2003:  530 MB

Windows XP:  490 MB


384 GB or system commit limit, whichever is smaller

Windows 8.1 and Windows Server 2012 R2:  15.5 TB or system commit limit, whichever is smaller.

Windows Server 2008 R2, Windows 7, Windows Server 2008, and Windows Vista:  128 GB or system commit limit, whichever is smaller

Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM.


Nonpaged pool


75% of RAM or 2 GB, whichever is smaller.

Windows 8.1 and Windows Server 2012 R2:  RAM or 16 TB, whichever is smaller (address space is limited to 2 x RAM).

Windows Vista:  Limited only by kernel mode virtual address space and physical memory. Starting with Windows Vista with SP1, the nonpaged pool can also be limited by the NonPagedPoolLimit registry key value.

Windows Home Server, Windows Server 2003, and Windows XP:  256 MB, or 128 MB with 4GT.


RAM or 128 GB, whichever is smaller (address space is limited to 2 x RAM)

Windows 8.1 and Windows Server 2012 R2:  RAM or 16 TB, whichever is smaller (address space is limited to 2 x RAM).

Windows Server 2008 R2, Windows 7, and Windows Server 2008:  75% of RAM up to a maximum of 128 GB

Windows Vista:  40% of RAM up to a maximum of 128 GB.

Windows Server 2003 and Windows XP:  Up to 128 GB depending on configuration and RAM.


System cache virtual address space (physical size limited only by physical memory)


Limited by available kernel-mode virtual address space or the SystemCacheLimit registry key value.

Windows 8.1 and Windows Server 2012 R2:  16 TB.

Windows Vista:  Limited only by kernel mode virtual address space. Starting with Windows Vista with SP1, system cache virtual address space can also be limited by the SystemCacheLimit registry key value.

Windows Home Server, Windows Server 2003, and Windows XP:  860 MB with LargeSystemCache registry key set and without 4GT; up to 448 MB with 4GT.


Always 1 TB regardless of physical RAM

Windows 8.1 and Windows Server 2012 R2:  16 TB.

Windows Server 2003 and Windows XP:  Up to 1 TB depending on configuration and RAM.

Physical Memory Limits: Windows 8

The following table specifies the limits on physical memory for Windows 8.

Version Limit on X86 Limit on X64
Windows 8 Enterprise
4 GB


512 GB

Windows 8 Professional
4 GB


512 GB

Windows 8
4 GB


128 GB

Physical Memory Limits: Windows Server 2012

The following table specifies the limits on physical memory for Windows Server 2012. Windows Server 2012 is available only in X64 editions.

Version Limit on X64
Windows Server 2012 Datacenter
4 TB

Windows Server 2012 Standard
4 TB

Windows Server 2012 Essentials
64 GB

Windows Server 2012 Foundation
32 GB

Windows Storage Server 2012 Workgroup
32 GB

Windows Storage Server 2012 Standard
4 TB

Hyper-V Server 2012
4 TB

Physical Memory Limits: Windows 7

The following table specifies the limits on physical memory for Windows 7.

Version Limit on X86 Limit on X64
Windows 7 Ultimate
4 GB


192 GB

Windows 7 Enterprise
4 GB


192 GB

Windows 7 Professional
4 GB


192 GB

Windows 7 Home Premium
4 GB


16 GB

Windows 7 Home Basic
4 GB


8 GB

Windows 7 Starter
2 GB


N/A

Physical Memory Limits: Windows Server 2008 R2

The following table specifies the limits on physical memory for Windows Server 2008 R2. Windows Server 2008 R2 is available only in 64-bit editions.

Version Limit on X64 Limit on IA64
Windows Server 2008 R2 Datacenter
2 TB

 
Windows Server 2008 R2 Enterprise
2 TB

 
Windows Server 2008 R2 for Itanium-Based Systems  
2 TB

Windows Server 2008 R2 Foundation
8 GB

 
Windows Server 2008 R2 Standard
32 GB

 
Windows HPC Server 2008 R2
128 GB

 
Windows Web Server 2008 R2
32 GB

 

Physical Memory Limits: Windows Server 2008

The following table specifies the limits on physical memory for Windows Server 2008. Limits greater than 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit on X86 Limit on X64 Limit on IA64
Windows Server 2008 Datacenter
64 GB


1 TB

 
Windows Server 2008 Enterprise
64 GB


1 TB

 
Windows Server 2008 HPC Edition  
128 GB

 
Windows Server 2008 Standard
4 GB


32 GB

 
Windows Server 2008 for Itanium-Based Systems    
2 TB

Windows Small Business Server 2008
4 GB


32 GB

 
Windows Web Server 2008
4 GB


32 GB

 

Physical Memory Limits: Windows Vista

The following table specifies the limits on physical memory for Windows Vista.

Version Limit on X86 Limit on X64
Windows Vista Ultimate
4 GB


128 GB

Windows Vista Enterprise
4 GB


128 GB

Windows Vista Business
4 GB


128 GB

Windows Vista Home Premium
4 GB


16 GB

Windows Vista Home Basic
4 GB


8 GB

Windows Vista Starter
1 GB

 

Physical Memory Limits: Windows Home Server

Windows Home Server is available only in a 32-bit edition. The physical memory limit is 4 GB.

Physical Memory Limits: Windows Server 2003 R2

The following table specifies the limits on physical memory for Windows Server 2003 R2. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit on X86 Limit on X64

Windows Server 2003 R2 Datacenter Edition


64 GB

(16 GB with 4GT)


1 TB


Windows Server 2003 R2 Enterprise Edition


64 GB

(16 GB with 4GT)


1 TB


Windows Server 2003 R2 Standard Edition


4 GB


32 GB

Physical Memory Limits: Windows Server 2003 with Service Pack 2 (SP2)

The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 2 (SP2). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit on X86 Limit on X64 Limit on IA64

Windows Server 2003 with Service Pack 2 (SP2), Datacenter Edition


64 GB

(16 GB with 4GT)


1 TB


2 TB


Windows Server 2003 with Service Pack 2 (SP2), Enterprise Edition


64 GB

(16 GB with 4GT)


1 TB


2 TB


Windows Server 2003 with Service Pack 2 (SP2), Standard Edition


4 GB


32 GB

 

Physical Memory Limits: Windows Server 2003 with Service Pack 1 (SP1)

The following table specifies the limits on physical memory for Windows Server 2003 with Service Pack 1 (SP1). Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit on X86 Limit on X64 Limit on IA64

Windows Server 2003 with Service Pack 1 (SP1), Datacenter Edition


64 GB

(16 GB with 4GT)


X64 1 TB


1 TB


Windows Server 2003 with Service Pack 1 (SP1), Enterprise Edition


64 GB

(16 GB with 4GT)


X64 1 TB


1 TB


Windows Server 2003 with Service Pack 1 (SP1), Standard Edition


4 GB


32 GB

 

Physical Memory Limits: Windows Server 2003

The following table specifies the limits on physical memory for Windows Server 2003. Limits over 4 GB for 32-bit Windows assume that PAE is enabled.

Version Limit on X86 Limit on IA64

Windows Server 2003, Datacenter Edition


64 GB

(16 GB with 4GT)


512 GB


Windows Server 2003, Enterprise Edition


64 GB

(16 GB with 4GT)


512 GB


Windows Server 2003, Standard Edition


4 GB

 

Windows Server 2003, Web Edition


2 GB

 

Windows Small Business Server 2003


4 GB

 

Windows Compute Cluster Server 2003

 
32 GB


Windows Storage Server 2003, Enterprise Edition


8 GB

 

Windows Storage Server 2003


4 GB

 

Physical Memory Limits: Windows XP

The following table specifies the limits on physical memory for Windows XP.

Version Limit on X86 Limit on X64 Limit on IA64
Windows XP
4 GB


128 GB


128 GB (not supported)

Windows XP Starter Edition
512 MB


N/A


N/A

Physical Memory Limits: Windows Embedded

The following table specifies the limits on physical memory for Windows Embedded.

Version Limit on X86 Limit on X64

Windows XP Embedded


4 GB

 

Windows Embedded Standard 2009


4 GB

 

Windows Embedded Standard 7


4 GB


192 GB

How graphics cards and other devices affect memory limits

Devices have to map their memory below 4 GB for compatibility with non-PAE-aware Windows releases. Therefore, if the system has 4GB of RAM, some of it is either disabled or is remapped above 4GB by the BIOS. If the memory is remapped, X64 Windows can use this memory. X86 client versions of Windows don’t support physical memory above the 4GB mark, so they can’t access these remapped regions. Any X64 Windows or X86 Server release can.

X86 client versions with PAE enabled do have a usable 37-bit (128 GB) physical address space. The limit that these versions impose is the highest permitted physical RAM address, not the size of the IO space. That means PAE-aware drivers can actually use physical space above 4 GB if they want. For example, drivers could map the "lost" memory regions located above 4 GB and expose this memory as a RAM disk.

Related topics

4-Gigabyte Tuning
IMAGE_FILE_LARGE_ADDRESS_AWARE
Physical Address Extension

原文:http://msdn.microsoft.com/en-us/library/windows/desktop/aa366778(v=vs.85).aspx#physical_memory_limits_windows_8

Memory Limits for Windows and Windows Server Releases

时间: 2024-10-24 09:46:17

Memory Limits for Windows and Windows Server Releases的相关文章

Windows Server2016+SQL Server 2016 Cluster安装及配置

Windows Server2016+SQL Server 2016 Cluster 安装及配置 我们知道,近期微软正式发布了Windows Server2016和SQL Server Cluster 2016,所以借此机会来尝试一下Windows Server2016+SQL Server Cluster 2016安装及配置,对于相关功能的优化及升级需要在官网上自己查看整理.大概就是windows server2016跟windows10页面框架结构差不多,SQL Server2016从安装上

windows (windows server 2003 64位)开启 curl扩展 (php-5.4.5-Win32-VC9-x86.zip,httpd-2.2.22-win32-x86-no_ssl.msi ,mysql-5.5.27-win32.msi)

(1)在windows下开启curl扩展,php.ini中 extension_dir路径是对的,extension=php_curl.dll前面的分号也去掉了,php加载的php.ini也是对,但是就是没有效果,上网百度,解决了. 需要将php目录中的libeay32.dll, ssleay32.dll, php5ts.dll, 文件到 system32 目录.重启apache即可. (2)在windows server 2003 64位 中  需要将libeay32.dll, ssleay3

Windows 7或者 server 小技巧 添加 IIS和FTP 组件功能

Windows 7或者 server 小技巧  添加 IIS和FTP 组件功能 在万能的 控制面版 ,添加删除 组件中 . 在IE中输入  http://127.0.0.1 或者 http://localhost 打开如下图片,即表示安装成功. 在控制面版,管理工具中可以打开 IIS管理器.

Windows Server2016+SQL Server Cluster 2016安装及配置

我们知道,近期微软正式发布了Windows Server2016和SQL Server Cluster 2016,所以借此机会来尝试一下Windows Server2016+SQL Server Cluster 2016安装及配置,对于相关功能的优化及升级需要在官网上自己查看整理.今天主要介绍一下Windows Server2016+SQL Server Cluster 2016安装及配置的详情介绍.具体见下: 环境介绍: Hostname:DC IP:192.168.5.10 Role:DC.

VMware ESXi 5.5无法与Windows 2012 NTP Server同步时间

这次笔者需要面对的环境对时间的同步有比较高的要求, 而虚拟化的环境中时间是比较容易出问题的, 您可以参考上一篇博文为什么Domain controller上的time synchronization非常重要? 笔者的环境里, 经过亲自观察, 如果没有时间同步, 虚拟机与标准时间差距在短短的两个小时之内竟然就偏差了近半个小时!   按照VMware KB 1003063的说法, ESXi 5.5只要在vCenter的vSphere里配好NTP client就可以了. Note: For ESX 3

在Windows 2008 R2 Server中,上传视频遇到的问题

在Windows 2008 R2 Server中,上传视频不能播放,以及服务器大小限制问题,这里记录我的解决方法,以免再次遇到,无所适从. 1.上传视频不能播放 打开IIS,找到"MIME类型",如下: 双击"MIME类型",在右上角,点击"添加",如下: 点击确定,如下: 注:其他类型视频,一样如上添加. 2.上传大视频(这里45M),报404 在web.config文件的<system.web>节点中添加<httpRunti

Windows 2008 R2 Server FTP使用问题

 Windows 2008 R2 Server FTP必须在安装IIS的时候.安装IIS6.0兼职性. 否则建的FTP网站仅仅有关了防火墙才干使用. 原因未知.

Windows 2008 R2 Server激活方法

最近工作测试需要安装了Windows 2008 R2 Server,但是Mircro Soft只给了10天的试用期,所以采用以下方式激活使用 激活工具:Windows Loader 下载地址: http://down.51cto.com/data/359318 下载后安装运行后,就可以用于激活Windows 2008 Server. 只有10天的试用期 下载安装Windows Loader 安装完后提示重启系统 系统重启后,显示已被激活 font 声明:以上方法,只是用于测试:切勿用于生产环境,

从Windows迁移SQL Server到Linux

原文:从Windows迁移SQL Server到Linux 前一篇博客关于SQL Server on Linux的安装,地址:http://www.cnblogs.com/fishparadise/p/8057650.html,现在测试把Windows平台下的一个数据库迁移到Linux平台下. 1. 环境 Windows: Microsoft SQL Server 2008 R2 (SP3) - 10.50.6000.34 (X64) Linux: CentOS 7.4,SQL Server 2