December 30, 20232 yr two consecutive days after about 1 hour of flying (A32N FBW) i get a CTD below is from the event viewer any help appreciated Log Name: Application Source: Application Error Date: 12/30/2023 11:00:47 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: DESKTOP-T7LPU5E Description: Faulting application name: FlightSimulator.exe, version: 1.35.21.0, time stamp: 0x00000000 Faulting module name: FlightSimulator.exe, version: 1.35.21.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x000000000024e834 Faulting process id: 0x2b10 Faulting application start time: 0x01da3aa7d9906eae Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report Id: db804948-baf9-4ac0-8d01-03948d24c59a Faulting package full name: Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2023-12-30T00:00:47.6770488Z" /> <EventRecordID>55427</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>DESKTOP-T7LPU5E</Computer> <Security /> </System> <EventData> <Data>FlightSimulator.exe</Data> <Data>1.35.21.0</Data> <Data>00000000</Data> <Data>FlightSimulator.exe</Data> <Data>1.35.21.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>000000000024e834</Data> <Data>2b10</Data> <Data>01da3aa7d9906eae</Data> <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data> <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data> <Data>db804948-baf9-4ac0-8d01-03948d24c59a</Data> <Data>Microsoft.FlightSimulator_1.35.21.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event> Richard Mawkes Intel Core i7 7700 4.2GHz, , Kingston Hyper Fury Black 16GB 2400MHz DDR4 Asus Geforce GTX 1070 8GB Dual Fan edition
December 30, 20232 yr Well where to start? First, ask yourself (very honestly) what you recently changed in your environment. Any new driver, plane, livery, tool, mod, update etc? Then revert it and check again. Eg try with an empty community folder. Also, does it only happen with the FBW? Did you try any other (default) plane. Do the CTDs then happen again? If not then delete and reinstall the FBW, or try the stable version. all above are just a mere start to circle your problem. No success guaranteed Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
January 1, 20242 yr I'm finding it to be a pain as well. I never had any problems with the sim until the most recent update, now it crashes all the time. The difference is for me I don't get CTDs but the program locks up solid. Just happened as I was flying from Burbank to San Francisco. using all default scenery in a default aircraft.
January 1, 20242 yr Always worth trying for those dreaded 0x00000005 errors:https://forums.flightsimulator.com/t/ctd-fix-info/471880 For transparency: I'm a community mentor at the BATC discord. However, I do not get paid for it in any way.
January 4, 20242 yr But in my case at least, the error causing CTDs is 0x887a0006, which, based on what I have read, seems to be fairly common. I do find that running MSFS as administrator helps reduce the frequency of CTDs but does not really cure the problem. I think that this is not a Windows problem -- it started with SU13 for me.
Archived
This topic is now archived and is closed to further replies.