February 20, 201412 yr Moderator Hi JIm, Nice to see you continuing to help people with CTD problems. I've flown many times this month and haven't had a single CTD during flight so it looks very much like the MyTrafficX problem has been resolved. But several times after closing FSX without any sign that there was a problem I've noticed an entry in AppCrash. It's another StackHash one and always has the same memory address. Here's the AppCrash report... Version=1EventType=APPCRASHEventTime=130372071142609325ReportType=2Consent=1UploadTime=130372071142909326ReportIdentifier=7aba60ae-98a8-11e3-aa65-94de80a6c959IntegratorReportIdentifier=7aba60ad-98a8-11e3-aa65-94de80a6c959WOW64=1Response.BucketId=3417677212Response.BucketTable=1Response.type=4Sig[0].Name=Application NameSig[0].Value=fsx.exeSig[1].Name=Application VersionSig[1].Value=10.0.61472.0Sig[2].Name=Application TimestampSig[2].Value=475e17d3Sig[3].Name=Fault Module NameSig[3].Value=StackHash_e16fSig[4].Name=Fault Module VersionSig[4].Value=0.0.0.0Sig[5].Name=Fault Module TimestampSig[5].Value=00000000Sig[6].Name=Exception CodeSig[6].Value=c0000005Sig[7].Name=Exception OffsetSig[7].Value=74e3c9f5DynamicSig[1].Name=OS VersionDynamicSig[1].Value=6.1.7601.2.1.0.768.3DynamicSig[2].Name=Locale IDDynamicSig[2].Value=2057DynamicSig[22].Name=Additional Information 1DynamicSig[22].Value=e16fDynamicSig[23].Name=Additional Information 2DynamicSig[23].Value=e16f26ed920b77e80b57d6228a772083DynamicSig[24].Name=Additional Information 3DynamicSig[24].Value=b0c5DynamicSig[25].Name=Additional Information 4DynamicSig[25].Value=b0c550a6b80dcc0aa18542106ee0a0b6UI[2]=D:\FSX\fsx.exeUI[3]=Microsoft Flight Simulator® has stopped workingUI[4]=Windows can check online for a solution to the problem.UI[5]=Check online for a solution and close the programUI[6]=Check online for a solution later and close the programUI[7]=Close the programLoadedModule[0]=D:\FSX\fsx.exeLoadedModule[1]=C:\Windows\SysWOW64\ntdll.dllLoadedModule[2]=C:\Windows\syswow64\kernel32.dllLoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dllLoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLLLoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dllLoadedModule[6]=C:\Windows\syswow64\msvcrt.dllLoadedModule[7]=C:\Windows\syswow64\GDI32.dllLoadedModule[8]=C:\Windows\syswow64\USER32.dllLoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dllLoadedModule[10]=C:\Windows\SysWOW64\sechost.dllLoadedModule[11]=C:\Windows\syswow64\RPCRT4.dllLoadedModule[12]=C:\Windows\syswow64\SspiCli.dllLoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dllLoadedModule[14]=C:\Windows\syswow64\LPK.dllLoadedModule[15]=C:\Windows\syswow64\USP10.dllLoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dllLoadedModule[17]=C:\Windows\syswow64\ole32.dllLoadedModule[18]=C:\Windows\system32\apphelp.dllLoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLLLoadedModule[20]=C:\Windows\system32\UxTheme.dllLoadedModule[21]=C:\Windows\system32\WINMM.dllLoadedModule[22]=C:\Windows\system32\samcli.dllLoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dllLoadedModule[24]=C:\Windows\system32\MSACM32.dllLoadedModule[25]=C:\Windows\system32\VERSION.dllLoadedModule[26]=C:\Windows\syswow64\SHELL32.dllLoadedModule[27]=C:\Windows\system32\sfc.dllLoadedModule[28]=C:\Windows\system32\sfc_os.DLLLoadedModule[29]=C:\Windows\system32\USERENV.dllLoadedModule[30]=C:\Windows\system32\profapi.dllLoadedModule[31]=C:\Windows\system32\dwmapi.dllLoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dllLoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dllLoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dllLoadedModule[35]=C:\Windows\syswow64\urlmon.dllLoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dllLoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dllLoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dllLoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dllLoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dllLoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dllLoadedModule[42]=C:\Windows\syswow64\normaliz.DLLLoadedModule[43]=C:\Windows\syswow64\iertutil.dllLoadedModule[44]=C:\Windows\syswow64\WININET.dllLoadedModule[45]=C:\Windows\system32\MPR.dllLoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLLLoadedModule[47]=C:\Windows\system32\WINSPOOL.DRVLoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLLLoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dllLoadedModule[50]=C:\Windows\system32\mscms.dllLoadedModule[51]=C:\Windows\system32\DDRAW.dllLoadedModule[52]=C:\Windows\system32\DCIMAN32.dllLoadedModule[53]=C:\Windows\syswow64\COMDLG32.dllLoadedModule[54]=C:\Windows\syswow64\IMM32.dllLoadedModule[55]=C:\Windows\syswow64\MSCTF.dllLoadedModule[56]=C:\Windows\syswow64\WS2_32.dllLoadedModule[57]=C:\Windows\syswow64\NSI.dllLoadedModule[58]=C:\Windows\system32\msi.dllLoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLLLoadedModule[60]=D:\FSX\language.dllLoadedModule[61]=D:\FSX\API.DLLLoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dllLoadedModule[63]=D:\FSX\ablscpt.dllLoadedModule[64]=D:\FSX\flight.dllLoadedModule[65]=D:\FSX\ai_player.dllLoadedModule[66]=D:\FSX\acontain.dllLoadedModule[67]=D:\FSX\controls.dllLoadedModule[68]=C:\Windows\system32\DINPUT8.dllLoadedModule[69]=D:\FSX\fsui.dllLoadedModule[70]=D:\FSX\atc.dllLoadedModule[71]=D:\FSX\facilities.dllLoadedModule[72]=D:\FSX\demo.dllLoadedModule[73]=D:\FSX\main.dllLoadedModule[74]=D:\FSX\fe.dllLoadedModule[75]=D:\FSX\util.dllLoadedModule[76]=D:\FSX\simprop.dllLoadedModule[77]=D:\FSX\g2d.dllLoadedModule[78]=C:\Windows\system32\d3dx9_34.dllLoadedModule[79]=C:\Windows\system32\d3dx10_34.dllLoadedModule[80]=C:\Windows\system32\d3d9.dllLoadedModule[81]=C:\Windows\system32\d3d8thk.dllLoadedModule[82]=D:\FSX\g3d.dllLoadedModule[83]=D:\FSX\panels.dllLoadedModule[84]=D:\FSX\multiplayer.dllLoadedModule[85]=D:\FSX\ui.dllLoadedModule[86]=D:\FSX\sound.dllLoadedModule[87]=D:\FSX\sim1.dllLoadedModule[88]=D:\FSX\simscheduler.dllLoadedModule[89]=D:\FSX\visualfx.dllLoadedModule[90]=D:\FSX\window.dllLoadedModule[91]=D:\FSX\terrain.dllLoadedModule[92]=D:\FSX\weather.dllLoadedModule[93]=C:\Windows\system32\DSOUND.dllLoadedModule[94]=C:\Windows\system32\POWRPROF.dllLoadedModule[95]=D:\FSX\symmap.dllLoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dllLoadedModule[97]=C:\Windows\system32\MSIMG32.dllLoadedModule[98]=D:\FSX\xuipc.dllLoadedModule[99]=D:\FSX\livingwater.dllLoadedModule[100]=D:\FSX\fs-traffic.dllLoadedModule[101]=D:\FSX\gps.dllLoadedModule[102]=C:\Windows\system32\MSWSOCK.dllLoadedModule[103]=C:\Windows\system32\SHFOLDER.dllLoadedModule[104]=C:\Windows\system32\RICHED20.DLLLoadedModule[105]=C:\Windows\system32\CRYPTSP.dllLoadedModule[106]=C:\Windows\system32\rsaenh.dllLoadedModule[107]=C:\Windows\syswow64\WINTRUST.dllLoadedModule[108]=C:\Windows\syswow64\CRYPT32.dllLoadedModule[109]=C:\Windows\syswow64\MSASN1.dllLoadedModule[110]=C:\Windows\syswow64\CLBCatQ.DLLLoadedModule[111]=C:\Windows\system32\wbem\wbemprox.dllLoadedModule[112]=C:\Windows\system32\wbemcomn.dllLoadedModule[113]=C:\Windows\system32\RpcRtRemote.dllLoadedModule[114]=C:\Windows\system32\wbem\wbemsvc.dllLoadedModule[115]=C:\Windows\system32\wbem\fastprox.dllLoadedModule[116]=C:\Windows\system32\NTDSAPI.dllLoadedModule[117]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLLLoadedModule[118]=C:\Windows\system32\dxgi.dllLoadedModule[119]=C:\Windows\system32\d3d11.dllLoadedModule[120]=C:\Windows\system32\nvd3dum.dllLoadedModule[121]=C:\Windows\syswow64\PSAPI.DLLLoadedModule[122]=C:\Windows\system32\D3DCompiler_34.dllLoadedModule[123]=C:\Windows\system32\WindowsCodecs.dllLoadedModule[124]=C:\Windows\system32\d3d10_1.dllLoadedModule[125]=C:\Windows\system32\d3d10_1core.dllLoadedModule[126]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dllLoadedModule[127]=C:\Windows\SysWOW64\dxdiagn.dllLoadedModule[128]=C:\Windows\SysWOW64\d3d10.dllLoadedModule[129]=C:\Windows\SysWOW64\d3d10core.dllLoadedModule[130]=C:\Windows\system32\winbrand.dllLoadedModule[131]=C:\Windows\system32\nvapi.dllLoadedModule[132]=C:\Windows\system32\WTSAPI32.DLLLoadedModule[133]=C:\Windows\system32\WINSTA.dllLoadedModule[134]=C:\Windows\SysWOW64\gameux.dllLoadedModule[135]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dllLoadedModule[136]=C:\Windows\SysWOW64\XmlLite.dllLoadedModule[137]=C:\Windows\SysWOW64\wer.dllLoadedModule[138]=C:\Windows\System32\Wpc.dllLoadedModule[139]=C:\Windows\System32\wevtapi.dllLoadedModule[140]=C:\Windows\System32\msxml6.dllLoadedModule[141]=C:\Windows\system32\SAMLIB.dllLoadedModule[142]=C:\Windows\system32\netutils.dllLoadedModule[143]=D:\FSX\uiautomationcore.dllLoadedModule[144]=C:\Windows\system32\OLEACC.dllLoadedModule[145]=C:\Windows\System32\MMDevApi.dllLoadedModule[146]=C:\Windows\System32\PROPSYS.dllLoadedModule[147]=C:\Windows\system32\AUDIOSES.DLLLoadedModule[148]=C:\Windows\system32\HID.DLLLoadedModule[149]=C:\Windows\system32\ntmarta.dllLoadedModule[150]=C:\Windows\syswow64\WLDAP32.dllLoadedModule[151]=C:\Windows\system32\wdmaud.drvLoadedModule[152]=C:\Windows\system32\ksuser.dllLoadedModule[153]=C:\Windows\system32\AVRT.dllLoadedModule[154]=C:\Windows\system32\msacm32.drvLoadedModule[155]=C:\Windows\system32\midimap.dllLoadedModule[156]=C:\Windows\system32\dinput.DLLLoadedModule[157]=C:\Windows\system32\BfLLR.dllLoadedModule[158]=C:\Windows\system32\IPHLPAPI.DLLLoadedModule[159]=C:\Windows\system32\WINNSI.DLLLoadedModule[160]=C:\Windows\system32\dhcpcsvc.DLLLoadedModule[161]=C:\Windows\system32\dhcpcsvc6.DLLLoadedModule[162]=C:\Windows\System32\wshtcpip.dllLoadedModule[163]=C:\Windows\System32\wship6.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]=D:\FSX\fs_earth\simconnect.dllLoadedModule[168]=C:\Program Files (x86)\AFX\AFXModuleFSX.dllLoadedModule[169]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dllLoadedModule[170]=C:\Windows\system32\mscoree.dllLoadedModule[171]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dllLoadedModule[172]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dllLoadedModule[173]=C:\Windows\assembly\NativeImages_v2.0.50727_32\mscorlib\ede2c6c842840e009f01bcc74fa4c457\mscorlib.ni.dllLoadedModule[174]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorsec.dllLoadedModule[175]=C:\Windows\syswow64\imagehlp.dllLoadedModule[176]=C:\Windows\system32\ncrypt.dllLoadedModule[177]=C:\Windows\system32\bcrypt.dllLoadedModule[178]=C:\Windows\SysWOW64\bcryptprimitives.dllLoadedModule[179]=C:\Windows\system32\GPAPI.dllLoadedModule[180]=C:\Windows\system32\cryptnet.dllLoadedModule[181]=C:\Windows\system32\SensApi.dllLoadedModule[182]=C:\Windows\system32\WINHTTP.dllLoadedModule[183]=C:\Windows\system32\webio.dllLoadedModule[184]=C:\Windows\system32\credssp.dllLoadedModule[185]=C:\Windows\system32\DNSAPI.dllLoadedModule[186]=C:\Windows\system32\rasadhlp.dllLoadedModule[187]=C:\Windows\System32\fwpuclnt.dllLoadedModule[188]=D:\FSX\as_srv\as_connect.dllLoadedModule[189]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorjit.dllLoadedModule[190]=C:\Windows\assembly\NativeImages_v2.0.50727_32\System\b3a78269847005365001c33870cd121f\System.ni.dllLoadedModule[191]=C:\Windows\system32\Secur32.dllLoadedModule[192]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dllLoadedModule[193]=C:\Windows\system32\msadp32.acmLoadedModule[194]=C:\Windows\SysWOW64\ieframe.dllLoadedModule[195]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dllLoadedModule[196]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dllLoadedModule[197]=C:\Windows\SysWOW64\mshtml.dllLoadedModule[198]=C:\Windows\system32\msimtf.dllLoadedModule[199]=C:\Windows\system32\msls31.dllLoadedModule[200]=C:\Windows\system32\d2d1.dllLoadedModule[201]=C:\Windows\system32\DWrite.dllLoadedModule[202]=C:\Windows\system32\MLANG.dllLoadedModule[203]=C:\Windows\SysWOW64\uiautomationcore.dllLoadedModule[204]=D:\FSX\Aerosoft\AES\ViMaCli.dllLoadedModule[205]=C:\Windows\Microsoft.NET\Framework\v2.0.50727\diasymreader.dllState[0].Key=Transport.DoneStage1State[0].Value=1FriendlyEventName=Stopped workingConsentKey=APPCRASHAppName=Microsoft Flight Simulator®AppPath=D:\FSX\fsx.exe It ends by saying that FSX has stopped working but I would dispute that. When I closed the sim using the red X (top right) it never displayed any message saying FSX has encountered a problem. It's almost like it's a false positive. I wonder if you have any thoughts on it and whether you've had the same error yourself. Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
February 20, 201412 yr Hi Ray, Sorry to hear you are having an issue again with the StackHash error. There is only one known solution. Google says it is connected to the Windows security program Data Execution Prevention (DEP) but If I disable DEP for FSX, the crash continues. The last four digits next to StackHash is the memory address where the crash occurred. I know of no way to find out what was at that memory address when the crash occurred. As I have stated previously, it is something in our FSX that is stuck in memory. That's why you will always see that memory address. In my case a couple of years ago, it was my two monitors I use to run FSX. Members here found that if you start up FSX in full screen and then shutdown FSX in full screen, you will get a StackHash address error 100% of the time. But if you start up fsx in Windowed Mode and close FSX down in Windowed Mode, the crash does not occur. That's just one known solution but some have accidently fixed their problem by renaming the Fsx.cfg, restarting FSX and letting the config rebuild. Maybe it was a bad tweak that was messing with the memory for the application. Some others who have rebuilt their Fsx.cfg had no joy. The only way to find out the issue is like what we did when we found MyTrafficX had an issue and was causing the errors. You just have to disable all of your scenery, see if the error occurs again and, if not, then it must be one of your scenery textures that is not rendering properly. If the error continues after all the addon scenery has been disabled, then it might be one of your modules in the dll.xml so you have to disable them and see if that fixes the problem. If not, then unfortunately you will have to look at a complete reinstall of Windows AND FSX. If you do find a solution, definitely let us know but there is no know magic bullet. Thanks for your kind comments my friend! Best regards, 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
February 21, 201412 yr Author Moderator Hi Jim, After I posted that message I tried launching and closing FSX several times all at the same airport - Amsterdam Schiphol. The first time I closed it I got the stackhash error in AppCrash but on 4 subsequent exits it was clean. Baffling! Then I lowered the Scenery Complexity setting from Extremely Dense to Very Dense and tried it again. No further crashes either at EHAM or JFK with several exits. I did see a message from Pete Dowson in his forum that it could be related to high settings. Having lowered one setting I'll see if it changes anything. I haven't tried creating a new FSX.cfg or disabling addon scenery since I don't get any problems whilst flying. I always start and end FSX in windowed mode. If it continues I'll lower another scenery setting and hopefully over time it will stop. As I said earlier, it's not particularly bothersome because it doesn't happen during a flight. In that respect FSX is now very stable. I'll keep you updated on any developments. Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
February 21, 201412 yr I did see a message from Pete Dowson in his forum that it could be related to high settings. Having lowered one setting I'll see if it changes anything. Hi Ray, That was indicated in the AVSIM CTD Guide too as one of the possible solutions. Is the Amsterdam Schiphol the default of the commercial version? It should be happening with the default but there could be a texture problem with a commercial version (much like what you found in MyTrafficX and reported to the developer. Hopefully you have it fixed. See it is warming up in Cheshire. Believe it was 5C yesterday. Best regards, 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
February 21, 201412 yr Author Moderator Hi Jim, It's the commercial Schiphol but as it's happened at other airports too I would be very surprised if they all had memory leaks. It still doesn't explain why it wouldn't happen during approach or taxiing to the gate. That's why it's such a strange error. Temps here have been mild for the whole winter. No snow and hardly any frost. Quite unlike you over there. With only a week or so left of winter I think we've escaped it. Hope it warms up for you soon! Ray (Cheshire, England). System: P3D v5.3HF2, Intel i9-13900K, MSI 4090 GAMING X TRIO 24G, Crucial T700 4Tb M.2 SSD, Asus ROG Maximus Z790 Hero, 32Gb Corsair Vengeance DDR5 6000Mhz RAM, Win 11 Pro 64-bit, BenQ PD3200U 32” UHD monitor, Fulcrum One yoke, Fulcrum Throttle Quadrant. Cheadle Hulme Weather website.
.thumb.jpeg.70674dda83c26f38738b63be9b37943e.jpeg)
Create an account or sign in to comment