Geek asks and answers

How to resolve freezing (or deadlock) in the ntdll.dll file?

I have an application running on the .Net framework 4, and my application runs managed AND unmanaged code. Unmanaged code uses UDP sockets. When the application starts from Visual Studio, everything is fine, but when it starts by itself, it often freezes. I have seen behavior on both Windows XP SP3 and Windows 7 SP1. When I attach the debugger to the application and pause it, I see that many MANY threads are stuck at the same memory address in the ntdll.dll file. With a disassembler, executing the netdll.dll command is "ret".

Is this calling someone?

It looks like there were similar problems earlier, like the ones reported here, and this was due to UDP: http://social.msdn.microsoft.com/Forums/en-US/netfxnetcom/thread/1b54b2f2-6e7c-405b-bdda- 62197ac8a287 There were no answers.

I also found an old fix for a similar problem, but according to Microsoft, it only applies to Windows NT 4.

Any help would be appreciated.

+3
source share
1 answer

This is not an operating system that causes a dead end. Yes, your stack trace will show that it blocks KiFastSystemCallRet () inside ntdll.dll. With a stack trace pointing to the RET command after SYSENTER. But he just does what you asked.

Debug + Windows + Threads, , . , . , . .

+3

More articles:


All Articles