WOW !!!After upgrading my system (Vista 32 bit, 4 GB RAM) I got the OOM errors constantly after 10-15 minutes.Now I have implemented this "fix" and it appears to work like a charm !Brilliant solution !Thanks a lot !Regards,Bernt

Everyone still happy with this fix, did it solve OOM errors for good?Also, I currently have 2GB installed , dealer said no point for more with Vista 32bit, said something about a 3GB limit, and little difference from 2 to 3GB. Should I upgrade to 3GB or 4GB, was the dealer missing something?/thanks

If you run Vista 32bit the limit is around 3 GB. So a update to 4 GB is vaste of money.To use the fix shown here, you didn't need to have the physical memory. It will work with 2 GB too.The fix shown here change the virtual adress space and this could be done even if zouh have only 512 MByte in youre PC.So youre dealer is right no point for more than 2 GB with Vista 32bit, but why no change to Vista 64bit, it cost only $4.

After flying a couple hours tonight, got the dreaded OOM error.Was using a F-18 addon aircraft, now sure if that had anything to do with it or not. Had run the fix 10 days ago, this is the 1st problem...

Hi,I downloaded the suite from http://www.ntcore.com/exsuite.php, however, it will not open my fsx.exe file (Windows XP).Is it possible to manually enter the data required into the fsx.exe, if so, can you tell me what to enter ?I have changed my boot.ini and this seems OK and I have changed the amount of virtual memory in the Control PanelSystemAdvancedPerfomanceAdvancedVirtual Memory to 2560 in both the min and max area's.What I dont know is if I was correct in changing the virtual memory as I have done, and if fsx.exe will pick up this information.Any help will be greatly appreciated.Best regards.John Cattell

I tried to do this in Win XP / FSX Post SP2 (Acceleration).When I click on the "click here" and select the mark.The FSX.EXE already has the setting "App can handle> 2gb adressest" selected.Do I still have to save it?Maybe the SP2/Acceleration changed the FSX.EXE file maybe?So I just did the Boot.ini to addthe "/3GB /userva=2560".Manny

I think you are correct, I remember reading that somewhere, that flag has changed with the SP2 FSX.exe.

yes, my blog post on Accel/SP2 indicated we marked the FSX.exe file with the 3G aware flag. No need to do anything to FSX, but you still need to modify the OS boot.

Thank you Thank thank you.That seemed to fix the problem for me.... Particularly with the PMDG 747 with which I discovered the problem for the first time.Woo hoo! MannyI think I saw that Phil blog 3G comment..I for some reason..thought that was for the physical memory.. and i was unable to add more than 2 G due to some issues..I had filtered it out completely.

Not sure if this is related to OOM, but my nemesis is the sporatic Fatal Error within FSX.Applying the "fix" did reduce the frequency of the CTD, but did not eliminate it altogether.APPCRASH Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: nvwgf2um.dll Fault Module Version: 7.15.11.6375 Fault Module Timestamp: 4705932a Exception Code: c0000005 Exception Offset: 00125c19 OS Version: 6.0.6000.2.0.0.256.1 Locale ID: 1033Additional information about the problem: LCID: 1033

"Applying the "fix" did reduce the frequency of the CTD, but did not eliminate it altogether.APPCRASHApplication Name: fsx.exeApplication Version: 10.0.61637.0Application Timestamp: 46fadb14Fault Module Name: nvwgf2um.dllFault Module Version: 7.15.11.6375Fault Module Timestamp: 4705932aException Code: c0000005Exception Offset: 00125c19OS Version: 6.0.6000.2.0.0.256.1Locale ID: 1033"You evidently have a corrupted nvwgf2um.dll with your installation of the NVIDIA 163.75 drivers. NVIDIA just released a new display driver that is WHQL certified. You can download the new display drivers or recommend you reinstall your current display drivers. Make sure you completely uninstall the old drivers prior to reinstalling. Best regards,Jim

I must admit to not fully uninstalling the driver set before intalling the 163.75s. That appears to be the culprit. Definately not an OOM issue.

I just wanted to add that the fix in the original post cured my OOM errors completely!

It appears that I declared victory prematurely with the FSX Fatal errors under DX10. I uninstalled and ran Driver Cleaner on the old Nvidia driver before installing 163.75s.nvwgf2um.dll is the culprit again. I had sucessfully flown from the US mainland to SE Asia in the PMDG 744 without a problem. The FSX error occured halfway accross the Pacific on the way back to N America near Fiji.

I think that is actually a driver crash for which I/we are waiting on news from nVidia.informing nVidia about bugs like this on their forum, like we did after SP1, is always a good thing.