Frequent FSX Crashes [NGX]

[aceridgey 330]

Hi guys,I have been super unlucky recently, only completing 1/10 flights, it has been super frustrating.At the moment, I just saved my flight before another crash, loaded in again.By clicking "Clr" on my FMC, caused the Flight simulator to freeze immediately/ completely, twice at the same point.AlexP.sMaybe some help or none at all, the faulting module path is "unknown"

[stweaver321 0]

Alex,I think your best bet at getting help with CTDs is to include the application event log showing the crash. If you're running Win7, type "Event Viewer" in the Start menu lookup. In the Event Viewer, go to "Windows Logs-->Application" and find the FSX entries. There should be a Red icon next to the log entry showing that there was an Error. Often times there will be more than one, so find the one that contains Faulting module (e.g., ATC.dll) and copy the contents in your post. If it's always the same module causing your crash, it's easier to narrow down the problem. if you're seeing a variety of modules causing the CTD, then it's probably unstable hardware (e.g., bad RAM or unstable Overclock). There are other common causes of CTDs that can be addressed if you provide the faulting module.

[aceridgey 330]

Alex,I think your best bet at getting help with CTDs is to include the application event log showing the crash. If you're running Win7, type "Event Viewer" in the Start menu lookup. In the Event Viewer, go to "Windows Logs-->Application" and find the FSX entries. There should be a Red icon next to the log entry showing that there was an Error. Often times there will be more than one, so find the one that contains Faulting module (e.g., ATC.dll) and copy the contents in your post. If it's always the same module causing your crash, it's easier to narrow down the problem. if you're seeing a variety of modules causing the CTD, then it's probably unstable hardware (e.g., bad RAM or unstable Overclock). There are other common causes of CTDs that can be addressed if you provide the faulting module.

Thanks for the reply,"""Maybe some help or none at all, the faulting module path is "unknown""" Next time I experience this I will upload itAlex

[stweaver321 0]

FYI, there usually is 2 or 3 error logs created when FSX crashes and often only one of them will identify the faulting module.