Fatal Error

[OldAirmail]

D28-HD, you're telling us that you have a new system with a new clean OS & FSX install.

That tells me that your problem is probably hardware related.

Even if everything is brand new and unused, factories do produce bad parts from time to time.



You can do this 2 ways. Pay someone to fix it. Or download free programs that will test the hard drive, memory, etc.

Obviously, the best choice would be to learn how to do it yourself.

But we all have out plusses and minuses. I can't do everything that I would like to do, and you're probably the same.

So learn or pay. Those are the options.

[HarrytMJ66]

Getting the fatal error on long flights E.G Heathrow-Edinburgh as i was doing this morning but on shorter flights its fine.
Will try turning down the settings in graphics and report back

[OldAirmail]

"Getting the fatal error on long flights..."

"long flights" just doesn't cut it. Giving a set of temperatures, CPU & GPU, in particular would be best. Even saying it poops out after 20 continues minutes would be of some help.



But at the very least GIVE US SOMETHING MORE ACCURATE TIME THAN "long flights".



Download HWMonitor from CPUid.

[/quote]

Keep it running as you fly. When you have your problem do a screen capture (search on the internet for screen capture and pick out whatever program you like, or just use the PrtScn button).

Just don't tell us that it happens after "long flights".

[Bubblehead]

I've always had my settings around the mid level with Autogen at "Dense". I don't have any problems with any Fatal Error when just flying around airports in any kind of plane. However when flying from different airports after several minutes during the flight, then I often experience the Fatal Error. For example, flights from SAN to LAX using default B737-800 I never reach my destination without Fatal Error. i tried it with the CRJ700, still the same problem. So what the heck, I moved all my settings to max, unlimited FPS, Autogen at Extremely Dense, etc. and guess what, I did the same flights with the same aircraft and did not experience any Fatal Error. I tried it with longer flights, SAN to SFO, no problem, I tried it from Hongkong to Manila flying AB380, no Fatal Error. I tried flying around several airports local and overseas, flying various type aircraft including performance fighter jets, no problem. I'm not saying this is a quick and permanent fix but if it works I'm happy. I don't have the most powerful rig so it couldn't be hardware. I also may have occasional Fatal Error problems in other flights but for the moment I'll leave it where it is. Any practical or logical explanation about my experience?

[Bass]

If there is anyone who can explain the mystories going on in windows and their own products, i would be glad to shake his/her hand

[garymbuska]

For starters if this was a heat related issue it would not cause this kind of a error message. At worst the computer would shut it self down as the power supply is protected and would shut down if it over heated. You may or may not get a warning message.
Same thing apply,s to the video card if it over heats it will usually just shut down but not always depends on the manufacturer.
As one post stated the quick way to find out what happened is to check your event log
Open the control panel and select Administration Tools then click on event viewer
Entries are listed by date and time.

[OldAirmail]

Hardware failures aren't necessarily like a light switch, on or off.

Back in the mid '90s I was having some odd, intermittent, problems with my computer and had no clue what it was at the time.

That is until some capacitors in the power supply literally blew their tops. The motherboard & hard drive went with it.

There were signs. I just didn't understand them.



This is like someone on the other side of the world, who keeps saying "I don't feel so well".

"What's the problem Mikey?"

"I don't feel so well."



"I think that it's an upset stomach."

"No, I think that it's a heart attach."

"Well, I think it's the flu."

"Hay, no, I saw this on TV, he's got a cold."

"You're all wrong. That's the first symptom of Beriberi."



"I don't feel so well."



All that we know is that there's a problem, an "error". It happens "sometimes", under "some conditions", not not always.

Until you can reliably reproduce the problem it will be very hard to diagnose.

And if you can't reliably reproduce the problem, run some diagnostic software. Start with memory. Start with temperatures. Start with System File Checker. START SOMEWHERE!

free windows troubleshooting software

[D28-HB]

after days of frustration I downloaded at Beta version Video drive from AMD, FSX came to life but with some graphic issue over water, ran repair mode from disc, BANG all is well.....no more stalls stutters hangups, running steady 25 FPS over Miami and large traffic areas, have UTUSA< CAN< ALASKA< all sliders full, Also running FSWP water config. I think this is the way the program was supposed to run...also tweaked fsx config.

[OldAirmail]

after days of frustration

....

I know it too well.

Good job, there.

good luck.

[garymbuska]

I am glad to see you got it working. Things like this can drive one nuts

[Bubblehead]

As the famous saying goes " If you like FSX you can keep it".

[OldAirmail]

Did Obama say that?