BonanzaPilot

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

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

Will do. I will test this later and report my results. Thanks.

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

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

Edit: Disregard.

It appears that OpusFSX might be causing fatal errors for me. Maybe it's just coincidence, but I never get a fatal error when I just start FSX without Opus. However, when I open OpusFSX and then start FSX, 90% of the time I get a fatal error on the opening screen. Anyone have any ideas? Thanks. Edit... OpusFSX cannot cause fatal errors within FSX, it interfaces entirely through the SimConnect so any fatal errors have nothing to do with OpusFSX, other than you may have detailed and varied RW weather injected. Stephen

Thanks a ton.

I have found many people saying that they have the FlyTampa KSEA working in FSX. However, the website containing the patch is down. Does anyone know where I can find this patch? Thanks for the help.

Figured it out.... it was my settings. :Doh:

I just purchased a new hard drive after my other one became corrupt and had to reinstall everything. Today I went on a test flight in the NGX and the sound was very quiet. It wasn't like this on my old hard drive and all of my settings are set properly. Any ideas as to what could be causing this? Thanks.

My old hard drive became corrupt and today I purchased a new one. After hours of reinstalling my flight sim stuff, my CH Pedals/Yoke are not being recognized. However, my Saitek X52 throttle is recognized and works fine. I have updated the drivers for all my computer parts but it is still not working. I couldn't find any drivers for the yoke/pedals. I am using Windows 7 64 bit. Does anyone know what could be causing this problem. Thanks a lot.

My older Seagate hard drive is starting to give out on me and I think it's time for an upgrade. Would anyone have any suggestions for a nice hard drive for FSX Win 7 64 bit? Thanks.

Thanks again for all of the help guys. Here is what I have in my basket but I want to check once more before ordering: http://f.cl.ly/items/2T1Q1l1o0Q3V0w13181a/Screen%20Shot%202013-01-01%20at%209.17.34%20PM.png How's it look?

Right now I am getting around 40fps in FS9. I don't really have a set number I'd like to get in FSX, I just want it to be smooth, so probably around 20. As for cooling, I am not really sure what I am using. Thanks.

Thanks for that. If I were to get the 3770k and a slightly worse motherboard would I have better frames than I will with the 3570k and the motherboard I posted?

Hey guys, I am wanting to upgrade my computer to run FSX with pretty high settings. Haven't really thought about a price limit at the moment, but I'd like to keep it reasonable. I am currently running FS9 with tons of scenery, REX, ActiveSky Evolution, GEPro, iFly 737, etc. I am also using 3 monitors with Eyefinity. If I upgrade to FSX I want to run the same addons but with the PMDG 737. My current setup: -i5-750 Lynnfield 2.67GHz CPU. -Foxconn P55MX motherboard -Sapphire 6950 Flex Edition Vid Card with Eyefinity(3 24" monitors) -2GB ram This is what I am looking at upgrading: -Ram: http://www.newegg.co...N82E16820233240 -Motherboard: http://www.newegg.co...N82E16813131819 -CPU(which I will overclock): http://www.newegg.co...N82E16819116501 What kind of frames can I expect to get with 3 monitors, GEPro, PMDG 737, REX, and other airport sceneries? Thanks for the help.

Thanks guys. Matt

Hello, First off, I love the product and will not fly without it. It has enhanced my simming experience greatly. However, is there any possible way I can customize some small things? For example, I would like the F/A landing announcement on descent to be done at 10,000 ft, rather than 5,000 ft. I would also like the F/O to turn off the lights at 18,000 ft. and let me have full control over the seatbelt sign, rather than him turning it off at 10,000 ft. Is this possible at all? Thanks for the help.

No Turkish sceneries. Mainly stay in North and South America. However, I have completed 3 flights with no issues. Two 2.5 hr and one 3.5 hr. They had a lot of weather involved to so I think the fix worked? Thanks for all of the help.

Had a successful flight today with no OOM error. I am assuming 2560 works then? Thanks for all of the help, I really appreciate it!

Using a 2GB card running 3 monitors with EyeFinity. What number would you recommend? Is there any way that I can check if the patch is working while running FS? Thanks for all of the help.

Disregard

Yes, I patched FS9 with Explorer Suite and I am running Win7 x32. I wanted to make sure the number in the bcdedit command was supposed to be 2560. Thanks!

Hey guys, I am currently running FS9 on Windows 7. Lately, I have been getting Out of Memory errors about every other flight. Today I decided to apply the 3GB patch to stop the error. I followed the guide seen here: http://forum.simflight.com/topic/55994-set-fs-and-winxp-to-use-the-3gb-switch/ However, I don't believe the boot.ini file can be manually edited in Windows 7. When looking online I found that you can add the line: bcdedit /set IncreaseUserVa 2560 into Pommand Prompt. Command Prompt said that this was successful. Is this all that I needed to do to install the 3GB or did I do something wrong? Is there any way that I can check to see if FS9 is able to successfully use more than 2GB now? If I did this wrong, could someone please point me in the right direction for the 3GB patch on Windows 7? Thanks for the help.