Because of my only C.T.D. when attempting to fly anywhere around the Seattle area (even at 23,000 ft) the screen freezes, and computer shows busy, and then the C.T.D. The two offenders at different CTD events are the d3d.dll and the terrain.dll.Because I have ORBX PNW, Fjords, and Northern Rockies, I decided to reload all once more with also the PNW Service pack 1.03 to correct the double buildings in Seattle. I then applied the latest ORBX lib as they say to do after all the others. I rebooted, and then ran FSX again, with a flight path towards KSEA as a fix waypoint. As usual, I didn't make the fly over. I crashed once more to the desktop after the computer trying to load something around Seattle. Does anybody have any suggestions. This is getting rather old....Bummed out and not in Seattle....Mitch

32-bit OS?

Because of my only C.T.D. when attempting to fly anywhere around the Seattle area (even at 23,000 ft) the screen freezes, and computer shows busy, and then the C.T.D. The two offenders at different CTD events are the d3d.dll and the terrain.dll.Because I have ORBX PNW, Fjords, and Northern Rockies, I decided to reload all once more with also the PNW Service pack 1.03 to correct the double buildings in Seattle. I then applied the latest ORBX lib as they say to do after all the others. I rebooted, and then ran FSX again, with a flight path towards KSEA as a fix waypoint. As usual, I didn't make the fly over. I crashed once more to the desktop after the computer trying to load something around Seattle. Does anybody have any suggestions. This is getting rather old....Bummed out and not in Seattle....Mitch

I have all the ORBX programs you have installed but, a search of my system does not reveal d3d.dll. According to Google, d3d.dll is most likely malware disguised by evil people to look like a legitimate system file for DirectX. If it is legitimate (and XP use to use this dll), it would be located in the Windows/System32 folder. Anyplace else and it's more than likely malware. In any case, it was not installed by any ORBX programs. And, if you have Vista or Windows 7 OS, you can safely delete or, if you are afraid to delete it, just rename it to d3d.old, rerun FSX and see if it fixes the problem. I would run a good malware removal program and make sure there's no other malware threats on your system. In addition, I would look at your scenery.cfg and make sure it has not become corrupted, like Areas/Layers not in sequence or mismatched.Best regards,Jim

Don't we all like the outcome of misconceptions? :biggrin:Try g3d.dll instead, Jim. That's a (or THE) very typical CTD "cause" to show up in the logs. It isn't a cause at all it seems, but at least one can sum up some events by categorizing them by the .dll showing up.I think that Mitch might well be referring to that one.Mitch, there currently is a huge thread running over at Orbx', regarding the whole CTD aspect. I can't tell if you'll find a solution there, but at least some thoughts to share maybe.http://www.orbxsyste...-errors-in-pnw/And also mind the special CTD forum section here at Avsim. http://forum.avsim.net/forum/262-crash-to-desktop-ctd-forum/

A couple of suggestions.If you have your AI traffic set high turn it down to 20% and see what happens.Uninstall all ORBX PNW addons and delete all ORBX PNW addon folders/files that remain. Remove any separate addons for the area that you may have added like aiports downloaded from Avsim. Reboot. Run a registry cleaner like CCleaner and/or Glary's. Reboot then test.http://www.piriform.com/ccleaner/downloadFree download link is at the bottom of the grey box.http://www.glarysoft.com/products/utilities/registry-repair/If uninstalling works then add stuff back in one at a time and test until you find what addon is causing the problem and then go from there.

Mitch,A shot in the dark.....Try changing the season. Switch to the Winter or Fall season. Jack

Mitch,Are you using OzX or the free 2S1?

I have all the ORBX programs you have installed but, a search of my system does not reveal d3d.dll. According to Google, d3d.dll is most likely malware disguised by evil people to look like a legitimate system file for DirectX. If it is legitimate (and XP use to use this dll), it would be located in the Windows/System32 folder. Anyplace else and it's more than likely malware. In any case, it was not installed by any ORBX programs. And, if you have Vista or Windows 7 OS, you can safely delete or, if you are afraid to delete it, just rename it to d3d.old, rerun FSX and see if it fixes the problem. I would run a good malware removal program and make sure there's no other malware threats on your system. In addition, I would look at your scenery.cfg and make sure it has not become corrupted, like Areas/Layers not in sequence or mismatched.Best regards,Jim

-----------------------------------------------------------------------------Thanks for the feedback! I mistyped...it is g3d.dll. Sorry about that!Mitch

I have all the ORBX programs you have installed but, a search of my system does not reveal d3d.dll. According to Google, d3d.dll is most likely malware disguised by evil people to look like a legitimate system file for DirectX. If it is legitimate (and XP use to use this dll), it would be located in the Windows/System32 folder. Anyplace else and it's more than likely malware. In any case, it was not installed by any ORBX programs. And, if you have Vista or Windows 7 OS, you can safely delete or, if you are afraid to delete it, just rename it to d3d.old, rerun FSX and see if it fixes the problem. I would run a good malware removal program and make sure there's no other malware threats on your system. In addition, I would look at your scenery.cfg and make sure it has not become corrupted, like Areas/Layers not in sequence or mismatched.Best regards,Jim

-----------------------------------------------------------------------------Thanks for the feedback! I mistyped...it is g3d.dll. Sorry about that!Mitch

32-bit OS?

W7 64 bit Ultimate

Don't we all like the outcome of misconceptions? :biggrin:Try g3d.dll instead, Jim. That's a (or THE) very typical CTD "cause" to show up in the logs. It isn't a cause at all it seems, but at least one can sum up some events by categorizing them by the .dll showing up.I think that Mitch might well be referring to that one.Mitch, there currently is a huge thread running over at Orbx', regarding the whole CTD aspect. I can't tell if you'll find a solution there, but at least some thoughts to share maybe.http://www.orbxsyste...-errors-in-pnw/And also mind the special CTD forum section here at Avsim. http://forum.avsim.n...ktop-ctd-forum/

Thank you very much, I'll certainly check it all out. This is a major P.I.T.A.!

A couple of suggestions.If you have your AI traffic set high turn it down to 20% and see what happens.Uninstall all ORBX PNW addons and delete all ORBX PNW addon folders/files that remain. Remove any separate addons for the area that you may have added like aiports downloaded from Avsim. Reboot. Run a registry cleaner like CCleaner and/or Glary's. Reboot then test.http://www.piriform....leaner/downloadFree download link is at the bottom of the grey box.http://www.glarysoft...egistry-repair/If uninstalling works then add stuff back in one at a time and test until you find what addon is causing the problem and then go from there.

-----------------------------------------------------------------------------I guess this would be a safe bet...thank you. I'll look into doing this. I have my A.I. set to ORBX recommended; 16 percent.Mitch

Mitch,A shot in the dark.....Try changing the season. Switch to the Winter or Fall season. Jack

--------------------------------------------------------------------------Ok, Jack...I'll do that and try the same flight plan and see what happens. Thanks.Mitch

Mitch,Are you using OzX or the free 2S1?

Yes in fact, I have the 2S1 installed as well as OzX. You think it might be the 2S1?~?Mitch

-----------------------------------------------------------------------------Yes in fact, I have the 2S1 installed as well as OzX. You think it might be the 2S1?~?Mitch

Hi Mitch I PM'ed you about this did you get it?Regards

Delete 2S1 and see if that does it.If you have OzX installed, don't be surprised if you get crashes down under. I had to do a clean install to get rid of OzX.But, I don't have any more CTDs in specific areas like over Seattle.

It seems that when I approach WA61 heading straight from KFHR enroute to a fly over to KSEA...that I CTD with either a gd3.dll, or a terrain.dllIf you have PNW and the free Oz NA installed, that if you take my flight path at say 7,000 to 9,000 feet..that you will be also able to reproduce this gd3.dll or terrain.dll CTD also. I'll bet on it.I can repeat this over and over. There is something it seems that is fatal to FSX in or around the area of WA61. I can never get past this point no matter what aircraft, or at what altitude. There is something surrounding that airport that FSX can't handle. If I stay away from that general area at about a range of 30-50 miles, I am fine. I can fly all around KFHR and KORS with no problem whatsoever. I have all graphics cranked to full with the exception of MESH at 5M for general ORBX area usage.Mitch

Hi Mitch I PM'ed you about this did you get it?Regards

Not yet...I just got on. I added a further comment about what seems to me to be the 'culprit area'....it is where as I was viewing the garmin in the F1 Citation and approaching..that I went down with a CTD.Mitch

Delete 2S1 and see if that does it.If you have OzX installed, don't be surprised if you get crashes down under. I had to do a clean install to get rid of OzX.But, I don't have any more CTDs in specific areas like over Seattle.

----------------------------------------------------------Isn't this all so frustrating and crazy?!? I have no CTD's 'down under' with Oz installed...just this P.I.T.A. area around KSEA. Like I am posting...I can't even get within visual...I'll try deleting 2S1 and see what happens. I know (and read at length on the ORBX forums that this is NOT an exclusive g3d.dll and terrain.dll 'club'. Many other users are getting and being able to reproduce time and time again this CTD scenario. I was watching my GARMIN display like a hawk....and I was approaching a fly-over of WA61 when I CTD'd enroute to trying a fly over of KSEA.Mitch

At a suggestion from a PM message...I was advised to untick v1.10 Vachon-2S1 from my Scenery Lib. I did so...and then once more set up my test flight of KFHR----->KSEA------>(Calgary International)I was amazed when I actually got to, and flew over KSEA!!!!Is something in the the freeware Vachon 2S1 causing the gd3.dll and terrain.dll's ???? Before unticking this airport, I could NEVER get to KSEA from KFHR. I'm going to do another flight...but this is absolutely noteworthy. Somebody else with this KSEA area issue, should untick 2S1 and fly around to see if no CTD's occur after having done so.MitchEdit: I might be onto something here. In the Vachon menu, I had ticked off the Vachon air-show, but I never saw anything happen with A.I. in the sky over this airport. I wonder if that was causing the crashes, when fly over and near S21. If you have this airport package...untick the airshow and see if that helps.Edit 2: I just tried to untick the AIR SHOW box in the 2S1 Vachon Island control module. When I tried, a message box opened which stated that 'it could not switch Air Show'. The check mark left the box...but the message box opened with the latter. Could this be what is happening to a lot of other Vachon Island 1.1 version users? There is something corrupted/broken with the control box or scenery files themselves?

Mitch,I simply just deleted it when I found out that it was causing a CTD.I have a feeling that we are overloading our systems with too many add-ons, or there's something seriously wrong with some of the add-on software we are using.

Mitch,I simply just deleted it when I found out that it was causing a CTD.I have a feeling that we are overloading our systems with too many add-ons, or there's something seriously wrong with some of the add-on software we are using.

DJ, when I tried to uncheck the Air Show at the top of the control box menu...I got a message stating it could not turn off. The check mark was removed...but the message came up right after. I wonder if this is the corruption that is making FSX CTD when this scenery starts loading into the matrix as you approach the island even if having no intention of viewing/landing there.....I am going to bring Vachon Island back into the Scenery Lib and try to fly KFHR---------->KSEA but with the check mark extinguished for the Airshow, even though there was an error message and see what happens.....CTD or not.... BTW, there appears to be no uninstall option, so how did you make sure there were all BGL's and such referenced to Vachon removed from your system? Did you merely locate and delete the folder for it?I think that I found a fatal bug in the Vachon v1.1 that is supposed to fix the vegetation bug at that location. There appears to be another bug that once you choose the Air Show option, you can not deselect it. If you try, you get a 'could not select option Airshow' message box. If you untick the Airshow..and then vacate the control module...and then bring it back up...the Airshow will still be ticked as on. I'm now going to remove it as DJJose did. The ORBX guys should check this out. I did not get a KSEA fly over CTD when I unticked 2S1 in the Scenery Lib. All of the above is at least manifesting on my system. Who knows...it might not on the reader's....?!?Mitch

Everyone who has downloaded and installed:Vashon Island v1.10:If you go into the Vashon Island folder, inside your FSX/ORBX/FTX_NA/FTX_AA_2S1/Scenery folder, you might find that you have TWO (2) airshow.bgl files. I just did that and found that this is why I could not turn off the airshow option. Having 2 airshow files could be the reason for FSX crashing to the desktop with a g3d.ll failure in and/or around the KSEA area of ORBX PNW.This is the file: ORBX_PNW_2S1-Airshow_PLC-bglAs soon as I deleted one of those files, I then could turn on and off the Airshow option in the 2S1 control module.This might be a bug with the installer. I'm going to do a test flight towards KSEA from KFHR as soon as I finish typing this post with 2S1 operational in the Scenery Lib and if, with it still tick as available...I do not get my C.T.D....then that was (at least on my system) was the source of a CTD when flying near Vashon Island on towards KSEA. This is totally weird stuff...but it is what it is....