I know that Windows XP 32-bit can be configured, through PAE, to support more than 3.5 GB of RAM. Is there a good tutorial to do this with Windows 7 32-bit?

As to why I don't simply use 64-bit Windows 7: The software for my Internet connection (cell phone-as-modem) will only work in 32-bit environments.

  • Unless you are using applications that are specifically designed to take advantage of the 36-bit PAE extensions in the CPU and the AWE API, there is absolutely NO point in using the PAE switch.
    – Molly7244
    Oct 7, 2009 at 15:00
  • 17
    Molly: Actually there is a point to PAE even with apps that are not aware of 36-bit addressing. Even though each app can only access 2GB of memory, you can run multiple apps, each with their own 2GB.
    – davr
    Oct 7, 2009 at 17:17
  • @Molly7244 AWE and PAE have nothing to do with each other. And there is a point to using PAE without extended RAM, and that is to enable hardware No-Execute protection. On an x86 processor there is no NX without PAE. May 11, 2017 at 15:47
  • @JamieHanrahan AWE uses PAE. Aug 13, 2018 at 13:45
  • @ctrl-alt-delor Sorry, but that is clearly a misunderstanding, because AWE works on 32-bit Windows systems that don't have PAE enabled. Heck, AWE even works on systems where PAE isn't even an option (x64, ARM, Itanium - those CPUs don't support PAE). It is true that on a 32-bit x86 Windows system without PAE enabled, an AWE-aware app won't find much RAM to let you open "windows" into, but it'll work within the available RAM. AWE does not at all depend on PAE; it's just that on x86, having PAE + more than 4 GB RAM supported will give more RAM for AWE (and everything else) to work in. Aug 13, 2018 at 20:12

9 Answers 9


A few years ago, a group of programmers have released a kernel patch for Windows 7 to allow the usage of more than 4 GB of RAM under Windows 7. Recently, due to some virus scanners detecting the patch as a false positive, the download was removed from the website. Fortunately, I have saved a copy of the patch (which uses the RTM Windows 7 kernel), and uploaded it to my website here (see option #1 when I discuss the two methods to patch your Windows kernel). Furthermore, the authors have posted instructions on how to patch your kernel manually.

Even if you have Windows 7 SP1 (Build 7601), you can install the patch which contains kernel 7600. This is because your default kernel is not modified; a new one is copied to your system folder, and an additional boot menu option is added to boot Windows with the new, patched kernel instead of the older one. While I haven't found any problems running Windows 7 SP1 with the older kernel, if you do wish to use build 7601 of ntkrnlpa.exe, you need to manually patch your kernel (see the link above).

The patch basically modifies the Windows 7 Kernel to be more like the Windows Server 2003 Datacenter Edition, which is compatible with up to 8 GB of RAM under 32-bit mode. This allows you to extend the PAE well into 8 GB of RAM under Windows 7 32-bit. For more information about why Microsoft implemented this technical limitation, see Licensed Memory in 32-Bit Windows Vista (requires JavaScript to be allowed from www.geoffchappell.com).

As mentioned above, note that individual processes will still be limited to 4 GB even if the system can access more... Although if you had 8 GB of RAM, then at least you'd still have another 4 GB for other processes ;)

For those interested in the technical aspects, this happens because of memory-mapped input/output (MMIO for short). This allows a CPU to access both peripherals and RAM through the address bus itself. Usually this is done though the higher-order memory addresses to avoid lower-order address conflicts. However, this gave rise to the commonly known 3 GB Memory Barrier in all consumer variants of 32-bit Windows operating systems.

  • 5
    Warning: that first link has some NSFW content.
    – Jon Seigel
    Jan 25, 2011 at 15:44
  • 1
    Warning added to response, thank you. I didn't even notice that :S Jan 31, 2011 at 12:56
  • Any information on whether this works well or is unreliable? Aug 23, 2011 at 21:38
  • 1
    @Mark Gibaud I used it for a year with no problems. I only had 4GB of RAM, but at least I was able to use the whole thing. Do note that the patch modifies the Windows Kernel, so I would make a backup before you patch your system. That being said, I never had a problem (I applied the patch on both my desktop and laptop a few times with no problems, even after everything was installed). Aug 23, 2011 at 21:42
  • 1
    @Breakthrough: This is amazing. Do you happen to know how to get XP to do something similar?
    – user541686
    Aug 29, 2011 at 7:02

This article at Microsoft's MSDN site shows the memory limits for versions of Windows and Windows 7 32-bit is listed as a 4 GB limit.

You used to be able to use PAE to see more than 4 GB of RAM with Windows XP but this option was disabled in Service Pack 2.

The reason was that most drivers weren't PAE aware and threw their toys out of their pram if they ended up in memory above the 4 GB boundary.

If you use the /PAE switch now on Windows XP you'll make DEP available, but you won't be able to see more than 4 GB of RAM.

This 4 GB limit is still in place for Windows 7 32-bit. If you want to see more than 4 GB of RAM you will have to use a 64-bit version of Windows.

(This option to use PAE to see more than 4 GB of RAM is still available on 32-bit Server versions of Windows which I assume is down to a better quality of drivers expected for the kind of hardware you'd run Windows Server on.)

  • 2
    I think the Server support is less due to better driver quality and more due to the fact that system administrators will be able to handle the situation much better than a mom. Oct 7, 2009 at 14:56
  • 1
    "The reason was that most drivers weren't PAE aware and threw their toys out of their pram if they ended up in memory above the 4GB boundary." - Does this apply to Windows 7 32bit as much (using the kernel hack)? Aug 23, 2011 at 21:56
  • 2
    The great Mark Russinovich explains the rationale behind the client and server memory limits under windows in his "Pushing the Limits of Windows" series of blog posts. blogs.technet.com/b/markrussinovich/archive/2008/07/21/… Aug 29, 2011 at 7:28
  • Does the 4GB windows7 limit include hardware. I have set up PAE and get about 3.15GB. Is there about 1GB of (potential)hardware using up the rest and ms-windows blocking use of more that 4GB. On Gnu/Linux I get all 4GB. Jan 26, 2012 at 13:06
  • @richard - the address limit includes address space needed for other hardware, most notable graphics cards which can eat up a lot of the 4GB.
    – David Webb
    Jan 27, 2012 at 3:55

PAE should be enabled by default - Windows already uses it internally for the DEP/No-Execute feature.

But these instructions might help if Windows is doing its thing again.

Note that individual processes will still be limited to 4 GB even if the system can access more.

  • That link is wrong. Vista 32-bit only uses PAE for DEP and does not allow you to see more than 4GB of RAM. support.microsoft.com/kb/929605
    – David Webb
    Oct 7, 2009 at 14:48
  • But Niphoet (the asker) uses Windows 7, which has a limit of 8 GB (Home Basic; even more in other versions). Oct 7, 2009 at 16:29
  • @grawity: yes, it's 8GB if you're using 64-bit Windows 7. The limit is still 4GB in 32-bit Windows 7.
    – Joshua
    Oct 7, 2009 at 17:05

According to the MSDN article Physical Address Extension:

Windows automatically enables PAE if DEP is enabled on a computer that supports hardware-enabled DEP, or if the computer is configured for hot-add memory devices in memory ranges beyond 4 GB. If the computer does not support hardware-enabled DEP or is not configured for hot-add memory devices in memory ranges beyond 4 GB, PAE must be explicitly enabled.

To explicitly enable PAE, use the following BCDEdit /set command to set the pae boot entry option:

bcdedit /set [{ID}] pae ForceEnable

IF DEP is enabled, PAE cannot be disabled. Use the following BCDEdit /set commands to disable both DEP and PAE:

bcdedit /set [{ID}] nx AlwaysOff
bcdedit /set [{ID}] pae ForceDisable

Windows Server 2003 and Windows XP: To enable PAE, use the /PAE switch in the boot.ini file. To disable PAE, use the /NOPAE switch. To disable DEP, use the /EXECUTE switch.


If your system can support it, you can use virtualization to allow access to your 32-bit phone drivers.

It would be a slightly more complicated setup but you could set up a virtual machine that made the connection and did internet connection sharing to your host, that way you get the benefits of 64-bit as well as being able to use legacy drivers.

VMware Workstation (commercial), VirtualBox (free, open source), and Windows Virtual PC (free) can all route usb devices directly into your virtual machine. Just install a 32-bit OS (even XP if you wanted), give it a marginal amount of RAM and you can do what you need. I've done this to load legacy applications that didn't support Windows 7 and my brother actually loaded his old Creative webcam (with no 64-bit drivers) and used Skype through his virtual machine.

  • He's got Windows 7...you completely forgot to mention "XP Mode", which is the new free virtualization feature included in Windows 7.
    – davr
    Oct 7, 2009 at 17:18
  • I didn't directly mention XP mode since they didn't say if they were running 7 Professional or Ultimate (it's unavailable for the other SKUs) :)
    – Joshua
    Oct 7, 2009 at 17:24

Windows 7 32 has PAE disallowing access past the 4 GB mark. See http://msdn.microsoft.com/en-us/library/aa366778(VS.85).aspx for details.

For people out there who insist on 64 bit usage - there are some things that would not work in 64 bit environments that could benefit a performance gain from a ram disk that COULD access past the 3.25 mark in a 32 bit environment - specifically applications that page often. You could also put the page file within said ramdisk. In addtion, a VM is great, however emulation never really works as great as the real thing -- it all really depends on the application and the way it is implemented. There are still many hardware devices that will not work in a 64 bit world, and need the real time access to make them work well (while there are accelerators that help with real time access, it can still present problems.)

So, while 64 bit is technically superior, 32 bit is a legacy that will take a while go away, and there will be plenty of reason why people would like to access memory through PAE.

PS: There is a reply to this post stating that putting a page file on RAM disk makes no sense. Let me explain. If the system has 4GB RAM and you make a 2GB RAM disk and put the page file there, then yes, this configuration makes no sense. However, if the system has 8GB RAM and you make a 4GB RAM disk (accessing the extra memory that 32 bit Windows can not reach) and put the page file (and temp folder, and turn on "ReadyBoost" and add any other frequently used files) on there, then yes, the speed up is very considerable. And "yes" is the answer, you can get software that allows you to create RAM disks above the 4GB limit on 32bit systems.

  • 5
    Putting your pagefile on a RAMdisk makes no sense. Aug 29, 2011 at 7:11
  • Putting your pagefile on a RAMdisk makes no sense only when RAM is available normally in the system, which is not this case. Jun 11, 2015 at 6:56

DO NOT USE THE PATCH, its simply a german test version of windows, and will muck up youre boot record.

I have just spent an hour downloading easybcd on another machine to fix this.

Be warned!

  • The 'patch' is quite simple to do yourself and you don't need 'easybcd' to fix your boot records :: it's quite trivial to fix your boot record with bcdedit.exe ... RTFM Feb 2, 2013 at 6:46

The question is “How can I enable PAE on Windows 7 (32-bit) to support more than 3.5 GB of RAM” and the answer is type the command prompt “bcdedit /set [{ID}] pae ForceEnable”.

But, probably the question is worthy to be rephrased how to enable and be able to use more than 3.5 (or 3.25) GB of RAM on W7 32 bits system.

I tried PAE in 2 different Desktop mainboards with identical systems: Intel® Desktop Board D945GNT with a Intel® Pentium® D Processor 3.4GHZ and 3.00GB usable Ram, and Intel® Desktop Board DG41WV with Intel® E7500 2.93GHZ and 3.25GB usable Ram. Both 64 bits capable and 4GB Ram.

The 2 systems enabled PAE; then, using the procedure indicated in http://www.jensscheffler.de/using-gavotte-ramdisk-in-windows-7 I installed Gavotte Ram disk and recovered 16MB Ram (nothing) on the first system, but recovered the entire 775MB unused for the second one.

So, in the Ram disk of the second system, I assigned a movable pagesys file to it, from 16MB to 700MB, and a movable pagesys of 16MB to 3300MB on a partition of a different physical disk of the system.

I proved 2 facts: 1. The systems preferred the Ram swap file over the one in the hard disk. I saw it moving, growing and shrinking. 2. Benchmark with PC Pitstop (image attached in http://www.pablomolina.net/bench700.png) shows great improvement in system disk speed, and the system runs quite faster. In the bench I compared a 700 MB page file in the Ram disk with a 700MB page file in another partition of the same system drive.!

You need to set the system to clean page file at shutdown with Microsoft kb/314834 procedure.

For me, PAE makes sense on a 32 bit system, and works. I won´t go for the 64 bits system as I use Windows professionally and accumulated 450 programs over years, which will take me months to reinstall.


If you don't want to a patch files, you can use a boot loader. This Bootloader can be installed on the current system or an an USB pen drive. So you can easily test it without effecting your system.

enter image description here

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .