Sign in to follow this  
davidzill

ApphangB1 crash

Recommended Posts

So I did a fresh install of FSX Acceleration. I use lots of add-ons: FTX/Orbx, REX TD, EZCA, FlyTampa, Flightbeam airports, Aersosoft airports DX10 fixer, PMDG, FS2 Crew, GSX, FSUIPC, SODE, AES, etc. The day I finished reinstalling everything I have been getting ApphangB1 crashes 100% of the time. I have done the same FSX.CFG tweaks, so this isn't the issue. This is a total nightmare, the act of a fresh install consumes several tedious hours just to finish with an unplayable program. I refuse to give up. I'm at a full loss at what to do. I'm very computer savy, yet this is getting exhaustive. Can someone please help me figure out a solution before I say screw it, uninstall everything, and spend another 18 hours installing it all again? 

Share this post


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

In the AVSIM CTD Guide, around page 10, look for how to fix most FSX CTD's and Freezes.  See link in my signature.

You did not indicate where you are getting the freezes.  At startup?  While loading?  During a flight?  If it was at startup, most like you have an out of date module, like FSUIPC or one of the other modules in your dll.xml.  Disable your dll.xml and restart FSX and see if this fixes the problem.  You should never ever reinstall FSX/Acceleration.  Deleting or renaming your FSX.cfg and then restarting FSX is like reinstalling FSX.  Individuals just put too much junk (tweaks) in their FSX.cfg.  High settings, a monitor not being identified, sound card not being identified properly, etc., etc.

Best regards,

Jim

 

Share this post


Link to post
Share on other sites
On May 9, 2017 at 7:15 AM, Jim Young said:

In the AVSIM CTD Guide, around page 10, look for how to fix most FSX CTD's and Freezes.  See link in my signature.

You did not indicate where you are getting the freezes.  At startup?  While loading?  During a flight?  If it was at startup, most like you have an out of date module, like FSUIPC or one of the other modules in your dll.xml.  Disable your dll.xml and restart FSX and see if this fixes the problem.  You should never ever reinstall FSX/Acceleration.  Deleting or renaming your FSX.cfg and then restarting FSX is like reinstalling FSX.  Individuals just put too much junk (tweaks) in their FSX.cfg.  High settings, a monitor not being identified, sound card not being identified properly, etc., etc.

Best regards,

Jim

 

Thanks for your reply Jim. I gave up, uninstalled and removed all traces of FSX. Memory tested and passed. I reinstalled using Nickn's bible. So far so good with a few apphangb1 crashes. I'm thinking maybe running a CCleaner registry scan, maybe something in the registry is causing the hangs and needs to be cleaned out. 

  • Upvote 1

Share this post


Link to post
Share on other sites

So this morning it has been apphangB1 crash city. 4 in 15 minutes. All other programs working fine. Memory tested. Everything is up to date. CTD guide doesn't even mention apphangB1. Here is my latest crash log:

Version=1
EventType=AppHangB1
EventTime=131391599698429767
ReportType=3
Consent=1
UploadTime=131391599735391881
ReportIdentifier=f8189cda-37e9-11e7-b88a-7824af4714b1
IntegratorReportIdentifier=f8189cdb-37e9-11e7-b88a-7824af4714b1
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=4392
Sig[4].Name=Hang Type
Sig[4].Value=1
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Hang Signature 1
DynamicSig[22].Value=439245d266346cfe65b77153d030bed5
DynamicSig[23].Name=Additional Hang Signature 2
DynamicSig[23].Value=3ed1
DynamicSig[24].Name=Additional Hang Signature 3
DynamicSig[24].Value=3ed1de379b6db6eb8deafa7ce82f7b3d
DynamicSig[25].Name=Additional Hang Signature 4
DynamicSig[25].Value=4392
DynamicSig[26].Name=Additional Hang Signature 5
DynamicSig[26].Value=439245d266346cfe65b77153d030bed5
DynamicSig[27].Name=Additional Hang Signature 6
DynamicSig[27].Value=3ed1
DynamicSig[28].Name=Additional Hang Signature 7
DynamicSig[28].Value=3ed1de379b6db6eb8deafa7ce82f7b3d
UI[3]=Microsoft Flight Simulator® is not responding
UI[4]=If you close the program, you might lose information.
UI[5]=Close the program
UI[6]=Close the program
UI[7]=Close the program
LoadedModule[0]=C:\1-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\XmlLite.dll
LoadedModule[37]=C:\Windows\syswow64\WININET.dll
LoadedModule[38]=C:\Windows\syswow64\iertutil.dll
LoadedModule[39]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[40]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[41]=C:\Windows\system32\MPR.dll
LoadedModule[42]=C:\Windows\AppPatch\AcLayers.DLL
LoadedModule[43]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[44]=C:\Windows\AppPatch\AcSpecfc.DLL
LoadedModule[45]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18837_none_ec86b8d6858ec0bc\COMCTL32.dll
LoadedModule[46]=C:\Windows\system32\mscms.dll
LoadedModule[47]=C:\Windows\system32\DDRAW.dll
LoadedModule[48]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[49]=C:\Windows\syswow64\COMDLG32.dll
LoadedModule[50]=C:\Windows\syswow64\IMM32.dll
LoadedModule[51]=C:\Windows\syswow64\MSCTF.dll
LoadedModule[52]=C:\Windows\syswow64\WS2_32.dll
LoadedModule[53]=C:\Windows\syswow64\NSI.dll
LoadedModule[54]=C:\Windows\system32\msi.dll
LoadedModule[55]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[56]=C:\1-FSX\language.dll
LoadedModule[57]=C:\1-FSX\API.DLL
LoadedModule[58]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[59]=C:\1-FSX\ablscpt.dll
LoadedModule[60]=C:\1-FSX\flight.dll
LoadedModule[61]=C:\1-FSX\ai_player.dll
LoadedModule[62]=C:\1-FSX\acontain.dll
LoadedModule[63]=C:\1-FSX\controls.dll
LoadedModule[64]=C:\Windows\system32\DINPUT8.dll
LoadedModule[65]=C:\1-FSX\fsui.dll
LoadedModule[66]=C:\1-FSX\atc.dll
LoadedModule[67]=C:\1-FSX\facilities.dll
LoadedModule[68]=C:\1-FSX\demo.dll
LoadedModule[69]=C:\1-FSX\main.dll
LoadedModule[70]=C:\1-FSX\fe.dll
LoadedModule[71]=C:\1-FSX\util.dll
LoadedModule[72]=C:\1-FSX\simprop.dll
LoadedModule[73]=C:\1-FSX\g2d.dll
LoadedModule[74]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[75]=C:\1-FSX\d3dx10_34.dll
LoadedModule[76]=C:\Windows\system32\MSVCR100.dll
LoadedModule[77]=C:\1-FSX\reald3dx10_34.DLL
LoadedModule[78]=C:\1-FSX\dx10fixerlib.DLL
LoadedModule[79]=C:\1-FSX\dx10SharedLib.dll
LoadedModule[80]=C:\Windows\system32\d3d9.dll
LoadedModule[81]=C:\Windows\system32\d3d8thk.dll
LoadedModule[82]=C:\1-FSX\g3d.dll
LoadedModule[83]=C:\1-FSX\panels.dll
LoadedModule[84]=C:\1-FSX\multiplayer.dll
LoadedModule[85]=C:\1-FSX\ui.dll
LoadedModule[86]=C:\1-FSX\sound.dll
LoadedModule[87]=C:\1-FSX\sim1.dll
LoadedModule[88]=C:\1-FSX\simscheduler.dll
LoadedModule[89]=C:\1-FSX\visualfx.dll
LoadedModule[90]=C:\1-FSX\window.dll
LoadedModule[91]=C:\1-FSX\terrain.dll
LoadedModule[92]=C:\1-FSX\weather.dll
LoadedModule[93]=C:\Windows\system32\DSOUND.dll
LoadedModule[94]=C:\Windows\system32\POWRPROF.dll
LoadedModule[95]=C:\1-FSX\symmap.dll
LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.23721_none_5c052bcda00f9399\gdiplus.dll
LoadedModule[97]=C:\Windows\system32\MSIMG32.dll
LoadedModule[98]=C:\1-FSX\xuipc.dll
LoadedModule[99]=C:\1-FSX\livingwater.dll
LoadedModule[100]=C:\1-FSX\fs-traffic.dll
LoadedModule[101]=C:\1-FSX\gps.dll
LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[104]=C:\Program Files (x86)\Razer\Razer Cortex\K_FPS.dll
LoadedModule[105]=C:\Windows\system32\dbghelp.dll
LoadedModule[106]=C:\Program Files (x86)\Razer\Razer Cortex\d3dx9_43.dll
LoadedModule[107]=C:\Program Files (x86)\Razer\Razer Cortex\d3dx10_43.dll
LoadedModule[108]=C:\Program Files (x86)\Razer\Razer Cortex\d3dx11_43.dll
LoadedModule[109]=C:\Program Files (x86)\Razer\Razer Cortex\D3DX8Wrapper.dll
LoadedModule[110]=C:\Program Files (x86)\Razer\Razer Cortex\D3DCOMPILER_43.dll
LoadedModule[111]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[112]=C:\Windows\system32\OPENGL32.dll
LoadedModule[113]=C:\Windows\system32\GLU32.dll
LoadedModule[114]=C:\Program Files (x86)\Razer\Razer Cortex\EasyHook32.dll
LoadedModule[115]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[116]=C:\Windows\system32\rsaenh.dll
LoadedModule[117]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[118]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[119]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[120]=C:\Windows\system32\wbemcomn.dll
LoadedModule[121]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[122]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[123]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[124]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[125]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL
LoadedModule[126]=C:\Windows\system32\dxgi.dll
LoadedModule[127]=C:\Windows\system32\d3d10.dll
LoadedModule[128]=C:\Windows\system32\d3d10core.dll
LoadedModule[129]=C:\Windows\system32\d3d11.dll
LoadedModule[130]=C:\Windows\system32\nvd3dum.dll
LoadedModule[131]=C:\Windows\system32\nvspcap.dll
LoadedModule[132]=C:\Windows\system32\WINHTTP.dll
LoadedModule[133]=C:\Windows\system32\webio.dll
LoadedModule[134]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[135]=C:\Windows\system32\nvapi.dll
LoadedModule[136]=C:\Windows\system32\nvwgf2um.dll
LoadedModule[137]=C:\Windows\system32\bcrypt.dll
LoadedModule[138]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[139]=C:\Windows\SysWOW64\bcryptprimitives.dll
LoadedModule[140]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[141]=C:\Windows\system32\d3d10_1.dll
LoadedModule[142]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[143]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[144]=C:\Windows\system32\WINSTA.dll
LoadedModule[145]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[146]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18837_none_41e855142bd5705d\COMCTL32.dll
LoadedModule[147]=C:\Windows\SysWOW64\wer.dll
LoadedModule[148]=C:\Windows\System32\Wpc.dll
LoadedModule[149]=C:\Windows\System32\wevtapi.dll
LoadedModule[150]=C:\Windows\System32\msxml6.dll
LoadedModule[151]=C:\Windows\system32\SAMLIB.dll
LoadedModule[152]=C:\Windows\system32\netutils.dll
LoadedModule[153]=C:\Windows\system32\uiautomationcore.dll
LoadedModule[154]=C:\Windows\system32\OLEACC.dll
LoadedModule[155]=C:\Windows\System32\MMDevApi.dll
LoadedModule[156]=C:\Windows\System32\PROPSYS.dll
LoadedModule[157]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[158]=C:\Windows\system32\RICHED20.DLL
LoadedModule[159]=C:\Windows\system32\HID.DLL
LoadedModule[160]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[161]=C:\Windows\system32\wdmaud.drv
LoadedModule[162]=C:\Windows\system32\ksuser.dll
LoadedModule[163]=C:\Windows\system32\AVRT.dll
LoadedModule[164]=C:\Windows\system32\msacm32.drv
LoadedModule[165]=C:\Windows\system32\midimap.dll
LoadedModule[166]=C:\Windows\system32\dinput.DLL
LoadedModule[167]=C:\Windows\System32\wship6.dll
LoadedModule[168]=C:\Windows\System32\wshtcpip.dll
LoadedModule[169]=C:\1-FSX\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll
LoadedModule[170]=C:\Windows\system32\dnsapi.DLL
LoadedModule[171]=C:\Windows\system32\iphlpapi.DLL
LoadedModule[172]=C:\Windows\system32\WINNSI.DLL
LoadedModule[173]=C:\Windows\system32\RASAPI32.dll
LoadedModule[174]=C:\Windows\system32\rasman.dll
LoadedModule[175]=C:\Windows\system32\rtutils.dll
LoadedModule[176]=C:\Windows\system32\sensapi.dll
LoadedModule[177]=C:\Windows\system32\NLAapi.dll
LoadedModule[178]=C:\Windows\system32\rasadhlp.dll
LoadedModule[179]=C:\Windows\system32\ntmarta.dll
LoadedModule[180]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[181]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll
LoadedModule[182]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[183]=C:\1-FSX\bglmanx.dll
LoadedModule[184]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[185]=C:\Windows\system32\MSVCP120.dll
LoadedModule[186]=C:\Windows\system32\MSVCR120.dll
LoadedModule[187]=C:\1-FSX\Modules\FSUIPC4.dll
LoadedModule[188]=C:\1-FSX\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[189]=C:\1-FSX\VistaMare\ViMaCoreX.dll
LoadedModule[190]=C:\1-FSX\VistaMare\bin\VMCX_AP.dll
LoadedModule[191]=C:\1-FSX\VistaMare\bin\ViMaNET_AP.dll
LoadedModule[192]=C:\Program Files (x86)\12bPilot\SODE\SimObjectAnimationModule.dll
LoadedModule[193]=C:\1-FSX\PMDG\DLLs\PMDG_Interface.dll
LoadedModule[194]=C:\Windows\system32\api-ms-win-core-synch-l1-2-0.DLL
LoadedModule[195]=C:\1-FSX\RAASPRO\RAASPRO.dll
LoadedModule[196]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[197]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll
LoadedModule[198]=C:\Windows\system32\MSDART.DLL
LoadedModule[199]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll
LoadedModule[200]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLL
LoadedModule[201]=C:\Windows\system32\comsvcs.dll
LoadedModule[202]=C:\Windows\system32\ATL.DLL
LoadedModule[203]=C:\Windows\SysWOW64\msjetoledb40.dll
LoadedModule[204]=C:\Windows\SysWOW64\msjet40.dll
LoadedModule[205]=C:\Windows\SysWOW64\mswstr10.dll
LoadedModule[206]=C:\Windows\SysWOW64\msjter40.dll
LoadedModule[207]=C:\Windows\SysWOW64\MSJINT40.DLL
LoadedModule[208]=C:\Windows\SysWOW64\mstext40.dll
LoadedModule[209]=C:\Windows\system32\mlang.dll
LoadedModule[210]=C:\Windows\system32\RAASAUDIO32.DLL
LoadedModule[211]=C:\Windows\system32\X3DAudio1_6.dll
LoadedModule[212]=C:\Windows\SysWow64\xactengine3_4.dll
LoadedModule[213]=C:\Windows\SysWow64\XAudio2_4.dll
LoadedModule[214]=C:\1-FSX\as_srv\as_btstrp.dll
LoadedModule[215]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[216]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[217]=C:\Windows\SysWOW64\msls31.dll
LoadedModule[218]=C:\Windows\system32\msimtf.dll
LoadedModule[219]=C:\1-FSX\VistaMare\bin\ViMaIScnX_AP.dll
LoadedModule[220]=C:\1-FSX\GAUGES\PMDG_737NGX.DLL
LoadedModule[221]=C:\Windows\system32\NETAPI32.dll
LoadedModule[222]=C:\Windows\system32\srvcli.dll
LoadedModule[223]=C:\Windows\system32\wkscli.dll
LoadedModule[224]=C:\Windows\system32\WSOCK32.dll
LoadedModule[225]=C:\Windows\system32\MSVCP100.dll
LoadedModule[226]=C:\Windows\SysWow64\XAudio2_7.dll
LoadedModule[227]=C:\1-FSX\FS2Crew2010\Versions\PMDG737NGXRB\Gauges\FS2CrewNGXRB.GAU
LoadedModule[228]=C:\1-FSX\libcurl.dll
LoadedModule[229]=C:\Windows\system32\FS2AUDIO.dll
LoadedModule[230]=C:\Windows\system32\napinsp.dll
LoadedModule[231]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[232]=C:\Windows\System32\winrnr.dll
LoadedModule[233]=C:\Windows\system32\msadp32.acm
LoadedModule[234]=C:\1-FSX\Gauges\PMDG_737NGX_2.dll
LoadedModule[235]=C:\Windows\system32\snmpapi.dll
LoadedModule[236]=C:\Windows\system32\icmp.Dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped responding and was closed
ConsentKey=AppHangXProcB1
AppName=Microsoft Flight Simulator®
AppPath=C:\1-FSX\fsx.exe
ReportDescription=A problem caused this program to stop interacting with Windows.
 

Share this post


Link to post
Share on other sites

Google AppHangB1, there are a lot of articles online concerning this. As a last resort install one addon at a time, speed some time flying then add another addon and see if you can isolate the one that might be causing the problem. 

I get them occasionally and did a couple of the suggestion I found online and it helped, haven't had a crash in sometime.

Good luck, I know how frustrating they are!

Share this post


Link to post
Share on other sites

AppHang's are discussed under probable solutions for Freezes.

Best regards,

Jim

Share this post


Link to post
Share on other sites

Thanks gentleman for your patients and responses. I have once considered myself savvy on the topic of FSX crashes to where I fixed it and not an issue for years. I do know what I did, but it seams like the apphangB1 crash is without definitive resolution, and it is probably safe to say some time of process handshake between FSX and Windows is causing the crash, almost like a timeout error. I made some minor adjustments tonight (Edited FSX.EXE to start maximized, bufferpools/ usepools=0 in fsx.cfg, plus the vsync fixes. Additionally, I threw in the correct UIAutomationcore.DLL in my main FSX directory. I'll try setting up some flights in the morning before work to see if I get any more crashes. In the mean time, I'm totally open to any advice or recommandations.

Thanks,

David

Share this post


Link to post
Share on other sites

Update: Apparently I made have had the incorrect UIAutomationcore.dll in my FSX directory. I downloaded the UIAutomationcore.dll ending in 1800. I was able to successfully load a flight without a crash, which unfortunately at this point is quite an accomplishment. 

Share this post


Link to post
Share on other sites

If you have Windows 10 or Windows 8.1, you will need one of the old versions in your main FSX directory.  I never required it when I was using Windows 7 and earlier.  But just recently upgraded to Windows 10 and the crashes began.  Thanks to SteveW for setting me straight (for the first time in my life).  LOL

Glad you were able to find the solution to your problem.

Best regards,

Jim

Share this post


Link to post
Share on other sites
8 hours ago, Jim Young said:

If you have Windows 10 or Windows 8.1, you will need one of the old versions in your main FSX directory.  I never required it when I was using Windows 7 and earlier.  But just recently upgraded to Windows 10 and the crashes began.  Thanks to SteveW for setting me straight (for the first time in my life).  LOL

Glad you were able to find the solution to your problem.

Best regards,

Jim

Btw for Windows 7 64 which is the official correct uiautomationcore.dll? I had the one with the last set of numbers beginning with 6. I was crashing everytime. With the 1800, it appeared stable (For now).

Share this post


Link to post
Share on other sites

I use the 32 bit version of the 16386 version.  Since FSX and P3D are 32 bit applications, you must use the 32 bit version.  I would continue to use the 18000 version until you get a crash with uiautomationcore.dll as the faulting module.  Then try the 16386.  Either version should work.

Best regards,

Jim

Share this post


Link to post
Share on other sites
On May 9, 2017 at 7:15 AM, Jim Young said:

In the AVSIM CTD Guide, around page 10, look for how to fix most FSX CTD's and Freezes.  See link in my signature.

You did not indicate where you are getting the freezes.  At startup?  While loading?  During a flight?  If it was at startup, most like you have an out of date module, like FSUIPC or one of the other modules in your dll.xml.  Disable your dll.xml and restart FSX and see if this fixes the problem.  You should never ever reinstall FSX/Acceleration.  Deleting or renaming your FSX.cfg and then restarting FSX is like reinstalling FSX.  Individuals just put too much junk (tweaks) in their FSX.cfg.  High settings, a monitor not being identified, sound card not being identified properly, etc., etc.

Best regards,

Jim

 

Thanks for your reply Jim. I gave up, uninstalled and removed all traces of FSX. I reinstalled using Nickn's bible. So far so good with a few apphangb1 crashes. I'm thinking maybe running a CCleaner registry scan, maybe that is the root cause. 

Share this post


Link to post
Share on other sites

Still apphangb1 central. Things I've done: 

- Tested memory (Passed)

-Scanned Windows 2x's (sfc/scan) - no errors/no missing or corrupt dlls

-updated video card drivers

- directx updated

-tried 3 different uiautomationcore.dlls; 18000, 16386, and the one in my win32 folder (16385). 

One thing to keep in mind, I performed a careful, sterile FSX reinstall after removing any trace of FSX or its addons from anywhere on my hard drive. No other program has an indicated apphangb1 crash, however I know the crash is due to hanging between Windows and FSX itself. I'm at a total loss. As a reminder, I'm operating Windows 7 64. Lol please help!

 

 

 

 

Share this post


Link to post
Share on other sites

If you are overclocked, remove the overclock and go to the optimal defaults.  The fact you reinstalled FSX "carefully" and still get the crash indicates to me it is your hardware or overclock.  The fact the apphangb1 occurred while running FSX does not indicate it is the fault of FSX.  FSX just happened to hang up when something in your system caused a hangup. 

Where does it hang up at?  Before you get to the setup screen?  Before you get to the page where FSX is ready to fly?  Did it happen during a flight.

What aircraft were you using?  Where were you flying from/to?

Did it hang at exactly the same spot?

When you reinstalled the "sterile" fsx, did you replace your scenery.cfg with your old scenery.cfg and your fsx.cfg with your old fsx.cfg? 

NickN's "Bible" has flaws in it.  Did you try to install his tweaks?  Don't.

34 minutes ago, davidzill said:

-tried 3 different uiautomationcore.dlls; 18000, 16386, and the one in my win32 folder (16385). 

This is strange.  the 18000 and the 16386 versions are the really old versions that some recommend placing in your main fsx folder (but you should not with Windows 7; only Windows 8.1 or Windows 10 users).  The win32 folder... What is that?  I cannot find it on my computer.  I have a uiautomationcore.dll in my System32 (v93479) and the same version in SysWow64 folder.  This is part of the Microsoft.net package and is used by Windows to run applications.

As stated in the AVSIM CTD Guide, you need the old Microsoft Visuals 2005 w/SP1 installed (there's an image on what needs to be installed and the versions.  You need Microsoft.net 2.0 or Microsoft dotnet 1.1 (page 24).  FSX will not run if this Microsoft Visual and Microsoft.net is not installed.  The latest version will not work.

Best regards,

Jim

Share this post


Link to post
Share on other sites

Forgot to mention that the Microsoft.net version you stated was in your Win32 folder is one less version than the really old 2005 version.  You didn't put an old version of the uiautomationcore.dll in your System32 folder did you?

Share this post


Link to post
Share on other sites
46 minutes ago, Jim Young said:

Forgot to mention that the Microsoft.net version you stated was in your Win32 folder is one less version than the really old 2005 version.  You didn't put an old version of the uiautomationcore.dll in your System32 folder did you?

Jim, everything is updated, non-corrupted, good to go. I am having no issues with other programs like DCS, etc. Apphangb1 now happens 100% of the time within about a minute. I did't place a UIautomation.dll anywhere, the one in sys32 is: 6.1.7600.16385, size 733kb, dated 7/13/09. I doubt the issue is related to uiautomationcore.dll due to the similarity/time of the issue no matter which one is in there. Net framework is up to date, visual is up to date, dirext x installed is 11. The apphangb1 freeze manifest itself either during the loading of the flight or initialization of the PMDG NGX. If I switch to windowed mode and open an addon program sush as GSX, EZCA, etc, I usually get a hang as well. 

Share this post


Link to post
Share on other sites

You need to run the Microsoft.net Repair Tool and make sure you have versions 2.0 and the latest version installed.  You might be able to see this if you look in Windows/Microsoft.net/Framework and look at the versions installed (X86).

FSX does not use DX11 even though your video card is capable of running DX11.  FSX can run DX9 and DX10 if you have SP2 or Acceleration installed.

When you startup FSX, the first thing to load is the modules loaded by your dll.xml.  Might give you a hint as to what is causing your crashes.  Again, FSX will not even start up if you do not have Microsoft Visual C++ 2005 installed and/or Microsoft.net 2.0. 

Best regards,

Jim

 

Share this post


Link to post
Share on other sites

So last night I had a good run, I loaded a flight, and changed locations several times trying to indice an apphang...didn't happen. I exited and reopened FSX about 6 times, each time loading a different complex aircraft (PMDG) in different HIFI airports; no crashes. Today I start my computer and can't even load a flight anywhere without an apphangb1. 

Share this post


Link to post
Share on other sites

Based upon all the material I have read regarding the apphangB1 crash, I'm convinced its an issue outside of FSX and inside windows. Notably, sometimes when I boot into windows 7 64 the last 1.5 weeks, I have been receiving a warning message on screen: AisuiteIII: Access violation at address 002AA689. Read of address 002AA689. Almost every time I see that, I get apphangb1's in FSX. Most of the time, if not all the time, if I don't see that message, I only get apphangb1's if I push FSX to. Also, when I don't get the message, the FSX flight set up screen is much more responsive. I think I'm getting closer to resolving this. I have a feeling this may be related to the most recent nvidia drivers.  

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