• 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.

CTD trouble

dhasdell

dhasdell

SOH-CM-2023
Recently after about 30-40 minutes of FSX I am getting a CTD with an "FSX has stopped working" message, followed by "FSX is restarting". This happens with an assortment of a/c in an assortment of places and stages of flight. It doesn't occur with any other program, but I think FSX is the most graphics intensive. Does this sound like a dying video card?
 
When it happens independent of where and what you are flying, the answer is yes.....

It might also be a cooling/heat problem. You could try whether it improves when you take a cover from your PC.
 
I might add to blow out the dust with a compressed air container. This should be done on a regular basis. Heat is number one for computer trouble and damage.
 
dhasdell said:
Recently after about 30-40 minutes of FSX I am getting a CTD with an "FSX has stopped working" message, followed by "FSX is restarting". This happens with an assortment of a/c in an assortment of places and stages of flight. It doesn't occur with any other program, but I think FSX is the most graphics intensive. Does this sound like a dying video card?
Click to expand...

Could you give us the specs of your rig please? Not just the hardware, but also the OS and other programs installed. And - last but not least - the number of services/processes you have running after booting up.

If you're running windows 7, type "eventvwr" in the search or run fields of the start menu and look for anomalies that occurred at the time your rig CTD'd. That would give a good indication of what and where things are clogging up.
 
Thank you. The interior is pretty clean, but I am now trying running it outside the kneehole in the desk and with the side removed.

System: i7-2600 CPU @ 3.40 GHz, 6.00Gb RAM, Windows 7 64bit
Windows Experience Index shows 4.5, the lowest score being the graphics @ 4.5
Graphics card AMD Radeon HD 6470M, which I realise is a bit low level, and which has a heat sink and no fan, but this is a recent problem

Processes:

View attachment 88952
Goodness knows what AICarriers is doing there, as it shouldn't be running.
 
Control Panel-> Administrative Tools-> Event Viewer, select Custom Views-> Administrative Events.
One of the latest listed events in the "Source" column will be for your CTD. Find, and select it.

On the general tab will be a breakdown of the failure. The "Faulting Module", if any, should give a clue as to what to look for...Don
 
dhasdell said:
No, neither in modules nor root directory. Do I want it? I do have ui.dll in the main directory.
Click to expand...

I Believe it should be the Vista version you need and I'd guess it would need to be the 64 bit version. If you Google for UIAutomationCore.dll FsX you might find the downloadable version. I still think it may be a heat problem though.
 
:frown:
No good. I searched for UIAutomationCore.dll and found a thread where it sounded just the thing to cure crashes in 64 bit Windows 7, so I downloaded and installed it but it still happened. Then I took the side off the computer again and pointed a fan inside, but still no luck. There's still a CTD after about 30-40 minutes.

Thank you for the suggestions, though. Any more, please?
 
dhasdell said:
:frown:
No good. I searched for UIAutomationCore.dll and found a thread where it sounded just the thing to cure crashes in 64 bit Windows 7, so I downloaded and installed it but it still happened. Then I took the side off the computer again and pointed a fan inside, but still no luck. There's still a CTD after about 30-40 minutes.

Thank you for the suggestions, though. Any more, please?
Click to expand...

Pointing a fan inside is not enough. Try to remove all the dust and things that clog up the cooler of your CPU and PSU. Use tweezers and toothpicks if necessary!

About the eventviewer: if you can see what happened (following fsxttcb's instructions) you can also see what program or which dll is causing the trouble.

Oh, and using the Win7 version of the UIAutomationCore.dll is no good. You need the Vista 64 bit version of it and place it in the root of your fsx install.

As for reducing the number of processes and services to an acceptable level, read this: http://www.blackviper.com/

Keep us posted!

Dumonceau
 
Still no good. I thought it was cured, but it's happened again.

Here's a screendump of the error in the event log, but I don't know what it means!
 
I notice in your screenshot the faulting module was "ai_player.dll".

I was having quite a few CTD's, with that being the cause of most, if not all of them. I figured it must be AI related, so checked through all my traffic files for problems and found a fair few flightplans in which one or more airport or waypoint was missing. Most of these were MAIW flightplans, converted to FSX format. Checking on the MAIW website, I managed to download most of the missing ones, and also a few from other sites. Any flightplans that I couldn't find the missing items for, I removed completely. Since then I haven't had a single CTD (touch wood!)

Maybe something to look at.
 
I think you are on to it. I have looked back, and none of the crashes relates to UIAutomationCore.dll. All seem to be ai_player.dll. I think perhaps I will try temporarily removing all but the default and TrafficX files, and all but the default boats too. Might it be that an FTX traffic file calls up an airfield that is removed when I change my Orbx scenery area?
 
From your screen shot the problem is with the ai_player.dll, try setting your sliders for AI aircraft, ships and ground vehicles to zero and see what happens.
 
Still crashing for ai_player.dll with all but default traffic and Traffic X tempororarily deactivated. I'll try with sliders to zero next session. Bit depressing, really.
 
Progress at last! With all addon traffic files removed (which didn't help on its own) and all traffic sliders set to 0% I've just gone two hours without a crash, but where do we go from here? Am I looking at a reinstall? Definitely not the video card or the cooling, I think, but something in the AI.
 
You must log in or register to reply here.
Back
Top