Archived

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

stevenp

md-11 oom errors

Recommended Posts

I love the new a/c but I have a problem that stops me from flying long distances. I get ooms with this a/c but none others including the 744x. I have vista 64 with 4gb of memory, any help?

Share this post


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

Hi,Hmm.... Not sure on that one. I've precisely zero issues like this in nearly 24 hours of flying and generally messing around. No CTDs, OOMEs or anything.I run Vista 64-bit too, with 4Gb RAM.Is your swap file enabled? What are you running in the background? What do you have loaded in the sim? What are your system specs (please answer all questions as fully as possible!). I'm intrigued.Best regards,Robin.

Share this post


Link to post
Share on other sites

Snag Process Explorer here: http://technet.microsoft.com/en-us/sysinte...s/bb896653.aspxSet up the column like the screen shot. Virtual Size is the OOM stuff. WS Private is your physical memory load. I was able to OOM Vista 64, but it really needed some DeliBerAte effort. Run this along with FS flight and monitor VS. It's gotta hit +4G to get an OOM in Vista 64. I really expect something else is going on. http://forums.avsim.net/user_files/193369.jpg

Share this post


Link to post
Share on other sites

Hmm, I didn't check the actual memory usage, but after a three hour flight yesterday FSX refused to take screenshots in the approach, VC textures became blurry (ground textures followed suit).... That seemed to me like a memory problem. Well, terrain blurries aren't terribly exciting, but in the VC? The VC remained unusable, even after landing.Thats on 32bit Vista and 2 Gigs of RamCheers,Niklas

Share this post


Link to post
Share on other sites

Hi Niklas:To be honest, sounds like a video memory thing. The trouble is, even with two people operating the same system, ther are so many variables that it would be almost impossible to point an exact cause.CheersPaul

Share this post


Link to post
Share on other sites

>Hi,>>Hmm.... Not sure on that one. I've precisely zero issues like>this in nearly 24 hours of flying and generally messing>around. No CTDs, OOMEs or anything.>>I run Vista 64-bit too, with 4Gb RAM.>>Is your swap file enabled? What are you running in the>background? What do you have loaded in the sim? What are your>system specs (please answer all questions as fully as>possible!). I'm intrigued.>>Best regards,>Robin.I actually had nothing running except the sim this time, I usually fun active sky. Not I never put in any sway. Yesterday I turned off everything i.e. internet antivirus, and explorer. My system specs are q6600, 4gb gskill, 780i, 2 8800gts g92, raptor x. Everything is oc (it wont make a difference everything is stressed and works fine)- except memory- the pc crashed with the mem oc before.

Share this post


Link to post
Share on other sites

I think im goin to do a full reinstall of fsx, cause some things are starting to get screwed up.

Share this post


Link to post
Share on other sites

I think its to busy failure... Thats a problem of your operating system. There are many solutions...SP1 is on of it.Another way are this little program: http://ntcore.com/Files/4gb_patch.zip make sure that you have a backup of your fsx.exe. Start program, choose fsx.exe, patch it... Thats it.Vista have many problems with 4GB RAM. Google is one station to get a solution about it.Note:4GB problem is everytime a strange problem in following operation systems: WinXP, Vista32 and Vista64.WinXP users must make an entry in boot.ini/3GB /userva=2700Put this in your last line of boot.ini. Its recommend to space up some virtual memory.Belive me thats all. This fault is not a PMDG prob. This prob do you have general with all programs.@PMDG TEAM:U will get more of those user action. Put my solution in your FAQ's. Other develop do the same.

Share this post


Link to post
Share on other sites

>I think its to busy failure... Thats a problem of your>operating system. There are many solutions...>>SP1 is on of it.>>Another way are this little program:>http://ntcore.com/Files/4gb_patch.zip make sure that you have>a backup of your fsx.exe. Start program, choose fsx.exe, patch>it... Thats it.>>Vista have many problems with 4GB RAM. Google is one station>to get a solution about it.>>Note:>>4GB problem is everytime a strange problem in following>operation systems: WinXP, Vista32 and Vista64.>>WinXP users must make an entry in boot.ini>>/3GB /userva=2700>>Put this in your last line of boot.ini. Its recommend to space>up some virtual memory.>>Belive me thats all. This fault is not a PMDG prob. This prob>do you have general with all programs.>>@PMDG TEAM:>>U will get more of those user action. Put my solution in your>FAQ's. Other develop do the same.So you think this will help me. I probably will still do a full reinstall of fsx- i hate it cause it takes like 3 hours with all the stuff I have with it.

Share this post


Link to post
Share on other sites

HI,How can i check if my swap file is enabled or not? and if not how would i enable it?Im using vitsa 32 home premium.Many Thanks,NicholasBB

Share this post


Link to post
Share on other sites

A reinstall of system wont work. You get this problem in the next future.Install 32/64bit system microsoft OOM patch. I can put here so many site with your problem! Just use my hints and after this you can post here if you have this fault or not. Dont ask just do it. ;)Try to patch your fsx.exe as i posted.Google:http://www.google.com/search?hl=us&q=vista...gle-Suche&meta=Enable Vista Swapfile:http://www.tech-faq.com/swap-file-settings.shtml

Share this post


Link to post
Share on other sites

If you are running Vista 64 and FSX the system is already fully 4G capable. These is not need to set switches with Vista 64. OOMs with this setup are virtually impossible. (sans a science experiment like I ran). Run Process explorer to check this out for yourself. It's a good education, anyway. Vista 64 has no problems with 4G.

Share this post


Link to post
Share on other sites

Paul: I agree, I personally suspect the rather crappy video memory management of the Nvidia 8 series... It tends not to clean up after itself - a proper memory leak in the VRAM. You just don't notice it too ofter with 700+ Megs...CheerioNiklas

Share this post


Link to post
Share on other sites

I've had one OOM error so far - and I see now that it was as I approached Aerosoft's H'row, over Horizon's VFR London demo, in a MD-11 that I'd re-loaded 3 times despite the advice that I've now spotted in the intro that we ought not to try to reload the same plane...Funnily enough, it's not happened since :)

Share this post


Link to post
Share on other sites

If you are running Vista 64 and FSX the system is already fully 4G capable.Sure this is a point. This do the patch! You dont know if this guy put more ram into his system after full installation. SP1 is required for that.For Vista32:windowsbutton + r put this in bcdedit /set IncreaseUserVA 3072 Vista64:SP1Try to patch the fsx.exe with 4gb_patch.zip

Share this post


Link to post
Share on other sites

Hey, I noticed all that posted are Vista users. Does anyone use Wix XP Pro and if so...any ideas on how to solve this? I was running ASX at the time, whilst on the ground. Oh, yeah...at KJFK (addon. Nothing else.Had no OOM probs otherwise.system is roughly AMD 64x2 3800+ w/NVid.GeForce 9600GTsoundblaster cardThx for help if possible.Chad D.

Share this post


Link to post
Share on other sites

Relative to these OOM issues, Vista 32 and XP 32 are both simply 32bit operating systems. Both will need the same mod to allow the memory system's talley sheet to schedule 3G of ram. Again, this has nothing to do with physical ram. OOMs occur only on the basis of ram scheduling that is happening inside the op system's "kernal."

Share this post


Link to post
Share on other sites

No. It will only help 32Bit systems. However make sure you have FSX's SP2 installed. That sets the program's 3G switch. FS9 is going to be fun. The operating system "switching" will still be required for 32bit systems, but there is no automatic way to set the program's 3G switch within the FS9.exe file. It can be done by dedicated computer scientists, but yikes . . . that's gonna be a mess.When we get it, I'll be beating it hard. I'll let us know.

Share this post


Link to post
Share on other sites

>No. It will only help 32Bit systems. However make sure you>have FSX's SP2 installed. That sets the program's 3G switch. >>FS9 is going to be fun. The operating system "switching" will>still be required for 32bit systems, but there is no automatic>way to set the program's 3G switch within the FS9.exe file. It>can be done by dedicated computer scientists, but yikes . . .>that's gonna be a mess.>>When we get it, I'll be beating it hard. I'll let us know.The program itself (FS9) doesn't have a "3G" switch. When the /3GB flag in boot.ini is set in a 32-bit Windows OS, it permits the OS to allocate up to 3GB of memory address space to any program running under it, and as a potentially troublesome side-effect, it crams the OS in the remaining 1GB of address space. Assuming /3GB is set in the OS, the LARGEADDRESSAWARE flag must be set in a program's PE header for that program to make use of the expanded virtual address space. Setting the flag allows a 32-bit program to see addresses in the complete 4GB 32-bit virtual address space. Normally, the top address bit is disabled, meaning that an application considers its environment to only include the first 2GB of the 4GB virtual 32-bit address space (Windows is assumed to "own" the upper 2GB of the address space).It's actually fairly straightforward to set the LARGEADDRESSAWARE flag in fs9.exe or any other 32-bit program using editbin (in Win XP or Vista, and 32 or 64-bit in either). No CS degree required.I've just built a Vista 64 environment on my computer, and am about to try running FS9 on Vista 64 to see if setting the LARGEADDRESSAWARE flag on the program when running on a 64-bit OS provides relief for the out of memory problem that plagues FS9 on a 32-bit OS.RegardsBob ScottColonel, USAF (ret)ATP IMEL Gulfstream II-III-IV-VColorado Springs, CO

Share this post


Link to post
Share on other sites

Especially for FS9, folks need to be aware there are TWO (2) switches that need to be set. 1) One is in the FSX(9) program's .exe file. 2) The other is in the op system's boot.ini file. Therefore, individual programs Do need this switch set via a modification to their .exe files. Semantic discussions are great fun, just as long as we understand what's actually going on. For FSX, the FSX.exe switch-mod is set automatically with the SP2 update. For FS9, it will need to be set manually.Fixing an IRU drift problem is pretty straight forward to me, but it might not be to others. So too, might setting the program's .exe switch in FS9's .exe file. When the time comes, we're really gonna appreciate your help with this. Thanks in advance. All this clumsiness is a function of this transition from 32 to 64 bit operating systems. It's no one's fault, other than the need to keep increasing software capabilities. FS/PMDG users are at the leading edge this transition because of the inefficiencies of FSX and the complexities of the PMDG product. It's the price we pay. Ain't it great being a pioneer? (Not!)

Share this post


Link to post
Share on other sites