I won't tell you what I have gone through when investigating this terrible and absolutely misleading issue. It cost me some sleepless nights. However, I have finally proved it is (in my case) related to bad hw driver definition in the Windows registry. I had tested and repeated that behaviour even on a fresh installation of Windows. So what was the ultimate solution? I went to this registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}
In that key there were two values:
Shockprf
PartMgr
I deleted the latter and voila!
Note:
You may want to play with other (conflicting) Upper/Lower Filters, however some changes will likely cause the BSOD (it happened to me too). In such a case you simply let Windows rebuild the last state during the next boot...
I have found a good reference and even scripted tools for the Upper and Lower filters here:
http://www.cdr-zone.com/forum/about4719.html&highlight=filters
cheers