I just suffered a CTD in the J41. This is the first one in a long time. The error file had this:Log Name: ApplicationSource: Application ErrorDate: 4/26/2010 8:32:43 AMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: RichardSr-PCDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58Exception code: 0xc0000005Fault offset: 0x0006cdd0Faulting process id: 0x159cFaulting application start time: 0x01cae5318c79949dFaulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exeFaulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g3d.dllReport Id: cf24afd9-512f-11df-b6d4-00038a000015Event Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2010-04-26T12:32:43.000000000Z" /> <EventRecordID>39012</EventRecordID> <Channel>Application</Channel> <Computer>RichardSr-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>g3d.dll</Data> <Data>10.0.61637.0</Data> <Data>46fadb58</Data> <Data>c0000005</Data> <Data>0006cdd0</Data> <Data>159c</Data> <Data>01cae5318c79949d</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g3d.dll</Data> <Data>cf24afd9-512f-11df-b6d4-00038a000015</Data> </EventData></Event>Can anyone tell me what happened.ThksRichard Churchill

Hi Richard, If it was a one time thing, I wouldn't worry to much but if it is a persisting issue with the same faults it could be a number of things. Normally I do a google search of the faulting module but unfortunately you'll see a ton of issues (Only flight sim related) all tied to "g3d.dll". It can be scenery or livery textures, it can be due to a specific addon like AES and a number of other issues. From what I read it looks like it may also be tied into overloaded memory, but you'd need to try to see for yourself by investigating when the problem happens. So if it happens only when flying in certain areas where addon scenery is being introduced, it could be minimized to a couple possibles, etc. Some have reported replacing the g3d.dll with another fixed their issues, but you want to be careful now a days when downloading files like this.People cannot turn a .dll into a virus/spyware, but they can tie one into an installer, so don't trust any type of executable saying it will install it, since it is merely a .dll.You could also try reinstalling all of your C++ runtimes as that may help also. Again, it really comes down to how much of a problem and how often it is for you. Personally I wish EVERY addon/software company would have better logging for their apps to help find the problem since fsx.exe issues tell us absolutely nothing about a problem. Most addons don't have any type of logging at all but I love the ones that do.

Isn't there a recent thread on the g3d.dll? My memory is so poor, but maybe a search will find it for you.

Isn't there a recent thread on the g3d.dll? My memory is so poor, but maybe a search will find it for you.

Yes this was the first time,thanks for your input. If it continues I'll attempt a fixThanksRichard

I just saw it again in the large string pinned in the general section about fixing textures and crashes, take a look there.

I attempted to say (and obviously failed to make it obvious) that this error has no one exact place it can be pinpointed. What causes the error for one person may not be what happens for another.