I guess my reference was very well placed
Quite frankly, I don't know if it's the hook .dll that's misbehaving par se, I can only observe that certain processes starts to misbehave and nothing have been changed but the injection driver, so it was kinda natural to me to suspect that it was something with the driver, not that I know for sure that it's the driver as such..
My hook .dll is not loading any other .dlls and it creates no threads, not so sure about the fancy part.
The hook .dll hooks all the LoadLibrary calls and then proceed to hook all the dns resolution apis in the various winsock .dlls (getaddrinfo, DNSQuery_W and so on) as well as the connect and sendto calls.
Why it hooks loadlibrary is if the winsock .dlls are not loaded at the point of injection, then I want to hook them as (if) they get loaded later.
Currently I'm inserting some debug messaging code to signal what gets called and when, that way it might give me some kind of idea of where it may be looping, if that's the case (I don't thinks so, but you never know).
I have been thinking that by me hooking the loadlibrary calls during dllmain it might overwrite a return pointer or something, but time might tell..