January 14, 201412 yr Hi all, first of all excuse my English, it's not my native language! I'm facing a strange but very annoying problem after reinstalling FSX end of December on an almost fresh (end of November) Win7 64bit installation. Never had that before with old hardware and same OS & FSX addons. Quick description: everything runs fine if I do not use 2 specific addons that both hangs FSX at specific time with the AppHangB1 Event Type. The 2 addons are "FSPS Ultimate Checklist" and "AivlaSoft EFB". FSPS Ultimate Checklist has the ability to "connect" to FSX in order to intercept key presses (defined in FSUIPC as Offset Byte Setbits controls) to advance checklist items and show the "progressed" check list in FSX in a LUA window. The crash happens after a random (a few, between 2 and 5-7 max) number of keypresses, exactly after the external app receives the command and therefore just before the LUA display is updated. In AivlaSoft EFB the crash happen after a random number of SID/STAR activation. Exactly when I use the "activate" button of the display unit. My inspections suggest there could be something wrong with SimConnect or FSUIPC but I haven't been able to reduce or change the problem neither going through the AVSIM CTD guide and neither applying a few random fix loosely related (i.e. uiautomationcore.dll, disabling firewall). Also note that the problem was still there after a complete FSX disintall, registry clean and following reinstall of FSX, with just FSUIPC and FSPS Ultimate Checklist installed - with the basic fsx.cfg generated after the installation. As an additional note I always use FSX windowed @ 1920x1080 on one of my 2 monitors. If avoid using the 2 addons, or avoid using them as specified everything works fine. To me it looks something system-related, so I refrained to ask individual support to the addon vendors, whose support forums doesn't show anything somehow similar to what I'm experiencing... Any idea for further investigation beside reinstalling the OS - last resort if nothing else will work? AppCrash View details example: Version=1 EventType=AppHangB1 EventTime=130341877455193279 ReportType=3 Consent=1 ReportIdentifier=76acda52-7d32-11e3-befe-08606e87f286 IntegratorReportIdentifier=76acda53-7d32-11e3-befe-08606e87f286 WOW64=1 Response.type=4 Sig[0].Name=Nome applicazione Sig[0].Value=fsx.exe Sig[1].Name=Versione applicazione Sig[1].Value=10.0.61472.0 Sig[2].Name=Timestamp applicazione Sig[2].Value=475e17d3 Sig[3].Name=Firma di blocco Sig[3].Value=b529 Sig[4].Name=Tipo interruzione Sig[4].Value=517 DynamicSig[1].Name=Versione SO DynamicSig[1].Value=6.1.7601.2.1.0.768.3 DynamicSig[2].Name=ID impostazioni locali DynamicSig[2].Value=1040 DynamicSig[22].Name=Firma blocco aggiuntiva 1 DynamicSig[22].Value=b529f17e82491225480867debdeaabb9 DynamicSig[23].Name=Firma blocco aggiuntiva 2 DynamicSig[23].Value=d2f5 DynamicSig[24].Name=Firma blocco aggiuntiva 3 DynamicSig[24].Value=d2f5f88d0e6a0ce2054f32ca84fa721c DynamicSig[25].Name=Firma blocco aggiuntiva 4 DynamicSig[25].Value=b529 DynamicSig[26].Name=Firma blocco aggiuntiva 5 DynamicSig[26].Value=b529f17e82491225480867debdeaabb9 DynamicSig[27].Name=Firma blocco aggiuntiva 6 DynamicSig[27].Value=d2f5 DynamicSig[28].Name=Firma blocco aggiuntiva 7 DynamicSig[28].Value=d2f5f88d0e6a0ce2054f32ca84fa721c UI[3]=Microsoft Flight Simulator® non risponde UI[4]=Windows: è possibile cercare una soluzione online. Se si chiude il programma, si potrebbero perdere alcune informazioni. UI[5]=Cerca una soluzione e chiudi il programma UI[6]=Cerca una soluzione e chiudi il programma UI[7]=Chiudi il programma LoadedModule[0]=E:\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\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.18201_none_ec80f00e8593ece5\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\MFC80ITA.DLL LoadedModule[60]=E:\FSX\language.dll LoadedModule[61]=E:\FSX\API.DLL LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[63]=E:\FSX\ablscpt.dll LoadedModule[64]=E:\FSX\flight.dll LoadedModule[65]=E:\FSX\ai_player.dll LoadedModule[66]=E:\FSX\acontain.dll LoadedModule[67]=E:\FSX\controls.dll LoadedModule[68]=C:\Windows\system32\DINPUT8.dll LoadedModule[69]=E:\FSX\fsui.dll LoadedModule[70]=E:\FSX\atc.dll LoadedModule[71]=E:\FSX\facilities.dll LoadedModule[72]=E:\FSX\demo.dll LoadedModule[73]=E:\FSX\main.dll LoadedModule[74]=E:\FSX\fe.dll LoadedModule[75]=E:\FSX\util.dll LoadedModule[76]=E:\FSX\simprop.dll LoadedModule[77]=E:\FSX\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]=E:\FSX\g3d.dll LoadedModule[83]=E:\FSX\panels.dll LoadedModule[84]=E:\FSX\multiplayer.dll LoadedModule[85]=E:\FSX\ui.dll LoadedModule[86]=E:\FSX\sound.dll LoadedModule[87]=E:\FSX\sim1.dll LoadedModule[88]=E:\FSX\simscheduler.dll LoadedModule[89]=E:\FSX\visualfx.dll LoadedModule[90]=E:\FSX\window.dll LoadedModule[91]=E:\FSX\terrain.dll LoadedModule[92]=E:\FSX\weather.dll LoadedModule[93]=C:\Windows\system32\DSOUND.dll LoadedModule[94]=C:\Windows\system32\POWRPROF.dll LoadedModule[95]=E:\FSX\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]=E:\FSX\xuipc.dll LoadedModule[99]=E:\FSX\livingwater.dll LoadedModule[100]=E:\FSX\fs-traffic.dll LoadedModule[101]=E:\FSX\gps.dll LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll LoadedModule[104]=C:\Program Files (x86)\TeamViewer\Version9\tv_w32.dll LoadedModule[105]=C:\Windows\system32\CRTDLL.dll LoadedModule[106]=C:\Windows\system32\RICHED20.DLL LoadedModule[107]=C:\Windows\system32\CRYPTSP.dll LoadedModule[108]=C:\Windows\system32\rsaenh.dll LoadedModule[109]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[110]=C:\Windows\system32\dxgi.dll LoadedModule[111]=C:\Windows\system32\d3d11.dll LoadedModule[112]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[113]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[114]=C:\Windows\syswow64\MSASN1.dll LoadedModule[115]=C:\Windows\system32\nvd3dum.dll LoadedModule[116]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[117]=C:\Windows\system32\nvspcap.dll LoadedModule[118]=C:\Windows\system32\nvapi.dll LoadedModule[119]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[120]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[121]=C:\Windows\system32\d3d10_1.dll LoadedModule[122]=C:\Windows\system32\d3d10_1core.dll LoadedModule[123]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[124]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[125]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[126]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[127]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[128]=c:\windows\syswow64\wbem\wbemprox.dll LoadedModule[129]=C:\Windows\system32\wbemcomn.dll LoadedModule[130]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[131]=c:\windows\syswow64\wbem\wbemsvc.dll LoadedModule[132]=c:\windows\syswow64\wbem\fastprox.dll LoadedModule[133]=C:\Windows\system32\NTDSAPI.dll LoadedModule[134]=C:\Windows\system32\winbrand.dll LoadedModule[135]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[136]=C:\Windows\system32\WINSTA.dll LoadedModule[137]=C:\Windows\SysWOW64\gameux.dll LoadedModule[138]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[139]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[140]=C:\Windows\SysWOW64\wer.dll LoadedModule[141]=C:\Windows\System32\Wpc.dll LoadedModule[142]=C:\Windows\System32\wevtapi.dll LoadedModule[143]=C:\Windows\System32\msxml6.dll LoadedModule[144]=C:\Windows\system32\SAMLIB.dll LoadedModule[145]=C:\Windows\system32\netutils.dll LoadedModule[146]=C:\Windows\system32\uiautomationcore.dll LoadedModule[147]=C:\Windows\system32\OLEACC.dll LoadedModule[148]=C:\Windows\System32\MMDevApi.dll LoadedModule[149]=C:\Windows\System32\PROPSYS.dll LoadedModule[150]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[151]=C:\Windows\system32\HID.DLL LoadedModule[152]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[153]=C:\Windows\system32\wdmaud.drv LoadedModule[154]=C:\Windows\system32\ksuser.dll LoadedModule[155]=C:\Windows\system32\AVRT.dll LoadedModule[156]=C:\Windows\system32\msacm32.drv LoadedModule[157]=C:\Windows\system32\midimap.dll LoadedModule[158]=C:\Windows\system32\dinput.DLL LoadedModule[159]=C:\Windows\System32\wship6.dll LoadedModule[160]=C:\Windows\System32\wshtcpip.dll LoadedModule[161]=E:\FSX\Modules\FSUIPC4.dll LoadedModule[162]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[163]=C:\Windows\system32\WINNSI.DLL LoadedModule[164]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[165]=E:\FSX\FSCaptain\bin\FSCaptain.dll LoadedModule[166]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dll LoadedModule[167]=C:\Windows\system32\WSOCK32.dll LoadedModule[168]=E:\FSX\FSCaptain\bin\GaugeSound.DLL LoadedModule[169]=C:\Windows\system32\msadp32.acm LoadedModule[170]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[171]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll LoadedModule[172]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll LoadedModule[173]=C:\Windows\system32\Secur32.dll LoadedModule[174]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll LoadedModule[175]=C:\Windows\SysWOW64\mshtml.dll LoadedModule[176]=C:\Windows\system32\msimtf.dll LoadedModule[177]=C:\Windows\system32\msls31.dll LoadedModule[178]=C:\Windows\system32\d2d1.dll LoadedModule[179]=C:\Windows\system32\DWrite.dll LoadedModule[180]=C:\Windows\system32\D3D10Warp.dll LoadedModule[181]=C:\Windows\system32\MLANG.dll LoadedModule[182]=C:\Windows\system32\ntmarta.dll LoadedModule[183]=C:\Windows\syswow64\WLDAP32.dll FriendlyEventName=Non risponde più ed è stato chiuso ConsentKey=AppHangXProcB1 AppName=Microsoft Flight Simulator® AppPath=E:\FSX\fsx.exe ReportDescription=Si è verificato un problema che impedisce al programma di interagire con Windows. Marco Manieri Perugia - Italy
January 14, 201412 yr Uninstall SP2 and SP1. Reinstall SP1, run fsx for at least one time. Reinstall SP2. To uninstall SP2 and SP1, doubleclick on the apps and select remove for SP2.exe and SP1.exe. If it does not give you the option to remove, then you will have to do a complete repair of FSX by inserting the FSX disk one and selecting the repair option. Do the same for SP1 and SP2 then restart FSX. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 14, 201412 yr Author Also note that the problem was still there after a complete FSX disintall, registry clean and following reinstall of FSX, with just FSUIPC and FSPS Ultimate Checklist installed Hi Jim, thanks a lot for you time. Both first install and the reinstall mentioned above where done running FSX (starting the default flight) at least once before applying each SP. So I guess a third reinstall/repair would be useless.. Marco Manieri Perugia - Italy
January 14, 201412 yr Hi Marco, The reasons for this are too many, but i would check FSUIPC and Simconnect first. - Check that you have the latest version of FSUIPC http://forum.simflight.com/topic/66139-updated-modules/ - Check that you have correct(for your FSX version)and latest version of simconnect: http://www.fsdeveloper.com/wiki/index.php?title=SDK_Installation_(FSX) I would check for errors FSUIPC and Simconnect logs too. Some friend solved his AppHangB1 after installing VCRedist C++, he forgot to do this during fsx installation. If you don't have it, install only "ENU (vcredist_x86.exe)" from this list: http://archive.msdn.microsoft.com/KB961894/Release/ProjectReleases.aspx?ReleaseId=2067 All the best Zeljko P.S. Jim, i'm back. Missed this forums... Zeljko Budovic
January 15, 201412 yr Author Hi Zeljko and thanks for your time, much appreciated.- PSUIPC was 4.927a 18th Dec 2013, updated to 4.928, no changes.- the link refers to FSX SDK SP2 installation. I do have it already installed but can't figure out how that pages helps me checking correct and latest version of simconnect?FSUIPC and Simconnect logs show no errors, they just "stop" at the hang time (logs here).Regarding VCRedist C++ I do have this in installed list from control panel (Not listed the x64 since I guess they are uninfluent):2005 8.0.610012005 8.0.50727.422008 9.0.30729.172008 9.0.30729.61612010 10.0.40219Do you think I'd better download and install from the page you linked? In case do you confirm the ENU or should I go with my OS language (ITA)?Thanks once again! Marco Manieri Perugia - Italy
January 15, 201412 yr Jim, i'm back. Missed this forums... Welcome back Zeljko! I was wondering where you were and thinking about sending a PM. Glad to see you're back. Any help here in the CTD Forum is greatly appreciated. Jim Hi Jim,thanks a lot for you time. Both first install and the reinstall mentioned above where done running FSX (starting the default flight) at least once before applying each SP. So I guess a third reinstall/repair would be useless.. This is true but, did you reinstall with Administrator privileges (i.e., right click the .exe and select Run as Administrator)? Did you shutdown or disable your Anti-virus program? It sounds to me you might be having sharing issues. Right click the Main FSX folder and make sure it is properly shared. These new systems with all of this security is killing the older applications. According to your crash report you have the latest Microsoft Visuals installed (MSV2005 w/sp1). MSV2008 did not load so none of the fsx products you have installed needed it? Based on your most recent post, Microsoft Visual 2008 is the most recent but it did not load as probably not needed by any of the apps. Also check to make sure you have Microsoft.net framework versions 1.1 thru at least 3.5 installed. (See the AVSIM CTD Guide about Microsoft.net verifications). Simconnect is installed properly and the latest version. AppHang's are very difficult to diagnose. We can only provide suggestions. AivlaSoft EFB was recently updated to 1.5 so make sure you have that version installed. It appears to me you have narrowed the issues down with the freezing to either AivlaSoft EFB and/or the FSPS Ultimate Checklists. So FSX w/SP2 works perfectly when not using these modules? I do know that if you have two monitors and you move a program to the secondary monitor, FSX will crash 100% of the time if you try to move or reposition the items on the second monitor. If that's what you are doing, you can't do it. The programs you have installed were made for one monitor (or one big wide-screen multiple monitors). You can do it for a bit but do not touch the item in the secondary monitor to try to resize it or move it. It will crash FSX. Hope this helps. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
January 15, 201412 yr Author I always disable UAC on new OS installs so I usually don't run installers as Administrator. I also have not disabled the AV (MS Security Essentials) during FSX & SPs installs. Will keep these indication good for when I'll eventually be forced to a complete OS reinstall if nothing else will help. I think I properly shared the FSX folder and after that I also tried the "howtogeek takeownership" tool on it. Microsoft.net framework versions already checked when going through the guide. AivlaSoft EFB version is 1.5.0. And yes, FSX w/SP2 works perfectly when not using these modules. What most puzzles me is that not only everything runs fine with other modules/addons (FlightSim Commander, FSCaptian, OpusFSX, PlangG) but nothing happens and I can fly happily with both EFB and UC running just avoiding the 2 specific actions ... I do know that if you have two monitors and you move a program to the secondary monitor, FSX will crash 100% of the time if you try to move or reposition the items on the second monitor. If that's what you are doing, you can't do it. The programs you have installed were made for one monitor (or one big wide-screen multiple monitors). You can do it for a bit but do not touch the item in the secondary monitor to try to resize it or move it. It will crash FSX. Uhm.. FSX opens in the primary monitor. I then launch my addons from desktop icons in the secondary monitor and all those that have an individual window popup in the secondary display. Only exception is the FSXSERVER window of OpusFSX that for some reason always pops up in front of the FSX window on the main monitor, but I always moved it to the secondary without any issue. By the way I've now also posted my issue on the 2 vendors suport forums, if nothing else jump up I think I'll disinstall FSX & everything related and then try a dual boot OS installation to have just a fresh Win7 + FSX installation on the SDD dedicated to FSX... Thanks a lot for taking again time for this "battle"! Marco Manieri Perugia - Italy
January 16, 201412 yr Author Just FYI it looks like I might have found the common denominator of the hangs: both addons write a file at the exact time where I get the hangs. Ultimate Checklist writes a lua script and then issue a command to FSX to execute it while EFB writes a flight plan and issue a command to FSX to load it... Now I'll investigate around this ... Marco Manieri Perugia - Italy
January 27, 201412 yr Author Just for the records, the issue was only fixed with a complete O.S. reinstall... :( Marco Manieri Perugia - Italy
January 27, 201412 yr Thanks Marco for posting your solution. I had a nasty StackHash crash that wouldn't go away a year or two ago and fixed it by reinstalling the OS and FSX. After the reinstall I found the solution to the original problem and it was a simply one which did not require reinstallation of everything yet I was happy I reinstalled everything as I was able to clean up an old installation. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
Create an account or sign in to comment