Here is a thread over at the Nvidia Forum that deals with driver problem. I added my name to the user list that is having issues.http://forums.nvidia.com/index.php?showtop...&st=0&p=279236&In the meantime they have released the beta 169.09s today. I'll see if I can duplicate the problem with the new release.

Thanks for your tip, I am in the process of working through it. I am waiting for the FSX Accell/Sp2 package to arrive shortly, so have done the bcdedit part in vista and have had a look at my nvidia system information. I have a nvidia 8800GTX/768MB board on a 6600 dual core system.1. It states that total memory is 2302MB and dedicated video memory is 768MB which would indicate that I have done it right? 2. I also found somehting about installing KB905866 in regard to paging size, has anybody played round with this?3. Does anybody know whether the Shared system memory being 1535 and system video memory being 0 has any significance.4. Does running FSX as an administrator make any difference.5. Using nvidia to override the FSX filtering and anti-aliasing make any difference?RegardsNeville

>Thanks for your tip, I am in the process of working through>it. I am waiting for the FSX Accell/Sp2 package to arrive>shortly, so have done the bcdedit part in vista and have had a>look at my nvidia system information. I have a nvidia>8800GTX/768MB board on a 6600 dual core system.>>1. It states that total memory is 2302MB and dedicated video>memory is 768MB which would indicate that I have done it>right? >2. I also found somehting about installing KB905866 in regard>to paging size, has anybody played round with this?>3. Does anybody know whether the Shared system memory being>1535 and system video memory being 0 has any significance.>4. Does running FSX as an administrator make any difference.>5. Using nvidia to override the FSX filtering and>anti-aliasing make any difference?>>Regards>>NevilleHi Neville,if the taskmanager, not the system information from Nvidia, shows more than 2049 MB you done it right.2. The KB905866 is a update for the Junk Mail filter (http://support.microsoft.com/kb/905866/en-us), I guess you mean another article?3. Shared memory for the graphics card means, the space of normal memory the card can use if the 768 MB are full.4. Dont know, guess no.5. Visual, maybe, performance wise dont know, guess no.Hope this help.

Hello,I have done the ntcore suite and bcdedit mods suggested here to my system (Vista Home Premium 32 bit, Duo Quad Core, 4 gigs RAM) yet task manager shows I'm only maxing at 2 gigs of memory when running FSX. Any suggestions? Thanks,Joel

The OOM update Phil described at his forum I have installed.All other Vista updates.I have 4 Gb of memory ; the Bios sees 3072 mb and Windows sees 3071 mb.However I am having Out Of Memory errors.Does the OS tweak do anything for me I can benefit from ?Or is there something else that can be done ?

I might be wrong on this, but I think SP2 addresses/fixes the OOM error.-Arvid

Looking into the possibility of making the 2+ GB address space change. CFF Explorer tells me that the "App can handle> 2gb adressest " is already checked. Seeing the date of your post, is this a change implemented by SP1 or SP2 ? Just curious what flipped the flag !

>Looking into the possibility of making the 2+ GB address>space change. CFF Explorer tells me that the "App can handle>>2gb adressest " is already checked. Seeing the date of your>post, is this a change implemented by SP1 or SP2 ? Just>curious what flipped the flag !The 'flag' was set in SP2, as mentioned on Phil's blog as well as the readme files no one ever reads... ;)

Hi,Look at reply #35 above in this post, from Phil:"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."If you are running SP2, then it appears as though all you need to do is change the boot.ini file. I recall too taht you need the latest DX9C (assuming you run XP as the OS).Bruce.

>The 'flag' was set in SP2, as mentioned on Phil's blog as well>as the readme files no one ever reads... ;)>Read the readme files?!!!!Gesh..... next thing you know they'll be expecting me to stop and ask for directions as well :-hahron

thanks for this fix!i too was getting OOM errors in FSX SP1 with PMDG 747 aircraft, after this my textures are wonderfully sharper and although it takes the same long time for FSX to boot up and go through it loading process, closing FSX is amazingly fast, before when i closed FSX i would get the dreaded error message, but not now!i will just have to put it to its ultimate test with a very long haul flight over the weekend and see how it goes!on a side note i also got FSX running smoothly! so i may finally ditch FS9 for FSX, the graphics and camera views are great in FSX!!!

The /3GB line fixed my OoM errors (great!), but unless I have the userva value as low as 2112 (which hardly helps with OoM problems), I get serious texture loading problems: very blurred ground, a/c (including Ultimate Traffic AI at airports) with no liveries or VC gauges etc. (not great at all!).What I really don't understand is this:Why with a /3GB switch do textures stop loading correctly like this right from FS9 startup: when FS9 has only just opened there is usually at least 1GB of free physical RAM showing, so why am I getting these texture loading problems right from the outset, with so much physical RAM still available?Textures load up fine without the /3GB modification. Is there any way around this or am I going to have to forget the /3GB fix and go back to OoM errors?Thanks,Martin