AZWildk4t

Leo Bodnar cards are the best for switches and encoders. Also use them for Hall Sensors needed to built 737 TQ. I also use the I/O boards from Flightdeck Solutions because it drives both inputs and outputs

You're right ilu. But once i uninstalled FSX and re-installed it, FSX would never completely launch. it got hung on the splash screen.

Thanks Dan. I tried a complete uninstall of PMDG 737NGX and then a complete uninstall of FSX. That didn't solve the issue. So I completely reformatted my drive and have started the rebuild process. I needed to do it anyways since I had a bunch of unnecessary programs on it anyways. Thanks in advance for your help. Steve

FSX has been installed at c:\fsx. PMDG 737NGX has been running fine up until Friday when I completed my flight and walked away from the computer for a bit. Then it froze up. Now I get a crash only with the PMDG 737NGX. My Aerosoft Airbus X and PMDG 777 work just fine. I think I'll try a complete uninstall and reinstall of the PMDG 737NGX before I end up uninstalling and reinstalling FSX.

Thanks ilu. I am running 64-bit Windows 7 with 8GBs. I'll try what you suggested on the reinstall of FSX. It's probably my last hope before I do a complete re-install of Windows 7. It's possible that the Registry got corrupt when the FSX froze.

Thanks everyone for the suggestions. I tried the 'repair' option Dan suggested but that didn't fix the issue. I've had similar issues with the throttle levers not being in the correct position but they appear to be correct. I'll try taiyang's suggestion and see if that resolves it.

Thanks Dan. I think I might need to run the repair as you said. I loaded the PMDG 777 and it loads fine. The issue is with any PMDG 737NGX. As soon as I load the aircraft on Free Flight menu, FSX crashes. I've tried Free Flight with a Trike and then switch to PMDG 737 after it parks at a gate. The problem looks to be with the GAUGE. This is what I found in the Windows Event Viewer: Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3 Faulting module name: PMDG_737NGX.DLL, version: 1.0.0.0, time stamp: 0x4f5162a3 Exception code: 0xc0000005 Fault offset: 0x000ff55f Faulting process id: 0x1480 Faulting application start time: 0x01d03d895fa61cfb Faulting application path: C:\fsx\fsx.exe Faulting module path: C:\fsx\GAUGES\PMDG_737NGX.DLL Report Id: 87a1ff29-a997-11e4-854f-001e4cccc031 Then this: Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: fsx.exe P2: 10.0.61472.0 P3: 475e17d3 P4: PMDG_737NGX.DLL P5: 1.0.0.0 P6: 4f5162a3 P7: c0000005 P8: 000ff55f P9: P10: Attached files: C:\Users\Steve\AppData\Roaming\Microsoft\FSX\fsx.CFG.txt C:\Users\Steve\AppData\Roaming\Microsoft\FSX\dxdiag.txt C:\Users\Steve\AppData\Roaming\Microsoft\FSX\scenery.cfg C:\Users\Steve\AppData\Roaming\Microsoft\FSX\fdr.dat C:\Users\Steve\AppData\Roaming\Microsoft\FSX\dll.xml C:\Users\Steve\AppData\Local\Temp\WERA549.tmp.WERInternalMetadata.xml These files may be available here: C:\Users\Steve\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_fsx.exe_9d3d7cf235dc4d3ca38d1177d4ced895805b1e51_1571bde7 Analysis symbol: Rechecking for solution: 0 Report Id: 87a1ff29-a997-11e4-854f-001e4cccc031 Report Status: 1 Thanks, Steve Parrilla

Hi guys, I've been flying the PMDG 737NGX for quite some time now without any problems. Yesterday, I flew the NGX from LAX to PHX without any problems. I walked away from the computer for a bit. When I came back, I noticed FSX had frozen when loading the scenery (about 43%). Now, whenever I select the PMDG 737NGX (any livery), FSX crashes. I have selected the stock Microsoft B737 and it loads correctly. But as soon as I switch to the PMDG, it crashes. Any suggestions?

Can someone explain how you dial in the DH/MDA? I know how to switch between DH and MDA via the knob. However, I can't figure out how to change DH to say '400'. What dial is used to adjust this value?

How do I get ahold of these textures? I went to the Facebook page but don't see links for download.

Thanks guys for the responses... Kuragiman - The couati.exe shuts down and the menu and any payware airports disappear leaving only the jetways. Red259 - the voice recognition is the same as the PMDG. The problem is there are commands for '... at the line' and ones for '... in the line'. The voice recognition doesn't pick them up very well. I've also found that most of the checklist items need to be done by the PIC so why pay for a product that uses a lazy FO. Brendan - any help to understand the 'line' stuff would be helpful. The aircraft is really awesome but FS2Crew doesn't seem to play well with it - like the PMDG 737.

PSour23 - I agree with you 100%. I expected more from FS2Crew with the Q400, similar to the PMDG 737NGX. I end up turning on most of the switches myself and can't get the lazy FO to start the engines. Nice FS2Crew got 40 USD from me for a lousy product.

I've been using FS2CREW for the PMDG B737 NGX for some time now and love it. The only issue is the conflict it has with GSX (FSDreamTeam). Naturally I was excited that FS2CREW had a product for my newly purchased Majestic Dash8-Q400. However, compared to the PMDG 737 version, this is a very disappointing product. The voice commands for below the line or at the line are difficult. Most of the commands are not executed and I have to manually do them myself, which is rather difficult while trying to fly the plane, respond to ATC on Vatsim, etc. Without some serious revisions to voice control, I would recommend you hold off on this product and do it yourself.

Thanks Pete for the response. You are probably correct that I might have a key mapping the same command as GSX. But I also noticed that it causes GSX to crash as the process no longer exists on the FSX menu or in Task Manager. I did find a CRASH REPORT. I reported this to the FSDreamteam developers and they indicated it's a FS2CREW issue. Version=1 EventType=APPCRASH EventTime=130579512029752140 ReportType=2 Consent=1 UploadTime=130580272789739959 ReportIdentifier=1304e577-5553-11e4-85a1-001e4cccc031 IntegratorReportIdentifier=1304e576-5553-11e4-85a1-001e4cccc031 WOW64=1 Response.BucketId=394911589 Response.BucketTable=17 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=couatl.exe Sig[1].Name=Application Version Sig[1].Value=2.0.0.2364 Sig[2].Name=Application Timestamp Sig[2].Value=53cfcbe7 Sig[3].Name=Fault Module Name Sig[3].Value=couatl.exe Sig[4].Name=Fault Module Version Sig[4].Value=2.0.0.2364 Sig[5].Name=Fault Module Timestamp Sig[5].Value=53cfcbe7 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=00002956 DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.768.3 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 DynamicSig[22].Name=Additional Information 1 DynamicSig[22].Value=0a9e DynamicSig[23].Name=Additional Information 2 DynamicSig[23].Value=0a9e372d3b4ad19135b953a78882e789 DynamicSig[24].Name=Additional Information 3 DynamicSig[24].Value=0a9e DynamicSig[25].Name=Additional Information 4 DynamicSig[25].Value=0a9e372d3b4ad19135b953a78882e789 UI[2]=C:\fsx\fsdreamteam\couatl\couatl.exe UI[3]=Couatl"! Scripting Engine for FSX//ESP 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\fsdreamteam\couatl\couatl.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\syswow64\user32.dll LoadedModule[5]=C:\Windows\syswow64\GDI32.dll LoadedModule[6]=C:\Windows\syswow64\LPK.dll LoadedModule[7]=C:\Windows\syswow64\USP10.dll LoadedModule[8]=C:\Windows\syswow64\msvcrt.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\oleaut32.dll LoadedModule[15]=C:\Windows\syswow64\ole32.dll LoadedModule[16]=C:\Windows\syswow64\shell32.dll LoadedModule[17]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[18]=C:\Windows\system32\version.dll LoadedModule[19]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[20]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll LoadedModule[21]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[22]=C:\Windows\syswow64\WS2_32.dll LoadedModule[23]=C:\Windows\syswow64\NSI.dll LoadedModule[24]=C:\Windows\system32\SHFOLDER.dll LoadedModule[25]=C:\Windows\syswow64\WININET.dll LoadedModule[26]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll LoadedModule[27]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll LoadedModule[28]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll LoadedModule[29]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll LoadedModule[30]=C:\Windows\syswow64\normaliz.DLL LoadedModule[31]=C:\Windows\syswow64\iertutil.dll LoadedModule[32]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll LoadedModule[33]=C:\Windows\syswow64\USERENV.dll LoadedModule[34]=C:\Windows\syswow64\profapi.dll LoadedModule[35]=C:\fsx\fsdreamteam\couatl\python25.dll LoadedModule[36]=C:\fsx\fsdreamteam\couatl\OpenAL32.dll LoadedModule[37]=C:\Windows\system32\WINMM.dll LoadedModule[38]=C:\fsx\fsdreamteam\couatl\alut.dll LoadedModule[39]=C:\Windows\system32\IMM32.DLL LoadedModule[40]=C:\Windows\syswow64\MSCTF.dll LoadedModule[41]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\comctl32.dll LoadedModule[42]=C:\Windows\system32\uxtheme.dll LoadedModule[43]=C:\fsx\fsdreamteam\couatl\wx\_core_.pyd LoadedModule[44]=C:\fsx\fsdreamteam\couatl\wx\wxmsw28uh_vc.dll LoadedModule[45]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_72d576ad8665e853\gdiplus.dll LoadedModule[46]=C:\Windows\syswow64\comdlg32.dll LoadedModule[47]=C:\Windows\system32\WSOCK32.dll LoadedModule[48]=C:\fsx\fsdreamteam\couatl\wx\_gdi_.pyd LoadedModule[49]=C:\fsx\fsdreamteam\couatl\wx\_windows_.pyd LoadedModule[50]=C:\fsx\fsdreamteam\couatl\wx\_controls_.pyd LoadedModule[51]=C:\fsx\fsdreamteam\couatl\wx\_misc_.pyd LoadedModule[52]=C:\Windows\system32\dwmapi.dll LoadedModule[53]=C:\fsx\fsdreamteam\couatl\wx\_xrc.pyd LoadedModule[54]=C:\Windows\system32\CRYPTSP.dll LoadedModule[55]=C:\Windows\system32\rsaenh.dll LoadedModule[56]=C:\Windows\system32\MMDevAPI.DLL LoadedModule[57]=C:\Windows\system32\PROPSYS.dll LoadedModule[58]=C:\Windows\system32\wdmaud.drv LoadedModule[59]=C:\Windows\system32\ksuser.dll LoadedModule[60]=C:\Windows\system32\AVRT.dll LoadedModule[61]=C:\Windows\syswow64\SETUPAPI.dll LoadedModule[62]=C:\Windows\syswow64\CFGMGR32.dll LoadedModule[63]=C:\Windows\syswow64\DEVOBJ.dll LoadedModule[64]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[65]=C:\Windows\system32\msacm32.drv LoadedModule[66]=C:\Windows\system32\MSACM32.dll LoadedModule[67]=C:\Windows\system32\midimap.dll LoadedModule[68]=C:\Windows\system32\dsound.dll LoadedModule[69]=C:\Windows\system32\POWRPROF.dll LoadedModule[70]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[71]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[72]=C:\Windows\system32\WINNSI.DLL LoadedModule[73]=C:\Windows\system32\apphelp.dll LoadedModule[74]=C:\Windows\system32\dhcpcsvc.DLL LoadedModule[75]=C:\fsx\fsdreamteam\couatl\wrap_oal.dll LoadedModule[76]=C:\fsx\fsdreamteam\couatl\wx\_html.pyd State[0].Key=Transport.DoneStage1 State[0].Value=1 State[1].Key=DataRequest State[1].Value=Bucket=394911589/nBucketTable=17/nResponse=1/n FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Couatl"! Scripting Engine for FSX//ESP AppPath=C:\fsx\fsdreamteam\couatl\couatl.exe

I have run into a conflict with FS2CREW for PMDG 737 NGX (using Voice Control) and GSX. I use FS2CREW to run through the preflight checklist. Then at the time of pushback, I select the GSX key mapping (CTRL+ALT+F12). The GSX menu appears and I select the Pushback menu item. Then suddenly GSX shuts down. I have noticed that when I select the CTRL key, the FS2CREW display shows "M+" for Mute. I am using Voice Control so I am unsure why it is using the keyboard or button mappings.