Winsock Kernel: "multi-threading" issues


I ran into strange problems/BSODs when using Winsock Kernel. I am able to create a socked, bind it and connect to the remote host. While the connection is active, attempts to establish additional connections usually end with a double fault exception somewhere within the WSK code. My driver registers as a WSK application and captures NPI only once.

Hence, I would like to ask whether there are some limitations of using one client NPI in multiple threads at the same time, or in processing of multiple requests at once.