Jump to content

FSX Crash


Emi
 Share

Recommended Posts

  • Administrator

Hello,

I have a problem with the Katana. On every flight I have done untill now FSX crashed after about 10 minuits of flight when I press the middle mouse button. But I have to use this button because my EZDok Camera uses it.

Also when switching between windowed and fullscreen mode FSX crashes if I do it a few times.

I'm needing help!

Regards

Emi

Link to comment
Share on other sites

  • Administrator

I have just resetted my FSX.cfg using Flusifix, but that didn't help in any way.

This time FSX even crashed without any inputs from me. I had just taken off from EDXW any been flying for about 2 or 3 minuits and then suddenly it said FSX.exe doesn't work anylonger (Or however the error is called in english).

Any other suggestions?

Link to comment
Share on other sites

Mostly caused by driver errors. Did you re-build the shaders and double-check there aren't duplicate entries for the graphic card in FSX.cfg?

If so, then I would look at this as a driver issue - you don't detail precisely what the error message contains, so can't help any further.

Perhaps show the FSX .cfg here (remove the gauge permissions, they're irrelevant). I don't know this `Flusfix` you mention, but sounds like it has all the potential to screw up your .cfg.

Link to comment
Share on other sites

Flusifix (Flugsimulator Fix) is a software tool that allows you to set certain parameters or reset stuff back to default and so on...

Here is the developer's English page if you're interested:

http://www.wolfgang-picheta.de/flusifix_eng.htm

You mention using EZDok, maybe there is some strange interaction there... like a simconnect issue?

Sorry, stabbing a little in the dark...

Andrew

Link to comment
Share on other sites

  • Administrator

Well, here is my FSX.cfg:

<I'm not sure where the gaige permissions are, so I left it as it was.

[GRAPHICS]

SHADER_CACHE_PRIMED_10=1693500672

SHADER_CACHE_PRIMED=1693500672

TEXTURE_MAX_LOAD=1024

NUM_LIGHTS=8

AIRCRAFT_SHADOWS=1

AIRCRAFT_REFLECTIONS=1

COCKPIT_HIGH_LOD=1

LANDING_LIGHTS=1

AC_SELF_SHADOW=1

EFFECTS_QUALITY=2

GROUND_SHADOWS=0

TEXTURE_QUALITY=3

IMAGE_QUALITY=0

See_Self=1

Text_Scroll=1

D3D10=0

[sOUND]

AmbientUIMusicVolume=-6.000000

PrimaryDevice={00000000-0000-0000-0000-000000000000}

VoiceDevice={00000000-0000-0000-0000-000000000000}

SOUND=1

SOUND_QUALITY=2

SOUND_LOD=0

UISound=1

AmbientUI=0

[Display]

ChangeTime=2.000000

TransitionTime=2.000000

ActiveWindowTitleTextColor=255,255,255

ActiveWindowTitleBackGroundColor=0,28,140,64

NonActiveWindowTitleTextColor=255,255,255

NonActiveWindowTitleBackGroundColor=24,33,87,64

InfoUpperRightTextColor=255,0,0

InfoUpperRightBackGroundColor=0,0,0,0

InfoLowerLeftTextColor=255,255,255

InfoLowerLeftBackGroundColor=255,0,0,128

InfoLowerRightTextColor=255,255,255

InfoLowerRightBackGroundColor=255,0,0,128

InfoBrakesEnable=False

InfoParkingBrakesEnable=False

InfoPauseEnable=False

InfoSlewEnable=False

InfoStallEnable=False

InfoOverspeedEnable=False

BLOOM_EFFECTS=0

SKINNED_ANIMATIONS=1

TEXTURE_BANDWIDTH_MULT=40

UPPER_FRAMERATE_LIMIT=20

WideViewAspect=False

[Main]

User Objects=Airplane, Helicopter

SimObjectPaths.0=SimObjects\Airplanes

SimObjectPaths.1=SimObjects\Rotorcraft

SimObjectPaths.2=SimObjects\GroundVehicles

SimObjectPaths.3=SimObjects\Boats

SimObjectPaths.4=SimObjects\Animals

SimObjectPaths.5=SimObjects\Misc

ProcSpeed=10623

PerfBucket=7

HideMenuNormal=0

HideMenuFullscreen=1

[PANELS]

IMAGE_QUALITY=1

QUICKTIPS=1

PANEL_OPACITY=100

PANEL_MASKING=1

PANEL_STRETCHING=1

UNITS_OF_MEASURE=0

DEFAULT_VIEW=0

[Weather]

WindshieldPrecipitationEffects=1

MinGustTime=10

MaxGustTime=500

MinGustRampSpeed=1

MaxGustRampSpeed=200

MinVarTime=5

MaxVarTime=50

MinVarRampSpeed=10

MaxVarRampSpeed=75

TurbulenceScale=1.000000

WeatherServerAddress=fs2k.zone.com

WeatherServerPort=80

WeatherGraphDataInDialog=0

AdjustForMagVarInDialog=1

DynamicWeather=2

DownloadWindsAloft=0

DisableTurbulence=0

CLOUD_DRAW_DISTANCE=3

DETAILED_CLOUDS=1

CLOUD_COVERAGE_DENSITY=8

THERMAL_VISUALS=0

[DISPLAY.Device.NVIDIA GeForce GTX 460.0]

Mode=1680x1050x32

Anisotropic=1

AntiAlias=1

[AccelerationPack]

ControlsFirstRun=0

HomePageFirstRun=0

[CONTROLS]

Controls_Default=Standard

Controls_Current=Standard

KBDAIL=64

KBDELEV=64

KBDRUD=64

[TextInfo.1]

Latitude=1,1

Longitude=1,2

Altitude=1,3

Heading=1,4

AirSpeed=1,5

WindDirectionAndSpeed=1,6

[TextInfo.2]

FrameRate=1,1

LockedFrameRate=1,2

GForce=1,3

FuelPercentage=1,4

[TextInfo.3]

Latitude=1,1

Longitude=1,2

Altitude=1,3

Heading=1,4

AirSpeed=1,5

WindDirectionAndSpeed=1,6

FrameRate=2,1

LockedFrameRate=2,2

GForce=2,3

FuelPercentage=2,4

[slewTextInfo.1]

Latitude=1,1

Longitude=1,2

Altitude=1,3

Heading=1,4

AirSpeed=1,5

[slewTextInfo.2]

FrameRate=1,1

LockedFrameRate=1,2

[slewTextInfo.3]

Latitude=1,1

Longitude=1,2

Altitude=1,3

Heading=1,4

AirSpeed=1,5

FrameRate=2,1

LockedFrameRate=2,2

[Trusted]

C:\Program Files (x86)\EZCA\EZCA.exe.znqnqkbcnziaqinebirkoiceziwtentltrklwtat=1

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\GPSModule.dll.uwaatunzqqernrzlktlwetirzherunhlwrkwzknr=1

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll.auahnbrbkwrunqohkakewhteblttteozollcnrwl=1

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Diamond DA20-100 'Katana'\panel\ASC.DLL.ourrlhzolekknenhoenitqukoruwockrqrnwluiu=2

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Diamond DA20-100 'Katana'\panel\loadsave.GAU.iitenwwtkoezaikewwuaztltbubuouiqqchhilne=2

C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\SimObjects\Airplanes\Diamond DA20-100 'Katana'\panel\payload.GAU.eonchluqerwkoucektbbbccuekuzbhticizeteqw=2

[DynamicHeadMovement]

LonAccelOnHeadLon=-0.020000

LonAccelOnHeadPitch=-0.010000

RollAccelOnHeadLat=0.010000

YawAccelOnHeadLat=-0.100000

RollAccelOnHeadRoll=0.100000

MaxHeadAngle=5.000000

MaxHeadOffset=0.300000

HeadMoveTimeConstant=1.000000

[VirtualCopilot]

VirtualCopilotActive=0

[uSERINTERFACE]

PageID=1

OpenATCOnCreate=0

SHOW_MISSION_CAPTIONS=0

PAUSE_ON_LOST_FOCUS=1

PROMPT_ON_EXIT=1

SITUATION=FLIGHTS\OTHER\FLTSIM

Map_Orientation=2

ShowAllACPaintSchemes=1

SelectAircraftManufacturer=Alle

SelectAircraftPublisher=Alle

SelectAircraftType=Alle

[ATC]

ShowATCText=1

COMM_MSG_NONE_COLOR=FFFFFFFF

COMM_MSG_ATC_USER_COLOR=FFB6FFB6

COMM_MSG_USER_ATC_COLOR=FFFFD21B

COMM_MSG_ATC_AI_COLOR=FF00FF00

COMM_MSG_AI_ATC_COLOR=FFFF7840

AutoOpenAirTrafficWindow=1

UsePilotVoice=1

PilotVoice=0

[PointOfInterestSystem]

CycleSetting=0

[MULTIPLAYER]

condAccoutPassword=0

[sCENERY]

LENSFLARE=1

DAWN_DUSK_SMOOTHING=1

IMAGE_COMPLEXITY=4

[TrafficManager]

AirlineDensity=0

GADensity=100

FreewayDensity=0

ShipsAndFerriesDensity=0

LeisureBoatsDensity=0

IFROnly=0

AIRPORT_SCENERY_DENSITY=0

[TERRAIN]

LOD_RADIUS=4.500000

MESH_COMPLEXITY=75

MESH_RESOLUTION=20

TEXTURE_RESOLUTION=25

AUTOGEN_DENSITY=3

DETAIL_TEXTURE=1

WATER_EFFECTS=7

[AContain]

ShowLabels=1

ShowUserLabel=0

ShowLabelManufacturer=1

ShowLabelModel=1

ShowLabelTailNumber=0

ShowLabelDistance=1

ShowLabelAltitude=1

ShowLabelAirline=0

ShowLabelAirlineAndFlightNumber=0

ShowLabelFlightPlan=0

ShowLabelContainerId=0

ShowLabelAirspeed=0

ShowLabelHeading=0

LabelDelay=1000

LabelColor=FFFF0000

[iNTERNATIONAL]

ASLAT=2

ASLON=1

MEASURE=0

[REALISM]

PFactor=0.000000

Torque=0.000000

GyroEffect=0.000000

CrashTolerance=0.000000

General=0.000000

UnlimitedFuel=True

AllowEngineDamage=False

TrueAirspeed=False

AutoCoord=False

RealMixture=False

StressDamage=False

GEffect=False

ManualLights=False

GyroDrift=False

CrashWithDyn=False

CrashDetection=False

AutoTrim=False

[sIM]

SYSCLOCK=1

[sTARTUP]

DEMO=0

SHOW_OPENING_SCREEN=1

STARTUP_DEMO=

LoadWindow=1

[FACILITIES]

COUNTRY=

STATE=

CITY=

GTL_BUTTON=4096

[Misc]

Com_Rate=7

[FlightPlanMap]

LineWidth=2

SHOW_AIRPORTS=1

SHOW_VORS=1

SHOW_NDBS=1

SHOW_APPROACHES=1

SHOW_INTERSECTIONS=1

SHOW_VICTOR=0

SHOW_JET=0

SHOW_AIRSPACE=1

SHOW_FLIGHTPLAN=1

SHOW_WEATHERSTATIONS=1

SHOW_WEATHERSYSTEMS=1

SHOW_DATATAGS=1

SHOW_TERRAIN=1

show_waypoints=1

show_airways=1

show_markers=1

show_volume_boundaries=1

show_ac_twr=1

Flusifix is a programm which can modify datas in FSX to make it faster, or similar things. You can look it up here: Flusifix Homepage.

By the way, I have been able to make a 30 minuites flight around the VRMM now without a crash while flying. But FSX crashed when I wanted to end the flight using the Escape button on my keyboard.

Link to comment
Share on other sites

You have a large number of anomalous entries in that FSX .cfg, many of which are in direct contradiction to the advice given in the Katana manuals, and these forums.

Once again, you seem to have rushed headlong into something without taking the time to think things through. You are using one of the most sophsiticated addon packages ever created for FS, yet you have most of the Realism settings in the .cfg set at what is best described as `moron` level. You should fix those.

I hope this `Flusifix` is the cause, as then you can throw it away or get your money back if you paid for it, and then use your knowledge of FS to set things up properly.

You also have GA traffic set at 100%. ANY setting of 100% in AI has the potential to cause problems. You should fix that too.

Your sound card may also be the cause of your problems as that is a very strange identifier in the sound section - all `0`'s suggests to me that your sound card may be a problem. Is it an onboard sound card combined with the mobo? If so, you might want to check with the mobo manufacturer for updated drivers for that.

What does the error message say?

Link to comment
Share on other sites

  • Administrator

As I have not that much knowledge of correcting any things in the .cfg, may you do it for me and send me the corrected text back? Or could you post your FSX.cfg here, so that I can copy it into my FSX please?

Link to comment
Share on other sites

Not really a good idea using someone else's fsx.cfg file. There are PC specific entries in there that will not work in your PC, unless of course Simon and you have EXACTLY the same PC, set up in exactly the same way...

I don't understand your sound card primary device identifier either... I assume you do have sound?

My personal suggestion would be the HIGHMEMFIX=1 in the [GRAPHICS] section

and as Simon writes, your realism settings are way off the ball...

Andrew

Link to comment
Share on other sites

  • Administrator

I have now deleated my FSX.cfg so that a new one was build. Now the Katana works fine. At least untill now. I'll report if it crashes again.

Yes I have sound. I think that problem was there because I had a new soundcard build in for some time untill I got my GTX 460 which took to much place so that I had to remove the soundcard again.

By the way, usually my realism setting are set to max, I just forgot to do this here because I have been playing around a little in my FSX to find a fix for my problems myself :).

Link to comment
Share on other sites

  • Root Admin

As I have not that much knowledge of correcting any things in the .cfg, may you do it for me and send me the corrected text back? Or could you post your FSX.cfg here, so that I can copy it into my FSX please?

Just delete it Emi (it indeed seems rather strange). FSX will make a new one as it starts and there is a good chance your problems will be solved. All FS support staff will tell you that these tweaks in cfg files cause over half the problems we have to deal with.

Link to comment
Share on other sites

  • Administrator

The Problem appeared again. But after a few hours of flying time all around Germany I can now say that the problem with the crash appears only when I'm flying around the German Airfields 1 scenery!

So there must be a problem between the Katana and German Airfields 1. Does anyone have an idea what the problem is and how I can fix it?

Link to comment
Share on other sites

Those tweaks are usually applied as a result of unscientific recommendations made by unqualified people with only limited understanding and a single computer to play on. If they were clever they wouldn't be proffering suggestions in a flight sim forum, they'd be selling their services to MS or Laminar Research, or Lockheed-Martin!

You don't want to know the number and variations of problems that have been caused by inappropriate modifications to that file. That's not to say that some don't work, only that the number that do are small, and the number of machines they work on smaller still. And that's where the danger is - trying something then not testing it properly, or failing to recall that modification when a problem surfaces later on.

But good to know Emi has got his Kat working well, and let's hope this proves to be sound advice for other simmers experiencing the same issues.

Sweet!

Link to comment
Share on other sites

..... .duplicate entries for the graphic card in FSX.cfg?

This could be the toppest of top tips! I chanced upon that line and thought "I seem to remember several ATI5870 series entries with different resolutions". My reaction to that was maybe FSX stores a selection for future use (Yeah, I know :rolleyes:) and gave it no more thought. Well, I commented them out leaving just one entry and...and this could be a huge coincidence, an hour flight an no CTD! :o

Link to comment
Share on other sites

The Problem appeared again. But after a few hours of flying time all around Germany I can now say that the problem with the crash appears only when I'm flying around the German Airfields 1 scenery!

So there must be a problem between the Katana and German Airfields 1. Does anyone have an idea what the problem is and how I can fix it?

What does the event viewer say happened.

if you windows 7 you can find it here

Click start

in the searchbox type "event viewer"

It will list the event viewer

Click on event viewer in list and it will open the vent viewer.

Now double click on the "Administartive events"

it will now list the errors and warnings

Click on the error. It will then list the detail.

EG: here is an error I ot with the RXP gauge.

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: rxpGNS.DLL, version: 1.4.9.9, time stamp: 0x4d1167fd

Exception code: 0xc0000005

Fault offset: 0x0002d078

Faulting process id: 0x81c

Faulting application start time: 0x01cc05c5c729924a

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\rxpGNS.DLL

Report Id: 2e938a18-71b9-11e0-8bc0-00248c2a6ff4

check if you did get an error around the time you got the CTD that look like this that list FSX. You might need to go though them all until you find the eroor of FSX..

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: ai_player.dll, version: 10.0.61637.0, time stamp: 0x46fadb57

Exception code: 0xc0000005

Fault offset: 0x00037489

Faulting process id: 0x4f8

Faulting application start time: 0x01cc04f27ced99d4

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll

Report Id: a2a1a257-70e7-11e0-8963-00248c2a6ff4

or this

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58

Exception code: 0xc0000005

Fault offset: 0x000ba79f

Faulting process id: 0x11f0

Faulting application start time: 0x01cc0366a598e019

Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Faulting module path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g3d.dll

Report Id: cab74dd5-6f60-11e0-b513-00248c2a6ff4

If you have such an error eg g3d.dll error then it is an texture error at an airport and that is why you get it only when you near an airport. Most of the times it is an texture error of an ai airplane parked at the airport. (It was in my case anyway)

You can then google g3d.dll error and you will find lots of information.

if it is an AI_plyer error, it is mostly hardware unable to cope with all the data to process.

ag:

itle: Re: Ai_player.dll error with FSX

Post by: Norman Dean on June 10, 2010, 10:23:20 PM

Hi John,This is a common error, that occurs for some unknow reason, and you will see it reported in many forums. The fact that it fails in ai_player is probably of no significance, it is just the module that is running at the time it crashes, and the only problable explanation is that FSX is unable to handle the cpu load associated with high graphics and closing down satisfactorily. I had this myself not associated with any product and happend after every flight. I can't remember which oes now, and one good thing is that is doesn't seem to have any effect on the program which starts as normal next time. However, in my case after some time it suddenly stopped happening, and I really don't know why that happend either.

hi John, Its likely that EGKK comes up because of the high graphic load with all the other airfields around it plus any other addon that you are using. It can also happen with EGLL and even EGLC, but you will seldom find it any where else in this country. This seems to be the pattern on other forums as well, in that it usually follows a flight to a large hub.

I doubt very much that a clean install will make any difference, but if you have the time then its worth a try.

So use the event viewer to see what happened before you make assumptions. The event viewer will give you detail like the one at the top with the RX gauge. You can then go direct to that problem and corrrect the problem instead of thinking it is this or that.

.

Link to comment
Share on other sites

Just to add, I was not suggesting that the HIGHMEMFIX would solve the issue, but allows the user to deal with some memory issues that have plagued FSX since the outset.

It is in my mind one of the few effective tweaks that can/should be added to the FSX.cfg. I use pretty much a standard cfg file with minor tweaks only...

Works a dream...

Andrew

Link to comment
Share on other sites

  • Administrator

What does the event viewer say happened.

[...]

So use the event viewer to see what happened before you make assumptions. The event viewer will give you detail like the one at the top with the RX gauge. You can then go direct to that problem and corrrect the problem instead of thinking it is this or that.

.

Thank you, you're errors you've listed brought me to the idea to turn off all the AI-traffic. Now It works absolutly fine when I'm flying.

Only one last thing:

On my last flight yesterday I got an CTD when I tried to end the flight (When I pressed the Escape button). Not that that would be that annoying, but the fact that the flight hours I have done in this time doesn't get into the aircrafts loggers is a little disturbing.

Does someone have an idea what's happening there?

Link to comment
Share on other sites

  • Root Admin

Thank you, you're errors you've listed brought me to the idea to turn off all the AI-traffic. Now It works absolutly fine when I'm flying.

Only one last thing:

On my last flight yesterday I got an CTD when I tried to end the flight (When I pressed the Escape button). Not that that would be that annoying, but the fact that the flight hours I have done in this time doesn't get into the aircrafts loggers is a little disturbing.

Does someone have an idea what's happening there?

It's an issue we seen with most complex aircraft. Our Airbus X does it most of the time. We have asked MS for help on this but they did not want to assist. We think it has to do with XML code as C++ coded aircraft do not display this effect (saying so, all PMDG aircraft do it on my system)

So for now it is something we can't fix.

Link to comment
Share on other sites

  • 4 weeks later...

It's an issue we seen with most complex aircraft. Our Airbus X does it most of the time. We have asked MS for help on this but they did not want to assist. We think it has to do with XML code as C++ coded aircraft do not display this effect (saying so, all PMDG aircraft do it on my system)

So for now it is something we can't fix.

Is anybody who is getting this error by any chance using any FPS limiter?

Link to comment
Share on other sites

Is anybody who is getting this error by any chance using any FPS limiter?

I'm using an external FPS limiter, but FSX closes normally after a flight in the Katana.

Other than renaming FSX.CFG and letting FSX create a new one (always a good thing to do if FSX is acting up), it may help to look through the DLL.XML file located in the same folder and disable entries that are not needed. Many addons (Aerosoft scenery and aircraft from PMDG, Captain Sim, iFly etc) add .dlls to this file that get loaded every time you start FSX, whether they are needed or not. Disabling those you don't need at the moment may lighten the load on a stressed system. (The disadvantage is, you have to remember to enable them again when they are needed)

Link to comment
Share on other sites

  • Root Admin

I'm using an external FPS limiter, but FSX closes normally after a flight in the Katana.

Other than renaming FSX.CFG and letting FSX create a new one (always a good thing to do if FSX is acting up), it may help to look through the DLL.XML file located in the same folder and disable entries that are not needed. Many addons (Aerosoft scenery and aircraft from PMDG, Captain Sim, iFly etc) add .dlls to this file that get loaded every time you start FSX, whether they are needed or not. Disabling those you don't need at the moment may lighten the load on a stressed system. (The disadvantage is, you have to remember to enable them again when they are needed)

I doubt that will do any good as the DLL's are not loaded if they are not called. They are just bits on the disk then.

Link to comment
Share on other sites

I doubt that will do any good as the DLL's are not loaded if they are not called. They are just bits on the disk then.

True, but some add themselves to the addon menu, so those at least are being called.

Anyway, just a suggestion. Seems to help on my system, but who knows - as you keep piling addons on FSX it becomes very difficult to keep track of where things began to go wrong and what corrective steps had a positive effect.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...