Jump to content

Archived

This topic is now archived and is closed to further replies.

guy

"Insufficient Memory" at FSX startup!

Recommended Posts

Hi all, When I try to start FSX the FSX image appears and then, during STARTUP, after 5-7 seconds themessage "INSUFFICIENT MEMORY. Restart FS with other settings...." comes up. This happen's now all of a SUDDEN.I still use Vista 32 bits(with 4 MB memory and 500 giga free disk space),but I NEVER have had memory problems during the 3 years I use FSX now.Also I did not install anything new or modified anything during the last days. I have found a Microsoft topic about it:http://support.micro...kb/892610/en-us I tried to follow their advice.I have rebuilt the windows paging file.I have run dxdiag and memory test, evrything is ok. I have also analyzed the logbook of Fsx. It is ok, no corrupt entry.I have deleted then the Fsx.cfg file to force FSX to create a new one. But nothing helps! Has anybody ever seen this, Insufficient memory during FSX startup?Would be grateful for any ideas. Guy

Share this post


Link to post
Share on other sites

FSX can only use 3gig of ram, even on a 64bit system. Have you replaced your video card with a larger Ram one, have you installed any addons. Check your startup list and see whats being loaded, you may simply have too many other programmes loaded.

Share this post


Link to post
Share on other sites

Thanks for the answer.I have several addons installed (LVD, Pmdg, IFly.etc)They have always worked without problems.The video card has 512 MB. I haven't changed anything on this system in the last 2 weeks.Fsx has run well still yesterday, and today it refuses to start even when no other application is running!The message comes immediatly, only 5-7 seconds after the start and the task monitor indicates that only 25% of memory is in use at this moment.The most astonishing is that this happened all of a sudden, without an apparent reason! Guy

Share this post


Link to post
Share on other sites

Download Memtest and run some tests on your physical memory sticks. Is the pc running warm, by any chance?

Share this post


Link to post
Share on other sites
Hi all, When I try to start FSX the FSX image appears and then, during STARTUP, after 5-7 seconds themessage "INSUFFICIENT MEMORY. Restart FS with other settings...." comes up. This happen's now all of a SUDDEN.I still use Vista 32 bits(with 4 MB memory and 500 giga free disk space),but I NEVER have had memory problems during the 3 years I use FSX now.Also I did not install anything new or modified anything during the last days. I have found a Microsoft topic about it:http://support.micro...kb/892610/en-us I tried to follow their advice.I have rebuilt the windows paging file.I have run dxdiag and memory test, evrything is ok. I have also analyzed the logbook of Fsx. It is ok, no corrupt entry.I have deleted then the Fsx.cfg file to force FSX to create a new one. But nothing helps! Has anybody ever seen this, Insufficient memory during FSX startup?Would be grateful for any ideas. Guy
By any chance, is this when you load the PMDG 737NGX? (If you have it of course) If so that is probably your problem. The NGX uses a massive amount of memory, being as detailed as it is. For 32 bit systems especially, you need to reduce FSX's initial memory load. These are the things you need to try. Set your USERVA to 2816 (Which is the proper setting for a 512MB video card)If you have other complex addon aircraft in your dll.xml, set the ManualLoad field for each unused (in the current session) addon aircraft, and any other unused utility to TRUE. This will make FSX ask you each startup whether to load that DLL into memory. Say No to each one you are not using, and yes to the one(s) you are. (Again in that session) Note don't set it to any that are used all the time or is scenery dependent, such as FSUIPC, or FSDT's Addon Manager. Doing this was enough for me to get the NGX running smoothly on my system (Also a Vista 32bit system). If that's still not enough, reduce some of your graphic settings.

Share this post


Link to post
Share on other sites

Thanks for the answers.I said in my initial message that I have already deleted Fsx.cfg and run a memory test.The PC is also not too warm and Userva is set.I tried the dll.xml modification (manualload =true), makes no difference.I do not have the pmdg ngx but the pmdg 747x, Lvd 767, ifly 737 etc have always run without problems. I have had no problems at all until now with FSX or any add-on and haven't done any modifications.The message "Insufficient memory" comes not when I load an aircraft,but IMMEDIATLY after STARTING FSX! Guy NB: I have the french version of Fsx.

Share this post


Link to post
Share on other sites

Down load and run malware bytes, just incase there is a gremlin causing the issue. It has to be manulayy updated but is really good

Share this post


Link to post
Share on other sites
FSX can only use 3gig of ram, even on a 64bit system.
Wrong wrong wrong!!! FSX can use up to 4GB of VIRTUAL SPACE! Nothing to do with RAM. How often more?On 32bit, it's another story though. With userva, 3GB is correct. But still virtual space. And to the OP: couple of things to try.1) backup dll.xml and exe.xml (rename/remove)2) move everything out of FSX\Modules folder3) delete fsx.cfg4) ProgramData\Microsoft\FSX\ backup scenery.cfg here and rename/remove5) Move to a backup folder any Aircraft you might have installed (I create a folder BACKUP inside the Simobjects/Airplanes, and just move it there You have to find the culprit causing it, and this is the way. If it starts up afterwards, you can start by adding stuff in, each time you do, just fire up FSX to see what happens.

Share this post


Link to post
Share on other sites

"I have run dxdiag and memory test, evrything is ok." Memtest is run from a floppy or USB key before Windows boots. Is this what you did?

Share this post


Link to post
Share on other sites

Hi, Many thanks for your answers. Malware has found no infections. I had already done the test with the rename of dll.xml and Fsx.cfg. and I have made thetest now of renaming scenery.cfg and removing everything out of the modules folder.But the result is always the same: INSUFFICIENT MEMORY! When i delete the fsx.cfg before startup, afterwards it contains only two parameter: [GRAPHICS] SHADER_CACHE_PRIMED_10=1693458432 [sOUND] AmbientUIMusicVolume=-6.000000So the startup goes not very far. I have run the standard windows memory test wich run's also before the boot.If the memory was faulty, the message would also be another one. I also don't think that the problem is due to a specific aircraft, because the messagecomes up so early , IMMEDIATLY after the STARTUP-initiation ! There must be a problem with some basic FSX-file! Guy

Share this post


Link to post
Share on other sites
Hi, Many thanks for your answers. Malware has found no infections. I had already done the test with the rename of dll.xml and Fsx.cfg. and I have made thetest now of renaming scenery.cfg and removing everything out of the modules folder.But the result is always the same: INSUFFICIENT MEMORY! When i delete the fsx.cfg before startup, afterwards it contains only two parameter: [GRAPHICS] SHADER_CACHE_PRIMED_10=1693458432 [sOUND] AmbientUIMusicVolume=-6.000000So the startup goes not very far. I have run the standard windows memory test wich run's also before the boot.If the memory was faulty, the message would also be another one. I also don't think that the problem is due to a specific aircraft, because the messagecomes up so early , IMMEDIATLY after the STARTUP-initiation ! There must be a problem with some basic FSX-file! Guy
Did you do the same with exe.xml??? That one also holds some files that preload with FSX. Why don't you reinstall FSX if everything else fails?

Share this post


Link to post
Share on other sites
Did you do the same with exe.xml??? That one also holds some files that preload with FSX. Why don't you reinstall FSX if everything else fails?
I have no exe.xml ! I think I will try a repair install. I have FSX-Sp2 installed.I have made some research about the repair install in the forum.They say one must first desinstall Sp2 and Sp1 and then do the repair and afterwards reinstall SP1 and Sp2.Seems logical to me. Is that right?It is also imortant to save before the repair the following files:fsx.cfg, dll.xml, scenery.cfg and all the modfied default files , aircraft.cfg etc.Are there other files to save? Guy

Share this post


Link to post
Share on other sites
Guest jahman
Wrong wrong wrong!!! FSX can use up to 4GB of VIRTUAL SPACE! Nothing to do with RAM. How often more?On 32bit, it's another story though. With userva, 3GB is correct. But still virtual space.
  1. Not quite 4 GBy as some address space needs to be reserved for the 32-bit Windows compatibility stub so 32-bit FSX can communicate with 64-bit Windows. (Anyone know the actual size of this stub?)
  2. /USERVA has been obsoleted since at least SP2/Acceleration.

Cheers, - jahman.

Share this post


Link to post
Share on other sites

1. I don't quite know what you mean here, but I know I can measure full 4GB usage under 64bit2. And why is that? USERVA basically tells 32bit OS to assign 3GB for an app and 1GB to system, not correct??

Share this post


Link to post
Share on other sites
Guest jahman

1. A 32-bit app can't directly address the data structures of a 64-bit OS, therefore the OS must replicate a 32.bit version of any data structure accessed by the 32-bit app and do so inside that 32-bit app's address space. Therefeore the 32-bit app can't use the entire 4 GBy or it would not be possible for that app to communicate with the OS. 2. Apologies, my wires got crossed! /USERVA is of course not obsolete, what's been obsoleted is the need to physically patch the fsx.exe to make it /USERVA-aware. Cheers, - jahman.

Share this post


Link to post
Share on other sites

I had this problem about a month ago. After searching the web and the forums I tried moving the most recent flightplans I had installed (about 2 weeks worth) to my Temp folder. FSX then started without the error. I added the traffic.bgls one by one until one caused the issue. I deleted that one and redownloaded it and haven't had the problem since. A bad .bgl file can cause this error. Check it out. Steve LewisAIG Dispatch

Share this post


Link to post
Share on other sites
1. A 32-bit app can't directly address the data structures of a 64-bit OS, therefore the OS must replicate a 32.bit version of any data structure accessed by the 32-bit app and do so inside that 32-bit app's address space. Therefeore the 32-bit app can't use the entire 4 GBy or it would not be possible for that app to communicate with the OS. 2. Apologies, my wires got crossed! /USERVA is of course not obsolete, what's been obsoleted is the need to physically patch the fsx.exe to make it /USERVA-aware. Cheers, - jahman.
1. OK if you know it's like that, but why does it then show usage up to 4GB and crashes if it wants more?

Share this post


Link to post
Share on other sites
Guest jahman
1. OK if you know it's like that, but why does it then show usage up to 4GB and crashes if it wants more?
Not sure about that. Perhaps since the 32-bit OS stub is one per 32-bit app, the stub address space is tagged as part of the app? Cheers, - jahman.

Share this post


Link to post
Share on other sites
Not sure about that. Perhaps since the 32-bit OS stub is one per 32-bit app, the stub address space is tagged as part of the app? Cheers, - jahman.
I never ever heard anything about this "stub" you are talking about, whatever that is. I googled it, but found no plausible definitions. And you are by this definition the first one here to say something like this.I can also take a comparison that under XP 32bit, I was able to use 2GB of RAM, with the tweak, 3GB, and then under 64bit the usage was same for the same config (I remember back then I used to do a lot of testing in that area), and then I pushed the envelope further to 4GB.But with FS9, same installation being used in XP and Win7, I confirmed that virtual space used was the same in both OS's.

Share this post


Link to post
Share on other sites
I never ever heard anything about this "stub" you are talking about, whatever that is. I googled it, but found no plausible definitions. And you are by this definition the first one here to say something like this.I can also take a comparison that under XP 32bit, I was able to use 2GB of RAM, with the tweak, 3GB, and then under 64bit the usage was same for the same config (I remember back then I used to do a lot of testing in that area), and then I pushed the envelope further to 4GB.But with FS9, same installation being used in XP and Win7, I confirmed that virtual space used was the same in both OS's.
Try here Word Not Allowed, went over my head. :) So not sure if this is what you mean. I would rather eat a kilo of baked beans sitting in a telephone box than read what is in that link. http://lafaix.online...s2/contest.html

Share this post


Link to post
Share on other sites

To come back to my original subject: I think I will try a repair install. I have FSX-Sp2 installed.I have made some research about the repair install in the forum.They say one must first desinstall Sp2 and Sp1 and then do the repair and afterwards reinstall SP1 and Sp2.Seems logical to me. Is that right? It is also important to save before the repair the following files:fsx.cfg, dll.xml, scenery.cfg and all the modfied default files , aircraft.cfg etc.Are there other files to save? Thanks Guy

Share this post


Link to post
Share on other sites
I had this problem about a month ago. After searching the web and the forums I tried moving the most recent flightplans I had installed (about 2 weeks worth) to my Temp folder. FSX then started without the error. I added the traffic.bgls one by one until one caused the issue. I deleted that one and redownloaded it and haven't had the problem since. A bad .bgl file can cause this error. Check it out. Steve LewisAIG Dispatch
That helped! About two weeks ago I had modified also, like you, a traffic Bgl file.I now recompiled that Bgl file again without those modifications.And ... FSX RESTARTS now ! and I can fly! I still get a message at startup saying "DLGALERT.bmp could not be laded" .That is the box with the progress bar.But this doesn't hinder the startup. I will try to sort that out also. Many thanks!!!! Guy

Share this post


Link to post
Share on other sites
Yupp - this message refers to the image of the box in which you see the progress bar while things load. It is to be found in the "Uires" folder. If it's gone, you can get it here:- http://www.mediafire.../?v0l48si9k8zw8
Thanks for your answer and the link. As I have Fs9 still on the Pc I replaced already the Dlgalert.bmp of Fsx by the one from Fs9.(The only difference is, the one from Fsx has a red border and the one from Fs9 has a grey border!) So this problem is also solved now and EVERYTHING seems OK again! Thanks again to all (and especially Steve Lewis) for your help! Guy

Share this post


Link to post
Share on other sites

×
×
  • Create New...