Event ID 1000 - How to debug

W

WebMaximus

Contributor
Joined
Sep 26, 2018
Posts
32
I have an issue I could really need some help with.

I spend a lot of time in Microsoft Flight Simulator but lately, it keeps crashing to the desktop with no error message. Looking in the Windows Event Viewer Application log, it's always the same error caused by the same module. In this case flightsimulator.exe

Sometimes it will crash already after 15-30 minutes, someone I can fly for longer. On rare occasions, I mange to fly from A to B without a crash.

I'm far from the only one having this problem. Doing a simple Google search gives you loads of hits. I've been wading through all of these and trying more things than I can recall. All to no avail.

Reaching out to Asobo who is the developer is pointless. They will respond with a standard message, listing a number of things I already tried and if none of these work, they will suggest a complete reinstall of MSFS and/or Windows. Since I have spent a lot of time setting everything up the way I like it with my controllers for MSFS etc, I would like to avoid that route for as long as possible.

So, with this said, I figured there must be some way to properly debug this issue. To learn what is the actual culprit, resulting in these CTDs.

This is my system specs:

Case: Corsair Obsidian 500D RGB SE
Board: MSI MAG Z690 Tomahawk WIFI DDR4 - Bios: 1.90
PSU: Corsair HX1000i
CPU: Intel Core i9 13900K
GPU: MSI GeForce RTX 4090 SUPRIM X
MEM: Corsair Vengeance RGB 3200MHz CL16 4x8 GB
HDD: 1 x Samsung 970 Evo Plus 2 TB, 1 x Samsung 970 Evo Plus 1 TB, 1 x Seagate IronWolf 10 TB, 1 x Western Digital Red 4 TB
CPU Cooler: Corsair iCUE H150i Elite LCD (Front mounted as intake)
Fans: 2x140 mm Corsair ML140 RGB Elite (top exhaust), 1x120 Corsair ML120 RGB Elite (rear exhaust)
HMD: Varjo Aero
OS: Microsoft Windows 11 Pro 64-bit (10.0, Build 22621)

This is the Event ID 1000 in the Application log I get whenever these crashes occur:

Code: 
Faulting application name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.29.30.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000001543e15
Faulting process id: 0x0x5564
Faulting application start time: 0x0x1D92A4FCA7A0C19
Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
Report Id: 2d03fe3a-8089-4491-ab7a-57136d098105
Faulting package full name: Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Followed by this 1001 event:

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


Problem signature:
P1: Microsoft.FlightSimulator_1.29.30.0_x64__8wekyb3d8bbwe
P2: praid:App
P3: 1.29.30.0
P4: 00000000
P5: FlightSimulator.exe
P6: 1.29.30.0
P7: 00000000
P8: c0000005
P9: 0000000001543e15
P10:


Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.25f7037f-8a0b-47a3-b16b-95475a9e602b.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.4ae22f07-4219-45c9-8477-1e41c5341ba4.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.bc1e987a-bde2-46ec-bb27-c03f15b4cc3a.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.69771451-47df-4be2-9b97-c52c629d5e34.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.9b0ff414-a7a1-45c6-858c-1d1e0bfcf528.tmp.xml


These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Microsoft.Flight_3919da12fa35f5ae2edab484a1724d93bdef9b4a_c45ef8e0_f5ae3317-d0f6-40d2-95db-7ed0d77d4820


Analysis symbol:
Rechecking for solution: 0
Report Id: 2d03fe3a-8089-4491-ab7a-57136d098105
Report Status: 268435456
Hashed bucket: 2c1eac22ed88c8f4e394deb474b453c9
Cab Guid: 0

If someone in here could help me find what is actually triggering these crashes, I would be forever grateful!
 
Thanks, already tried the majority of tips listed in that link. Plus a multitude of other things suggested elsewhere.

What I'm really looking for now isn't more tips of things to try. Rather some tool or method to find out what is actually going on behind the scenes in my system when these crashes occur.

Was hoping a forum such as this one could be the place to find the knowledge and/or tools to achieve this.
 
Have you checked the Event Viewer? BTW, if it was perfect in Windows 10, then it's pretty obvious where the problem lies.
 
Corday is simply trying to help. Showing gratitude instead of condescension would be a platform to try.
Have a checked the Event Viewer?! Did you read my initial post? Where do you think those detailed error messages come from?

Yes, it was mostly working fine in Windows 10. Which has also been the case in Windows 11. So not as simple and obvious as that I'm afraid.

Again, was hoping this would have been the place to find some real skills. I know it has been before but maybe that sadly no longer is the case.
 
Unfortunately you've discounted the option of reinstalling the app which is what "simmers" try first. I'm not sure, but you might be able to save your Profile so settings wouldn't be lost. Just a stab here, but FPS, either too high or low could be an issue. Your hardware is great, so no problem there.
 
Reason I'm not so keen on reinstalling MSFS or possible Windows as well is how I read about many people going through that hassle. Only to find they still have the same issue when finished. Meaning all time and effort wasted.

The thing with MSFS is these CTD issues have been going on for over 2 years when MSFS was first released. With lots of people affected. Not enough though since Asobo/MS clearly don't find it worth investing enough time and effort on their side to implement better error handling. Or even better, do whatever changes are required to make MSFS less prone to crashing.

So this is the real reason for my question in here. Would be so good being able to find the actual culprit. Rather than just shooing left and right and hoping you'll hit the target eventually. I'm confident there are tools which could do this and people with enough skill to know how to use these tools. You just need to find them. Or become one of them yourself I suppose.

Thanks anyway.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top