Is there a way to have FSX tell you what is causing a fatal error? I have recently been getting several of these and can't figure out what is causing them. I have most recently been flying in the great Orbx FTX PNW scenery. I have read in their forums of possible issues causing fatal errors, but all I get when this happens is the standard dialog box stating that a fatal error occurred, without any other explanation. Can FSX tell you what the problem is??

First, go to your Control Panel and then, assuming you have Windows 7, type in "event log" in the search bar. After that, you'll see "Administrative Tools" and under it, an option to view your event logs. Click on that and a new window should pop up. On the left hand pane, click on the arrow next to "Custom Views" to expand the "folder" and then click on "Administrative Events." Finally, you'll just have to look for FSX in the scroll menu through all the application errors. You'll eventually find one that has a faulting application name called "fsx.exe." Click on it once and you should find out all the details of the "fatal error" below the scroll menu.Hope this helps. It may not be 100% word for word, but you should be able to figure it out. If you need anymore help, tell me.

First, go to your Control Panel and then, assuming you have Windows 7, type in "event log" in the search bar. After that, you'll see "Administrative Tools" and under it, an option to view your event logs. Click on that and a new window should pop up. On the left hand pane, click on the arrow next to "Custom Views" to expand the "folder" and then click on "Administrative Events." Finally, you'll just have to look for FSX in the scroll menu through all the application errors. You'll eventually find one that has a faulting application name called "fsx.exe." Click on it once and you should find out all the details of the "fatal error" below the scroll menu.Hope this helps. It may not be 100% word for word, but you should be able to figure it out. If you need anymore help, tell me.

Thanks LtCarman. At least now I can see what the problems are. Seems to be a bad ntdll.dll file. I'll work on correcting that.