I have not only this issue with windows, but on my gaming machine, unless I unplug my Microsoft-made keyboard when booting, the OS blue screens [1]. Of course if I then don't plug it back into the same USB port as before, it will reinstall the drivers...
(I also find it amusing that this happens with devices made by Microsoft themselves; you'd think they would make sure it worked, wouldn't you)
You may wish to enable kernel dumps, reproduce the BSoD, then install Debugging Tools for Windows. Now spin up WinDbg and inspect the kernel dump to see what is really causing this.
Looks like a corrupt Windows install to me, but you'll know more after WinDbg. Scandisk (with fix bad sectors) and the Windows memory checker might also reveal how the OS became damaged.
The same computer and hardware runs both Linux and Mac OS without issues, so if it's some other piece of hardware, Windows is the only one choking on it. And it only manifests when the Microsoft keyboard is plugged in.
So yeah. Sure, possibly it is some other piece of hardware in combination that is exposing brokenness in the MS USB drivers. But that doesn't change the fact that the software is the problem here.
Well the problem is the driver and likely Linux and MacOS are treating the keyboard as a generic device. Have you tried forcing windows to use a generic drive for the keyboard?
(I also find it amusing that this happens with devices made by Microsoft themselves; you'd think they would make sure it worked, wouldn't you)
[1]: http://www.hanselman.com/blog/FIXEDBlueScreenOfDeathBSOD7EIn...