Archived

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

BonanzaPilot

Fatal Error - No Solution

Recommended Posts

Hey guys. I have been searching for months and trying many different things to get the fatal errors to stop in FSX. I have added the uiautomationcore.dll but that does nothing. I have gotten a new hard drive as well so I had to do a clean install of Windows 7 and FSX and I am still having the problem. Does anyone have any other suggestions? The fatal errors will happen randomly, often on startup of FSX and shortly after loading an aircraft, but will occasionally happen at cruise or on descent. Let me know if there are any tests that I can run and provide the results here because I would love to get this worked out. Thanks.

Share this post


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

if you could check your event viewer it  will tell you what module  is causing  the ctd 

Share this post


Link to post
Share on other sites

I will try this if I experience another fatal error. Performed a Windows Update tonight and tried to duplicate the error but couldn't. I'm sure it will happen on an upcoming flight soon. It's hard to duplicate the error when I'm not sure what the problem is and it happens so randomly. Thanks for your help. I'll keep this topic updated.

Share this post


Link to post
Share on other sites

I used to get FSX crashing on start up:  solved it by amending the compatibility tab at FSX.exe to Windows XP or Vista.   Other problems such as freezes and CTDs solved by lowering the sliders.  Of course, I have the usual main tweaks such as Highmemfix and AffinityMask. Hope you can sort out your problems.

 

Chris

Share this post


Link to post
Share on other sites

This is an automatic message.

 

This topic has been moved from "MS FSX Forum" to "Crash To Desktop (CTD) Forum". This move has been done for a number of possible reasons.

  • The most likely reason is that the post was off topic.
  • The topic could also have contained images or a video that were not appropriate to the original forum it was posted in.
  • The images might not have been "illustrative" or "explanatory" in nature.
  • The topic could have been moved because we deemed it to be more appropriately placed elsewhere.
Please ensure that your posts are "on topic" and contain illustrative images or videos as appropriate. Do not post videos or images just for entertainment purposes anywhere but in the screen shot or video forums. See our image posting rules here.

 

Members who continue to post off topic posts can be denied entry to specific forums in order to reduce and remove the practice. Your cooperation is appreciated.

Share this post


Link to post
Share on other sites

Here are my results from my most recent fatal error:

Version=1
EventType=APPCRASH
EventTime=130144074522211846
ReportType=2
Consent=1
ReportIdentifier=e12c7e26-c94b-11e2-bf27-902b34d386bb
IntegratorReportIdentifier=e12c7e25-c94b-11e2-bf27-902b34d386bb
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61637.0
Sig[2].Name=Application Timestamp
Sig[2].Value=46fadb14
Sig[3].Name=Fault Module Name
Sig[3].Value=g3d.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.61637.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=46fadb58
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=000ba7e9
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\FSX\fsx.exe
UI[3]=A fatal error occurred.
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\FSX\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\WININET.dll
LoadedModule[37]=C:\Windows\syswow64\iertutil.dll
LoadedModule[38]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[39]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[40]=C:\Windows\system32\MPR.dll
LoadedModule[41]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[42]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[43]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[44]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll
LoadedModule[45]=C:\Windows\system32\mscms.dll
LoadedModule[46]=C:\Windows\system32\DDRAW.dll
LoadedModule[47]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[48]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[49]=C:\Windows\syswow64\IMM32.dll
LoadedModule[50]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[51]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[52]=C:\Windows\syswow64\NSI.dll
LoadedModule[53]=C:\Windows\system32\msi.dll
LoadedModule[54]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[55]=C:\FSX\language.dll
LoadedModule[56]=C:\FSX\API.DLL
LoadedModule[57]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[58]=C:\FSX\ablscpt.dll
LoadedModule[59]=C:\FSX\flight.dll
LoadedModule[60]=C:\FSX\ai_player.dll
LoadedModule[61]=C:\FSX\acontain.dll
LoadedModule[62]=C:\FSX\controls.dll
LoadedModule[63]=C:\Windows\system32\DINPUT8.dll
LoadedModule[64]=C:\FSX\fsui.dll
LoadedModule[65]=C:\FSX\atc.dll
LoadedModule[66]=C:\FSX\facilities.dll
LoadedModule[67]=C:\FSX\demo.dll
LoadedModule[68]=C:\FSX\main.dll
LoadedModule[69]=C:\FSX\fe.dll
LoadedModule[70]=C:\FSX\util.dll
LoadedModule[71]=C:\FSX\simprop.dll
LoadedModule[72]=C:\FSX\g2d.dll
LoadedModule[73]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[74]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[75]=C:\Windows\system32\d3d9.dll
LoadedModule[76]=C:\Windows\system32\d3d8thk.dll
LoadedModule[77]=C:\FSX\g3d.dll
LoadedModule[78]=C:\FSX\panels.dll
LoadedModule[79]=C:\FSX\multiplayer.dll
LoadedModule[80]=C:\FSX\ui.dll
LoadedModule[81]=C:\FSX\sound.dll
LoadedModule[82]=C:\FSX\sim1.dll
LoadedModule[83]=C:\FSX\simscheduler.dll
LoadedModule[84]=C:\FSX\visualfx.dll
LoadedModule[85]=C:\FSX\window.dll
LoadedModule[86]=C:\FSX\terrain.dll
LoadedModule[87]=C:\FSX\weather.dll
LoadedModule[88]=C:\Windows\system32\DSOUND.dll
LoadedModule[89]=C:\Windows\system32\POWRPROF.dll
LoadedModule[90]=C:\FSX\symmap.dll
LoadedModule[91]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17514_none_72d18a4386696c80\gdiplus.dll
LoadedModule[92]=C:\Windows\system32\MSIMG32.dll
LoadedModule[93]=C:\FSX\xuipc.dll
LoadedModule[94]=C:\FSX\livingwater.dll
LoadedModule[95]=C:\FSX\fs-traffic.dll
LoadedModule[96]=C:\FSX\gps.dll
LoadedModule[97]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[98]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[99]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[100]=C:\Windows\system32\rsaenh.dll
LoadedModule[101]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[102]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[103]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[104]=C:\Windows\system32\wbemcomn.dll
LoadedModule[105]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[106]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[107]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[108]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[109]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL
LoadedModule[110]=C:\Windows\system32\dxgi.dll
LoadedModule[111]=C:\Windows\system32\aticfx32.dll
LoadedModule[112]=C:\Windows\system32\atiu9pag.dll
LoadedModule[113]=C:\Windows\system32\atiumdag.dll
LoadedModule[114]=C:\Windows\system32\atiumdva.dll
LoadedModule[115]=C:\Windows\system32\atiuxpag.dll
LoadedModule[116]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[117]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[118]=C:\Windows\system32\d3d10_1.dll
LoadedModule[119]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[120]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[121]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[122]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[123]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[124]=C:\Windows\SysWOW64\d3d11.dll
LoadedModule[125]=C:\Windows\system32\winbrand.dll
LoadedModule[126]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[127]=C:\Windows\system32\WINSTA.dll
LoadedModule[128]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[129]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[130]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[131]=C:\Windows\SysWOW64\wer.dll
LoadedModule[132]=C:\Windows\System32\Wpc.dll
LoadedModule[133]=C:\Windows\System32\wevtapi.dll
LoadedModule[134]=C:\Windows\System32\msxml6.dll
LoadedModule[135]=C:\Windows\system32\SAMLIB.dll
LoadedModule[136]=C:\Windows\system32\netutils.dll
LoadedModule[137]=C:\FSX\uiautomationcore.dll
LoadedModule[138]=C:\Windows\system32\OLEACC.dll
LoadedModule[139]=C:\Windows\System32\MMDevApi.dll
LoadedModule[140]=C:\Windows\System32\PROPSYS.dll
LoadedModule[141]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[142]=C:\Windows\system32\RICHED20.DLL
LoadedModule[143]=C:\Windows\system32\HID.DLL
LoadedModule[144]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[145]=C:\Windows\system32\wdmaud.drv
LoadedModule[146]=C:\Windows\system32\ksuser.dll
LoadedModule[147]=C:\Windows\system32\AVRT.dll
LoadedModule[148]=C:\Windows\system32\msacm32.drv
LoadedModule[149]=C:\Windows\system32\midimap.dll
LoadedModule[150]=C:\Windows\system32\dinput.DLL
LoadedModule[151]=C:\Windows\System32\wship6.dll
LoadedModule[152]=C:\Windows\System32\wshtcpip.dll
LoadedModule[153]=C:\FSX\bglmanx.dll
LoadedModule[154]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[155]=C:\Windows\system32\inetmib1.dll
LoadedModule[156]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[157]=C:\Windows\system32\WINNSI.DLL
LoadedModule[158]=C:\Windows\system32\snmpapi.dll
LoadedModule[159]=C:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[160]=C:\Windows\system32\MSVCR100.dll
LoadedModule[161]=C:\FSX\FeelThere\Erj\E145XH.dll
LoadedModule[162]=C:\Program Files (x86)\SquawkBox\sbtrans10.dll
LoadedModule[163]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[164]=C:\Program Files (x86)\SquawkBox\sbaicontrol10.dll
LoadedModule[165]=C:\Program Files (x86)\SquawkBox\sbmod10.dll
Sec[0].Key=LCID
Sec[0].Value=1033
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft® Flight Simulator X
AppPath=C:\FSX\fsx.exe
 

Share this post


Link to post
Share on other sites

You are another one getting FSX CTD's and FSX is not installed in the default directory....  May be the cause, most likely not.  I have had a couple of crashes myself with FSX installed in the default directory. 

 

Diego provided some excellent links that might fix your problem.  The g3d.dll is the faulting module and installing the FSUIPC might fix your issue as it has trapped some bad code and prevented crashes but it has not fixed all g3d.dll errors.  When it doesn't, I think it happens if your settings are set too high.  You may be having an issue with your memory heap.  Here's a link to automatically fix the memory heap limitation that normally repairs out-of-memory issues but, since you probably have your settings set too high, you can use all the memory you can get - http://www.microsoft...s.aspx?id=26368.  Just click on Microsoft Fix and the issue will be fixed on your system.

 

Microsoft Visual C++ 2005 is properly installed with the latest update.  So is MSV 2010.  MSV 2008 did not load.  Make sure it is installed with the latest update - http://www.microsoft...s.aspx?id=26368.  Hope this helps!

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Thanks for the answers guys. I will put all of these changes in later and hopefully the problem will be fixed. 

Share this post


Link to post
Share on other sites

Thanks for the help guys. I followed the suggestions and it was working great. I was on a flight today, beginning descent into ORD, and FSX froze. I got a 'not responding' message and had to exit FS. Not sure if this is considered a fatal error or if this was just a random freezing.

 

Version=1
EventType=AppHangB1
EventTime=130149358071041891
ReportType=1
Consent=1
ReportIdentifier=0c25c9e0-ce1a-11e2-8f2d-902b34d386bb
IntegratorReportIdentifier=0c25c9e1-ce1a-11e2-8f2d-902b34d386bb
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=fsx.exe
Sig[1].Name=Application Version
Sig[1].Value=10.0.61637.0
Sig[2].Name=Application Timestamp
Sig[2].Value=46fadb14
Sig[3].Name=Hang Signature
Sig[3].Value=f7fc
Sig[4].Name=Hang Type
Sig[4].Value=2048
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=f7fc88831a14516a1a53b7dc654b9c89
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=0a03
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=0a0361110b548a85e6238b8d704beae7
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=f7fc
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=f7fc88831a14516a1a53b7dc654b9c89
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=0a03
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=0a0361110b548a85e6238b8d704beae7
UI[3]=Microsoft Flight Simulator® is not responding
UI[4]=Windows can check online for a solution. If you close the program, you might lose information.
UI[5]=Check for a solution and close the program
UI[6]=Check for a solution and close the program
UI[7]=Close the program
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=Microsoft Flight Simulator®
AppPath=C:\FSX\fsx.exe
ReportDescription=A problem caused this program to stop interacting with Windows.

 

There is the crash report. Maybe it was just random and my FSX is working fine. Any idea? Thanks again.
 

Share this post


Link to post
Share on other sites

There is nothing in the Microsoft crash report that provides any information as to what caused the hang other than it happened at Memory Address f7fc and the Hang Type=2048 (which also means zilch).  I saw no solutions to your problem Googling Hang Type=2048 but there are a lot of other flight simmers who have had this type of 'hang'.

 

On AppHangs, most likely a program was running in the background that couldn't complete its mission so your fsx stopped and froze.  For me it was AS2012.  I would be flying in heavy weather and then, evidently, AS2012 decides it wants to update the weather.  It could be a connection problem or a firewall problem or something else in the network that is stopping the completion of this simple task.  Maybe the weather server is down.  You will never find out (or at least I didn't).  I simply did a Ctrl-Alt-Del and opened up Task Manager and terminated AS2012.  Now, getting back into FSX was difficult as there is a known bug that prevents this most of the time.  I was just patient and kept trying to open up FSX again and finally the screen popped up.  I was able to continue the flight w/o any issues.  The next time I flew, I didn't startup AS2012 as the manual states AS2012 takes over your default weather program.  So I started up FSX and loaded real weather thru the FSX setup.  Success!  No hangs and the flight completed without any issues.  I tried the flight again with AS2012 enabled.  Same problem.  The flight froze and I had to terminate AS2012 to get FSX running again.  Now, since I increased the heap limitation as I suggested you do in post #10, I have been able to enable AS2012, crank up my LOD_Radius to 6.5 and my Texture_Max_Load to 2048 and no apphangs or crashes.

 

Now I'm telling you my little story as it is something that fixed my problem.  It may or may not fix your issue or you might see something similar that happened to you.  I also found that if you have a weather program like AS2012 or REX and set your graphics in those programs to display HD graphics you will probably get a crash or your FSX will freeze up especially if you also have Texture_Max_Load set to 2048 or 4096.

 

Check to make sure there is nothing in the AppCrashView program related to this apphang.  Many AppHangB1's will be displayed in AppCrashView.  What AppCrashView does is decipher the Microsoft report you provided above by providing more information or all of the information any Microsoft Techie would receive if you were able to send him/her the details of your crash/AppHang.  I'm not an expert but I can decipher some crash reports and I think there are many others who visit this forum who have some expertise.

 

There could also be something in your FSX.cfg that FSX does not like.  A tweak.  The BufferPool tweak does not work for all systems and is the most likely cause of freezes/crashes if you have this tweak in your config. 

 

Hope this helps.

 

Best regards,

Jim

Share this post


Link to post
Share on other sites

Thanks for the great explanation. I was running OpusFSX so that might have been the problem. I also have the BufferPool tweak so I will take a look at that. Thanks again. 

Share this post


Link to post
Share on other sites