Search the Community

Hello, I have a need to run FSX with EZCA & FSUIPC in a new admin user account. On launching FSX, EZCA will also attempt to launch with an error. This works fine in the other user account. In short, the problem is add ons for FSUIPC and EZCA either do not launch or an Add-On menu is not available. SO TWO ISSUES: 1) When launching FSX, EZCA attempts to launch but fails with the error: Ezdok camera addon Unable to write to C:\Users\sim\AppData\Roaming\EZCA\db\general.INI. 2) The Add-On menu doesn’t appear in this new user account. (So, I cannot access FSUIPC) QUESTIONS THAT MAY BE ASKED: Are both users administrative users? Yes Have you tried right clicking and running as administrator? Yes (in both users) Is the folder, “EZCA” located at, “C:\Users\sim\AppData\Roaming\”? No Version numbers: FSUIPC 4.929 and EZCA 1.16 Microsoft Flight Simulator X Deluxe 10.0.61472.0 (fsx-sp2.20071210-2023) MY CONFIGURATION: iMac (27-inch, Late 2012), Intel i7 3.40 GHz, 32 GB, GeForce GTX 680MX 2GB VRAM, 3TB HDD Fusion OPERATING SYSTEM: (running via Boot Camp) Microsoft Windows 7 Ultimate (64-bit) SP1 Any assistance would be appreciated! - Shaun

Just installed FSX on a new Windows 7 machine, and we've run into quite a problem. Whenever we run 'Kiosk Mode', FSX will crash after about a minute of flight time, and display the "A fatal error has occurred" message box. FSX seems to run just fine by itself - no crashes so far. We've placed a new "UIAutomationCore.dll" file in the FSX folder, and we've tried compatibility mode - no luck so far. I've attached the error that shows up in the application log: Any thoughts?

Hi all, Iam having a slight problem with my computer at the moment so hoping some of you might be able to guide me. We are all use to (well at least Iam) use to the odd FSX crash but recently this has been happening more than normal which is obviously very annoying. I run FSX on a Windows 7 (x.64 bit) version and have found the so called 'fix' for it ( by adding uiautomationcore.dll file into my main fsx folder.) However this is not working for me so I was hoping someone could guide me on any solutions they might have previously come across. Heres the link for the file I added: uiautomationcore.dll . My specs are: Intel 2700k cpu @ 3.8 ghz 800w powecool psu 16gb g skill or kingston ram 120gb ocz solid state drive 2 x 1tb western digital hard drives 32m sata3 nvidia gtx560ti video card gigabyte z68 main board samsung dvdrw drive coolemaster elite 430 case I run everything on lowered setting at about medium. My test flight has been in the PMDG NGX on Vatsim from EGKK (xtreme) to EHAM (mega airport) I usually get about half way in the flight but it can vary from 2 seconds before takeoff to seconds before landing. I havent done a succcesfull flight since way back in about November time as it always crashes. :( :( After disabling DEP and UAC it doenst 'Crash' anymore it just freezes and I get the little blue loading bar forcing me to close. i recently updated by Nvidia settings but still no joy :( Fyi I run FTX england, REX and FS2crew but dont think thats relevent? No changes have been made to my CFG. and I dont run anything like 'SWEETFX' for example. Ill look forward to some advice Kind Regards Josh

Hello, I know that this may have been asked multiple times, however I am curious. Currently, I am running Windows 7 64-bit and I am currently getting decent performance out of FSX with medium high settings. I have been reading about the benefits of Windows 8 in terms of being a better system resource handler than Windows 7 currently does, so as a result I am very interesting into upgrading to the next version of Windows as soon as I upgrade my computer's RAM memory capacity. As a result of this prospect, I would like to answer the following questions. Does FSX in Windows 8 behaves in the same way as in Windows 7? Are there any installation problems that I should be aware of? When running FSX on Windows 8 have there been any changes in performance (positive or negative) when compared to Windows 7? Thanks for your time and answers.

Hi to all guys, I got SSD OCZ Vertex 3 where I wanto instal ONLY FSX, not operating system. My actual system is: C: OS Windows 7 (HDD WD Velociraptor 160G) D: FSX (HDD WD Caviar Black 500G) So I want to change WD Caviar Black with OCZ Vertex 3. My question is: may I have to set something special settings under BIOS or Windows 7? or can I simply initialize OCZ Vertex 3 (now it's not yet mounted onto Windows 7, but only phisical installed), change drive letter to "D" (after changing Caviar Black's one) and copy fsx data files? I repeat: I want only to use OCZ for FSX, not as boot operating system. My MOBO is ASUS Rampage II Extreme. Many thanks for your help, Riccardo

I've got a fairly new machine which I used to sim race constantly on but i've pulled back on that habit and decided i'd give good ol FSX a whirl on here but every time, without fail, i'm about 10 seconds maybe 30 seconds into a flight my entire machine freezes. I can't ctrl-tab can ctrl-alt-del can't do anything but hold the power button and shut down the machine. This is mega-frustrating as i'm not exactly running an ancient machine here. I've tried turning up and down the sliders, not running the game full screen, making sure the computer is nice and cool...nothing is overclocked or non standard I guess. I've looked in the event logs and have no idea what i'm looking for...seriously, this is frustrating. I've been running iRacing and rFactor on this computer with fairly robust graphics with little if any freezing whatsoever so there is something in FSX that doens't like my machine... I really have no idea where to go with this. I'm assuming I should be able to run FSX with some tweaking, but the sheer volume of problems I see posted in this forum are entirely overwhelming...i figured i'd see if anyone can get me started. I'm not even sure where i should begin as i've never had FSX running on this machine previously. Here are my system specs Windows 7 64bit- fully patched as of this morning, prior to even installing FSX 2 ATI Radeon 5700's, crossfire enabled, 12.3 drivers (I did roll this back from the 12.6 drivers already - the problem happens with both drivers) FSX + Acceleration pack CPU Type QuadCore Intel Core 2 Quad Q9550, 2833 MHz (8.5 x 333) Motherboard Name Asus Rampage Formula (2 PCI, 3 PCI-E x1, 2 PCI-E x16, 4 DDR2 DIMM, Audio, Dual Gigabit LAN, IEEE-1394 Motherboard Chipset Intel Beachwood X48 System Memory 8192 MB (DDR2-800 DDR2 SDRAM) Can someone please just help me figure this out? Where on earth do I start to trouble shoot? It's a new install and a clean version of windows...i've no idea what to do. Thanks.

Hi, I've just purchased MCE and have so far only tried it with the PMDG 737NGX. I've hit a few problems which someone here may be able to assist me with. Here are my most pressing MCE issues: 1) Starting a new flight cold & dark I find I can't "set autobrake RTO" as the copilot replies "can't select rejected takeoff on the autobrake when we are airborne captain". We are most definitely on the ground. 2) When I request him to "release parking brake" his only response is to yell at me "do you want to destroy the gear on landing or what?" 3) Whilst I can get my co-pilot to set the vertical speed to a positive value I can't work out how to get him to set a negative VS. 4) How do I ask the copilot to retract the flaps by just one notch? (The only command I found in the 737NGX that allows extension of the flaps by one notch is "extend slats") 5) If I load a flightplan into FSX and then start MCE it successfully lists origin, destination, registration and crz alt on its ATC tab. But can this information in MCE be updated ? (eg If I load MCE before setting a flightplan the MCE ATC tab remains mostly blank and its "flight plan" button is always greyed out) Many thanks for any suggestions! Cheers Peter.

Hello everyone, Just to put you into context, here's my situation: I have been flight simming for a very long time using X-Plane. Near the end of 2009 though, I discovered some aircraft sytems were better modeled in FS9 for certain addon aircraft and decided to try it. Since then, I have been flying FS9 on VATSIM and I really love the experience. As you can see on my Vataware page though (http://vataware.com/pilot.cfm?cid=1008468) I have not flown for a very long time. I basically ran out of time, and when I came back to FS9 about a year ago, my PC's performance discouraged me. (Back then, I was running an Intel P4 2.8 GHz with an nVidia GeForce 7600 GS, and Windows XP 32 bit. It wasn't that bad, but I didn't feel like spending hours tuning again. Recently though, I upgraded my computer. Surely it's not the best out there, but I built it myself and it's really the best I could afford for now. At least I still have a lot of headroom for future upgrades, I am no longer limited by my old AGP slot and/or my unique motherboard socket type. My specs are on my profile. I was about to install FS9 when I thought I might try FSX. Why not? My PC could maybe handle it quite well. Turns out it does! Yes, I did do my research. I read the most popular guides online, did everything I was supposed to do and I am very impressed with the results! FSX runs really great, super smooth and never lags. I have not installed any addons or anything extra yet, just the basic FSX install with SP1 and SP2. I have the Deluxe version, not Acceleration. Here's my problem - even though I've only played with it for about 1 or 2 hours, just flying around the default area in the default aircraft, I have been getting random Windows 7 fatal errors. I am running Windows 7 64 bit now. I did do a bit of research, but most threads seem to be telling people to remove X addon and try again - which is why I am starting my own thread, I have no addons! There seems to be a lot of debate about this strange uiautomationcore.dll thing. I have not tried anything yet because there are 2 options I find on the web and I don't know what to do. Deactivate the file in system32 (by renaming it)?? Download the Vista 32 bit version and place it in my FSX directory? Basically, I'm just asking to find out if I missed anything major. It's a one month old build, with fresh OS and clean FSX install. Any tips? Maybe this will help others getting random CTD after a clean system install. Thank you very much for your time, I look forward to starting my long haul airline flights and sharing my screen shots again! Don't get me wrong, I am very happy with my FSX performance, but just wandering what my last tune-ups should be for the best Windows 7 64 bit crashless experience possible. Regards, Phil H

Ive installed FSX on a seperate drive (128GB SSD) called the F drive. Opposed to the normal C drive in hopes of making the sim run faster. However, i cant find the cfg. I know under normal circumstances, it would be under appdata, etc. However, when i installed FSX on the F drive, there was nothing currently on that drive, not one folder. I created a folder called Microsoft Flight Simulator X and thats what the game was installed into. Where would i go about finding the .cfg? Would i have to add a new one? The game runs fine, so im sure there has to be one somewhere on that drive. Thanks- Matt

I am puzzled...I unplugged my pro flight yoke from its current USB port, and replaced it with my headset (my headset had mysteriously stopped working, so I tried a new port). I eventually discovered the problem for the headset. I plugged the headset into another port. I re-plugged the yoke and got an ominous message...it indicated that the yoke had not been installed (I don't remember the exact words). I've tested it in other USB ports, but nothing works! In addition, I don't see it reflected in the Device Manager. The yoke's clock screen is totally blank, and the light on the quadrant is unlit. Interestingly, my Saitek rudder pedals work fine (it shows up in Device Manager as well). In addition, my Saitek Radio panel and Multi panel are working. I've consulted MadCatz, and they suggested the following: -Open the control panel and select the System and security -Select power options -Under your current preferred power plan, please select the "Change Plan Settings" option then click on the "Change Advanced Power Settings" -Click on the USB settings tab to access the USB selective suspend setting -If you have this option disabled then enable it. If the power setting is already enabled then disable it. -Hit apply then OK and close the power options page. -Open the control panel and select hardware and sound -Open device manager -Open universal serial bus controls -Right click on any USB root hubs or the generic USB hub and select properties> power management -Untick allow the computer to turn off this device to save power I am using Windows 7 pro 64 bit; HP ProDesk 400 G1 MT; 3.3GHz; 8192MB RAM; Direct X 11; Default System BIOS. I've tried everything, but nothing has worked! Any suggestions?

I have been consistently receiving CTD (fsx.exe APPCRASH) when running MegasceneryEarth 2.0 over the states of CO, UT, NE. I have not had issues previously with MI, FL, NY. For example: I am able to load up and take off from Denver without issue. But as soon as I pass west of Denver, then CTD. It will also CTD when I try to load a flight @ Aspen (KASE). For Utah, as soon as I approach Bryce Canyon, then CTD. In all cases, if I disable the scenery area from the library, all is fine. Any suggestions would be helpful. I am also running UTX USA and FS Global Ultimate - The Americas. PC Specs Windows 7 64-bit CPU= Intel Core i7-3770k RAM = 8GB GPU = GeForce GTX 660 Below is the AppCrash Data. I did notice the module was different each time it crashed. Version=1 EventType=APPCRASH EventTime=130177201423750249 ReportType=2 Consent=1 ReportIdentifier=d65b2e22-e76c-11e2-a2bd-ec460422f674 IntegratorReportIdentifier=d65b2e21-e76c-11e2-a2bd-ec460422f674 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.61472.0 Sig[2].Name=Application Timestamp Sig[2].Value=475e17d3 Sig[3].Name=Fault Module Name Sig[3].Value=ntdll.dll Sig[4].Name=Fault Module Version Sig[4].Value=6.1.7601.17725 Sig[5].Name=Fault Module Timestamp Sig[5].Value=4ec49b8f Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=00038dc9 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 Information 1 DynamicSig[22].Value=7cf3 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=7cf314754711732647adaf012eb32201 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=62c0 DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=62c0c4d0167c0e1f308a5b753985a147 UI[2]=F:\Microsoft Flight Simulator X\fsx.exe UI[3]=Microsoft Flight Simulator® has stopped working 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]=F:\Microsoft Flight Simulator X\fsx.exe LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll LoadedModule[2]=C:\Windows\syswow64\kernel32.dll LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll LoadedModule[7]=C:\Windows\syswow64\GDI32.dll LoadedModule[8]=C:\Windows\syswow64\USER32.dll LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll LoadedModule[14]=C:\Windows\syswow64\LPK.dll LoadedModule[15]=C:\Windows\syswow64\USP10.dll LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[17]=C:\Windows\syswow64\ole32.dll LoadedModule[18]=C:\Windows\system32\apphelp.dll LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL LoadedModule[20]=C:\Windows\system32\UxTheme.dll LoadedModule[21]=C:\Windows\system32\WINMM.dll LoadedModule[22]=C:\Windows\system32\samcli.dll LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll LoadedModule[24]=C:\Windows\system32\MSACM32.dll LoadedModule[25]=C:\Windows\system32\VERSION.dll LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll LoadedModule[27]=C:\Windows\system32\sfc.dll LoadedModule[28]=C:\Windows\system32\sfc_os.DLL LoadedModule[29]=C:\Windows\system32\USERENV.dll LoadedModule[30]=C:\Windows\system32\profapi.dll LoadedModule[31]=C:\Windows\system32\dwmapi.dll LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll LoadedModule[35]=C:\Windows\syswow64\urlmon.dll LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL LoadedModule[43]=C:\Windows\syswow64\iertutil.dll LoadedModule[44]=C:\Windows\syswow64\WININET.dll LoadedModule[45]=C:\Windows\system32\MPR.dll LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll LoadedModule[50]=C:\Windows\system32\mscms.dll LoadedModule[51]=C:\Windows\system32\DDRAW.dll LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[54]=C:\Windows\syswow64\IMM32.dll LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll LoadedModule[57]=C:\Windows\syswow64\NSI.dll LoadedModule[58]=C:\Windows\system32\msi.dll LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[60]=F:\Microsoft Flight Simulator X\language.dll LoadedModule[61]=F:\Microsoft Flight Simulator X\API.DLL LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[63]=F:\Microsoft Flight Simulator X\ablscpt.dll LoadedModule[64]=F:\Microsoft Flight Simulator X\flight.dll LoadedModule[65]=F:\Microsoft Flight Simulator X\ai_player.dll LoadedModule[66]=F:\Microsoft Flight Simulator X\acontain.dll LoadedModule[67]=F:\Microsoft Flight Simulator X\controls.dll LoadedModule[68]=C:\Windows\system32\DINPUT8.dll LoadedModule[69]=F:\Microsoft Flight Simulator X\fsui.dll LoadedModule[70]=F:\Microsoft Flight Simulator X\atc.dll LoadedModule[71]=F:\Microsoft Flight Simulator X\facilities.dll LoadedModule[72]=F:\Microsoft Flight Simulator X\demo.dll LoadedModule[73]=F:\Microsoft Flight Simulator X\main.dll LoadedModule[74]=F:\Microsoft Flight Simulator X\fe.dll LoadedModule[75]=F:\Microsoft Flight Simulator X\util.dll LoadedModule[76]=F:\Microsoft Flight Simulator X\simprop.dll LoadedModule[77]=F:\Microsoft Flight Simulator X\g2d.dll LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll LoadedModule[80]=C:\Windows\system32\d3d9.dll LoadedModule[81]=C:\Windows\system32\d3d8thk.dll LoadedModule[82]=F:\Microsoft Flight Simulator X\g3d.dll LoadedModule[83]=F:\Microsoft Flight Simulator X\panels.dll LoadedModule[84]=F:\Microsoft Flight Simulator X\multiplayer.dll LoadedModule[85]=F:\Microsoft Flight Simulator X\ui.dll LoadedModule[86]=F:\Microsoft Flight Simulator X\sound.dll LoadedModule[87]=F:\Microsoft Flight Simulator X\sim1.dll LoadedModule[88]=F:\Microsoft Flight Simulator X\simscheduler.dll LoadedModule[89]=F:\Microsoft Flight Simulator X\visualfx.dll LoadedModule[90]=F:\Microsoft Flight Simulator X\window.dll LoadedModule[91]=F:\Microsoft Flight Simulator X\terrain.dll LoadedModule[92]=F:\Microsoft Flight Simulator X\weather.dll LoadedModule[93]=C:\Windows\system32\DSOUND.dll LoadedModule[94]=C:\Windows\system32\POWRPROF.dll LoadedModule[95]=F:\Microsoft Flight Simulator X\symmap.dll LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll LoadedModule[97]=C:\Windows\system32\MSIMG32.dll LoadedModule[98]=F:\Microsoft Flight Simulator X\xuipc.dll LoadedModule[99]=F:\Microsoft Flight Simulator X\livingwater.dll LoadedModule[100]=F:\Microsoft Flight Simulator X\fs-traffic.dll LoadedModule[101]=F:\Microsoft Flight Simulator X\gps.dll LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll LoadedModule[104]=C:\Program Files (x86)\MMTaskbar\shellhook.dll LoadedModule[105]=C:\Windows\system32\RICHED20.DLL LoadedModule[106]=C:\Windows\system32\CRYPTSP.dll LoadedModule[107]=C:\Windows\system32\rsaenh.dll LoadedModule[108]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[109]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[110]=C:\Windows\syswow64\MSASN1.dll LoadedModule[111]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[112]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[113]=C:\Windows\system32\wbemcomn.dll LoadedModule[114]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[115]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[116]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[117]=C:\Windows\system32\NTDSAPI.dll LoadedModule[118]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[119]=C:\Windows\system32\dxgi.dll LoadedModule[120]=C:\Windows\system32\d3d11.dll LoadedModule[121]=C:\Windows\system32\nvd3dum.dll LoadedModule[122]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[123]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[124]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[125]=C:\Windows\system32\d3d10_1.dll LoadedModule[126]=C:\Windows\system32\d3d10_1core.dll LoadedModule[127]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[128]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[129]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[130]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[131]=C:\Windows\system32\winbrand.dll LoadedModule[132]=C:\Windows\system32\nvapi.dll LoadedModule[133]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[134]=C:\Windows\system32\WINSTA.dll LoadedModule[135]=C:\Windows\SysWOW64\gameux.dll LoadedModule[136]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[137]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[138]=C:\Windows\SysWOW64\wer.dll LoadedModule[139]=C:\Windows\System32\Wpc.dll LoadedModule[140]=C:\Windows\System32\wevtapi.dll LoadedModule[141]=C:\Windows\System32\msxml6.dll LoadedModule[142]=C:\Windows\system32\SAMLIB.dll LoadedModule[143]=C:\Windows\system32\netutils.dll LoadedModule[144]=F:\Microsoft Flight Simulator X\uiautomationcore.dll LoadedModule[145]=C:\Windows\system32\OLEACC.dll LoadedModule[146]=C:\Windows\System32\MMDevApi.dll LoadedModule[147]=C:\Windows\System32\PROPSYS.dll LoadedModule[148]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[149]=C:\Windows\system32\HID.DLL LoadedModule[150]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[151]=C:\Windows\system32\wdmaud.drv LoadedModule[152]=C:\Windows\system32\ksuser.dll LoadedModule[153]=C:\Windows\system32\AVRT.dll LoadedModule[154]=C:\Windows\system32\msacm32.drv LoadedModule[155]=C:\Windows\system32\midimap.dll LoadedModule[156]=C:\Windows\system32\dinput.DLL LoadedModule[157]=C:\Windows\System32\wship6.dll LoadedModule[158]=C:\Windows\System32\wshtcpip.dll LoadedModule[159]=F:\Microsoft Flight Simulator X\bglmanx.dll LoadedModule[160]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[161]=C:\Windows\system32\inetmib1.dll LoadedModule[162]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[163]=C:\Windows\system32\WINNSI.DLL LoadedModule[164]=C:\Windows\system32\snmpapi.dll LoadedModule[165]=F:\Microsoft Flight Simulator X\Modules\iFly737NG.dll LoadedModule[166]=F:\Microsoft Flight Simulator X\Flight One Software\Audio Environment\AEMODULE.dll LoadedModule[167]=F:\Microsoft Flight Simulator X\FeelThere\E170\EJetH.dll LoadedModule[168]=F:\Microsoft Flight Simulator X\Modules\Fsuipc4.dll LoadedModule[169]=F:\Microsoft Flight Simulator X\Captain_Sim\Captain_Sim.b757.menu.dll LoadedModule[170]=F:\Microsoft Flight Simulator X\Captain_Sim\757\cs.sound.dll LoadedModule[171]=F:\Microsoft Flight Simulator X\PMDG\DLLs\PMDGOptions.dll LoadedModule[172]=F:\Microsoft Flight Simulator X\PMDG_SimConnect_Ldr.dll LoadedModule[173]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll LoadedModule[174]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll LoadedModule[175]=C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dll LoadedModule[176]=C:\Windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_49768ef57548175e\MFC90ENU.DLL LoadedModule[177]=F:\Microsoft Flight Simulator X\PMDG\DLLs\PMDGEvents.dll LoadedModule[178]=F:\Microsoft Flight Simulator X\PMDG\DLLs\PMDGSounds.dll LoadedModule[179]=F:\Microsoft Flight Simulator X\WaveLib.dll LoadedModule[180]=F:\Microsoft Flight Simulator X\Captain_Sim\Captain_Sim.b767.menu.dll LoadedModule[181]=F:\Microsoft Flight Simulator X\Captain_Sim\767\cs.sound.dll LoadedModule[182]=F:\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll LoadedModule[183]=F:\Microsoft Flight Simulator X\VistaMare\bin\VMCX_SP2.dll LoadedModule[184]=F:\Microsoft Flight Simulator X\VistaMare\bin\ViMaNET.dll LoadedModule[185]=F:\Microsoft Flight Simulator X\Modules\FSCopilot.dll LoadedModule[186]=C:\Windows\system32\oledlg.dll LoadedModule[187]=C:\Windows\system32\dhcpcsvc.DLL LoadedModule[188]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SIMCONNECT.DLL LoadedModule[189]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[190]=C:\Windows\SysWOW64\api-ms-win-downlevel-shlwapi-l2-1-0.dll LoadedModule[191]=C:\Windows\SysWOW64\api-ms-win-downlevel-advapi32-l2-1-0.dll LoadedModule[192]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll LoadedModule[193]=C:\Windows\system32\Secur32.dll LoadedModule[194]=C:\Windows\SysWOW64\mshtml.dll LoadedModule[195]=C:\Windows\system32\msimtf.dll LoadedModule[196]=C:\Windows\system32\msls31.dll LoadedModule[197]=C:\Windows\system32\d2d1.dll LoadedModule[198]=C:\Windows\system32\DWrite.dll LoadedModule[199]=C:\Windows\system32\D3D10Warp.dll LoadedModule[200]=C:\Windows\system32\MLANG.dll LoadedModule[201]=C:\Windows\system32\ntmarta.dll LoadedModule[202]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[203]=C:\Windows\SysWOW64\uiautomationcore.dll LoadedModule[204]=F:\Microsoft Flight Simulator X\VistaMare\bin\ViMaIScnX.dll LoadedModule[205]=F:\FS Program Files\FSFDT\FSCopilot\FSCopGPWS.ocx LoadedModule[206]=C:\Windows\system32\MSVBVM60.DLL LoadedModule[207]=C:\Windows\system32\SXS.DLL LoadedModule[208]=F:\FSPROG~1\FSFDT\FSCOPI~1\FSCOPI~1.OCX LoadedModule[209]=F:\FS Program Files\FSFDT\FSCopilot\FSCopTimeSync.ocx LoadedModule[210]=F:\FS Program Files\FSFDT\FSCopilot\FSCopHeadEffects.ocx LoadedModule[211]=F:\FS Program Files\FSFDT\FSCopilot\FSCopTuner.ocx LoadedModule[212]=C:\Windows\system32\msiltcfg.dll LoadedModule[213]=C:\Windows\SysWOW64\MSCOMCTL.OCX LoadedModule[214]=C:\Windows\system32\wmp.dll LoadedModule[215]=C:\Windows\system32\wmploc.dll LoadedModule[216]=C:\Windows\system32\MFPlat.DLL LoadedModule[217]=c:\Windows\SysWOW64\jscript.dll LoadedModule[218]=F:\Microsoft Flight Simulator X\GAUGES\Captain_Sim.b767.sound.GAU LoadedModule[219]=F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_B767-300\panel\Captain_Sim.b767.adi.GAU LoadedModule[220]=F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_B767-300\panel\Captain_Sim.b767.fms.GAU LoadedModule[221]=F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_B767-300\panel\Captain_Sim.b767.eicas1.GAU LoadedModule[222]=F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_B767-300\panel\Captain_Sim.b767.eicas2.GAU LoadedModule[223]=F:\Microsoft Flight Simulator X\SimObjects\Airplanes\CS_B767-300\panel\Captain_Sim.b767.300.GAU LoadedModule[224]=C:\Windows\system32\msadp32.acm FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft Flight Simulator® AppPath=F:\Microsoft Flight Simulator X\fsx.exe

I use Windows 7. I have been having issues recently with my system after Microsoft automatically installed what they called critical updates. Now I can no longer download software on to my computer. I keep getting a weird message - The system cannot find the file specified. I was using win zip. I am trying to trouble shoot to locate the issue. Is there any other software besides win zip I can try out? Thanks for your assistance.

Now that I'm thinking to upgrade my laptop to a SSD (see current specs at the bottom), I'll also perform a clean install of Windows on it (something I never did with my 4-year old laptop, i.e., I started it using it as unboxed). However, this could be a good chance to move to Windows 10. This is what i have in my laptop: - FS 2004, in full screen (always) - FSUIPC registered - PSS 757 and 777 - Wilco/Feelthere Airbus - Feelthere E135/E145 - Feelthere E170/E190 - Leonardo Maddog - vasFMC gauge version - ISG gauges - iFly 737 and 747v2 (but I'm not longer flying them) - And lots of sceneries that shouldn't be an issue. Is it worthwhile to move to Windows 10 or should I stay with Windows 7? I have already downloaded both ISOs...

Ultimate fsx pc ? Help! Ideas? I wan't to create the ultimate fsx pc for my b737 home cockpit. This is wat I got out of thousends of forums. Please say your opinions and ideas. Also if it all would work together. The mobo and the memory for example. Please share your comments! Cooler Master HAF-X 1000 Watt power supply Intel Core i7 4770K 3.5 GHz (OC to 4.5 GHZ) ASUS Maximus VI Hero (Intel Z87) SATA 6Gb/s, USB 3.0 ASUS Nvidia GTX Titan 6GB Corsair H110 Dominator® Platinum with Corsair Link Connector — 1.65V 16GB Dual/Quad Channel DDR3 (CMD16GX3M4A2400C9) SSD Samsung 840 Evo 250GB (for windows 7 64bit ultimate, I got the ultimate for the langauge options in fs2crew) SSD Samsung 840 Evo 500GB (for fsx and other addons and scenerie Windows 7 Ultimate 64Bit Please help?

Hello! I recently got a new motherboard the GIGABYTE GA-F2A55M-DS2 and the AMD A6 6400K. after i had switch from the old motherboard and the old cpu to the new motherboard/cpu and put everything were they should be my pc won't start up i got nothing... i can se at the power suply a green light but when i am trying to start it up nothing happends PLEASE HELP!!!!

Hi, I have a new rig dedicated to FSX (see signature for details). First, I did install a light FSX (with only the main addons and sceneries) in order to test and fine tune the system and its overclocking settings. I ended up with 2 OC profiles (4.5GHz and 4.6GHz). Since everything was running fine and stable, I made a full clean reinstall of windows and FSX with all the addons. But now that everything is properly installed, I always have CTD during flight. This only occures when the CPU is overclocked. With the CPU at stock speed, no CTD. At 4.5GHz, the CTD usually occurs on final approach, when the destination airport is loading I guess. At 4.6GHz, it happens anywhere between 10 to 15 mns of flight. The win7 error log indicates that the crash comes from the gdiplus.dll module. I did search around for this error but didn't find anything helpfull. So far, I only tried to raise the CPU vcore but it didn't help. I don't know what to do to solve this issue so any advice is welcome. Thanks, Herby.

I am not getting any audio from HDMI. I am using Windows 7 64 bit, Gigabyte 970 motherboard, a Vizio plasma tv connected directly to my Evga Nvidia GeForce GTX 660 GPU via HDMI cable. In the control panel - audio devices the Vizio tv shows up but is listed as not plugged in. Obviously it is physically plugged in and working becuase my display works but no audio. I tried uplugging and reconnecting the HDMI cable and when I do that the audio works, however, the resolution of the display becomes distorted. Then when I switch imputs on the display from HDMI to a TV channel and then back to HDMI the audio goes away again but the resolution is fixed and goes back to normal. I have also made sure that I have the latest Nvidia drivers installed. I am at a loss with this audio problem and will appreciate any help! Thank you Ben

Hello, Well, this is nothing new really, but today I'm elated because for me at least, I've finally gotten fsx and a lot of orbx scenery stuff working beautifully....smooth 30-70 fps without jitters or tearing or anything weird over SeaTac with autogen on dense. It's been a long, tedious waste of time trying to get things to work on my system. i7 3.5 ghz, gtx 560ti windows 7. one SSD drive for Windows, one SSD drive for FSX....near instant texture loading and menu loading. Nice to have but $$$$ and limited storage. The issues I've had are numerous crashes to desk-top, fatal error messages, bizarre graphics meltdowns (black skies, smearing weirdness etc, blurries, stuttering, you name it. This stuff doesn't happen all the time, but definitely once in every flying session. Fatal error 2-3 times per session : ( I've tried everything under the sun and have reinstalled fsx and all the add ons four times (my wife is ready to leave me). For me at least I've 'learned' what works on my system and I can repeat it now every time on my computer to ensure great results. I just thought I'd share what I've done that's worked so well. I realize that all systems are different yaddayadda yadda. Some of this might work for you, some of it might not. Posts like this sure helped me sort things out, so I thought I'd give back. So here's my story: -I've tried many tweaks to the config, usually with the Bohote fsx tweaker tool. Bufferpools, max texture load, reject threshold, etc. etc. etc. After hours of trial and error using a saved flight for consistency, I only found the tweaks to cause instability and noticed little to no difference to frame rates or visual performance. I've concluded that for better or worse, the stock config is the most stable. I run the sim at stock config except for the swarmcloud fix which solved flashing clouds for me and the ForceFullScreenVsync=1 which solved the screen tearing. I run my card on default settings with vsync enabled. Nothing else is different. (I've experimented with external AA, vsync settings, external frame limiter, and have noticed no differences to the sim in performance or quality..only instability and unpredictable performance. I'm running fsx acceleration btw. -I also run all the Orbx North America sceneries. I LOVE these addons but have found them to cause a lot of instability to FSX on my machine (crashing, errors, artifacts etc.). I run REX, but have never had any issues with it anywhere and the fsx default scenery flies like a dream and has never crashed or erred. So for me, Orbx FTX was the issue. Now here's the game changer: What really solved MY problems was the UIAutomationCore-1.dll vista file 'fix'. I downloaded this Vista file and simply dropped it into the FSX main folder. I can now fly FSX problem free. I can switch menus over and over, change settings, start and stop, fly in complex areas in addon aircraft and never have a crash or error. If you're having issues on a Widows 7 setup and haven't tried this, I highly recommend it. http://www.mediafire.../?mik2mlqdz1w�� It might not work...hope it does because for me it was like Christmas. It could be wishful thinking, but I'm pretty sure I've gained 10 frames per second from this as well. I'm no computer expert though so don't know if that's even possible. As for settings: Filtering-Bilinear AA-On All boat traffic 100% Cars 25% Water low 2.0 Private traffic 100% Airline traffic-off Autogen Dense / Auto gen complexity maximum Mesh Complexity 50% Mesh Resolution 100% Detail radius 100% Texture res 100% No ground shadows, NO BLOOM!!, no aircraft shadows, cloud distance 80K, Also, I tried using the Grand theft auto ENBseries mod, but only found it to cause issues for me and maybe even instability. I don't know though, people seem to use it and works for them. Thoughts on Frame limiter: If you have a fast machine and you're getting a wide range of fps in a single flight it can cause stutters (as you know). I found that by simply setting the fsx frame limiter to 100, it stops the stutters, but still allows high fps. It's as if by simply having it on, it irons out the issues for a fast machine. So in busy areas, things drop to 20-40 fps, but can fly up to 70 fps without jitters as well in simple areas. By setting to 100, I never fiddle with the slider anymore no matter where I'm flying. Definitely advice for fast systems only though I suspect. This nice little program will allow you to slow down the AI vehicles from 1000 mph to something more realistic like 25 mph. Looks great in towns. http://www.wolfgang-...ng-picheta.de�� Also fixes lots of little details. For me, the brakes release/hold control would never repeat. I'd set the slider to max repeat but it would revert. I tried many joystick assignments for it but the problem persisted. I discovered that by setting it to medium, it now behaves like a true car brake and never reverts in the assignments. On an aesthetic note, I love the Water configurator from http://www.strikings...om/fswc.shtml�� combined with REX, the water can look beautifully real ('black' lakes, rich dark oceans etc.) Well, that's all....sorry for the novel. I just wish that I would have found this post 3 months ago, so I'm just writing it to put it all down in one place. Maybe it can help someone out there with similar issues/setup to me. I realize that it's all nothing new. It just hard to find it all in one place! Hope some of it makes your fsx experience a little more friendly.

not sure if this the right forum, but I just got a new PC with windows &. came from Vista. installed fsx with accelerator and ran into a problem. flying at 300 feet with the auto pilot. approaching the ILS feather, and the cockpit freezes up. not gauges, panels like gps radio etc work. if I look to the side the scenery is moving but I have no control. Please tell me I am not the first. All drivers updated. data in my profile Ron

Hi I was just wondering if someone can help me I am looking to try my hand at building my first ever pc however I will only be trying with cheap parts first of all then upgrade if all goes well. Obviously I will need windows of some sort (in this case I have chose 7 but please say if you disagree with that when running fsx) but I was just wondering in the future when I upgrade I have heard that windows can invalidate. Will I then need to buy a new key or just contact Microsoft and explain what I have done? I don't intend to do anything illegal as it will only be running on this pc but was just wondering do I get so many installs before i have to do anything or will it only resister once then I need to buy a new copy. Many thanks in advance for any replies Nathan

I am at a critical stage of my new computer build – that is, ready to install Windows 7. I have a Caviar Black 1TB drive and a just purchased Crucial 256 GB m4 SSD. From a post I made yesterday, it was suggested that I put Windows 7 on the Caviar Black and FSX on the SSD. Since I am a fairly inexperienced hardware guy, I appreciate and don’t question the guidance to not put both Windows 7 and FSX on the SSD. But it would be of help to me to understand why, since there is certainly room on the SSD for both. I expect there is good reason. It would be of help if someone could explain why. Thank You in Advance

Go ask in the REX forums. This isn't a support forum.

Hi guys, A few days ago I had crashes in FSX. A kind man helped me find out what was wrong, the ENB series was the problem. BUT now it gone alright, until this minute. I was flying about 50 minutes when I wanted to save (3rd time) when FSX suddenly quit without message that what was wrong, so I launched Event Viewer and I saw this message: " A request to disable the Desktop Window Manager was made by process (Flight Simulator X v10.0.61637.0) " and at that same time this one: " The Desktop Window Manager was unable to start because composition was disabled by a running application " nothing more, no crash logs about e.g. uiautomationcore.dll or SweetFX but I believe that this kind of crash wasn't caused by SweetFX. I searched the net about this kind of crash but I did not find so much things about this crash. I have installed uiautomationcore.dll (proper version), I have Window 7 with the latest updates and with the latest nvidia graphic drivers. Can somebody help me out what went wrong? I really can't understand why Microsoft stopped FSX development. Thanks

:t4020: I have an older system [Dell 8250 Desktop] that runs Windows 7 Home Premium 32 bit. I have been totally unable to get the Expansion Pack installed, I think Microsoft does not intend that we will be able to re-install [on Windows 7]! Consequently, I have given up trying to re-install the Expansion Pack. What I am now looking for is a workaround that will allow me to install the F-18 and the aircraft carriers from my Expansion Pack disk [after all I paid for them!]. Does anyone know how to do that? Thank you! Steven L. Edwards Palm Springs, CA USA :united-states-flag:

Hi all, I had a question I was hoping everyone here may be able to help with. I currently have 4 drives in my PC, listed below: 250 GB SSD - OS, FSX, Orbx, Other small non-FSX programs 120 GB SSD - FSX addons (REX and Planes) 3TB HDD - iTunes 1TB HDD - Storage and where my USERTEMP and WINTEMP files are written (saves writes on the SSD) The set up for the OS, FSX, and the add-ons kind of developed over time and as I look at it now, it doesn't make sense. What I would really like to do is to be able to move my OS to the smaller SSD and have everything FSX-related on the larger SSD so it would look like: 250GB SSD - FSX, FSX add ons 120GB SSD - OS and other non-FSX programs And then leave the other two drives alone. Would this be at all possible with any kind of cloning software? Can I move the OS to the smaller SSD and then move FSX to the larger SSD. I don't mind reinstalling all of the add-ons for FSX after FSX has been moved to the larger SSD. I've already done hours and hours of customization and work for my FSX install which I'd hate to have to repeat if it wasn't necessary. I would sincerely appreciate any help or advice offered. Thank you so much!!