CTD's with Exception code: 0xc0000005 Fault offset: 0x000000000258a8a9 Faulting process ID: 0x32b4

I have been using REX while having CTD and now after rolling back Nvidia, for me, this was not the cause

1 Like

Oh good to hear and where did you roll it back to? Which driver because it happened again to me ctd?

That is a sad commentary on the state of things… :woozy_face:

Running the SU14 Beta has stopped the crashing for me so far, but I was unable to get Bing Maps to load in one instance, even after turning on and off online connections

Same here. After installing SU14 Beta no CTD !!

first CTD after 6~7 days with 537.13
typically “friday evening CTD” - I may say

Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000025f84a9
ID des fehlerhaften Prozesses: 0x0x4BC8

PA24 Commanche cruising at 3.500Ft over Austria

Fault bucket 1560424989613081798, type 5
Fault bucket 1275072019061138831, type 5
Fault bucket 1183966330537460714, type 4
Fault bucket 1283489453539676834, type 4
Fault bucket 1211189021504463169, type 5
Fault bucket 1724932380758412949, type 5
Fault bucket 1229029555288734682, type 4
Fault bucket 1416700587825189381, type 4
Fault bucket 1321017739356568306, type 5
Fault bucket 1175124532603933758, type 4

PS C:\WINDOWS\system32> Get-EventLog -LogName Application -Message “FlightSimulator.exe” -InstanceId 1000,1001

Index Time EntryType Source InstanceID Message


 239 Nov 18 13:20  Error       Application Error            1000 Faulting application name: FlightSimulator.exe,...
 234 Nov 18 12:46  Information Windows Error Rep...         1001 Fault bucket 1560424989613081798, type 5...
 233 Nov 18 12:46  Error       Application Error            1000 Faulting application name: FlightSimulator.exe,...
 189 Nov 18 07:49  Information Windows Error Rep...         1001 Fault bucket 1609472321302564091, type 5...

                  Get-EventLog -LogName Application -Message "*FlightSimulator.exe*" -InstanceId 1000,1001 | Select-Object Message | select-string "Exception code:*"

@{Message=Faulting application name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000002293a731997
Faulting process id: 0x0x3a4
Faulting application start time: 0x0x1da1a538292991d
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: unknown
Report Id: 83a53ff4-2f7c-4e37-89be-b9f45083c096
Faulting package full name: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App}
@{Message=Faulting application name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000023f9441
Faulting process id: 0x0x39fc
Faulting application start time: 0x0x1da1a4d304cb251

I have no idea what any of these fault buckets mean or how they can help me resolve any of my issues.

Tried again with nothing in community folder. launched game twice. first was successful and then on second load i got the CTD.

I have saved approximately 23 ctd reports. All drivers up to date. Even tried to roll back drivers but same result and then updated to latest and again same ctd’s. I’ve tried with and without 3rd party products in community folder in order to troubleshoot. same results with or without.

[Display]
DirectX version: 12.0
GPU processor: NVIDIA GeForce RTX 4090
Driver version: 546.17
Driver Type: DCH
Direct3D feature level: 12_1
CUDA Cores: 16384
Resizable BAR Yes
Core clock: 2520 MHz
Memory data rate: 21.00 Gbps
Memory interface: 384-bit
Memory bandwidth: 1.01 TB/s
Total available graphics memory: 56891 MB
Dedicated video memory: 24564 MB GDDR6X
System video memory: 0 MB
Shared system memory: 32327 MB
Video BIOS version: 95.02.3C.40.B5
IRQ: Not used
Bus: PCI Express x16 Gen4
Error Correction Code (ECC): Off
Device Id: 10DE 2684 88E31043
Part Number: G139 0332

1 Like

First CTD on 537.xx NVidia drivers with 0xc0000005 error on short final into EKCH yesterday. Makes me wonder if it’s related to AI traffic (FSLTL) or GSX.
Symptoms: complete slowdown/pause of visuals before CTD.
Second flight of sim session so maybe I just need to reboot FS before every flight. :roll_eyes:

I still keep getting CTD’s, even with mostly everything turned off internally in MSFS and external. Sometimes I can complete a flight sometimes not. First I tried the traffic thing and thought that it was it but it isn’t. Outdated scenery definitely is a side issue, wondering if something changed that makes old scenerie more likely to cause CTD…
I am running out of ideas what is causing this. It only started for me SU13. Hopefully the new SU14 will change somethihg

still trouble shooting. tried nvidia driver 537.42 and crash on launch.
Fault bucket 1620466250668328567, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 1448516336341827686

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

Faulting application name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000001dba3341997
Faulting process id: 0x0x4038
Faulting application start time: 0x0x1DA1B125F3B0CDF
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: unknown
Report Id: 0a7c64d6-d935-4997-8949-e5b63a6da1d8
Faulting package full name: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

running out of ideas. at this point the game is unplayable…lol of course it is since it will not even launch now. lol

As stated in previous post ive tried reinstall now 3 times of msfs and a complete windows reinstall. i hope the devs see this as most of these posts have merged.

all i wanna do is fly and enjoy the sim but they have made this impossible. extremely frustrating!

was able to launch into a generic c152 at klvk, then switched to a be36 at ktyr, then loaded th iniA310 at kafw and CTD:

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

Problem signature:
P1: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.34.16.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.34.16.0
P7: 00000000
P8: c0000005
P9: 00000000023f9441
P10:

Faulting application name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000023f9441
Faulting process id: 0x0xFCC
Faulting application start time: 0x0x1DA1B14A86C7D84
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 21018eff-dc8c-48e0-8bc6-faa998b6cfee
Faulting package full name: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

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

Problem signature:
P1: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.34.16.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.34.16.0
P7: 00000000
P8: c0000005
P9: 000000000296d9f0
P10:

Faulting application name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.34.16.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000000296d9f0
Faulting process id: 0x0xAF0
Faulting application start time: 0x0x1DA1B396F7B842B
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 89fcf7ba-ff25-4fac-8adc-ecc012113e7a
Faulting package full name: Microsoft.FlightSimulator_1.34.16.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

This one crashed while zooming in on map to select departure airport

at least your making it in game. i crash on loading now. don’t think it fsltl or gsx as i’ve removed those and still multiple crashes.

will the ingame crash reports help here? i’ve saved those as well.

Have you run a windows system file checker. (DISM/SFC) on your o/s.
I run this like every month or so. After latest crash i noticed some errors running this and they are now fixed.
Windows updates seem to somehow need checked and fixed to make them “as new” when compared to an image of how they should be.
Worth running it every so often. Its how I keep windows ticking along and FS more stable.

I crashed also now, sunday evening CTD I might say … :slight_smile:

Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000025f84a9
ID des fehlerhaften Prozesses: 0x0xEAC

cant wait for SU14

PS C:\WINDOWS\system32> DISM.exe /Online /Cleanup-image /Restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.22621.1

Image Version: 10.0.22631.2715

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

PS C:\WINDOWS\system32> sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
PS C:\WINDOWS\system32>

I’ve run these before. always no issues.

1 Like

Why should we think SU14 will fix these issues? hope this doesn’t come across the wrong why just curious if there is talk of a fix with SU14. I’ve heard SU14 has cause way more issues in beta.

I’ve done what customer support suggested here several clean installs and still same CTD’s

Had a couple myself since this week. Didn’t have them in months. Haven’t been in the SU14 beta yet.

customer support only can suggest “clean simulator”… Problem is, this issue is caused by the sim itself from what i understand.

SU14 probably can fix it, as this one is tragged as bug-logged.