Vista 4gb memory patch

I deleted the patched Boot entry in msconfg, and started over rebuilding the patched OS but using the original winload. Still crashes. Any thoughts or suggestions? It seems to me your article is aimed at people who are running 32 bit windows on 64 bit systems. If however they are using it on a 32 bit system 32 bit processor such as say Pentium IV or so for example , then there is indeed a physical reason why the OS cannot access memory up to and possibly above 4Gb and that has to do with the systems possible inability to actually address that memory at a hardware level, in order to do so the system must support PAE Physical Address Extensions , but even then, PAE is not supported on all 32 bit systems and is typically only present on some of the most recent 32 bit motherboards say within the last years or so roughly.

Of course if they are using a 32 bit version of Windows on a 32 bit system that supports PAE then there is also no real need for software like you mentioned in your article to enable support for PAE in the OS as versions of Windows from Windows XP on up already have support for PAE built in. Though admittedly in the case of Windows XP at least it may not be enabled by default and may need to be enabled through the use of a boot.

The details of which can be found easily enough using google. Additonally there are boot. On another note there are also a few utilities available that can be used to patch 32 bit programs so that they may be able to take advantage of memory above roughly 2Gb making them hence LMA Large Memory Aware , I myself have used one such program to patch the program Bryce 7. One such utility can be found at ntcore. So if it boots, you can hack windows to use it. I tried the 2 modules in one machine, it worked fine, I tried them in my machine and the machine will boot up but will eventually blue screen and I have to revert to the original boot.

The 1st machine worked perfectly, seeing all 4Gig of memory. Where should I look? Oh, the laptop is an Acer Aspire But, will this modification process open up the computer to malicious exploits? What are the risks? And, how can I mitigate them? All patching is successfully applied but after reboot computer goes to repair mode, peforms some analysis and says that ntkrnlpx. As I can see this problem persists for years but nobody could find a desision…. Not the tool in the article but the author has a different version out for Win wj Using real double quote in ascii, not some weird variant you got by cutting and pasting from this page.

I think some web publishing blog engines try to pretty up the double quote by turning it into the leading and inverted ones in pairs. Ok Cool.. I tried. I got the same problem as Tim Edwards. However I have not tried disabling my antivirus yet during the patch of the 2nd command line for creation of winloadp.

So if this step fails for you. This also means it may be more advisable to work in a non-networked environment. I will be trying again by turning off antivirus and unplugging my lan later when i get back home tonight to attempt this again.

Tim, if you read this. However on startup my screen displayed some fuzzy lines and when trying to login it blue screened. Slack, just go get a 64bit version. As I said I would look at Rampatch and report back. I have ran the program and received a copy of ntkrlICE which is a patched copy of ntkrlpa which is the original kernel.. The program does NOT at least for me write a boot load change and make it available on a reboot..

The fact is, it wants to review and repair the load just as it does for patchpae. I edited the command structure from patchpae to get the boot loader added. I suspect the issue is in the boot loader. The author of rampatch says the program will edit the boot load file, if that is the case how and where does this happen? Poor documentation is more the norm than quality writing.

Nothing works. Some users report mixed results as well as working versions. I find nothing to work for me. I am through with this moon walk and hope someone else will report a DETAILED writing of how they got a working version for either patchpae or rampatch. Best of luck. Upon several trials it never works. The pathing to the folder used for the installation does not allow at least me to run the file from CMD.

The operations at least worked until the above failure. Everything else seems to be in place and will work. In short it fails all the way around. I am an old DOS guy so I am with in my element.

The program is not right. I placed the main sub folder with the exe thinking it might be missing some sort of library. The same results. Unless the author refines his exe it is dead in the water. The first version had the same results.

I never have gotten it to work. Somethings missing. I really would like to avoid using 64 bit software. I will try the other Rampatch and see what it is missing. If anything. Thanks, Worked on my Win 7 Home. But when I put more ram in my machine, it only saw 5.

But still more than the 3. I tried this and it works. From 2. There was also noticeable improvement in system performance. Then no change to the ram at all, no start up boot option, nothing. I tried to do it manually with PatchPae, twice, but it blue screens me on restart and messes my screen all up.

Flickering and stuff. How can I get this to work again? I can start with new new patched version but it still only show 2. Thank you very much. It says that my kernel is corrupted with a error message: Status 0xcb. One thing that i noticed is that when i try to start the patched version, the loading screen became in English and it was in Portuguese. It is related?

Ok quick question. I have a sony vaio vgn are laptop running win 7 32bit ultimate. Sony says max ram is 2gb.. I have 2 ram slots 1gb sticks in each.. If that was the case you might not even need the patch as 32BIT allows you to have close to 4GB of ram. Tried this today — Windows 7 SP1 all up-to-date with updates. Attempting repairs … ad infinitum. I had the same problem as one of the other posters; the patched system went into repair mode and stayed there.

My win7 Ultimate is up to date with the latest patches. Any suggestions? I did mine and after restart i went to boot menu to put my full memory on then restarted again now i cant swap back all i get after the little windows 8 sighn then black screen no option to swap back.

Win7 Professional 32 bit and Core 2 Duo. Odd thing about my computer is it sees the 6 gb even without the patch but saying only 2. This patch stop working after installing KB!!! I had this problem and had to restore the system. Hello, first I would like to say that this patch works alright.

I have Windows 7 Ultimate bit and when I restart after doing all the procedures and change to the patched version it starts normally, so its fine up to tht point. But when I stut my computer down and the next day I try to start the patched version again it enters the Startup Repair mode but it does not fix anything at all, it simply enters an infinite loop.

I know someone has already posted a similar comment above since I have read them all in hope of finding a solution for this but no luck. If anyone has found a way to fix this Startup Repair thing please help.

Again, this patch actually works. When I installed it, everything worked fine until about 5 minutes into using my laptop, the screen flickered in multi-colors and then went blank and would not come on again. I re-started with the non-patched windows 7 and it is fine. It was still showing 70 mb reserved for hardware. Any reason why the screen would not work? I have intel graphics integrated with the ram for my laptop. If anyone has any suggestions please reply many thanks in advance.

Have you extracted the patchPae2. Hi, I tried to patch but when i start the patched version, i get the windows startup repair loop. Any workaround for this? I have been doing these over several months, so they were at different levels of win update. I have always run the mem patch process in an elevated cmd window start menu accessories cmd, rt clcik, run as admin. Another thing I did different between the failed and good attempt, on the failed attempt, I just googled patchpae2 and downloaded from another site.

Maybe a bad copy. On the good attempt, I came to this site and downloaded. I run a legal windows 7 ultimate testing environment beneath linux on a supermicro workstation, whose is capable to adress up to 64GB of ram.

The hardware has no limits, but i installed 7 ages ago as i had a smaller amount of ram. Just no entries. Anyone have a solution? Thanks Stan. Thank you so much it works perfectly in my Desktop. It should work the same on a laptop as it does on a desktop.

I followed all the instructions on my Core-i5 machine running Windows 7 Pro bit. My question is, this stop code, does it mean there is something faulty with my hardware and how to i get around it if installing with 3GB of ram does not work? The hotfix installation went through, but when tried to restart the computer with all four memory sticks Blue screen. As of now, my system is running quite stable with just 3 sticks on, at MHz.

I've been having this problem all night, and I've found a few solutions, but depending on your setup, it may be a whole bunch of other things. However, I had multiple problems with my latest one. Most of you guys are probably saying : "So what? I'll just take it out" which is true, but once you try to install a RAID setup, you're pretty much screwed. This is exactly what happened to me. Secondly, I wasn't able to install vista with 4GB for one simple reason. I was using 4 x 1GB sticks.

Did you know that 4 sticks consome a lot more power than two sticks of the same size? If you really want to ever use 4 sticks in a same rig, you'll have to increase your memory voltage.

This is why you'll find no manufacturer selling 4 sticks in one package. What did you do finally to resolve this problem. I am in a similar situation like you. I see BSOD for this. With 2 GB in windows, it says I am not required to use th kb fix pack.

So Either 2 Gb or none. Office Office Exchange Server. Not an IT pro? Windows Client. Sign in. United States English.

Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. I haven't tested it personally. Microsoft claims that it is not their fault and is instead a limitation of the 32 bit architecture.

At first glance this seems correct. However, this is not actually true. Before getting started, keep in mind that this patch involves modifying the kernel.

Do no proceed unless you are confident. Most security products will identify these patches as malicious since they modify the Windows kernel. This patch will allow the OS to use more than 4 GB of memory.

However, it does have a limitation? However, in some cases installing this patch on 4 GB systems will also lead to an increase in available memory which may not necessarily result in performance improvement. This may appear to be a bit strange since Windows 7 and Vista are technically capable of addressing up to 4 GB of memory. Ugh, those things always cause problems. One of my friends tried something like that enabling PAE in 32bit Windows, but by using the proper way to do it and it caused nothing but problems application crashes, BSOD's, You can even use the same license for it.

Just download the iso from one of Microsoft's DigitalRiver servers and install that instead.