Hello can you please help me.I'm experiencing some weird textures loading when I switch views from external to Virtual Cockpit and ground textures flickering causing my FSX to CTD with OOM problem.I upgraded my Graphics card from GTX 660Ti  to  EVGA GeForce GTX 780 3GB SC w/ EVGA ACX Cooler.

 

I'm using DX9 and below are my Pc Specs:

 

Intel Core i7 3770K OC @ 4.5Ghz

Nvidia Geforce EVGA GTX 780 3GB

16GB Ram,

2TB HD  

1TB Ext HD

 

Kind Regards

 

Lloyd

Apologize for going a little off topic but just wanted to pass on a friendly reminder that we have changed our signature policy again and we are kindly asking everyone to please put their system specs and flight sim information in their respective "My Profile". More details can be found at the following link - http://forum.avsim.net/topic/436632-new-signature-rules or under the Forums tab above. Thanks for your cooperation.

An OOM indicates you are running out of virtual address space (VAS). Here's what it says about out of memory crashes in the AVSIM CTD Guide located to the right of this forum under Hot Spots:

Out-of-Memory (OOM) – Caused by running out of Virtual Address Space (VAS). Lower LOD_Radius (if above 4.5) and/or Texture_Max_Load (if above 1024). Check BufferPools setting in FSX.cfg and disable (fix for some). The following points apply in regards to VAS -

• FSX and P3D are 32-bit applications. A 64-bit operating systems is limited to 4GB of VAS no matter how much RAM (system memory) is installed. A 32-bit operating system is limited to 2GB of VAS with a “switch” to provide up to 3GB’s.

• OOM’s relate to VAS, not physical memory. Microsoft OOM error should have stated something like “FSX (or P3D) has run out of virtual address space” instead of the application has run out of memory.

• VAS is not the same thing as the virtual memory (page swap file) that you can adjust in your system settings. A large page file or virtual memory swap file does not protect anyone from the 4GB VAS limit.

• VAS is effectively a pre-allocation of everything FSX/P3D can potentially access during a flight. It will fluctuate over the course of a flight and over different areas.

• Microsoft.net Framework packages reserve a chunk of the VAS and then commit memory from that chunk. For this reason, it is important you have the proper version of .net installed.
 
To monitor the amount of VAS you are using during a flight:

Monitoring VAS in FSX – The freeware or registered versions of the FSUIPC utility will allow you to monitor the amount of VAS remaining during a flight session. This might be valuable in troubleshooting Out-of-Memory (OOM’s).

Startup FSX/P3D and then enter the Addon Menu and select FSUIPC. Once FSUIPC is open, click on the Logging Tab and enter 024C under Offset and select S32 under Type. Select where you would like to have the usage displayed. The FS Window is for Full Screen sessions. The FS Title Bar is for Windowed Mode. AVSIM recommends you also check the Normal log file as this provides you information on how much VAS you had to start out with and then it logs usage throughout your flight.

The VAS usage is displayed in Kilobytes (KB’s). The value represents the amount of VAS left so, the lower the value, the more VAS being depleted. The max amount of VAS allowed in computers with 64 bit Operating Systems is 4GB’s. This is shared with other applications running in the background on your computer. For 32 bit Operating Systems, the max amount of VAS allowed for FSX/P3D is 2GB’s but this can be expanded to 3GB’s with a switch like the /3GB switch.
To convert the KB’s to the amount of GB’s, you should use one of the Byte converters on the Internet like the following: http://www.whatsabyte.com/P1/byteconverter.htm. You will never see 4194304 KB’s displayed as this equals 4GB’s. You might see around 3GB’s (3145728) remaining when you first start up FSX/P3D but that would be unusual. Do not be too concerned with the amount of VAS remaining when you first start up.

 

Hope this helps.

 

Best regards,

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

• The most likely reason is that the post was off topic.
• The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
• The images might not have been "illustrative" or "explanatory" in nature.
• The topic could have been moved because we deemed it to be more appropriately placed elsewhere.

Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Hi Jim thanks for the response and a gently reminder about the signature I wasn't aware,I'll do likewise sort it out.

 

I followed your step by step instructions from your post using FSUIPC to check the amount of VAS left before and after running FSX.

Below are my results:

 

Before = 1668500 converted  1.59121GB  Approx 1.6GB

 

After =    1194200 converted 1.13888GB   Approx 1.1GB

 

I presume with above figures its pretty bad I have more VAS being depleted.

 

I'll try and change settings in my Fsx.cfg. Currently I have LOD_RADIUS =6.50000

AND Texture_Max_Load=4096.

The other thing I noticed is a StackHash_27eb error message thats seems to appear when I exit Fsx.

 

Can you please assist me or point me to a link in the Avsim forums on how best I can config my Fsx settings and Fsx.cfg. Thank you.

 

Kind Regards

 

Lloyd

Thanks for your cooperation regarding the signature policy.

 

I'm a bit confused as you stated you were getting OOM's. From your latest post, you are no longer getting OOM's? I use no tweaks in my fsx.cfg (basically follow the guidance of NickN and, of course, the AVSIM FSX Configuration Guide located to the right of this forum under Hot Spots). The only two tweaks I use is the LOD_Radius (set at 6.5) and the Texture_Max_Load (set at 2048 - I found 4096 just did not work for me and I saw little or no difference in texture quality).

 

StackHash crashes can be caused by high settings or a bad tweak in your fsx.cfg (Bufferpool tweak is the biggest offender). It can also be caused by a bad setting in your BIOS, especially a voltage set too high or too low. As you will see in the AVSIM CTD Guide, the StackHash crash can occur if you have MyTrafficX, version 5.4c installed. A StackHash will occur 100% of the time if you have two monitors like I have and you start up or shutdown FSX in full screen mode. I always go to Windowed Mode before I shutdown FSX. That kind of crash will occur when you shutdown FSX 100% of the time.

 

Can you please assist me or point me to a link in the Avsim forums on how best I can config my Fsx settings and Fsx.cfg. Thank you.

My recommendation is to use the AVSIM FSX Configuration guide for setting up your FSX.cfg and NVidia Inspector settings. It's what I use. The guide was developed using guidance from Orbx/FTX manuals and other professional guidance found on the Internet. I don't think there is one perfect config or one config that will fit everyone but the AVSIM FSX Configuration Guide provides the guidance and you can go from there. Just remember, you are going to always see a certain amount of blurriness or flickering or stuttering occasionally depending on what's loaded into FSX. I know of nothing that will completely eliminate those issues but you can reduce them considerably using the guide.

 

Best regards,

Hi Jim sorry for the late reply I have been away.Sorry my bad to get you confused from my previous post. Indeed my initial problem was OOM and I'm still getting them. I only forgot to mention that prior to OOM issues I was also experiencing StackHash_27eb error when I exit Fsx.

I have changed my settings in the Fsx.cfg

-LOD_Radius  6.5 and

-Texture_Max_Load 2048

-Removed Buffer pools set them =0

 

With the above settings changed I haven't seen any OOM issue today  but the StackHash_27eb is still there when I exit FSX 

 

I have My Traffic x 5.4c installed at the moment of which I might consider downgrading to MTX 5.4b as you suggested previously.

 

FSX Shutdown procedure, that's something new I have learnt from you thank you very much.I need to keep an eye on because sometimes I fly in full screen mode as well as launching and exiting FSX..

 

I'll try go through Nicks Bible tweak guide but its quite long though. i think to get the best out of it is to go through everything anyway.

 

Kind Regards

 

Lloyd

I lowered my LOD  settings to 4.5. No more OOM

-Removed Buffer pools set them =0

Glad you have resolved the OOM issues. You should be able to run FSX at 6.5 LOD Radius though. You should completely remove the Bufferpool entry or at least comment it out so it will not load in the future. If you are not familiar with commenting out a parameter in the fsx.cfg, it only involves placing two slashes (//) in front of the parameter as follows:

 

//[bufferpools]

//UsePools=0 (BTW, I have found that using UsePools parameter causes more CTD's for many for some reason. Maybe it was the way you configured the rest of your computer).

 

Best regards,