Vista 8gb patch

If windows makes a reboot, paepatch is not active. I thought i re-patched the 2 files.. Didnt redo any bcdedit stuff. My workaround see above works. All exe-files ntknew, ntoskrnl, winldnew and winload are For those uninitiated who are experiencing crashes after the latest windows update try this method:.

Hate to ask but what does the command do?? Sooner or later Mr. Seems to be the best answer. Even if it does not move you up to latest version the last update I had was easy to patch. How do i check this setting? What does this mean? I have to rerun all the bcdedit commands again? Fails on PAE boot entry just keeps in restarting loop cycle or ends up with the green screen of death informing bout failure of some nvxyz.

Also it screwed up the WinBtrfs module somehow; clicking on a drive in File Explorer results in An internal error occurred message. Now the latest version of Windows 10 is Anyone is working on patching the new kernel and loader? It is only a matter of the video-drivers. You have to obtain and use old maybe Win7- driver. Please see my comments above. Maybe it works with your card. Thank you so much Michael. I really appreciate your help. I do not use Win10 regularily. But due to my experiences with Win7 and Win10 in the past it is not a matter of the winversion but a matter of the nvidia-driver-version.

The same problem occurs with Win7. I also do not exspect that a newer Winversion would not accept the old Win7-driver. But at last with all this patches and improvisations and workarounds: There is no guarantee, make a try. See my comments of Feb. I need help thanks in advance. Upgrade to is done. The result was that after patching the kernel the system does not boot. You may remember that when patching the Win7-kernel manually you must give the patched file ntkrlICE.

Although there was no error-message and so the signature should be o. Any idea why this does not work with Win 10? Also upgrade to Build is done. The result was again that after patching the kernel the system does not boot. F4 80 62 C1 8B 75 FC B9 00 00 02 00 90 The file checksum is obviously different, even if the code of the function is basically the same. Any ideas? I do not have any idea due to the fact that I do not know the sourcecode of the patcher.

But you can do the necessary patches manually using a hexeditor and the information of my previous posts. Of course offline. Hi Alex, hi from Germany, too. Had you used the newest patch from this thread? I just re-applied the patch. Neuw Windows kernel is Works fine with this version, too. How can I determine if this is truly working on my system? Should I try the ntknew. Perhaps there is a hardware conflict?

Thanks, Randy. Without the benefit of any troubleshooting guidelines, I guess I must conclude that my x60 is not compatible due to a hardware conflict…. Update failed several Times 0xf So I selected the nonpatched-Entry as default from the Boot-Menu.

Then after boot, KB was installed with now Problems. I delete the old ntoskrnx. PatchPae3 succesfully tested on build Despite of this message, loader is patched correct way. Can you make a mod like Escape 75 did before, just an exe file to make it work. Btw many thanks for your patch. OK, I hope it will be useful, but without any warranty. Just unzip and copy into the same directory with patchpae. Ignore it.

Windows 7 has not such option, it has legacy boot menu only. The scriptPAE3v26 process is completed without errors but does not activate the 4gb of memory on the windows 7 desktop. I just installed windows 7 with latest updates kernel 6. Eugeny, attempting to patch W10 Previous versions could be patched well. Could you please look into new kernel file or publish your source code? Many THX. Original ntoskrnl. Full admin cmd and such. Running the script throws a x64 bit OS detected error and dumps me out.

No luck. Would the space matter? It took me rather too much time to find the current files. Having seen the readme unzipped from the top of the thread it never occurred to me to treat the patchpae3. Aside from the exe downgrading my Xeons to is inside joke for those who actually owned a once upon a time and some fat fingers it actually worked.

Without memory hogs like Waterfox it may take me awhile to get programs to actually use that space, but I look forward to it with great anticipation. Thank you for your help. Is that really sane to do on my primary personal system? Are these newly required dumb commands really so obscure as to practically never execute? Will my system be stable if I do this? Not mentioned in the patch instructions. Do I continue to come up short or have you magicians solved this problem too?

Weirdness, my hyperthreading turned off. It claims to be enabled on in the BIOS. Does some part of what we did turn it off? Firefox is hitting the CPU harder than anticipated. Next question, Microsoft never recognized my failed attempts years ago to upgrade this hardware to Windows 10 and never supplied a digital key for it to install.

There used to be many ways to complete a free and legal Windows 10 upgrade. Do any of these remain? Seem the patch dont work correctly with the new win10 ver It says something like side-by-side configuration is incorrect when open programs. Any1 get the same problem? The executable was compressed with mpress, then converted to a hex text file, which gets re-assembled at runtime to prevent possible false positive virus detections. The self executable rar file is packed with upx to reduce size,- contents can be inspected.

The other one "Windows 10 PAE " worked. You could use msconfig now and go under Boot and remove the other non-working boot entry. Who can help? My job is electrical technician. My guess is that perhaps the software was designed for Windows XP and not compatible with Windows 7? Works fine with new Windows Hey folks. Using the right paepatch3. Thank you.. Hello again In windows 10 ver: The parameter is incorrect. Im using Ryzen X and the last working version of windows is I tried many time on the newer version of windows but always get Out of memory error or Not enough memory to do something error when the RAM consum more than 4GB.

The computer runs noticeably faster. Yes, you can. Then you can remove the non-patched option. In very rare cases, windows will not start with the patched files after a monthly update. There is no really option to fix it. Therefore, you need the standard-windows-option to start the system! Menu see first sentence of this post. And… You can use it!

I read now all comments — still did not get the issue with Intel HD onboard graphic: Is it working with Intel onboard graphic HD or not?? PatchPAE3 0. Hi bro, what is new in this version? But since January-Update after selcting the nonpatched-Entry from the Boot-Menu, booting is interrupting and stating new.

While selcting the patched-Entry, everything is working still fine. I remembered the build for ntoskrnl. When I select the nonpatched-Entry from the Boot-Menu, booting is interrupting and starting new. But then there is prompting now Boot-Menu and booting is ending in perfect nonpatched Modus.

But when selecting the default patched-Entry, booting always works fine and is not interrupted by a second boot. This version works fine with 20H1 as Could you tell me where you got it from so I can check for future tool updates? Instead they should look for winloadx. Just to clarify and sort out some misunderstanding. Best way updating could be deleting the PAE-Boot entry using msconfig , install the update, delete elevated rights the patched ntoskernl and patched winload, reboot and just call the script ScriptPAE3v That should do, at least it did with mine.

Does anyone have experience with a more recent driver? The patch is working perfect on my ancient laptop with core i5 M, win 10 , but doesnt work properly with 2 new PC with i7 HQ and Ryzen X from win 10 and above, it only working good with win 10 and below.

What is the problem here? Patch is installed but I am not getting my memory back. Absolutely super. I can use all my 8GB. Jan Itor: What is with ntoskrnl and winload, also Here both are still I wanna thank to the people who make this possible.

Still works after Patchday Feb. I updated windows to february patch Still working fine with 8gb of RAM and not a single issue!!! No difference in memory availability with and without PAE. File versions: ntoskrnl and ntkrnlpx both What should the patch do? Give You 8GB Ram? So you reckon that the difference between installed and usable memory is what Windows itself needs, including drivers and display controller?

I have several bit Windows machines in my stable. Does your theory contend that some installations of bit Windows occupy 1. You need chipset or newer, see Intel r Ark. I remain mystified why the limit of 3GB, which many insist is a Microsoft marketing restriction, is not relaxed by the PAE Patch, thereby affording full use of installed memory more than 3GB albeit less than 4GB.

Once again, JRElliott. Thanks, evgeny. Win10 Works like a charm Win10 patchday Win7 works like a charm Win7 Build latest patchday ntkrnlpa. Patch does not work for HP Compaq , kernel It freezes with blank screen just before splashing user login screen. Any suggestions? The problem was integrated Intel graphics card. PatchPAE3 version is still incompatbile with nvidia video card?

Please, help! Now I have 8 Gb installed and no other text added such as 2. For me KB made no Problems. Installation at June 10, paepatch still working. I installed after booting by non-patched Entry in Bootmenu, bootet again by non patched area, patched winload and ntoskrnl.

Then next Start by patched Entry in Bootmenu with no problems. Small report: Works fine on Windows 10 x86 Newer driver version I dont understand how install PatchPae3, shoud i follow the tuto for PatchPae2 exactly same way??

Hello, any help would be grateful. I read almost all of the exchanges, and it is not clear for me if the patch can work with integrated Intel graphic card or not.

I really would like to run this PAE mode, are there any manipulations that could work? I tried some of them suggested on the posts below, but for the moment not worked. I also tried to downgrade or update the driver for graphic card but it is up to date and to downgrade it, the result was worse. If you have any suggestion…Thanks in advance. Enn, In my experience I could never get it working with integrated Intel graphics card on my machine.

PAE patch only started working once I added external graphics card. Hello Ped, thanks for your feedback. I feared that, me too. See my previous posts to this matter reg. My advice: Test the oldest driver you can find and which are working for your purpose. Hello Michael, thanks for your feedback. I already tried to install older driver, but the result was worse.

In my case and with the project that requires more memory, I think I will try 2 other options: use an additional external graphic card and second: try to interface my bit OPC client in virtual machine with an OPC server on a bit Windows and not bit Windows.

I have tried everything that has been suggested on this forum with the integrated graphics card, with no success. Maybe the driver you found are not old enough. The disadvantage of all this workarounds is the limitation to the old videodrivers with maybe less functionality and performance.

I also would like to know. In case of integrated graphics card, I can see a reason. These devices use the higher part of the existing memory, that is why when we have 4 Go of memory, only around 3. But this can not be the sole reason for the problem. Because the pae-paetch works actually with old driver and aktive integrated videohardware. I do not not know how I can proof this report exactly. If the reason for this problem would be the active use of the integrated videohardware than the pae-patch would never work, even not with old video-driver.

But the problem also occurs with some external videografic-cards and some newer driver. Of course I can confirm the problem and the working with old drivers only as I have reported in the past, not in general. OK, thanks for the explanation. Precisely, I needed these details, my problem is to run an XP virtual machine in Virtualbox with a sufficient amount of memory.

I will try to find and older driver, but not sure to find it, I have almost no details on the driver used in this PC. So I go hunting for the driver. Open the device-manager and go to the videografic-entry. Double-click and then open driver. There you find all informations about the used driver, version, date, hardware. You will find a large number of links, much of them fakes, but after some hours you will have an overview about the driver-history.

I dont know whether the current Winimages still has the old driver of the first Winversion or new driver. If working use drivermax or similar software for extracting the driver and delete the installation.

If not working do the same procedure with Win8 and Win7 or Vista until you find a working driver. Once you have found a working old driver you can test step for step newer driver until you have found the newest working old driver.

Per aspera ad astra. I tried all graphics card driver for the integrated graphics card, nothing to do! So we bought an Nvidia Geforce GT, installed the driver for it and it works well!

Win modified with patchpae3. All later video-driver do not work, system crashes will booting. Solution: Go to intel website, download HD system drivers, install latest bit drivers.

Thank you very much. Now only MB for Hardware reserved, crazy. Downloaded PatchPAE3 from the link in the immediately previous post. Extracted the 2 files PatchPAE3.

Still, if the patches above work then that will be brilliant, because Ive seen alot of complaints about this problem in forums but so far no fixes.

Without new drivers I dont know as it will work, but if AMD is recommending these patches then I might as well give them a go. Chiltonj1, thanks very much for the very useful input. I also used your links and installed 2 out of 4 successfully, the 2 that did not install said that they were not for my system. It did not start. The machine just did not want to start with all 4 DIMM's populated. Everything went well until Windows tried to load and blue screen. The machine restarted and then it just hung on the raid load screen.

So i restartrd the machine manually and again it hung trying to start. Ive contacted Asus and their Tech Support guy keeps asking me questions i answered in the previous respnse i gave him.

So guys, after spending the best part of 5 hours trying to get this machine running full bore i'm still no further forward. That sucks. Try having Crossfire enabled with the 4GB and then reapply the patches, reboot with crossfire enabled and then add the RAM.

That's what I did. Are you using CCC 7. I am also have a problem with 8 gb on vista ultimate x64 machine. I also have a ATI x My Machine boots fine and allows me to work on it until I try to do something heavy like copy the content of a gb drive to a gb drive. I get the BSOD. Or if I do any thing to resource consuming.

I have tested all ram to make sure they are all good and same batch. I have also tried to install Vista SP1 but that did not help. I am running the following config and really do need the 8gb and ultimate x64;. VS SP1 2 virtual machines setup to auto start with windows running 2gb ram total. I guess I will have to try reloading vista x64 on a clean partition with all 8gb installed to see what the system does. Don't waste your time.

Read the earlier threads and you will see that myself and other users have tried reinstalling Windows and this never worked. This memory uses 1. When memory is made at the manufacturers a chip is fitted and firmware is flashed on this chip with the hardware spec and resourse needs built in. I was sent a form from the Tech guy asking about excactly what i was using, Apparently they are going to attemp to replicate the problems we are having and get back to me.

So if any of you guys want to try adding more voltage to the DIMM slots when all 4 are populated go for it. Or even fit all 4 sicks and look in the Asus Probe2 to see what voltage is being sent. I cannot even get the PC to boot now with 4 sticks fitted so i canot try this.

And i cannot downgrade the bios image so i'll have to wait for a new release. But i remain open minded. Hey Rabbit, thanks for the info.

The mem voltage is interesting. I didn't even thing about that. After reading your post, the voltage has been pushed up to 1. My AI Suite has never worked properly either v 1. It immediately says that it stopped working but there is limited functionality on it. Kinda makes me mad that memory doesn't run at it's rated speed right out of the box.

Good luck. Maybe I just got lucky and the stars aligned with the 8GB working after those patches. I still think something isn't stable due to the fact that Vista is reporting my memory in Megabytes! I think they all like to say they support X, Y, and Z but don't anticipate people implementing high-end systems right away. My motherboard is also different to yours!

Even with all 4 DIMMs populated it still runs between the 1. That makes me even more doubtful that its the DIMMs and not the graphics driver. Its only when I enable crossfire things go wrong, I can alter anything else in the Catalyst Centre and yes its 7.

Once again that makes me pretty certain its their drivers, along with all the other forum posts Ive seen on this issue. ATI are very aware now that there is a compatability issue with Crossfire and Vista64 bit op systems.

They say that because 64bit technology is so new they didn't anticipate having problems. He also said that the Driver Support Team at ATI are working very hard to resolve the problem, which is encouraging to hear, but he also said that they do not know when it will be released could be 1 week or 2 months.

I think that i will push this further with ATI customer care beacuse these cards were mean't to work with Vista, regardless of the version. Maybe see if i can get a refund but i doub't it. Hopefully Release 7. My dad thought he'd found the fix for this on Tom's Hardware yesterday, but it turned out the post in the thread he was looking at was made by chiltonj and was the same as the one from here.

At least now that we know ATi know there should be some kind of fix planned, rather than the "we dont know whats going on in our company" fob off we've been getting so far. First of all i would like to thank Lionel Chen Microsoft for the original input and getting the thread started, cheers mate. And i would also like to thanks Ahriman, chiltonj1 and ghaynes for the valuable input. So i called Consumer Direct in the UK and they said that if the hardware isn't doing what it said it was meant to do i should take them back to the shop i bought them from and get a full refund.

Of course my cards are 3 months old now and the shop wouldn't take them back. But apparently i am still entitled a refund or exchange. Yesterday i got another ticket response back from ATI saying simply "we know there is a problem and our engineers are working on it.

Thank you from ATI. No appologies no possible fixes. Not satisfied with the response i called their tech support in the UK and got the same response on the phone.

So i called back the UK office and asked to be put through to someone else but not tech support, and i got this guy i shall not mention his name for obvious reasons , who was very helpful indeed.

I got a result from this chap, although, as i'm sure you can appreciate it wouldn't be fair to say what he did for me. And this has actually restored my faith in customer service and ATI. I don't know where you guys are from and what your laws are but if i were you guys i would seek further advise from a consumer body and get stuck in. You never know what you might get in the post. If your cards say that they will run Vista then the should run Vista, regardless of the version.

I hope all this info helps you guys, i don't think its fair that you spend a lot of money on parts and then end up spending hours trying to get them working when really they should just plug and play. I have spent countless hours ajusting, tweaking, plugging and unplugging hardware, looking for software, fimware updates and patches and to be honest i'm pretty fed up.. All i want to do is switch the machine on and play a game or watch the telly or movies.

I hope this thread stays on the forum for a while because i would like to hear how you guys get on with your own problems. Yeah, I posted on Toms also. The message has gotten a lot of hits. The native frequency for the Geil Black Dragon is Mhz, so i manually set this to Mhz in the bios. This seems to work and the memory is still performing very well. If i clock ant higher i get temp warnings and i don't know what the safe max temps are as of yet.

I have ran the Windows Experience Rating and i am now scoring 5. And i can use all my RAM. I switch back to 4GB it works fine. I switched my memory around still it works fine only with upto 4GB.

That rules out my new memory sticks. So it is not the motherboard. But that didn't make a difference either. I am wondering if this is Graphics card issue or OS? I saw some post indicating ATI had some fix for this. If you run 1 GPU you can freely populate all DIMM slots on your MB, regardless of what make or model, but you may need to install the patches from Microsoft, and you will likely need to increse the voltages to the RAM according to your RAM manufacturers spec, this info will be found on the little sticker on the mem stick.

You may also have to adjust the CAS timings too to run them that little bit sweeter, If you are using a gaming RAM the tolerances for adjustment will be more forgiving. I the lower the latency the faster the RAM responds and crunches the data that is given to it. I have since found out that there is a fix planned for the second half of this year, it's a long time away.

Get on to the GPU manufacturer and complain like hell. At the end of the day we have all bought products expensive products at that and they don't work. I just don't think they anticipated users filling all 4 slots, i mean vista ultimate will take Gb providing you can find a board and afford the RAM. They work fine upto 4GB. When I upgrade to 8GB same type of memory it was having problem.

I tried different memory timings, voltage etc. This worked out of the box without any custom memory timings or voltages etc. This worked fine. I also recommend running the memtest x86 program to verify your new memory. Been a while since someone posted, but this helped me and maybe other people. Someone else said to try to raise the voltage and it worked for me. My RAM said to go 2.

So I kept pushing my voltage up a little more and when I went two settings higher on the voltage, Vista x64 booted like a pro and 8GB of ram working fine now.

I would suggest to just keep bumping up your voltage little by little to see if you get somewhere. Don't go crazy though because you dont' want to fry any components. I originally had 4x 1Gb Corsair DDR2 Dimms in the system, installed Vista with SP1 integrated and everything was fine, I replaced the memory with 4x 2Gb Corsair DDR2 Dimms and the system does not start without blue screening and the blue screen is so quick that you cannot read the message.

If I remove two of the dimms the system is fine, I have tested each dimm in turn and they are all full;y functional, re-installation of an operating system is not really acceptable is it Microsoft. When the full 8Gb Was installed, Windows would not boot successfully without blue screening, so I decided to test something out, Memory Diagnostics passed on all the memory so there was no tporblems with any of the RAM whatsoever. So I proceeded to do a little more troubleshooting.

I booted Vista up into Safe Mode with Networking So I could still access the internet , Vista registered the full 8Gb RAM in safe mode which I thought was a little strange, if the system is going to blue screen with 8Gb then it would do the same in safe mode at least, but that thought went out of the window rather quickly. After this I decided to reboot the system and the system rebooted into normal mode successfully, and I have rebooted a few times and ran some tests on the system, and the system has been stable overnight running multiple benchmarks and cpu tests.

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:. Archived Forums. Windows Vista Hardware. Sign in to vote. System Spec. Vista Ultimate 64 MB. Intel Q GPU. Trying to fit 8Gb The memory part No.

Showing 1 - 15 of 27 comments. You will not be able to do it without rewriting the games code. Beths does not allow that. The best you can get is 3. Vanilla Skyrim uses 1 GB less than the patch. I guess you could do it if you were a coder, but you couldn't share it without possible legal repercussions.

Belanos View Profile View Posts. Skyrim is a 32 bit program, so it will never be able to use your 8 gigs of RAM. Only a 64 bit program can do that. The most any 32 bit program can access, if it's being run on a 64 bit OS, is 4 gig.

Though usually it's only about 3. Originally posted by Belanos :. Originally posted by cfs :.