January 2, 201313 yr Hey guys and gals, My frustration has peaked with this one. I reformatted my hd this past weekend to "upgrade" from Win8 x64 to Win7 x64 for the controller disconnect issues with 8. Since then I frequently get the g3d.dll CTD. I have 2 failed flights today. The first on was on 20nm final into FSDT KLAX v2 and the second one was around 20nm final into default KDEN. Scarlett's post on Sunday says it could be corrupt scenery installation so I reinstalled FSDT KLAX. I have Bojote's tweaking tool, FSUIPC4 (unregistered) and followed NickN's guide for installation. My specs are <-----. Any other ideas will be greatly appreciated. Thank you, Chuck Version=1 EventType=APPCRASH EventTime=130015820589232535 ReportType=2 Consent=1 ReportIdentifier=6f092bba-54a6-11e2-af70-bcaec576077c IntegratorReportIdentifier=6f092bb9-54a6-11e2-af70-bcaec576077c WOW64=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=g3d.dll Sig[4].Name=Fault Module Version Sig[4].Value=10.0.61637.0 Sig[5].Name=Fault Module Timestamp Sig[5].Value=46fadb58 Sig[6].Name=Exception Code Sig[6].Value=c0000005 Sig[7].Name=Exception Offset Sig[7].Value=000ba79f 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\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\iertutil.dll LoadedModule[37]=C:\Windows\syswow64\WININET.dll LoadedModule[38]=C:\Windows\syswow64\Normaliz.dll LoadedModule[39]=C:\Windows\system32\MPR.dll LoadedModule[40]=C:\Windows\AppPatch\AcLayers.DLL LoadedModule[41]=C:\Windows\system32\WINSPOOL.DRV LoadedModule[42]=C:\Windows\AppPatch\AcSpecfc.DLL LoadedModule[43]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\COMCTL32.dll LoadedModule[44]=C:\Windows\system32\mscms.dll LoadedModule[45]=C:\Windows\system32\DDRAW.dll LoadedModule[46]=C:\Windows\system32\DCIMAN32.dll LoadedModule[47]=C:\Windows\syswow64\COMDLG32.dll LoadedModule[48]=C:\Windows\syswow64\IMM32.dll LoadedModule[49]=C:\Windows\syswow64\MSCTF.dll LoadedModule[50]=C:\Windows\syswow64\WS2_32.dll LoadedModule[51]=C:\Windows\syswow64\NSI.dll LoadedModule[52]=C:\Windows\system32\msi.dll LoadedModule[53]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL LoadedModule[54]=C:\FSX\language.dll LoadedModule[55]=C:\FSX\API.DLL LoadedModule[56]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll LoadedModule[57]=C:\FSX\ablscpt.dll LoadedModule[58]=C:\FSX\flight.dll LoadedModule[59]=C:\FSX\ai_player.dll LoadedModule[60]=C:\FSX\acontain.dll LoadedModule[61]=C:\FSX\controls.dll LoadedModule[62]=C:\Windows\system32\DINPUT8.dll LoadedModule[63]=C:\FSX\fsui.dll LoadedModule[64]=C:\FSX\atc.dll LoadedModule[65]=C:\FSX\facilities.dll LoadedModule[66]=C:\FSX\demo.dll LoadedModule[67]=C:\FSX\main.dll LoadedModule[68]=C:\FSX\fe.dll LoadedModule[69]=C:\FSX\util.dll LoadedModule[70]=C:\FSX\simprop.dll LoadedModule[71]=C:\FSX\g2d.dll LoadedModule[72]=C:\Windows\system32\d3dx9_34.dll LoadedModule[73]=C:\Windows\system32\d3dx10_34.dll LoadedModule[74]=C:\Windows\system32\d3d9.dll LoadedModule[75]=C:\Windows\system32\d3d8thk.dll LoadedModule[76]=C:\FSX\g3d.dll LoadedModule[77]=C:\FSX\panels.dll LoadedModule[78]=C:\FSX\multiplayer.dll LoadedModule[79]=C:\FSX\ui.dll LoadedModule[80]=C:\FSX\sound.dll LoadedModule[81]=C:\FSX\sim1.dll LoadedModule[82]=C:\FSX\simscheduler.dll LoadedModule[83]=C:\FSX\visualfx.dll LoadedModule[84]=C:\FSX\window.dll LoadedModule[85]=C:\FSX\terrain.dll LoadedModule[86]=C:\FSX\weather.dll LoadedModule[87]=C:\Windows\system32\DSOUND.dll LoadedModule[88]=C:\Windows\system32\POWRPROF.dll LoadedModule[89]=C:\FSX\symmap.dll LoadedModule[90]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll LoadedModule[91]=C:\Windows\system32\MSIMG32.dll LoadedModule[92]=C:\FSX\xuipc.dll LoadedModule[93]=C:\FSX\livingwater.dll LoadedModule[94]=C:\FSX\fs-traffic.dll LoadedModule[95]=C:\FSX\gps.dll LoadedModule[96]=C:\Windows\system32\MSWSOCK.dll LoadedModule[97]=C:\Windows\system32\SHFOLDER.dll LoadedModule[98]=C:\Windows\system32\CRYPTSP.dll LoadedModule[99]=C:\Windows\system32\rsaenh.dll LoadedModule[100]=C:\Windows\syswow64\WINTRUST.dll LoadedModule[101]=C:\Windows\syswow64\CRYPT32.dll LoadedModule[102]=C:\Windows\syswow64\MSASN1.dll LoadedModule[103]=C:\Windows\syswow64\CLBCatQ.DLL LoadedModule[104]=C:\Windows\system32\wbem\wbemprox.dll LoadedModule[105]=C:\Windows\system32\wbemcomn.dll LoadedModule[106]=C:\Windows\system32\RpcRtRemote.dll LoadedModule[107]=C:\Windows\system32\wbem\wbemsvc.dll LoadedModule[108]=C:\Windows\system32\wbem\fastprox.dll LoadedModule[109]=C:\Windows\system32\NTDSAPI.dll LoadedModule[110]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9876.0_none_b7e610287b2b4ea5\MSXML4.DLL LoadedModule[111]=C:\Windows\system32\dxgi.dll LoadedModule[112]=C:\Windows\system32\nvd3dum.dll LoadedModule[113]=C:\Windows\syswow64\PSAPI.DLL LoadedModule[114]=C:\Windows\system32\D3DCompiler_34.dll LoadedModule[115]=C:\Windows\system32\WindowsCodecs.dll LoadedModule[116]=C:\Windows\system32\d3d10_1.dll LoadedModule[117]=C:\Windows\system32\d3d10_1core.dll LoadedModule[118]=C:\Windows\SysWOW64\dxdiagn.dll LoadedModule[119]=C:\Windows\SysWOW64\d3d10.dll LoadedModule[120]=C:\Windows\SysWOW64\d3d10core.dll LoadedModule[121]=C:\Windows\SysWOW64\d3d11.dll LoadedModule[122]=C:\Windows\system32\winbrand.dll LoadedModule[123]=C:\Windows\system32\WTSAPI32.DLL LoadedModule[124]=C:\Windows\system32\WINSTA.dll LoadedModule[125]=C:\Windows\SysWOW64\gameux.dll LoadedModule[126]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll LoadedModule[127]=C:\Windows\SysWOW64\XmlLite.dll LoadedModule[128]=C:\Windows\SysWOW64\wer.dll LoadedModule[129]=C:\Windows\System32\Wpc.dll LoadedModule[130]=C:\Windows\System32\wevtapi.dll LoadedModule[131]=C:\Windows\System32\msxml6.dll LoadedModule[132]=C:\Windows\system32\SAMLIB.dll LoadedModule[133]=C:\Windows\system32\netutils.dll LoadedModule[134]=C:\Windows\system32\uiautomationcore.dll LoadedModule[135]=C:\Windows\system32\OLEACC.dll LoadedModule[136]=C:\Windows\System32\MMDevApi.dll LoadedModule[137]=C:\Windows\System32\PROPSYS.dll LoadedModule[138]=C:\Windows\system32\AUDIOSES.DLL LoadedModule[139]=C:\Windows\system32\RICHED20.DLL LoadedModule[140]=C:\Windows\system32\HID.DLL LoadedModule[141]=C:\Windows\system32\ntmarta.dll LoadedModule[142]=C:\Windows\syswow64\WLDAP32.dll LoadedModule[143]=C:\Windows\system32\XInput9_1_0.dll LoadedModule[144]=C:\Windows\system32\wdmaud.drv LoadedModule[145]=C:\Windows\system32\ksuser.dll LoadedModule[146]=C:\Windows\system32\AVRT.dll LoadedModule[147]=C:\Windows\system32\msacm32.drv LoadedModule[148]=C:\Windows\system32\midimap.dll LoadedModule[149]=C:\Windows\system32\dinput.DLL LoadedModule[150]=C:\Windows\System32\wship6.dll LoadedModule[151]=C:\Windows\System32\wshtcpip.dll LoadedModule[152]=C:\FSX\bglmanx.dll LoadedModule[153]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll LoadedModule[154]=C:\Windows\system32\inetmib1.dll LoadedModule[155]=C:\Windows\system32\IPHLPAPI.DLL LoadedModule[156]=C:\Windows\system32\WINNSI.DLL LoadedModule[157]=C:\Windows\system32\snmpapi.dll LoadedModule[158]=C:\FSX\Modules\FSUIPC4.dll LoadedModule[159]=C:\Windows\syswow64\imagehlp.dll LoadedModule[160]=C:\Windows\system32\ncrypt.dll LoadedModule[161]=C:\Windows\system32\bcrypt.dll LoadedModule[162]=C:\Windows\SysWOW64\bcryptprimitives.dll LoadedModule[163]=C:\Windows\system32\GPAPI.dll LoadedModule[164]=C:\Windows\system32\cryptnet.dll LoadedModule[165]=C:\Windows\system32\SensApi.dll LoadedModule[166]=C:\FSX\PMDG\DLLs\PMDG_HUD_interface.dll LoadedModule[167]=C:\Windows\system32\MSVCR100.dll LoadedModule[168]=C:\Squawkbox\sbtrans10.dll LoadedModule[169]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll LoadedModule[170]=C:\Squawkbox\sbaicontrol10.dll LoadedModule[171]=C:\Squawkbox\sbmod10.dll LoadedModule[172]=C:\FSX\PMDG\DLLs\PMDGOptions.dll LoadedModule[173]=C:\FSX\PMDG_SimConnect_Ldr.dll LoadedModule[174]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll LoadedModule[175]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll LoadedModule[176]=C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dll LoadedModule[177]=C:\Windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_49768ef57548175e\MFC90ENU.DLL LoadedModule[178]=C:\FSX\PMDG\DLLs\PMDGEvents.dll LoadedModule[179]=C:\FSX\PMDG\DLLs\PMDGSounds.dll LoadedModule[180]=C:\FSX\WaveLib.dll LoadedModule[181]=C:\Windows\SysWOW64\ieframe.dll LoadedModule[182]=C:\Windows\system32\Secur32.dll LoadedModule[183]=C:\Windows\system32\dnsapi.DLL LoadedModule[184]=C:\Windows\SysWOW64\mshtml.dll LoadedModule[185]=C:\Windows\system32\msimtf.dll LoadedModule[186]=C:\Windows\system32\msls31.dll LoadedModule[187]=C:\Windows\system32\d2d1.dll LoadedModule[188]=C:\Windows\system32\DWrite.dll LoadedModule[189]=C:\Windows\system32\D3D10Warp.dll LoadedModule[190]=C:\Windows\system32\MLANG.dll LoadedModule[191]=C:\FSX\GAUGES\PMDG_747400_Main.DLL LoadedModule[192]=C:\FSX\TCAS2v7.dll LoadedModule[193]=C:\FSX\GAUGES\PMDG_747400_ACS.DLL LoadedModule[194]=C:\FSX\GAUGES\PMDG_747400_Overhead.DLL LoadedModule[195]=C:\FSX\GAUGES\PMDG_747400_Center.DLL LoadedModule[196]=C:\Windows\system32\d3dx9_31.dll Sec[0].Key=LCID Sec[0].Value=1033 FriendlyEventName=Stopped working ConsentKey=APPCRASH AppName=Microsoft® Flight Simulator X AppPath=C:\FSX\fsx.exe Chuck Biggins
January 2, 201313 yr http://forum.avsim.net/topic/355100-g3ddll-workaroundfix-to-prevent-fsx-crashes/ This completely fixed the issue for me...... Regards AMD Ryzen 7800x3d, Asus ROG Strix RTX4090, Asus x670e-e, G-Skill F5-6000J3038F16GX2-TZ5NR
January 2, 201313 yr yea couldnt agree more, it fixes most ctds that are around I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card, RM850 power supply Peter kelberg
January 2, 201313 yr Pipped to the post! A great many thanks go out to Peter Dowson, and I think Word Not Allowed, for their sterling efforts in bringing this to the simming community. I too have not had a g3d.dll crash since installing the latest version of FSUIPC. HowardMSI Mag B650 Tomahawk MB, Ryzen7-7800X3D CPU@5ghz, Arctic AIO II 360 cooler, Nvidia RTX4090 GPU, 32gb DDR5@6000Mhz, SSD/2Tb+SSD/500Gb+OS, Corsair 1000W PSU, LG Ultragear 48"4K, MFG Crosswinds, TQ6 Throttle, Fulcrum One YokeMy FlightSim YouTube Channel: https://www.youtube.com/@skyhigh776
January 2, 201313 yr I was about to post the same on the FSUIPC magic, but then I saw that the OP is already running FSUIPC. So there's a slim chance that he has an outdated version (without the g3d.dll fix) or that it isn't installed correctly. Means not running or something. Wrong dll.xml entry, no FSUIPC menu visible in FSX. Therefore, no CTD fix enabled. On another occasion, I could guess that the uiautomationcore.dll spreads out and leads to a CTD. Plenty of options and buzz words delivered. ^_^ To start with. Which FSUIPC is running at your end? Can you see the FSUIPC menu entry in FSX?
January 2, 201313 yr Author -<Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> This is at the bottom of my dll.xml located here: C:\Users\Skynet\AppData\Roaming\Microsoft\FSX I downloaded it a couple days ago. Ver 4.583 is listed in addons. (I do plan on registering the first opportunity I can). I have not done uiautomation due to the skeptics. I have not seen that CTD yet. Can this still be related to uiautomation eventhough its's not listed in the crash reports? Thank you for the suggestions. Edit: Found my install log in FSX\modules ********* FSUIPC4, Version 4.853 by Pete Dowson ********* Running inside FSX on Windows 7 Module base=65E60000 User Name="" User Addr="" FSUIPC4 not user registered WIDEFS7 not user registered, or expired 702 System time = 02/01/2013 03:11:09 702 FLT path = "C:\Users\Skynet\Documents\Flight Simulator X Files\" 733 Trying to connect to SimConnect Acc/SP2 Oct07 ... 733 FS path = "C:\FSX\" 1061 LogOptions=00000000 00000001 1061 Wind smoothing fix is fully installed 1061 G3D.DLL fix attempt installed ok 1061 SimConnect_Open succeeded: waiting to check version okay 1061 Trying to use SimConnect Acc/SP2 Oct07 1903 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 1903 Initialising SimConnect data requests now 1903 FSUIPC Menu entry added 1934 C:\FSX\FLIGHTS\OTHER\FLTSIM.FLT 1934 C:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 98327 System time = 02/01/2013 03:12:47, Simulator time = 03:11:10 (11:11Z) 98577 Starting everything now ... 99669 Advanced Weather Interface Enabled 111712 System time = 02/01/2013 03:13:00, Simulator time = 03:11:13 (11:11Z) 111712 *** FSUIPC log file being closed Average frame rate for running time of 4 secs = 125.1 fps G3D fix: Passes 8481, Null pointers 0, Bad pointers 0, Separate instances 0 Memory managed: 5 Allocs, 5 Freed ********* FSUIPC Log file closed ********* I read the new NVIDIA drivers can "underspeed" the GPU fan. I currently have 310.70. NickN recommended MSI Aferburner to speed them up. Can G3D.dll be caused by 310.70? Thank you Chuck Biggins
January 2, 201313 yr I was about to post the same on the FSUIPC magic, but then I saw that the OP is already running FSUIPC. So there's a slim chance that he has an outdated version (without the g3d.dll fix) or that it isn't installed correctly. Means not running or something. Wrong dll.xml entry, no FSUIPC menu visible in FSX. Therefore, no CTD fix enabled. On another occasion, I could guess that the uiautomationcore.dll spreads out and leads to a CTD. Plenty of options and buzz words delivered. ^_^ To start with. Which FSUIPC is running at your end? Can you see the FSUIPC menu entry in FSX? yea just noticed that but its a unregistered version maybe it needs to be a paid version is the question here? I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card, RM850 power supply Peter kelberg
January 2, 201313 yr Good point. But I recall Pete explaining that the free version also offers the g3d.dll fix. A gift to all users. Makes even more sense to buy it then, supporting the fair policy. Chuck, thanks for posting the details. From the log, FSUIPC is loading and working. Including the fix. You should see a menu in the FSX top bar. By this, I'd say FSUIPC already takes care of the things it can handle. There's a later version available (4.859m), but this may not affect your crashes. http://forum.simflig...pdated-modules/ Well, the uiautomationcore.dll is worth a shot. I saw the crashes showing up as g3d.dll too. Perhaps test it. It only needs to be placed in the FSX folder. No extra steps. If it doesn't work for you, just remove it. It doesn't alter anything on your installation. A hot GPU may indeed be a cause for a g3d.dll log entry. Did you check the temps? We would be talking about unstable levels though, perhaps with occasional driver resets in all kind of games. Seeing e.g. 80°C is not necessarily a warning sign. It really depends on what the GPU model allows. Which model are you running? The bug on the Nvidia drivers with the too low commanded fan speeds goes some months back. I don't recall that one being present on the current WHQL set. And 310.70 is current. Well, you can still check the temps when the card receives some load and look how the fan revs behave. You initial assumption may still prove to be true. Faulty scenery can crash the sim like that. Can you disable all the addon scenery and just fly over default stuff for a while? If it doesn't crash, the lower load and/or the missing 'errors' in the scenery may allow this. So this may need further testing if it really is related to a certain addon of yours. Plenty of testing and 'to look at' items. Sorry. :(
January 2, 201313 yr make sure u use the right uiautomationcore.dll since there are different versions of it not sure whch is the correct version for your pc since i havnt used it as of yet I7-8700k,Corsair h1101 cooler ,Asus Strix Gaming Intel Z370 S11 motherboard, Corsair 32gb ramDD4,, gtx 1080ti Card, RM850 power supply Peter kelberg
January 2, 201313 yr FSUIPC4.dll did not load in the crash report in the OP (or I can't see where it loaded in the OP) even though you said in the OP it was installed. I see in post #6 though you have the log where it just did today (Jan 2nd). In post #6, you state the dll.xml shows - -<Launch.Addon> <Name>FSUIPC 4</Name> <Disabled>False</Disabled> <Path>Modules\FSUIPC4.dll</Path> </Launch.Addon> </SimBase.Document> (all in one line?). If this is all in one line, then the dll.xml is corrupted. Are you still getting the error now that FSUIPC4 appears to have been loaded? I think your problem is fixed now since the FSUIPC is now loading properly. 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
January 2, 201313 yr Author Thank you for your help again! I'm at work now so I'll check it around 0800 GMT. FSUIPC was definitely loaded before my first flight after my reinstall so I ruled that out as being a fix. Jim, I hope what you're saying is correct. I have another crash report from that same day so I'll see if the module loaded on that flight. I did attempt a reinstall of FSUIPC because I do not remember FSX asking me permission to trust the module from simFlight GmbH. It did not ask me the second time either. As far as the dll.xml I'm not sure of the format for spacing, not sure what it is suppose to look like. Can it just be a matter of the way it was copy and pasted into here? Thank you, Chuck Edit: Here is the module from the original APPCRASH report above. LoadedModule[158]=C:\FSX\Modules\FSUIPC4.dll So does this mean it did load? Chuck Biggins
January 3, 201313 yr Edit: Here is the module from the original APPCRASH report above. LoadedModule[158]=C:\FSX\Modules\FSUIPC4.dll So does this mean it did load? I looked several times for that module! It did load and I was completely wrong. Forget about my comments above. There is no known solution to the G3D CTD other than the fix provided with the FSUIPC4 and the developer of the FSUIPC4 just happened to trap the fault and fix it - http://forum.simflight.com/topic/72270-g3ddll/. You will have to trace back to what happened before you started getting this error. Did you install a new program (fsx or any software program made for Windows)? Did you try a system restore prior to the time you received the crash(es)? Your memory settings in your bios may not be correct. ASUS does a lousy job figuring out memory settings when ASUS does one of those automatic overclocks. They'll set your memory frequency to Auto and they will have wrong memory timings. You need to run CPU-Z and look in the Memory tab to see your current settings in the BIOS. Then look over to the SPD tab and check to make sure it matches one of the columns in the Timing Tables. You will manually have to open up the BIOS to check the DRAM Voltage setting but it should be no higher or lower than 1.50. That should be on the AI Tweaker page of your BIOS as well as all of your other memory settings. I see in your PC Specs that you have your system overclocked to 3.8 GHz so I'm thinking that's one of those auto overclocks that ASUS tries to set up for you. Return it to the normal setting until we get this problem fixed. Sorry for missing that loaded module! 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
January 3, 201313 yr Author No problem Jim. The turbo boost is what Intel implements in SB. It is set to 3.4 stock clock with turbo boost enabled in the bios. I'll go ahead and turn that off. I have never heard of anyone having issues with that but these things can be so hard to t/s. This is a fresh hard drive reformat from last Thursday so I do not think I can pinpoint one thing since everything was recently redone. I have my voltages and timings manually set to what G.Skill recommends. I did this right before I reformatted. Thanks again Chuck Chuck Biggins
January 3, 201313 yr All of my G3d.dll g2d.dll, terrain.dll ctds have been because of an unstable Overclock. You mentioned that your CPU is not overclocked and I doubt it's because of turbo. Nonetheless, you should review carefully your BIOS, your memory timings, all settings, and vcore.
January 3, 201313 yr Author I'll definitely do that. I'll set bios back to safe defaults and adjust the memory and timings to G.Skill specs. My memory is G.Skill Ripjaws X 1600 7-8-7-24. I have them set at 1.5 volts but I do read about conflicting reports of them being set to 1.6. These sticks are on the qualified vendor list for my board. I thought SB is 1.5. :unsure: Edit: I think my memory needs to run at 1.6V. I'll open my case up and check the exact model of them in a couple hours and try to find the exact spec. They have always been at 1.5 and I have never had any issues before. Chuck Biggins
Create an account or sign in to comment