btw. LSZH Zurich seems to be having a libraryalert all the time cant get rit of it (FSDREAMTEAM V2) Reinstall ? /Michael

no, I do not think a reinstall solved the library alert.An uninstall will solve it that is the disadvantage... you get the messages now...solution (for LOWI region) is the patch from Aerosoft for LOWI, then you can disable the libraryAlert!

hmm where is that patch ? i have bought mine on simmarket and login to aerosoft does not give me updates in innsbruck. If you is refering to the 1.10 patch where you are self to put the textures in the texture folder then i did that but still getting CTD at OEV16 (simmarket provided the update) /Michael BTW A new fsx.cfg and a uninstall of UT2 did not work --- still need the alert

the current Aerosoft Version is 1.20.And you insert no textures, but BGLs... Sorry, I don't know if or how SimMarket provides this files. maybe you have to contact them ...

So what do you do if this crashes the sim on the free flight menu?

I don't think it's ORBX scenery causing this crash. The g3d.dll crash has been around since at least FS2K4 and back in those days it was usually fixed by completely uninstalling the video card drivers, using a registry cleaner to get rid of anything leftover, then reinstalling the drivers. I got the crash recently using the default scenery and on my current high tech rig. It happened when I was flying into a complex airport (KSFO), at night, in heavy weather in the PMDG 747. The memory settings I had in the BIOS were set at "Auto" and I changed them to the correct settings for my memory and I have not seen this CTD since. I have also gotten the terrain.dll CTD and the NTDLL.dll CTD and those were caused by bad overclocking and having my FSX settings set too high. I have seen that thread over at Orbx/FTX and the people are blaming the wrong guys. IMHO it's the user and system settings that are causing the crash(es). That's why the people over at Orbx will never find a solution for their software. Best regards,Jim

Hi Jim, The guys who experienced CTD's were at exactly the same locations, using Aerosoft or Orbx scenery. These CTD's are unlikely to be from poor system settings. A bad overclock or poor settings or bad drivers, would produce a more random CTD. These are in the same locations every time. This points to the .bgl and the scenery add ons. The CTD you experienced at KSFO, you traced to your "system". Did you just have the one CTD at KSFO or were there several, which led you to re-examine your system settings? D3d's are FSX bgl problems. Ntdll.dll and terrain.dll can be an either or cause. Either RAM fragmentation/discontiguous or, low level errors from drivers/poor overclock/RAM timings. It has been said that FSX is now almost maxed out, insofar as add ons are concerned. When the core code was written, I do not think the developers saw that we would be flying completely accurate 737's, with all aircraft systems running as subroutines, over terrain mesh modelled to 1 metre accuracy, with photo realistic airports modelled to 20 cms ( Not to mention people walking around the aprons!) All within a 4 GB VAS!! I think we may have exceeded the ability to run such items with FSX! I echo what another post said, that instead of trying to write a new sim (Flight) they should have looked at FSX stability and made it multi core with a 6/12 GB Virtual Address Space. But then they sacked the ACES team didn't they Best Regards,

Well stated David. I have also received the CTD's at the exact locations. I wrote a long article about this over at the FTX/PNW forums as the crash always occurred directly in line with the Seattle Space Tower or downtown Seattle with PNW scenery enabled. And it happened 100% of the time. I also had 100% crashes when flying from Boise, ID to Seattle and the CTD would occur exactly after flying over the mountains and Seattle comes into view coming in from Portland, OR. But, these crashes were only with the PMDG 747 with the FMC programmed. If the FMC was not programmed and flying manually, the CTD did not occur. And, it never happened with any of the other PMDG aircraft, the default aircraft, or 3d Party aircraft like iFly's or LevelD, whether the FMC was programmed or not. So I personally think there are various reasons for the crashes that always occur exactly at the same spot or in the same general area. On all my crashes, the Event Viewer stated the Error Code was a memory exception (0xc00000005 or something like that) and then it states the related .dll (g3d, ntdll, etc). Via a Google search, memory exceptions are very difficult to solve. I no longer fly the PMDG 747 into Seattle. It's sort of frustrating to have a crash that's not your fault after a lengthy flight. Best regards,Jim

Hi Jim, Interesting issues! Its pointing to the PMDG 747 in your case approaching/over Seattle? All I know about that area is that, even in default scenery, thats the region that loads big scenery files into FSX. (Must be the Seahawks wages bill?) However, if you can fly everything else there, well, the suspect is the 747 model. I think that many of these extremely complex aircraft add ons, are not tested over add on scenery. The memory use is different from the default scenery. Even VOR/NDB/ILS/WP's can be different in add on scenery. If these present a conflict with the aircrafts Navdata/FMS, there may be issues. As an example, Madeira Scenery has the (LPMA) runway correctly modelled without ILS. FSX default has ILS. As we add "things" to our FSX, we make our installs dissimilar to what the aircraft designer thinks we have. Everyone will have a dissimilar FSX install, unless they do not add on addons Then there are the many different hardware types and the way folks have installed the sim? Out of Memory issues can also crop up if the add on, be it scenery, or aircraft, has a memory "leak". Without going into that nightmare scenario, the leaking "module" will eventually cause memory fragmentation and the infamous "contiguous" memory issue. This has been mentioned by Peter Taylor (ACES) and was an issue years ago. No one is sure how much contiguous VAS FSX needs to run. 1GB has been mentioned? So there we are, trying to solve our fragile FSX, which has no equal, as yet. Happy Simming,Best RegardsDavid.

Agree but FTX thinks it's missing scenery objects and they think they have fixed the problem by updating the FTXORBX object library. I haven't tried that theory yet but hope to over the weekend as I now have the latest library installed. I agree with your theory about a memory leak even though I have a 64 bit system (so what?). But 64 bit systems are capable of managing memory much better than 32 bit systems which were prevalent when Phil Taylor from ACES was running things a few years ago and from which FSX was developed. It could still be some sort of a memory leak. Like I said, the crash occurs 100% of the time when the FMC in the PMDG 747X is programmed and I'm on the glideslope for landing on 16L at KSEA. If the FMC is not programmed and I'm flying on the same glideslope manually, the CTD will not occur 100% of the time. I use Navigraph data and that is updated frequently. I doubt there is a problem with the flight data BUT there is a massive amount of computing going on in the FMC as an aircraft is in its landing and approach phase and in nasty weather in known heavy duty scenery like that in the Seattle area. I think the system could have an issue. If it was a missing scenery object, then logically, it should happen 100% of the time with any aircraft. It doesn't for me. Just the 747X with the FMC programmed. Unfortunately for me, no one else who owns the 747X, with the FMC programmed for landing, has had the CTD right at the area equal to the Space Needle on the KSEA flight path. Just me. Since I wrote my thesis above, I have read over at the FTX forums that others have had crashes in other aircraft, even default, exactly at the very same spot where my poor little 747X crashes. So it is confusing. I like mysteries... Best regards,Jim

Has anyone tried to reinstall the FSUIPC? I had this problem before and I think (unfortunatelly I'm not sure) that installing the latest version might help.

 

I also found this site:

http://#####.wordpress.com/fsx-software-and-hardware-guide/

saying:

 

"Pete Dawson, a maker of FSUIPC utility for FSX, has implemented a g3d.dll crash fix into his product. The fix that is implemented covers one of the crashes only – it is NOT all miracle g3d.dll crash fix. You should install (and actually buy) the latest module from his website."

 

I will try to do it again at home, but I can not reproduce the problem, it's still random for me. Haven't found one region where it crashes all the time.

The FSUIPC fix for the g3d.dll crash does not fix all g3d.dll crashes.  If you go into the Modules folder in FSX, you can open up the fsuipc.log and it will provide you information on whether the g3d.dll trap has been installed or not.  If you open it up after a flight it will show you how many crashes it prevented.

 

Best regards,

Jim