Not sure if everyone is aware of this revelation, but the presence of a TDL3 aka TDSS rootkit infection was what was causing the affected systems to become unbootable after installation of the MS10-015 update. Apparently, the rootkit driver used a hardcoded address method to calculate its Windows kernel entry points. Since MS10-015 updated the OS kernel, the addresses the rootkit code referenced were no longer valid, resulting in BSODs.
In effect, the update was a TDSS detector, though not a very friendly one!http://www.prevx.com/blog/143/BSOD-after-MS-TDL-authors-apologize.html
Most of those users were angry with Microsoft, but the problem this time is not related to Microsoft. Indeed a number of the users affected by this BSOD was infected by TDL3/TDSS rootkit.
More exactly, TDL3 rootkit looks incompatible with MS10-015 update. This is the cause of the BSOD. Problem resides in the lazyness of rootkit writers when writing the driver infection routine.