HiAfter long time using XP 32 bit with fs9 I decide to try XP64 bit OS.No difference between XP 32 and XP 64 regarding FS9.If You don't do 3Gb patch even on XP64 bit You will have OOM message.After patching fs9.exe to use >2Gb you won't have OOM (if you have solved memory leak, if You didn't solve memory leak it will happen sooner or later), but new problem arrives.After 3Gb patch I have more frequent CTD with g3d.dll. Never have it without patch.Because of fs9 limit to use <2gb even without memory leak You will have OOM for example complex scenery+complex a/c.I spend days trying to find the cause of CTD on route LDZA-EGLL, near EBBR (Aerosoft), no progress.CTD with g3d.dll. As I see on task manager, no memory leak, no excessive memory usage, but game crashes.Filemon does not show any missing texture files, which could lead to memory leak and CTD.It shows only missing autogen files which does not exist anywhere on my PC.I read long time a go on FSInsider.com that stated there was some sort of issue with DirectX and the /3GB switch. No details of any kind were provided.So conclusion:To use non patched exe and have OOM (with complex a/c+scenery) orTo use 3Gb sw and pray to finish flight without CTD (g3d.dll)I hope that somebody will do similar a/c like PMDG for XPlane. I'm tired of troubleshooting fs9 with quality paywares.Edin

OK, with a 64bit OS you do not need to run the 3GB patch and mess with your boot ini.All that you need to do is patch the FS9.exe to be large address aware (so it can see beyound the 2GB limit).That is it.Are you using the latest version of AES? Because older versions of AES would cause a g3d.dll error with the large address aware enabled FS9.exe, the newer versions do not have this isuue.I do not think it has anything to do with DX read this post here (and the DX problem is fixed).http://blogs.msdn.com/ptaylor/archive/2007...ress-space.aspx

Well i must dissapoint you :(...I use 32 bit XP, without 3gb switch, and NEVER have CTD or OOM. Planes i use/have installed, beside default one, are PMDG MD11 and 747, Ariane 737, CLS Airbus 330 and DC10 and thats it. Scenery...well there is all "mega" from Aerosoft, FSDream Team, Fly Tampa...and i have ALL WoAI packages installed...+REX, GE Pro, AS 6.5, Zinertek Ultimate Water Advanced...Last few months i started to fly long haul routes, EHAM-TNCM, EGLL-KBOS, EDDF-KJFK...and so on, and afcourse, i do that just for fun, so i don't sit for 8,9 or 10 hours in front of the monitor. Plane fly i do some other things.My machine, which is not something special, is:E2220 Intel dual core3GB memory8600GTS 512MB24FPS constant lock at 30, with 1024x1024 DXT3 REX clouds.Why em i write all this? Well because there must be something wrong with your system, or with some add on you use. For example, do you have latest drivers for GPU, latest DirectX, mother board drivers...or maybe plane making you trouble. I know for sure that Wilco 737 can cause CTD and OOM...there is really TOOOOO many things that cause problems, FS9 is just very small part of it. Just ask your self, "Why pure and clean FS work like a charm...?"Cheers mate! :(

After 3Gb patch I have more frequent CTD with g3d.dll. Never have it without patch.

Edin,I must tell you I did have g3d.dll errors both before and after the 3GB patch. Though in my case they don't cause CTD but FS termination and error report.However they were more frequent before the patch!Actually I had a g3d.dll with FISD EFHK every time I tried to fly there, before and after.So I did some thorough research and spied three suspicious files. After deactivating them, no more g3d.dll.Conclusion: I don't associate g3d.dll errors with applying the 3GB patch.If you do take care of your addons, don't mess too much, don't use poorly made ones plus do regular checks - no problem.I'm using the 32bit XP Home, 3GB switch and AES.

Hi Rafal and other guys and thanks.Yes when crash happens I have fs9 termination with report :( .I don't have many scenaries installed, only proven from Aerosoft and similar etc.For me it is strange that crash always happen on approx. same place 20nm inbound BUB (HGD 300) (VOR at EBBR) but only at route LDZA-EGLL (LDZA PODET UL25 VATAL UL608 LOGAN EGLL) with PMDG 747.If I try for example EDDF-EGLL (connecting on same waypoints like with previous one), crash does not happen.Also, Mem usage before crash wasn't to big around 900000K.I tried to TO from EBBR and fly to approximate position with same distance and heading from BUB and no CTD this time.I don't see what could cause this. If the error is permanent, then I will have it all the time (when approaching BUB VOR) or....What are You suggesting to check?FILEMON shows only missing agn files.For test I deactivate EBBR 2007 (from Aerosoft) and sim didn't crash.I don't think that EBBR is cause of crash.I never had this error before 3gb patch.I have latest drivers MBO, VGA etc...To dallyborr: I must say that You are very lucky, and If possible could you please attach screenshot with Mem usage when sitting at gate FSDT KJFK with PMDG (ready to taxy) with ASV weather active. I know that without 3gb patch sim will crash with MEM USAGE around 1.6Gb. And I think with this scenery and PMDG 747 I have it around 1.2-1.3Gb, very small gap to limits for OOM.Edin

I agree, dont point to the 3GB switch so quick, Ehasanov.I use WinXP 32 Home and both the 3GB switch and fs9.ewe 2gb aware. No OOMs nor CTDs.I recently encountered those g3d.dll crashes though, and I was fortunate enough to find the culprit: it was the latest Aerosoft frankfurt update. What I did? I moved it under all my other sceneries in the library, and that solved the problem. So it's not only crappy sceneries who cause problems, sometime it's nice famous ones.I've been lucky to find the cause of my g3d.dll, but that was easy: the g3d.dll crashes started right after I installed the new scenery.Have you always had those crashes or did it start recently? If so, check what you have last installed and try stpe by step, doing always the same flight that causes FS to crash.That's what I did, flew 3 times an EDDF-EHAM flight, had 3 times g3d.dll crash. When I found the solution, to make sure I had it sorted, I flew again EDDF-EHAM flights without any problems.FS is definitely not en exact science. So many different setups, different PCs etc.

could be a corrupt texture

Use some more tools for your search and check.Try these, they helped me a lot:- http://aifs.pvdveen.net/- http://www.nwlink.com/~erog/The reasons are usually corrupt bgl files (both Scenery and AFCAD), but also textures (bmp) and even effects (fx) can crash your seem.The worst case is the textures. If you suspect AI, try deactivating the airlines (one by one) which occupy your favourite airport.If you get the erros in flight, see if it happens always with exactly the same route. Errors in you navdata (FMS data) may be responsible too.

Hi to all.I experience this error from time to time.It does not appears on my regular routes (short one, around 1h).I have EBBR installed from beginning but crash does not shows till now.I have turned off AI before, because of possibility of corrupted textures.I don't know, my wife will kill me because sitting and flying same route for testing :( And I'm using UTE, but for me it is strange that crash does not happens when I'm flying from other location.It should crash if the problem with corrupted textures, effects or other files exist.If I go from point A to B and to C, sim will crash at C (around C). If I go from A1 to B to C, sim will run normally and I will reach EGLL without crash.This part is strange. I tested only with 747, maybe to try another a/c, Edin

I have no idea what causes these for people, but I've been flying FS9 since the day it was released and I've never had a crash that wasn't caused by 3rd party scenery. I've used XP 32 bit, Vista 32 bit and Win 7 64 bit. All have worked great. After I formatted clean for Win 7, I reinstalled clean and had a CTD around Florida seemingly out of nowhere. I disabled all scenery from this area and the problem went away. I am very picky on what add-ons get installed (especially scenery). I keep a database of every airport I add. If I get a crash, everything recent gets uninstalled until I find the culprit. I also completely re-install my OS and flightsim every 2 years max (usually every one year). I'm not a Windows basher, but I've never had a version of Windows that didn't get "funny" after a year+ (and I work in the IT industry). Maybe I've just been lucky with my combination of add-ons or something. I've never used the memory switch, or any other modified fs9.exe. Just the one patched to 9.1.

HiAfter long time using XP 32 bit with fs9 I decide to try XP64 bit OS.No difference between XP 32 and XP 64 regarding FS9.If You don't do 3Gb patch even on XP64 bit You will have OOM message.After patching fs9.exe to use >2Gb you won't have OOM (if you have solved memory leak, if You didn't solve memory leak it will happen sooner or later), but new problem arrives.After 3Gb patch I have more frequent CTD with g3d.dll. Never have it without patch.Because of fs9 limit to use <2gb even without memory leak You will have OOM for example complex scenery+complex a/c.I spend days trying to find the cause of CTD on route LDZA-EGLL, near EBBR (Aerosoft), no progress.CTD with g3d.dll. As I see on task manager, no memory leak, no excessive memory usage, but game crashes.Filemon does not show any missing texture files, which could lead to memory leak and CTD.It shows only missing autogen files which does not exist anywhere on my PC.I read long time a go on FSInsider.com that stated there was some sort of issue with DirectX and the /3GB switch. No details of any kind were provided.So conclusion:To use non patched exe and have OOM (with complex a/c+scenery) orTo use 3Gb sw and pray to finish flight without CTD (g3d.dll)I hope that somebody will do similar a/c like PMDG for XPlane. I'm tired of troubleshooting fs9 with quality paywares.Edin--------------------------------------------------------------Edin, something else is wrong. I have W7 64 Ultimate and never have O.O.M. issues. Flights can be for 11 hours or more....(trans Atlantic) and no CTD's. Something else with your system is causing this rather than 32 bit or 64 bit. My guess, anyway. Check that you are not having the g3d.dll issue. This is where this .dll will crash FS9 or FSX as you transition to a new scenery layer. This has happened pretty much since FS98! Some get it, some don't as to what add-ons and such they have onboard.Mitch

Thanks for help.It is very hard to find when this happened, after which scenery installation, because appearance is not so frequent and depends on flight.I will try to search and in worst case deactivate EBBR. After that I have finished the flight without the problems.Edin

could be a corrupt texture

I agree with the others...you have other problems. It IS quite possibly a bad texture. Perhaps a ground texture? You're going to have to start eliminating sceneries one by one and fly the route that gives you ctd's to find the ofending texture. Good luck.

I agree with the others...you have other problems. It IS quite possibly a bad texture. Perhaps a ground texture? You're going to have to start eliminating sceneries one by one and fly the route that gives you ctd's to find the ofending texture. Good luck.

No progress.Only way to end the flight is to disable EBBR scenery. After that, I reach EGLL without the problems.Filemon shows few missing bmp but nothing special.Mem usage not more then 960000K.Edin

How do you patc fs9 exe to use more than 2gb? is it just the standard 9.1 update?