Hi everyone,I was flying today with the Jetstream and I was on a 10 mile final for KBUR from KLAS. I got a CTD and I was wondering if anyone else has seen this happen.There were 2 errors. I don't know if it was related to the Jetstream or what it was. My specs are in my sig. I was back to stock clocks at this time. I have uiautomation, Bojote's tuning tool, and Ryan's Nvidia tweaks. No addon scenery. I was on VATSIM at the time. Very frustrating, was 5 minutes from shutting down. ugh! Any thoughts or ideas are appreciated.Here is my report from event viewer.Log Name: ApplicationSource: Application ErrorDate: 4/20/2011 1:09:10 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: SkyNetDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba58Exception code: 0xc0000005Fault offset: 0x0002e3fbFaulting process id: 0xec8Faulting application start time: 0x01cbff86bf798a49Faulting application path: C:\FSX\fsx.exeFaulting module path: C:\Windows\SysWOW64\ntdll.dllReport Id: 0d36e584-6b8a-11e0-ab55-bcaec576077cEvent Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-04-20T20:09:10.000000000Z" /> <EventRecordID>5268</EventRecordID> <Channel>Application</Channel> <Computer>SkyNet</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>ntdll.dll</Data> <Data>6.1.7601.17514</Data> <Data>4ce7ba58</Data> <Data>c0000005</Data> <Data>0002e3fb</Data> <Data>ec8</Data> <Data>01cbff86bf798a49</Data> <Data>C:\FSX\fsx.exe</Data> <Data>C:\Windows\SysWOW64\ntdll.dll</Data> <Data>0d36e584-6b8a-11e0-ab55-bcaec576077c</Data> </EventData></Event>Log Name: ApplicationSource: Application ErrorDate: 4/20/2011 1:09:14 PMEvent ID: 1000Task Category: (100)Level: ErrorKeywords: ClassicUser: N/AComputer: SkyNetDescription:Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14Faulting module name: terrain.dll, version: 10.0.61637.0, time stamp: 0x46fadb59Exception code: 0xc0000005Fault offset: 0x0005595eFaulting process id: 0xec8Faulting application start time: 0x01cbff86bf798a49Faulting application path: C:\FSX\fsx.exeFaulting module path: C:\FSX\terrain.dllReport Id: 1003a493-6b8a-11e0-ab55-bcaec576077cEvent Xml:<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2011-04-20T20:09:14.000000000Z" /> <EventRecordID>5270</EventRecordID> <Channel>Application</Channel> <Computer>SkyNet</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61637.0</Data> <Data>46fadb14</Data> <Data>terrain.dll</Data> <Data>10.0.61637.0</Data> <Data>46fadb59</Data> <Data>c0000005</Data> <Data>0005595e</Data> <Data>ec8</Data> <Data>01cbff86bf798a49</Data> <Data>C:\FSX\fsx.exe</Data> <Data>C:\FSX\terrain.dll</Data> <Data>1003a493-6b8a-11e0-ab55-bcaec576077c</Data> </EventData></Event>

Chuck, do you have the himemfix statement in your fsx.cfg? HIMEMFIX=1 goes in the <Display> section. See also many other CTD threads here using search.Perhaps a computer named SkyNet should not be allowed to run too reliably?

Hi Dan!I found the CTD Forum right after I posted here. I did do a search for about an hour but had nothing to really go off of other than rebuild my fsx.cfg. I will check to see if I have the HIMEMFIX=1 when I get home tonight. The only .cfg tweaks I did was with Bojote's Tweaking and Tuning Tool.Appreciate the suggestion.Looks like John Conner found me and is planning his attack through FSX!

That's hilarious, "Skynet" haha... hopefully it does not become self-aware on you next. The crash is happening in ntdll.dll - this is one of the fundamental Windows kernel files. Usually that indicates generalized system instability. Are you overclocked at all? If so, that's where I'd start looking - remove the OC and see if it goes away - if it does, then you know that's the issue - you'll have to increase CPU voltage most likely to gain stability at whatever speed you're at.