CTD with exception code 0xc0000005 Fault bucket 1945005070971162045, type 4

Sim Update 15 Beta CTDs
, ,
43

Same, 2 plus hours in

Faulting application name: FlightSimulator.exe, version: 1.37.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.37.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000002544c7e
Faulting process id: 0x0x3F90
Faulting application start time: 0x0x1DA60D0DF75E28C
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 5f908dfd-eee5-4789-aff1-8d4d7e15bba5
Faulting package full name: Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

44

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

Pretty much

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

Havent had a succesful flight out of 5

If relevant, provide additional screenshots/video:

image
image708×303 6.1 KB

45

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

CTD with same fault bucket as the OP on an unrelated flight.

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

Was cruising along 3500ft about 2/3 throught the second to last leg of the Hispaniola bush trip. Hardware is a RTX 4090 with the most recent nVidia driver and a AMD 5800x3D CPU.

If relevant, provide additional screenshots/video:

46

more of the same
image

Log Name: Application
Source: .NET Runtime
Date: 2/16/2024 6:08:22 PM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: desktop
Description:
Application: FlightSimulator.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF655E0A9CE

Event Xml:



1026
0
2
0
0
0x80000000000000

116901


Application
desktop



Application: FlightSimulator.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF655E0A9CE


47

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

No

Are you using Developer Mode or made changes in it?

No

Brief description of the issue:

Each flight, anywhere between 30 - 50 minutes the simulator will lock up for a few seconds and then CTD. Has happened in a variety of locations and with various addons.

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

Detailed steps to reproduce the issue encountered:

Seems to occur in a variety of locations with a variety of different aircraft, both 3rd party and MSFS (787)

PC specs and/or peripheral set up:

7950X3D, 64GB RAM, 4090

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

1945005070971162045, type 4

: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:

48

As I understand it, every time the sim crashes, it sends a crash report back to Microsoft. That creates a separate event. If you check the Event Viewer, you should see an event with “Level: Information” and “Event ID: 1001” around the time the crash occured (using default sorting, it should be just above the “Error” event), and that contains the Fault bucket ID they want.

If you search the forum for the Fault bucket ID, you might find other threads with users having the same issue.

49

So… no workaround yet, huh?

I don’t want to reinstall MSFS, but I also don’t want to stop flying until we get a new build… and there are people streaming SU15 on Twitch for hours without crashing. I wonder what we (the crash survivors) have in common.

50

Thanks for that - Just had another one…different part of the world, different airplane.

Thats enough of this BETA for me - The smoothness is great but to hell with having a CTD every flight. I’m going back to SU14

51

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:

Getting a CTD every flight since updating to SU15 Beta

If relevant, provide additional screenshots/video:

Fault Bucket: 1945005070971162045, type 4

52

I’m getting the same - a CTD anywhere between 20 - 120 minutes after the flight starts.

Happens at various parts of the world in various aircraft.

Fault bucket 1945005070971162045, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: FlightSimulator.exe
P2: 1.37.2.0
P3: 65c23c2b
P4: FlightSimulator.exe
P5: 1.37.2.0
P6: 65c23c2b
P7: c0000005
P8: 000000000253a9ce
P9:
P10:

53

Great diagnostics - Hopefully a fix comes with the next BETA update.

I’ve had four of these the past four flights. Same fault bucket. Never had CTD’s before and nothing changed in terms of addons betwen S14 and installing SU 15 Beta

54

I’ve just had this same CTD… CTD happened 6Hours 45mins into flight.

787 with the Horizon Simulations -9 Mod

EGLL-KJFK
EGLL/27R N0472F360 CPT3F CPT L9 DIDZA N14 OKTAD DCT MEDOG DCT VATRY DCT RESNO/M082F360 DCT 56N020W 57N030W 56N040W 54N050W DCT PELTU/N0476F360 DCT DANOL DCT ENE PARCH3 KJFK/04R

EVENT Viewer
Faulting application name: FlightSimulator.exe, version: 1.37.2.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.37.2.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000002544c7e
Faulting process ID: 0x0x567C
Faulting application start time: 0x0x1DA6120F9CB2C4F
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report ID: 6c953cbe-5fb5-4cd9-93cc-1a7a887fad23
Faulting package full name: Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

55

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

negatory, but see below

Are you using Developer Mode or made changes in it?

negatory

Brief description of the issue:

CTD while enroute over PNG

Detailed steps to reproduce the issue encountered:

n/a

PC specs and/or peripheral set up:

Ryzen 9, 4090, 64GB, Brunner CLS-E NG, CH pedals, Bravo, custom throttle quadrant, Valve Index

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

Fault bucket 1945005070971162045, type 4

All flights in the SWS Kodiak (G1000), live traffic, live weather, real time, online (all players) and in VR
Maybe relevant: I have a couple of SimConnect clients active on every flight: Little Navmap 3.0.2, FSUIPC 7.4.6, Brunner CLS2Sim 5.5.2

VFR WAJJ-AYKI, DX12
Report Id: 5e05dcc8-e608-412b-b7ff-c0de4090dc0f

IFR WAJJ IDIN1A ZX AYKI, DX12, result:
Report Id: 1efccde1-7dd4-4f25-a74f-8c0ad6873369

same route, removed most content from Community except fsuipc-lvar-module, navigraph-avionics-g1000, navigraph-navdata, navigraph-navdata-base, sws-aircraft-kodiak-wheell. DX12. Result:
Report Id: 095d2883-bd6a-489d-81b8-d44910369574

WAJJ VANK1A ZX AYKI, removed Navigraph as well, DX12, result:
Report Id: 4751eb1f-1d2b-4843-a359-d07d068e3f3a

WAJJ DCT ZX AYKI, DX11:
Report Id: 9804d042-f2c6-44f2-8fc9-3a1b45471371
On this flight, I only launched Little Navmap mid-flight, the CTD happened a few minutes later. Could be coincidence, ofc.

I lobotomized MSFS by setting all graphics settings to LOW, turning off all online functionality and disabling the rolling cache. MSFS CTD’ed before I could even start the flight, same bucket id as always.
Report Id: fe588029-ca08-425e-9576-9f3d1f58905e
After restarting the sim, I could start the flight, but halfway through, it CTD’ed:
Report Id: 47b6ab67-0bd4-42b0-955f-4494017d5180

: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:

58

CTD almost every time.

Name der fehlerhaften Anwendung: FlightSimulator.exe, Version: 1.37.2.0, Zeitstempel: 0x00000000
Name des fehlerhaften Moduls: FlightSimulator.exe, Version: 1.37.2.0, Zeitstempel: 0x00000000
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000002544c7e
ID des fehlerhaften Prozesses: 0x5464
Startzeit der fehlerhaften Anwendung: 0x01da60e4282c2427
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Pfad des fehlerhaften Moduls: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Berichtskennung: 7ade51f8-72be-469e-ab42-0a6b15fcdf7b
Vollständiger Name des fehlerhaften Pakets: Microsoft.FlightSimulator_1.37.2.0_x64__8wekyb3d8bbwe
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: App

59

I’m certainly getting more CTDs with this build at various times even during loading. Previously very few on the stable build.

Also several oddities (including an unresponsive dashboard requiring flight restart), which may be linked to the CTDs.

VR Quest 2
GTX 1080Ti
i9-12900
64Gb RAM

60

Adding:

Anwendung: FlightSimulator.exe
Frameworkversion: v4.0.30319
Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet.
Ausnahmeinformationen: Ausnahmecode c0000005, Ausnahmeadresse 00007FF663B94C7E

Reverting to SU14 now. Happens every flight after almost an hour.

61

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:

PMDG 737-700 (Marketplace version, PC, Steam). Two flights in a row one day apart. After cruising for about 2 hours, the game CTDs with the same errors (fault bucket 1945005070971162045, type 4, Exception code: 0xc0000005, Fault offset: 0x000000000253a9ce.
7800X3D and RTX 3080, 32GB RAM
CTDs did not occur before SU 15 beta.

If relevant, provide additional screenshots/video:

62

Back on SU14 (my first beta-to-release downgrade, it isn’t as painful as you think if you know what to keep). Someone let me know when the CTD has been fixed.

1 Like
63

Crashed loading in PMDG 737. Fault bucket 1851043371179210403, type 4

64

I’ve only been able to complete 2 flights out of 10 since installing beta SU15. Flights are from 10 minutes to an hour and half before the crash occurs. No crashes with the prior stable build.

I would post a crash log but the computer doesn’t even have a chance to record the fault. It’s just a sudden hard reset of the computer. Event log shows normal activity leading up to the crash and then the next event shown is windows starting. I’ve had CTDs with some earlier versions and event log entries, but never anything this severe.

Not using Developer mode and all mods disabled.

i7 6700K
GTX 1080Ti
Win 10.0.19045
32 GB ram
crashes occur with either DX11 or DX12

Follow up -

Two more flights approximately 10 minutes long before crash ended flight. For both instances, the same event log entry occurs. The most recent one says:

The previous system shutdown at 12:59:14 PM on ‎2/‎17/‎2024 was unexpected.

Very serious issue with this beta when it causes the system to crash so hard it can’t determine what caused the crash.