CTD on First Load After 1.34.14.0 Update During Loading Screen After Clicking FLY w/ A310 at KLAX

Bug Reporting Hub Crashes (CTDs)
, , , ,
1

Have you disabled/removed all your mods and add-ons?

No, in this case – I’ve been testing regularly with and without them as chronicled elsewhere in the beta forum.

Are you using Developer Mode or made changes in it?

No

Brief description of the issue:

This may have been a one-off, but I feel it ought to be reported given the 1.34.14.0 release notes for the A310 indicate a fix for CTDs for some users and I had not seen a non-“Your graphics device has encountered a problem” CTD with all my add-ons installed on this PC since the very start of the beta cycle. This CTD seems out of place given this. Also, this was on first-load of the A310 since the update happened.

I was not able to replicate it on subsequent loads. As stated, it was on first-load and I’ve seen this before with the sim. Hopefully, the Fault Bucket can shed some light if any is needed to monitor it.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Select A310, select KLAX, select gate, no flight plan, click Fly

PC specs and/or peripheral set up:

i7-8750H / GTX 1060 Max Q / 32GB RAM / Samsung 970 EVO Plus 2TB / 1080p @ 60Hz

If on PC, Fault Bucket ID - Instructions here - Please type in just the Fault Bucket ID # rather than a screenshot for privacy reasons:

2094859389998662568, type 5

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

2

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes

Provide extra information to complete the original description of the issue:

Same symptoms: CTD on first load of the A310 @ KLAX after update, 2nd attempt is successful.
Crash info from event viewer:
Faulting application name: FlightSimulator.exe, version: 1.34.14.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000001fc50b01997
Faulting process id: 0x0x3CB4
Faulting application start time: 0x0x1D9E0EBC1585782
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: unknown
Report Id: 6e2483a2-49ed-4152-a9a9-8d3f9bddd449
Faulting package full name:
Faulting package-relative application ID:

If relevant, provide additional screenshots/video:

1 Like
3

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes

Provide extra information to complete the original description of the issue:

It occured only the first time and second try was ok.

If relevant, provide additional screenshots/video:

Faulting application name: FlightSimulator.exe, version: 1.34.14.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000122a4711997
Faulting process id: 0x0x4F38
Faulting application start time: 0x0x1D9E175625DA0A9
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.14.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: unknown
Report Id: 0cd59051-c65b-40b3-81dc-158eaba8caea
Faulting package full name: Microsoft.FlightSimulator_1.34.14.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

4

Do you have the same issue if you follow the OP’s steps to reproduce it?

Yes

Provide extra information to complete the original description of the issue:

For me happens in any airport after selecting A310.

Fault bucket 1605687384167450943, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0

Problem signature:
P1: Microsoft.FlightSimulator_1.34.14.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.34.14.0
P4: 00000000
P5: StackHash_2264
P6: 0.0.0.0
P7: 00000000
P8: c0000005
P9: PCH_0A_FROM_unknown+0x0000000000000000
P10:

If relevant, provide additional screenshots/video:

7

I wanted to add that after removing all Marketplace and Community folder content, except WUs, CUs, Top Gun & Red Bull, that the A310 CTD again on first load.

Prior to this change in installation configuration, I’d loaded the A310 numerous times without issue.

Hopefully, this bit of added information is helpful in understanding the bug.

EDIT:

Okay, this is really easily reproducible. I quit the sim, added a single add-on to the Community folder, launched the sim and tried to load into the A310 and it CTD.

8

Still crashing on 1.34.15.0

9

try load with default livery once. It will work, than switch with other livery it will work.

10

Strange. I only have default livery. But, CTD every first load.

11

Also CTD everytime first load of the sim, after that fine… It occurs every time before the Asobo splash screen if that’s any help.

12

Same. Loading the A310 into Inibuilds KJFK leads to immediate CTD after clicking Fly. Using Navigraph, if that makes a difference. Other planes fine. On PC