I just got my memory settings in the bios set properly after almost a year...Best regards,Jim

JimWill take a look at those too - out of interest, did use a Windows tool to establish the stability of your RAM - e.g., happy to fly the same FSX route, but will not always crash so just wondering if you made use of any other stress testing utils?Just wondering too what you would change first, e.g., voltage by itself, RAM timings etc.?ThanksCarl

JimWill take a look at those too - out of interest, did use a Windows tool to establish the stability of your RAM - e.g., happy to fly the same FSX route, but will not always crash so just wondering if you made use of any other stress testing utils?Just wondering too what you would change first, e.g., voltage by itself, RAM timings etc.?ThanksCarl

Hi Carl,First off, the bad memory settings did not cause my g3d crashes but caused the ntdl.dll CTD after I successfully fixed the g3d CTD. I seriously doubt bad memory settings in the bios cause the g3d CTD's. G3D CTD's are triggered missing objects the g3d.dll is trying to render. That's why I think the smallpartrejectradius tweak has been successful. And, yes, I did several stress tests after setting the evidently wrong values in the bios. I ran the Intel Burn Test Version 2, Prime95, Windows 7 Memory Diagnostics, and the ASUS PC Diagnostic Program. The Intel Burn Test and Prime 95 successfully passed the extreme settings for each program. I had no CTD's for several months. It was just recently that I started getting the g3d CTD's like many others here. With a clean fsx.cfg and the highmemfix and smallpartrejectradius tweaks, I got rid of the g3d CTD's. I have even raised most of my terrain settings to max since I posted my fix for the g3d crash and still no CTD's. I confess I am a novice regarding memory settings. That's why I set my memory settings the same as SpiritFlyer (his bios settings are shown in the Hardware Forum in the pinned bios topic) as he has pretty much the same system as mine. It worked as I got rid of the NTDL errors too. Thanks for your interest.Best regards,Jim