If it is a timezone issue, I wonder if using SimElite Solutions Time Zone Fixer may fix the problem. May have to do a trans atlantic flight to see.

When I got the CTD many months ago, have not flown a TA since.

1 hour ago, ZKOKQ said:

If it is a timezone issue, I wonder if using SimElite Solutions Time Zone Fixer may fix the problem. May have to do a trans atlantic flight to see.

When I got the CTD many months ago, have not flown a TA since.

 

I’m absolutely curious now about the time zone theory.

4 hours ago, B777ER said:

If it is a time zone bug, we need to reference this thread over at the LM forum so they can look into it. An ntdll error with this CTD is very likely a memory management corruption issue. The sim looks for something, doesn't find it and bam, to the desktop you go. I'm away so blasting this out via my phone.  So if somebody can do the heavy lifting and get this shipped over to Lockheed Martin that would be appreciated.

I thought i read a thread over at the LM forum that P3Dv4.2 is going to have "various time zone fixes".  

Then again, it could be the scotch I had...

16 hours ago, tumtiddle said:

Any of those experiencing crashes using Navigraph Simlink (even if you aren't actively using it, is the plugin installed)?

I do, I had it installed on the last crash when it happened. And moving map on iPad. Although I didn’t have it installed when I experienced ctds in the same area. So I wouldn’t pass that simlink causes ctd errors

On 2/2/2018 at 3:28 PM, ZKOKQ said:

I wonder if using SimElite Solutions Time Zone Fixer may fix the problem

Unfortunately, it doesn't. I've got it installed and still get the ntdll crash.

Dang :(

On 3.2.2018 at 1:41 AM, Mace said:

I thought i read a thread over at the LM forum that P3Dv4.2 is going to have "various time zone fixes".  

Then again, it could be the scotch I had...

 

Confirmed by LM here

"We've made a few updates and fixes regarding time zones. You should find them in your next update."

Hopefully that’s the actual root cause of these CTDs then.

On 2/2/2018 at 0:47 PM, B777ER said:

I think it has to be something with the default software that is a carry over from the FSX days. People report a lot of the times it's with PMDG planes but I think that is only because they are really the only game in town for long haul aircraft. Once say the Aerosoft A330 is released people will get them with this as well. People also get it with default aircraft as alluded to earlier in this thread. 

If it is a time zone bug, we need to reference this thread over at the LM forum so they can look into it. An ntdll error with this CTD is very likely a memory management corruption issue. The sim looks for something, doesn't find it and bam, to the desktop you go. I'm away so blasting this out via my phone.  So if somebody can do the heavy lifting and get this shipped over to Lockheed Martin that would be appreciated.

Interesting.  How can I fly similar routes without experiencing the error?  The last time I did have a similar event was closer to the West coast of Hudson bay repeatable at the same coordinates.  I got rid of Navigraph SimLink and it went away so it appears my problem was different from the one of discussion here; however, I point out that I often fly the NATS and do not experience this event, nor do a majority of users based on this being the only thread on this topic.  I'm open to hypothesis such as a time zone bug, but one has to be much more specific and provide conditions and steps to reproduce the problem before you have a valid hypothesis.

15 minutes ago, downscc said:

Interesting.  How can I fly similar routes without experiencing the error?  The last time I did have a similar event was closer to the West coast of Hudson bay repeatable at the same coordinates.  I got rid of Navigraph SimLink and it went away so it appears my problem was different from the one of discussion here; however, I point out that I often fly the NATS and do not experience this event, nor do a majority of users based on this being the only thread on this topic.  I'm open to hypothesis such as a time zone bug, but one has to be much more specific and provide conditions and steps to reproduce the problem before you have a valid hypothesis.

Stop with the semantics Dan. If we could be more specific with the bloody issue it likely would have been resolved some time ago. Fact is, regardless of your personal experience, there is an anomaly going on in the sim in the upper northeastern part of Canada. LM will likely have to do a deep dive into the code to rectify it once and for all. People are getting them in vanilla installs thus highly likely there is a unique set of circumstances that when all come into play cause the CTD. It's been present for some time, just not in p3dv4.x. Lack if threads or amount of users reporting it is irrelevant to the fact the issue is present.

Good luck with that approach, do you think you have convinced LM to do a "deep dive" into their code to solve a rarely reported problem? I haven't seen this reported in the LM forums yet.

I'm curious if anyone else can reproduce the CTD with the below flight plan. I've tried it three times this weekend, and get a CTD every time. Happens about 60 miles before JOOPY. You should be able to 8x it if you want to save some time. I did that just now and it didn't change anything.

744 flight from EGLL-KIAD. Not sure weather matters much, but if it does, you can use 11 gmt today. I'm planning on trying this a few times with various things installed/uninstalled and on/off to see if I can find a cause.

https://www.dropbox.com/s/j5q6tejh6vhjjo2/EGLLKIAD01.rte?dl=0

I've downloaded the .RTE - Will try and fly it this week to see if I can produce at the same location.

21 hours ago, BlueFinn said:

 

Confirmed by LM here

"We've made a few updates and fixes regarding time zones. You should find them in your next update."

3 years of moaning and they are finally fixing them.  Now we just need dynamic light and stuttering and my faith will be restored 

15 hours ago, CaptKornDog said:

Hopefully that’s the actual root cause of these CTDs then.

I'm telling you it's timezones.  I'm convinced