DVA7816
Captain, MD-88
Joined on October 11 2009
50 State Club
Double Century Club
Wahiawa, HI USA
263 legs, 477.3 hours
43 legs,
75.8 hours online
259 legs,
471.3 hours ACARS
9 legs,
25.6 hours event
|
Posted onPost created on
March 07 2010 13:44 ET by Justin Beavers
|
DVA2564
Captain, MD-88
Joined on September 09 2005
Triple Century Club
Online Triple Century Club
Knoxville, TN USA
386 legs, 832.1 hours
361 legs,
767.2 hours online
379 legs,
801.0 hours ACARS
4 legs,
8.1 hours event
0 legs dispatched, 13.6
hours
|
Posted onPost created on
March 09 2010 08:50 ET by Terry Kocher
|
If I recall correctly this has happened to me in the past..not entirely sure what I did that fixed the problem. Since FS doesn't like to give error codes with this message you can't really pinpoint the problem easily. There are a number of things I would suggest doing.
-in no particular order, just which comes to mind first-
1. Restart your computer (when in doubt reboot..)
2 End any background programs that aren't necessary from the startup queue, this could very well be a issue with computer memory. Background programs and processes will leech away at available memory, which may cause your FS to terminate with no warning.
3. Run the Disk Clean-up program that comes with Windows followed by the Disk Defragmenter, then reboot and try again.
4. Perform a registry cleanup using a certified registry cleaner. (Unless you know what you are doing, never attempt to modify the registry by hand. This can kill your computer in a heartbeat)
4. Uninstall FSPassengersX and attempt to fly a flight, if the problem goes away - then it is an issue with FsPax, I'd contact customer support. If the problem still exists after the uninstall then it is very likely it is an internal computer problem.
5. Run a full system scan using whatever Anti-virus, anti-malware program you have in SAFE mode. I have found that running anti-virus scans in SAFE mode are the most effective way of removing them. Since this is a 'fatal error' with no code or other information, you can't rule out a virus.
... thats all I could come up with just brain storming.. you should also try doing a search on the FSPax officials forums for this problem, somebody may have had the same issue with FSPax.
Let me know how things turn out, good luck.
|
