I know this to be true because I had a Win8.1 PC here the day before yesterday with the same issue:-
"Stop 0x50 errors," aka blue screen after applying any of four updates (KB2982791 KB2970228 KB2975719 or KB2975331).
If you update your Windows with the update, a message flashed on the screen that reads: “Your PC ran into a problem and needs to restart. We’re just collecting some error info and then we’ll restart for you (0% complete).”
“Installation went smoothly. After rebooting everything worked fine. But when I shut down my notebook and switched it on a little later it came up with a blue screen with a Stop 0x50 in Win32k.sys. I could not even boot into safe mode as Windows failed to start no matter which mode chose”
Maybe their latest 18,000 layoffs bit into the QA dep’t, and we’re now into the runaway train scenario
[EDIT]
This one has been committed to “bookmarks” (along with a few other examples of updates breaking Windows) for when someone next bitches about a kernel update breaking something in a “well it doesn’t happen in Windows” kinda way.
Bizarrely, reading the link you posted about fixing this mess, it all seems to be related to fonts - how can fonts ever be that critical, and involve the kernel?!?!