Jump to content

Saitek Switch Box Causes g3d.dll Error


Recommended Posts

Sorry to start a ne thread but I want to start over. Pulling my hair out my Saitek Switch Box causes the FSX to crash when ending the flight. Tried and removed the Saitek driver/software and using SPAD now with the same issue. Thought it might be the aircraft (still might be) but it just happened with the default cessna as well. Any and all suggestions welcome. Got to be some kind of conflict just can't isolate it.

Mike G.

Intel Core i7-4770K, ASUS MAXIMUS VI HERO Motherboard, , 8GB Memory , EVGA GeForce GTX 1070 6GB Video Card,Corsair Enthusiast 750W 80+ Bronze Certified ATX Power Supply,Windows 7 64bit, Corsair Hydro Series H55 CPU Cooler

Link to comment
Share on other sites

Update, the switch box works fine with my other single monitor build do maybe an update or something? Just can't find the answer. A microsoft frame work update it requires? I am grasping at straws now.

Mike G.

Intel Core i7-4770K, ASUS MAXIMUS VI HERO Motherboard, , 8GB Memory , EVGA GeForce GTX 1070 6GB Video Card,Corsair Enthusiast 750W 80+ Bronze Certified ATX Power Supply,Windows 7 64bit, Corsair Hydro Series H55 CPU Cooler

Link to comment
Share on other sites

Good idea, tried. Here is what I have tried as well:

 

Saitek Switch panel causes FSX to crash after

1st. Ending Flight

2nd. Changing Planes

3rd. changing Airports

CTD mostly a g3d.dll error

What I have checked:

Tested on another computer with X52 Pro and Pro Yoke flight systems with drivers for all installed. Works fine. Build:

AMD 6300 Radeon 7770 DirectX 64-bit Operating System Windows 7

 

FSUIPC registered installed.

UIAutomationCore.dll installed

 

Issue with Build:

Intel Core i7-4770K, ASUS MAXIMUS VI HERO Motherboard, , 8GB Memory , EVGA GeForce GTX 770 4GB Video Card, Corsair Enthusiast 750W 80+ Bronze Certified ATX Power Supply, Windows 7 64bit, Corsair Hydro Series H55 CPU Cooler Overclocked to 4.2 at 1.25V

 

Tested using Keyboard and mouse with Saitek Switch Box. Works fine.

 

Tested X52 Pro only with Switch Box. Causes error

Tested Pro Yoke only with Switch Box. Causes error

Tested both X52 Pro and Pro Yoke connected. Causes error

Tested all three again with drivers removed. Causes error

 

 

FSUIPC registered installed.

UIAutomationCore.dll installed

 

I am about to offer a reward for any information leading to solving this issue. Been googling everything I can think of.

Mike G.

Intel Core i7-4770K, ASUS MAXIMUS VI HERO Motherboard, , 8GB Memory , EVGA GeForce GTX 1070 6GB Video Card,Corsair Enthusiast 750W 80+ Bronze Certified ATX Power Supply,Windows 7 64bit, Corsair Hydro Series H55 CPU Cooler

Link to comment
Share on other sites

Have you tried different graphics card drivers?

 

Is this a problem thats only just started happening? Has it been working ok on this computer.?

 

It sounds like a driver conflict somewhere. Have your updated graphics drivers prior to this problem arising?

 

Good luck

Stinger

 

 

 

Sent from my MZ604 using Tapatalk

Link to comment
Share on other sites

I just bought the gox. The switch box works fine if I disconnect the other Saitek controls. It works without crashing if I use my Thrustmaster stick instead of the Saitek Yoke or X52 Pro. Don't believe it is a graphics issue even though it gives a g3d.dll error.

Mike G.

Intel Core i7-4770K, ASUS MAXIMUS VI HERO Motherboard, , 8GB Memory , EVGA GeForce GTX 1070 6GB Video Card,Corsair Enthusiast 750W 80+ Bronze Certified ATX Power Supply,Windows 7 64bit, Corsair Hydro Series H55 CPU Cooler

Link to comment
Share on other sites

And yet all three work together fine on a different PC? Which means there's something in your main PC causing the issue. And the error type points towards graphics. That's where I'd be looking.

 

Cheers

Stinger

 

Sent from my SM-A300FU using Tapatalk

Link to comment
Share on other sites

But what could be wrong with my Graphics? The PC in question is very high end and everything is working like a dream. There is the three monitors. And obviously a different motherboard, processor the like. Also, the switch box works fine as long as I don't use the X52 or the Saitek yoke. Using the Thrustmaster stick with the box or just the keyboard and mouse it works fine. I had a someone tell me the Switch box didn't like the USB3 so I am checking that out now. I have also been avoiding the "End Flight " option as well ie changing planes, moving to other locations to see if and when the error occurs.

Mike G.

Intel Core i7-4770K, ASUS MAXIMUS VI HERO Motherboard, , 8GB Memory , EVGA GeForce GTX 1070 6GB Video Card,Corsair Enthusiast 750W 80+ Bronze Certified ATX Power Supply,Windows 7 64bit, Corsair Hydro Series H55 CPU Cooler

Link to comment
Share on other sites

Could any ,of these updates have anything to do with it? These are installed on the CP with no issues.

Microsoft Visual C++ 2015 Redistributable (x86)-14.0.23506

 

Microsoft Visual C++ 2013 Redistributable (x86)-12.0.30501

 

Microsoft Visual C++ 2012 Redistributable (x86)-11.0.61030

 

Microsoft Visual C++ 2012 Redistributable (x64)-11.0.61030

 

Microsoft Visual C++ 2010 x86 Redistributable-10.0.30319

 

Microsoft Visual C++ 2010 x64 Redistributable-10.0.30319

 

Microsoft Visual C++ 2008 Redistributable-x86 9.0.30729.6161

 

Microsoft Visual C++ 2008 Redistributable-x64 9.0.30729.6161

 

Microsoft Visual C++ 2008 Redistributable-x86 9.0.30729.17

 

Microsoft Visual C++ 2008 Redistributable-x64 9.0.30729.17

 

Microsoft Visual C++ 2005 Redistributable x64

 

Microsoft Visual C++ 2005 Redistributable

 

MSXML 4.0 SP2 (KB954430)

MSXML 4.0 SP2 (KB973688)

MSXML 4.0 SP2 Parser and SDK

Mike G.

Intel Core i7-4770K, ASUS MAXIMUS VI HERO Motherboard, , 8GB Memory , EVGA GeForce GTX 1070 6GB Video Card,Corsair Enthusiast 750W 80+ Bronze Certified ATX Power Supply,Windows 7 64bit, Corsair Hydro Series H55 CPU Cooler

Link to comment
Share on other sites

I'm not suggesting that there is anything wrong with you graphics but it is obviously different to your other PC and that would include the drivers for your card. A quick Google reveals many reasons for this type of error, from bad add on scenery to memory issues. It's going to take a lot if trial an error to see why one of your systems is fine and the other not. It might be worth disabling all of your add on scenery via the scenery library to see if it still does it.

 

Good luck

Stinger

 

Sent from my SM-A300FU using Tapatalk

Link to comment
Share on other sites

Ha! Ha! That would be a good idea but I have so much installed I just had this new computer put together about three years ago and even then it took six months to completely bring it up to speed with the old one so I am sure you can understand that would be only a last resort as even suggested a clean reinstall of FSX it's self. That Switch Box doesn't mean that much to me and I can tell you now if I did that and still had the issue I would not be happy. I have learned from experience with FSX it is definitely better to trace down the cause of an issue at least you will know what it is and not repeat it. I believe you on the graphic issue however, if it was a particular scenery issue the error would occur using the Thrustmaster and or the keyboard to without using the Saitek Yoke or X52 wouldn't you agree to that?

Mike G.

Intel Core i7-4770K, ASUS MAXIMUS VI HERO Motherboard, , 8GB Memory , EVGA GeForce GTX 1070 6GB Video Card,Corsair Enthusiast 750W 80+ Bronze Certified ATX Power Supply,Windows 7 64bit, Corsair Hydro Series H55 CPU Cooler

Link to comment
Share on other sites

Holy cow! I am approaching it in another way. I am trying to create it on the other computer. It's funny because I generally use that older one to test and work new things anyway and then when I know they work install them in the newer computer. I have started to keep a list of what I have checked so far if you would like to see. Maybe you will catch something I missed.

 

Maybe someone has had this happen. I have the Saitek X52 Pro and the Pro Yoke systems connected and working great. I recently purchased the Saitek Switch box but when I use it with the other saitek controls when I exit and change planes and or relocate I crash fsx usually with a g3d.dll error. Payware, default and freeware aircraft no difference. The switch Box works fine except for that. Have tried SPAD and Saitek Software/drivers. Here is what Have done:

Saitek Switch panel causes FSX to crash after

1st. Ending Flight

2nd. Changing Planes

3rd. changing Airports

What I have checked:

Tested on another computer with X52 Pro and Pro Yoke flight systems with drivers for all installed. Works fine. Build:

AMD 6300 Radeon 7770 DirectX 64-bit Operating System Windows 7

 

FSUIPC registered installed.

UIAutomationCore.dll installed

Issue with Build:

Intel Core i7-4770K, ASUS MAXIMUS VI HERO Motherboard, , 8GB Memory , EVGA GeForce GTX 770 4GB Video Card, Corsair Enthusiast 750W 80+ Bronze Certified ATX Power Supply, Windows 7 64bit, Corsair Hydro Series H55 CPU Cooler Overclocked to 4.2 at 1.25V

 

Tested using Keyboard and mouse with Saitek Switch Box. Works fine.

Tested X52 Pro only with Switch Box. Causes error

Tested Pro Yoke only with Switch Box. Causes error

Tested both X52 Pro and Pro Yoke connected. Causes error

Tested all three again with drivers removed. Causes error

FSUIPC registered installed.

UIAutomationCore.dll installed

 

Here are the two typical errors I get:

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0x6a1f1000

Faulting process id: 0xef8

Faulting application start time: 0x01d294ebabd44f76

Faulting application path: C:\FSX\fsx.exe

Faulting module path: unknown

Report Id: 341218cb-00ee-11e7-9073-e03f498468c0

 

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14

Faulting module name: g3d.dll, version: 10.0.61637.0, time stamp: 0x46fadb58

Exception code: 0xc0000005

Fault offset: 0x0002e766

Faulting process id: 0xae8

Faulting application start time: 0x01d293bb0f095323

Faulting application path: C:\FSX\fsx.exe

Faulting module path: C:\FSX\g3d.dll

Report Id: 7653517d-ffb0-11e6-a8e8-e03f498468c0

 

 

Here are updates installed on the PC with no Switch box crashes. Might they have something to do with it?

Microsoft Visual C++ 2015 Redistributable (x86)-14.0.23506

 

Microsoft Visual C++ 2013 Redistributable (x86)-12.0.30501

Microsoft Visual C++ 2012 Redistributable (x86)-11.0.61030

Microsoft Visual C++ 2012 Redistributable (x64)-11.0.61030

Microsoft Visual C++ 2010 x86 Redistributable-10.0.30319

Microsoft Visual C++ 2010 x64 Redistributable-10.0.30319

Microsoft Visual C++ 2008 Redistributable-x86 9.0.30729.6161

Microsoft Visual C++ 2008 Redistributable-x64 9.0.30729.6161

Microsoft Visual C++ 2008 Redistributable-x86 9.0.30729.17

Microsoft Visual C++ 2008 Redistributable-x64 9.0.30729.17

Microsoft Visual C++ 2005 Redistributable x64

Microsoft Visual C++ 2005 Redistributable

 

MSXML 4.0 SP2 (KB954430)

MSXML 4.0 SP2 (KB973688)

MSXML 4.0 SP2 Parser and SDK

 

Here is the notes from AppCrashView on a crash:

Version=1

EventType=BEX

EventTime=131331512361749285

ReportType=2

Consent=1

UploadTime=131331512362841286

ReportIdentifier=cbcd34a6-0143-11e7-8b7e-b8975a32c33c

IntegratorReportIdentifier=cbcd34a5-0143-11e7-8b7e-b8975a32c33c

WOW64=1

Response.BucketId=529557138

Response.BucketTable=5

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=unknown

Sig[4].Name=Fault Module Version

Sig[4].Value=0.0.0.0

Sig[5].Name=Fault Module Timestamp

Sig[5].Value=00000000

Sig[6].Name=Exception Offset

Sig[6].Value=00000012

Sig[7].Name=Exception Code

Sig[7].Value=c0000005

Sig[8].Name=Exception Data

Sig[8].Value=00000008

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]=C:\FSX\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]=C:\FSX\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\syswow64\USERENV.dll

LoadedModule[30]=C:\Windows\syswow64\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]=C:\FSX\language.dll

LoadedModule[61]=C:\FSX\API.DLL

LoadedModule[62]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll

LoadedModule[63]=C:\FSX\ablscpt.dll

LoadedModule[64]=C:\FSX\flight.dll

LoadedModule[65]=C:\FSX\ai_player.dll

LoadedModule[66]=C:\FSX\acontain.dll

LoadedModule[67]=C:\FSX\controls.dll

LoadedModule[68]=C:\Windows\system32\DINPUT8.dll

LoadedModule[69]=C:\FSX\fsui.dll

LoadedModule[70]=C:\FSX\atc.dll

LoadedModule[71]=C:\FSX\facilities.dll

LoadedModule[72]=C:\FSX\demo.dll

LoadedModule[73]=C:\FSX\main.dll

LoadedModule[74]=C:\FSX\fe.dll

LoadedModule[75]=C:\FSX\util.dll

LoadedModule[76]=C:\FSX\simprop.dll

LoadedModule[77]=C:\FSX\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]=C:\FSX\g3d.dll

LoadedModule[83]=C:\FSX\panels.dll

LoadedModule[84]=C:\FSX\multiplayer.dll

LoadedModule[85]=C:\FSX\ui.dll

LoadedModule[86]=C:\FSX\sound.dll

LoadedModule[87]=C:\FSX\sim1.dll

LoadedModule[88]=C:\FSX\simscheduler.dll

LoadedModule[89]=C:\FSX\visualfx.dll

LoadedModule[90]=C:\FSX\window.dll

LoadedModule[91]=C:\FSX\terrain.dll

LoadedModule[92]=C:\FSX\weather.dll

LoadedModule[93]=C:\Windows\system32\DSOUND.dll

LoadedModule[94]=C:\Windows\system32\POWRPROF.dll

LoadedModule[95]=C:\FSX\symmap.dll

LoadedModule[96]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18834_none_72d38c5186679d48\gdiplus.dll

LoadedModule[97]=C:\Windows\system32\MSIMG32.dll

LoadedModule[98]=C:\FSX\xuipc.dll

LoadedModule[99]=C:\FSX\livingwater.dll

LoadedModule[100]=C:\FSX\fs-traffic.dll

LoadedModule[101]=C:\FSX\gps.dll

LoadedModule[102]=C:\Windows\system32\MSWSOCK.dll

LoadedModule[103]=C:\Windows\system32\SHFOLDER.dll

LoadedModule[104]=C:\Program Files (x86)\ATI Technologies\HydraVision\HydraDMH.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\wbemcomn2.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\aticfx32.dll

LoadedModule[121]=C:\Windows\system32\atiu9pag.dll

LoadedModule[122]=C:\Windows\system32\atiumdag.dll

LoadedModule[123]=C:\Windows\system32\atiumdva.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:\Windows\SysWOW64\dxdiagn.dll

LoadedModule[129]=C:\Windows\SysWOW64\d3d10.dll

LoadedModule[130]=C:\Windows\SysWOW64\d3d10core.dll

LoadedModule[131]=C:\Windows\system32\winbrand.dll

LoadedModule[132]=C:\Windows\system32\WTSAPI32.DLL

LoadedModule[133]=C:\Windows\system32\WINSTA.dll

LoadedModule[134]=C:\Windows\SysWOW64\gameux.dll

LoadedModule[135]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.18807_none_41e554362bd82458\COMCTL32.dll

LoadedModule[136]=C:\Windows\SysWOW64\XmlLite.dll

LoadedModule[137]=C:\Windows\SysWOW64\wer.dll

LoadedModule[138]=C:\Windows\System32\Wpc.dll

LoadedModule[139]=C:\Windows\System32\wevtapi.dll

LoadedModule[140]=C:\Windows\System32\msxml6.dll

LoadedModule[141]=C:\Windows\system32\SAMLIB.dll

LoadedModule[142]=C:\Windows\system32\netutils.dll

LoadedModule[143]=C:\FSX\uiautomationcore.dll

LoadedModule[144]=C:\Windows\system32\OLEACC.dll

LoadedModule[145]=C:\Windows\System32\MMDevApi.dll

LoadedModule[146]=C:\Windows\System32\PROPSYS.dll

LoadedModule[147]=C:\Windows\system32\AUDIOSES.DLL

LoadedModule[148]=C:\Windows\system32\RICHED20.DLL

LoadedModule[149]=C:\Windows\system32\HID.DLL

LoadedModule[150]=C:\Windows\system32\XInput9_1_0.dll

LoadedModule[151]=C:\Windows\system32\wdmaud.drv

LoadedModule[152]=C:\Windows\system32\ksuser.dll

LoadedModule[153]=C:\Windows\system32\AVRT.dll

LoadedModule[154]=C:\Windows\system32\msacm32.drv

LoadedModule[155]=C:\Windows\system32\midimap.dll

LoadedModule[156]=C:\Windows\system32\dinput.DLL

LoadedModule[157]=C:\Windows\System32\wship6.dll

LoadedModule[158]=C:\Windows\System32\wshtcpip.dll

LoadedModule[159]=C:\Instant Scenery 3\InstantSceneryFSX.dll

LoadedModule[160]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll

LoadedModule[161]=C:\Windows\system32\IPHLPAPI.DLL

LoadedModule[162]=C:\Windows\system32\WINNSI.DLL

LoadedModule[163]=C:\Windows\syswow64\PSAPI.DLL

LoadedModule[164]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll

LoadedModule[165]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61242.0_none_e079b46b85043c20\SimConnect.dll

LoadedModule[166]=C:\Windows\system32\msadp32.acm

LoadedModule[167]=C:\Windows\SysWOW64\ieframe.dll

LoadedModule[168]=C:\Windows\SysWOW64\api-ms-win-downlevel-shell32-l1-1-0.dll

LoadedModule[169]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll

LoadedModule[170]=C:\Windows\system32\Secur32.dll

LoadedModule[171]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll

LoadedModule[172]=C:\Windows\SysWOW64\mshtml.dll

LoadedModule[173]=C:\Windows\system32\msimtf.dll

LoadedModule[174]=C:\Windows\system32\msls31.dll

LoadedModule[175]=C:\Windows\system32\d2d1.dll

LoadedModule[176]=C:\Windows\system32\DWrite.dll

LoadedModule[177]=C:\Windows\system32\D3D10Warp.dll

LoadedModule[178]=C:\Windows\system32\MLANG.dll

LoadedModule[179]=C:\Windows\system32\ntmarta.dll

LoadedModule[180]=C:\Windows\syswow64\WLDAP32.dll

LoadedModule[181]=C:\Windows\SysWOW64\uiautomationcore.dll

LoadedModule[182]=C:\FSX\GAUGES\Cessna.DLL

LoadedModule[183]=C:\FSX\GAUGES\Cessna172.DLL

LoadedModule[184]=C:\FSX\GAUGES\Cessna182s.DLL

LoadedModule[185]=C:\FSX\GAUGES\CessnaWAlpha.DLL

LoadedModule[186]=C:\FSX\GAUGES\Bendix_King_Radio.DLL

LoadedModule[187]=C:\FSX\GAUGES\dsd_fsx_xml_sound.GAU

LoadedModule[188]=C:\FSX\GAUGES\Bell_206B.DLL

LoadedModule[189]=C:\Windows\system32\DNSAPI.dll

LoadedModule[190]=C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live\WLIDNSP.DLL

LoadedModule[191]=C:\Windows\System32\netprofm.dll

LoadedModule[192]=C:\Windows\System32\nlaapi.dll

LoadedModule[193]=C:\Windows\system32\dhcpcsvc6.DLL

LoadedModule[194]=C:\Windows\system32\dhcpcsvc.DLL

LoadedModule[195]=C:\Windows\System32\npmproxy.dll

LoadedModule[196]=C:\Windows\system32\rasadhlp.dll

LoadedModule[197]=C:\Windows\system32\msiltcfg.dll

LoadedModule[198]=C:\Windows\System32\fwpuclnt.dll

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=529557138/nBucketTable=5/nResponse=1/n

FriendlyEventName=Stopped working

ConsentKey=BEX

AppName=Microsoft® Flight Simulator X

AppPath=C:\FSX\fsx.exe

Mike G.

Intel Core i7-4770K, ASUS MAXIMUS VI HERO Motherboard, , 8GB Memory , EVGA GeForce GTX 1070 6GB Video Card,Corsair Enthusiast 750W 80+ Bronze Certified ATX Power Supply,Windows 7 64bit, Corsair Hydro Series H55 CPU Cooler

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...