A corrupt logbook.bin won't cause anything more than a hang as FSX loads it's files, sceneries, textures, etc., Don.It can be checked with this little app, available from the Avsim library:- Look for fsxlogrecovery.zip. It will analyse and repair any corruption or indexing errors that it finds. To my knowledge it has been around since FSX was released, and always works.

Also, be sure to clear shader cache.Another thing to check to be sure that this isn't the cause is to delete you logbook.BIN file in your "yournamedocumentsflight simulator x fileslogbook.BIN"

A corrupt shader cache won't cause the ntdll.dll CTD

Thanks again, Jim. Just for the record, the .cfg rebuild has worked so far.For the newbies reading this from a Google search:

• Location - %AppData%MicrosoftFSXfsx.cfg
• Delete fsx.cfg.
• Start FSX.
• Close FSX, reapply tweaks.

Can we mark this as solved so we keep the information in this thread for solving this issue clear and easy to find, please? At least until the above doesn't work for someone with this CTD. Adding a bunch of junk to a thread concerning issues like this only makes things more difficult for those afflicted and looking for answers.

Edited February 14, 201214 yr by ZachLW

A corrupt shader cache won't cause the ntdll.dll CTD

It did for me...... I rebuilt it and viola!