November 1, 20223 yr FSX steam edition which i bought recently have been crashing always randomly. Sometimes i can do 2 hour long flight session and sometimes when i takeoff it crashes. Tried Uiautomatoncore from windows directory, didnt work, tried renaming logbook, didnt work, tried lowering graphics, didnt work, administrator mode, didnt work. My system specs are: CPU:Intel(R) Celeron(R) CPU G3900T @ 2.60GHz 2.59 GHz RAM: 4gb (if the specs are unclear, i just looked in the system tab) And also in appcrash view and windows event viewer i cant see the fsx crash.. Edited November 1, 20223 yr by AnySajmon
January 4, 20233 yr Author I am 14yo, deeply addicted to playing flight simulators. Problem is, i have low-end pc... My specs are: (Taken from windows system tab, if unclear ask further more in comments) Intel(R) Celeron(R) CPU G3900T @ 2.60GHz 2.59 GHz 4GB Ram FSX has on my computer one problem. It keeps crashing almost always after i takeoff, no matter where. I heard that fsx is low specs so i left the settings tab on high and it runs pretty smooth-(30-60 fps). If anybody has any fixes or, any tips, please write it down in the comments. FSX is the only Flight Simulator i can have to enjoy flight simulators, because i can not run almost any flight simulator.
January 4, 20233 yr Administrators I have merged this topic into your oldest post in the crash to desktop forum! DO NOT START ANY NEWER TOPICS on this problem. You need to go into your System erro logs to see what the faulting module is. That will give a hint as to what is causing your CTDs. Control Panel-> Administrative Tools-> Event Viewer, select Custom Views-> Administrative Events. One of the listed events will be for your CTD. The "Faulting Module" should point to the problem area. Tell us what the Faulting Module is! That will point us in the direction of the proper error, aiding in troubleshooting. BELOW IS A SAMPLE OF WHAT YOU MIGHT SEE! General Tab: Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14 Faulting module name: This is what we need to Know! Exception code: 0xc0000005 Fault offset: 0x0000ee3a Faulting process id: 0x748 Faulting application start time: 0x01ce0253dc4b69d4 Faulting application path: R:\FSX\fsx.exe Faulting module path: R:\FSX\window.dll Report Id: 9caf77b4-6e50-11e2-8570-3085a99825d1 If there is not one listed: Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000, you will need to do as previously noted No Faulting Module? -> Remove all of the add-ons, and test the sim. If it works OK, then reinstall them one at a time and test. Be sure to test each thoroughly before moving on to the next Charlie AronAVSIM Board of Directors-ADMIN/Moderator-RegistrarJust going to run a Chromebook and not upgrade to a Windows computer. Too many problems with the new Sims! 😱Trying to keep peace and harmony and the will of Landru on the site seems to be a full time job!
Archived
This topic is now archived and is closed to further replies.