We do not recommend that you disable PAE mode.
We recommend that you disable PAE mode only to work around a hardware issue or to troubleshoot a specific issue that involves PAE or Address Windowing Extensions (AWE). Some features in hardware, such as the security features that are described in this article, depend on the PAE kernel for implementation. Contact your hardware vendor for information that is relevant to a specific model of computer.
Starting with Windows XP SP2 and later versions of Windows XP, the 32-bit versions of Windows use one of the following hardware technologies to implement DEP:
- The no-execute page-protection (NX) processor feature as defined by Advanced Micro Devices.
- The Execute Disable Bit (XD) feature as defined by Intel.
Note To support DEP, Windows will automatically load the PAE kernel. You do not have to use the /PAE boot switch in the Boot.ini file.
How to disable PAE modeWarning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.
To troubleshoot a system, you may have to disable PAE mode on a computer where Windows has automatically enabled PAE mode. In this scenario, you can disable PAE mode by editing the Boot.ini file.
Disable PAE mode in Windows Server 2003 with SP1 and later versions of Windows Server 2003Add the following switches to the Windows Server 2003 Boot.ini file:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows Server 2003" /fastdetect /execute /NOPAE
Disable PAE mode in Windows XP with SP2 and later versions of Windows XPAdd the following switches to the Windows XP Boot.ini file:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP" /fastdetect /noexecute=alwaysoff /NOPAE
For more information about how to edit the Boot.ini file, click the following article number to view the articles in the Microsoft Knowledge Base: