UCRTBase.dll CTD with P3DV5.1 SODE 1.7.1 and AIGAIM

[MammyJammy 124]

6 hours ago, 12bPilot said:

Thanks for your tests.

What if you went to some „non-SODE jetway“ airport and leave the detection setting on and AI traffic on?

This test will reveal if the AI collection within SODE triggers the crash or the activation of the SODE jetways.

I have done several tests over the past few days.  Here's what I have found.

With SODE enabled (registered via the SODE Platform Manager) I will get a ucrtbase.dll crash regardless of AI setting in SODE.  Here's what I tested:

PC:

9900K @ 5 ghz (removed overclock and re-tested all scenarios, no effect)
32GB RAM
1080 ti (Nvidia Drivers 456.71)

Steps to duplicate:

1)  Start a flight in the default F-35 at KSEA, runway 34R.
2)  Slew/look around for a few seconds
3)  Slew up to roughly 2,000 ft.  Slew ahead to downtown Seattle/Paine Field
4)  Wait for screen freeze/CTD (if it does not happen instantly, keep slewing around)
 

Here's the scenarios I tested
1)  DEFAULT P3D 5.1 install (client, content, scenery), no add-ons, Default F-35
No crashes.

2)  DEFAULT P3D 5.1 install, SODE enabled, AI Detection on, no add-ons (except SODE), default AI, Default F-35
Crash from ucrtbase.dll as the faulting module with Prepar3d.exe as the faulting application within 20 seconds +/- 10 seconds

3)  P3D 5.1 install, SODE unregistered, D. Design Seattle X + Airports (no SODE jetways as SODE was disabled), Default F-35
No crashes.

4)  P3D 5.1 install, SODE unregistered, 86 add-ons, AIG AIM, PMDG and QualityWings aircraft (no SODE jetways as SODE was disabled)
No crashes.  I also performed a full flight 8h 31m KSEA-EGLL in the QW 787 with full AIG AI, no crashes.

5)  P3D 5.1 install, SODE enabled, AI Detection OFF, 86 add-ons, AIG AIM, PMDG and QualityWings aircraft
Crash from ucrtbase.dll with as the faulting module Prepar3d.exe as the faulting application within 20 seconds +/- 10 seconds

5)  P3D 5.1 install, SODE enabled, AI Detection OFF, AIG AIM, base scenery (Randolph AFB), default F-35
Crash from ucrtbase.dll with as the faulting module Prepar3d.exe as the faulting application within 20 seconds +/- 10 seconds

6)  P3D 5.1 install, SODE enabled, AI Detection OFF, AIG AIM, AI SET TO 0%, default F-35
Crash from ucrtbase.dll with as the faulting module Prepar3d.exe as the faulting application within 20 seconds +/- 10 seconds

All the faults are identical, except time stamps. 

Faulting application name: Prepar3D.exe, version: 5.1.8.26742, time stamp: 0x5f988752
Faulting module name: ucrtbase.dll, version: 10.0.19041.546, time stamp: 0x43cbc11d
Exception code: 0xc0000409
Fault offset: 0x000000000007287e
Faulting process id: 0x263c
Faulting application start time: 0x01d6ad9f5d78997f
Faulting application path: D:\p3dv5\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 8751468d-3c07-4d55-bbde-a4e17cc65bbf
Faulting package full name: 
Faulting package-relative application ID: 

And the last of the SODE log from the last error:

[16:39:54.094] INFO SODE.FSLOOP :  - SimObject 'S50_X:Seasonal Object based on Texture Variation' [Seasonal Trees S50 FA]. ID: 218
[16:39:54.094] INFO SODE.FSLOOP : ### FILTERING OBJECTS: R=40000m, Bubble Lat/Lon: 47.606050, -122.306801 ###
[16:39:54.210] INFO SODE.FSLOOP : ### Active SimObjects: 118; Active Wind Data Probes: 0 ###
[16:40:01.225] FATAL SODE.WATCHDOG : Sim Process running test failed!
[16:40:01.239] DEBUG SODE.FSPROCESS : Cleaning up Memory...
[16:40:01.258] DEBUG SODE.FSPROCESS : Removing Top-Menu structure...
[16:40:01.258] DEBUG SODE.FSPROCESS : Closing Connection to FS.
[16:40:01.367] INFO  : Terminate SODE.

Let me know if other scenarios would be helpful, with/without add-ons, etc.  Hope it helps.

[mpo910 2,112]

8 hours ago, MammyJammy said:

I have done several tests over the past few days.  Here's what I have found.

With SODE enabled (registered via the SODE Platform Manager) I will get a ucrtbase.dll crash regardless of AI setting in SODE.  Here's what I tested:

PC:

9900K @ 5 ghz (removed overclock and re-tested all scenarios, no effect)
32GB RAM
1080 ti (Nvidia Drivers 456.71)

Steps to duplicate:

1)  Start a flight in the default F-35 at KSEA, runway 34R.
2)  Slew/look around for a few seconds
3)  Slew up to roughly 2,000 ft.  Slew ahead to downtown Seattle/Paine Field
4)  Wait for screen freeze/CTD (if it does not happen instantly, keep slewing around)
 

Here's the scenarios I tested
1)  DEFAULT P3D 5.1 install (client, content, scenery), no add-ons, Default F-35
No crashes.

2)  DEFAULT P3D 5.1 install, SODE enabled, AI Detection on, no add-ons (except SODE), default AI, Default F-35
Crash from ucrtbase.dll as the faulting module with Prepar3d.exe as the faulting application within 20 seconds +/- 10 seconds

3)  P3D 5.1 install, SODE unregistered, D. Design Seattle X + Airports (no SODE jetways as SODE was disabled), Default F-35
No crashes.

4)  P3D 5.1 install, SODE unregistered, 86 add-ons, AIG AIM, PMDG and QualityWings aircraft (no SODE jetways as SODE was disabled)
No crashes.  I also performed a full flight 8h 31m KSEA-EGLL in the QW 787 with full AIG AI, no crashes.

5)  P3D 5.1 install, SODE enabled, AI Detection OFF, 86 add-ons, AIG AIM, PMDG and QualityWings aircraft
Crash from ucrtbase.dll with as the faulting module Prepar3d.exe as the faulting application within 20 seconds +/- 10 seconds

5)  P3D 5.1 install, SODE enabled, AI Detection OFF, AIG AIM, base scenery (Randolph AFB), default F-35
Crash from ucrtbase.dll with as the faulting module Prepar3d.exe as the faulting application within 20 seconds +/- 10 seconds

6)  P3D 5.1 install, SODE enabled, AI Detection OFF, AIG AIM, AI SET TO 0%, default F-35
Crash from ucrtbase.dll with as the faulting module Prepar3d.exe as the faulting application within 20 seconds +/- 10 seconds

All the faults are identical, except time stamps. 

Faulting application name: Prepar3D.exe, version: 5.1.8.26742, time stamp: 0x5f988752
Faulting module name: ucrtbase.dll, version: 10.0.19041.546, time stamp: 0x43cbc11d
Exception code: 0xc0000409
Fault offset: 0x000000000007287e
Faulting process id: 0x263c
Faulting application start time: 0x01d6ad9f5d78997f
Faulting application path: D:\p3dv5\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 8751468d-3c07-4d55-bbde-a4e17cc65bbf
Faulting package full name: 
Faulting package-relative application ID: 

And the last of the SODE log from the last error:

[16:39:54.094] INFO SODE.FSLOOP :  - SimObject 'S50_X:Seasonal Object based on Texture Variation' [Seasonal Trees S50 FA]. ID: 218
[16:39:54.094] INFO SODE.FSLOOP : ### FILTERING OBJECTS: R=40000m, Bubble Lat/Lon: 47.606050, -122.306801 ###
[16:39:54.210] INFO SODE.FSLOOP : ### Active SimObjects: 118; Active Wind Data Probes: 0 ###
[16:40:01.225] FATAL SODE.WATCHDOG : Sim Process running test failed!
[16:40:01.239] DEBUG SODE.FSPROCESS : Cleaning up Memory...
[16:40:01.258] DEBUG SODE.FSPROCESS : Removing Top-Menu structure...
[16:40:01.258] DEBUG SODE.FSPROCESS : Closing Connection to FS.
[16:40:01.367] INFO  : Terminate SODE.

Let me know if other scenarios would be helpful, with/without add-ons, etc.  Hope it helps.

I can also exactly replicate what @MammyJammy wrote!

Thanks for writing so clear what you did.

@12bPilot

I checked following:

AI on

SODE Activated

AI Detection in SODE FALSE (so OFF)

KSFO Flightbeam

A330 Aerosoft

Jetways connected

Called GSXL2

Undocked jetways

Called pushback via GSXL2

Pushback started

CTD ucrtbase.dll after a couple of seconds ((round about 10Sec?)

Regards Marcus

Edited November 1, 2020 by mpo910

[yvesamuel 17]

Hi,

 

I can confirm that SODE seemes cumpilt.
I uninstalled SODE and now I'm flying...

 

Best regards from ELLX

Yves

[yvesamuel 17]

Hi,

 

Just tried to reinstall SODE in another directory. Same problem.
I wait now for a anwxer...

 

Yves

[flynman33 15]

I have this same issue "AFTER installing AIG-OC" on my hard drive.

[20:27:10.243] INFO SODE.FSLOOP :  - SimObject 'Flightbeam_KPDX:Jetway 1 GATE_C 5' [kpdx_jetway]. ID: 135
[20:27:10.243] INFO SODE.FSLOOP :  - SimObject 'Flightbeam_KPDX:Jetway 1 GATE_C 3' [kpdx_jetway]. ID: 136
[20:27:10.243] INFO SODE.FSLOOP :  - SimObject 'Flightbeam_KPDX:EDP KPDX' [12bPilot_SODE_Environmental_Data_Probe]. ID: 133
[20:27:10.243] INFO SODE.FSLOOP : ### FILTERING OBJECTS: R=40000m, Bubble Lat/Lon: 45.742366, -122.596179 ###
[20:27:10.346] INFO SODE.FSLOOP : ### Active SimObjects: 63; Active Wind Data Probes: 1 ###
[20:27:51.285] FATAL SODE.WATCHDOG : Sim Process running test failed!
[20:27:51.298] DEBUG SODE.FSPROCESS : Cleaning up Memory...
[20:27:51.315] DEBUG SODE.FSPROCESS : Removing Top-Menu structure...
[20:27:51.315] DEBUG SODE.FSPROCESS : Closing Connection to FS.
[20:27:51.425] INFO  : Terminate SODE.

I was flying the PMDG 737-7 out of Flightbeams KPDX to CYVR. When the aircraft crossed the BTG VOR 10 miles north of PDX the screen would freeze and then CTD.

I disabled my AIG AI aircraft and deactivated SODE and was able to fly 15 minutes before I terminated the flight. Then I disabled the AI function of SODE and enabled AIG and had the same freeze over the BTG VOR again. I also deactivated SODE and activated AIG with the same CTD at the same point.

Sounds like 12bpilot has some work cut out for them.

 

 

Randy

 

 

[Fantrainer 5]

Hi

I`ve the issue too, in addition I can confirm the ctds dissapear after disabling sode, so I hope LM or SODE could be aware of this.

Regards

 

[12bPilot 35]

On 11/1/2020 at 12:46 AM, MammyJammy said:

I have done several tests over the past few days.  Here's what I have found.

With SODE enabled (registered via the SODE Platform Manager) I will get a ucrtbase.dll crash regardless of AI setting in SODE.  Here's what I tested:

PC:

9900K @ 5 ghz (removed overclock and re-tested all scenarios, no effect)
32GB RAM
1080 ti (Nvidia Drivers 456.71)

Steps to duplicate:

1)  Start a flight in the default F-35 at KSEA, runway 34R.
2)  Slew/look around for a few seconds
3)  Slew up to roughly 2,000 ft.  Slew ahead to downtown Seattle/Paine Field
4)  Wait for screen freeze/CTD (if it does not happen instantly, keep slewing around)
 

Here's the scenarios I tested
1)  DEFAULT P3D 5.1 install (client, content, scenery), no add-ons, Default F-35
No crashes.

2)  DEFAULT P3D 5.1 install, SODE enabled, AI Detection on, no add-ons (except SODE), default AI, Default F-35
Crash from ucrtbase.dll as the faulting module with Prepar3d.exe as the faulting application within 20 seconds +/- 10 seconds

3)  P3D 5.1 install, SODE unregistered, D. Design Seattle X + Airports (no SODE jetways as SODE was disabled), Default F-35
No crashes.

4)  P3D 5.1 install, SODE unregistered, 86 add-ons, AIG AIM, PMDG and QualityWings aircraft (no SODE jetways as SODE was disabled)
No crashes.  I also performed a full flight 8h 31m KSEA-EGLL in the QW 787 with full AIG AI, no crashes.

5)  P3D 5.1 install, SODE enabled, AI Detection OFF, 86 add-ons, AIG AIM, PMDG and QualityWings aircraft
Crash from ucrtbase.dll with as the faulting module Prepar3d.exe as the faulting application within 20 seconds +/- 10 seconds

5)  P3D 5.1 install, SODE enabled, AI Detection OFF, AIG AIM, base scenery (Randolph AFB), default F-35
Crash from ucrtbase.dll with as the faulting module Prepar3d.exe as the faulting application within 20 seconds +/- 10 seconds

6)  P3D 5.1 install, SODE enabled, AI Detection OFF, AIG AIM, AI SET TO 0%, default F-35
Crash from ucrtbase.dll with as the faulting module Prepar3d.exe as the faulting application within 20 seconds +/- 10 seconds

All the faults are identical, except time stamps. 

Faulting application name: Prepar3D.exe, version: 5.1.8.26742, time stamp: 0x5f988752
Faulting module name: ucrtbase.dll, version: 10.0.19041.546, time stamp: 0x43cbc11d
Exception code: 0xc0000409
Fault offset: 0x000000000007287e
Faulting process id: 0x263c
Faulting application start time: 0x01d6ad9f5d78997f
Faulting application path: D:\p3dv5\Prepar3D.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: 8751468d-3c07-4d55-bbde-a4e17cc65bbf
Faulting package full name: 
Faulting package-relative application ID: 

And the last of the SODE log from the last error:

[16:39:54.094] INFO SODE.FSLOOP :  - SimObject 'S50_X:Seasonal Object based on Texture Variation' [Seasonal Trees S50 FA]. ID: 218
[16:39:54.094] INFO SODE.FSLOOP : ### FILTERING OBJECTS: R=40000m, Bubble Lat/Lon: 47.606050, -122.306801 ###
[16:39:54.210] INFO SODE.FSLOOP : ### Active SimObjects: 118; Active Wind Data Probes: 0 ###
[16:40:01.225] FATAL SODE.WATCHDOG : Sim Process running test failed!
[16:40:01.239] DEBUG SODE.FSPROCESS : Cleaning up Memory...
[16:40:01.258] DEBUG SODE.FSPROCESS : Removing Top-Menu structure...
[16:40:01.258] DEBUG SODE.FSPROCESS : Closing Connection to FS.
[16:40:01.367] INFO  : Terminate SODE.

Let me know if other scenarios would be helpful, with/without add-ons, etc.  Hope it helps.

Thanks a lot for the various tests and your write-up.

I'm trying to CTD with your scenario 2), since that one involves no add-ons except SODE. Did as instructed but couldn't get it to crash unfortunately.

Question: Is your SODE xml folder empty (C:\ProgramData\12bPilot\SODE) ? Since those data are shared across simulators, it could be that P3Dv4 objects are still loaded in v5 (from the v4 install), even if the airport is not installed explicitly. I'd be particularly interested if the CTD still happens if the xml folder is empty, and for the same reason the "cfg" subfolder.

[mpo910 2,112]

29 minutes ago, 12bPilot said:

Thanks a lot for the various tests and your write-up.

I'm trying to CTD with your scenario 2), since that one involves no add-ons except SODE. Did as instructed but couldn't get it to crash unfortunately.

Question: Is your SODE xml folder empty (C:\ProgramData\12bPilot\SODE) ? Since those data are shared across simulators, it could be that P3Dv4 objects are still loaded in v5 (from the v4 install), even if the airport is not installed explicitly. I'd be particularly interested if the CTD still happens if the xml folder is empty, and for the same reason the "cfg" subfolder.

At least mine is not empty. I did a full clean install P3D V5.0 and "compatible addons. Then uninstalled P3D V5.0 completely. Installed all P3D V5.1 components via the updated P3D Setup.EXE.

Remarkable is, with AIGAIM  turned on, AIGAIM Traffic in the sim the CTD occurs much quicker as without AIGAIM Traffic (so all traffic sliders turned off). Always within couple of minutes!

Also with AI Traffic Autodetection turned off, the CTD came first when pushed back with addon airplane like Aerosoft A330 at payware airport KSFO HD2

When using a Stock F22, AI turned on and autodetection turned off I could NOT reproduce a CTD within 25 minutes testing cycles each.

My C:\ProgramData\12bPilot\SODE\xml shows all ADDON SODE XML files 

My C:\ProgramData\12bPilot\SODE\cfg shows one DrzewieckiDesign.sdx file

My C:\ProgramData\12bPilot\SODE\sdx\DrzewieckiDesign shows several NNNN_X.sdx files, all from DrzewieckiDesign

Edited November 2, 2020 by mpo910

[12bPilot 35]

Could you create some "temp" folder in that SODE root folder and copy all the contents of the "cfg" and the "xml" subfolder into it? When the cfg and xml are cleared out, SODE will not have any input files to work with and will run in some sort of "idle-mode". I would be highly interested if the CTD still occur in this idle-mode.

Thanks for all your help, guys.

Also, to get all the info as I can get, could you turn on "Debug Mode" within SODEPlatformManager.exe -> Tools -> Settings ? This will generate a more detailed SODE.log file.

To those who consistently can create CTDs: A SimConnect trace log could be helpful, since it shows all the communications between Prepar3D and the SimConnect add-ons (such as SODE). Maybe I can pinpoint the exact SimConnect call which could trigger the crash. Instructions on how to generate such a trace log: https://sode.12bpilot.ch/?topic=faq, Section D.

[mpo910 2,112]

18 minutes ago, 12bPilot said:

Could you create some "temp" folder in that SODE root folder and copy all the contents of the "cfg" and the "xml" subfolder into it? When the cfg and xml are cleared out, SODE will not have any input files to work with and will run in some sort of "idle-mode". I would be highly interested if the CTD still occur in this idle-mode.

Thanks for all your help, guys.

Also, to get all the info as I can get, could you turn on "Debug Mode" within SODEPlatformManager.exe -> Tools -> Settings ? This will generate a more detailed SODE.log file.

To those who consistently can create CTDs: A SimConnect trace log could be helpful, since it shows all the communications between Prepar3D and the SimConnect add-ons (such as SODE). Maybe I can pinpoint the exact SimConnect call which could trigger the crash. Instructions on how to generate such a trace log: https://sode.12bpilot.ch/?topic=faq, Section D.

On my way....

[mpo910 2,112]

3 hours ago, 12bPilot said:

Could you create some "temp" folder in that SODE root folder and copy all the contents of the "cfg" and the "xml" subfolder into it? When the cfg and xml are cleared out, SODE will not have any input files to work with and will run in some sort of "idle-mode". I would be highly interested if the CTD still occur in this idle-mode.

Thanks for all your help, guys.

Also, to get all the info as I can get, could you turn on "Debug Mode" within SODEPlatformManager.exe -> Tools -> Settings ? This will generate a more detailed SODE.log file.

To those who consistently can create CTDs: A SimConnect trace log could be helpful, since it shows all the communications between Prepar3D and the SimConnect add-ons (such as SODE). Maybe I can pinpoint the exact SimConnect call which could trigger the crash. Instructions on how to generate such a trace log: https://sode.12bpilot.ch/?topic=faq, Section D.

Hello @12bPilot Jeffrey

I performed 2 Tests.

Test 1 called SODE Files in TEMP

• SODE DEBUG Mode on
• SODE AI Jetway Autodetection = FALSE
• As you instructed I moved all the files from SODE to a TEMP folrder
• started P3D
• Selected A330 Aerosoft
• Selected EDDF Gate A20
• No SODE Jetways visible, as expected
• After 10 Minutes still no CTD

Test 2 called TEST Normal Procedure

• All files back to the normal folders in SODE
• SODE AI Jetway Autodetection turned TRUE
• Started P3D
• Selected A330
• Selected EDDF Gate A20
• Waited till scenery is loaded
• Let both Jetways dock via GSX Menu
• After a few seconds CTD

I have both file packages with DEBUG LOGS and SIMCONNECT.LOG stored in 1 Folder at DropBox. in that folder you will find both packages.

LINK CAN BE REPLACED IF NEEDED ( @12bPilot)

Regards Marcus

Edited November 2, 2020 by mpo910

[Dick 47]

Dear 12B pilot,

 

I have a simconnect log. The file was too big to copy paste here. It is in the mail now to you

Thank you very much !

b rdgs / Dick

[12bPilot 35]

Thanks for the data, they helped me narrow down the conditions and I was able to reproduce the CTD.

In my case, SODE's AI detection is OFF, the SODE jetway must have a static variant (gets swapped to a dynamic one when stand is selected...).

Using SODE's own text-menu, I select the stand, dock the jetway. Then undock the jetway. Then from the menu, I de-select the stand manually -> CTD.

So something when swapping the dynamic jetway back to the static one triggers the CTD (in fact, I am removing the dynamic jetway using SimConnect). And it is exactly this SimConnect object removal call which trigger it. Funny thing is, it only it only crashes when the jetway has moved! When I select the stand and de-select it again without operating the jetway, it doesn't CTD, even though the very same SimConnect removal call is fired...very strange. Worked in all previous P3D versions without any troubles.

I need to investigate further to confirm that the removal call is flawed, just thought I give you guys a heads up.

[Dick 47]

Thank you !

It is of any help to know that not at all airports jetways cause the CTD ? (at least on my system.)

I tried FSDT KORD en Gaya;s EDDT and there I could pushback normally. I could do further testing but do not know which addon airports you may have.

Jetway movement and pushback at FlyTampa KLAS and EKCH did trigger a CTD.

Good luck with your trouble shooting !

b rdgs / Dick

[AlanB77L 0]

31 minutes ago, 12bPilot said:

Thanks for the data, they helped me narrow down the conditions and I was able to reproduce the CTD.

In my case, SODE's AI detection is OFF, the SODE jetway must have a static variant (gets swapped to a dynamic one when stand is selected...).

Using SODE's own text-menu, I select the stand, dock the jetway. Then undock the jetway. Then from the menu, I de-select the stand manually -> CTD.

So something when swapping the dynamic jetway back to the static one triggers the CTD (in fact, I am removing the dynamic jetway using SimConnect). And it is exactly this SimConnect object removal call which trigger it. Funny thing is, it only it only crashes when the jetway has moved! When I select the stand and de-select it again without operating the jetway, it doesn't CTD, even though the very same SimConnect removal call is fired...very strange. Worked in all previous P3D versions without any troubles.

I need to investigate further to confirm that the removal call is flawed, just thought I give you guys a heads up.

This tallies with what I experienced and reported in your forum: https://sode.12bpilot.ch/?topic=p3dv5-hf2-ctd

The jetway keeps docking at the A321's L2 door, needing me to reset it and send it to L1. This reset causes a CTD every time.