Jump to content

Archived

This topic is now archived and is closed to further replies.

AnkH

Crashes always "unknown module"

Recommended Posts

Dear all,

 

Sadly, my FSX, after running several months flawlessly, now suddenly crashes all the time inflight. I was not able to reproduce the crashes (plane, scenery, clicking, view changes etc.), and it is always inflight. Here is my log (sorry, its in German):

 

Version=1
EventType=BEX
EventTime=130194850242476564
ReportType=2
Consent=1
UploadTime=130194850242956592
ReportIdentifier=05ef2894-f77a-11e2-96f4-c86000c2fbc0
IntegratorReportIdentifier=05ef2893-f77a-11e2-96f4-c86000c2fbc0
WOW64=1
Response.BucketId=2564907304
Response.BucketTable=5
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=fsx.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=10.0.61637.0
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=46fadb14
Sig[3].Name=Fehlermodulname
Sig[3].Value=StackHash_2264
Sig[4].Name=Fehlermodulversion
Sig[4].Value=0.0.0.0
Sig[5].Name=Fehlermodulzeitstempel
Sig[5].Value=00000000
Sig[6].Name=Ausnahmeoffset
Sig[6].Value=79e04794
Sig[7].Name=Ausnahmecode
Sig[7].Value=c0000005
Sig[8].Name=Ausnahmedaten
Sig[8].Value=00000008
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=2055
DynamicSig[22].Name=Zusatzinformation 1
DynamicSig[22].Value=2264
DynamicSig[23].Name=Zusatzinformation 2
DynamicSig[23].Value=2264db07e74365624c50317d7b856ae9
DynamicSig[24].Name=Zusatzinformation 3
DynamicSig[24].Value=875f
DynamicSig[25].Name=Zusatzinformation 4
DynamicSig[25].Value=875fa2ef9d2bdca96466e8af55d1ae6e
UI[2]=D:\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
UI[3]=Microsoft Flight Simulator® funktioniert nicht mehr
UI[4]=Windows kann online nach einer Lösung für das Problem suchen.
UI[5]=Online nach einer Lösung suchen und das Programm schließen
UI[6]=Später online nach einer Lösung suchen und das Programm schließen
UI[7]=Programm schließen
LoadedModule[0]=D:\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\Windows\syswow64\kernel32.dll
LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL
LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll
LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll
LoadedModule[7]=C:\Windows\syswow64\GDI32.dll
LoadedModule[8]=C:\Windows\syswow64\USER32.dll
LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll
LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll
LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll
LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll
LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll
LoadedModule[14]=C:\Windows\syswow64\LPK.dll
LoadedModule[15]=C:\Windows\syswow64\USP10.dll
LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll
LoadedModule[17]=C:\Windows\syswow64\ole32.dll
LoadedModule[18]=C:\Windows\system32\apphelp.dll
LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL
LoadedModule[20]=C:\Windows\system32\UxTheme.dll
LoadedModule[21]=C:\Windows\system32\WINMM.dll
LoadedModule[22]=C:\Windows\system32\samcli.dll
LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll
LoadedModule[24]=C:\Windows\system32\MSACM32.dll
LoadedModule[25]=C:\Windows\system32\VERSION.dll
LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll
LoadedModule[27]=C:\Windows\system32\sfc.dll
LoadedModule[28]=C:\Windows\system32\sfc_os.DLL
LoadedModule[29]=C:\Windows\system32\USERENV.dll
LoadedModule[30]=C:\Windows\system32\profapi.dll
LoadedModule[31]=C:\Windows\system32\dwmapi.dll
LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll
LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll
LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll
LoadedModule[35]=C:\Windows\syswow64\urlmon.dll
LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL
LoadedModule[43]=C:\Windows\syswow64\iertutil.dll
LoadedModule[44]=C:\Windows\syswow64\WININET.dll
LoadedModule[45]=C:\Windows\system32\MPR.dll
LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
LoadedModule[50]=C:\Windows\system32\mscms.dll
LoadedModule[51]=C:\Windows\system32\DDRAW.dll
LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[54]=C:\Windows\syswow64\IMM32.dll
LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[57]=C:\Windows\syswow64\NSI.dll
LoadedModule[58]=C:\Windows\system32\msi.dll
LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80DEU.DLL
LoadedModule[60]=D:\Microsoft Games\Microsoft Flight Simulator X\language.dll
LoadedModule[61]=D:\Microsoft Games\Microsoft Flight Simulator X\API.DLL
LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[63]=D:\Microsoft Games\Microsoft Flight Simulator X\ablscpt.dll
LoadedModule[64]=D:\Microsoft Games\Microsoft Flight Simulator X\flight.dll
LoadedModule[65]=D:\Microsoft Games\Microsoft Flight Simulator X\ai_player.dll
LoadedModule[66]=D:\Microsoft Games\Microsoft Flight Simulator X\acontain.dll
LoadedModule[67]=D:\Microsoft Games\Microsoft Flight Simulator X\controls.dll
LoadedModule[68]=C:\Windows\system32\DINPUT8.dll
LoadedModule[69]=D:\Microsoft Games\Microsoft Flight Simulator X\fsui.dll
LoadedModule[70]=D:\Microsoft Games\Microsoft Flight Simulator X\atc.dll
LoadedModule[71]=D:\Microsoft Games\Microsoft Flight Simulator X\facilities.dll
LoadedModule[72]=D:\Microsoft Games\Microsoft Flight Simulator X\demo.dll
LoadedModule[73]=D:\Microsoft Games\Microsoft Flight Simulator X\main.dll
LoadedModule[74]=D:\Microsoft Games\Microsoft Flight Simulator X\fe.dll
LoadedModule[75]=D:\Microsoft Games\Microsoft Flight Simulator X\util.dll
LoadedModule[76]=D:\Microsoft Games\Microsoft Flight Simulator X\simprop.dll
LoadedModule[77]=D:\Microsoft Games\Microsoft Flight Simulator X\g2d.dll
LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[80]=C:\Windows\system32\d3d9.dll
LoadedModule[81]=C:\Windows\system32\d3d8thk.dll
LoadedModule[82]=D:\Microsoft Games\Microsoft Flight Simulator X\g3d.dll
LoadedModule[83]=D:\Microsoft Games\Microsoft Flight Simulator X\panels.dll
LoadedModule[84]=D:\Microsoft Games\Microsoft Flight Simulator X\multiplayer.dll
LoadedModule[85]=D:\Microsoft Games\Microsoft Flight Simulator X\ui.dll
LoadedModule[86]=D:\Microsoft Games\Microsoft Flight Simulator X\sound.dll
LoadedModule[87]=D:\Microsoft Games\Microsoft Flight Simulator X\sim1.dll
LoadedModule[88]=D:\Microsoft Games\Microsoft Flight Simulator X\simscheduler.dll
LoadedModule[89]=D:\Microsoft Games\Microsoft Flight Simulator X\visualfx.dll
LoadedModule[90]=D:\Microsoft Games\Microsoft Flight Simulator X\window.dll
LoadedModule[91]=D:\Microsoft Games\Microsoft Flight Simulator X\terrain.dll
LoadedModule[92]=D:\Microsoft Games\Microsoft Flight Simulator X\weather.dll
LoadedModule[93]=C:\Windows\system32\DSOUND.dll
LoadedModule[94]=C:\Windows\system32\POWRPROF.dll
LoadedModule[95]=D:\Microsoft Games\Microsoft Flight Simulator X\symmap.dll
LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll
LoadedModule[97]=C:\Windows\system32\MSIMG32.dll
LoadedModule[98]=D:\Microsoft Games\Microsoft Flight Simulator X\xuipc.dll
LoadedModule[99]=D:\Microsoft Games\Microsoft Flight Simulator X\livingwater.dll
LoadedModule[100]=D:\Microsoft Games\Microsoft Flight Simulator X\fs-traffic.dll
LoadedModule[101]=D:\Microsoft Games\Microsoft Flight Simulator X\gps.dll
LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[104]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[105]=C:\Windows\system32\rsaenh.dll
LoadedModule[106]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[107]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[108]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[109]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[110]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[111]=C:\Windows\system32\wbemcomn.dll
LoadedModule[112]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[113]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[114]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[115]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[116]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[117]=C:\Windows\SysWOW64\ctagent.DLL
LoadedModule[118]=C:\Windows\system32\dxgi.dll
LoadedModule[119]=C:\Windows\system32\d3d11.dll
LoadedModule[120]=C:\Windows\system32\nvd3dum.dll
LoadedModule[121]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[122]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[123]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[124]=C:\Windows\system32\d3d10_1.dll
LoadedModule[125]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[126]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[127]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[128]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[129]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[130]=C:\Windows\system32\winbrand.dll
LoadedModule[131]=C:\Windows\system32\nvapi.dll
LoadedModule[132]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[133]=C:\Windows\system32\WINSTA.dll
LoadedModule[134]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[135]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[136]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[137]=C:\Windows\SysWOW64\wer.dll
LoadedModule[138]=C:\Windows\System32\Wpc.dll
LoadedModule[139]=C:\Windows\System32\wevtapi.dll
LoadedModule[140]=C:\Windows\System32\msxml6.dll
LoadedModule[141]=C:\Windows\system32\SAMLIB.dll
LoadedModule[142]=C:\Windows\system32\netutils.dll
LoadedModule[143]=D:\Microsoft Games\Microsoft Flight Simulator X\uiautomationcore.dll
LoadedModule[144]=C:\Windows\system32\OLEACC.dll
LoadedModule[145]=C:\Windows\System32\MMDevApi.dll
LoadedModule[146]=C:\Windows\System32\PROPSYS.dll
LoadedModule[147]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[148]=C:\Windows\system32\RICHED20.DLL
LoadedModule[149]=C:\Windows\system32\HID.DLL
LoadedModule[150]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[151]=C:\Windows\system32\wdmaud.drv
LoadedModule[152]=C:\Windows\system32\ksuser.dll
LoadedModule[153]=C:\Windows\system32\AVRT.dll
LoadedModule[154]=C:\Windows\system32\msacm32.drv
LoadedModule[155]=C:\Windows\system32\midimap.dll
LoadedModule[156]=C:\Windows\system32\dinput.DLL
LoadedModule[157]=C:\Windows\System32\wship6.dll
LoadedModule[158]=C:\Windows\System32\wshtcpip.dll
LoadedModule[159]=D:\Microsoft Games\Microsoft Flight Simulator X\bglmanx.dll
LoadedModule[160]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[161]=C:\Windows\system32\inetmib1.dll
LoadedModule[162]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[163]=C:\Windows\system32\WINNSI.DLL
LoadedModule[164]=C:\Windows\system32\snmpapi.dll
LoadedModule[165]=D:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.dll
LoadedModule[166]=D:\Microsoft Games\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll
LoadedModule[167]=D:\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\VMCX_AP.dll
LoadedModule[168]=D:\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\ViMaNET_AP.dll
LoadedModule[169]=D:\Microsoft Games\Microsoft Flight Simulator X\FeelThere\E170\EJetH.dll
LoadedModule[170]=C:\Program Files (x86)\FS Recorder for FSX\FSRecorder_FSX.dll
LoadedModule[171]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[172]=C:\Windows\system32\msadp32.acm
LoadedModule[173]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[174]=C:\Windows\SysWOW64\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[175]=C:\Windows\SysWOW64\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[176]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[177]=C:\Windows\system32\Secur32.dll
LoadedModule[178]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[179]=C:\Windows\system32\msimtf.dll
LoadedModule[180]=C:\Windows\system32\msls31.dll
LoadedModule[181]=C:\Windows\system32\d2d1.dll
LoadedModule[182]=C:\Windows\system32\DWrite.dll
LoadedModule[183]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[184]=C:\Windows\system32\MLANG.dll
LoadedModule[185]=C:\Windows\system32\ntmarta.dll
LoadedModule[186]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[187]=C:\Windows\SysWOW64\uiautomationcore.dll
LoadedModule[188]=D:\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\ViMaIScnX_AP.dll
LoadedModule[189]=D:\Microsoft Games\Microsoft Flight Simulator X\Aerosoft\AES\ViMaCli.dll
LoadedModule[190]=C:\Windows\syswow64\imagehlp.dll
LoadedModule[191]=C:\Windows\system32\ncrypt.dll
LoadedModule[192]=C:\Windows\system32\bcrypt.dll
LoadedModule[193]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[194]=C:\Windows\system32\GPAPI.dll
LoadedModule[195]=C:\Windows\system32\cryptnet.dll
LoadedModule[196]=C:\Windows\system32\SensApi.dll
LoadedModule[197]=D:\Microsoft Games\Microsoft Flight Simulator X\GAUGES\737-400.DLL
LoadedModule[198]=D:\Microsoft Games\Microsoft Flight Simulator X\GAUGES\Magnetic_Compass.DLL
LoadedModule[199]=C:\Windows\system32\explorerframe.dll
LoadedModule[200]=C:\Windows\system32\DUser.dll
LoadedModule[201]=C:\Windows\system32\DUI70.dll
LoadedModule[202]=C:\Windows\system32\EhStorShell.dll
LoadedModule[203]=C:\Windows\system32\ntshrui.dll
LoadedModule[204]=C:\Windows\system32\srvcli.dll
LoadedModule[205]=C:\Windows\system32\cscapi.dll
LoadedModule[206]=C:\Windows\system32\slc.dll
LoadedModule[207]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[208]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[209]=C:\Windows\SysWOW64\actxprxy.dll
LoadedModule[210]=C:\Program Files (x86)\Internet Explorer\ieproxy.dll
LoadedModule[211]=C:\Windows\SysWOW64\thumbcache.dll
LoadedModule[212]=C:\Windows\system32\SearchFolder.dll
LoadedModule[213]=C:\Windows\system32\SHDOCVW.dll
LoadedModule[214]=C:\Windows\system32\LINKINFO.dll
LoadedModule[215]=C:\Windows\system32\NetworkExplorer.dll
LoadedModule[216]=C:\Windows\System32\drprov.dll
LoadedModule[217]=C:\Windows\System32\ntlanman.dll
LoadedModule[218]=C:\Windows\System32\davclnt.dll
LoadedModule[219]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[220]=C:\Windows\system32\wkscli.dll
LoadedModule[221]=C:\Windows\system32\PortableDeviceApi.dll
LoadedModule[222]=C:\Windows\system32\EhStorAPI.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Nicht mehr funktionsfähig
ConsentKey=BEX
AppName=Microsoft Flight Simulator®
AppPath=D:\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

 

Do you have any idea, what could be the reason and why it suddenly appeared, while I had no crashes for months before? Thank you for any hint!

 

regards

Chris

Share this post


Link to post
Share on other sites

No, you are getting a BEX/StackHash CTD.  Look at some of the posts here about StackHash crashes. I reinstalled Windows 7 and FSX/Acceleration. I was getting unexplained BEX/StackHash crashes (well, they occurred when I closed FSX). When I looked at the crash report it showed that the uiautomationcore.dll was in my main fsx folder. Now I never put it there and I know it was not there when FSX/Acceleration were installed. So some other program installed it. I removed it. So far the BEX/StackHash crashes are gone.  Most are due to having your FSX settings set too high.

 

 

Your Microsoft Visuals 2005 and 2008 are installed properly.  You might also try to expand your desktop heap limitation - http://support.microsoft.com/kb/947246.

 

Uiautomationcore.dll - I would also remove the uiautomationcore.dll from your main FSX directory.  Since you did get a crash, the Vista version obviously did not stop it. The uiautomationcore.dll only fixes one problem and that's a crash if you repeatedly hit the FSX menu bar.  I personally cannot replicate this crash and have tried several times to crash my FSX by repeatedly clicking on the fsx menu bar.  No joy... I really think the menu bar crash is caused by high settings where fsx is running short of memory by the constant hitting on the menu bar.  I do not have the uiautomationcore.dll in my main fsx folder and never have.  The uiautomationcore.dll belongs with the Microsoft.net framework packages and, developers of FSX and FSX addons require dotnet versions 1.1 thru 4.5 installed to make their products work properly.  I believe the Vista version of dotnet is 1.1 as it is installed with FSX/Acceleration.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Hmm, ok, thank you for this reply. If I got you right, my crashes seem not to be an FSX related problem but more something general. I will try with removing the uiautomationcore.dll from the FSX main folder and check back.

 

Could it also be a masked heat problem of my PC? While it was crashing for every flight last week including the weekend, I was able to perform a 2h flight without crash yesterday evening. Difference? About 5-6°C (!) in the room I have my PC installed. What did I change? I increased the CPU voltage in the BIOS slightly by 0.02 Volts. I have my i5-3570K running at 4.5GHz and managed to reduce the voltage quiet a lot when I was tuning it, maybe it was to much for FSX.

 

Keep you updated. Thank you for your help!

 

regards

Chris

 

PS: I already adapted my desktop heap limitations according to the guide.

Share this post


Link to post
Share on other sites

 

 


If I got you right, my crashes seem not to be an FSX related problem but more something general.

 

The BEX (Buffer_Exception_Overrun) and StackHash caused your crash while running FSX so it is FSX related.  Do you get the same crash error when running another software program?  No.  It's all related to your settings, your overclock, overheating, or bad memory configurations (sometimes the memory has to be manually configured in the BIOS as Auto may not be reading the memory properly).

 

If you brought your overclock back to the default settings and ran FSX, do you still get the crash?  If not, it probably was the overclock.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Hmm, ok, thank you for this reply. If I got you right, my crashes seem not to be an FSX related problem but more something general. I will try with removing the uiautomationcore.dll from the FSX main folder and check back.

 

Could it also be a masked heat problem of my PC? While it was crashing for every flight last week including the weekend, I was able to perform a 2h flight without crash yesterday evening. Difference? About 5-6°C (!) in the room I have my PC installed. What did I change? I increased the CPU voltage in the BIOS slightly by 0.02 Volts. I have my i5-3570K running at 4.5GHz and managed to reduce the voltage quiet a lot when I was tuning it, maybe it was to much for FSX.

 

Keep you updated. Thank you for your help!

 

regards

Chris

 

PS: I already adapted my desktop heap limitations according to the guide.

 

That FSX CTD's sometimes can mean that your overclock is not stable. Even if you don't get BSOD. You can be pretty close to stable overclock, maybe that 0.2 increase fixed it.

There can be some other hardware problem, i had this once becouse my joystick voltages. Unpluged joystick and never happpened again :)

 

Check that you have UAC disabled.

 

I would keep UIAutomationCore.dll, just ensoure that you have correct version https://www.dropbox.com/s/adxsx0mxb6wztil/UIAutomationCore.rar

 

This fixes fsx menu crashes, not all crashes.

 

If you still get BEX error, try to disable DEP globaly using command prompt and see if that helps: http://computerrepairsacramentoca.net/knowledge-base/disable-dep-windows-7-disable-dep-windows-2008-r2/

Don't do this if you don't have a good antivirus program, DEP protects you from mallwares, but like some other windows features, DEP can have a problem with FSX - you can read more about this on flightsimlabs support pages for example.

 

After you install new addon, allways check you XML.DLL http://support.precisionmanuals.com/KB/a92/dllxml-information-and-troubleshooting.aspx

 

and FSUIPC installation, just update to latest version http://forum.simflight.com/topic/66139-updated-modules/

 

If you are using FSinn, check also that fscopilot is the last entry in XML.DLL, allways

 

Apply that microsoft fix like Jim suggested, it's very important to avoid OOM errors, and don't set texture max load to more then 2048 in your fsx.cfg

 

Then - right click on fsx.exe, go to compatibility tab and click on "change settings for all users", and in "compatibility for all users" window - check only "disable visual themes" and "disable desktop composition".  After that click on apply, ok, apply and ok untill you clear all windows.

 After that go to the control Panel, "appearance and personalization" and select "Personalization". On the left hand side click on the "Change mouse pointers". In the "Pointers" tab,  under "Scheme" select (None), under "customize" select "Normal Select" and press apply and ok.

 

This should fix ocasional in-flight crashes

Share this post


Link to post
Share on other sites

Thank you guys again for your help. I did some testings now and I think that I found (one of) the problem: I often use timecompression in FSX, I am not the kind of a guy performing 4-5h in real time. However, somehow the [bufferPools] entries do not cope well with time compression, so I removed this completely. Managed to perform a 2h flight incl. 30min under 4x timecompression (so in fact a 3h30 flight ^_^ ) without any crash. But, I also did not use TrackIR for this flight. Could it be, that the crashes are also related to some TrackIR issue?

Share this post


Link to post
Share on other sites

Not sure about the TrackIR crashes but I recall seeing something when fsx first came out that using time compression above 4x's can cause crashes.  If I ever use it, I run 4x's exclusively.  Might have been a bug that would have been fixed if the FSX development was still going on.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Ok, it seems to be ok for now. I did increase the voltage, added some new RAMs (2133MHz with CL9) and disabled the bufferpool line completely. Now, even time compression works without crash. I anyway never go above 4x, as this would also disable AI Traffic. For the moment I am settled, lets see if I can bring up TrackIR again (did a reinstall with the newest software build from their homepage).

Share this post


Link to post
Share on other sites

Getting weird now. Here is my last crash view:

 

Version=1
EventType=AppHangB1
EventTime=130206129742181740
ReportType=1
Consent=1
UploadTime=130206129742791775
ReportIdentifier=3a75917d-01bc-11e3-bd50-c86000c2fbc0
IntegratorReportIdentifier=3a75917e-01bc-11e3-bd50-c86000c2fbc0
WOW64=1
Response.type=4
Sig[0].Name=Anwendungsname
Sig[0].Value=fsx.exe
Sig[1].Name=Anwendungsversion
Sig[1].Value=10.0.61637.0
Sig[2].Name=Anwendungszeitstempel
Sig[2].Value=46fadb14
Sig[3].Name=Absturzsignatur
Sig[3].Value=f7fc
Sig[4].Name=Absturztyp
Sig[4].Value=2048
DynamicSig[1].Name=Betriebsystemversion
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Gebietsschema-ID
DynamicSig[2].Value=2055
DynamicSig[22].Name=Zusätzliche Absturzsignatur 1
DynamicSig[22].Value=f7fc88831a14516a1a53b7dc654b9c89
DynamicSig[23].Name=Zusätzliche Absturzsignatur 2
DynamicSig[23].Value=0a03
DynamicSig[24].Name=Zusätzliche Absturzsignatur 3
DynamicSig[24].Value=0a0361110b548a85e6238b8d704beae7
DynamicSig[25].Name=Zusätzliche Absturzsignatur 4
DynamicSig[25].Value=f7fc
DynamicSig[26].Name=Zusätzliche Absturzsignatur 5
DynamicSig[26].Value=f7fc88831a14516a1a53b7dc654b9c89
DynamicSig[27].Name=Zusätzliche Absturzsignatur 6
DynamicSig[27].Value=0a03
DynamicSig[28].Name=Zusätzliche Absturzsignatur 7
DynamicSig[28].Value=0a0361110b548a85e6238b8d704beae7
UI[3]=Microsoft Flight Simulator® reagiert nicht
UI[4]=Wenn Sie das Programm schließen, gehen möglicherweise Informationen verloren.
UI[5]=Programm schließen
UI[6]=Programm schließen
UI[7]=Programm schließen
FriendlyEventName=Beendet und geschlossen.
ConsentKey=AppHangXProcB1
AppName=Microsoft Flight Simulator®
AppPath=D:\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
ReportDescription=Aufgrund eines Problems kann dieses Programm nicht mehr mit Windows kommunizieren.
 

Now, important notice: I was performing this flight from OMDB to VIDP using the SMS/Overland 777 with an Emirates paint. Thinking about that, I thought that most of my crashes occured in a SMS/Overland plane. So I fired up FSX again and performed the same flight (OMDB to VIDP) with a PA A320 and a IndiGO repaint. And, surprise surprise, no crash. I was able to perform the full flight, even with almost 20min using 4x time compression. Flawless. Could it be related to the SMS/Overland plane? Or to the repaint I use there?

Share this post


Link to post
Share on other sites

Every crash has to be investigated to find the cause and it appears you have investigated and found the probable solution.  Could be a memory leak being caused by the aircraft and/or the repaint.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Starts to be weird here, I am still not able to perform any long haul flight. I completely deleted the SMS Planes and switched to Project Opensky, but still performing long haul flights from asian airports, I get a crash within 20 - 30 minutes inflight, no matter if I use time compression or not. Strange enough that short/medium haul flights with the Project Airbus A32X can last up to 4h with or without time compression and I never get a crash. Next will be: test if longhaul works if I avoid Asia. Something is really strange here, why can I perform flights up to 4h within Europe using A32X and each and every longhaul flight starting in OMDB, VIDP, WSSS, RKSI etc. leads to a crash after 30min max?

 

One thing to note: I never get any information anymore, the FSX simply freezes, sound continues and after two minutes only, the message "FSX has stopped working" appears. Crash log is always similar to the one above (AppHangB1). I am lost. I love longhaul flights but so far, I need to restrict myself to shorthauls in Europe/US. Sad.

Share this post


Link to post
Share on other sites

Look in your FSUIPC.log (in the Modules folder) and see if you are getting any "running out of memory" messages.  The longer the flight the more likely you will get a freeze as FSX and your addons are using more and more memory VAS.  As I have stated before, you can lower your settings a notch or two and that might help.  A guy named Mitch just posted a solution for OOM's (know you are not getting OOM's but freezes but the situation is close to an OOM) and he fixed it by lowering his Global Scenery setting.  Download and run Process Explorer and see what processes are running in the background that are taking up so much memory during your flight (it can run in the background during your flight and you can look to see what the culprit was when fsx freezes up again).

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Another update:

 

It seems to be still somehow related to time compression. I managed to perform several flights without crashes not using the timecompression at all this weekend. However, starting a long haul flight and running 1x, works great. As soon as I start to use time compression -> freeze. Still not when using PA A32X in Europe though. Strange. And, as already stated somewhere else, if I restart my FSX after the freeze, I can usually perform whatever flight I want and use time compression as much as I want without any freeze. That really puzzles me, do I have to get used to this? Starting a flight, let FSX freeze and start over again? Thats ridiculous. BTW: I followed the "one notch less..." hint and reduced my settings one notch, but it did not change the frequency of freezes. So it is most probably not an out of memory issue...

Share this post


Link to post
Share on other sites

×
×
  • Create New...