P3D 4.2 and 747 loading problem

[B777ER 2,484]

5 hours ago, scandinavian13 said:

Interesting.

Start > type "View All Problem" and select "View All Problem Reports." Find P3D in the list. Find the latest crash report. Copy and paste here.

So far, we have a handful of similar reports. The only commonality is FSUIPC, and the 744.

Last CTD via the method you asked for:

 

Description
Faulting Application Path:    C:\Prepar 3D\Prepar3D.exe

Problem signature
Problem Event Name:    BEX64
Application Name:    Prepar3D.exe
Application Version:    4.2.21.24048
Application Timestamp:    5a7c832c
Fault Module Name:    bglmanx64.dll_unloaded
Fault Module Version:    4.0.0.8
Fault Module Timestamp:    59ddff64
Exception Offset:    0000000000019340
Exception Code:    c0000005
Exception Data:    0000000000000008
OS Version:    10.0.16299.2.0.0.256.48
Locale ID:    1033
Additional Information 1:    a0cf
Additional Information 2:    a0cf3cfd1960a3c1aca9ffac59202653
Additional Information 3:    b140
Additional Information 4:    b14028c889877bc4a6f85b7d01458f95

Extra information about the problem
Bucket ID:    cb8ca3f1f97b31aa70ad42dcaf897db8 (1201690191183052216)

 

Now pulling up Event Viewer/Custom Views/Administrative Events I see this for the last 3 CTD's, all FSDT Couatl.exe (and good luck getting Umberto to admit it's their problem):

 

Faulting application name: Couatl.exe, version: 3.2.0.3894, time stamp: 0x5a37ed5a
Faulting module name: ucrtbase.dll, version: 10.0.16299.125, time stamp: 0x9e3394c7
Exception code: 0xc0000409
Fault offset: 0x000933ab
Faulting process id: 0x330
Faulting application start time: 0x01d3a92362abd25c
Faulting application path: C:\P3DAddon\Addon Manager\Couatl\Couatl.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 7122e93c-59dc-4f10-9ec3-affc1c56e304
Faulting package full name: 
Faulting package-relative application ID: 

 

Faulting application name: Couatl.exe, version: 3.2.0.3894, time stamp: 0x5a37ed5a
Faulting module name: ucrtbase.dll, version: 10.0.16299.125, time stamp: 0x9e3394c7
Exception code: 0xc0000409
Fault offset: 0x000933ab
Faulting process id: 0x17fc
Faulting application start time: 0x01d3a922618e8bf2
Faulting application path: C:\P3DAddon\Addon Manager\Couatl\Couatl.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 540cf261-ae2a-4d2b-8522-8b318c72f0cb
Faulting package full name: 
Faulting package-relative application ID: 

 

Faulting application name: Couatl.exe, version: 3.2.0.3894, time stamp: 0x5a37ed5a
Faulting module name: ucrtbase.dll, version: 10.0.16299.125, time stamp: 0x9e3394c7
Exception code: 0xc0000409
Fault offset: 0x000933ab
Faulting process id: 0xea8
Faulting application start time: 0x01d3a8cebdf14af6
Faulting application path: C:\P3DAddon\Addon Manager\Couatl\Couatl.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 83e5fb06-b1f9-47b6-ba2d-f5a19267ab2a
Faulting package full name: 
Faulting package-relative application ID: 

[stratfordman10 0]

I too are having the exact same problem.

 

Michael

[scandinavian13 5,192]

On ‎2‎/‎18‎/‎2018 at 7:35 PM, cyyzrwy24 said:

Basically what are you saying this would LM problem? No issues with NGX and 777....

Our stuff was working in their betas and release candidate. Things stopped working in the RTM. We were able to alleviate many of the problems with our interim update, which was released last week. There must still be something in the background. Multiple developers are reporting that they're having issues.

...so, yes.

You'll note the crash reports in all of the issues are not pointing to our code. Eric's, above, all point to Couatl.exe. Many others point to generic P3D dlls. None of that is ours. The fact that the 744 loads after loading a default aircraft also suggests that it's not an issue with our code. If it were, it wouldn't be able to load at all.

[cyyzrwy24 127]

Thanks Kyle....Funny my crash report shows nothing (?!)....I guess you guys will get word from LM and advise or we have to wait for them to announce?

[AZJim320 0]

Having the same problem. It seems to be isolated to the PMDG 747.  All my other aircraft load normally, including the PMDG 777 and 737.  I can get the 747 to work by first loading the F22 like others have suggested..  I did a client only update to 4.2.  

Jim

[berts 97]

On 2/18/2018 at 6:51 PM, B777ER said:

By chance do you know if simply not starting Simserver for Remote CDU is sufficient or does it add/modify anything from PMDG?

To get Simserver for Remote CDU working with P3Dv4.2 and the PMDG 737, 747 or 777 aircraft, you will have to re-scan the Q Codes again using your iPad or Tablet.  Apart from that they work well and have not added or modified anything to my PMDG aircraft.

Bertie Goddard

[PAINMAN 33]

In my case it seems like its Active sky that causes the crash.

Tested without Active sky and no crash with active sky its a crash every time but only with the 747.

 

Kind regards.

[Andrey Galik 0]

On 22.02.2018 at 5:01 AM, Jim Milton said:

Having the same problem. It seems to be isolated to the PMDG 747.  All my other aircraft load normally, including the PMDG 777 and 737.  I can get the 747 to work by first loading the F22 like others have suggested..  I did a client only update to 4.2.

I have the same problem after update 747 to 3.00.8605 version

[amresh03 1]

On 23-2-2018 at 11:19 AM, PAINMAN said:

In my case it seems like its Active sky that causes the crash.

Tested without Active sky and no crash with active sky its a crash every time but only with the 747.

 

Kind regards.

I have the same problem!

regards Amresh S Mishre

[Olympic260 415]

All that having the issue and had not opened a ticket.

 

Can you please confirm that it loads ok without starting ActiveSky at the beginning?

[Andrey Galik 0]

2 hours ago, Olympic260 said:

All that having the issue and had not opened a ticket.

 

Can you please confirm that it loads ok without starting ActiveSky at the beginning?

No (((  I can`t confirm that.  When I start 747  without Active Sky at the beginning, my P3Dv4.2 crashes too.

 

Edited February 25, 2018 by Andrey Galik

[Keen 6]

3 hours ago, Olympic260 said:

Can you please confirm that it loads ok without starting ActiveSky at the beginning?

No luck for me with ActiveSky closed.

Interestingly I can load a saved flight perfectly fine, but starting a new flight with the 744 always crashes during initialization unless I start with a default aircraft.

Tony Wills

[PAINMAN 33]

Just completed a 10 hour flight with the 747.

I loaded the scenery with default F22 and when the scenery was done loading i switched to the 747 no crash at all.

BUT if i choose the 747 with AS activated in the beginning it will crash.

Do a test and load the F22 first at your scenery and the gate you want and when its done loading switch to the 747.

 

Kind regards

[davjg 32]

Hi

After not being able to fly 747 after the update for P3Dv4 AND from PMDG OC, I get a constant crash. Therefore I have decided to uninstall everything to find the problem. After ensuring I did a clean installed I finally got her working without any crash. The only install was the following

1. P3D a full clean installed

2. Both PMDG 737/777 no issues as before - nothing change here

3. FSUIPC

4. Envidir/EnvTex/EnvShade

I did get a CTD when I start Active Sky/ASCA P3Dv4 with beta no issues for 737/777 BUT the 747  gave me CTD. When loading the 747 the screen remain black for 4 secs than the cockpit would appear for the countdown. Additionally I also get a CTD if I set it for cold & dark regardless whether I saved the panel to that setting or not without Active Sky. I also learned that even though you shut down Active Sky make sure you do the same for ASCA otherwise it will be lurking in the background conflicting with the 747.

 

I hope this information helps

David G.

[B777ER 2,484]

Maybe it's the priority of the way the dll's are loaded into the sim.