Leave a comment

New Windows update can cause Blue Screen of Death

New Windows update can cause Blue Screen of Death
JaysonPhotography / Shutterstock.com

You know how much I advocate your security. Keeping your programs and security software up to date is the best defense against hackers and malicious software.

But Microsoft had a bit of an "oopsie" with the most recent Update Tuesday, formerly known as Patch Tuesday. In some computers, the newest update can cause the Blue Screen of Death, effectively bricking your computer.

-advertisement - article continues below-

Don't panic, there is a specific set of elements that's needed to create the perfect storm for the Blue Screen of Death. The kernel update, named MS 14-045, has been pulled by Microsoft, so if you still haven't updated from the last Update Tuesday, you should do so now.

The Blue Screen of Death happens when the update kernel incorrectly handles the Windows font cache file. This happens during the boot-up part of the update, so you're stuck in a reboot loop.

If you have been affected by the update, you'll see the Blue Screen of Death but you'll also see the bugcheck number "0x50 PAGE_FAULT_IN_NONPAGED_AREA."

"The reason this problem didn't show up in testing is because it only happens under rather specific circumstances.

You need to have one or more OpenType Font (OTF) files, installed in non-standard font directories, that are recorded in the registry with fully-qualified filenames.

A default Windows 8.1 install, for instance, includes only TTF (TrueType Font), TTC (TrueType font Collection) and FON (Windows bitmap FONt) files, recorded without pathnames ..."

Microsoft has created a workaround to help you if you've gotten the Blue Screen of Death. Click here to recover your computer.

 
 
 
 
 
 
A high-tech personal airbag can save you from hip fractures
Previous Happening Now

A high-tech personal airbag can save you from hip fractures

Hackers steal 4.5 million patient hospital records
Next Happening Now

Hackers steal 4.5 million patient hospital records

View Comments ()