I have posted in the ctd forum as well, but this question is an offshoot. I have started getting CTD's, something i have never had before, i think a lot relate to my install of reality XP gauge, but I am also getting some referencing the fault as ntdll.dll.Does this denote a hardware or software issue ? I just need pointing in the right direction to track the culprit down. I am weighing up another fresh install and if I can avoid it it would be good.....thx, Mark

I have posted in the ctd forum as well, but this question is an offshoot. I have started getting CTD's, something i have never had before, i think a lot relate to my install of reality XP gauge, but I am also getting some referencing the fault as ntdll.dll.Does this denote a hardware or software issue ? I just need pointing in the right direction to track the culprit down. I am weighing up another fresh install and if I can avoid it it would be good.....thx, Mark

Mark,It's been my experience with ntdll.dll crashes in FSX that they are a sign of an unstable overclock, sometimes it could be due to a corrupt scenery or texture file. No amount of stress testing will stress your system in the way FSX does. The first thing I would recommend is loosening your memory timings (try 8,8,8,24 and or drop your memory speed) or revert to standard system settings with no overclocking and see if the problem persists.Regards,Bob

If your maximum texture resolution is 4096x4096, try using DXT5 clouds, or limiting the TEXTURE_MAX_LOAD to 1024.

I have posted in the ctd forum as well, but this question is an offshoot. I have started getting CTD's, something i have never had before, i think a lot relate to my install of reality XP gauge, but I am also getting some referencing the fault as ntdll.dll.Does this denote a hardware or software issue ? I just need pointing in the right direction to track the culprit down. I am weighing up another fresh install and if I can avoid it it would be good.....thx, Mark

MarkAnother thought:One thought is that somehow the ntdll.dll used in FSX located in the WinSxS folder has become corrupted. It can happen in a variety of ways and it is not easy to fix any errors in this folder. One option might be to run VSP1CLN.exe which came with Vista SP1. This tends to remove clutter in the WinSxS folder but do read here first: http://blogs.technet.com/askcore/archive/2...t-so-large.aspx.This is a shot in the dark so I don't guarantee anything but I do see that most errors we get with FSX seem to have a root in the WinSxS folder.RegardsPeterH

Your registry may have gotten corrupted too. I would run a registry cleaner and see if that fixes the problem.Best regards,Jim Young

Thanks, i will try reducing the memory settings a bit. Out of interest are there any decent registry cleaners for 64 bit operating systems? cheers, Mark

Thanks, i will try reducing the memory settings a bit. Out of interest are there any decent registry cleaners for 64 bit operating systems? cheers, Mark

I use the free Advanced System Care which was designed for both the 32 and 64 bit systems: http://www.iobit.com/Best regards,Jim Young