FSX fatal error

[SSI01]

I've checked the forum's previous posts for this but can't seem to find anything germane, so here goes.

This evening I was conducting an unevent flight (the best kind) from KSSI to TriCities Regional in E. TN. I was running into cloudy weather that would have necessitated an ILS approach to the APT. After creating a flight plan from and to the two mentioned airports, I entered this plan and did not elect to have the aircraft returned to KSSI but rather to remain at its current location (near TriCities Reg). I was able to pick up approach instructions from GCI and to get in about four minutes of additional flight before I received a "fatal error" message, followed by the dialog box stating FSX had to shut down.

I was able to get into my event log but wasn't able to determine anything happened at the rough time of this incident. I did note a number of red/white "X" marks next to FS9 on past occasions when similar events occurred; nothing was shown for FSX, however, now and then a "userenv" entry is shown as having one of these "X" marks next to it as well.

I don't have the settings for FSX maxed out, and in every other instance of flying in clear weather, or even in cloudy weather I have not had problems with FSX; sometimes FS9 will continue to show an aircraft in flight but "greyed-out," which tells me the video card (?) may be loaded to the max to process the cloudscape. At least, that's all I can figure. I've experienced no such incidents with FSX.

Is there some method of determining what is causing this problem, and is there some cross-applicability for a fix between the two sims?

Thanks!

[mirage3]

I think you must download an "error reader" or search to refind a error.txt (which explains what's happened and find the error following the codes into the PC) but i am not sure.... the best thing is you ask a PC specialist...

PS: fatal errors happens me sometimes when i run too many processes at the same time... in that case, forget about to refind your flightplan and all setting who you make before, when you don't saved it....:(

[Dumonceau]

I've checked the forum's previous posts for this but can't seem to find anything germane, so here goes.

This evening I was conducting an unevent flight (the best kind) from KSSI to TriCities Regional in E. TN. I was running into cloudy weather that would have necessitated an ILS approach to the APT. After creating a flight plan from and to the two mentioned airports, I entered this plan and did not elect to have the aircraft returned to KSSI but rather to remain at its current location (near TriCities Reg). I was able to pick up approach instructions from GCI and to get in about four minutes of additional flight before I received a "fatal error" message, followed by the dialog box stating FSX had to shut down.

I was able to get into my event log but wasn't able to determine anything happened at the rough time of this incident. I did note a number of red/white "X" marks next to FS9 on past occasions when similar events occurred; nothing was shown for FSX, however, now and then a "userenv" entry is shown as having one of these "X" marks next to it as well.

I don't have the settings for FSX maxed out, and in every other instance of flying in clear weather, or even in cloudy weather I have not had problems with FSX; sometimes FS9 will continue to show an aircraft in flight but "greyed-out," which tells me the video card (?) may be loaded to the max to process the cloudscape. At least, that's all I can figure. I've experienced no such incidents with FSX.

Is there some method of determining what is causing this problem, and is there some cross-applicability for a fix between the two sims?

Thanks!

What OS are you running? You might want to look into the windows eventviewr.

If you have windows 7, go to the start menu and type eventvwr.

You should be looking at "administrative events" in the custom views and in the application and system views.

If you post the errors you see there, most people here should be able to help.

Dumonceau

[stansdds]

That's a long flight and FSX sometimes has problems with long flights. FSX is not particularly good at managing its memory (Virtual Address Space) and on a long flight it is easy to run out of VAS. Oh, you may have 4, 6, 8, 64GB of RAM, but FSX is a 32 bit program and can only use a maximum of 4GB VAS. FSX tends to not tidy up after itself, so your departure airport and all of the scenery, or at least parts of it, that you have flown past are still residing within that 4GB of VAS. Turning down autogen, mesh, and scenery complexity help as does eliminating add-on airports and scenery that are neither your departure nor arrival points. Some people have even saved a flight shortly before arriving at their destination, close FSX to clean up the memory, then restart FSX and continue the flight. That's a reality breaker for sure, but that is what some have resorted to doing just to avoid the fatal error crash.

[SSI01]

Thanks to all who've replied. I've reviewed every post.

The idea of running too many processes at once comes to mind. I have GameBooster 3 on my computer and will duplicate the flight but with GB3 on, to see if it makes a difference.

If memory serves somewhere I've seen FSX tends to be a "messy" program. Too bad there isn't a patch for this, you'd think MS would have noted this and released something to alleviate this problem. It would seem in the meantime we're left to unchecking all scenery areas we're not flying in to see if that helps.

Since I can't read the earlier posts while preparing this reply, I'll take a chance and say I was flying the Basler BT-67 in this little hop, and had already made a landing and take-off en route prior to this incident.

If there is another incident like this, I'll go into admin. tools, find the error log, make a copy and post to see what is causing this little issue.

So - the game plan is:
1) fly with GB3 on to see if that works.
2) if that doesn't work, uncheck any scenery areas we are not flying over.
3) if neither of the above work, make a copy of the error log if neither of the above helps on long flights, and see what we can see based on this log.

Again, many thanks to all.

[mirage3]

I'll take a chance and say I was flying the Basler BT-67 in this little hop.


Ok, this is a first explanation....:(:D
The BT-67 made me many crashes until i changed PC with a 4GHz and 16GB RAM DDR4.....