• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

Strange Anomaly

Stinger

Stinger

Charter Member
I'm having an issue with flying east of the Rockies, whenever i load and start my sim(FSX:ACC) the aircraft loads, then freezes up and crashes to desktop and restarts. It doesn't matter which aircraft i use. I tested with all and in other parts of the world which it doesn't created the same problem. Has anybody heard of this? For the life of me i don't know what's causing it. I thought it may have been ORBX causing the issue, but i deleted it and it still persists. Any Ideas why this is happening?
 
I'd look at the specific airplane you're loading for a possible missing gauge or sound dll error. Also if you are loading into an addon scenery it could be related to that. . .just a few considerations.
 
doesn't matter which A/C( payware or freeware default) i load, and i've tested it with just default scenery and also addon on scenery... it still does the same.... crashes to desktop right after the A/C loads
 
Hi,

Have a look in your Windows error log for more information. That will tell you which module is causing a CTD.

Look in Event Viewer/Windows Logs/Application

Double click on any entry that has the red exclamation mark and the word "Error". You can find the right entry by the date and time. If you know what time the CTD occurred, open the "Error" entry closest to that time.

Have a read through the Event properties and search for the words "Faulting module", and it should give you a clue why the CTD is occurring. It could be ATC, or weather or traffic, but finding the faulting module with event viewer and then investigating that module will get you closer to a solution.

Cheers,
 
just where might i find " Event Viewer/Windows Logs/Application"? I did a serch of my computer and didn't find it
 
In Windows 7 it is in your Start Menu program files list under "Administrative Tools". You should just be able to type "Event" in the Windows search bar in the start menu and Event Viewer should show up.

If you have a different version of Windows I'm afraid I can't offer any more help because I only have Windows 7.

If you do have Windows 10, it's possible you need to turn Event Viewer on. Just google "Event Viewer in Windows 10" and you will find plenty of info on it.

Cheers,
 
You must log in or register to reply here.
Back
Top