Application Error: ntdll.dll crash?

[MikeB]

I have a program I designed that needs to run 24/7. I keep noticing that it crashes, at least once a day, and when I look in the event viewer, it says it crashed in reference with ntdll.dll?

Does anybody have any clue what ntdll.dll is?

[Stephen]

http://www.computerhope.com/issues/ch000960.htm

stephen1980

[Yves]

A crash in ntdll usually means corrupted memory or buffer overrun. If you can reproduce the crash in the event editor, if possible you should send your application to Francois so that he takes a look and see if he can fix it.

EDIT: and in which module does it crash at runtime? That could be 2 different issues.

[MikeB]

I will look into it and get back to you.

[kungsangun]

I too have had this exact issue. I cannot get my application to crash in the editor. How do we determine the exact module?..

This would be great to get insight on.

[MikeB]

Go to control panel---->Administrative Tools------>Event Viewer------>Application Logs.

[Yves]

I too have had this exact issue.

For info, a crash in ntdll is a "generic" crash that can be due to multiple reasons. At runtime this crash is often due to a memory management error in an extension.

[Nifflas]

Some Saira users have reported crashes with ntdll.dll and it usually happens when the game is saving (Ini++ is used for this). The only thing Saira does differently than my earlier games is the use of Ini++ and hardware acceleration.

It would be really helpful if this is actually identified.

[James]

If you get them to debug it (using ollydbg or such) and look at the call stack, they'll be able to tell you which module called ntdll.

[Nifflas]

Those of you who have this crash, if you're on XP, perhaps you can provide some info about the crash from the crash log file? (usually C:\Documents and Settings\All Users\Application Data\Microsoft\Dr Watson\drwtsn32.log)? A good idea is to select Run in the start menu, type drwtsn32 and set the crash dump type to "full", because then the log file will contain the call stack which is the information needed to figure out which extension that causes this.