I think this is probably just a co-incidence. CF is a .net application so you'd expect the framework to kick in and terminate CF way way before it got to BSOD stage.
Last time this happened to me, it turned out that there was a solder splat stuck to the inside of my system somewhere that had finally gotten loose, fallen off and shorted out my USB controller. Fortunately it did no permanent damage.
I think you're going to end up reinstalling Windows