Since SU8, crashes during startup precisely right after checking for updates and the blue bar is ~90% filled. 100% reproducible and happens every time. Game suddenly loses audio and then closes. Can’t even load to the menu. Operating system continues to run after CTD. Have not used developer mode or made any changes.
Things I’ve tried:
Cleared the entire install drive and re-downloaded and reinstalled twice
Community folder empty
Cleared directX cache
DX 11/12
Normal/Safe mode makes no difference
Updated graphics drivers
Starting up with and without internet
Made sure it was installed language English version
Start program in administrator mode
Without any peripherals attached
Do not have firewall
Made exception in Windows Defender
I do not overclock and do not have issues with other software/games. I’ve lost track of how many ‘similar’ fixes and numerous other threads dating back to the release of the game and having no such luck. This has gone on for more than a month and apart from some magical update, I’m losing hope.
PC Specs:
AMD 5950x
64gb ram 3200mhz
1070ti
1000W PSU
Multimonitor
With and w/o VR
Peripherals include X56 HOTAS and Logitech rudder pedals.
Samsung Odyssey+ HMD
Error Logs:
Faulting application name: FlightSimulator.exe, version: 1.24.5.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.24.5.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000025145e7
Faulting process id: 0x4ef8
Faulting application start time: 0x01d8470a82f81f20
Faulting application path: G:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: G:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: e01460a8-8029-4f57-b3f2-9c70ead4bb08
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: FlightSimulator.exe, version: 1.24.5.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.24.5.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000025145e7
Faulting process id: 0x68e8
Faulting application start time: 0x01d847074c8c24c0
Faulting application path: G:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: G:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: c10cd73b-dae4-4e9e-a77c-c5e85898fccc
Faulting package full name:
Faulting package-relative application ID:
Faulting application name: FlightSimulator.exe, version: 1.24.5.0, time stamp: 0x00000000
Faulting module name: FlightSimulator.exe, version: 1.24.5.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000025145e7
Faulting process id: 0x173c
Faulting application start time: 0x01d846c7c38ca654
Faulting application path: G:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Faulting module path: G:\SteamLibrary\steamapps\common\MicrosoftFlightSimulator\FlightSimulator.exe
Report Id: b102f0cd-a145-4ebf-a6ed-f2200246b405
Faulting package full name:
Faulting package-relative application ID:
Same here. Except that the game crashes when the blue bar is at about 50%; goes silent than CTD. This is the same behavior displayed after the infamous SU5 release.
Maybe instrumenting the code and adding try/catch blocks would allow for more descriptive error messages.
Here is a link to the troubleshooter.
Hey thanks for the advice. That was one of the first things I tried nearly a month ago. Have followed it again multiple times hoping things have changed, but no luck.
Reproducible for a crash should mean that it can be reproduced on multiple computers in the exact same way. That said, as someone who has dealt with a ton of CTD issues, my only recourse and solution twice was to reset Windows. I did the type of reset that doesn’t delete your files but does uninstall programs. I’ll never know what caused my crashes, but from experience, crashing during loading is almost always an addon. I trust you’ve already tried removing all of them (including any installed by other programs.) Best of luck to you!
1 Like
Did you follow the links at the bottom of the article to the next versions of the troubleshooters?
Thanks for the insight, I will reset windows when I find the time. Sorry to hear you had tons of CTD issues.
I just tried those. Good news is that it Windows said it fixed some corrupt files. Bad news is that the CTD still happens at the exact same spot during loading. Will delve deeper when I get some time. Thanks for the clarification.
1 Like
Brand new build, same errors as you. tried everything, and I mean everything. 12900K Asus Rog Strix E z690 DDR5, G.Skill Trident Z5 RGB F5-6000U4040E16GX2-TZ5RS DDR5-6000 CL40-40-40-76 1.30v, 3090 FTW3, M.2 2TB Samsung Pro, Windows 11. with or without XMP enabled, no overclock, Asus MCE disabled.
GREAT NEWS! I updated to SU9 pre-release test today and it seemed to have magically fixed everything! I can finally run the game after a month! Give it a shot and I hope it works out for you too.
Can you link me to that download location, when i go to Sim Update 9 on the forum, there’s no link to the download, just all the fixes that the 1.25.4.0 has? Right now I’m running 1.24.5.0,
I got it from the steam launcher. There should be instructions on the launcher on how to download. Good luck.
1 Like
Non-Steam here… I had to join the insider program, reboot, then get the update from MS Store/Xbox app, crossing fingers, and thanks a ton!!! EDIT: No luck, Im on 1.25.5.0 , same thing but Faulting Module this time is the same as the faulting application name (FlightSimulator.exe). Exception Code: 0xc0000005
That is a generic code that doesn’t pin point anything unfortunately.
Did you follow the troubleshooter (I believe there are four of them) for CTD’s?
I sure did, i even ran tons of memory tests and nothing comes up with errors. EDIT: I let the RAM default to 4800 (which is what it will do if XMP is disabled) even though it’s 6000 DDR5, and I was able to fly a lot longer and multiple flights for about 20 min., then an application error popped up in middle of screen saying it couldn’t find referenced memory. So yea, better but no cigar. It did not crash to desktop but rather had that pop up window which was a crash of course. i called G.Skill and they said to test each memory stick separately, especially if Im running the clock speed at 4800. He said 4800 should run perfect for testing purposes. But anyway, back to the drawing board. EDIT2: I’m running mem86 memory test from BIOS on each stick separately in the A2 slot. EDIT3: Just ran mem86 tests on each stick individually, both PASSED. Perhaps I have corruption from all the CTD’s early in the fresh install process, but would that produce memory related crash exceptions? If so, I suppose I could just reinstall from scratch, but ugh, lot of time to do that, do you think I should?
1 Like
