GrizRod1

This joystick was working perfectly before I reinstalled Windows 7. Now FSX and Win7 will not recognise it. Device manager list three things under Other Devices, Universal Serial Bus Controller (No Driver), Eternet Controller (No Driver), and Unknown Device(No Driver) I have reinstalled all the USB Drivers from my Gigabyte MB cd, tried unplugging the joystick from the usb port, restarting, shutting down the computer and plugging back in to the usb connection. Tried every Microsoft fix I could find plus their Fix It program. It says it cannot find a driver as does Windows 7. I've been thru ten pages of searches about here on the forum, so far no luck. This problem has to be related to the Win7 reinstall is the only thing I can come up with, and you cannot clean an ssd with diskpart. Something I would have done if I could have. Maybe the only way to fix thid problem is to install Windows 7 on a new disk.

Popped the GTX 770 in , same deal CTD right before T/D Top of Descent. I guess I've got to get Aersofts "Maldive" folder out of there along with the Fly Tampa Duibai Rebooted, tried disabling Maldives and the 777 is in the grass, no runway. I have the UIAutomation. dll, the PMDG version, I hear there's two versions. Oh well, may get it after awhile. Sure getting an education on the inner workings of a computer. :Shocked:

Thanks Kyle, also Michael, and olli4770. I think I compounded my problems by adding scenery after a successful landing at Dubai with the addition of Fly Tampa-Dubai Rebooted and Aerosofts Maldives. Been turning down my GTX550TI settings, loading only the necessary scenery from FSX, but I've flown three flights and get a CTD right before T/D or a little earlier everytime. Hopefully my new GTX770 4GB OC arriving today will solve the problems , so far nothing is working that I've tried on the Crash To Desktop Guide. I will let you know .

Scandinavian, I'm not going to nitpick your excellent video of the PMDG Tutorial 1 flight from Male to Dubai. I was just trying to make the point that most anything can have a error or two, if one wants to look hard enough, and is that comment going to be helpful. Keep up the good work, I really liked your video.

pcubine, thanks for the link, it says something about signing your full name to a post. . Then the info on setting up a signature looks to me like guidelines for an avatar saying a signature is not necessary, but encouraged, maybe you or someone can enlighten me. http://forum.avsim.net/page/AVSIM%20Pages/sig.html Badfinger, that woman's cubicle comment is funny. :lol: Olli4740, I noticed my AUTO CRUISE kicked off when my AUTO TIME COMPRESSION stopped by itself right before T/D. I wonder if that is normal.

I was just quoting the tutorial, and the terms they are using, anybody read the Boeing 777 manuals, this conversation can get even more technical, if anyone want's to read a few thousand pages. :huh: Technically Scandinavian is correct, I just thought he was splitting hairs.IMO I could sharp shoot his video over a minor thing, but I won't do that, it would just ###### him off, and what good would that do. He been a big help for a lot of people, but I've seen to many comments on here, not necessarily from this topic, that are not helpful at all. I had no idea FSX needed so many fixes to run PMDG 777, pretty much have all of them down now. When you are working night to try and get PMDG working you are bound to miss some miniscule details. Something that's forgotten sometimes. IMO I wanted to mention it's like to land a helicopter on an ILS approach, no auto pilot, no trim, one half of a localizer, any of you know what I'm talking about? You are flying it every second, because if you let go of the controls the aircraft will be upside down in about five to ten seconds scanning the instruments around and around at a much faster rate then fixed wing pilots, because you have fly it every second, monitoring altitude, vertical speed, airspeed, and heading, right or left of course, because that's the only needle you've got. The big advantage you had with Huey is that your speed is a lot slower then a 777, but they were primitive compared to the Black Hawk's that the US Army is flying today. But back in the day they were the best helicopter of it's time. But I will admit this 777 sim is a blast to land ILS on auto-pilot. I think PDMG is right when they say this sim is the next best thing to a mult-million dollar simulator. Sorry if I stepped on any toes. :unsure:

Would you please copy that info from the signature requirements, I've read it three times and all I can find is that it is encouraged, maybe it's posted somewhere else. I see you are in Tampa, not a bad town. I'm be working on it. Thanks, Brian

Snarkey is as snarkey does, on the CDU you set the AUTO TIME COMPRESSION WHICH SETS THE AUTO CRUISE since you want to get technical. I BEG YOUR HUMBLE PARDON. I forgot one more thing if you read page 81 of the PMDG 777 Tutorial 1, it says at the top of the page " Turn off the automatic time compression" not the Auto Cruise. Page 79 says " Continue the cruise either in real time or using Auto Cruise. So maybe someone should notify PMDG since they do not call the phase of the flight at the T/D properly, as being in Auto Cruise, instead of being in automatic time compression. What do you think?

It's nice to have a few nitpickers on here to try and correct everyone, I'm impressed. :Big Grin: Fortunately most members are quite helpful, if people knew what a pain in the &@($* FSX is PMDG probably would not sell any downloads. But with all the help on here and PMDG and a moderate amount of computer knowledge, PMDG 777 can be set up to run well eventually.

Hello Javier, Looks like you have just gotten started with PMDG 777. The are quite a few problems with FSX and Directx9c that need to be fixed. See what I finally had to do to get my PMDG running here, I know it's a bit long, but I was trying to make it understandable. Runtime installer is a big fix IMO, along with turning your graphics settings down, along with correctly installing FSX, unless you are running something like a GTX770. Did you also uninstall all the files and folders remnants left from FSX, and did you install FSX correctly. Are you running all of your flight sim stuff on a second HD or SSD? You did not say anything about your computer or video card. Sorry forgot the link. http://forum.avsim.net/topic/438758-pmdg-777-will-not-descend-to-land-on-auto-cruise/

Thanks for all the replies. The PMDG 777 sim is running perfectly. I finally did what I was putting off doing, uninstalling and reinstalling FSX Acceleration and PMDG 777 again. Here's what I thought might be the problem. I had remnants of FSX and PMDG 777 left on my C:/ drive, all files and folders related to them were deleted. I uninstalled FSX and PMDG 777 from my E:/ drive, installed FSX as per instruction on one of the forum guides. I do not believe it was installed correctly, reinstalled PMDG 777 to my E:/ drive FSX folder. I then went back into my C:/ drive and renamed my fsx.CONFIG file,so FSX would load a new one, made the changes as per guide, reloaded the UlAutomation file, ran the Runtime installer for DirectX again, I'm using 9c version from the FSX program. I think a lot of problems with PMDG 777 can be blamed on DirectX9c, it needs fixing,IMO. I then detuned the graphics settings on FSX, which seemed to cure my CTD problem, part of which came from not having used Runtime installer brfore. The setting are close to the PMDG Intro guidelines , and I also turned all my traffic sliders to 0. Maybe with my new GTX 770 I can run max settings for most all of the graphics, but this is working great with my Nvidia GTX550TI. I've got plenty of CPU, the i5 3570k which should run at 3.8ghz when the turbo mode kicks in, and 8gb of RAM. I have not used my overclock of 4.5ghz yet, as I've been two weeks fooling with everything to try PMDG 777 running and get to land my 777 in Dubai. What a relief, I was wondering if I'd ever get here.

Phil, thanks for your imput. I reset the altitude, but did not check the FMC which would be a good indication at least the FMC was calling to adjust the altitude, good think to check, I also bring the throttles on my sim controls at the same time. The first leg of the decent, the VNAV PTH is alwaysan idle path, there is no requirement to set the altitude below 38,000 ft. in the FMC after T/D or before, all the altitude and speed reqirements for the descent and approach were programed in the FMC, before take off from Male. I think it's a PMDG 777 problem, reason I posted the question was hoping someone had seen this problem. Still waiting on PMDG for an answer. I'm almost sure they will say to reinstall the program.

Thanks for all the replys, I just watched a you tube video by a forum member doing the whole flight, I think I may have caught the problem. When I adjust the MCP altitude to 38000 ft, for the flight, I turn the inner knob to the right to get 1,000 ft with every click of the outer knob. I see that he brings the inner knob back to auto after resetting the MCP altitude before the TD. Nothing written in the tutorial on that. Hope that is it, Logitech speakers went out, not much over a year old, got to buy some knew ones before I do any more 777 flying.

Well as you can see I do not know much about FSUIPC, the download page has a Pro download and a regular download. No clue given as to if the regular download costs, my mistake maybe. The bleeder plan only bleeds you at $5 a month rate,the regular price was $55. :lol: IMO, the website is not that clear. Thanks for the link to Pete Dawson's Sim Flight Forum.

No all that would have showed up when the FMC was programed back at Male, I believe, and the MCP was lowered manually before top of decent marker. I believing I have a problem with the sim. It flies great up until descent time.

Thanks again Jim, I am getting a top of desent icon, and both Vnav and Lnav are on and showing, the vertical path deviation indicator popup as it's supposed to. Probably a PMDG problem, waiting to hear from them. Thanks again, Brian

Thanks for the reply Jim, I have the downloaded most all the tweaks and fixes. I did turn back some of the graphics settings and make the tutorial flight to my TD before GIRMI. No crashes after two flights, only problem the aircraft will not throttle back to idle for the first part of the descent leg to GIRMI, just keeps flying along at 38,000 feet following the landing legs. I've posted it on the PMDG Forum and have a ticket in to PMDG. Thanks, Brian

I set my MCP to 2,000ft, turn off the auto compression, running at 4x, I get a vertical path deviation indicator on the right side of my ND, but the throttle never go to idle for the decent for the decent to GIRMI with it's 230/13000B restriction. The aircraft just keeps cruising at 38,000 ft, following the decent and landing legs at that altitude. Waiting to hear from PMDG, but am hoping some one on this forum has run into this problem. Unable to find anything by searching. Thanks

I did register on the bleeder plan, $5 a month, I don't know what's going on here, I definitely have fsx.CFG file in my C: Users\Microsoft\FSX folder, but I'm running the flight simulator from my second drive, my E:\ drive. I've installed FSUIPC and it says it is installed and in the FSX folder. But it is not listed in the C:\ FSX folder, or the E:\ FSX folder. So I guess I have it, but can't access it. The folder has Users Guide doc., List of FSX Controls, and two other docs, History, and Advanced Users. Thanks Installer for FSUIPC4.DLL version 4.09 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" SetupPath="E:\FX\" Checking version of FSX.EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: ... Okay, Probe Manifest matches an installed SimConnect module Checking if there's already a version of FSUIPC4 installed in: E:\FX\Modules\FSUIPC4.DLL ... Version 4.090 found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "E:\FX\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Brian\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\Brian\AppData\Roaming" Found FSX.CFG in "C:\Users\Brian\AppData\Roaming\Microsoft\FSX\FSX.CFG"! Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Brian\Application Data\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Contacts\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Cookies\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Desktop\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Documents\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Downloads\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Dropbox\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Favorites\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Links\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Local Settings\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Music\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\My Documents\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\NetHood\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Pictures\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\PrintHood\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Recent\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Saved Games\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Searches\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\SendTo\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Start Menu\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Templates\Roaming" ... No FSX.CFG there Looking in "C:\Users\Brian\Videos\Roaming" ... No FSX.CFG there Now installing additional files into the Modules folder: Installed "FSUIPC4 User Guide.doc" okay Installed "FSUIPC4 for Advanced Users.doc" okay Installed "FSUIPC4 History.doc" okay Installed "List of FSX controls.pdf" okay All installer tasks completed okay!

Forgot my computer specs, and I have no add-ons except TrackIR5 and it is on my main drive, not the one with FSX. I have not used the IR5 since all these crashes. Cpu i5-3570k, running at stock, will overclock to 4.5ghz, I'm assuming the turbo mode kicks in with FSX to give me 3.8ghz, 8gb of ram, 240gb SSD, Windows 7, DirectX9c, ITB HD with FSX and a few temp files, from the SSD, no OS or AV on this drive. Nvidia GTX 550ti, probably the weak link. I already scaled back the great looking graphics, with the max settings. Does not help. A new GTX770 ordered, not sure that will help the crash situation. Been working thru CTD guide, so far the only thing that did help a lot was renaming the fsx.CFG file, and letting FSX install a new one. Tried a couple of other things, but need a little Thanks, Brian

I did rename my fsx.config file to let FSX build a new one seemed to help a lot, tried to finish a flight with PMDG 777, was in a hurry and used the speedup feature 16x, was swithing back and forth from 8x. I will try turning down the scenery, as it was maxed out. No warnings before the CTD, screen just goes black, then I have to force the computer to shut down after it crashes. Thanks Version=1 EventType=APPCRASH EventTime=130403358943309576 ReportType=2 Consent=1 UploadTime=130403358944209628 ReportIdentifier=3cfa1a35-b51d-11e3-99e0-0008546df92c IntegratorReportIdentifier=3cfa1a34-b51d-11e3-99e0-0008546df92c WOW64=1 Response.BucketId=3841790844 Response.BucketTable=1 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=fsx.exe Sig[1].Name=Application Version Sig[1].Value=10.0.61637.0 Sig[2].Name=Application Timestamp Sig[2].Value=46fadb14 Sig[3].Name=Fault Module Name Sig[3].Value=PMDG_777X.DLL Sig[4].Name=Fault Module Version Sig[4].Value=1.0.0.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=52256029 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=000b418d DynamicSig[1].Name=OS Version DynamicSig[1].Value=6.1.7601.2.1.0.768.3 DynamicSig[2].Name=Locale ID DynamicSig[2].Value=1033 UI[2]=E:\FX\fsx.exe UI[3]=A fatal error occurred. UI[4]=Windows can check online for a solution to the problem and try to restart the program. UI[5]=Check online for a solution and restart the program UI[6]=Check online for a solution later and close the program UI[7]=Close the program LoadedModule[0]=E:\FX\fsx.exe LoadedModule[1]=C:\Windows\SysWOW64\ntdll.dll LoadedModule[2]=C:\Windows\syswow64\kernel32.dll LoadedModule[3]=C:\Windows\syswow64\KERNELBASE.dll LoadedModule[4]=C:\Windows\WinSxS\x86_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_cbf5e994470a1a8f\MFC80.DLL LoadedModule[5]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCR80.dll LoadedModule[6]=C:\Windows\syswow64\msvcrt.dll LoadedModule[7]=C:\Windows\syswow64\GDI32.dll LoadedModule[8]=C:\Windows\syswow64\USER32.dll LoadedModule[9]=C:\Windows\syswow64\ADVAPI32.dll LoadedModule[10]=C:\Windows\SysWOW64\sechost.dll LoadedModule[11]=C:\Windows\syswow64\RPCRT4.dll LoadedModule[12]=C:\Windows\syswow64\SspiCli.dll LoadedModule[13]=C:\Windows\syswow64\CRYPTBASE.dll LoadedModule[14]=C:\Windows\syswow64\LPK.dll LoadedModule[15]=C:\Windows\syswow64\USP10.dll LoadedModule[16]=C:\Windows\syswow64\SHLWAPI.dll LoadedModule[17]=C:\Windows\syswow64\ole32.dll LoadedModule[18]=C:\Windows\system32\apphelp.dll LoadedModule[19]=C:\Windows\AppPatch\AcGenral.DLL LoadedModule[20]=C:\Windows\system32\UxTheme.dll LoadedModule[21]=C:\Windows\system32\WINMM.dll LoadedModule[22]=C:\Windows\system32\samcli.dll LoadedModule[23]=C:\Windows\syswow64\OLEAUT32.dll LoadedModule[24]=C:\Windows\system32\MSACM32.dll LoadedModule[25]=C:\Windows\system32\VERSION.dll LoadedModule[26]=C:\Windows\syswow64\SHELL32.dll LoadedModule[27]=C:\Windows\system32\sfc.dll LoadedModule[28]=C:\Windows\system32\sfc_os.DLL LoadedModule[29]=C:\Windows\system32\USERENV.dll LoadedModule[30]=C:\Windows\system32\profapi.dll LoadedModule[31]=C:\Windows\system32\dwmapi.dll LoadedModule[32]=C:\Windows\syswow64\SETUPAPI.dll LoadedModule[33]=C:\Windows\syswow64\CFGMGR32.dll LoadedModule[34]=C:\Windows\syswow64\DEVOBJ.dll LoadedModule[35]=C:\Windows\syswow64\urlmon.dll LoadedModule[36]=C:\Windows\syswow64\api-ms-win-downlevel-ole32-l1-1-0.dll LoadedModule[37]=C:\Windows\syswow64\api-ms-win-downlevel-shlwapi-l1-1-0.dll LoadedModule[38]=C:\Windows\syswow64\api-ms-win-downlevel-advapi32-l1-1-0.dll LoadedModule[39]=C:\Windows\syswow64\api-ms-win-downlevel-user32-l1-1-0.dll LoadedModule[40]=C:\Windows\syswow64\api-ms-win-downlevel-version-l1-1-0.dll LoadedModule[41]=C:\Windows\syswow64\api-ms-win-downlevel-normaliz-l1-1-0.dll LoadedModule[42]=C:\Windows\syswow64\normaliz.DLL LoadedModule[43]=C:\Windows\syswow64\iertutil.dll LoadedModule[44]=C:\Windows\syswow64\WININET.dll LoadedModule[45]=C:\Windows\system32\MPR.dll LoadedModule[46]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[47]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[48]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[49]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.18201_none_ec80f00e8593ece5\COMCTL32.dll LoadedModule[50]=C:\Windows\system32\mscms.dll LoadedModule[51]=C:\Windows\system32\DDRAW.dll LoadedModule[52]=C:\Windows\system32\DCIMAN32.dll LoadedModule[53]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[54]=C:\Windows\syswow64\IMM32.dll LoadedModule[55]=C:\Windows\syswow64\MSCTF.dll LoadedModule[56]=C:\Windows\syswow64\WS2_32.dll LoadedModule[57]=C:\Windows\syswow64\NSI.dll LoadedModule[58]=C:\Windows\system32\msi.dll LoadedModule[59]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[60]=E:\FX\language.dll LoadedModule[61]=E:\FX\API.DLL LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[63]=E:\FX\ablscpt.dll LoadedModule[64]=E:\FX\flight.dll LoadedModule[65]=E:\FX\ai_player.dll LoadedModule[66]=E:\FX\acontain.dll LoadedModule[67]=E:\FX\controls.dll LoadedModule[68]=C:\Windows\system32\DINPUT8.dll LoadedModule[69]=E:\FX\fsui.dll LoadedModule[70]=E:\FX\atc.dll LoadedModule[71]=E:\FX\facilities.dll LoadedModule[72]=E:\FX\demo.dll LoadedModule[73]=E:\FX\main.dll LoadedModule[74]=E:\FX\fe.dll LoadedModule[75]=E:\FX\util.dll LoadedModule[76]=E:\FX\simprop.dll LoadedModule[77]=E:\FX\g2d.dll LoadedModule[78]=C:\Windows\system32\d3dx9_34.dll LoadedModule[79]=C:\Windows\system32\d3dx10_34.dll LoadedModule[80]=C:\Windows\system32\d3d9.dll LoadedModule[81]=C:\Windows\system32\d3d8thk.dll LoadedModule[82]=E:\FX\g3d.dll LoadedModule[83]=E:\FX\panels.dll LoadedModule[84]=E:\FX\multiplayer.dll LoadedModule[85]=E:\FX\ui.dll LoadedModule[86]=E:\FX\sound.dll LoadedModule[87]=E:\FX\sim1.dll LoadedModule[88]=E:\FX\simscheduler.dll LoadedModule[89]=E:\FX\visualfx.dll LoadedModule[90]=E:\FX\window.dll LoadedModule[91]=E:\FX\terrain.dll LoadedModule[92]=E:\FX\weather.dll LoadedModule[93]=C:\Windows\system32\DSOUND.dll LoadedModule[94]=C:\Windows\system32\POWRPROF.dll LoadedModule[95]=E:\FX\symmap.dll LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18120_none_72d2e82386681b36\gdiplus.dll LoadedModule[97]=C:\Windows\system32\MSIMG32.dll LoadedModule[98]=E:\FX\xuipc.dll LoadedModule[99]=E:\FX\livingwater.dll LoadedModule[100]=E:\FX\fs-traffic.dll LoadedModule[101]=E:\FX\gps.dll LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll LoadedModule[104]=C:\ProgramData\Ad-Aware Browsing Protection\adawarebp.dll LoadedModule[105]=C:\Windows\system32\CRYPTSP.dll LoadedModule[106]=C:\Windows\system32\rsaenh.dll LoadedModule[107]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[108]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[109]=C:\Windows\syswow64\MSASN1.dll LoadedModule[110]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[111]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[112]=C:\Windows\system32\wbemcomn.dll LoadedModule[113]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[114]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[115]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[116]=C:\Windows\system32\NTDSAPI.dll LoadedModule[117]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[118]=C:\Windows\system32\dxgi.dll LoadedModule[119]=C:\Windows\system32\d3d11.dll LoadedModule[120]=C:\Windows\system32\nvd3dum.dll LoadedModule[121]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[122]=C:\Windows\system32\nvspcap.dll LoadedModule[123]=C:\Windows\system32\nvapi.dll LoadedModule[124]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[125]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[126]=C:\Windows\system32\d3d10_1.dll LoadedModule[127]=C:\Windows\system32\d3d10_1core.dll LoadedModule[128]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll LoadedModule[129]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[130]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[131]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[132]=C:\Windows\system32\winbrand.dll LoadedModule[133]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[134]=C:\Windows\system32\WINSTA.dll LoadedModule[135]=C:\Windows\SysWOW64\gameux.dll LoadedModule[136]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[137]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[138]=C:\Windows\SysWOW64\wer.dll LoadedModule[139]=C:\Windows\System32\Wpc.dll LoadedModule[140]=C:\Windows\System32\wevtapi.dll LoadedModule[141]=C:\Windows\System32\msxml6.dll LoadedModule[142]=C:\Windows\system32\SAMLIB.dll LoadedModule[143]=C:\Windows\system32\netutils.dll LoadedModule[144]=C:\Windows\system32\uiautomationcore.dll LoadedModule[145]=C:\Windows\system32\OLEACC.dll LoadedModule[146]=C:\Windows\System32\MMDevApi.dll LoadedModule[147]=C:\Windows\System32\PROPSYS.dll LoadedModule[148]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[149]=C:\Windows\system32\RICHED20.DLL LoadedModule[150]=C:\Windows\system32\HID.DLL LoadedModule[151]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[152]=C:\Windows\system32\wdmaud.drv LoadedModule[153]=C:\Windows\system32\ksuser.dll LoadedModule[154]=C:\Windows\system32\AVRT.dll LoadedModule[155]=C:\Windows\system32\msacm32.drv LoadedModule[156]=C:\Windows\system32\midimap.dll LoadedModule[157]=C:\Windows\system32\dinput.DLL LoadedModule[158]=C:\Windows\System32\wship6.dll LoadedModule[159]=C:\Windows\System32\wshtcpip.dll LoadedModule[160]=E:\FX\PMDG\DLLs\PMDG_Interface.dll LoadedModule[161]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[162]=E:\FX\RAASPRO\RAASPRO.dll LoadedModule[163]=C:\Windows\system32\Secur32.dll LoadedModule[164]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll LoadedModule[165]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[166]=C:\Windows\system32\WINNSI.DLL LoadedModule[167]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll LoadedModule[168]=C:\Windows\system32\DNSAPI.dll LoadedModule[169]=C:\Windows\system32\dhcpcsvc6.DLL LoadedModule[170]=C:\Windows\System32\netprofm.dll LoadedModule[171]=C:\Windows\System32\nlaapi.dll LoadedModule[172]=C:\Windows\system32\dhcpcsvc.DLL LoadedModule[173]=C:\Program Files (x86)\Bonjour\mdnsNSP.dll LoadedModule[174]=C:\Windows\System32\npmproxy.dll LoadedModule[175]=C:\Windows\system32\rasadhlp.dll LoadedModule[176]=C:\Windows\System32\fwpuclnt.dll LoadedModule[177]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[178]=C:\Program Files (x86)\Common Files\System\ado\msado15.dll LoadedModule[179]=C:\Windows\system32\MSDART.DLL LoadedModule[180]=C:\Program Files (x86)\Common Files\System\Ole DB\oledb32.dll LoadedModule[181]=C:\Windows\system32\bcrypt.dll LoadedModule[182]=C:\Program Files (x86)\Common Files\System\Ole DB\OLEDB32R.DLL LoadedModule[183]=C:\Windows\system32\comsvcs.dll LoadedModule[184]=C:\Windows\system32\ATL.DLL LoadedModule[185]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[186]=C:\Windows\SysWOW64\msjetoledb40.dll LoadedModule[187]=C:\Windows\SysWOW64\msjet40.dll LoadedModule[188]=C:\Windows\SysWOW64\mswstr10.dll LoadedModule[189]=C:\Windows\SysWOW64\msjter40.dll LoadedModule[190]=C:\Windows\SysWOW64\MSJINT40.DLL LoadedModule[191]=C:\Windows\SysWOW64\mstext40.dll LoadedModule[192]=C:\Windows\system32\mlang.dll LoadedModule[193]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[194]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll LoadedModule[195]=C:\Windows\SysWOW64\mshtml.dll LoadedModule[196]=C:\Windows\system32\msimtf.dll LoadedModule[197]=C:\Windows\system32\msls31.dll LoadedModule[198]=C:\Windows\system32\d2d1.dll LoadedModule[199]=C:\Windows\system32\DWrite.dll LoadedModule[200]=C:\Windows\system32\D3D10Warp.dll LoadedModule[201]=C:\Windows\system32\ntmarta.dll LoadedModule[202]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[203]=E:\FX\GAUGES\PMDG_777X.DLL LoadedModule[204]=C:\Windows\system32\NETAPI32.dll LoadedModule[205]=C:\Windows\system32\srvcli.dll LoadedModule[206]=C:\Windows\system32\wkscli.dll LoadedModule[207]=C:\Windows\system32\WSOCK32.dll LoadedModule[208]=C:\Windows\system32\napinsp.dll LoadedModule[209]=C:\Windows\system32\pnrpnsp.dll LoadedModule[210]=C:\Windows\System32\winrnr.dll LoadedModule[211]=C:\Windows\system32\icmp.Dll LoadedModule[212]=C:\Windows\system32\msadp32.acm Sec[0].Key=LCID Sec[0].Value=1033 State[0].Key=Transport.DoneStage1 State[0].Value=1 State[1].Key=DataRequest State[1].Value=Bucket=-453176452/nBucketTable=1/nResponse=1/n FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft® Flight Simulator X AppPath=E:\FX\fsx.exe

Thanks for the reply, I fixed the problem with a bit of help from PMDG. Actually PMDG did give me three links to C++ run times, but the first link is to a DirectX run time installer, so PMDG trying to fix my DirectX got me thinking. I'm using DirectX9, have read there are less problems with it then DirectX10. I decided to research DirectX9, and it looked like a later version DirectX9c came out in 2010, which is later date then the last copy of MSFX Gold I installed on my HD with DirectX on it. I downloaded DirectX9c, and installed, then downloaded again the DirectX run time installer, the first link of the four PMDG gave me, ran it's program and the problem is fixed. Did the newer version DirectX9c fix the problem, not sure, but I'd guess yes. But did the DirectX run time installer fix any problems with DirectX9c? No way of knowing, at least it did not do any harm.

I'm slow with software, and there are some real guru's on here, some patient, thank God. I had the same problem so, as Bill O'reilly says I'm a simple minded person. So maybe I can explain it simpler, step by step. I'm using Windows 7, first install Microsoft Flight Simulator, Gold Edition is less hassle . First step open control panel, if your view has everything clustered in eight categories, click on the small Category icon to the top right of the panel, click small icons, large will work. Then you have about 51 items listed: Action Center to Windows Card Space. In the third column from the left, the fourth one down from the top click on "Folder Options". A window will open titled "Folder Options", click on "search" at the top right. Another window opens, at the top a category says "what to search", click the dot, "in indexed locations, search file name and content. In non-indexed locations search file names only, if you do this first the file will not show up". Do not search a second drive even if you have FSX installed on it, search your main drive, that has Windows on it. Now go to Start button, type C:\Users\Your Username\, "usually your first name" \AppData\Roaming\Microsoft\FSX\fsx.CFG, the "fsx.CFG" will popup . Right click "fsx.CFG", click open, another small window opens titled "File Type Helper". It will ask you "What do you want to do?" Click on the dot, "Open this file using software which is already installed". Another window opens titled "Open with" Choose Notepad if more then one choice is listed, otherwise click "okay" at the bottom, and the "fsx.CFG" file will open. "DISPLAY" is about a third or more down the list. HIGHMEMFIX was not listed, so I moved my mouse arrow next to DISPLAY, left clicked like I was adding to that line, clicked enter on the keyboard which makes a space below DISPLAY. That's where I added HIGHMEMFIX=1, although it can go anywhere under display. I made a few other changes as per FSX mod. guide found on the FSX forum here at AVSIM. Be sure to Click Save before closing the fsx.CFG file. I know this is long but maybe it will help, I went thru quite a process trying to find this file myself.

Thanks for the reply, but I saw your post, and my problem is not this. I did hear from the PMDG technical staff and they gave me four links to Microsoft. The first one was for Microsoft DirectX runtimes full installer, and the other three were for Microsoft Visual C++ 2005 SP1 runtimes:, and 2008 SP1 runtimes:, and 2010SP! runtimes: I installed them all, the first one in a temp. file on my E drive as I'm running a separate drive for MSFX. The other three went on my C drive automatically as these files do not give any choice where you want to put them. I tried another flight from Male with the PMDG 777 and thought these fixes might be working, but they weren't. About a minute after I engaged the Auto Pilot the PFD and ND went crazy again, as I've previously described. I'm waiting for a response from the PMDG staff as what to do next. I posted on this forum to possibly find a solution a bit quicker. Thanks, Brian http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=8109 http://www.microsoft.com/en-us/download/details.aspx?id=5638 http://www.microsoft.com/en-us/download/details.aspx?id=5582 http://www.microsoft.com/download/en/details.aspx?id=8328