Yes I Knew it ! I was trying to show that the 2.4 + 1.6 its the correct balance to 4GB of memory that is suppose to be used for P3D. But in the image that I post first, clearly OOM's occurs with only 3GB of VAS usage. ):   

 

You should not be getting OOMs at 3GB - unless you are using 32Bit Windows.  But I don't think you are running 32 Bit Windows. 

 

Delete your prepar3d.cfg file only and let it rebuild and see if you get the same OOMs. 

 

If you did any tweaks to prepar3d.cfg - a typo could result in an error

You should not be getting OOMs at 3GB - unless you are using 32Bit Windows.  But I don't think you are running 32 Bit Windows. 

 

Delete your prepar3d.cfg file only and let it rebuild and see if you get the same OOMs. 

 

 

If you did any tweaks to prepar3d.cfg - a typo could result in an error

 

 

This is a fresh W10 64bits and Prepar3d V2.5 installation (:

 

It was the first test trying to force OOM's at 4GB but all that I can touch is 3GB. 

This is a fresh W10 64bits and Prepar3d V2.5 installation (:

 

It was the first test trying to force OOM's at 4GB but all that I can touch is 3GB. 

 

Get on the Prepar3d forums and post a message there - LM guys and gals need to look at this

Get on the Prepar3d forums and post a message there - LM guys and gals need to look at this

 

 

An update:

 

This OOM was happening because of an error in a SID of SBCF airport in my NGX.

 

It was stable using max 1.8GB VAS usage during SBCF takeoff then CTD occur. Switching to Process Explorer it's showing abruptly from 1.8gb to 3.0gb after crash.

 

I'm free of CTDs taking off without load a SID from that airport. Just including manually the waypoints.

 

Obviously that still limited to 3gb but at least I discover what was the problem that was bothering me.

 

Sorry guys, I'm describing it here maybe to be an history to anyone that has the same problem in the future.

 

I'll post it on LM forum also.

 

Skywolf thanks again