Jim,

 

I just did a 3rd test.  First,  I rebooted my computer and attempted again with the Default KSFO airport and PMDG 747-8 with FSPassengers.  Like the first test, there was no fatal error because I just started after turning on my computer.  The second test I did not reboot and the fatal error occured.  This 3rd test I rebooted my computer before the test flight and was a night flight plus the frame rates were good also on this occasion.  I quit about after 15 minutes of flying.  So this may narrow down the fatal error problem.  I think it is an OOM issue, but as I mentioned in my last posting today,  I am unable to see it in FUSIPC.  I am not familiar with OOM issues and what the fix may be.  I remember before when I looked at posts regarding OOM problems and it is quite complicated and I was unable to understand what people were even discussing.  It was advanced stuff regarding flight simulation, well, at least for me it is.

 

Sincerely,

Cray

First, I rebooted my computer and attempted again with the Default KSFO airport and PMDG 747-8 with FSPassengers. Like the first test, there was no fatal error because I just started after turning on my computer. The second test I did not reboot and the fatal error occured. This 3rd test I rebooted my computer before the test flight and was a night flight plus the frame rates were good also on this occasion. I quit about after 15 minutes of flying.

You shouldn't have to reboot your computer to run FSX. I seem to remember reading somewhere here on AVSIM that you used a backup program and transferred FSX from your old system to your current system. I really do not know how that can be accomplished without running into major problems. If it transferred the old registry to the current system, then that could be causing your problems. Most security programs look at hardware running on your system, like a hard drive or your CPU to make sure you are the person who bought their product. Same goes with FSX and Microsoft. I'm from the old school where I install Windows on my new system, then FSX, Acceleration and all my addons. I do backup my personal files like pictures and my e-mail program files. So, I'm really not familiar with what you did to get your fsx programs and addons to the new system.

 

This is not an OOM issue that you are having. That would occur long after you have loaded FSX and your addons as you get 4GB's of virtual address space but your system is only going to give you around 3GB's for FSX. I would suggest running AppCrashView so I can see the faulting module when fsx shuts down.

 

Best regards,

JIm,

 

When I transferred my files over to my new computer with a program I purchased called "Zinstall",  FSX did transfer over but I needed to register again with my purchase key code, along with other many of my other add ons.  My new computer came with Windows 7, like my old computer.  The only one that did not require a key was my PMDG 747,  it did the pruchase key  with PMDG 737.  I will do another AppCrashView when the fatal errror occurs.  But I know it did not help before if you check my older posts from this summer and it did not say much for what is causing it, for it is the exact same issue that I have been unable to solve.

 

Sincerely,

Cray

Hi Cray,

 

Thanks for the explanation. I guess I should have gone to the Zinstall website sooner. Looks like it does a decent job. I still prescribe to reformatting and reinstallation on a brand new system but that's my problem.

 

So, if you are still getting the API.dll error, that is OOM/VAS related in most cases. So, something is eating up your VAS as you load FSX. I had this happen to me a year or so ago and it was strictly related to my installation of MegaSceneryEarth (MSE) V2 of 42 US States. At the time I did not realize photoscenery ate VAS and I would get a black screen just loading FSX. Even at the setup screen it took about 20 minutes for the aircraft I had selected to appear in the preview screen. Then another 20 minutes to load. Once loaded, the FSX was sluggish and I would eventually get a CTD. I heard a lot of HD disk thrashing while doing all of this and went into the Process Monitor to see what was still running. It was just FSX but it was using a lot of resources. When I disabled every photoscenery, the problems went away. I'm telling you this as you might be experiencing the same thing?

 

If it is still the API.dll as the faulting module, you should monitor your VAS as follows:

 

Monitoring VAS in FSX or P3DV2 – 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.

 

You should also look at the processes running while FSX is running. To do this you would do a Ctrl-Alt-Del, Click on Start Task Manager, and then click on the Processes tab. Check to see if you have one or more instances of Internet Explorer running. This program sometimes does not shutdown properly and, when it is running in the background, it takes a huge amount of resources.

 

So not sure what else I can do to help you. You should get rid of any tweaks in your FSX.cfg as one or more of them could be causing this issue (tweaks have been known to cause crashes). This can only be done by moving your fsx.cfg to a temporary directory, restarting FSX and letting the config rebuild. You should remove the uiautomationcore.dll from your main FSX folder to a temporary folder. You should disable all of your addon scenery in the Scenery Library, and you should move your dll.xml and exe.xml (if installed) to another temporary folder (these files are located in the same folder as your FSX.cfg). Now, FSPassengers and any addon is not going to work properly and that's okay. You just need to see if FSX runs and has no problems. If not, move the dll.xml and exe.xml back to the fsx.cfg folder and run FSX. If fsx is running properly, with no crashes, then enable all of your addon scenery and run FSX again. Something major should happen during one of processes. Another crash should happen. If no crashes, then you probably had a problem in your FSX.cfg.

 

Hang in there!

 

Best regards,

Jim,

 

Thanks for all the help you are giving me with this problem.  Fortunately I have no "Tweeks" set in FSX and never used them, especially after reading various AVSIM posts in the past that they could only make things worse.  I do have have low settings for traffic, scenery, etc for some time now.  I also have my add on airports disabled in FSX, with the exception of 4.   The information you gave me on tracking OOM in FSUIPC will help to see when it gets used fast.   One question though,  I do have FSX Booster installed I purchased about 3 years ago.  Is that a "tweek" and should uninstall it?  I really don't know if it even improves anything.

 

As for FSX Real World Weather,  there is no change and it is frozen in time, despite "Sharing".  But like I said before,  I do have FS Global Weather now and I will try it out..  My only concern if it will have an impact on my OOM's, or frame rates by adding more resource troubles in FSX. 

 

Sincerely,
Cray

One question though, I do have FSX Booster installed I purchased about 3 years ago. Is that a "tweek" and should uninstall it? I really don't know if it even improves anything.

Hi Cray,

 

Yes, it tweaks the heck out of FSX during flight - http://forum.avsim.net/page/index.html/_/reviews/fsx-booster-2013-version-14-r1702. I believe FSX_Fiber_Accelerator does the same thing as this product (both were developed by the same developer) but probably a bit better. Many like their new product, FSX_Fiber_Accelerator but I had issues with it as I use photoscenery only and it did nothing for me. Programs like this and individual tweaking have been known to cause FSX crashes and major issues. This is why many experts, including me, suggest you rename or move your fsx.cfg, restart fsx and let the config rebuild whenever you are encountering problems. It will get rid of any bad tweak. You can easily employ or install this program after you have your fsx back to normal, stable and with no problems.

 

It is my understanding that if you install FSX in a folder like C:\FSX instead of the default Program Files (x86) folder, you will get rid of security problems that many encounter. Supposedly, those files will be shared with everyone without you having to do what I suggested above (right clicking on the fsx folder, hitting properties, and looking at the share tab). Okay, I have my FSX installed in the default folder and have never had problems but my folders were not shared so I went in and made sure they were shared. You could have a problem too with your firewall. An anti-virus program could be preventing access to the firewall or blocking your system with communicating with the Internet as your anti-virus program fears some evil person is trying to break into your system. I personally do not use an anti-virus program, never have, never will but I understand why many use them. I just make sure my firewall is turned on at all times. I cannot provide you advice on your anti-virus program and what it restricts or give you advice on your firewall. Normally, you install Windows and it is automatically set up for you and, when you install a program like FSX, that program will make sure it has access to the firewall or not. But anti-virus programs come in and change those settings to protect you from evil people and that may be why you cannot get an update. So, if you have an anti-virus program, take a look at that, especially in any areas where it might be discussing your Internet firewall.

 

Best regards,

Jim,

 

I was able to do a flight today for the first time in months with my Level-D 767 from KMSP to KLAX.  Everything went fine with no fatal error or frame rate issues.  I used FSPassengers, Ultimate Traffic II and GSX ground services as well and the frame rates were excellent at both airports.  KLAX is an add on airport.  Both of these airports frame rates on my old computer were absolutely terrible, including the KMSP FSX default airport,  but work fine now on my new computer.  Even though FSX Real Weather is still frozen in time on my system,  I used GS Global Real Weather and it worked out just fine and is easy to use.   I hope later I can have the same success with my PMDG 747 on a long flight.  It is not often I can do long flights more than 5 hours because of my busy schedule.   I also replaced my controller, or joystick.  My old one did not work with my Level D 767 auto pilot since last winter and my PDMG 777 (which I am still learning to fly).  For some reason the auto pilot would not hold with the old controller.  In flight,  I had to unplug and replug it for the auto pilot to hold, and sometimes that did not work.   I remember you, or someone in a forum post informing me it could be the controller needs to be replaced and replacing it did the trick!

Sincerely,

Cray

I remember you, or someone in a forum post informing me it could be the controller needs to be replaced and replacing it did the trick!

Glad to hear things are working better Cray. Hope you can continue to enjoy. I probably recommended moving the USB connection to another USB port.

 

Best regards,

Jim,

 

I had made several flights over the past few weeks.  Most flights have been successful. Mostly domestics like KLAX to KATL, etc.   I did fly from EGLL to KSEA with the Level-D 767 with a fatal error occurring over Northern Canada for some reason. I repeated the same flight and managed without any fatal error until I got to the gate at KSEA and changed a view when it occurred    I tried the PMDG 777 for the first time today from KATL (add on)  to LIRF (FSX default).  It went fine until I was taxing after arrival, trying to find a parking spot when the fatal error took place.  A lot of FSX default airports don't have much space for heavies and are taken by other aircraft, even when I have FSX airline traffic set around 35%.   Even though the fatal errors crop up now and then,  at least it was when I had already landed and at the gate.   When I watch the VAS,  it appears to happen when it is around 110,000 at the top of the screen.  Also, it happens in all instances when I change views.   I think LIRF would have been successful if it were not being able to find a parking spot.  I was changing views a great deal.  So I will need to limit switching views when I land on long hauls.   It is pretty nerve wracking during final approach on some long flights and it suddenly freezes for a few seconds, not knowing if it will unfreeze or a fatal error crops up.  Fortunately so far it unfreezes, as long as I don't try and change views when the freeze happens. 

 

Sincerely,
Cray

it appears to happen when it is around 110,000 at the top of the screen.

Hi Cray,

 

This means you only have a little more than 107MB's of VAS left which is not sufficient to run FSX. In fact I'm surprised it got that low. Usually you'll see a crash around 500MB's remaining. Changing views dramatically takes up resources even though you might see your fps counter high. Have you tried FSPS Fiber Accelerator - http://www.thefsps.com/fsx/54-fsps-fsx-fiber-accelerator.html? Think there are 5 60-minute demos to see if it will work for you. It changes FSX.cfg settings on the fly and even adds tweaks so that you get the best during your flight session. When the flight is over, it returns to your normal fsx.cfg. I own it but don't use it as I have exclusive photoscenery and I could not get it to work properly for that.

 

Best regards,

Jim,

 

Yes,  I do have FSPS Fiber Accelerator, but have not used it yet on my new computer.  I tried it at first on my old computer when FSPS Fiber Accelerator first came out but it was causing fatal errors, like everything else seemed to cause fatal errors on my old system.  I will try it again on my new computer and see how it goes.  With the PMDG 777 flight from KATL to LIRF yesterday,  I monitored the VAS at the top of  the screen and it would jump around  from 132,000 range to 123,000, if a changed a view in flight for the entire flight.  It got lower when I approached LIRF from around 117,000 to 110,000.  From what I understand too,  that PMDG 777 takes up a lot of resources.

 

Cray

The PMDG 777 takes up about 700-800 MB's according to their publication of VAS usage - http://support.precisionmanuals.com/kb/a108/vas-management-stopping-out-of-memory-oom-errors.aspx. The biggest eater of VAS is Autogen. If you want to crash real fast, crank up the Autogen. This is one reason why I went to photoscenery as I can turn Autogen off.

 

Best regards,

Jim,

About two weeks ago I did a flight with the PMDG 777 from KATL to KLAX.  Both are add on airports as well.   I made it successfully and kept an eye on the VAS.  While taxiing to the gate at KLAX,  the VAS was as low as 15,000.  I thought the fatal error would pop up at any second.   I did not change screen views during that time frame and I think that prevented any fatal errors.  Usually if I change a screen view, it will freeze and then the fatal error.

 

Cray

Hi Cray,

 

I just installed the latest SP1c update to the 777 and I think the VAS management has vastly improved. The aircraft feels very smooth and my fps have jumped considerably. I still keep my flights down to around 1 hour and 30 minutes or less but think I could fly longer. My VAS gets down to around 500 MB's and I'm still okay. The other day though I installed REX-4 Texture Direct to replace my default clouds. I thought I had a super computer system so increased the low-level and high/mid-level clouds from 512 to 2048. Then I changed the texture compressions from DX5 to 32 bit. It almost brought my system to its knees while running both FSX and then later on P3D. I guess it did not like my LOD_Radius of 6.5 and Texture_Max_Load settings in the fsx.cfg as fps went down considerably and I was in total fear of having a CTD at any moment. Returned the settings in REX back to the default and the REX clouds still look better than the default and my sims work great.

 

Changing screens/views will definitely take its toll on fsx. I suspect it is because it is rendering more as views are being constantly changed. Not much you can do but moderate the views. I go from VC to Wing View instantly using the Ctrl+S key (instead of cycling through the various views to get to it).

 

Best regards,