I have issues with ntdll.dll, but only after closing a session with Airbus X. I know it probably has been beaten to death, but any ideas?ThanksGraham

If it only happens with the AirbusX, then there's something wrong with the installation of the Airbus. It's probably looking for a module or texture and it's not there. Just guessing though. Try uninstalling the Airbus and reinstalling it. Make sure you have UAC disabled and any anti-virus program disabled too.Best regards,Jim

Arrrrrrrrrg! As my engines on the 739NGX was spooling down after a flight to LHR, the ntdll.dll caused a CTD. First time it happened to me (and my third CTD since i bought this PC in july).Before I posted this I read this thread and did not get wiser, Im not good at computers. My system has been running pretty much flawlessly, BUT, before this flight I did do some changes here and there.First off I installed SP1b from PMDG updating my NGXI then ran my cfg through Bojotes online cfg wiz and replaced my cfg (which also was run through the same earlier this autnum)I went to my Nvidia control panel and changed my Anti-aliasing settings according to Bojotes tips (transparency off etc)Lastly (and heres what I think may have triggered it) I OC`ed my CPU via Asus AI suite II by pressing "fast" and the PC rebooted and I was told it was successful... (<-- I may just have been a moron for doing that :( )Now, I did not get the crash until the end of the flight however, but that might not have anything to say or..?An update: I ran memtest and got one error: copying between 701dc10 and 701db34Win7 64intel I5 2500KGTX560 TiAsus X67 pro8GB of Corsair 1333MhzProblemsignatur: Navn på problemhendelse: APPCRASH Programnavn: fsx.exe Programversjon: 10.0.61637.0 Tidsstempel for program: 46fadb14 Navn på feilmodul: ntdll.dll Feilmodulversjon: 6.1.7601.17514 Tidsstempel for feilmodul: 4ce7ba58 Unntakskode: c0000005 Unntaksforskyvning: 0003a6a7 OS-versjon: 6.1.7601.2.1.0.768.3 ID for nasjonal innstilling: 1044 Tilleggsinformasjon 1: e8ad Tilleggsinformasjon 2: e8adce1c2b9e7be834b4063ac3c53863 Tilleggsinformasjon 3: e8ad Tilleggsinformasjon 4: e8adce1c2b9e7be834b4063ac3c53863

Now, I did not get the crash until the end of the flight however, but that might not have anything to say or..?An update: I ran memtest and got one error: copying between 701dc10 and 701db34Win7 64intel I5 2500KGTX560 TiAsus X67 pro8GB of Corsair 1333Mhz

As I stated earlier, this error is primarily caused by incorrect memory settings in the bios. You may need to bring in a computer professional to correct those settings or, if you have a setting in your bios that brings the bios settings back to the default, you can try that. If you are crashing near the end of a long flight I would suspect overheating of the CPU or memory.Best regards,Jim

As I stated earlier, this error is primarily caused by incorrect memory settings in the bios. You may need to bring in a computer professional to correct those settings or, if you have a setting in your bios that brings the bios settings back to the default, you can try that. If you are crashing near the end of a long flight I would suspect overheating of the CPU or memory.Best regards,Jim

I spent several hours yesterday reading about similar faults. I suspect that my settings may have overheated the memory. My CPU has a water cooling system which generate superb temps on the CPU (Got like 40-50 centigrades on 4.5 GHz.)I went in to BIOS and reduced clock speed from 1648 to 1333 Mhz on the DDR3 and ran memtest afterwards even longer then the first round, without getting errors. Have not flown since, so ill have to wait till tonight and see what happens next.I think ur very correct regarding memory overheating.

About this ntdll.dll crash most happened with OC,if you has OC try to decrease OC number.

Alright folks! It happened again, at the EXACT same point. I did a replica of the flight and as engines where spooling down at LHR again, it happened when i pushed the open door button, with fspassengers deboarding.FSX crashed last time exactly when i opened the doors and fspassengers began deboarding, so this does not look like overheating. This time i did not overclock anything.. so what is this..?CPU temp was 32 celsius 10 seconds after crash..Update: Now, an hour later, i repeated the flight in the exact same manner as the two previous sessions.. and guess what? No crash.. I hate it when its like this.. Navn på problemhendelse: APPCRASH Programnavn: fsx.exe Programversjon: 10.0.61637.0 Tidsstempel for program: 46fadb14 Navn på feilmodul: ntdll.dll Feilmodulversjon: 6.1.7601.17514 Tidsstempel for feilmodul: 4ce7ba58 Unntakskode: c0000005 Unntaksforskyvning: 0003a6a7 OS-versjon: 6.1.7601.2.1.0.768.3 ID for nasjonal innstilling: 1044 Tilleggsinformasjon 1: e8ad Tilleggsinformasjon 2: e8adce1c2b9e7be834b4063ac3c53863 Tilleggsinformasjon 3: e8ad Tilleggsinformasjon 4: e8adce1c2b9e7be834b4063ac3c53863

I'm beginning to see a trend with this one after a couple trouble-shoot flights.It comes down strictly to addons:-If I do a flight with FSPassengers, the NGX, Active Sky, FSDreamTeam Sceneries and Radar Contact I will get an NTDLL.DLL Crash within 1 minute.-If I do a flight with FSPax, NGX, Active Sky, FSDreamTeam Sceneries and no Radar Contact I will get a NTDLL.DLL crash during rapid view changes on the ground or at any moment during taxi.-If I do a flight with FSPax, NGX, Active Sky, and no FSDreamTeam Sceneries and no Radar Contact I will get an NTDLL.DLL crash only during pushback, and it won't always occur.-Finally, if I do a flight with NO FSPax, or NO NGX, or NO Active Sky, I will never encounter an NTDLL.DLL crash.This is my experience* after several flights using the exact same save starting at FSDreamTeam's ORD, same weather setting from Active Sky, doing a pushback and flight to FlyTampa's Tampa Intl. I can not reproduce an ntdll.dll crash if I don't use the NGX, or if I don't use FSPassengers, or if I don't use Active Sky. However, any combination of the three seems to give me the crash, and adding other addons like payware scenery and radar contact expedite the crash to the point of a guaranteed CTD.I have no idea why. I will try the suggested fix of deleting my FSX.CFG and lowering my video settings.*Your mileage will vary.

I'm beginning to see a trend with this one after a couple trouble-shoot flights.It comes down strictly to addons:-If I do a flight with FSPassengers, the NGX, Active Sky, FSDreamTeam Sceneries and Radar Contact I will get an NTDLL.DLL Crash within 1 minute.-If I do a flight with FSPax, NGX, Active Sky, FSDreamTeam Sceneries and no Radar Contact I will get a NTDLL.DLL crash during rapid view changes on the ground or at any moment during taxi.-If I do a flight with FSPax, NGX, Active Sky, and no FSDreamTeam Sceneries and no Radar Contact I will get an NTDLL.DLL crash only during pushback, and it won't always occur.-Finally, if I do a flight with NO FSPax, or NO NGX, or NO Active Sky, I will never encounter an NTDLL.DLL crash.This is my experience* after several flights using the exact same save starting at FSDreamTeam's ORD, same weather setting from Active Sky, doing a pushback and flight to FlyTampa's Tampa Intl. I can not reproduce an ntdll.dll crash if I don't use the NGX, or if I don't use FSPassengers, or if I don't use Active Sky. However, any combination of the three seems to give me the crash, and adding other addons like payware scenery and radar contact expedite the crash to the point of a guaranteed CTD.I have no idea why. I will try the suggested fix of deleting my FSX.CFG and lowering my video settings.*Your mileage will vary.

Good assessment. The fact you are getting the crash at FSDT KORD and with the NGX indicates your sliders are way too high for your system. These are two programs that require a lot of CPU and GPU power. You cannot run FSX with all sliders to the right, especially in the AI section. For what it's worth, I have flown out of FSDT KORD to KSTL several times in the NGX with AS2012 enabled and Shade. I have never suffered a crash. Deleting the FSX.cfg will only move your sliders back to what Microsoft thought was best for your system. That's why you won't get a crash after rebuilding your fsx.cfg. It's only when you start moving those sliders way too high or pushing the LOD Radius above the FSX max of 4.5 will you start seeing problems with your system.Best regards,Jim

Jim,Do you think buying a new GPU would allow me to up my sliders without running into problems? I understand every system is different and you can't guarantee changing any hardware will fix my crashes (especially considering this is a 32 bit game from 2005) but considering there is a direct correlation between my crashes and my number of addons/slider settings would upgrading be a good idea? The guys over at PMDG stated, once, that using a GPU with 2GB of memory was a bad idea for FSX because it would be using memory FSX could use and allocate, or something to that effect. That was really the only reason I stuck with the 9800 GT.

Jim,Do you think buying a new GPU would allow me to up my sliders without running into problems? I understand every system is different and you can't guarantee changing any hardware will fix my crashes (especially considering this is a 32 bit game from 2005) but considering there is a direct correlation between my crashes and my number of addons/slider settings would upgrading be a good idea? The guys over at PMDG stated, once, that using a GPU with 2GB of memory was a bad idea for FSX because it would be using memory FSX could use and allocate, or something to that effect. That was really the only reason I stuck with the 9800 GT.

I believe so. My sliders are not at max though with the GTX580. I have never heard of anyone successfully running at max without eventually having an issue like a CTD or freeze. I still get great graphics though. FSX is more CPU dependent than the GPU. In FS9 it was the opposite. But a good GPU in the 4 or 5 series is still a good idea as they work more efficiently. You might want to check out some of the posts in the Hardware forum here at AVSIM where they discuss things like this.Best regards,Jim

For FSX and 9800GT i would go for the old WHQL 257.21, it's a legend driver in my eyes. But then you got trouble with BF3, Skyrim. etc. etc. i think, i would say it this way:It's a choice, and that's yours which to choose, the driver that works ok with FSX or the driver that works for BF3 etc....And a link to uninstall\install drivers are here: http://forums.nvidia...howtopic=169555

This is what I found during my research on the g3d.dll CTD:NTDL.dll: Ntdll.dll exports the Windows Native Application Programming Interfaces (API). The Native API is the interface used by user-mode components of the operating system that must run without support from Win32 or other API subsystems. Most of this API is implemented in ntdll.dll and at the upper edge of ntoskrnl.exe (and its variants) (http://en.wikipedia....s_library_files). Pretty complex to someone who doesn't know much about programming interfaces, etc., but I know things about the 'ntoskrnl.exe'. When I first put my system together I got BSOD's with the ntoskrnl.exe program always as the offender. Via Google, I learned any error with the ntoskrnl.exe program indicates there's something wrong with the installed memory. It could be timing, frequencies, wrong speed setting, memory not seated properly, overclocked, or the BIOS not identifying it correctly and providing the wrong settings. There could be other problems but it all has to do with your memory settings. I have my BIOS set up with XMP profile and that indicated the profile would manage my memory settings. I went back into my BIOS and saw that the Memory Frequency for my Muskin memory was set at DDR3-1333. CPU-Z indicated the speed for XMP should be 1600 so I change the Memory Frequency from DDR3-1333 to DDR3-1600. So much for XMP settings managing my memory settings!!!So changing the memory settings fixed the problem for me. It has nothing to do with graphics or FSX.Best regards,Jim

Hi again.I don't give up so easy on this one.Ok, ram have some influence on this ntdll.dll crash but i also look back at driver issues, i have tried several drivers and with several of them i sometimes get ntdll.dll fault, but when i get back to this old driver 257.21 WHQL driver, i never had this issue, so it must have something to do with drivers also, not only ram, timings and bios setup.Just my thought's.

ARGH! For several flights ive been without this stupid fault, but here it comes AGAIN!! I dont get this at all!It happens at the same part of the flight every single time, and thats after engine shutdown, whilst FSpassengers is running and im still pushing buttons.. stupid ntdll.dll, i hate you!It does not matter how long the flights last, 30 mins or 11 hours, it happens at random.. It happens at both add-on and non add-on airports.. However, its only been with the 737 NGX.. dont know if that might be it?

ARGH! For several flights ive been without this stupid fault, but here it comes AGAIN!! I dont get this at all!It happens at the same part of the flight every single time, and thats after engine shutdown, whilst FSpassengers is running and im still pushing buttons.. stupid ntdll.dll, i hate you!It does not matter how long the flights last, 30 mins or 11 hours, it happens at random.. It happens at both add-on and non add-on airports.. However, its only been with the 737 NGX.. dont know if that might be it?

The ASUS BIOS and their ASUS AI Suite program that overclocks your system from the desktop is filled with bugs. It does not work or very, very rarely does it work. If you are relying on those settings that ASUS gave you because everything appeared to be running okay and ASUS said the overclock was successful, then you will get crashes especially if you try to tax or put more system resources on a program such as FSX. I have learned that from personal experiences. System would run great for a few days then a CTD or BSOD. Shutdown, restart, and it would run find for another few days, then crash unexpectantly. I suggest you look at the bios settings for a similar system as yours in the Hardware Forum (there's a pinned topic on displayed bios settings). I use the one put out by SpiritFlyer as he and I have very similar systems. I'm sorry to hear you are still getting ntdl.dll crashes after all the previous suggestions. Unfortunately, there is no magic solution to this problem. It's different in everyone's systems. Just be aware of the facts as I put out earlier in more detail. The NTDL.dll does not belong to FSX and is a Windows 7 file. It manages memory and, when it can't, it crashes a program. Hope this helps and hope you can find a solution to your bios setting soon.Best regards,Jim

The ASUS BIOS and their ASUS AI Suite program that overclocks your system from the desktop is filled with bugs. It does not work or very, very rarely does it work. If you are relying on those settings that ASUS gave you because everything appeared to be running okay and ASUS said the overclock was successful, then you will get crashes especially if you try to tax or put more system resources on a program such as FSX. I have learned that from personal experiences. System would run great for a few days then a CTD or BSOD. Shutdown, restart, and it would run find for another few days, then crash unexpectantly. I suggest you look at the bios settings for a similar system as yours in the Hardware Forum (there's a pinned topic on displayed bios settings). I use the one put out by SpiritFlyer as he and I have very similar systems. I'm sorry to hear you are still getting ntdl.dll crashes after all the previous suggestions. Unfortunately, there is no magic solution to this problem. It's different in everyone's systems. Just be aware of the facts as I put out earlier in more detail. The NTDL.dll does not belong to FSX and is a Windows 7 file. It manages memory and, when it can't, it crashes a program. Hope this helps and hope you can find a solution to your bios setting soon.Best regards,Jim

That the ntdll.dll has with memory managing to do, was actually new to me, so thanks for clearing that up. Did run memtest without stop for i dont know how many days without any faults popping up, so everythings fine now.Thanks for helping out here, I really appreciate it! Im gonna go check the BIOS-settings out, and from now on, stupid ASUS AIsuite isnt gonna touch my CPU!

Im gonna go check the BIOS-settings out, and from now on, stupid ASUS AIsuite isnt gonna touch my CPU!

Agree. I deleted the AI Suite. I just make changes through the BIOS if needed.Best regards,Jim