For example, and exception of 0x0000005, means FSX had a MEMORY_ACCESS_VIOLATION. 90% of crashes can be identifyed and solved with these.Įxception Code basically gives us a big clue on why it happened. This is the DLL that was loaded before the Application crashed. In each crash report, the information that is most important to troubleshoot are:įault Module Name is the self explanatory.

With that being said, lets get in with the trouble shooting! This program views the events in way more detail, giving you every single dll that was loaded up until your crash.

Than select 'Application', and select, and view the crash.Ī more efficient way to view your crashes are through a program called 'AppcrashView'. On the left column, choose 'Event Viewer'. Start > Right click on computer > Select 'manage'. There are several ways you can access this information, one gives you more basic information. With every event, problem, message, update etc, the Windows operating system records and logs every error that happens on your system. I know you just wanted to finish that flight, but what we have to do now is find the cause of the error, so we can make sure it won't happen again! Now, the most important thing to do, is not to panic. You press the button to switch views, and BAM! Your FSX freezes with a loading icon.

So let's picture you have been flying your favorite route in FSX for hours now, and you decide you want to view the exterior of the airplane. WIth all of us trying every day to improve FSX, I hope this topic will help new-comers understand why FSX is giving them crashes. With hundrens, and if not thousands of users posting topics here in the CTD forum every month about crash to desktop errors, I have decided to compile a list, and guide on the most common CTD errors, and why they happen.Įven though I became a member back in 2011, I have been reading this forum for quite awhile, and taking note of a-lot of crash to desktop errors, and have been learning about them ever since!

Windows 10 update kb2538242 repeating