Hey guys,Is there a known fix for crashes related to ntdll.dll? I want to play flight simulator, but the thought of doing all the work to create a flight plan, do the preflight & FMC, set up all the appropriate programs (FS2Crew, Radar Contact, Active Sky, etc) only to have a CTD because of ntdll.dll during pushback or taxi kills any urge I had to play the game. This morning, after wasting an hour on all the appropriate preflight-to-taxi steps and procedures I had my third CTD caused by ntdll.dll out of the four flights I've attempted in recent months.It's tiresome.I took a glance at google and the rest of the avsim forums, but didn't really find anything concrete about ntdll.dll (except that it's an illusive CTD) and most of the topics on it here on avsim had some suggestions that were a couple credit hours above my head (Like changing the ram voltage in my bios, or something complex to a novice) - has anyone encountered the problem and been successful in fixing it? Thank you guys for any help you provide.

My experience with ntdll.dll problems have been a bad graphic driver, i'm on Nvidia, try to find a stable, good driver for your videocard.

Hi WestAirI had so many CTD with famous ntdll.dll on fs9, until I installed fs9-1 update patch, and the problem gone away !!!Maybe worth trying it. Hope it helps for you.Regards.Mapez

My experience with ntdll.dll problems have been a bad graphic driver, i'm on Nvidia, try to find a stable, good driver for your videocard.

It sounds like, from other threads around avsim, that ntdll.dll is something that comes up with system stability issues (drivers, ram) - That would make sense, because I usually do update my drivers for other games (BF3, Skyrim, etc).My major question now is how do I know what a stable driver for my card is? I'm currently running an Nvidia 9800 GT with 6GB of RAM on a stock i7 950 w/ Windows 7 64bit. When I go into control panel and try to update drivers for my 9800 GT my system tells me the best drivers for my GPU is already installed. How do I know if that's the right one I want?

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

Stein-Ove,Thank's for that. I'll give the new driver a shot, clean out my FSX.cfg anew, and try lowering my memory usage to see if any of that helps with the CTD. Much appreciated.

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

Jim,Glad to hear! I hate to ask, because you've been so generous in explaining ntdl.dll and providing feedback already, but as a novice I honestly have no idea how to check my RAM frequency at all. I do know how to go into the BIOS, but that's about it. Jim, would you mind explaining how I can view my DDR3 Freq. and modify it to a value appropriate for my CPU?You'd make a fellow simmer one happy guy.

Jim,Glad to hear! I hate to ask, because you've been so generous in explaining ntdl.dll and providing feedback already, but as a novice I honestly have no idea how to check my RAM frequency at all. I do know how to go into the BIOS, but that's about it. Jim, would you mind explaining how I can view my DDR3 Freq. and modify it to a value appropriate for my CPU?You'd make a fellow simmer one happy guy.

Yes. You need to download the freeware CPU-Z (Google). Open the program and go to the SPD (Speed) Tab and it will give you all the various frequencies and settings that are available for your installed memory. It will not tell you if it's installed properly or not though as your bios will automatically provide settings. They may be accurate but I have found they are inaccurate at least for the ASUS MB's. ASUS has an "AUTO" setting for the frequency and I have found that will cause real problems unless you set it to the actual frequency. The XMP setting on the various frequencies will provide you with the frequency for your installed memory. It could be DDR3 1600 or DDR3 2000, DDR3 1333, etc. So, if you set your bios with the XMP profile, these are the settings you will want to use. Down at the bottom of each column is the voltage setting for the memory and you want to make sure it is set properly in your bios. You did not indicate what MB you have installed but in the AVSIM hardware forum, you will find pinned several settings other flight simmers have entered in their bios. You might find one that matches your board/memory. I'm not a guru or expert on memory settings but have learned a little from the frequent NTDL.dll crashes I once received. Some others here on AVSIM are experts and hopefully they will come on and help you if you have any additional settings. You might want to tell everyone what CPU, memory and MB you have installed.Best regards,Jim

Thank you very much, Jim. I appreciate it.I should probably throw my PC Specs in my signature just for easy access whenever I need help. From what I remember I'm running on:OS: Windows 7 64 bit Home PremiumMemory: Corsair XMS3 6GB (3x2GB) DDR3 SDRAM 1600 (PC3 12800)Mobo: Gigabyte GA-X58A-UD3R LGA 1366 Intel X58 SATA 6GB/s USB 3.0 ATX Intel MotherboardCPU: Intel Core i7-950 Bloomfield 3.06Ghz LGA 1366 Quad-Core ProcessorGPU: Nvidia 9800 GT Graphics CardAnyways, I'm going to look into CPU-Z and see where that gets me. Fingers crossed.

Thank you very much, Jim. I appreciate it.I should probably throw my PC Specs in my signature just for easy access whenever I need help. From what I remember I'm running on:OS: Windows 7 64 bit Home PremiumMemory: Corsair XMS3 6GB (3x2GB) DDR3 SDRAM 1600 (PC3 12800)Mobo: Gigabyte GA-X58A-UD3R LGA 1366 Intel X58 SATA 6GB/s USB 3.0 ATX Intel MotherboardCPU: Intel Core i7-950 Bloomfield 3.06Ghz LGA 1366 Quad-Core ProcessorGPU: Nvidia 9800 GT Graphics CardAnyways, I'm going to look into CPU-Z and see where that gets me. Fingers crossed.

Yes, there are several FS'ers with the Gigabyte board and you should see some recommended settings for the bios in the Hardware forum here on AVSIM. If I were you I would go with the XMP Profile for your bios and set the frequency to DDR3-1600 and the memory voltage at 1.65. That should work. If you don't use the XMP profile, then you'll have to use DDR3-1333 and manually enter the settings for memory based on that memory spd tab I spoke about on the CPU-Z program. The voltage would then be set to around 1.50V. Good luck!Best regards,Jim

Hey guys,Well, I managed to up my memory to the correct values suggested by factory default - used memcheck and other programs to make sure it was stable without errors. I also cleaned my FSX folder with new installs and made sure my F drive (FSX is on it) was clean of errors through dskchk in command prompt. Finally I deleted all my old drivers and made sure every driver on system was up to date and properly installed. I'm positive my hardware is sound.Regardless, I was able to reproduce the ntdll.dll crash while sitting at the gate in the PMDG 737NGX programming the FMC. Like clockwork the CTD pops up during preflight or pushback. The log says:

Problem signature: Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61472.0 Application Timestamp: 475e17d3 Fault Module Name: ntdll.dll Fault Module Version: 6.1.7601.17514 Fault Module Timestamp: 4ce7ba58 Exception Code: c0000005 Exception Offset: 0002dece OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Additional Information 1: e8ad Additional Information 2: e8adce1c2b9e7be834b4063ac3c53863 Additional Information 3: e8ad Additional Information 4: e8adce1c2b9e7be834b4063ac3c53863Read our privacy statement online: http://go.microsoft....88&clcid=0x0409If the online privacy statement is not available, please read our privacy statement offline: C:Windowssystem32en-USerofflps.txt

I'm dumbfounded and quite frankly out of idea's. Honestly, I think my only plan now is to delete FSX and wait for MS Flight. I love FSX and my gajillion payware addons to death, but this CTD just won't go away. Can anyone at least tell me what the exception code on that crash means? If it means a fault with the system, the dll, something? Otherwise, I guess I'm flat out of ideas.

Hey guys,Well, I managed to up my memory to the correct values suggested by factory default - used memcheck and other programs to make sure it was stable without errors. I also cleaned my FSX folder with new installs and made sure my F drive (FSX is on it) was clean of errors through dskchk in command prompt. Finally I deleted all my old drivers and made sure every driver on system was up to date and properly installed. I'm positive my hardware is sound.Regardless, I was able to reproduce the ntdll.dll crash while sitting at the gate in the PMDG 737NGX programming the FMC. Like clockwork the CTD pops up during preflight or pushback. The log says:I'm dumbfounded and quite frankly out of idea's. Honestly, I think my only plan now is to delete FSX and wait for MS Flight. I love FSX and my gajillion payware addons to death, but this CTD just won't go away. Can anyone at least tell me what the exception code on that crash means? If it means a fault with the system, the dll, something? Otherwise, I guess I'm flat out of ideas.

The exception code c0000005 indicates you had a memory access violation. It could be caused by several things - http://windows.microsoft.com/en-US/windows7/Diagnosing-memory-problems-on-your-computer. NTDL.dll is a windows system file and does not belong to FSX. It relates to memory too as I already indicated above.Best regards,Jim

I would add that you may have your FSX settings set too high. The graphics card you have does not allow very high settings. This could trigger a conflict between your display drivers and system memory. I reread this thread and didn't see where you had deleted or renamed your FSX.cfg, restart FSX, and let the config be rebuilt. Many times this fixes a problem because people have set their settings too high or have added tweaks that are not compatible. If you want to keep your FSX.cfg, just rename it so that you can rename it back to fsx.cfg should this not work.Best regards,Jim

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