Pilot53

First I want to thank pmdg for such a great set of addons, the ngx and 777 are the reason I have gotten back into fs after about 6 years off. However, after my second long haul with the 777 I was plagued by OOM issues. What would happen is the vas usage would increase over the duration of the flight, crashing my sim after about 2 hours. After much testing with the 777 I have narrowed it down to going from fullscreen to windowed mode. It seems whenever I would alt + enter I would create a memory leak. The vas usage would just go up over time. So far I have completed two flights (KIAH-PHNL and PHNL-KDEN) after these findings without any oom issues. These flights were conducted with fsdt and flightbeam airports at both ends of the trip complete with aes, gsx, and a total of 5 mse western states enabled in the scenery library. While vas usage was obviously high I was able to complete the 7+ hour flights because vas usage remained relatively constant throughout the flight. I am also running fsx in dx10 mode with the fixer as dx10 has been known to help with oom issues. So if you are having climbing vas usage issues try running fsx in fullscreen without switching to any other windows once you have loaded the aircraft.

Yes but would adding even more vram free up more vas?

After learning that running fsx in dx10 mode can offload some of the ram useage to the vram I am wondering if a gpu with alot of vram can cure oom issues. With the pmdg 777, photoscenery and fsdt airports I am right at the vas limit for fsx. Would more vram help free up some vas space for fsx?

Ive struggled with this issue as well, for me even with no aa at all and default fsx clouds I was getting low fps anytime there were alot of layers or towering cumulus. I found that having water set higher than low 2x caused the fps drop. Must have something to do with how fsx handles cloud reflections

Just wondering if you ever got to the bottom of this as I am having the same issue.

Update: I tried replicating the problem again this time switching from the 777 to a default aircraft and back again with no memory leak. Seems it might have something to do with switching tasks back and forth between fsx.

Ok here's an update, to much photoscenery does indeed cause issues with some users but if you ready my post something else is causing a problem for me. The problem I am having is: vas usage increased over time eventually hitting 4gb over the course of 3 hours or so. Ive tried running fsx again with the same scenery installed but this time the vas usage remained steady. I think the problem might have had to do with switching aircraft over and over and alt tabbing fsx. Earlier today I had problems causing controller disconnects so I was forced to switch from the 777 to a default aircraft and back to the 777 again to get my controller online. Also because of problems with ezdok I was switching views to play with the settings. Maybe some of this had caused a memory leak? It seems in this case its not just a matter of high res settings causing issues but instead a memory leak that causes vas useage to climb continuously.

Well yesterdays flight was ksfo to phnl using fsdt phnl and ksfo scenery. The only difference is today I am flying phnl to kiah and have megascenery az socal nm and west tx loaded as those are the states I am flying through. The inital 3 hours of the flight were over the same area with pretty much the same weather and I was getting an oom issue. I dont think the photoscenery is to blame as I have never had a problem with those scenery areas with the ngx and the vas starts out fine once fsx is loaded.

Hello everyone, I am on my second flight with the 777 and I am having oom issues. Would it be possible for a bad repaint to cause this? I ask because I had no issues yesterday on my first flight but today after modifying the textures of a ual repaint on avsim to include an alpha channel for see through cabin windows I am getting a slow continuous climb of vas usage until fsx crashes. I have read and followed all of the common oom fixes. Thanks, Mike Iacovetta

Hi everyone I am currently doing a long flight on the pmdg 777 and am wondering if anyone knows if there is a hotkey that will disable ezdok "rnd" effects without alt tabbing the sim. If I alt tab I will will lose my controls.

After reading books written by airline pilots and watching cockpit dvd's I notice that before each flight the crew will preform various tests such as, flight control stby hyd, standby pwr, apu fire warn, eng fire warn, cargo fire warn, pressurization etc. but all of this is absent from the normal procedures section of the manuals for the 777 and ngx. Are these tests routinely performed by the crew before each flight in the real world? -Mike Iacovetta

I personally dont notice a fps difference on my system. Anyhow as I sated the issue is not due to rex or cloud resolution as the problem can be replicated with default fsx clouds. It has to do with the way cloud reflections are handled.

yep I've got sp2.

Update: The problem has nothing to do with rex or dx10, as I am able to replicate the problem using a fresh install of fsx without rex and with or without dx10 enabled. I was able to eliminate the problem completely by turning water down to low2x from mid 2x. Mid is the setting that enables cloud reflections, this means the problem is related to cloud reflections.

Im having a strange issue with clouds in dx10 mode. Im using steves dx10 fixer and REX 4 Texture direct with asn. I notice it is not all clouds, just towering cumulus, especially when there are alot of them. There are many posts about this issue relating to AA settings, but i experience this issue even with aa disabled. i have tried resetting rex textures as well. The strange thing is my gpu is not straining at all, only showing about 12% usage.

Ok thanks I have fixed the issue, I do not have my traffic x but for some reason when downloading files from MSE about half of the files are corrupted. The installer will run corrupt archives, after re downloading the affected areas and re installing the crash was fixed.

Ive been getting a crash while flying the pmdg 737ngx over megascenery areas. The crash happens while flying over new mexico and southern california. In new mexico it is approx. 65nm east of the SSO VOR. I dont have the exact location of the socal crash but it is south of the PMD VOR. The crash is reproducible every time using a saved flight file, but only occurs when the offending mse areas are activated in the scenery cfg. The sceneries all installed without a hitch. Ive tried the scenery config tool and it does not detect any errors, I have also rebuild the scenery and shader cache. I have the c++ redistributables and .net sp's installed. An help is greatly appreciated. Specs: Windows 8.1 x64 nvidia 560ti up to date drivers gigabyte p55usb3, latest non beta bios 4gb ddr3 ram i5-750 quad core @3.9ghz Here is the crash view log: Version=1 EventType=APPCRASH EventTime=130500927797424630 ReportType=2 Consent=1 UploadTime=130500927800594816 ReportIdentifier=41dd80e1-0dda-11e4-8268-1c6f65327356 IntegratorReportIdentifier=41dd80e0-0dda-11e4-8268-1c6f65327356 WOW64=1 NsAppName=fsx.exe Response.BucketId=c4b61157195d893912a8cc0b1568ff2c Response.BucketTable=1 Response.LegacyBucketId=-271903774 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=StackHash_a036 Sig[4].Name=Fault Module Version Sig[4].Value=0.0.0.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=00000000 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=PCH_03_FROM_mscorwks+0x00254B2F DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.3.9600.2.0.0.256.4 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=a036 DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=a036f2b77c5930ee2a636a721449cd7c DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=dace DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=dace43eded1523adfa2bae07acbe51b2 UI[2]=C:\FSX\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]=C:\FSX\Microsoft Flight Simulator X\fsx.exe LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll LoadedModule[2]=C:\Windows\SYSTEM32\KERNEL32.DLL LoadedModule[3]=C:\Windows\SYSTEM32\KERNELBASE.dll LoadedModule[4]=C:\Windows\system32\apphelp.dll LoadedModule[5]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[6]=C:\Windows\SYSTEM32\msvcrt.dll LoadedModule[7]=C:\Windows\SYSTEM32\USER32.dll LoadedModule[8]=C:\Windows\SYSTEM32\GDI32.dll LoadedModule[9]=C:\Windows\SYSTEM32\SHELL32.dll LoadedModule[10]=C:\Windows\SYSTEM32\SHLWAPI.dll LoadedModule[11]=C:\Windows\SYSTEM32\OLEAUT32.dll LoadedModule[12]=C:\Windows\SYSTEM32\MPR.dll LoadedModule[13]=C:\Windows\SYSTEM32\SETUPAPI.dll LoadedModule[14]=C:\Windows\SYSTEM32\sfc.dll LoadedModule[15]=C:\Windows\SYSTEM32\WINSPOOL.DRV LoadedModule[16]=C:\Windows\SYSTEM32\RPCRT4.dll LoadedModule[17]=C:\Windows\SYSTEM32\combase.dll LoadedModule[18]=C:\Windows\SYSTEM32\CFGMGR32.dll LoadedModule[19]=C:\Windows\SYSTEM32\SspiCli.dll LoadedModule[20]=C:\Windows\SYSTEM32\sfc_os.DLL LoadedModule[21]=C:\Windows\SYSTEM32\CRYPTBASE.dll LoadedModule[22]=C:\Windows\SYSTEM32\sechost.dll LoadedModule[23]=C:\Windows\SYSTEM32\bcryptPrimitives.dll LoadedModule[24]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[25]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.16384_none_7c55c866aa0c3ff0\COMCTL32.dll LoadedModule[26]=C:\Windows\SYSTEM32\mscms.dll LoadedModule[27]=C:\Windows\SYSTEM32\ADVAPI32.dll LoadedModule[28]=C:\Windows\SYSTEM32\ole32.dll LoadedModule[29]=C:\Windows\SYSTEM32\WINMM.dll LoadedModule[30]=C:\Windows\SYSTEM32\DDRAW.dll LoadedModule[31]=C:\Windows\SYSTEM32\USERENV.dll LoadedModule[32]=C:\Windows\SYSTEM32\COMDLG32.dll LoadedModule[33]=C:\Windows\SYSTEM32\IMM32.dll LoadedModule[34]=C:\Windows\SYSTEM32\WS2_32.dll LoadedModule[35]=C:\Windows\SYSTEM32\dwmapi.dll LoadedModule[36]=C:\Windows\SYSTEM32\msi.dll LoadedModule[37]=C:\Windows\SYSTEM32\WINMMBASE.dll LoadedModule[38]=C:\Windows\SYSTEM32\DCIMAN32.dll LoadedModule[39]=C:\Windows\SYSTEM32\profapi.dll LoadedModule[40]=C:\Windows\SYSTEM32\SHCORE.DLL LoadedModule[41]=C:\Windows\SYSTEM32\MSCTF.dll LoadedModule[42]=C:\Windows\SYSTEM32\NSI.dll LoadedModule[43]=C:\Windows\SYSTEM32\DEVOBJ.dll LoadedModule[44]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL LoadedModule[45]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCR80.dll LoadedModule[46]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[47]=C:\FSX\Microsoft Flight Simulator X\language.dll LoadedModule[48]=C:\FSX\Microsoft Flight Simulator X\API.DLL LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.8428_none_d08a11e2442dc25d\MSVCP80.dll LoadedModule[50]=C:\FSX\Microsoft Flight Simulator X\ablscpt.dll LoadedModule[51]=C:\FSX\Microsoft Flight Simulator X\acontain.dll LoadedModule[52]=C:\FSX\Microsoft Flight Simulator X\ai_player.dll LoadedModule[53]=C:\FSX\Microsoft Flight Simulator X\atc.dll LoadedModule[54]=C:\FSX\Microsoft Flight Simulator X\controls.dll LoadedModule[55]=C:\FSX\Microsoft Flight Simulator X\demo.dll LoadedModule[56]=C:\FSX\Microsoft Flight Simulator X\facilities.dll LoadedModule[57]=C:\FSX\Microsoft Flight Simulator X\fe.dll LoadedModule[58]=C:\FSX\Microsoft Flight Simulator X\flight.dll LoadedModule[59]=C:\FSX\Microsoft Flight Simulator X\fsui.dll LoadedModule[60]=C:\FSX\Microsoft Flight Simulator X\g2d.dll LoadedModule[61]=C:\FSX\Microsoft Flight Simulator X\g3d.dll LoadedModule[62]=C:\FSX\Microsoft Flight Simulator X\gps.dll LoadedModule[63]=C:\FSX\Microsoft Flight Simulator X\livingwater.dll LoadedModule[64]=C:\FSX\Microsoft Flight Simulator X\main.dll LoadedModule[65]=C:\FSX\Microsoft Flight Simulator X\multiplayer.dll LoadedModule[66]=C:\FSX\Microsoft Flight Simulator X\panels.dll LoadedModule[67]=C:\FSX\Microsoft Flight Simulator X\sim1.dll LoadedModule[68]=C:\FSX\Microsoft Flight Simulator X\simprop.dll LoadedModule[69]=C:\FSX\Microsoft Flight Simulator X\simscheduler.dll LoadedModule[70]=C:\FSX\Microsoft Flight Simulator X\sound.dll LoadedModule[71]=C:\FSX\Microsoft Flight Simulator X\symmap.dll LoadedModule[72]=C:\FSX\Microsoft Flight Simulator X\terrain.dll LoadedModule[73]=C:\FSX\Microsoft Flight Simulator X\fs-traffic.dll LoadedModule[74]=C:\FSX\Microsoft Flight Simulator X\ui.dll LoadedModule[75]=C:\FSX\Microsoft Flight Simulator X\util.dll LoadedModule[76]=C:\FSX\Microsoft Flight Simulator X\visualfx.dll LoadedModule[77]=C:\FSX\Microsoft Flight Simulator X\weather.dll LoadedModule[78]=C:\FSX\Microsoft Flight Simulator X\window.dll LoadedModule[79]=C:\FSX\Microsoft Flight Simulator X\xuipc.dll LoadedModule[80]=C:\Windows\SYSTEM32\MSWSOCK.dll LoadedModule[81]=C:\Windows\SYSTEM32\SHFOLDER.dll LoadedModule[82]=C:\Windows\SYSTEM32\VERSION.dll LoadedModule[83]=C:\Windows\SYSTEM32\POWRPROF.dll LoadedModule[84]=C:\Windows\SYSTEM32\DINPUT8.dll LoadedModule[85]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.17056_none_dadc5d1c5bc8ab48\gdiplus.dll LoadedModule[86]=C:\Windows\SYSTEM32\d3dx9_34.dll LoadedModule[87]=C:\FSX\Microsoft Flight Simulator X\d3dx10_34.dll LoadedModule[88]=C:\Windows\SYSTEM32\d3d9.dll LoadedModule[89]=C:\Windows\SYSTEM32\DSOUND.dll LoadedModule[90]=C:\Windows\SYSTEM32\WININET.dll LoadedModule[91]=C:\Windows\SYSTEM32\MSACM32.dll LoadedModule[92]=C:\Windows\SYSTEM32\MSIMG32.dll LoadedModule[93]=C:\Windows\SYSTEM32\MSVCR100.dll LoadedModule[94]=C:\Windows\SYSTEM32\iertutil.dll LoadedModule[95]=C:\FSX\Microsoft Flight Simulator X\reald3dx10_34.DLL LoadedModule[96]=C:\FSX\Microsoft Flight Simulator X\dx10fixerlib.DLL LoadedModule[97]=C:\Windows\SYSTEM32\kernel.appcore.dll LoadedModule[98]=C:\Windows\system32\uxtheme.dll LoadedModule[99]=C:\Windows\SYSTEM32\CRYPTSP.dll LoadedModule[100]=C:\Windows\system32\rsaenh.dll LoadedModule[101]=C:\Windows\SYSTEM32\bcrypt.dll LoadedModule[102]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL LoadedModule[103]=C:\Windows\SYSTEM32\clbcatq.dll LoadedModule[104]=C:\Windows\SYSTEM32\urlmon.dll LoadedModule[105]=C:\Windows\SYSTEM32\dxgi.dll LoadedModule[106]=C:\Windows\SYSTEM32\d3d10.dll LoadedModule[107]=C:\Windows\SYSTEM32\d3d10core.dll LoadedModule[108]=C:\Windows\SYSTEM32\d3d11.dll LoadedModule[109]=C:\Windows\SYSTEM32\nvd3dum.dll LoadedModule[110]=C:\Windows\SYSTEM32\PSAPI.DLL LoadedModule[111]=C:\Windows\system32\nvspcap.dll LoadedModule[112]=C:\Windows\SYSTEM32\CRYPT32.dll LoadedModule[113]=C:\Windows\SYSTEM32\MSASN1.dll LoadedModule[114]=C:\Windows\system32\nvapi.dll LoadedModule[115]=C:\Windows\SYSTEM32\nvwgf2um.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:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[121]=C:\Windows\SYSTEM32\WTSAPI32.DLL LoadedModule[122]=C:\Windows\SYSTEM32\WINSTA.dll LoadedModule[123]=C:\Windows\SYSTEM32\gameux.dll LoadedModule[124]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.17031_none_a9efdb8b01377ea7\COMCTL32.dll LoadedModule[125]=C:\Windows\SYSTEM32\XmlLite.dll LoadedModule[126]=C:\Windows\SYSTEM32\msxml6.dll LoadedModule[127]=C:\Windows\System32\Wpc.dll LoadedModule[128]=C:\Windows\System32\NETAPI32.dll LoadedModule[129]=C:\Windows\SYSTEM32\Normaliz.dll LoadedModule[130]=C:\Windows\System32\wevtapi.dll LoadedModule[131]=C:\Windows\System32\netutils.dll LoadedModule[132]=C:\Windows\System32\srvcli.dll LoadedModule[133]=C:\Windows\System32\wkscli.dll LoadedModule[134]=C:\Windows\System32\SAMCLI.DLL LoadedModule[135]=C:\Windows\System32\Windows.Globalization.dll LoadedModule[136]=C:\Windows\System32\Bcp47Langs.dll LoadedModule[137]=C:\Windows\System32\Windows.Web.dll LoadedModule[138]=C:\Windows\SYSTEM32\taskschd.dll LoadedModule[139]=C:\Windows\system32\propsys.dll LoadedModule[140]=C:\Windows\SYSTEM32\WinTypes.dll LoadedModule[141]=C:\FSX\Microsoft Flight Simulator X\uiautomationcore.dll LoadedModule[142]=C:\Windows\SYSTEM32\OLEACC.dll LoadedModule[143]=C:\Windows\System32\MMDevApi.dll LoadedModule[144]=C:\Windows\SYSTEM32\AUDIOSES.DLL LoadedModule[145]=C:\Windows\SYSTEM32\RICHED20.DLL LoadedModule[146]=C:\Windows\SYSTEM32\USP10.dll LoadedModule[147]=C:\Windows\SYSTEM32\msls31.dll LoadedModule[148]=C:\Windows\SYSTEM32\HID.DLL LoadedModule[149]=C:\Windows\SYSTEM32\WINTRUST.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\XInput1_4.dll LoadedModule[158]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[159]=C:\Windows\SYSTEM32\wbemcomn.dll LoadedModule[160]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[161]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[162]=C:\FSX\Microsoft Flight Simulator X\bglmanx.dll LoadedModule[163]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[164]=C:\Windows\SYSTEM32\inetmib1.dll LoadedModule[165]=C:\Windows\SYSTEM32\IPHLPAPI.DLL LoadedModule[166]=C:\Windows\SYSTEM32\snmpapi.dll LoadedModule[167]=C:\Windows\SYSTEM32\WINNSI.DLL LoadedModule[168]=C:\FSX\Microsoft Flight Simulator X\ORBX\FTX_AU\FTXAA_ORBXLIBS\Scenery\ObjectFlow.dll LoadedModule[169]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[170]=C:\FSX\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_HUD_interface.dll LoadedModule[171]=C:\IVAO\IvAp v2\ivap_fsx_bootstrap.dll LoadedModule[172]=C:\Windows\SYSTEM32\mfc100.dll LoadedModule[173]=C:\Windows\SYSTEM32\MSVCP100.dll LoadedModule[174]=C:\Windows\SYSTEM32\MFC100ENU.DLL LoadedModule[175]=C:\FSX\Microsoft Flight Simulator X\Modules\FSUIPC4.dll LoadedModule[176]=C:\FSX\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dll LoadedModule[177]=C:\FSX\Microsoft Flight Simulator X\VistaMare\bin\VMCX_AP.dll LoadedModule[178]=C:\FSX\Microsoft Flight Simulator X\VistaMare\bin\ViMaNET_AP.dll LoadedModule[179]=C:\FSX\Microsoft Flight Simulator X\as_srv\as_btstrp.dll LoadedModule[180]=C:\Windows\SYSTEM32\mscoree.dll LoadedModule[181]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll LoadedModule[182]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll LoadedModule[183]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\3de119146ed0e59408f896aa69cdfc42\mscorlib.ni.dll LoadedModule[184]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dll LoadedModule[185]=C:\Windows\SYSTEM32\imagehlp.dll LoadedModule[186]=C:\Windows\SYSTEM32\ncrypt.dll LoadedModule[187]=C:\Windows\SYSTEM32\NTASN1.dll LoadedModule[188]=C:\Windows\SYSTEM32\gpapi.dll LoadedModule[189]=C:\Windows\SYSTEM32\cryptnet.dll LoadedModule[190]=C:\Windows\SYSTEM32\WLDAP32.dll LoadedModule[191]=C:\FSX\Microsoft Flight Simulator X\as_srv\as_connect.dll LoadedModule[192]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dll LoadedModule[193]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\20af51394609c937507288c2b1cf2c8c\System.ni.dll LoadedModule[194]=C:\Windows\SYSTEM32\Secur32.dll LoadedModule[195]=C:\Windows\SYSTEM32\ieframe.dll LoadedModule[196]=C:\Windows\System32\IDStore.dll LoadedModule[197]=C:\Windows\System32\SAMLIB.dll LoadedModule[198]=C:\Windows\System32\wlidprov.dll LoadedModule[199]=C:\Windows\SYSTEM32\mshtml.dll LoadedModule[200]=C:\Windows\system32\msimtf.dll LoadedModule[201]=C:\Windows\SYSTEM32\d2d1.dll LoadedModule[202]=C:\Windows\SYSTEM32\DWrite.dll LoadedModule[203]=C:\Windows\SYSTEM32\d3d10warp.dll LoadedModule[204]=C:\Windows\SYSTEM32\MLANG.dll LoadedModule[205]=C:\FSX\Microsoft Flight Simulator X\VistaMare\bin\ViMaIScnX_AP.dll LoadedModule[206]=C:\FSX\Microsoft Flight Simulator X\GAUGES\PMDG_737NGX.DLL LoadedModule[207]=C:\Windows\SYSTEM32\WSOCK32.dll LoadedModule[208]=C:\Windows\SYSTEM32\XAudio2_7.dll LoadedModule[209]=C:\FSX\Microsoft Flight Simulator X\GAUGES\PMDG_737NGX_3.DLL LoadedModule[210]=C:\Windows\SYSTEM32\uiautomationcore.dll LoadedModule[211]=C:\FSX\Microsoft Flight Simulator X\Gauges\PMDG_737NGX_2.dll LoadedModule[212]=C:\Windows\system32\napinsp.dll LoadedModule[213]=C:\Windows\system32\pnrpnsp.dll LoadedModule[214]=C:\Windows\system32\NLAapi.dll LoadedModule[215]=C:\Windows\SYSTEM32\DNSAPI.dll LoadedModule[216]=C:\Windows\System32\winrnr.dll LoadedModule[217]=C:\Windows\System32\fwpuclnt.dll LoadedModule[218]=C:\Windows\System32\rasadhlp.dll LoadedModule[219]=C:\Windows\SYSTEM32\icmp.Dll LoadedModule[220]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Drawing\d76ae95d56d39a59f727f5518ac8e396\System.Drawing.ni.dll LoadedModule[221]=C:\Windows\SYSTEM32\msadp32.acm LoadedModule[222]=C:\FSX\Microsoft Flight Simulator X\Aerosoft\AES\ViMaCli.dll LoadedModule[223]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Configuration\97272e5adde36ea896d7216bf0270e15\System.Configuration.ni.dll LoadedModule[224]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System.Xml\672138dc2f47a077f59ef14290a6973e\System.Xml.ni.dll State[0].Key=Transport.DoneStage1 State[0].Value=1 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft Flight Simulator® AppPath=C:\FSX\Microsoft Flight Simulator X\fsx.exe NsPartner=windows NsGroup=windows8 ApplicationIdentity=31736CD664C91611E8FACF7B443412D4

Thanks for the reply. I tried the demo for fs fiber accelerator and all it did for me was unlock the frame rate when at high detail areas which gave me the same fps as I got without it using an external limiter. Ive realized alot of the problem I was having with high detail areas had do do with the mouse cursor issue and the ngx, as long as I can keep the cursor hidden I get smooth performance. It seems now that my biggest killer is large storm systems with lots of high cumulonimbus using asn. I wonder if upgrading my gpu would help in this area, are clouds more gpu or cpu dependant?

Right now Im running a lynnfield i5 750 1156 quad clocked at 3.9ghz with an nvidia 560ti. The addons I use are asn, pmdg ngx, rex, and some orbx na with the latest cfg tweaks. FSX runs smooth as butter most of the time but flying into high detail addon airports in large cities causes to fps to drop into the 20's. Do you think I will see much of a performance boost by upgrading to a 680 and a newer socket 1150 cpu or is it not worth the money and time investment right now.