March 21, 201313 yr After a clean installation (as was having issues with PMDG MD11) of Win7 64bit, FSX, and the add ons that I can't live without I figure out my StackHash issue at the closing of FSX. I check one by one when installing the add ons. Ex. LVL-D: installed, tested, exited, reboot and after verifying no problems on closing FSX, reboot again, then installed next addon PMDG/737.....and same steps. When I had the FSX tweaked and pretty much done to my satisfaction with no error whatsoever when closing and so on, I decided to install FSCopilot + FSINN for the VATSIM connection...guess what? Yep, when closing FSX now I get the error message: Problem signature: Problem Event Name: BEX Application Name: fsx.exe Application Version: 10.0.61472.0 Application Timestamp: 475e17d3 Fault Module Name: StackHash_27eb Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Offset: 74b9c9f1 Exception Code: c0000005 Exception Data: 00000008 OS Version: 6.1.7600.2.0.0.256.1 Locale ID: 1033 Additional Information 1: 27eb Additional Information 2: 27eb358fe674a6f15dafe56d42bb9bf3 Additional Information 3: 2f06 Additional Information 4: 2f06c18113e6d7c00e6b91fa1fde84b6 If I remove FSINN and FSCopilot the error message dissappears, however, it damages the EZdok camera for the FSX, hence, new installation is required. At least I know for sure that the StackHash culprit is when I install FSCopilot + FSINN. The weird part is that I have 2 systems, they are pretty much clone of each other, except one system has 64G Mem and the other one 32G, other than that, they are identical, on one I don't get the error, even though it has the same installation. I go and try to figure, Jay Marin
March 21, 201313 yr Author I can't believe you are trying to understand these crashes! :lol: Some have no problems whatsoever installing and running FSInn and FSCoPilot. I think if you study the installation of FSInn and FSCoPilot, you'll probably see there's a switch in the setup configuration that fixes these problems. I don't use them but have read of reports where, if you tick this box, they will work great together. When you stated one system has 64G mem and the other one 32G, I assume you mean one computer has the 64 bit operating system and the other one has the 32 bit operating system. A 64 bit OS manages memory better than a 32 bit. A 64 bit system can use up to 4GB of system RAM for fsx. The rest of your RAM is used for the operating system to function properly. A 32 bit OS can only use up to 2GB of system RAM for FSX unless you employ the so-called /3GB switch which allows FSX to use up to 3GBs. :Applause: Thanks for posting your findings. When I see a crash in FSX, one of the first things I look for is the installation of FSInn and FSCopilot. Another one is the ENB Series module (d3d9.dll). 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
March 21, 201313 yr LOL. I think there is an "evil dwarf" inside my computer just messing with me. I will try to find out more on the FSINN and FSCopilot box to see if I can fix the problem. Thanks for the tips. BTW: The difference is the memory, one has 64Gb and the other one 32Gb, same 64 bit OS. Take care. Jay Jay Marin
June 3, 201313 yr Sigh, looks like asof lately I've been experiencing a lot of strange ctd as well. BEX, stackhash mostly. I'm not sure why all of a sudden. I don't recall having this many crashes before. I haven't been using FSX much, been using Xplane, but finally decided to go back to FSx and then I have to deal with these frustrating issues that I can't seem to fi d out the cause of them. This is what annoys me the most about FSX. I really want to enjoy it but I spend most of my time tweaking and trying to fix these crashes. The only thing that I've done different is have updated my video drivers and also changed a few settings in nvidia inspector. Not sure if the 16x antialiasing has any effect on these ctd's. anyhow I decided to rename my original fsx.cfg file and let the game create a new one from scratch. I see a lot of different behaviors with load times, it is significantly faster. Before it would usually hang at 6% and then take awhile for the progress bar to fill up, now it's almost instant. With that, brings up a new set of problems now. When flying the pmdg 747, the left side pfd, hd and fmc are black, while the ones on the right side are on and working like it should. I swear fits not one thing it's another. I've spent all night til the morning trying to figure out whats causing all these weird issues. I have reached a stopping point where I feel like just giving up. I spent roughly around$1700 to build a new computer just to run FSX and to find out that I can barely enjoy the game due to constant issues that keep popping up makes me wonder if that investment was even worth it. Sigh, sorry everyone. I just have a lot on my shoulder and wanted to vent. I really want to be able to fix these issues so that I can go back and enjoy flying one of my favorite flight sims again. But at this point I really don't know what to do next. I want to avoid reinstalling windows 7 and fsx from scratch at all costs. That's just way too time consuming for me. It's silly that I have to spend 75% troubleshooting these issues rather than enjoying the game. I suppose the next thing ill do is start going overly fsx.cfg settings and nvidia inspector settings to see if I can fix the problem, if not then i will get ridof sweetfx to see if that fixes the problems, and then lastly, get rid of my dll.xml file and let fsx build a new one. I really don't know what else to do. ASUS ROG Maximus Hero XII ▪︎ Intel i9-10900K ▪︎ NVIDIA RTX 3090 FE ▪︎ 64GB Corsair Vengeance RGB Pro ▪︎ Windows 10 Pro (21H1) ▪︎ Samsung 970 EVO Pro 1TB NVME SSD (OS Drive) ▪︎ Samsung 860 EVO 2TB SATA SSD ▪︎ Seagate 4TB SATA HDD ▪︎ Corsair RMx 850W PSU
June 3, 201313 yr Author You are getting close to an OOM (Out of Memory). Try this fix - http://support.microsoft.com/kb/947246. This will increase your heap limitation in Windows and give you some more space for fsx to breathe. You can then keep your settings set to the highest level as that appears to be what you want to do. FSX does not work well with high settings but people think they will get the best eye-candy if the settings are maxed out. I totally disagree with this concept and I have perfect crisp clear graphics and mostly high fps with conservative settings (NI settings are the default set by Nvidia techs for FSX). I do have my LOD_Radius set to 6.5 and Texture_Max_Load at 2048 but I run mainly photoscenery and those settings work the best. You can also try out DX10 by looking in the DX10 forum. Most of the issues have been fixed and more are coming. DX10 will give you more performance and better graphics if you stay away from FS9 stuff in FSX. And yes, 16x AA will place a lot on your system resources making it harder and harder for FSX to render a texture. You will definitely enjoy fsx much more by placing your NI or display driver settings to the default for FSX. Use Texture_Max_Load and LOD_Radius settings to make things more crisper but be careful as you are again starting to take up more resources. Placing a lot of so-called tweaks in the fsx.cfg will create problems too. The most popular screw up is the BufferPool settings. I leave it out as none of the settings do anything for my system. Affinity mask is set to 14 on my system and, in the Terrain section I lowered the number of autogen that is rendered by entering the following: TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=1000TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=800 Some individuals also put their Texture_Bandwidth_Multi too high too and that can have a detrimental affect on fsx. It should be no higher than 80 in modern systems. I have been using 40 or 80. 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
June 4, 201313 yr Jim, thanks for your help. Ill try that fix tonight and see how it goes. I am using Windows 7 ultimate 64bit, 16gb ram, evga gtx 680gb ftw 4gb, 30inch monitor running at 2560x1600, I7-3770k overclocked to 4.5ghz. I sometimes wonder if its my hardware. Maybe since its the summer that my computer is running a few degrees hotter that it can cause these random crashes? Sometimes in the middle of flying it will give me a blue screen and reboot. Strange as I never had this problem before. The same happened to me when in xplane. So maybe it's not an fsx problem but a hardware problem that has to do with heat since I am overclocked? ASUS ROG Maximus Hero XII ▪︎ Intel i9-10900K ▪︎ NVIDIA RTX 3090 FE ▪︎ 64GB Corsair Vengeance RGB Pro ▪︎ Windows 10 Pro (21H1) ▪︎ Samsung 970 EVO Pro 1TB NVME SSD (OS Drive) ▪︎ Samsung 860 EVO 2TB SATA SSD ▪︎ Seagate 4TB SATA HDD ▪︎ Corsair RMx 850W PSU
June 4, 201313 yr Author I am using Windows 7 ultimate 64bit, 16gb ram, evga gtx 680gb ftw 4gb, 30inch monitor running at 2560x1600, I7-3770k overclocked to 4.5ghz. I sometimes wonder if its my hardware. I doubt it is the hardware as you have a very nice system but you still won't be able to max everything out and you'll need a couple of tweaks to help. You might be able to run on max for a few sessions or a few hours but eventually it will CTD depending on the scenario. FSX does not need max settings to look pretty. 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
June 5, 201312 yr Jim, I finally decided to switch to DX10 mode and letting FSX build a new fsx.cfg file. I started from scratch and followed Paul's latest guide to set everything up. Hoping that this would fix my stackhash CTD errors. It still happens. I was flying in the PMDG 747-8i from KSEA to KLAX, and about 30 minutes into the flight, it CTD again. Sigh. I really am running out of ideas at this point as I don't know what else to do. I tried all the recommended fixes, like the heap limitation fix, disabling services, etc. I am starting to think maybe it's because I have no paging file set in Windows 7? In Paul's guide it didn't mention anything about an SSD. But I have my main OS installed on my 128GB SSD. Should I set my pagefile there with a 3072/3072mb min/max size limit and see if this fixes the issue? I have 16GB of physical ram, but I heard that most people say to have a pagefile set, because a few older programs require it and without one, one could face OOM errors? ASUS ROG Maximus Hero XII ▪︎ Intel i9-10900K ▪︎ NVIDIA RTX 3090 FE ▪︎ 64GB Corsair Vengeance RGB Pro ▪︎ Windows 10 Pro (21H1) ▪︎ Samsung 970 EVO Pro 1TB NVME SSD (OS Drive) ▪︎ Samsung 860 EVO 2TB SATA SSD ▪︎ Seagate 4TB SATA HDD ▪︎ Corsair RMx 850W PSU
June 5, 201312 yr Author I am starting to think maybe it's because I have no paging file set in Windows 7? In Paul's guide it didn't mention anything about an SSD. But I have my main OS installed on my 128GB SSD. Should I set my pagefile there with a 3072/3072mb min/max size limit and see if this fixes the issue? I have 16GB of physical ram, but I heard that most people say to have a pagefile set, because a few older programs require it and without one, one could face OOM errors? I would at least set it to system managed size. 16GB of RAM is overdoing it for fsx as FSX, on a 64 bit system, cannot use more than 4GB and the rest you have installed will be used for system apps/services. StackHash crashes are caused by memory being stuck at a certain address (the last four digits is where the address is located). The following article regarding Page Files should be checked out - http://lifehacker.com/5426041/understanding-the-windows-pagefile-and-why-you-shouldnt-disable-it. I cannot get back to the page where we might have had previous discussions but want to make sure you tried disabling your DEP as proposed in the following link here - http://forum.avsim.net/topic/403927-hooray-instructions-to-get-no-more-dep-induced-bev-or-stack-errorscrashes/. Supposedly it has worked for some. It doesn't hurt to try. Here's another link regarding the subject - http://www.vistax64.com/tutorials/120778-dep-enable-disable.html. It is for Vista but it works on Windows 7 and 8 systems too. 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
July 14, 201312 yr i have the same Problem -.- nothing help -.- Version=1EventType=APPCRASHEventTime=130182732319574248ReportType=2Consent=1ReportIdentifier=996d2377-ec74-11e2-a71d-902b3458479bIntegratorReportIdentifier=996d2376-ec74-11e2-a71d-902b3458479bWOW64=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=StackHash_61bdSig[4].Name=FehlermodulversionSig[4].Value=0.0.0.0Sig[5].Name=FehlermodulzeitstempelSig[5].Value=00000000Sig[6].Name=AusnahmecodeSig[6].Value=c0000005Sig[7].Name=AusnahmeoffsetSig[7].Value=7530c9f1DynamicSig[1].Name=BetriebsystemversionDynamicSig[1].Value=6.1.7601.2.1.0.256.48DynamicSig[2].Name=Gebietsschema-IDDynamicSig[2].Value=1031DynamicSig[22].Name=Zusatzinformation 1DynamicSig[22].Value=61bdDynamicSig[23].Name=Zusatzinformation 2DynamicSig[23].Value=61bd2fe06cc73a7800cc1eec71f5995bDynamicSig[24].Name=Zusatzinformation 3DynamicSig[24].Value=ca25DynamicSig[25].Name=Zusatzinformation 4DynamicSig[25].Value=ca252c14c03101a0f921bbff7c508f1cUI[2]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exeUI[3]=Microsoft Flight Simulator® funktioniert nicht mehrUI[4]=Windows kann online nach einer Lösung für das Problem suchen.UI[5]=Online nach einer Lösung suchen und das Programm schließenUI[6]=Später online nach einer Lösung suchen und das Programm schließenUI[7]=Programm schließenLoadedModule[0]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\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.6229_none_cbee8c4a4710d003\MFC80.DLLLoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6229_none_d089f796442de10e\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.6229_none_03c6cf28205ff947\MFC80DEU.DLLLoadedModule[60]=C:\Windows\SysWOW64\guard32.dllLoadedModule[61]=C:\Windows\system32\fltlib.dllLoadedModule[62]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\language.dllLoadedModule[63]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\API.DLLLoadedModule[64]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6229_none_d089f796442de10e\MSVCP80.dllLoadedModule[65]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ablscpt.dllLoadedModule[66]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\flight.dllLoadedModule[67]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ai_player.dllLoadedModule[68]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\acontain.dllLoadedModule[69]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\controls.dllLoadedModule[70]=C:\Windows\system32\DINPUT8.dllLoadedModule[71]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsui.dllLoadedModule[72]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\atc.dllLoadedModule[73]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\facilities.dllLoadedModule[74]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\demo.dllLoadedModule[75]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\main.dllLoadedModule[76]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fe.dllLoadedModule[77]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\util.dllLoadedModule[78]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simprop.dllLoadedModule[79]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g2d.dllLoadedModule[80]=C:\Windows\system32\d3dx9_34.dllLoadedModule[81]=C:\Windows\system32\d3dx10_34.dllLoadedModule[82]=C:\Windows\system32\d3d9.dllLoadedModule[83]=C:\Windows\system32\d3d8thk.dllLoadedModule[84]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\g3d.dllLoadedModule[85]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\panels.dllLoadedModule[86]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\multiplayer.dllLoadedModule[87]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ui.dllLoadedModule[88]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sound.dllLoadedModule[89]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\sim1.dllLoadedModule[90]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\simscheduler.dllLoadedModule[91]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\visualfx.dllLoadedModule[92]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\window.dllLoadedModule[93]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\terrain.dllLoadedModule[94]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\weather.dllLoadedModule[95]=C:\Windows\system32\DSOUND.dllLoadedModule[96]=C:\Windows\system32\POWRPROF.dllLoadedModule[97]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\symmap.dllLoadedModule[98]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dllLoadedModule[99]=C:\Windows\system32\MSIMG32.dllLoadedModule[100]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\xuipc.dllLoadedModule[101]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\livingwater.dllLoadedModule[102]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fs-traffic.dllLoadedModule[103]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\gps.dllLoadedModule[104]=C:\Windows\system32\MSWSOCK.dllLoadedModule[105]=C:\Windows\system32\SHFOLDER.dllLoadedModule[106]=C:\Windows\system32\CRYPTSP.dllLoadedModule[107]=C:\Windows\system32\rsaenh.dllLoadedModule[108]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLLLoadedModule[109]=C:\Windows\system32\dxgi.dllLoadedModule[110]=C:\Windows\system32\d3d11.dllLoadedModule[111]=C:\Windows\syswow64\WINTRUST.dllLoadedModule[112]=C:\Windows\syswow64\CRYPT32.dllLoadedModule[113]=C:\Windows\syswow64\MSASN1.dllLoadedModule[114]=C:\Windows\system32\nvd3dum.dllLoadedModule[115]=C:\Windows\syswow64\PSAPI.DLLLoadedModule[116]=C:\Windows\system32\D3DCompiler_34.dllLoadedModule[117]=C:\Windows\system32\WindowsCodecs.dllLoadedModule[118]=C:\Windows\system32\d3d10_1.dllLoadedModule[119]=C:\Windows\system32\d3d10_1core.dllLoadedModule[120]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dllLoadedModule[121]=C:\Windows\syswow64\CLBCatQ.DLLLoadedModule[122]=C:\Windows\SysWOW64\dxdiagn.dllLoadedModule[123]=C:\Windows\SysWOW64\d3d10.dllLoadedModule[124]=C:\Windows\SysWOW64\d3d10core.dllLoadedModule[125]=C:\Windows\system32\wbem\wbemprox.dllLoadedModule[126]=C:\Windows\system32\wbemcomn.dllLoadedModule[127]=C:\Windows\system32\RpcRtRemote.dllLoadedModule[128]=C:\Windows\system32\wbem\wbemsvc.dllLoadedModule[129]=C:\Windows\system32\wbem\fastprox.dllLoadedModule[130]=C:\Windows\system32\NTDSAPI.dllLoadedModule[131]=C:\Windows\system32\winbrand.dllLoadedModule[132]=C:\Windows\system32\nvapi.dllLoadedModule[133]=C:\Windows\system32\WTSAPI32.DLLLoadedModule[134]=C:\Windows\system32\WINSTA.dllLoadedModule[135]=C:\Windows\SysWOW64\gameux.dllLoadedModule[136]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dllLoadedModule[137]=C:\Windows\SysWOW64\XmlLite.dllLoadedModule[138]=C:\Windows\SysWOW64\wer.dllLoadedModule[139]=C:\Windows\System32\Wpc.dllLoadedModule[140]=C:\Windows\System32\wevtapi.dllLoadedModule[141]=C:\Windows\System32\msxml6.dllLoadedModule[142]=C:\Windows\system32\SAMLIB.dllLoadedModule[143]=C:\Windows\system32\netutils.dllLoadedModule[144]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\uiautomationcore.dllLoadedModule[145]=C:\Windows\system32\OLEACC.dllLoadedModule[146]=C:\Windows\System32\MMDevApi.dllLoadedModule[147]=C:\Windows\System32\PROPSYS.dllLoadedModule[148]=C:\Windows\system32\AUDIOSES.DLLLoadedModule[149]=C:\Windows\system32\RICHED20.DLLLoadedModule[150]=C:\Windows\system32\HID.DLLLoadedModule[151]=C:\Windows\system32\XInput9_1_0.dllLoadedModule[152]=C:\Windows\system32\wdmaud.drvLoadedModule[153]=C:\Windows\system32\ksuser.dllLoadedModule[154]=C:\Windows\system32\AVRT.dllLoadedModule[155]=C:\Windows\system32\msacm32.drvLoadedModule[156]=C:\Windows\system32\midimap.dllLoadedModule[157]=C:\Windows\system32\dinput.DLLLoadedModule[158]=C:\Windows\system32\BfLLR.dllLoadedModule[159]=C:\Windows\system32\IPHLPAPI.DLLLoadedModule[160]=C:\Windows\system32\WINNSI.DLLLoadedModule[161]=C:\Windows\System32\wship6.dllLoadedModule[162]=C:\Windows\System32\wshtcpip.dllLoadedModule[163]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\bglmanx.dllLoadedModule[164]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dllLoadedModule[165]=C:\Windows\system32\inetmib1.dllLoadedModule[166]=C:\Windows\system32\snmpapi.dllLoadedModule[167]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FsPassengers\bin\fspassengersx.dllLoadedModule[168]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NZ\FTX_NZNI_05_SCENERY\scenery\ObjectFlow_NZNI.dllLoadedModule[169]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dllLoadedModule[170]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_W16\scenery\ObjectFlow_W16.dllLoadedModule[171]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NZ\FTX_AA_NZMF\Scenery\ObjectFlow_NZMF.dllLoadedModule[172]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_PAKT\Scenery\ObjectFlow_PAKT.dllLoadedModule[173]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_AU\FTXAA_YBCS\scenery\ObjectFlow_YBCS.dllLoadedModule[174]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KCMW\Scenery\ObjectFlow_KCMW.dllLoadedModule[175]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_AU\FTXAA_YWOL\Scenery\ObjectFlow_YWOL.dllLoadedModule[176]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_KJAC\Scenery\ObjectFlow_KJAC.dllLoadedModule[177]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_AU\FTXAA_YMML\Scenery\ObjectFlow_YMML.dllLoadedModule[178]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_2WA1\Scenery\Objectflow_2WA1.dllLoadedModule[179]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\ORBX\FTX_NA\FTX_AA_1WA6\Scenery\ObjectFlow_1WA6.dllLoadedModule[180]=C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dllLoadedModule[181]=C:\Windows\system32\mfc100.dllLoadedModule[182]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\MSVCR100.dllLoadedModule[183]=C:\Windows\system32\MSVCP100.dllLoadedModule[184]=C:\Windows\system32\MFC100DEU.DLLLoadedModule[185]=C:\Windows\system32\ntmarta.dllLoadedModule[186]=C:\Windows\syswow64\WLDAP32.dllLoadedModule[187]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDG_HUD_interface.dllLoadedModule[188]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDGOptions.dllLoadedModule[189]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG_SimConnect_Ldr.dllLoadedModule[190]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.7523_none_508f21ccbcbbb7a8\MSVCP90.dllLoadedModule[191]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.7523_none_508f21ccbcbbb7a8\MSVCR90.dllLoadedModule[192]=C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.7523_none_4bf3b680bf9ea69d\mfc90.dllLoadedModule[193]=C:\Windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.7523_none_49726193754be3af\MFC90DEU.DLLLoadedModule[194]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDGEvents.dllLoadedModule[195]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\PMDG\DLLs\PMDGSounds.dllLoadedModule[196]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\WaveLib.dllLoadedModule[197]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Aerosoft\Flight Recorder\AS-FlightRecorder.dllLoadedModule[198]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\ViMaCoreX.dllLoadedModule[199]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\VMCX_AP.dllLoadedModule[200]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\ViMaNET_AP.dllLoadedModule[201]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Captain_Sim\777\cs.sound.dllLoadedModule[202]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Addon Modules\AirbusNewHUD.dllLoadedModule[203]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\LVLD.dllLoadedModule[204]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\LVLDLanguage.dllLoadedModule[205]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Level-D Simulations\B767-300\leveld.dllLoadedModule[206]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4_Loader.dllLoadedModule[207]=C:\Windows\system32\msadp32.acmLoadedModule[208]=C:\Windows\SysWOW64\ieframe.dllLoadedModule[209]=C:\Windows\SysWOW64\api-ms-win-downlevel-shlwapi-l2-1-0.dllLoadedModule[210]=C:\Windows\SysWOW64\api-ms-win-downlevel-advapi32-l2-1-0.dllLoadedModule[211]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dllLoadedModule[212]=C:\Windows\system32\Secur32.dllLoadedModule[213]=C:\Windows\SysWOW64\mshtml.dllLoadedModule[214]=C:\Windows\system32\msimtf.dllLoadedModule[215]=C:\Windows\system32\msls31.dllLoadedModule[216]=C:\Windows\system32\d2d1.dllLoadedModule[217]=C:\Windows\system32\DWrite.dllLoadedModule[218]=C:\Windows\system32\D3D10Warp.dllLoadedModule[219]=C:\Windows\system32\MLANG.dllLoadedModule[220]=C:\Windows\SysWOW64\uiautomationcore.dllLoadedModule[221]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\VistaMare\bin\ViMaIScnX_AP.dllLoadedModule[222]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLLLoadedModule[223]=C:\Windows\SysWow64\XAudio2_7.dllLoadedModule[224]=C:\Windows\system32\NLAapi.dllLoadedModule[225]=C:\Windows\system32\napinsp.dllLoadedModule[226]=C:\Windows\system32\pnrpnsp.dllLoadedModule[227]=C:\Windows\system32\DNSAPI.dllLoadedModule[228]=C:\Windows\System32\winrnr.dllLoadedModule[229]=C:\Windows\system32\wshbth.dllLoadedModule[230]=C:\Program Files (x86)\Bonjour\mdnsNSP.dllLoadedModule[231]=C:\Windows\System32\fwpuclnt.dllLoadedModule[232]=C:\Windows\system32\rasadhlp.dllLoadedModule[233]=C:\Windows\system32\icmp.DllLoadedModule[234]=C:\Windows\system32\asycfilt.dllLoadedModule[235]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_737NGX.DLLLoadedModule[236]=C:\Windows\system32\NETAPI32.dllLoadedModule[237]=C:\Windows\system32\srvcli.dllLoadedModule[238]=C:\Windows\system32\wkscli.dllLoadedModule[239]=C:\Windows\system32\WSOCK32.dllLoadedModule[240]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\GAUGES\PMDG_737NGX_3.DLLLoadedModule[241]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Gauges\PMDG_737NGX_2.dllLoadedModule[242]=C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx.dllLoadedModule[243]=C:\Program Files (x86)\IVAO\IvAp v2\ivap_usrint_resources.dllLoadedModule[244]=C:\Windows\system32\dhcpcsvc6.DLLLoadedModule[245]=C:\Windows\System32\netprofm.dllLoadedModule[246]=C:\Windows\system32\dhcpcsvc.DLLLoadedModule[247]=C:\Windows\System32\npmproxy.dllLoadedModule[248]=C:\Program Files (x86)\IVAO\IvAp v2\TSRemote.dllLoadedModule[249]=C:\Windows\system32\RICHED32.DLLLoadedModule[250]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\FsPassengers\bin\FsPassengersMini.DLLFriendlyEventName=Nicht mehr funktionsfähigConsentKey=APPCRASHAppName=Microsoft Flight Simulator®AppPath=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
July 14, 201312 yr Author Uiautomationcore.dll - I would remove the uiautomationcore.dll from your main FSX directory. Since you did get a crash, the Vista version obviously did not stop it. The uiautomationcore.dll only fixes one problem and that's a crash if you repeatedly hit the FSX menu bar. I personally cannot replicate this crash and have tried several times to crash my FSX by repeatedly clicking on the fsx menu bar. No joy... I really think the menu bar crash is caused by high settings where fsx is running short of memory by the constant hitting on the menu bar. I do not have the uiautomationcore.dll in my main fsx folder and never have. The uiautomationcore.dll belongs with the Microsoft.net framework packages and, developers of FSX and FSX addons require dotnet versions 1.1 thru 4.5 installed to make their products work properly. I believe the Vista version of dotnet is 1.1 as it is installed with FSX/Acceleration. Microsoft Visuals - Your Microsoft Visual C++ 2005 and 2008 program is completely out of date. Here's the latest - http://www.microsoft...s.aspx?id=26347, http://www.microsoft...s.aspx?id=26368. And, just in case the 2010 version is out-of-date, here's the latest version of that very important program (PMDG is using the 2010 version) - http://www.microsoft...s.aspx?id=26999. You might take a look at FSPassengers. It might have been the last module loaded before the crash. The Bonjour Service for iTunes and other Apple products has been known to cause problems with FSX. Possibly checking for updates or whatever that product does. No indications it caused this crash though. Just for your information. I found it very interesting that the Microsoft Visual C++ 2010 module (MSVCR100.dll) is located in your main FSX folder: LoadedModule[182]=X:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\MSVCR100.dll. It should not be there. It could be conflicting with the system module with the same name. It's very possible this is the thing that is causing your crashes as the PMDG737NGX uses this 2010 module. 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
July 17, 201312 yr I am now getting these CTOD's after installing and running Flight1 B200. I looked into the out of memory issues but my settings are what MS says they should be 20480 for the second value. I have not had any problems with any of my other add-ons until this one Flight1 B200 any suggestions?? Also, this last one happened while using the Andriod app at the same time using the 2D pop-up. The app is a cool concept but too slow. Thanks, Ray
July 17, 201312 yr Author Also, this last one happened while using the Andriod app at the same time using the 2D pop-up. The app is a cool concept but too slow. I would suspect this is the problem. You can easily find out by not using the Android app. There is no known solution to OOM's other than lowering settings, checking your overclock (if applicable), overheating issues, improperly installed programs and addons, and/or improper memory configurations. I do know that running an app on a second monitor while running FSX would sometimes bring my previous system to its knees (hasn't happened yet with current system). If you continue to get CTD's, you can download and run AppCrashView and post the results in a new topic. It gets very confusing posting several crashes in the same topic. For instance, the OP was about a BEX/StackHash error. 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
July 17, 201312 yr Hey Thanks Jim, yeah I'll try it this evening without running the android app to see if that's the problem...and also to check out the AppCrashView application...thanks for the feedback. BTW the CTD I'm getting is the BEX/StackHash error. Sorry if I didn't make that clear. FYI...the Android app doesn't run on a second monitor, per say, it runs on an android tablet, but communicates with FSX over a TCP/IP network protocol. So I'm sure Flight1 installed some service that listens on a port over COM and communicates to a FSX/Fligth1 dll. Of course I'm assuming here... :-) Thanks, Ray p.s. I just remembered that I was also running a Garmin Android app (EFB) that connects via Bluetooth at the same time. So, it could be a combination of the TCP/IP android app, by Flight1, and the FSUIPC that communicates over Bluetooth that gives GPS info to the Garmin app. So my guess is that I can do one or the other but not both. I'll report back my findings.
January 17, 201511 yr After deleting that Shader10 folder I no longer get the DX10 StackHash crash. Hi Jim, More than 2 years later, your pain and research solved my issue - I started receiving StackHash errors a week ago, and today, after deleting files in the Shader10 folder (not the sub-folders, just the files within those folders) I was able to complete my flight which has consistently crashed my FSX for over a week. (KPGA to KHII via PGS IGM and EED). I wasn't able to even get to my first checkpoint (PGS) this whole week, and today flew the whole flight without issues. And this was with a clean, single installation of FSX-SE. So Thank You, VERY much! Stevan Makarevich
Create an account or sign in to comment