September 29, 201312 yr Hi! My FSX was running quite fine for while. In the last months I bought a couple of Add ons, FTX, Kig Air 200, lbeo Tomahawk ad now the PMDG 777. By now I was not able to comlete one flight. always airborn after 15 up to 3 hours I get a blue Screen or a CTD. I tried to minimize the SCENERy, I reduced, the visual Settings, I treda couple of advice frrrrrm te Forum, nothing helps. I hope, someone can help me. This is the last crash Report. Version=1EventType=APPCRASHEventTime=130242522964559114ReportType=2Consent=1UploadTime=130242522965109146ReportIdentifier=b19b4850-22d5-11e3-a898-00268315ae9eIntegratorReportIdentifier=b19b484f-22d5-11e3-a898-00268315ae9eWOW64=1Response.BucketId=2489183190Response.BucketTable=1Response.type=4Sig[0].Name=AnwendungsnameSig[0].Value=fsx.exeSig[1].Name=AnwendungsversionSig[1].Value=10.0.61637.0Sig[2].Name=AnwendungszeitstempelSig[2].Value=46fadb14Sig[3].Name=FehlermodulnameSig[3].Value=MSVCR80.dllSig[4].Name=FehlermodulversionSig[4].Value=8.0.50727.6195Sig[5].Name=FehlermodulzeitstempelSig[5].Value=4dcddbf3Sig[6].Name=AusnahmecodeSig[6].Value=c0000005Sig[7].Name=AusnahmeoffsetSig[7].Value=0001500aDynamicSig[1].Name=BetriebsystemversionDynamicSig[1].Value=6.1.7601.2.1.0.768.3DynamicSig[2].Name=Gebietsschema-IDDynamicSig[2].Value=3079UI[2]=E:\FSX\fsx.exeUI[3]=Ein schwerwiegender Fehler ist aufgetreten.UI[4]=Windows kann online nach einer Lösung für das Problem suchen und versuchen, das Programm neu zu starten.UI[5]=Online nach einer Lösung suchen und das Programm neu startenUI[6]=Später online nach einer Lösung suchen und das Programm schließenUI[7]=Programm schließenLoadedModule[0]=E:\FSX\fsx.exeLoadedModule[1]=C:\Windows\SysWOW64\ntdll.dllLoadedModule[2]=C:\Windows\syswow64\kernel32.dllLoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dllLoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLLLoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dllLoadedModule[6]=C:\Windows\syswow64\msvcrt.dllLoadedModule[7]=C:\Windows\syswow64\GDI32.dllLoadedModule[8]=C:\Windows\syswow64\USER32.dllLoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dllLoadedModule[10]=C:\Windows\SysWOW64\sechost.dllLoadedModule[11]=C:\Windows\syswow64\RPCRT4.dllLoadedModule[12]=C:\Windows\syswow64\SspiCli.dllLoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dllLoadedModule[14]=C:\Windows\syswow64\LPK.dllLoadedModule[15]=C:\Windows\syswow64\USP10.dllLoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dllLoadedModule[17]=C:\Windows\syswow64\ole32.dllLoadedModule[18]=C:\Windows\system32\apphelp.dllLoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLLLoadedModule[20]=C:\Windows\system32\UxTheme.dllLoadedModule[21]=C:\Windows\system32\WINMM.dllLoadedModule[22]=C:\Windows\system32\samcli.dllLoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dllLoadedModule[24]=C:\Windows\system32\MSACM32.dllLoadedModule[25]=C:\Windows\system32\VERSION.dllLoadedModule[26]=C:\Windows\syswow64\SHELL32.dllLoadedModule[27]=C:\Windows\system32\sfc.dllLoadedModule[28]=C:\Windows\system32\sfc_os.DLLLoadedModule[29]=C:\Windows\system32\USERENV.dllLoadedModule[30]=C:\Windows\system32\profapi.dllLoadedModule[31]=C:\Windows\system32\dwmapi.dllLoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dllLoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dllLoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dllLoadedModule[35]=C:\Windows\syswow64\urlmon.dllLoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dllLoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dllLoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dllLoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dllLoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dllLoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dllLoadedModule[42]=C:\Windows\syswow64\normaliz.DLLLoadedModule[43]=C:\Windows\syswow64\iertutil.dllLoadedModule[44]=C:\Windows\syswow64\WININET.dllLoadedModule[45]=C:\Windows\system32\MPR.dllLoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLLLoadedModule[47]=C:\Windows\system32\WINSPOOL.DRVLoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLLLoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dllLoadedModule[50]=C:\Windows\system32\mscms.dllLoadedModule[51]=C:\Windows\system32\DDRAW.dllLoadedModule[52]=C:\Windows\system32\DCIMAN32.dllLoadedModule[53]=C:\Windows\syswow64\COMDLG32.dllLoadedModule[54]=C:\Windows\syswow64\IMM32.dllLoadedModule[55]=C:\Windows\syswow64\MSCTF.dllLoadedModule[56]=C:\Windows\syswow64\WS2_32.dllLoadedModule[57]=C:\Windows\syswow64\NSI.dllLoadedModule[58]=C:\Windows\system32\msi.dllLoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80DEU.DLLLoadedModule[60]=E:\FSX\language.dllLoadedModule[61]=E:\FSX\API.DLLLoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dllLoadedModule[63]=E:\FSX\ablscpt.dllLoadedModule[64]=E:\FSX\flight.dllLoadedModule[65]=E:\FSX\ai_player.dllLoadedModule[66]=E:\FSX\acontain.dllLoadedModule[67]=E:\FSX\controls.dllLoadedModule[68]=C:\Windows\system32\DINPUT8.dllLoadedModule[69]=E:\FSX\fsui.dllLoadedModule[70]=E:\FSX\atc.dllLoadedModule[71]=E:\FSX\facilities.dllLoadedModule[72]=E:\FSX\demo.dllLoadedModule[73]=E:\FSX\main.dllLoadedModule[74]=E:\FSX\fe.dllLoadedModule[75]=E:\FSX\util.dllLoadedModule[76]=E:\FSX\simprop.dllLoadedModule[77]=E:\FSX\g2d.dllLoadedModule[78]=C:\Windows\system32\d3dx9_34.dllLoadedModule[79]=C:\Windows\system32\d3dx10_34.dllLoadedModule[80]=C:\Windows\system32\d3d9.dllLoadedModule[81]=C:\Windows\system32\d3d8thk.dllLoadedModule[82]=E:\FSX\g3d.dllLoadedModule[83]=E:\FSX\panels.dllLoadedModule[84]=E:\FSX\multiplayer.dllLoadedModule[85]=E:\FSX\ui.dllLoadedModule[86]=E:\FSX\sound.dllLoadedModule[87]=E:\FSX\sim1.dllLoadedModule[88]=E:\FSX\simscheduler.dllLoadedModule[89]=E:\FSX\visualfx.dllLoadedModule[90]=E:\FSX\window.dllLoadedModule[91]=E:\FSX\terrain.dllLoadedModule[92]=E:\FSX\weather.dllLoadedModule[93]=C:\Windows\system32\DSOUND.dllLoadedModule[94]=C:\Windows\system32\POWRPROF.dllLoadedModule[95]=E:\FSX\symmap.dllLoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dllLoadedModule[97]=C:\Windows\system32\MSIMG32.dllLoadedModule[98]=E:\FSX\xuipc.dllLoadedModule[99]=E:\FSX\livingwater.dllLoadedModule[100]=E:\FSX\fs-traffic.dllLoadedModule[101]=E:\FSX\gps.dllLoadedModule[102]=C:\Windows\system32\MSWSOCK.dllLoadedModule[103]=C:\Windows\system32\SHFOLDER.dllLoadedModule[104]=C:\Windows\system32\CRYPTSP.dllLoadedModule[105]=C:\Windows\system32\rsaenh.dllLoadedModule[106]=C:\Windows\syswow64\WINTRUST.dllLoadedModule[107]=C:\Windows\syswow64\CRYPT32.dllLoadedModule[108]=C:\Windows\syswow64\MSASN1.dllLoadedModule[109]=C:\Windows\syswow64\CLBCatQ.DLLLoadedModule[110]=C:\Windows\system32\wbem\wbemprox.dllLoadedModule[111]=C:\Windows\system32\wbemcomn.dllLoadedModule[112]=C:\Windows\system32\RpcRtRemote.dllLoadedModule[113]=C:\Windows\system32\wbem\wbemsvc.dllLoadedModule[114]=C:\Windows\system32\wbem\fastprox.dllLoadedModule[115]=C:\Windows\system32\NTDSAPI.dllLoadedModule[116]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLLLoadedModule[117]=C:\Windows\system32\dxgi.dllLoadedModule[118]=C:\Windows\system32\d3d11.dllLoadedModule[119]=C:\Windows\system32\nvd3dum.dllLoadedModule[120]=C:\Windows\syswow64\PSAPI.DLLLoadedModule[121]=C:\Windows\system32\D3DCompiler_34.dllLoadedModule[122]=C:\Windows\system32\WindowsCodecs.dllLoadedModule[123]=C:\Windows\system32\d3d10_1.dllLoadedModule[124]=C:\Windows\system32\d3d10_1core.dllLoadedModule[125]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dllLoadedModule[126]=C:\Windows\SysWOW64\dxdiagn.dllLoadedModule[127]=C:\Windows\SysWOW64\d3d10.dllLoadedModule[128]=C:\Windows\SysWOW64\d3d10core.dllLoadedModule[129]=C:\Windows\system32\winbrand.dllLoadedModule[130]=C:\Windows\system32\nvapi.dllLoadedModule[131]=C:\Windows\system32\WTSAPI32.DLLLoadedModule[132]=C:\Windows\system32\WINSTA.dllLoadedModule[133]=C:\Windows\SysWOW64\gameux.dllLoadedModule[134]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dllLoadedModule[135]=C:\Windows\SysWOW64\XmlLite.dllLoadedModule[136]=C:\Windows\SysWOW64\wer.dllLoadedModule[137]=C:\Windows\System32\Wpc.dllLoadedModule[138]=C:\Windows\System32\wevtapi.dllLoadedModule[139]=C:\Windows\System32\msxml6.dllLoadedModule[140]=C:\Windows\system32\SAMLIB.dllLoadedModule[141]=C:\Windows\system32\netutils.dllLoadedModule[142]=E:\FSX\uiautomationcore.dllLoadedModule[143]=C:\Windows\system32\OLEACC.dllLoadedModule[144]=C:\Windows\System32\MMDevApi.dllLoadedModule[145]=C:\Windows\System32\PROPSYS.dllLoadedModule[146]=C:\Windows\system32\AUDIOSES.DLLLoadedModule[147]=C:\Windows\system32\RICHED20.DLLLoadedModule[148]=C:\Windows\system32\HID.DLLLoadedModule[149]=C:\Windows\system32\XInput9_1_0.dllLoadedModule[150]=C:\Windows\system32\wdmaud.drvLoadedModule[151]=C:\Windows\system32\ksuser.dllLoadedModule[152]=C:\Windows\system32\AVRT.dllLoadedModule[153]=C:\Windows\system32\msacm32.drvLoadedModule[154]=C:\Windows\system32\midimap.dllLoadedModule[155]=C:\Windows\system32\dinput.DLLLoadedModule[156]=C:\Windows\System32\wship6.dllLoadedModule[157]=C:\Windows\System32\wshtcpip.dllLoadedModule[158]=E:\FSX\bglmanx.dllLoadedModule[159]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dllLoadedModule[160]=E:\FSX\VistaMare\ViMaCoreX.dllLoadedModule[161]=E:\FSX\VistaMare\bin\VMCX_AP.dllLoadedModule[162]=E:\FSX\VistaMare\bin\ViMaNET_AP.dllLoadedModule[163]=E:\FSX\PMDG\DLLs\PMDGOptions.dllLoadedModule[164]=E:\FSX\PMDG_SimConnect_Ldr.dllLoadedModule[165]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dllLoadedModule[166]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dllLoadedModule[167]=C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dllLoadedModule[168]=C:\Windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_49768ef57548175e\MFC90DEU.DLLLoadedModule[169]=E:\FSX\PMDG\DLLs\PMDGEvents.dllLoadedModule[170]=E:\FSX\PMDG\DLLs\PMDGSounds.dllLoadedModule[171]=E:\FSX\WaveLib.dllLoadedModule[172]=E:\FSX\PMDG\DLLs\PMDG_HUD_interface.dllLoadedModule[173]=C:\Windows\system32\MSVCR100.dllLoadedModule[174]=E:\FSX\Aerosoft\Flight Recorder\AS-FlightRecorder.dllLoadedModule[175]=E:\FSX\Modules\VRS_TacPack\VRS_TacPack.dllLoadedModule[176]=C:\Windows\system32\WINHTTP.dllLoadedModule[177]=C:\Windows\system32\webio.dllLoadedModule[178]=C:\Windows\system32\d3dx9_43.dllLoadedModule[179]=E:\FSX\RAASPRO\RAASPRO.dllLoadedModule[180]=C:\Windows\system32\Secur32.dllLoadedModule[181]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dllLoadedModule[182]=C:\Windows\system32\IPHLPAPI.DLLLoadedModule[183]=C:\Windows\system32\WINNSI.DLLLoadedModule[184]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dllLoadedModule[185]=C:\Windows\system32\DNSAPI.dllLoadedModule[186]=C:\Windows\System32\netprofm.dllLoadedModule[187]=C:\Windows\System32\nlaapi.dllLoadedModule[188]=C:\Windows\system32\dhcpcsvc.DLLLoadedModule[189]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLLLoadedModule[190]=C:\Windows\system32\dhcpcsvc6.DLLLoadedModule[191]=C:\Windows\System32\npmproxy.dllLoadedModule[192]=C:\Program Files (x86)\Bonjour\mdnsNSP.dllLoadedModule[193]=C:\Windows\system32\rasadhlp.dllLoadedModule[194]=C:\Windows\System32\fwpuclnt.dllLoadedModule[195]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dllLoadedModule[196]=C:\Program Files (x86)\Common Files\System\ado\msado15.dllLoadedModule[197]=C:\Windows\system32\MSDART.DLLLoadedModule[198]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dllLoadedModule[199]=C:\Windows\system32\bcrypt.dllLoadedModule[200]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLLLoadedModule[201]=C:\Windows\system32\comsvcs.dllLoadedModule[202]=C:\Windows\system32\ATL.DLLLoadedModule[203]=C:\Windows\SysWOW64\bcryptprimitives.dllLoadedModule[204]=C:\Windows\SysWOW64\msjetoledb40.dllLoadedModule[205]=C:\Windows\SysWOW64\msjet40.dllLoadedModule[206]=C:\Windows\SysWOW64\mswstr10.dllLoadedModule[207]=C:\Windows\SysWOW64\msjter40.dllLoadedModule[208]=C:\Windows\SysWOW64\MSJINT40.DLLLoadedModule[209]=C:\Windows\SysWOW64\mstext40.dllLoadedModule[210]=C:\Windows\system32\mlang.dllLoadedModule[211]=C:\Windows\system32\RAASAUDIO32.DLLLoadedModule[212]=C:\Windows\system32\X3DAudio1_6.dllLoadedModule[213]=C:\Windows\SysWow64\xactengine3_4.dllLoadedModule[214]=C:\Windows\SysWow64\XAudio2_4.dllLoadedModule[215]=E:\FSX\Modules\rxpGnsDriver.dllLoadedModule[216]=E:\FSX\Modules\LeonardoSH.dllLoadedModule[217]=E:\FSX\Modules\FSUIPC4_Loader.dllLoadedModule[218]=E:\FSX\PMDG\DLLs\PMDG_Interface.dllLoadedModule[219]=C:\Windows\system32\msadp32.acmLoadedModule[220]=C:\Windows\SysWOW64\ieframe.dllLoadedModule[221]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dllLoadedModule[222]=C:\Windows\SysWOW64\mshtml.dllLoadedModule[223]=E:\FSX\GAUGES\XGauge.DLLLoadedModule[224]=C:\Windows\system32\msimtf.dllLoadedModule[225]=C:\Windows\system32\msls31.dllLoadedModule[226]=C:\Windows\system32\d2d1.dllLoadedModule[227]=C:\Windows\system32\DWrite.dllLoadedModule[228]=C:\Windows\system32\D3D10Warp.dllLoadedModule[229]=C:\Windows\system32\ntmarta.dllLoadedModule[230]=C:\Windows\syswow64\WLDAP32.dllLoadedModule[231]=C:\Windows\SysWOW64\uiautomationcore.dllLoadedModule[232]=E:\FSX\Modules\FSUIPC4.DLLLoadedModule[233]=E:\FSX\VistaMare\bin\ViMaIScnX_AP.dllSec[0].Key=LCIDSec[0].Value=3079State[0].Key=Transport.DoneStage1State[0].Value=1FriendlyEventName=Nicht mehr funktionsfähigConsentKey=APPCRASHAppName=Microsoft® Flight Simulator XAppPath=E:\FSX\fsx.exe Thanks Rene
September 29, 201312 yr The faulting module belongs to Microsoft Visual C++ 2005 and is probably telling you an application is not properly installed as intended by the developer. Microsoft Visual 2005, 2008, and 2010 are used by FSX (2010 is used by PMDG). They appear to be properly installed as shown in your crash report. Some people had a bad assignment in the FSUIPC module and, when they got rid of that assignment, the crashes went away. I do not see where the FSUIPC module loaded though. Here's another link that might help - http://forum.avsim.net/topic/420526-my-ctd-has-reappeared-please-help-me-understand-these-log-files/. A blue screen of death (BSOD) is more serious than 'just a crash'. It usually indicates a problem with your hardware (a bad driver, cards not properly seated on your motherboard, etc). You can download and run the BlueScreenView program - http://www.nirsoft.net/utils/blue_screen_view.html and let us know at least the Bug Check String and the Bug Check Code. Best regards, Jim 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
September 29, 201312 yr Author Hi Jim, thank you very much for your fast reply. I just installed FSUIPC today again because I read a lot, that FSUIPC can help with crashes. It is in the Modules within FSX. This is the Installationfile from FSUIPC. Installer for FSUIPC4.DLL version 4.92 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath"... >>> OK! FOUND FSX! <<< ...Looking in registry for ESP install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"SetupPath"Not there, so looking in: HKEY_CURRENT_USER\ESP Parameter"AppPath"... NOT found! ...Looking in registry for Prepar3D install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath"Not there, so looking in: HKEY_CURRENT_USER\Prepar3D Parameter"AppPath"... NOT found! ...=========================================================== INSTALLATION FOR FSX:SetupPath="E:\FSX"Checking version of FSX.EXE:... Version 10.0.61637.0 (Need at least 10.0.60905.0)Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07)Checking if there's already a version of FSUIPC4 installed in: E:\FSX\Modules\FSUIPC4.DLL... Version 4.920 found.FSX Modules folder already exists.Okay -- installed FSUIPC4 into "E:\FSX\Modules\FSUIPC4.DLL"Looking for the current user's Application Data path:... found as "C:\Users\Alarga\AppData\Roaming"Now finding \Microsoft\FSX\FSX.CFG for all users, including this oneLooking in "C:\Users\Alarga\AppData\Roaming"Found FSX.CFG in "C:\Users\Alarga\AppData\Roaming\Microsoft\FSX\FSX.CFG"Now checking DLL.XML ...... There is a previous DLL.XML, checking for FSUIPC4 section.... FSUIPC4_Loader section already exists but will be replaced. (with FSUIPC4_Loader entry)... FSUIPC4 section of DLL.XML written okayNow checking for a SimConnect.XML file ...... No SimConnect.XML file found. This is okay.Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG thereLooking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG thereLooking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG thereLooking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG thereLooking in "C:\Users\UpdatusUser\AppData\Roaming" ... No FSX.CFG there"Modules\FSUIPC Documents" folder already exists.Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX controls.pdf" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "Offset Mapping for PMDG 737NGX.pdf" okay Installed "FSUIPC4 Offsets Status.pdf" okay=========================================================== All installer tasks completed. So the best would be to install everything new? A clean Setup? Appreciate your reply and your work for the fs Community a lot Best regards Rene
September 29, 201312 yr Hi Rene, Thanks for your support. Glad you reinstalled the FSUIPC but it looks like it was already installed. Yet, it makes sure the required entries in your dll.xml are there. Not sure if you own it but it works just as good as freeware. You still need to provide me a Blue Screen report as I requested above. I need to know what the bug check code stated. Since you reinstalled the FSUIPC, have you tried running fsx to see if you are still getting crashes? Perhaps you didn't get the Blue Screen of Death and FSX just crashed? Best regards, Jim 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
September 29, 201312 yr Author Hi Jim! I tried the sim today at least 3 times after installing FSUIPC. I had no Blue Screens, the Simulator just froze. Nothing worked. I to go into the Taskmanager, and closed FSX. I checked the Bluescreen view, it ist strange, there are no stored Bluescreens. The last stored was from April, this was caused by the Nvidia Driver. I did not witness the last bluescreens. I was on Long haule flights in the cruise, when I returned to my PC, there was the Bluescreen, so maybe FSX froze an went from there to the Bluescreen. What is strange that it happens inflight, when not a lot of things are Happening. Kind regards Rene
September 30, 201312 yr Hi Rene, It appears you did not get a BSOD. You get a BSOD and it will not only crash FSX but it will also crash your system. So now you need to investigate what could be the cause.... --- I would first try renaming your Fsx.cfg to Fsx.orig, restart FSX and let the config rebuild. This fixes a lot of problems as it could have gotten corrupted with bad tweaks or settings. Don't move the sliders at all. Leave them at the default. You might want to change the screen resolution though so the sim looks halfway decent. If no crash, then this was the culprit. If the crash continues, then you can go back and rename that fsx.orig back to fsx.cfg and you are back to square one. --- On long haul flights, it is known that FSX will take up a lot of Virtual Address Space (VAS) and it will build up until FSX crashes. During the flight you might have been looking at different views. This takes up the 4GB VAS limit for 32 bit applications. The only way to fix this is to lower your fsx settings just a notch until the problem goes away. --- If you have a lot of photoscenery like MegaSceneryEarth, then you will get a crash 100% during a lengthy flight. This stuff is loading in the background whether you are flying there or not. I downloaded and ran a utility called SceneryConfigEditor. This way, before I even load FSX, I can go in there and only load the scenery that my flightplan will be using. If you have FTX/Orbx stuff, they will load this at the top of the Scenery.cfg which is okay. But, they load all of your FTX/Orbx scenery so, in the SceneryConfigEditor you could go in and disable those areas in FTX that you will not be flying over during a planned flight session. If you are just flying over the PNW and you also have Central and Northern Rocky Mountains installed, you can disable the Central and Northern areas. --- During your investigation you can also disable all of your addon scenery, run fsx, and, if the crash goes away, it is probably a problem with one of your addon sceneries. Enable the sceneries 2-3 at a time until the crash returns. Hope this helps. Best regards, Jim 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
September 30, 201312 yr Author Hi Jim! I am going to try with the fsx. cfg. I already tried the other things. I used Scenery Config and removed all the scenery. I only kept FTX and the departure and arrivial Airport an one ORBx Scenery wich was on the route. I moved alll the sliders back within FSX, Graphics, Traffic; etc. The Only Programm I run beside is Aktive sky. I always start withou ony other programs aside. I Close Antivirus, etc. By now erverything worked. most of the time I flew Long Routes with the NGX, or 747, no Problems. Let you know about fsx.cfg Kind regards Rene
Create an account or sign in to comment