Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

P3D 4.1 CTD near Labrador

Featured Replies

On 19/12/2017 at 11:49 AM, Johnny19 said:

Guys,

I don't get CTD often, i am usually using my sim on short haul routes, long hauls a bit less, but it seems that is can't cross the Atlantic westbound without a program stoped working error. It is not a first time that a sim crashes near the Labrador peninsula, right about when exiting the NAT track. I haven't had issues flying over Greenland westobun, or NAT eastbound. Also no crashes on long hauls in other parts of the sim world. Addons using are pmdg 747 and 777, orbx global, vector, north america, Europe, active sky. I am thinking about reinstalling my system today.  Any thoughts would be really appriciated.

Using fsrealtime?? 

 
 
 
 
 
  913456
  • Replies 465
  • Views 62.5k
  • Created
  • Last Reply
On 12/19/2017 at 4:27 PM, G-YMML1 said:

Same here. Only happens in P3Dv4, P3Dv3.0 worked flawlessly

 

On 12/19/2017 at 2:40 PM, nazethc said:

Same for me, 4.1, Vector, NA LC, PMDG.  P3D always crashing while approaching Canada from Europe over Labrador also.  No mytraffic installed.  There is some kind of conflict in that area....I still can't nail it down though.

 

On 12/19/2017 at 10:30 PM, regis9 said:

I’ve also had repetitive crashes both approaching Labrador and over Greenland...it’s like a flightsim Bermuda Triangle.  I generally don’t fly between Europe and the US west coast anymore...too risky.

I know others have run into similar situations, where an otherwise stable sim is crashing in these locations only.  It would be interesting if there was a way for anyone who encounters a CTD in this area to log it on a map using the last/long coordinates at the point of CTD.  Not sure if such a tool exists?  That might help shed some light on the exact location causing the CTD (if there is one).  

My money’s on something weird buried deep down in the default scenery in these areas.

 

On 12/20/2017 at 7:17 PM, swiesma said:

Same here. I gave up the routes to America since V4. 

 

On 12/20/2017 at 8:20 PM, Johnny19 said:

As i said, it can be anything that affects the crash. It's just weird that it happens only around the same area of the sim world - north Atlantic Canadian side of the pond. I haven't had issues anywhere else. 

As above I also get them in that exact area.  Been saying it for 2 years that's theres something a foot in that area. 

Be interesting to hear how many of you use fsrealtime.  I'm convinced it's a timezone issue when you cross from the zulu at - 3.5 to - 4.

I think fsrealtime and the sim gets confused and boom CTD. 

My logic behind this is it always seem to happen in that area where the time line is, and it also for me only happens when traveling westbound not eastbound.

Although Good luck getting LM to admit there is an issue, youve got no chance. 

 
 
 
 
 
  913456

No i'm not using FSrealtime

  • Author

Not using FSrealtime also.

Ivan Majetic

ROG CROSSHAIR X670E HERO; 7900X3D; NZXT KRAKEN ELITE 360, GIGABYTE RTX 4080; G.SKILL TridentZ NEO RGB DDR5 64 Gb, WD HDD 2TB, SAMSUNG 980PRO, SAMSUNG 970EVO Plus 2x, ALIENWARE 3423DWF

I do not use fsrealtime.

Dave

Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 5090, 55" Samsung Q80T, 64GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU

Not using fsrealtime.

Eric 

 

 

  • 3 weeks later...

I got this today as well. NTDLL as the faulitng module. FTX Global and UTL (but no traffic at time).

Don't recall getting one before, happened as I was about 100m from the Canadian coastline between EDDF and KIAH. PITA!

 

 

Kael Oswald

9950X3D/ 64GB DDR5 6200 @ CL30 / Custom Water Loop / RTX 5090 / 3 x 48" LG C4 OLEDs

  • Commercial Member

Risked it today, same NTDLL CTD near the Canadian coastline as well in the PMDG 77L.  Westbound LHR-ORD (the eastbound flight was fine).  Would frequently get this in FSX:SE and now P3Dv4.

 

My previous work around in FSX:SE was to disable Vector.  Guess I'll try that again here.  NA LC, Global, Vector installed.

Kyle Weber (Private Pilot, ASEL; Flight Test Engineer)
Check out my repaints and downloads, all right here on AVSIM

Are you all using GSX for pushback? If so, after pushback is done, go to menu, restart coualt. Then see what happens? 

Eric 

 

 

I've experienced it before and do not have vector installed.  I do have UTX Canada installed though.

Dave

Current System (Running at 4k): ASUS ROG STRIX X670E-F, Ryzen 7800X3D, RTX 5090, 55" Samsung Q80T, 64GB DDR5 6000 RAM, EVGA CLC 280mm AIO Cooler, Brunner CLS-E NG Yoke, Thrustmaster Warthog HOTAS & Stick, Thrustmaster TCA Quadrant & Add-on, VirtualFly Ruddo+, TQ6+ and Yoko+, GoFlight MCP-PRO and EFIS, Skalarki FCU and MCDU

Are you guys all using the 777???

 
 
 
 
 
  913456

I have an very similiar problem ... my P3D will crash when i'm flying east and cross the E30° longitude resp. when im flying west it will crash between E97° and E98°. Also with stock aircraft, in my case it's the kernelbase.dll which causes the CTD. See the thread in the CTD forum for more info.

System: i9 [email protected] - 32 GB RAM - Aorus 1080ti --- Sim/Addons: P3D v5 + ProSim737
Signature3.png

Hi all,

 

I had this problem too but I managed to fix it. My error was an ntldll.dll error.

Here were the conditions:

P3Dv4.1

PMDG 777-200 flying northeast of Labrador, heading west/southwest.

Addons: FSDT CYYZ, FB KSFO, Orbx KSAN, Imaginesim KATL, FB KDEN, FB KIAD, UTL live, ORBX global, vector, NA landclass ASP4 with ASCA and Envtex only textures. All of these at there latest builds.

Sim crashes with ntldll.dll as the faulting module.

 

I reviewed the Avsim CTD document https://www.avsim.com/files/file/65-avsim-crash-to-desktop-guide-for-fsx-p3d-fs9/and followed its advice. I eventually cured these crashes by downloading Driver Booster and letting it update my drivers, apart from the nvidia driver. (I like to do a clean install of that manually but I have the latest driver 390.65.)

Driver Booster found many intel drivers and motherboard drivers out of date, about 19 in all, even though I had downloaded the latest ones from the Gigabyte site.

Not had the ntldll.dll errors since.

 

My computer specs are my sig.

 

Hopefully this will help some of you resolve this PITA.

Refards


Stu

 

i7 12700K , DDR4 64GB RAM @3600MHz, Asus Z690-Plus D4 MB, Gainward 4090 RTX Graphics, 850W Corsair PSU, Kraken AIO watercooler, Nvme 1TB ssd, 1TB ssd, 500GB ssd.

  • Commercial Member
On 1/31/2018 at 6:21 PM, B777ER said:

Are you all using GSX for pushback? If so, after pushback is done, go to menu, restart coualt. Then see what happens? 

No change on this end.  CTD (ntdll.dll) 127 NM E of YDP.

 

 

Kyle Weber (Private Pilot, ASEL; Flight Test Engineer)
Check out my repaints and downloads, all right here on AVSIM

 

1 hour ago, CaptKornDog said:

No change on this end.  CTD (ntdll.dll) 127 NM E of YDP.

 

 

 

21 hours ago, JoeFackel said:

I have an very similiar problem ... my P3D will crash when i'm flying east and cross the E30° longitude resp. when im flying west it will crash between E97° and E98°. Also with stock aircraft, in my case it's the kernelbase.dll which causes the CTD. See the thread in the CTD forum for more info.

both using the 777-200 ???

 
 
 
 
 
  913456

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.