g2d.dll crash due to overclock?

[p1muserfan 0]

After a month of fighting constant FSX crashes I went ahead and uninstalled per the PMDG uninstall guide and then reinstalled per the AVSIM guide. I never had these problems on my old machine with XP on it but decided to upgrade because my CPU cooler fan died and I couldn't keep my overclock with the stock fan. I had a I7 920 overclocked to around 3.9 on a EVGA X58 board and it ran great and was as solid as a rock.

My new build is a I5 3570 overclocked to 4.4 on a ASRock Extreme 6 board with 8gb GSkill 8-8-8-24 1.5v memory. My first crash after the FSX reinstall was the g3d.dll variety. No problem, remembered about the FSUIPC fix, upgraded to it, fixed. Or so I thought. Next came the g2d.dll crash. At this point I decided to abandon my overclock and run BIOS default settings.  Ran the same flight again and not a problem 1. However I noticed in CPU-Z that my memory was running at 11-11-11-28, i thought that was strange. I went back into my BIOS and overclocked the CPU to 4.4 again but left the memory at default settings again (11-11-11-28). This time the g2d.dll crash came even quicker than the first time.

So 2 questions. Why does my memory run at 11-11-11-28 unless I go in and manually set the timings to what it's rated at? And is it possible the g2d.ll is related to a bad overclock? Its not a system file its a FSX file, correct? At this point I may just say to heck with it and run this machine at stock, this last 5 weeks have been hell...included is the crash report.

 

 

Version=1
EventType=APPCRASH
EventTime=130149387495470459
ReportType=2
Consent=1
ReportIdentifier=e70e86e2-ce20-11e2-bf0c-bc5ff49c5d19
IntegratorReportIdentifier=e70e86e1-ce20-11e2-bf0c-bc5ff49c5d19
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.61472.0
Sig[2].Name=Application Timestamp
Sig[2].Value=475e17d3
Sig[3].Name=Fault Module Name
Sig[3].Value=g2d.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=10.0.61472.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=475e180c
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=0004374b
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=D:\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]=D:\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\SysWOW64\nvinit.dll
LoadedModule[54]=C:\Windows\WinSxS\x86_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727.6195_none_03ce2c72205943d3\MFC80ENU.DLL
LoadedModule[55]=D:\fsx\language.dll
LoadedModule[56]=D:\fsx\API.DLL
LoadedModule[57]=C:\Windows\WinSxS\x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.6195_none_d09154e044272b9a\MSVCP80.dll
LoadedModule[58]=D:\fsx\ablscpt.dll
LoadedModule[59]=D:\fsx\flight.dll
LoadedModule[60]=D:\fsx\ai_player.dll
LoadedModule[61]=D:\fsx\acontain.dll
LoadedModule[62]=D:\fsx\controls.dll
LoadedModule[63]=C:\Windows\system32\DINPUT8.dll
LoadedModule[64]=D:\fsx\fsui.dll
LoadedModule[65]=D:\fsx\atc.dll
LoadedModule[66]=D:\fsx\facilities.dll
LoadedModule[67]=D:\fsx\demo.dll
LoadedModule[68]=D:\fsx\main.dll
LoadedModule[69]=D:\fsx\fe.dll
LoadedModule[70]=D:\fsx\util.dll
LoadedModule[71]=D:\fsx\simprop.dll
LoadedModule[72]=D:\fsx\g2d.dll
LoadedModule[73]=C:\Windows\system32\d3dx9_34.dll
LoadedModule[74]=C:\Windows\system32\d3dx10_34.dll
LoadedModule[75]=C:\Windows\system32\d3d9.dll
LoadedModule[76]=C:\Windows\system32\d3d8thk.dll
LoadedModule[77]=D:\fsx\g3d.dll
LoadedModule[78]=D:\fsx\panels.dll
LoadedModule[79]=D:\fsx\multiplayer.dll
LoadedModule[80]=D:\fsx\ui.dll
LoadedModule[81]=D:\fsx\sound.dll
LoadedModule[82]=D:\fsx\sim1.dll
LoadedModule[83]=D:\fsx\simscheduler.dll
LoadedModule[84]=D:\fsx\visualfx.dll
LoadedModule[85]=D:\fsx\window.dll
LoadedModule[86]=D:\fsx\terrain.dll
LoadedModule[87]=D:\fsx\weather.dll
LoadedModule[88]=C:\Windows\system32\DSOUND.dll
LoadedModule[89]=C:\Windows\system32\POWRPROF.dll
LoadedModule[90]=D:\fsx\symmap.dll
LoadedModule[91]=C:\Windows\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.17825_none_72d273598668a06b\gdiplus.dll
LoadedModule[92]=C:\Windows\system32\MSIMG32.dll
LoadedModule[93]=D:\fsx\xuipc.dll
LoadedModule[94]=D:\fsx\livingwater.dll
LoadedModule[95]=D:\fsx\fs-traffic.dll
LoadedModule[96]=D:\fsx\gps.dll
LoadedModule[97]=C:\Windows\system32\MSWSOCK.dll
LoadedModule[98]=C:\Windows\system32\SHFOLDER.dll
LoadedModule[99]=C:\Windows\system32\RICHED20.DLL
LoadedModule[100]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[101]=C:\Windows\system32\rsaenh.dll
LoadedModule[102]=C:\Windows\syswow64\WINTRUST.dll
LoadedModule[103]=C:\Windows\syswow64\CRYPT32.dll
LoadedModule[104]=C:\Windows\syswow64\MSASN1.dll
LoadedModule[105]=C:\Windows\syswow64\CLBCatQ.DLL
LoadedModule[106]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[107]=C:\Windows\system32\wbemcomn.dll
LoadedModule[108]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[109]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[110]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[111]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[112]=C:\Windows\WinSxS\x86_microsoft.msxml2_6bd6b9abf345378f_4.20.9818.0_none_b7e811947b297f6d\MSXML4.DLL
LoadedModule[113]=C:\Windows\system32\dxgi.dll
LoadedModule[114]=C:\Windows\system32\nvd3dum.dll
LoadedModule[115]=C:\Windows\syswow64\PSAPI.DLL
LoadedModule[116]=C:\Windows\system32\D3DCompiler_34.dll
LoadedModule[117]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[118]=C:\Windows\system32\d3d10_1.dll
LoadedModule[119]=C:\Windows\system32\d3d10_1core.dll
LoadedModule[120]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI.dll
LoadedModule[121]=C:\Windows\SysWOW64\dxdiagn.dll
LoadedModule[122]=C:\Windows\SysWOW64\d3d10.dll
LoadedModule[123]=C:\Windows\SysWOW64\d3d10core.dll
LoadedModule[124]=C:\Windows\SysWOW64\d3d11.dll
LoadedModule[125]=C:\Windows\system32\winbrand.dll
LoadedModule[126]=C:\Windows\system32\nvapi.dll
LoadedModule[127]=C:\Windows\system32\WTSAPI32.DLL
LoadedModule[128]=C:\Windows\system32\WINSTA.dll
LoadedModule[129]=C:\Windows\SysWOW64\gameux.dll
LoadedModule[130]=C:\Windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\COMCTL32.dll
LoadedModule[131]=C:\Windows\SysWOW64\XmlLite.dll
LoadedModule[132]=C:\Windows\SysWOW64\wer.dll
LoadedModule[133]=C:\Windows\System32\Wpc.dll
LoadedModule[134]=C:\Windows\System32\wevtapi.dll
LoadedModule[135]=C:\Windows\System32\msxml6.dll
LoadedModule[136]=C:\Windows\system32\SAMLIB.dll
LoadedModule[137]=C:\Windows\system32\netutils.dll
LoadedModule[138]=D:\fsx\uiautomationcore.dll
LoadedModule[139]=C:\Windows\system32\OLEACC.dll
LoadedModule[140]=C:\Windows\System32\MMDevApi.dll
LoadedModule[141]=C:\Windows\System32\PROPSYS.dll
LoadedModule[142]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[143]=C:\Windows\system32\HID.DLL
LoadedModule[144]=C:\Windows\system32\XInput9_1_0.dll
LoadedModule[145]=C:\Windows\system32\wdmaud.drv
LoadedModule[146]=C:\Windows\system32\ksuser.dll
LoadedModule[147]=C:\Windows\system32\AVRT.dll
LoadedModule[148]=C:\Windows\system32\msacm32.drv
LoadedModule[149]=C:\Windows\system32\midimap.dll
LoadedModule[150]=C:\Windows\system32\dinput.DLL
LoadedModule[151]=C:\Windows\SysWOW64\pid.dll
LoadedModule[152]=C:\Windows\System32\wship6.dll
LoadedModule[153]=C:\Windows\System32\wshtcpip.dll
LoadedModule[154]=D:\fsx\bglmanx.dll
LoadedModule[155]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.61259.0_none_55f5ecdc14f60568\SimConnect.dll
LoadedModule[156]=C:\Windows\system32\inetmib1.dll
LoadedModule[157]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[158]=C:\Windows\system32\WINNSI.DLL
LoadedModule[159]=C:\Windows\system32\snmpapi.dll
LoadedModule[160]=C:\Program Files (x86)\AFX\AFXModuleFSX.dll
LoadedModule[161]=C:\Windows\WinSxS\x86_microsoft.flightsimulator.simconnect_67c7c14424d61b5b_10.0.60905.0_none_dd92b94d8a196297\SimConnect.dll
LoadedModule[162]=D:\fsx\PMDG\DLLs\PMDG_HUD_interface.dll
LoadedModule[163]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
LoadedModule[164]=C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll
LoadedModule[165]=C:\Windows\system32\mfc100.dll
LoadedModule[166]=C:\Windows\system32\MSVCR100.dll
LoadedModule[167]=C:\Windows\system32\MSVCP100.dll
LoadedModule[168]=C:\Windows\system32\MFC100ENU.DLL
LoadedModule[169]=C:\Windows\system32\ntmarta.dll
LoadedModule[170]=C:\Windows\syswow64\WLDAP32.dll
LoadedModule[171]=D:\fsx\PMDG\DLLs\PMDGOptions.dll
LoadedModule[172]=D:\fsx\PMDG_SimConnect_Ldr.dll
LoadedModule[173]=C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCP90.dll
LoadedModule[174]=C:\Windows\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_4bf7e3e2bf9ada4c\mfc90.dll
LoadedModule[175]=C:\Windows\WinSxS\x86_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_49768ef57548175e\MFC90ENU.DLL
LoadedModule[176]=D:\fsx\PMDG\DLLs\PMDGEvents.dll
LoadedModule[177]=D:\fsx\PMDG\DLLs\PMDGSounds.dll
LoadedModule[178]=D:\fsx\WaveLib.dll
LoadedModule[179]=D:\fsx\Modules\LVLD.dll
LoadedModule[180]=D:\fsx\Level-D Simulations\B767-300\leveld.dll
LoadedModule[181]=D:\fsx\Captain_Sim\Captain_Sim.b757.menu.dll
LoadedModule[182]=D:\fsx\Modules\FSUIPC4.dll
LoadedModule[183]=C:\Program Files (x86)\FSForce 2\FSForce.dll
LoadedModule[184]=C:\Windows\SysWOW64\ieframe.dll
LoadedModule[185]=C:\Windows\system32\Secur32.dll
LoadedModule[186]=C:\Windows\system32\dnsapi.DLL
LoadedModule[187]=C:\Windows\SysWOW64\mshtml.dll
LoadedModule[188]=C:\Windows\system32\msimtf.dll
LoadedModule[189]=C:\Windows\system32\msls31.dll
LoadedModule[190]=C:\Windows\system32\d2d1.dll
LoadedModule[191]=C:\Windows\system32\DWrite.dll
LoadedModule[192]=C:\Windows\system32\D3D10Warp.dll
LoadedModule[193]=C:\Windows\system32\MLANG.dll
LoadedModule[194]=D:\fsx\GAUGES\PMDG_737NGX.DLL
LoadedModule[195]=C:\Windows\system32\NETAPI32.dll
LoadedModule[196]=C:\Windows\system32\srvcli.dll
LoadedModule[197]=C:\Windows\system32\wkscli.dll
LoadedModule[198]=C:\Windows\system32\WSOCK32.dll
LoadedModule[199]=C:\Windows\SysWow64\XAudio2_5.dll
LoadedModule[200]=D:\fsx\GAUGES\PMDG_737NGX_3.DLL
LoadedModule[201]=D:\fsx\Gauges\PMDG_737NGX_2.dll
LoadedModule[202]=C:\Windows\system32\NLAapi.dll
LoadedModule[203]=C:\Windows\system32\napinsp.dll
LoadedModule[204]=C:\Windows\system32\pnrpnsp.dll
LoadedModule[205]=C:\Windows\System32\winrnr.dll
LoadedModule[206]=C:\Windows\System32\fwpuclnt.dll
LoadedModule[207]=C:\Windows\system32\rasadhlp.dll
LoadedModule[208]=C:\Windows\system32\icmp.Dll
LoadedModule[209]=C:\Windows\system32\d3dx9_31.dll
LoadedModule[210]=C:\Windows\system32\msadp32.acm
Sec[0].Key=LCID
Sec[0].Value=1033
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft® Flight Simulator X
AppPath=D:\FSX\fsx.exe
 

[lodestar 186]

What temperatures you have with FSX? Have you updated your video drivers recently? 

[Jim Young 2,356]

The g2d.dll handles plain text messages, like the frame rate counter and those other plain text messages you see periodically while running FSX, including plain text words in the FSX Menu, like the words "Options, View", etc.  There may be something corrupted in the dll.xml which loads menu items.

 

Best regards,

Jim

[p1muserfan 0]

My temps under load never exceed 65, water cooled. I'm running driver 306.97 which gave me zero issues on my previous build

Pretty familiar with the dll.xml file, how to get to it anyway. how would I check for corruption? Here's a copy of it:

 

 

<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
  <Descr>Launch</Descr>
  <Filename>dll.xml</Filename>
  <Disabled>False</Disabled>
  <Launch.ManualLoad>False</Launch.ManualLoad>
  <Launch.Addon>
    <Name>Addon Manager</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>bglmanx.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>AFXModule</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>C:\Program Files (x86)\AFX\AFXModuleFSX.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Object Placement Tool</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>..\Microsoft Flight Simulator X SDK\SDK\Mission Creation Kit\object_placement.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Traffic Toolbox</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Traffic Toolbox SDK\traffictoolbox.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Visual Effects Tool</Name>
    <Disabled>True</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>..\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Special Effects SDK\visualfxtool.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG HUD interface</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDG_HUD_interface.dll</Path>
    <DllStartName>module_init</DllStartName>
    <DllStopName>module_deinit</DllStopName>
  </Launch.Addon>
  <Launch.Addon>
    <Name>IvAp</Name>
    <Disabled>False</Disabled>
    <Path>C:\Program Files (x86)\IVAO\IvAp v2\ivap_fsx_bootstrap.dll</Path>
    <Commandline></Commandline>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG Options</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDGOptions.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG Events</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDGEvents.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>PMDG Sounds</Name>
    <Disabled>False</Disabled>
    <Path>PMDG\DLLs\PMDGSounds.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Level-D Simulations</Name>
    <Disabled>False</Disabled>
    <ManualLoad>False</ManualLoad>
    <Path>Modules\LVLD.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>Captain Sim Menu</Name>
    <Disabled>False</Disabled>
    <Path>Captain_Sim\Captain_Sim.b757.menu.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSUIPC 4</Name>
    <Disabled>False</Disabled>
    <Path>Modules\FSUIPC4.dll</Path>
  </Launch.Addon>
  <Launch.Addon>
    <Name>FSForce DLL</Name>
    <Disabled>false</Disabled>
    <ManualLoad>false</ManualLoad>
    <Path>C:\Program Files (x86)\FSForce 2\FSForce.dll</Path>
  </Launch.Addon>
</SimBase.Document>
 

[lodestar 186]

http://support.precisionmanuals.com/KB/a92/dllxml-information-and-troubleshooting.aspx

 

Something has changed with automatic updates for Nvidia drivers, it can be updated autonatically even if you have that option disabled, it's good to check

[Jim Young 2,356]

 

 

My new build is a I5 3570 overclocked to 4.4

 

How were you able to OC a locked CPU to 4.4GHz?  Maybe you forgot to add the 'K' at the end which means it is unlocked.

 

 

 

So 2 questions. Why does my memory run at 11-11-11-28 unless I go in and manually set the timings to what it's rated at? And is it possible the g2d.ll is related to a bad overclock?

 

You are probably trying to run your memory at lower timings/voltages.  I would not recommend that if you are overclocking.  It appears the memory timing controls of 11-11-11-28 are correct.  These are the XMP Profile 1 or 2 settings for your installed memory modules (not all have two profiles).  The problem might be what the proper voltage you have set.  XMP profiles usually require a higher voltage setting than the others.  In your ASRock UEFI Utility under the OC Tweaker, you should see the XMP profiles listed on Page 2 of the OC Tweaker.  You want to make sure the frequency, the timing controls, the DRAM Voltage is what is shown under the SPD Tab of the CPU-Z (far right profile)(do not look under the Memory Tab).  You do not want to have the JEDEC Profile.

 

You probably have seen it but here is a great overclocking guide for your board - http://www.overclock.net/t/1198504/complete-overclocking-guide-sandy-bridge-ivy-bridge-asrock-edition.

 

Best regards,

Jim

[p1muserfan 0]

Jim

 

After reading one of your suggestions to someone else about installing the service packs for the pmdg 737, I realized I hadn't done it either. Since the g2d.dll is an fsx file and not a system file, could that be the reason for the crashes and not so much the overclock?

[Jim Young 2,356]

No (but you still should install those service packs for the PMDG 737).  As I stated before, the g2d.dll is used for plain text messages in FSX.  The g2d.dll may not have been the fault of your crash but was being called by FSX when something else happened to your system.  But, if it is showing as the faulting module in all crashes, then it is most like the cause of your crash.  It was updated in SP2.  You have SP2 installed so I would uninstall SP2, run fsx, then reinstall SP2.  You do this by double-clicking on the SP2.exe and then selecting uninstall or remove as the option.  This way you'll still have FSX w/SP1 installed.  Make sure you run FSX before reinstalling.  If that doesn't work, then I would uninstall SP1 by doing the same thing.  Some people who have uninstalled SP2, ran FSX, then reinstalled it have fixed their problem by doing these procedures.  Unfortunately, PMDG737 will not run without SP2 or Acceleration installed (me thinks) so don't try to load that aircraft.  Just load a default aircraft, shut down fsx, then reinstall.

 

Best regards,

Jim

[Cai Zicheng 171]

Hi,

An unstable OC does lead to g2d.dll crash. I had that problem constantly at OC 4.5GHz and it was all fine at OC 4.3.

[p1muserfan 0]

Well, I think this is definitely overclock related. Installed the 737 service packs,went back to my overclock setings and had a panels.dll crash. Went back to BIOS default settings, flew the same flight, no problems. Jim, I think I read in one of your many posts to someone that if the overclock is unstable, the crash can come from anywhere. I think this is the case with my problem. Honestly, between default settings (it still runs at 3.8 with turbo) and removing the bufferpools entry completely I'm experiencing a pretty smoooth sim, no more micro stutters at all. At some point I'll revisit the overclocking thing but for now I just want to fly!

[Jim Young 2,356]

I really think it is your installed memory settings in the BIOS.  Wrong settings, too low or too high voltages will cause a lot of unexplained issues as it did for me when I first built my current system.

 

I do agree though that you should forget about overclocking your system right now and get it stable first.  Once stable and no more crashes, then start the overclocking process again.

 

I wish I could sit here and say that the g2d.dll ctd was caused by a bad overclock.  There are so many variables involved.  But the fact that the g2d ctd went away when you brought your system back to the default is an indicator it might have been the cause.

 

Best regards,

Jim

[p1muserfan 0]

Well, i may have found a minor problem, my memory was running in single channel mode, had one of the sticks in the wrong slot. However, before I discovered the problem I was able to overclock with more VCore up to 4.5 with Prime95 for an hour with no errors. But then after I rebooted my machine was as unstable as all get out. The USB port for my joy stick no longer worked, programs would never open, stuff like that. I did check the speed of the memory under the speed tab of CPU-Z and it did show the XMP profile and the timings were per spec. It may have to do with running the Vcore with offset voltage as opposed to fixed, I noticed that the majority of forum posters of the overclocking guide for my board at Overclock.net use fixed, that may just be more stable.  

[Jim Young 2,356]

So, do you have it up and running again without any problems after reinstalling your memory?  I personally think Prime95 is aged and you would be better off with maybe the IntelBurnTest but then I also ran Prime95 and Intel Burn Test several times after setting up my system a couple of years ago and both tests passed with flying colors.  I ran FSX, and it crashed and, in my case, I had to manually set up my freq/timings/voltages for the XMP profile.  I understand now that if you set up the XMP profile for your Overclock, it will automatically set up the XMP profile required for your memory.

 

Hope you have everything back up and running again.

 

Best regards,

Jim