Sign in to follow this  
intxeon

FSX Steam crash

Recommended Posts

Hi everyone

I have random crash on my fsx steam.

According to the event viewer crash is caused by this module: C:\WINDOWS\SYSTEM32\atidxx32.dll

Error code: 0xc0000005

 

My add-on: Aerosoft airbus x, active sky next, pro atc x, aivlasoft efb and Orbx Global and Vector

 

Here is my fsx.cfg 

 

[JOBSCHEDULER]

AffinityMask=84
[bufferPools]
RejectThreshold=262144
UsePools=1
PoolSize=10485760
[GRAPHICS]
SHADER_CACHE_PRIMED_10=1693751040
SHADER_CACHE_PRIMED=1693751040
TEXTURE_MAX_LOAD=4096
NUM_LIGHTS=8
AIRCRAFT_SHADOWS=1
AIRCRAFT_REFLECTIONS=1
COCKPIT_HIGH_LOD=1
LANDING_LIGHTS=1
AC_SELF_SHADOW=0
EFFECTS_QUALITY=2
GROUND_SHADOWS=0
TEXTURE_QUALITY=3
IMAGE_QUALITY=0
See_Self=1
Text_Scroll=1
D3D10=1
ForceWindowedVsync=1
ALLOW_SHADER_30=1
HIGHMEMFIX=1
MultiSamplesPerPixel=4
MultiSamplesQuality=24
[sOUND]
AmbientUIMusicVolume=-6.000000
PrimaryDevice={00000000-0000-0000-0000-000000000000}
VoiceDevice={00000000-0000-0000-0000-000000000000}
SOUND=1
SOUND_QUALITY=2
SOUND_LOD=1
UISound=1
AmbientUI=0
[Display]
ChangeTime=4.000000
TransitionTime=4.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=True
InfoParkingBrakesEnable=True
InfoPauseEnable=True
InfoSlewEnable=True
InfoStallEnable=True
InfoOverspeedEnable=True
BLOOM_EFFECTS=0
SKINNED_ANIMATIONS=1
TEXTURE_BANDWIDTH_MULT=120
UPPER_FRAMERATE_LIMIT=0
WideViewAspect=False
TextureMaxLoad=9
[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=8771
PerfBucket=7
HideMenuNormal=1
HideMenuFullscreen=1
Location=440,129,1480,908,\\.\DISPLAY1
Maximized=2
FIBER_FRAME_TIME_FRACTION=0.22
[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=0
DownloadWindsAloft=0
DisableTurbulence=0
CLOUD_DRAW_DISTANCE=6
DETAILED_CLOUDS=1
CLOUD_COVERAGE_DENSITY=8
THERMAL_VISUALS=0
[DISPLAY.Device.AMD Radeon HD 7900 Series.0]
Mode=1920x1080x32
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]
fsdreamteam\couatl\couatl.exe.zlqiotnnciutcwciooiwbrnkuelzalrctqockbwe=1
C:\Program Files (x86)\EZCA\EZCA.exe.wrcbbiuhwkklrrkiuurcezuoboewlulwohhiuwha=1
bglmanx.dll.wkzzhzbczuikqrnbnaenbtlewiueikwcqbueolle=1
Modules\FSUIPC4.dll.aqnknbhqtalioluokkrznzqrlnuwobenqihkhrzc=1
PMDG\DLLs\PMDG_Interface.dll.ewcacrioioueauzetwibbriobereweloinlhhzqu=1
RAASPRO\RAASPRO.dll.aqnbciwkqilwbebwurtlaqqzwkculblzouhonwoo=1
PMDG\DLLs\PMDG_HUD_interface.dll.ezirncqhrbrbtetqwtihzcohuttqbzeluqteonnc=1
PMDG\DLLs\PMDGOptions.dll.awbhznblnkhnhwuhtqbqzelokieantiwickqihbi=1
PMDG\DLLs\PMDGEvents.dll.quuurltcwklkqhubnuabrlaooelznaekiokoaera=1
PMDG\DLLs\PMDGSounds.dll.tzltzheozanohauqlnllantnetwtowicatziuwrw=1
Aerosoft\Flight Recorder\AS-FlightRecorder.dll.nwlqlqubocctbictcaeqrceqzlkcczztnoznzibr=1
Modules\A2A_Feel.dll.tulicnkwknaezuecbcnkobrezohitobzuiqczbow=1
Modules\AccuFeelMenu.dll.ztbitbnoenrtzbhuiraauulhzhekeurbkelawawc=1
D:\Program Files\FS Recorder for FSX\RecorderFSX.dll.ccunrqiozztaabkkaoizocnoeenncqolbhrhanli=1
carenavigraph.dll.tklwtrwczurrawzqbtaekncawqcezwieueochkhe=1
CMeteoXml.dll.qwhinizbobhruchazqlzwatuoattuooaibnenluz=1
as_srv\as_btstrp.dll.qnklibabbhialzqacawoqlkbneloreaclnhcczqa=1
D:\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\DLLs\fmgs.dll.hzaiiwltnetibllkblahazlzreqbwrnlekkzhcra=2
D:\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\Airbus_ECAMD2D.dll.wbwibbaotheaokkuroukanrwwrhhkqintaoehbon=2
D:\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\ASC.DLL.tknerrlrhzbeouqcaucochbclnrianwquczwqnnb=2
D:\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\ND\AB_ND_GDI.dll.cequzkueacbnothckqcwuwthwurouirhrkibbibw=2
D:\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\DLLs\AsInput.dll.qhezqaktnbuitckibikeetktranclbzulazzhzak=2
D:\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\DLLs\FBW.dll.uwqrzoqtlnlclwaaaklehoeznzlerkwuaebbewbb=2
D:\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\AirbusXE2.dll.wrzzqaqbahhhwhzlctknwuzbqabruniriebeohru=2
D:\Steam\steamapps\common\FSX\SimObjects\Airplanes\Aerosoft Airbus A320_A321 Base\Panel_Fallback\AirbusXE.dll.wokczeihlkwthkulnkoanihiqwinikhlchteuuiu=2
D:\Steam\steamapps\common\FSX\gauges\RASDuke_Sound.gau.ouhikonnoaonaohhceieiklecwwnczrzzkrcruel=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=0
PROMPT_ON_EXIT=0
SITUATION=FLIGHTS\OTHER\FLTSIM
Map_Orientation=2
ShowAllACPaintSchemes=1
SelectAircraftManufacturer=Tutti
SelectAircraftPublisher=Aerosoft
SelectAircraftType=Tutti
[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
[sCENERY]
LENSFLARE=1
DAWN_DUSK_SMOOTHING=1
IMAGE_COMPLEXITY=4
[TrafficManager]
AirlineDensity=20
GADensity=0
FreewayDensity=0
ShipsAndFerriesDensity=15
LeisureBoatsDensity=15
IFROnly=0
AIRPORT_SCENERY_DENSITY=2
[TERRAIN]
LOD_RADIUS=3.500000
MESH_COMPLEXITY=50
MESH_RESOLUTION=20
TEXTURE_RESOLUTION=26
AUTOGEN_DENSITY=1
DETAIL_TEXTURE=1
WATER_EFFECTS=4
BATCH_AUTOGEN2=1
SWAP_WAIT_TIMEOUT=2
[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=False
AllowEngineDamage=False
TrueAirspeed=False
AutoCoord=False
RealMixture=True
StressDamage=False
GEffect=False
ManualLights=True
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=1251
[Misc]
Com_Rate=7
[DISPLAY.Device.AMD Radeon HD 7900 Series.0.0]
Mode=1920x1080x32
AntiAlias=1
[MULTIPLAYER]
condAccoutPassword=0
 

 

My pc config: i7 2600 ,8gb ddr3,fsx running on ssd,amd radeon hd 7970

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

The crash was caused by one of your ATI/Radeon display drivers.  Could be caused by high settings or corrupted display drivers.  I opt for high settings but it would be easy to just reinstall your video card drivers and see if that fixes the problem.  You have so many tweaks in your fsx.cfg it could also be cause by a bad parameter set for the tweak(s).  An i7 2600 should be able to run fsx-se w/o any tweaks whatsoever (other than tweaking your FSX-SE settings).

 

Best regards,

  • Upvote 1

Share this post


Link to post
Share on other sites

Thanks Jim for your answer.

I already reinstalled display drivers so many times...

Regarding high setting what settings should I lower in order to test if crash happens again?

Share this post


Link to post
Share on other sites

Regarding high setting what settings should I lower in order to test if crash happens again?

 

I'm not familiar with the ATI Display Drivers.  FSX was built around NVidia video cards as ATI/Radeon decided not to play the game when FSX was developed/released.  ATI liked the Windows XP OS and was furious when Microsoft updated the OS to Vista and, almost immediately afterwards, to Windows 7.  They refused to release drivers for Vista as they publicly stated they liked Windows XP.  I know this only because I was an ATI user at the time and decided not to play their game and went and got me an NVidia card (8800GTX??).  Now video cards are video cards but just saying what happened.  This is why we only have guidance in the AVSIM FSX Configuration Guide for NVidia.  I think ATI made a major mistake back then as it hurt a lot of gamers who upgraded to Vista/Windows 7 and didn't have updated drivers for their new OS.  The biggest fps killer is in the AA areas.

 

Here's a possible solution I found on Google as you are using Steam - http://steamcommunity.com/app/8870/discussions/0/558756256356222940/.

 

Here's a similar crash reported over at the VATSIM forums - https://forums.vatsim.net/viewtopic.php?f=79&t=70025.  What is interesting about this one is the fact it happened recently and with an ATI card.  Makes me think it is the version of the display driver.  Maybe not working properly.  Maybe moving back to an older driver will work?

 

Best regards,

Share this post


Link to post
Share on other sites

I used process monitor and after another crash caused by the same module I see a lot of BUFFER OVERFLOW result in process monitor

Share this post


Link to post
Share on other sites

You should set it up to only monitor P3D.exe as you are monitoring everything happening on your computer and that's almost impossible to figure out (plus you get one heck of a huge log as hundreds of thousands of entries are logged every minute.  Running it too long and you could easily run out of disk space!!).  Buffer Overflow results are extremely common and you would never see them if you were monitoring just P3D and all of your addons as described on page 4 of the AVSIM CTD Guide:

 

Run Process Monitor – Another investigative tool used to pin down a situation where your application freezes, crashes, or stutters/pauses during a flight is to run a utility called Process Monitor. During your flight, this utility monitors activity such as calling textures, AI aircraft schedules, ATC, weather updates, and scenery loading.  When FSX/P3D stutters or FPS drop dramatically you simply write down the time it occurred.  This is important as thousands of entries are made every minute, every second.  Continue doing this throughout the flight.  Of course, if it freezes, you will know what was going on before the application froze.  This utility will not show you a definitive cause of your issue but it will show you what add-ons were being loaded about when you received the stutter, the long pause(s), and the freeze and you can further investigate by disabling that scenery, that aircraft, or whatever might have caused the event.  One member used this utility to determine that My Traffic X, version 5.4c was the cause of a BEX/StackHash/NTDLL.dll crash he was getting.  It was easy to disable My Traffic X in the Scenery Library and find that FSX no longer crashed.

AVSIM recommends you do not run a flight any longer than 60 minutes as the Process Monitor log becomes quite large (hopefully your application will freeze or crash by then!).  For a 60 minutes flight, expect the file to be at least as large as 8GB’s or tens of millions of captured events.  Make sure you delete the log or move it to another drive after you have finished your testing to free up HDD space.  Another recommended tip is to make sure you use system time to mark the time of each event and do not use an external clock unless they are synchronized.  Going through one minute of a process is a massive amount of data needed to be reviewed (it goes fast as thousands of entries just show a scenery being loaded).

To run this utility properly, you need to capture only FSX/P3D/FS9 events.  It would be nearly impossible to find a possible glitch or issue if Windows events or other system activities were being logged too.  AVSIM recommends opening of the Process Monitor when you are on the active runway and preparing to takeoff to save space on your HDD:

  • Startup FSX/P3D/FS9, as appropriate, to the Setup Screen.
  • Open Process Monitor
  • Click on the Filter tab and then Filter…. 
  • Click on Architecture and scroll down to Process Name
  • Click on blank box and select FSX/P3D/FS9, as appropriate
  • Click Ok or Apply

 

NOTE:  AVSIM recommends you click on the filter tab again and then select ‘Save filter…’ and name your Filter – FSX (or P3D/FS9).  Then, in the future, you can startup Process Monitor before opening your application and watch what is loading as your application loads to the Setup Screen.

 

You can use the utility while in Full Screen mode or Windowed Mode.  In Windowed Mode you can monitor what is happening instantly but it is best to run Process Monitor in Full Screen (unless you are seeing freezes in Windowed Mode).

 

When the flight is finished, immediately go to the Process Monitor application, click on it to bring it into focus, and hit Ctrl+E on your keyboard to capture the events (event logging will continue until you do this and make it more difficult to locate the cause of your crash).  Shutdown FSX/P3D/FS9 and begin your investigating!  You can also save the log for future investigations but remember the file will be as large as 8GB’s or more and using valuable disk space.

 

Your problem is definitely ATI related.  You just need to investigate and find out where (the drivers, the a high setting, a tweak in your fsx.cfg?).

 

Best regards,

Share this post


Link to post
Share on other sites

I forgot to mention that I was monitoring just fsx.exe process and before my last crash I saw a lot of buffer overflow strings

 

Anyway I just reinstalled fsx steam with only aribus x, active sky ,dx10 fixer,clean fsx.cfg w/o tweaks and I still have the same crash so probably dx10 mode it's incompatible with my hardware configuration. I'll try dx9 mode...

Share this post


Link to post
Share on other sites

Did not know you had DX10 Preview mode turned on.  That's a likely cause too.  If it is the cause, you might want to check with the developer Steve Parsons' and maybe he can figure out what you did wrong.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this