Industry News

Some Windows 7 PCs bricked by Microsoft after faulty Patch Tuesday update

Has your Windows computer been stuck in an endless Blue Screen of Death hell since last week?

Chances are it may be connected to the Patch Tuesday updates that Microsoft issued last week.

As ComputerWorld reports, a lengthy thread on Microsoft’s support forums reveal that many users have been hit by a so-called “Blue Screen of Death” (BSOD) 0x50 Stop error message.

The dodgy update which appears to have caused the problem is MS14-045, a security update for the Windows kernel-mode drivers.

Frustration amongst those hit by the problem grew towards the end of last week, as many users found that their Windows 7 computers had been effectively “bricked”, with the BSOD preventing them from booting up properly.

Why was this bulletin revised on August 15, 2014?

Microsoft revised this bulletin to address known issues associated with installation of security update 2982791. Microsoft is investigating behavior associated with the installation of this update, and will update this bulletin when more information becomes available. Microsoft recommends that customers uninstall this update. As an added precaution, Microsoft has removed the download links to the 2982791 security update. For instructions on how to uninstall this update, see Microsoft Knowledge Base Article 2982791.

Microsoft has now removed download links while they investigate more deeply, but the finger of suspicion has already been pointed strongly towards poor handling of the Windows font cache file.

Known issue 3
Microsoft is investigating behavior in which systems may crash with a 0x50 Stop error message (bugcheck) after any of the following updates are installed:

2982791 MS14-045: Description of the security update for kernel-mode drivers: August 12, 2014
2970228 Update to support the new currency symbol for the Russian ruble in Windows
2975719 August 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2
2975331 August 2014 update rollup for Windows RT, Windows 8, and Windows Server 2012

This condition may be persistent and may prevent the system from starting correctly.

It’s good that Microsoft has published a workaround (albeit a fiddly one) to get computers back up and running again, but there’s no doubt that everyone would be happier if the bug hadn’t been present in the first place – or had been intercepted during Microsoft’s testing process rather than only discovered once rolled out to users’ computers.

This is far from the first time that Microsoft’s critical security fixes have caused problems, forcing users to await a patch for the patch… and sadly I doubt it will be the last either.

About the author


Graham Cluley is an award-winning security blogger, researcher and public speaker. He has been working in the computer security industry since the early 1990s, having been employed by companies such as Sophos, McAfee and Dr Solomon's. He has given talks about computer security for some of the world's largest companies, worked with law enforcement agencies on investigations into hacking groups, and regularly appears on TV and radio explaining computer security threats.

Graham Cluley was inducted into the InfoSecurity Europe Hall of Fame in 2011, and was given an honorary mention in the "10 Greatest Britons in IT History" for his contribution as a leading authority in internet security.


Click here to post a comment
  • Amazing, don’t they update there own computers, I presume the people at microsoft do use computers with windows installed. Or don’t they?

  • First time reader. How do I get updates on patch Tuesday?go to updates? Or some Microsoft website. If it makes a difference windows 7 ultimate and /or, professional. Bought it 2hand . Computer works

  • Windows 7 Sept update bricked my PC. After the installation (I only ever install "Important Updates" due to previous issues with "Optional Updates" also bricking my PC) I got stuck in the forever updating loop where nothing happened when it was supposed to reboot.

    Manually intervening and hitting the reset button, after 30 mins in limbo, achieved nothing whatsoever. Windows 7 would boot to the Windows logo and seize solid. Another hour, and many restarts, later I decided to reboot to my backup SSD. You can see that I'm a seasoned Windows user as I always keep a spare reliable drive available because, these days, it seems Microsoft has abandoned Quality Control altogether.

    Generally it's my Windows 10 PC that suffers from Microsoft's cruddy upgrade processes. Now it seems we Windows 7 holdouts are getting a serve as well. My Linux machine rarely ever suffers a fault, and then it's usually my fault.

    So if you a) Can afford it; and b) Know how to change drives on booting; I'd recommend keeping a backup drive as a precaution against Microsoft's incompetence.

    By the way, my Macs are far more reliable as is my Hackintosh. Probably because they are base on BSD Unix forks.

    The only reason I keep my Windows PCs is Gaming. If and when Linux becomes a competitive gaming platform I'll switch ASAP.