PAE patch updated for Windows 7 SP1

Note: An updated version for Windows 8 is available.

This patch allows you to use more than 3/4GB of RAM on an x86 Windows system. Works on Vista and 7, has been tested on Windows Vista SP2, Windows 7 SP0 and Windows 7 SP1. Instructions and source code included.

Note: I do not offer any support for this. If this did not work for you, either:

• You cannot follow instructions correctly, or
• You cannot use more than 4GB of physical memory on 32-bit Windows due to hardware/software conflicts.

To remove the patch:

1. Run msconfig, click Boot, highlight the entry named “Windows 7 (PAE Patched)”, and click Delete.
2. Delete the files ntkrnlpx.exe and winloadp.exe from C:\Windows\system32.
This entry was posted in Hardware, Programming, Windows. Bookmark the permalink.

121 Responses to PAE patch updated for Windows 7 SP1

1. ruddj says:

Great job and quick release. Will this version fix the Intel HD Graphics version?

• wj32 says:

I don’t know what the problem actually is or what’s causing it…

• Big Boy says:

You see, this is the reason why MS disabled more than 4GB on 32-bit systems. Because of fishy drivers that can’t handle memory above 4GB. The fault is Intel driver, not the PAE patch.

Now, some versions of Windows Server do support more than 4GB on 32-bit. You may try Intel HD drivers for those versions of Windows. Note that I have NO IDEA if it will work or not! Basically you are at the mercy of the driver maker.

• Well, I have dug deeply the internet and from what we have found the following problems:
Microsoft has put a restriction of 4 Gb memory on all 32-bit versions of their operating systems from Vista, except for the Server versions (2003, 2008 and 2012). The reason is not known and there are several assumptions and rumors.
Intel is a partner of Microsoft in many things and not offended things decided it will not fix the bug in their driver (HD 2000/3000 and 2500/4000) which gives a beautiful crash every time you use a PAE kernel versions in a 32-bit no Server Windows O. S.
And these crashes doesn’t happen with Nvidia and AMD/ATI drivers.
This is very clear because Intel has partnered with linux.org and is a partner in developing drivers for GNU / Linux systems that have 32-bit PAE kernel and there is no limitation in the intel graphic driver nor crashes.
I also read that a user who probably did an upgrade from Windows XP to Seven, did a rollback of a Intel HD Windows 7 driver to a XP driver version and has worked fine (Windows PAE kernel driver Intel HD XP).
Unfortunately if you try to install the XP driver ain the Windows Vista/7/8 the system informs that “the computer does not meet the requirements”.
Then the bullet hole is there. Based on the Intel driver for Windows XP, or modify it to be accepted by Windows Vista/7/8 or modify the Intel driver for Vista/7/8.
I believe even in not a bug, but a deliberate restriction.
And so is this link (http://communities.intel.com/thread/32085) Forum Intel can sit and wait that Intel will fix this pseudo “bug”.
The other options are:
Use the Standard VGA Driver
Buy a Graphic Card (not Intel) to user with Windows PAE kernel.
Migrate to Windows 64 bit versions.
Migrate to Linux.
And f**k the consumer.

• Andy says:

I can’t believe it, but I got Win7 to work on a Intel HD 3000 graphics (i3 Sandy Bridge) with this PAE patch.

The solution was using an XP 32bit driver, which seemingly can do PAE. The only downside (?) is that it will NOT do Win7 Aero. But at least that’s better than the standard VGA driver, since it can do the full resolution of attached gig screens.

Here we go:

1) Patch Win7 for PAE

2) Boot Win7 in unpatched mode

4) Unpack

5) Edit the INF file in folder \Graphics\igxp32.inf by copying the WinXP section to the Vista/Win7 section:

5a) before:

[IntelGfx.NTx86.6.0]
; no install on Vista/Win7

[IntelGfx.NTx86.6.2]
; no install on Win8

5b) after:

[IntelGfx.NTx86.6.0]
; no install on Vista/Win7
%iSNBGM1% = iSNBM0, PCI\VEN_8086&DEV_0106
%iSNBGD1% = iSNBD0, PCI\VEN_8086&DEV_0102
%iSNBGM2% = iSNBM0, PCI\VEN_8086&DEV_0116
%iSNBGD2% = iSNBD0, PCI\VEN_8086&DEV_0112
%iSNBGM2P% = iSNBM0, PCI\VEN_8086&DEV_0126
%iSNBGD2P% = iSNBD0, PCI\VEN_8086&DEV_0122
%iSNBGD3% = iSNBD0, PCI\VEN_8086&DEV_010A
%iIVBGD0% = iIVBD0, PCI\VEN_8086&DEV_0162
%iIVBGM0% = iIVBM0, PCI\VEN_8086&DEV_0166
%iIVBGD0SRV% = iIVBD0, PCI\VEN_8086&DEV_016A
%iIVBGD0GT1% = iIVBD0, PCI\VEN_8086&DEV_0152
%iIVBGM0GT1% = iIVBM0, PCI\VEN_8086&DEV_0156
%iIVBGD0SRVGT1% = iIVBD0, PCI\VEN_8086&DEV_015A

[IntelGfx.NTx86.6.2]
; no install on Win8

6) Install the patched driver by
Device Manager
-> Update Driver
-> Browse my computer…
-> Let me pick…
-> Have disk
-> Point it to the folder with the INF file

You might have to agree to install unsigned drivers

7) Change the Windows 7 theme to Windows 7 Basic

8) Restart and enjoy 4+ GB RAM with HD graphics

• I did this in Sunday and have testing it before publish to avoid headache with lots of questions.
Really works but the Aero don’t work and the speed it’s no to great compared with the Microsoft VGA Generic driver.
But I do this in other machine that I have with the G41 chipset and have the same issue.
Well, I prepared to install the VGA after uninstalled the intel HD driver but Windows 7 have installed a Microsoft HD driver instead.
Well, I just try it and works with this driver that’s present in the Windows update on the G41 vdriver.
But it works in the HD2000 chipset too?
I don’t tested this too.
Maybe this weekend.
But if you can try this Andy and later report we appreciate.

2. R0man says:

The problem seems to be the driver of this Intel HD Graphics (Mobile Intel® 4 Series Express Chipset for me). Without it, I can go up to 1280×768 on my Dell Latitude E6400 using standard Windows VGA driver. As soon as the driver is installed, after Welcome Windows startup I have black screen and laptop freezes. But I can always enter within the Windows safe mode. Do you think that memory is shared differently with that kind of graphics adapters?

• wj32 says:

It’s the driver’s problem. It probably uses 32-bit variables to store physical addresses which are actually 64-bit, truncating the addresses and reading/writing random memory.

• Philippe ROSE says:

Just to be exact with PAE activated the addresses are not on 64 bits but on 36 bits.

• ruddj says:

Appears Symantec are also having problems with the Intel driver taking up too much Kernel space:
http://www.symantec.com/connect/forums/pgp-wde-blue-screen-after-kb2393802

• comdevil says:

Me too.
I’m using Lenovo ideapad U160 and having problem with Intel HD Graphic!

• WiFi says:

Same problem with Dell Inspiron 14R N4110 here. I only want to ask, if you have another graphic driver (mine is AMD Radeon HD 6630M), does disabling the Mobile Intel HD Graphics would solve the black screen problem?

3. kDn says:

Not working for me on Windows 7 SP1, causing BSOD 0x8E

• kDn says:

Sorry, I was wrong. All work fine
I was get BSOD 8e becouse had overclocked memory 2*270*(5/3)=900MHz (5-5-5-15) for DDR2 800. Then I grow up timings to 6-6-6-18 and tested with MemTest86+. Currently memory is stable and Windows 7 with PAE patch stable also.

Thank you).

4. Ivan says:

• Ivan says:

Apologies for my inferior reading and Googling skills, I used the old patch. However after finishing all steps successfully and rebooting to the new patched Windows, the usable RAM size was still only 3,46 GB.

• luca62 says:

patch is ok.
move directory “PatchPae” in C:
command is > C:\PatchPae\PatchPae.exe -etc etc

5. Pingback: Windows 7 Service Pack 1 Final

6. Royce says:

Did not works on me, the windows always restart randomly, and there’s written memory crash dump ?

7. Royce says:

My pc didn’t overclocked at all, and the configuration are on normal setting… , but still BSOD, windows 7 sp1..

8. Rishi says:

Dear Wj32,

Thank you for this worderful patch. What I want to know is that, all the steps mentioned in the readme text I have to follow. If after patching the system with the patched pae and then I delete PAE folder will it still work.

9. Bow says:

Hi Wj32,

I can get into windows but not for a while BSOD. I’ve tried more than 5 times using the patch PAE (Win7SP1) but always BSOD with various kinds of error messages.

Any suggestions?

10. chrisu3 says:

Hi everyone. Can someone explain me how to completely uninstall this patch? I have used instruction attached to patch, but it didn’t worked for me Now Win7 see only 2 GB of ram in my computer :/. I removed patched entry from boot tab in ms config but issue is still the same. Also in the bottom right corner of my desktop appeared info witch says: “Test mode, Windows 7 Compilation 7601″.

11. mauro says:

and version for xp 32 ? are plan to build? using kernel 2003 or patch kernel to activate PAE

12. voorhees says:

work fine here, this is some picture without patched and patched PAE

there is some problem, but that must be becouse, like wj32 said, software/hardware issue, in my case i start alot application which use user-mode or kernel-mode drivers but for now i saw just apllications which use capture drivers not work on my system, specifically AverMedia Hybrid TV card and Logitech WebCam

• voorhees says:

actually my mistake, just AverMedia capture device driver will cause application crash or system hang, depending which application will use that device driver.
WebCam works fine

13. triplexxx says:

thank you very much wj32 for this patch! it works pretty fine on windows 7 pro 32 bit. my kernel-version is: ntkrnlpa.exe 6.1.7601.17592.
till now no problems with drivers …

VGA driver?
This issue affect’s only INtel HD (2000/3000 and 2500/4000).
I tell you because I’m use this patch in a netbook with 945 chipset and has no problem with the Intel Graphic driver.

14. khangozzy says:

Hi all,

How to remove the water mark “Test mode, windows 7 compilation 7601″

Tks

• triplexxx says:

Did you do all steps like shown in the readme.txt-file?

I have exactly followed the instructions in the readme.txt, there is no water mark at all at me PC…

15. triplexxx says:

I have tried the patch on another Notebook with an Mobile Intel X3100 Grafic-Adapter onboard. The patch does NOT work. It seems to be a problem with the Intel-driver, like people reportet above …

16. PA says:

nointegritychecks works only for the 1st boot, after that Windows Startup Repari will launch and complain about bad signature in either ntkrnlpx or winloadp.
For the rest the patch works fine.

17. PA says:

Forget about last post, it works fine just now.
I forgot my bcd entry has nx AlwaysOff and it seems that option also disables PAE.
So if you want to have +4 Gb PAE kernel but dont want Microsoft DEP (Data Execution Prevention) on you you need to set:

bcdedit /set {current} nx AlwaysOff
bcdedit /set {current} pae ForceEnable

18. PA says:

Oh and another drivers that has problems with this memory seems to be MacDrive’s HFS driver, when the patched kernel is active the driver doesnt mount HFS partitions.

19. bvdl says:

works fine without any problems,
great work!

20. Luis Ibanez says:

Hi, thanks for the post, this helped me a lot, i tried with different patches, but without success. I follow your instructions over Windows 7 Ultimate “Sp1″ and it worked just FINE. For all of the guys that didn’t get it working, i would suggest PowerCmd , so you will be able to copy and paste the commands instead of typing everything manually. THANKS again, it works like a charm.

21. Previx64 says:

Those who are unable to run bcdedit for error “The boot configuration data store could not be opened”, this may be because your Boot files are on a recovery partition which is not attached by default to the windows. In that case you can press F8 at boot up and enter into repairmode. open a command prompt and do the procedure listed above. HTH

22. Previx64 says:

For those who got into a brick wall thanks to intel igdkmd32.sys and the like, they can verify whether this patch works by entering the safe mode.

23. kon says:

Thanks for this great hack, my pc works fine with win7 sp1 and this patch and now I dont need move to an 64bit version anymore!

• kon says:

Also that powercmd program makes ur life easier, as it has to do with the progress of this patch. Just copy-pastes and finished
Thanks again!

24. Pablo says:

Excellent patch…worked perfectly. Thank you!

25. sorin says:

Thank you! It worked … like a charm!

26. Novex says:

Still can’t work on Intel HD Graphics (Thinkpad x220)
In safe mode it totally works. When starting normally, black screen just like R0man says.

27. moon says:

I test on Lenovo G470 with Windows 7 Ultimate SP1(32bit)
work on RAM 4G
but can’t work on RAM 8G (4G x2)

28. Michel says:

I got the version before SP1 to work but this one does not.
I get a Windows repair screen just like when you insert the repair CD.
I used Powercmd as Administrator hoping that would be an elevated command prompt.
Anyway.. How do I REMOVE this?

29. Michel says:

Seems I myself made a mistake.
I could see what I did wrong in the powercmd history log.

Anyway it works now.
I will give a short tutorial how I did it, perhaps someone who is also not very technical will benefit from it.

Unpack the zip file with Winrar to a folder named tinytim on your desktop.
Type: cd C:Windowssystem32
Then just follow the steps from the read me which is also in the patch zip file.
Where it says:C:WherePatchPaeIs
remove that and put in: C:UsersusernameDesktoptinytim

So for example this:
3. C:WherePatchPaeIsPatchPae.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe

Would have to be this:
3. C:UsersusernameDesktoptinytimPatchPae.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe

It’s great having bought 4 GB and actually USING 4 GB!

30. pool of ram says:

not really working on cores which have memory sharing on built-in gpu’s (arrandale, sandybridge, new gen cores, nvidia’s optimus, other switching techs) unlike when you setup it on a machine with dedicated gpu it will run without any problems.

31. Julio Ariza says:

The selected entry could not be loaded because the application is missing or corrupt. Any idea?

32. Ottorino says:

I also have tried to patch the Win7 32bit on a nvidia optimus system. I get the same problems as decribed above. Everything works fine with standard vga driver. After install the Intel HD Graphics driver the system hangs close before welcome screen.

Does anyone with lots of knowledge about memory sharing have an idea how to solve this Intel driver problem?

33. Pizzetta says:

Same problem also for me on HP EliteBook 8460p with Intel HD graphic driver.
Installed this and other 4GB patch, but is always the same: BSOD after entered Seven password login account or the PC crash. If I execute the patched boot in safe mode than I don’t have problem.
I investigate that the root cause is due to Intel HD graphics driver. In fact I’ll uninstall the driver and execute the patch it works correctly but I have the VGA mode.
Any suggestion to fix this issue?

34. Has anyone verified this patch against the latest release of ntkrnlpa.exe?

File version: 6.1.7601.17713
Date modified: 10/25/2011 11:47 p.m.
MD5: F2368C2A4B126B2EAEF1985116B88A1D

Thanks.

• After some extensive experimentation, I will respond to my own post. The short answer is, “Yes … the patch will work with 32-bit Windows 7 Professional SP1, from the bare SP1 installation all the way through the latest available updates as of 14 Jan 2012.”

Environment:
Intel S1200BTL server motherboard (Intel & Micro$oft drivers) Intel Xeon E3-1230 CPU Video – ATI 5450 GPU (AMD/ATI driver) Sound – Creative Audigy PCI (Creative driver) Disks – (2) Seagate 1TB disks configured as a RAID 1 mirror array using standard Micro$oft software RAID

Kernel revisions:
The PAE kernel file (ntkrnlpa.exe) on the original SP1 install disc was version 6.1.7601.17514 (20 Nov 1010). The kernel file was updated per KB2633171 to revision 6.1.7601.17713 (25 Oct 2011). PatchPAE works correctly with either kernel file.

To repeat myself … If you install the PAE patch exactly in accordance with the instructions provided in the package it will work correctly with any 32-bit Win 7 Professional revision level from the M\$ distribution discs through the latest updates as of 14 Jan 2012. It is still possible that the patch will fail to work correctly in some environments due to non-standards-compliant third-party drivers.

I hope this helps.

35. Kostas says:

Win 7 SP1,
8GB RAM,
Intel Core i5 2500K + ATI 5850
working fine until now…

36. pizzetta72 says:

Nothing to do. Installed last version 6.1.7601.17713 but hte problem is still present if I start Seven in Normal mode. In Safe mode or better removing the Graphic driver (Intel) the problem disappear and I have the 4Gb.
The main problem is focused on the Intel Graphics drivers that probably are not compatible with PAE enabling

37. war10ck says:

Windows 7 runs well with Intel Graphics driver for XP. You won’t get the AERO effects but the basic design. Still better than default VGA or blue screen.

• R0man says:

• MAto says:

Have U any clue how to start aero in xp driver ???

• arfer says:

I can confirm that the Intel HD XP driver works fine on my Dell N5110 i7 8GB with Windows7 32bit, and I can use the full 8 gigs with the patch. But… the nVidia Geforce 525M with Optimus technology doesn’t work with this driver, so I am not able to use the nVidia card, just the HD graphics. Any suggestions? As a “workaround” I don’t use the patch, but I installed Gavotte Ramdisk which is able to use the memory above 4GB, and I put the pagefile there.

38. dumraja says:

HI all,

did exactly as the instruction everything went great but on boot it still shows ” 4.00gb 3.25gb usable”
have win 7 ultimate lic. copy and laptop XPS M1210 DEll can sone one help.

I tried again and again have more than three entries in boot but none works.

can some one help me and guide.

• R0man says:

Seems your video card doesn’t have its own memory…

39. mitko says:

i did that and just before the welcome screen where i should write my password for windows it only shows black screen without anything else… it seems its not working for me i have windows 7 32-bit with 4bg, but it says 2,36 usable.

40. Stiopa says:

After installing this patch on Windows 7 SP1 Eng i am getting only 847mb of usable memory.
http://funkyimg.com/u2/1445/050/227550tuned_windows7.jpg

Is there a way to uninstall this patch?
PS: Using ATI Radeon 3650 GPU

41. User says:

Exellent patch!

Also, big thanks to PA for these 2 lines:

bcdedit /set {current} nx AlwaysOff
bcdedit /set {current} pae ForceEnable

Did not work until after enetering them.

Sidenote: if the patch did not work from first try, chances are, you booted using the other “Windows 7″ boot entry. So to go into correct boot store, the lines above should look like this:

bcdedit /set {default} nx AlwaysOff
bcdedit /set {default} pae ForceEnable

Using this on HP 8540p notebook.

42. Anon says:

I always get blue screen after installing this patch, any help?

43. robin2001 says:

I installed the intel graphics hd driver for XP x86 in safe mode, rebooted and now…
Working on my Dell Latitude E5420 (Core i3, 8GB RAM now on 7 32bit )

Thanks to war10ck for the recommendation. (as he said no aero effects, but no big deal here)

• MAto says:

Does anybody know how to run aero theme under xp intel driver ?? it would be great

44. eric says:

try the uniwave patch..i have used it on several computers without any problems

• Steve says:

I tried the uniwave patch and it didn’t do anything. I have 4GB ram but still can only use 2.94GB even though it﻿ said patch was successful and I got the watermark and dual boot screen. typing in bcdedit proved it did nothing and ntkrlICE.exe file was unchanged. I didn’t try this patch from here and after reading these comments I won’t try this one either. I’ll just install 64bit 7 Ultimate.

45. marcio says:

someone managed to solve the problem with the intel HD igdkmd32.sys error 0×00000116?

46. soshallitbe says:

Fantastic! Just patched a Win7 SP1 32bit system (Intel i5 with Nvidia gfx) and it now shows the full 4GB that is installed. Mate you are a legend – put the donate button up now!

47. viltnieks says:

hi
I have a problem
after the restart and start Windows 7 (PAE Patched). I have mesage “Your computer was unable to start” and starting startup repair.
Startup repair is not corrected the problem.
what am i doing wrong and what is the solution?

• mixcomo says:

Same here, I try patch on my Windows 7 enterprise (legal trial). I do not try startup repair to correct the problem, but I will do it.

• Larry says:

I’ve been having the same problem. I’ve found that if you boot the normal windows first and do something for awhile and then restart and choose the PAE boot choice, the next few times or so you will be OK. Then it’ll do it again and you have repeat the process. It’s a little annoying, but not overly so. I’d still like a fix though.

48. Jonathan says:

Qual, é…?
Háa, tenho o Windows Srever 2008 64 bits…Como resolvo problemas de incompatibilidade com programas (32bits)?

49. grat Stuff !
…it works good under Win7.
How about Vista x86 ? someone tried it there ?

Hint for Win7:
if youre PC wont start after “correct” Patching, reboot again and press F8 in Bootmenu !
Now select the Menu “disable Signature veryfing” and VIOLA youre System will Run after this with FULL Ram !

50. its not “grat”… =D its GREAT
NOBODY outa there who tryed this Patch under
Vista 32bit
Windows Home Server 2011 64bit
???

• Larry says:

I ran this for over a year on vista 32, It was like magic. Every idiot out there says that the PAE patch, does not improve game performance. That’s horsesh** I got incredible performance increases from all my games.

51. jcm says:

I got this to work as well using the intel HD 3000 windows XP driver on windows 7. I downloaded the window 7 SDK for makecert and signed the patched ntkrnlpa.exe based on the german website instructions. Like everybody else I could boot in to safe mode but was just getting a black screen on boot (no windows logo ever).

We’ll see how we go but it looks like my dell vostro is kitted out with a new SSD and 8GB ram now. I like to run multiple virtual machines.

52. zam89 says:

does this work with macbook pro (via bootcamp)?

53. Anon says:

I don’t understand if PAE can be enabled via cmd console bcdedit then why the hell do we need this for?

• Larry says:

Come’on! It’s frustrating when someone who doesn’t know anything about something demands everyone else educate them on the subject. Just google PAE and the name of your windows version, and read the results that talk about PAE by itself. Enabling PAE in the BCD does NOT allow the use of more than 4 gbs. This patch fixes that.

54. Larry says:

Help! I had windows vista 32 and 6gbs ram with the PAE patch installed worked great.

Then I upgraded to windows 7 32 installed the PAE patch and now I have only 4 of 6 gbs usable.

I made no hardware changes. Why isn’t the patch giving me all 6 gbs????

55. Sergio says:

I does work!! Thank you!!!

56. Qwest says:

Patch appears to require the Microsoft .NET Framework to function.

57. jcm says:

I had about a half a dozen blue screens over the last 4 months using this patch with 8 GB ram, the windows XP intel HD 3000 driver, and a OCZ vertex 3 ssd. I got a lenovo T430s and put 16gb ram in that and went back to 3GB on this Dell, which has been relegated to secondary duties.

• Atis says:

I also have Intel HD graphics. Managed to run PAE Patch, a new boot entry has been created but I get BSOD too. Some of you guys say that installing the XP driver solves the BSOD. So how did you manage to install XP driver on Windows7? I downloaded both the zip and exe files from Intel’s website but I can not run any setup application because it complains that the installer cannot run on Windows7. I tried running it on Compatibility mode but still having that error. How did you guys install the XP Driver??

• DoKs says:
58. saboly says:

Hello
i did apply the patch before when had 4 GB only of ram , was working great and i was able to use all the ammount of ram
NOW i added extra 4 GB of ram , it was very strange to see only 3.94 gb usable !!!!!
i applied a MS update to update kernel to new version which is reported compatible with the pacth KB2633171-x86
i deleted bcd entries and created clean one > applied patch > but still 4029 usable reported in task manager
any suggestions would be appreciated
thanks for this work

59. Brian says:

Hi,

I applied the patch and i’m getting the 4GB working on win7 starter. However my graphics driver now isn’t working! (it’s a samsung nc110-intel atom n2600 – intel gma3600).

When i boot from the normal kernel the driver works fine but only 2GB of the 4GB is useable. When i boot from the PAE patched kernel i got the 4GB set as useable but the intel gma3600 driver has stopped working.

Any suggestions? Should i try reinstalling the driver or is their something I need to configure?

Thanks

60. Brian says:

I got win7 starter on an atom n2600 to recongise 3.25GB of ram – it wouldn’t work with the full 4GB as i think the 64bit instruction set is disabled on the atom n2600.

As above when I tried the full 4GB the GMA3600 graphics driver wouldn’t load (as i think it needed the address space over the 3.25GB hard limit on 32 bit).

I did this by going to MSCONFIG -> BOOT -> select the patched boot option and click Advanced Options then m,anually set the maximum memory field to 3328MB.

I’m happy enough with the 3.25GB as win7 starter is only supposed to have 2GB!

61. alex says:

Hello!
Can you please help? When I try to install the patch I get stuck at the third step:
C:UsersVIODesktoptinytimPatchPae.exe’ is not recognized as an internal or external command,
operable program or batch file.
Any ideas ?
Thank you!

• Thomas says:

Alex,

The 1st thing I would do is move the PAE folder to the C drive so it reads: C:PAE
Of course, you should have 5 files in this folder:
PatchPae.exe
PatchPae.sln
ProcessHacker.Common.dll
ProcessHacker.Native.dll

C:PAE\PatchPae.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe

Hope this helps.

• Thomas says:

*Note error, step 3 should read:

C:PAEPatchPae.exe -type kernel -o ntkrnlpx.exe ntkrnlpa.exe

62. Thomas says:

Thank you, wj32. I have downloaded and installed the patch. I’ve tested just about everything I could before posting this message. All programs seem to be working appropriately. My only concern was the Adobe PageMaker program I have since it is THE most important application on the computer. But low and behold, it works too! Thanks for making the instructions so easy to follow.

63. Tommy says:

I need help to remove this patch, installed it succesfully but with the result that I cant connect with my internet and my geforce 8600 wont work. Tryed to restore the sytem to an earlier config but it doesn’t help, the patch is still there… :/

• Tommy says:

Solved it…

1. Open an elevated Command Prompt window.

2. cd C:Windowssystem32.
Make sure the current directory is in fact system32.

3. bcdedit /enum

4. Made sure that “Windows 7 (PAE Patched)” were listed as {deafault}

5. bcdedit /delete {default}

Done! Restart and my Windows 7 in original started. =)

• Brian says:

You can also do this by typing msconfig into the run prompt and deleting the boot entry in the boot tab.

64. Fung says:

I got it working on my OptiPlex 380 at office. Both Resource Monitor and System Info show that I have 8GB installed and usable.

Here are the screen dumps:
http://i50.tinypic.com/5cgcrb.png
http://i47.tinypic.com/33d81m0.jpg

I also had the Intel driver issue. As told by comments above, I have to install the XP version of driver (no Areo, no big deal for me). My situation is I then encountered BSOD after XP driver was installed. It was due to Windows was trying to install another driver for Win7. So with two drivers, I got BSOD. I simply disable the Win7 one, and viola!

@wj32 thank you so much for your work. I have no option for 64bit, but I have to run VMs for work. You saved my life.

65. GalaxyGalaxy says:

Hi, wj32. I really need a patch for Windows 8 as my old laptop has just 4GB memory. A 64bit version do takes more memory while I usually open quite a lot of tabs in Firefox.
Also, many Chinese bank and the offical sites are still sticked to WinXP 32bit, and 64 bit softwares are often missing or cannot be setup directly due to the different path.

Would you please update this patch ?

66. Teeluck says:

Also interested with windows 8 patch. Please make it, i’m going to install windows 8 only if patch is released, thank you.
Or somebody can give instructions how to manually modify files using hex editors.
Currently with windows 7 sp1 32bit, 6gb ram, never had any problems.

67. luca zapparoli says:

OK, install and work good on “HD western Digital sata 320 gb AV series BUDT” with Windows 7 on “Samsung R580 notebook” . PAE Patched > 3956 mb RAM disponible > OK

But, NO BOOT (error of ntkrnlpx.exe no found…) on “SSD Samsung 120 gb 840 series” , system and the same machine….!

repeated 3 times…NO BOOT (PAE Patched) — BOOT OK > Win32 (no pae patched)

Luca Zapparoli
Gorgonzola (MI)
ITALY

thanks also.

• luca zapparoli (IT) says:

sorry, solved

the system on SSD had received two commands before starting the patch.
1) bcdedit / set {current} nx AlwaysOff
2) bcdedit / set {current) landscape ForceDisable
Blocking the kernel patch. (!!!)
Removed all.
launched two commands:
1) bcdedit / set {current} nx AlwaysOn
2) bcdedit / set {current} pae ForceEnable
3) patch as instructed
4) re-started
OK!!

nvidia more ‘available RAM
photoshop also
RamDisk also

perfect.

68. Prostoy says:

macbook pro 2011 early, bootcamp windows7, GJ! 2,5gb UP 8gb

thx ;*

69. theblue says:

I was getting the crash with this in win 7 32-bit enterprise. I downgraded my video drivers to the win XP ones and now it’s working great!!!

• theblue says:

I spoke a little too soon. It appears to crash (BSOD) when watching video for more than a few minutes. If I don’t watch video it’s stable.

70. Juri says:

I have successfully patched a current 32bit Windows 8 download upgrade. 8GB appear to be available. Unfortunately Adobe Creative Suite 6 programs don’t work. Does anyone has experienced this and maybe knows a solution?

Thanks a lot

Juri

71. MRT says:

HP ELiteBook 8470p With intel HD 4000 you have to install the latest XP drivers and change the .inf (copying from the Windows part of the INF to the part that says ;no install on Windows 7) and it works… If you try with the Windows 7 Drivers it boots and hangs.

Just my 2 Cents…

MRT

72. Didouc says:

Very good job, i’m a french user with Windows 7 sp1 32bit 12go ram

Thanks

73. Serraxer says:

Very very thank you. Work great on win8x86pro on msi windpad 110w see 8gb.

74. Jean Hofsté says:

WJ32 I have another problem not yet mentioned hereabove:
There is no winload.exe and no ntkrnl–.exe in my System32 folder, but in c:/Windows/Winsxs there are 4 winload.exe’s of even date and 4 ntkrnlpa.exe of even date.
The full reference of one such ntkrnlpa = “C:\Windows\winsxs\x86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.17207_none_6c5f1f0a15341779″.
No. 2 finishes as: 18044_none_6e173b82127da724, / no.3: 21417_none_6cddedcf2e59d05b and no.4 as: 22210_none_6ebd48cf2b868ae6
They are dated all 5 Jan 2013 and have the following time: 07:02/07:00/06:53/06:49

I executed the remainder of the bcdedits hoping (in vain) that the boot-loader would search for the actual ntkrnlpa.exe’s.

So now I have a double boot option of which the PAEpatch selection runs into the same problems a number of people have too: i.e. startup repair with no final solution.

I run Win 7 Ultimate + SP1 – 4GB available (2.96 usable) – (done earlier with bcdedit /set increaseuserva 3072)

Any suggestion to get the PAEpatch selection utilize the WINSXS folder entries, even with 4 different register entries for the even-dated ntkrnlpa.exe’s ?

75. Andreas says:

After having a patched Win7 Ultimate 32 on an MSI notebook, I ust tried to patch my Windows 7 Ultimate on a Atom D2700 driven machine.
When I select the patched winloaid version system stops caused by an inaccessable device.

I still have no idea where this comes from.

I also set up Win7 Ultimate in a virtual machine, giving 6 GB of RAM to it. Patch worked fine on that virtual machine, so I do not think that it’s the patch itself.

76. Andreas says:

Update: I was too stupid this time, sim´ply forgot to switch off integrity check.
Patch works fine but this time it could not help, because the display driver (Intel Atom D2700) crashes when additional ram is enabled.
I found a beta state driver for Win7 x64, even this driver on Win7 x64 crashes. So my new Atom driven mini-pc will remain 32 bit having 3.25MB addressable.

77. chewy says:

Hi all, not working for Toshiba Satellite Pro A100. I went through all the steps but the system couldn’t start. Then I added also the “nx AlwaysOff, pae ForceEnable” to the bcd and the system starts correctly although still only 3.00 GB usable. Processor supports PAE (checked with sysinternals), Mobility Radeon x1600 graphics.

78. exequos says:

it is working for me with some differences
instead of patch signature checking i use the signtool suggestion from this resource ( http://www.geoffchappell.com/viewer.htm?doc=notes/windows/license/memory.htm )
because my gigabyte z77n-wifi have intel hd4000 graphics i had to downgrade the drivers to modified inf file as suggested above.

Finally there is 16GB – gfx memory available
the only minus is that the performance in graphics goes from 6 to 1
the only question is why there is “test mode windows 7 kompilation 7601″ in the right-down corner.

• Can you explain how you do to generate the certificate etc, etc, etc, step by step?
What softwares are used?
I’m very interested on these!
It’s better than the workaround trying to modificate the intel video driver.

79. fabiano says:

It worked for me. Thanks for this patch, buddy. Just one doubt. Is it better to use this patch with 32 bit windows version or install 64 bit? Nowadays processors are still 32 bit processing, just memory addresses got an update to 64 bit. I guess processing 64 bit is more expensive for the processor, once it will have to break 64 bit words in two 32 bit, processing and remount again. Or am I mistaken?

80. Don Williams says:

I typed in the commands line by line. It appears to have partially worked for me. I built my PC via components, and the Motherboard/Processor supports 32 GB RAM.
Upon using this, I now have 24 GB RAM available, but I still have 8 GB RAM that are not usable. How would I got about correcting this?