• Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning old domain name stealing credentials

  • Special Server Maintenance

    Just when you think you have everything running some what better...

    You get a message from the Hosting company. Short story they need to move us to a new server. I have been working with them to plan a good date for all concerned. Here is what we have come up with as a schedule.

    1. November 4th 17:00 -5UTC shut off the forums and start backup proceedures. During this time there will be no access to the forums or the Resource Section.
    2. November 5th Continue with Backups and download same until complete.
    3. November 6th 7:00 turn over server to hosting company to move system to new server
    4. November 7th - 8th restore backups and upgrade forum software.

    If all goes well we should be back online on November 8th.

    To keep you updated we will post updates on AVSIM forums.

    Thank you for your support.

Strange Anomaly

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,
 
Back
Top