CTD 0xc0000005 with handleSEH in external view

I’ve never used AI traffic So far I moved to 537.58 driver and it’s OK, but I need more tests.

1 Like

Hope it keeps that way !

Memory is not meant to be “not enough” but some error within the memory itself. Might be RAM or VRAM, that’s not really clear to me.

But what I understand, it’s the sim itself.

1 Like

Maybe this means absolutely nothing, but if I look at my latest crash reports (I collected some in the mean time) :joy: I always see a similar size count at: TexturesToDeleteTotalSize=

I saw some crash reports from other people on the internet with some similar number. Does this maybe means something? Is it some sort of cache that adds up while flying and then at some point it becomes too big and MSFS crashes?

Renderer:
EnableD3D12=No
PreferD3D12=No
Model=Nvidia
VR State=Active
VideoMemoryBudget=11912871936
TexturesToDeleteCount=24
TexturesToDeleteTotalSize=18446744069164496024

Some previous crash reports:
TexturesToDeleteTotalSize=18446744071408364000
TexturesToDeleteTotalSize=18446744070440609408

So never exactly the same amount, but always something close…

Next release soon, let’s cross fingers…

I was having this issue and one of the recommendations from the thread below to disable Bing Data World Graphics seems to have resolved it at the expense of terrible-looking scenery (thread also covers how to limit network adapter speeds and leave Bing Data World Graphics on). Might be something worth trying for anyone else roaming through here as it’s a pretty quick test.

Note that the workaround I provide in that thread (which modifies your network connection) is only applicable if you connect to your router via a LAN cable…

Has anyone who has had this 0xc0000005 issue, tried safe mode? I have the same problem and I’ve done 2 flights in the AAU2 747 it and it seems fine. Which has me suspicious.

EDIT: just crashed in safe mode. Great, I have no idea what it could be. Custom pagefile set. RAM was available so I don’t think ram is the issue. I just wish there was a proper crash report that told you what failed. Not that the exe crashed.

1 Like

[EDIT] I retract the original post as I just had another sim crash with this error, despite driver rollback and DX11/DX12 variation. This follows a series of 1hr+ duration flights performed as a test. However, this error is persisting again now (which I’ve never encountered before yesterday, 27 November 2023).

Original Post:

This might be driver-related, as this only seemed to occur after a driver update for NVIDIA (546.17) (2080Ti). Attempted in SU14 Beta and current production (SU13). Switching from DX12 to DX11 solved this for me personally, without any other changes.

1 Like

I have the same issue:

/!/ CRASH /!/
OnCrash:
Msg=_handleSEH
Type=SEH
Code=0xC0000005

I tried everything: other airplane, safe mode, increased vram, changing ram frequency, lowering graphic settings, limiting fps. Everything is up-to-date. Win11.
It is easy to reproduce I just spawn in JFK and drone around spin around the airplane with the camera and it crashes. Please help!

Same for me 18446744071924547584

I’ve updated to SU14 beta and no crashes since. Reverted to all my previous settings and most recent drivers after previously rolling them back. However, I am down on FPS compared to SU13…

You might be right, updated too, no crash so far. Will reply if it does. Thx for the tip.

just crashed on SU14 beta with FSS ejets… great, back to crashing.

This crash suddenly started happing to me since last friday… Before that it was months ago since the last CTD during flight… All seems very random. Hopefully the upcoming update will fix it.

I think I just had the same crash. Usually flying after 40 minutes or so as well. Albeit I was in the cockpit, not outside view.

/!/ CRASH /!/TOML
[OnCrash]
Msg="_handleSEH"
Type="SEH"
Code=0xC0000005
[Engine]
ReportVersion=9
UnscaledDeltaTimeMs=68.421104
TimeSpentRunningMs=6064228.658376
TimeSpentPauseOffMs=6061247.184472
TimeSpentTurnedOnMs=6061247.184472
ContextUID=0xFA3E276DEBC86DAD
MemInfoUID=0x1D3C5F55A25E58C9
DebuggerAllowed=false
AllocatedMem=7927955456
FrameCount=207222
BuildVersion="1.35.21.0"
IsMSIXVC=false
FreeOpenOpsCount-Main=1024
FreeOpenOpsCount-Thread=951
[Hardware]

Version=1
EventType=APPCRASH
EventTime=133461124812026765
ReportType=2
Consent=1
UploadTime=133461124818511574
ReportStatus=268435456
ReportIdentifier=0bba41a5-fc01-4226-b542-04a25d55d5d1
IntegratorReportIdentifier=f00e9185-73c6-43d4-aeaa-b2fcf17f07d2
Wow64Host=34404
NsAppName=FlightSimulator.exe
AppSessionGuid=000062a0-0001-0118-fe94-af071d26da01
TargetAppId=W:0006128ab6eee0c024248968b38e4897be5e00000c04!0000f18ff193c03338ba4163cd830922cdce2ca42cb4!FlightSimulator.exe
TargetAppVer=2023//11//30:14:05:57!0!FlightSimulator.exe
BootId=4294967295
TargetAsId=6217
UserImpactVector=808464656
IsFatal=1
EtwNonCollectReason=1
Response.BucketId=0d6ff8e681e46d3647da71a93d061c63
Response.BucketTable=4
Response.LegacyBucketId=1718811179482487907
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=FlightSimulator.exe
Sig[1].Name=Application Version
Sig[1].Value=1.35.21.0
Sig[2].Name=Application Timestamp
Sig[2].Value=656896c5
Sig[3].Name=Fault Module Name
Sig[3].Value=FlightSimulator.exe
Sig[4].Name=Fault Module Version
Sig[4].Value=1.35.21.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=656896c5
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00000000014cbaa9

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

Problem signature:
P1: FlightSimulator.exe
P2: 1.35.21.0
P3: 656896c5
P4: FlightSimulator.exe
P5: 1.35.21.0
P6: 656896c5
P7: c0000005
P8: 00000000014cbaa9
P9: 
P10:
1 Like

This is the new Beta version… not very promising

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

similar issue but the crash will happen in any view

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

around 30-40 minutes of flying (normally after reaching cruise) the time will crash to desktop. Happens mostly when flying the default 747-800I. Sometimes the crash will happen towards the end of my flight but mostly after 40 minutes of flying. My sim in vanilla state and crashes in normal and safe mode.

If relevant, provide additional screenshots/video:

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

I have the same issue after 30-40 minutes flight time. Sometimes 3-4 hours after departure or on approach.

Has anyone tried doing a clean uninstall and reinstall of flight simulator? I am in the middle of doing so now, just waiting for flight simulator to install again. I have completed many steps to try and fix this issue, such as reducing graphics settings, rolling back drivers, clean uninstall and install of all graphics drivers, restore sim to vanilla etc. I have performed a sfc scan, where my system actually found and repaired corrupt files, however this was not a fix. I have updated integrated graphics too (I know this is hardly used in flight sim) but just wanted to make sure. The crashes happen mostly with the 747-800 after 40 minutes. With the a320 and lighter aircraft occasionally towards the end of the flight. I am waiting to see if a clean install of flight sim could fix this issue and will update you all when I have tried this (hopefully end of today). If this does not work I may consider a f3 recovery procedure! For anyone wondering my system specs are…

11th GEN intel core™ I7 11800h @2.30GHz
Nvidia GeForce RTX 3070 laptop GPU 8GB (latest game ready driver)
16GB RAM