The graphic card has nothing to do with VAS. Nothing at all.The problem is, we still didn't CONFIRM the source - in all the time you reply without an definitive answer how much your VAS usage is. The crash you are describing is an overloaded VAS (4GB+), and if it's not, then it's not OOM. Simple as that.We can hardly help you if you don't do that.Yep... seen it. But... mine is g2d.dll error.

Word Not Allowed,I managed to take the following screenshots using Process Explorer. The first is using the ifly 737 at uk2000 belfast. The second is after I changed location to UK2000 Birmingham - I tried to take a third but the computer locked up. It looks as though FS9.exe is going past 4gb.I hope I have the right column selected, please let me know if these are not the correct screenshots that you were afterThanksOli

Yep, that's correct.Now that you know that it is a real OOM, that FS9 is going over 4GB, you are sure it's NOT GPU driver. So you can stop looking there. Going back on the GPU won't be a solution. Can't be - to my knowledge.It's not common for computer to lock up because of this. Only FS9 should crash. Very simple...Some things I do when I have such problem (not necessarily this sequence):- deactivate scenery in FS9, to see where possibly problem is (incl. UT if you have it...)- activate ONLY scenery that is the suspect- start looking for empty texture folders- load scanafd(avsim library) to search for double afcads, these are deadly in fs9Always keep checking your VAS.If you do this with a system and diligently, you are likely to find a cause. I always did.Also, it's not impossible that it's a bad scenery (memory leak). Shouldn't be though, coming from UK2000...

I don't know if that's your normal configuration for FS9/FSX, Oli, but you're running an awful lot of useless programs there.Just in case you don't know about it, there's a great little free-bee by Ken Salter, called "Alacrity", which will kill all those 'Punkbuster2', and 'Firefox', background programs, etc... anything that the sim doesn't need ought to be killed, so that you have more memory available for your sim.Get it here.

While Alacrity will do wonders for the fluidity of the sim, it will do squawt for crashing sim on the OOM error basis. Just for the info.

I don't know if that's your normal configuration for FS9/FSX, Oli, but you're running an awful lot of useless programs there.Just in case you don't know about it, there's a great little free-bee by Ken Salter, called "Alacrity", which will kill all those 'Punkbuster2', and 'Firefox', background programs, etc... anything that the sim doesn't need ought to be killed, so that you have more memory available for your sim.Get it here.

Paul - thanks for the tip. I have been using another program called Gamebooster which I believe does the same thing, but in any case I may give Alacrity a try to compare IF I ever get to make another flight that is?!Im slightly worried by the amount of svchost.exe appears in those lists..

Yep, that's correct.Now that you know that it is a real OOM, that FS9 is going over 4GB, you are sure it's NOT GPU driver. So you can stop looking there. Going back on the GPU won't be a solution. Can't be - to my knowledge.It's not common for computer to lock up because of this. Only FS9 should crash. Very simple...Some things I do when I have such problem (not necessarily this sequence):- deactivate scenery in FS9, to see where possibly problem is (incl. UT if you have it...)- activate ONLY scenery that is the suspect- start looking for empty texture folders- load scanafd(avsim library) to search for double afcads, these are deadly in fs9Always keep checking your VAS.If you do this with a system and diligently, you are likely to find a cause. I always did.Also, it's not impossible that it's a bad scenery (memory leak). Shouldn't be though, coming from UK2000...

OK I'll go back and start doing that - better to start now I suspect while there is only a handful of sceneries, addons installed. Going to start with Ultimate Terrain as I believe (although I thought these had been solved with updates) that this is a major cause of problems such as mine.

I have been using another program called Gamebooster which I believe does the same thing, but in any case I may give Alacrity a try to compare IF I ever get to make another flight that is?!

Hey, Oli: Gamebooster doesn't belong in the same room as Alacrity. There has been a study or two posted around the Sim World which tested Gamebooster, and the concensus was that it does absolutely nothing to improve the performance of the pc while sucking one into the purchase of other softwares.Alacrity is free (donation if you wish), and is very configurable, besides setting up to launch TrackIR, (I launch FSX from a separate batch file) I use it to clean up the pc prior to doing a load test when overclocking. The app which it starts at the end of its clean-up is just a dos window: when I see that I know I can push the button.

Im slightly worried by the amount of svchost.exe appears in those lists..OK I'll go back and start doing that - better to start now I suspect while there is only a handful of sceneries, addons installed. Going to start with Ultimate Terrain as I believe (although I thought these had been solved with updates) that this is a major cause of problems such as mine.

svchost.exe is perfectly fine. I have it running 14 times. Normal thing with W7.UT is actually one thing in which I never found a bug... but you really never know. The memory leak is the worst - you should place yourself at the airport and observe if the VAS is growing without your input. And then when you fly, where it grows to such high number. It's very unusual for FS9 to grow up to 4GB. I have had about 350 lines of addons in FS9 and still usage not going much about 3.2 or about.

I have to jump in her, but guys, the correct solution was given early on but seems to have been dismissed.It's a common problem when upgrading video cards.You need more Ram....2gb is not enough when switching to these high end Video cards, and no, it doesn't matter if it's 32bit or 64bit. It's not an address space issue.It's to do with FS and the known limitations of Direct X 9. The main issue is; that Direct X 9 has to maintain a shadow copy of Video memory, in system memory. Now with the increase in video memory with the newer GPU,add to that, what's needed by the OS. and add to that, FS with all it's add ons, and there still has to be enough system memory left to carry the shadow copy of the GPU. If not, you get the OOM. Yes, even on a 64bit system.This is a FS and direct X 9 ( ie. XP ) issue, and Not with the newer memory managers in vista and Win7 which use Direct X 10 or 11, in which a shadow copy is not required.Every one here is correct in some way, you may fix it by removing some add ons etc, but really, save your self hours of grief and get at least 4GB of system Ram. ( 8GB recommended for 64bit )You didn't mention how much GPU memory your card has, but some have 2GB, can you see an obvious problem?interesting read here;http://support.microsoft.com/kb/940105keep up the good work guys,Ron.

I have to jump in her, but guys, the correct solution was given early on but seems to have been dismissed.It's a common problem when upgrading video cards.You need more Ram....2gb is not enough when switching to these high end Video cards, and no, it doesn't matter if it's 32bit or 64bit. It's not an address space issue.It's to do with FS and the known limitations of Direct X 9. The main issue is; that Direct X 9 has to maintain a shadow copy of Video memory, in system memory. Now with the increase in video memory with the newer GPU,add to that, what's needed by the OS. and add to that, FS with all it's add ons, and there still has to be enough system memory left to carry the shadow copy of the GPU. If not, you get the OOM. Yes, even on a 64bit system.This is a FS and direct X 9 ( ie. XP ) issue, and Not with the newer memory managers in vista and Win7 which use Direct X 10 or 11, in which a shadow copy is not required.Every one here is correct in some way, you may fix it by removing some add ons etc, but really, save your self hours of grief and get at least 4GB of system Ram. ( 8GB recommended for 64bit )You didn't mention how much GPU memory your card has, but some have 2GB, can you see an obvious problem?interesting read here;http://support.microsoft.com/kb/940105keep up the good work guys,Ron.

The shadow copy of the VRAM is in virtual memory, not physical memory.

To virtualize video memory, the video memory manager in Windows Vista assigns a virtual address range to every video memory resource. This range is conceptually similar to the copy that an application might create. However, the video memory manager manages the process more efficiently than the application might. The video memory manager uses the virtual address range to handle transitions or over-commitment of video memory. However, the virtual address range is typically unused on a system that has lots of video memory. As long as this virtual address range remains unused, no physical memory is allocated for it

but then...

In contrast, the system memory copy that is maintained in the older driver model is guaranteed to be fully populated with physical memory.

does that mean that directx9 apps running in Vista / Win 7 need their VRAM copy in physical memory for compatibility reasons with XPDM?So if I try to run FS9 or FSX on 1GB of RAM it will crash instead of slowing down due to massive page swapping?

The shadow copy of the VRAM is in virtual memory, not physical memory. but then...does that mean that directx9 apps running in Vista / Win 7 need their VRAM copy in physical memory for compatibility reasons with XPDM?So if I try to run FS9 or FSX on 1GB of RAM it will crash instead of slowing down due to massive page swapping?

So are you saying Ron and Daz that because FS9 is a DX9 program (I have DX10 I think) it plonks this shadow copy straight into the physical RAM - which would lead a large address aware copy of FS9 to exceed its memory and crash?My card is a 1gb I think from memory (I'm at work)

So are you saying Ron and Daz that because FS9 is a DX9 program (I have DX10 I think) it plonks this shadow copy straight into the physical RAM - which would lead a large address aware copy of FS9 to exceed its memory and crash?My card is a 1gb I think from memory (I'm at work)

I'm pretty sure adding more RAM won't fix your problem. The shadow copy sits in VIRTUAL memory and look at your FS9 virtual memory usage in PE. It's well above 2GB, almost 4GB, so it looks like a virtual memory issue. Does it crash when Process Explorer gets close to 4GB VA usage? It must be a memory leak or something?Try different drivers, disable all your scenery and traffic addons, lower your settings one by one, I dunno, try isolating things.You could even backup your system (with Acronis, or similar, or even with the built in system image utility of Vista) and try reinstalling FS9, then your addons one by one testing in between and try to find the source of the leak.You can also try on 1GB of RAM with only one memory stick. If it triggers the OOM error faster it could be an indication of a physical memory issue, but again I doubt that is the case. I'll do that test later with FSX & only 1GB of RAM and will get back to you. My 1.5GB VRAM GPU + 4V12 AA should easily crash the sim if Ron is right since the VRAM usage goes well above 1GB with that much antialiasing

I'm pretty sure adding more RAM won't fix your problem. The shadow copy sits in VIRTUAL memory and look at your FS9 virtual memory usage in PE. It's well above 2GB, almost 4GB, so it looks like a virtual memory issue. Does it crash when Process Explorer gets close to 4GB VA usage? It must be a memory leak or something?Try different drivers, disable all your scenery and traffic addons, lower your settings one by one, I dunno, try isolating things.You could even backup your system (with Acronis, or similar, or even with the built in system image utility of Vista) and try reinstalling FS9, then your addons one by one testing in between and try to find the source of the leak.You can also try on 1GB of RAM with only one memory stick. If it triggers the OOM error faster it could be an indication of a physical memory issue, but again I doubt that is the case. I'll do that test later with FSX & only 1GB of RAM and will get back to you. My 1.5GB VRAM GPU + 4V12 AA should easily crash the sim if Ron is right since the VRAM usage goes well above 1GB with that much antialiasing

This is the problem - I currently have no addons installed other than REX2004. The minute I add any addon scenery I get crashes.When FS9 starts I get virtual address space usage of around 1.6gb!

This is the problem - I currently have no addons installed other than REX2004. The minute I add any addon scenery I get crashes.When FS9 starts I get virtual address space usage of around 1.6gb!

But can you please confirm if it always crashes when it hits 4GB of VA space in Process Explorer?

But can you please confirm if it always crashes when it hits 4GB of VA space in Process Explorer?

Yes - always

But can you please confirm if it always crashes when it hits 4GB of VA space in Process Explorer?

If FS9 hits 4GB VA in PE, it will always crash. You might be lucky to go a little above 4GB and then drop again below, but that's it.. I've seen it happen on my system. 99% of the time, crash with OOM error.Another question is what is causing 4GB VA.I think FS9 cleanup and reinstall is needed to find the culprit. Complete reinstall, including manually deleting all user folders and folder where fs9.cfg resides. Complete cleanup.And then ONLY run fs9 + 9.1 patch. And check what's happening... without ANY addon!