calling socket bind results in Windows bluescreen

Question

We discovered that running our application under certain conditions results in Windows bluescreen. After some investigation we were able to narrow down the scenario to a sample of ~50 lines of C code using Winsock2 APIs. The sample -details removed by MS request-. Windows Server 2008 R2 crashes after several seconds running the sample. The problem reproduces on different physical machines as well as on Virtual Machines.

It looks like something that Microsoft would be willing to fix given that the problem repro is consistent. What is the right way to report such a bug? Any other suggestions?

Answer 1

This was just fixed in http://technet.microsoft.com/en-us/security/bulletin/ms12-032