5.1.2016: a quick update to this: using F8 and disabling driver sig enforcement is a valid workaround. Also determined that "Enable Boot Logging" also is a work around. This might not be a driver issue but could be a kernel level issue. A curious one as I have never encountered this in Windows. Merits further investigating.
Critical error encountered when updating from 14328 to 14332. blue screen during upgrade and after reboot. Fresh install also yields the same error.