Sign in to follow this  
martinlest2

"Your computer has run out of available memory" - any troubleshooting tips?

Recommended Posts

I get this (inaccurate) message sometimes, like just now flying happily from KSEA to CYVR. I thought it was a thing of the past: my PC has certainly not run out of memory - my O/S is Windows 7 x64 with 16GBs of RAM installed. My desktop CPU usage meter showed that there are still well over 11GBs of physical RAM free at the time FS9 crashed and the page file (I have it set to 1024MBs fixed - partly to stop it resizing itself on my SSDs) shows 0% usage. I would increase the page file, but as it is hardly ever even used, what would be the point?

 

I have also read that this error message can be generated by a corrupt page file; but I have also read that this only applies to Windows XP, not Win7 and later. Anyone know differently?

 

Nothing at all related to the cause of the crash in Event Viewer (just the consequences of it).

 

This error is usually (in my experience) generated by a faulty scenery file (bgl/bmp). I wonder if anyone has had this "OoM" problem in the area in which I was flying and could indicate what might be amiss.

 

Thanks,

 

Martin

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

That message is generally displayed when you have run out of VAS (Virtual Address Space). That is not the same as RAM. It's strange to hear of someone getting an OOM in FS2004, but that message was all too familiar to me when I used FSX and P3D v2!

Share this post


Link to post
Share on other sites

Thanks.

 

What exactly is VAS then? (Well, I see what it is from Googling, but what is the relevance here to FS9?). No, not the same as RAM, I know,and not the same as virtual memory (page file) either. How and why would I 'run out' of it.. and can this be fixed?

 

I started up my flight to Vancouver again from the same spot, with AutoSave, and it is running OK for now. So perhaps (though not conclusive) it's not a scenery file problem on this occasion.

Share this post


Link to post
Share on other sites

I get this (inaccurate) message sometimes, like just now flying happily from KSEA to CYVR. I thought it was a thing of the past: my PC has certainly not run out of memory - my O/S is Windows 7 x64 with 16GBs of RAM installed. My desktop CPU usage meter showed that there are still well over 11GBs of physical RAM free at the time FS9 crashed and the page file (I have it set to 1024MBs fixed - partly to stop it resizing itself on my SSDs) shows 0% usage. I would increase the page file, but as it is hardly ever even used, what would be the point?

 

I have also read that this error message can be generated by a corrupt page file; but I have also read that this only applies to Windows XP, not Win7 and later. Anyone know differently?

 

Nothing at all related to the cause of the crash in Event Viewer (just the consequences of it).

 

This error is usually (in my experience) generated by a faulty scenery file (bgl/bmp). I wonder if anyone has had this "OoM" problem in the area in which I was flying and could indicate what might be amiss.

 

Thanks,

 

Martin

Wow  I had  this  all  the time  when I flew  to cyvr  from  ksea   always  the same  spot was  a orbox  bgl  file  that was  the culpit   found  what it  was  and  removed   the 2  offending  files  and  no more ooms..  But   they  should  have  fixed  this with  the latest   patches.  So if  your  crashing  at the same  spot  all the time   as  I was  than it  the scenery  issue

Share this post


Link to post
Share on other sites

I would allow Windows to manage the page file size just in case, FS2004 does use it. On my Windows 7 x64 Ultimate, Windows has allocated a minimum of 12mb, recommended 12283mb, currently using 8189mb on my 1tb HD, and I've never had an OOM crash.

Share this post


Link to post
Share on other sites

Ok.. here's what the message means: The application (in this case FS9) tried to allocate memory for use and was denied the allocation. When the OS does not allow an application to allocate memory, you get an OOM. FS9 can only access around 3gb of memory, so if something is chewing that up via allocations (bad scenery BGL, etc)... it is going to get the error sooner or later. It's not a page file issue, it's not a physical RAM issue, it's not a hard drive space issue.

Share this post


Link to post
Share on other sites

Thanks for the replies. I knew it wasn't anything to do with physical memory and 95% sure it was nothing to do with pages memory either (and 100% certain it had nothing to do with disc space!). My fs9.exe is the /3GB patched version, BTW.

 

As I mentioned, I have usually been able to cure these problems (fortunately rare) by locating the faulty bgl or bmp file and removing it, but that is a long process as it is often by trial and error, and is especially frustrating when the crash is intermittent and cannot be reproduced every time you fly the same route.

 

I am very pleased to get some specific advice therefore! Thank you Pete, but which file was the culprit? What is an 'orbox' bgl file? I have no files called 'orbox' anything in my FS9 setup, bgl or otherwise. Which scenery/update were you talking about?

 

Hope you folks have a good Christmas meanwhile...

 

M.

Share this post


Link to post
Share on other sites

<p>Rerunning the flight, another CTD as I was descending on the glidescope, CYVR Rwy8L. Certainly 'felt' like a bgl error (having had so many over the past 12 years, each CTD has a kind of feel to it!)...

 

</p>
<p> </p>
<p>Problem signature:<br />
  Problem Event Name:    APPCRASH<br />
  Application Name:    FS9.EXE<br />
  Application Version:    9.1.0.40901<br />
  Application Timestamp:    4135a208<br />
  Fault Module Name:    d3d9.dll<br />
  Fault Module Version:    6.1.7601.17514<br />
  Fault Module Timestamp:    4ce7b7b3<br />
  Exception Code:    c0000005<br />
  Exception Offset:    00034706<br />
  OS Version:    6.1.7601.2.1.0.768.3<br />
  Locale ID:    2057</p>
<p> </p>

<p>Sometimes seems to me these days that completing a flight with no errors is the exception rather than the norm!</p>

Share this post


Link to post
Share on other sites

Even AVSIM has 'crashed' now! What's all that code doing there?

 

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    FS9.EXE
  Application Version:    9.1.0.40901
  Application Timestamp:    4135a208
  Fault Module Name:    d3d9.dll
  Fault Module Version:    6.1.7601.17514
  Fault Module Timestamp:    4ce7b7b3
  Exception Code:    c0000005
  Exception Offset:    00034706
  OS Version:    6.1.7601.2.1.0.768.3
  Locale ID:    2057

Share this post


Link to post
Share on other sites

Different error - it's in the DirectX code. May be a bad video driver or texture.

 

FWIW, if you have a 64-bit OS it may make sense to set the LARGE_ADDRESS_AWARE bit on your FS9.EXE file - it will allow it to get a full 4GB of memory instead of 2GB.

 

Cheers!

Luke

Share this post


Link to post
Share on other sites

<p>Rerunning the flight, another CTD as I was descending on the glidescope, CYVR Rwy8L. Certainly 'felt' like a bgl error (having had so many over the past 12 years, each CTD has a kind of feel to it!)...

 

 

Are you running Vancouver Plus, by chance?  I used to have to run the texture configurator to resolve CTD issues in that area.  fwiw.

Share this post


Link to post
Share on other sites

CYVR Vancouver International Version 1.0 by Jonathan Gabbert (AVSIM library) for the airport (about the only one out there of any real substance of course).

 

I don't have Vancouver Plus, no. I only really fly in and out of CYVR, IFR, never around the area, so probably not worth it (It is on sale on SimMarket for a bargain price though, if anyone thinks it's a 'must have', even so! The reviews there are amazingly good). 'Part 2' includes the airport, it says, but since this 'part 1' scenery is now so old (2005?) I suppose the project was abandoned? If the two were available together I'd probably go for it...

 

Whatever, have to look elsewhere for the CTDs..

Share this post


Link to post
Share on other sites

My exe file is patched, as I mentioned above. Thanks.

 

Apologies, I missed that. It's unfortunate that with FS you really need to install addons one at a time to ensure you can rollback if one is a little wonky. Scenery is especially challenging.

Cheers!

Luke

Share this post


Link to post
Share on other sites

I had such issues too, and they were due to some bad scenery files. So before waiste time or invest in other sceneries, try to deactivate all your sceneries and check whether you still have the same issue at the specific Position with your "virigin" FS. If not, you reactivate the sceneries steps by steps (about 20 at once) until you get the issue again. Finally you might be able to localize the responible scenery and the file. Needless to say that you should backup your scenery.cfg before starting deactivation. For this kind of handing I use FS Scenery Manager as it's very easy and fast to handle.

 

Bernard

Share this post


Link to post
Share on other sites

Hi, thanks for the comments. Yes, I have got to the bottom of many an issue like that, starting with the most likely culprits and deleting the sceneries from the scenery.cfg file (I have multiple backups!). If that doesn't work, then I start with a 'clean' cfg file and add sceneries back a large bunch at a time (i have almost 1400 entries, so it's quite a task). I use an aircraft folder with only the default Cessna in it, which hugely speeds up loading times between restarts of FS9. When you find the right one scenery, you can then move individual bgl files out of the folder until the one(s) responsible are located.

 

What is a problem in this case is that the sim can't be relied upon to crash every time and it could take days to hunt down a bgl file, if any. As I said above, after the CTD en route to CYVR, I restarted FS9, with the help of AutoSave, at a point just before the crash. And things went fine, at least until another crash half an hour later (which would not have been caused by the same problem, I am sure).

 

Sometimes tempted just to ignore it and move on - I don't fly in that part of the world all that often! I will try a few more test runs around the point of the last CTD but it's so unpredictable I doubt I'll get any real clues as to what is responsible.

Share this post


Link to post
Share on other sites

Thanks for the replies. I knew it wasn't anything to do with physical memory and 95% sure it was nothing to do with pages memory either (and 100% certain it had nothing to do with disc space!). My fs9.exe is the /3GB patched version, BTW.

 

As I mentioned, I have usually been able to cure these problems (fortunately rare) by locating the faulty bgl or bmp file and removing it, but that is a long process as it is often by trial and error, and is especially frustrating when the crash is intermittent and cannot be reproduced every time you fly the same route.

 

I am very pleased to get some specific advice therefore! Thank you Pete, but which file was the culprit? What is an 'orbox' bgl file? I have no files called 'orbox' anything in my FS9 setup, bgl or otherwise. Which scenery/update were you talking about?

 

Hope you folks have a good Christmas meanwhile...

 

 

 

http://www.orbxsystems.com/forum/topic/53664-ctd-near-cyvr/#comment-475371

 

http://www.fsdreamteam.com/forum/index.php/topic,8099.msg66636.html#msg66636

 

M.

 

 

If you havnt got fdst cyvr and orbx than it be a diferent issue you have than I had and others had

Share this post


Link to post
Share on other sites

Yes, but those are for FSX only - and this is the FS9 forum. So it will be different, you are right! :-)

Share this post


Link to post
Share on other sites

OK, another OoM crash. This time just east of EDRZ (I was flying from ELLX to LOWW). FS9 freezes (it doesn't crash, as such), but still 'works', inasmuch as the menu bar still opens when I press 'Alt' and all the options, like choose aircraft, show, but once I come out of full screen mode, the FS9 window is black, and is still if I go back to full screen. When I minimise the FS9 window, there is the cursed "Your computer has run out of available memory. Flight Simulator will now exit...." message. Well, there is still 11.5GBs of free RAM and 1GB of (unused) page file, so it has NOT run out of memory of course (as noted in an earlier post in this thread).

 

I run Windows 7 64-bit and have a 4GB patched Fs9.exe file. I thought I'd left these errors behind when I changed to 64-bit, some years ago now! Horrible to be getting them again. At least when I got OoM errors in FS with XP 32-bit, I could see that there really was no RAM left, and could always locate the bgl or bmp file that was to blame. Here, well, who knows??

 

Hard to think it's another scenery file error, but possible I suppose. I am using a recent nVidia driver - 359.06.

 

Any other ideas? I really am SO fed up of one problem after another with FS now (I seem to complete fewer than half of my flights without an error of some sort stopping me flying - different errors - and as fast as I fix one - or imagine I have - another comes up). If I weren't so addicted to FS I'd wipe the whole PC and forget it, it's hardly worth the frustration sometimes.

 

I suppose I could backup, uninstall and start afresh with a clean FS9.1, then add third party stuff bit by bit. Not much fun though, and it will take forever!!

 

What else could be causing these occasional OoMs? If it were every time, it would be easier to troubleshoot, and of course, if I reload the flight at the place it just crashed (not always easy with 3rd. party aircraft, they don't reload their panels state - reload the flight and the engines and electrics all shut down!), most likely it will continue quite happily from where it left off, so how even to begin troubleshooting this??

Share this post


Link to post
Share on other sites

Hi.

 

Do I recall someone once mentioning that having landclass bgls in a scenery layer that also contains a texture folder can tie up your memory by forcing FS9 to hunt endlessly for non-existent texture files?

 

I don't suppose that's causing the problem is it? I guess that restarting FS9 and picking up the flight where you left off would probably kill the endless search and re-free the memory.

 

Regards,

D

Share this post


Link to post
Share on other sites

I once ran Process Monitor out of curiosity and was surprised to find my FS2004 was constantly searching for some tree texture or other, causing a memory leak. I created a notepad file and saved it in the main Texture folder as tree_su.bmp or whatever the name was and that fixed it.

Share this post


Link to post
Share on other sites

Yes, Process Monitor has been very helpful in the past. Despite what I said (in frustration) I think this being down to a rogue file is the most likely. I am going to try again (last time didn't work) to get Process Monitor to run remotely, so that I can monitor things from a second PC on my network.

 

I have also let Windows create and manage its own page file. Even though it is not really being used, it could be a factor (??). Now got a page file of 16GBs.. if I still get OoM crashes, I'll put it back to 1GB, but I need to try everything to eliminate it from the possible culprit list.

 

Will keep you 'posted'! Thanks.

Share this post


Link to post
Share on other sites

 

 


I have also let Windows create and manage its own page file. Even though it is not really being used, it could be a factor (??). Now got a page file of 16GBs..

 

It's not a factor.

 

Cheers!
 

Luke

Share this post


Link to post
Share on other sites

Hi. Well you say it isn't, other folks on tech forums say the opposite. Usual thing :smile:  I tend to agree with you, but I'll try anything once!

Share this post


Link to post
Share on other sites

The page file provides virtual memory to the entire system. If your commit charge (ie. total memory used) when FS9 crashes is substantially less than your physical RAM, the page file isn't being meaningfully used and therefore increasing it will not make a difference.

 

Cheers!

Luke

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this