Does this event log give anyone information regarding my constant CTDs?

Community Support Tech Support
1

I’m on Update 12 beta and sometime over the last 10 days or so I am constantly getting a CTD when it has been stable for so long. I just updated to Nvidia 531.29 from 531.18 but still CTD. I was on 528.24 previously and had no CTDs for months so I switched back to it but still getting CTDs. I’ve tried booting in Safe Mode after a crash to disable all my add-ons but it still crashes. I have been flying one route over the last 10 days just to avoid adding in any other variables. I am trying to fly from 1O2 to KMOD using my Carenado M20R Ovation except when I boot to Safe Mode where I choose the G36. I am flying in VR with my G2 using a 3080ti and I9 9900K with 64GB ddr4 Ram. It’s like clockwork. Things will be going nice and smooth with minimal to no stutters then when I get to 30-40 minutes into the flight my VR screen goes black, the sound makes a couple stutters then shuts off, I take my headset off and see my screen is frozen in the VR view and then finally after a minute or so MSFS exits taking me back to desktop. I pulled up the event log when it happened but I’m not seeing anything that helps so I’m wondering if someone else might see something in it?

Log Name: Application
Source: Application Error
Date: 3/17/2023 9:10:47 PM
Event ID: 1000
Task Category: Application Crashing Events
Level: Error
Keywords:
User: OFFICE\Robert
Computer: Office
Description:
Faulting application name: FlightSimulator.exe, version: 1.31.22.0, time stamp: 0x6409dda0
Faulting module name: FlightSimulator.exe, version: 1.31.22.0, time stamp: 0x6409dda0
Exception code: 0xc0000005
Fault offset: 0x0000000001ee23aa
Faulting process id: 0x0x5D18
Faulting application start time: 0x0x1D95949CEA58282
Faulting application path: F:\SteamLibrary\steamapps\common\Chucky\FlightSimulator.exe
Faulting module path: F:\SteamLibrary\steamapps\common\Chucky\FlightSimulator.exe
Report Id: 8171533f-1db0-4b94-b1c5-aa509c562bc1
Faulting package full name:
Faulting package-relative application ID:
Event Xml:



1000
0
2
100
0
0x8000000000000000

981


Application
Office



FlightSimulator.exe
1.31.22.0
6409dda0
FlightSimulator.exe
1.31.22.0
6409dda0
c0000005
0000000001ee23aa
0x5d18
0x1d95949cea58282
F:\SteamLibrary\steamapps\common\Chucky\FlightSimulator.exe
F:\SteamLibrary\steamapps\common\Chucky\FlightSimulator.exe
8171533f-1db0-4b94-b1c5-aa509c562bc1





2

Google search for that fault code

The exception code 0xc0000005 may occur due to a corrupted or faulty hard drive .
https://www.google.com/search?q=exception+code+0xc0000005&rlz=1C1YTUH_enUS1002US1002&oq=exception+code+0xc0000005&aqs=chrome..69i57j0i546l5.11140j0j7&sourceid=chrome&ie=UTF-8

3

Reports on reddit, people are saying 531.29 is problematic too…roll back to your last stable nvidia driver

4

Thank you, that gave me a direction to go. I didn’t realize that 0xc0000005 was the actual fault code. I was thinking it was the Event ID: 1000. Your link pointed to a possible memory issue so I looked at it as a possible hardware issue. I have a dedicated 1TB SSD for FS. I did remember that I recently changed my memory settings from the BIOS default speed of 2666 MHz to the 3600 MHz that my memory is rated for. When I pulled one of my memory chips out to get the timing information to verify that I was running at the right timings, I noticed that I had not blew the dust out of my PC for too long. I blew out a huge dust bowl and left my memory at the rated speed of 3600 MHz. When I started up MSFS 2020 (I was on beta 12) it had a beta update of around 580 MB that it downloaded. I haven’t had a CTD for a week now. I suspect it was probably because I blew the dust out since that made more sense with my CTD happening 20-40 minutes into a flight. It’s possible that it was the beta update that fixed it but I doubt it.

1 Like