Saturday, February 28, 2015
How to fix the Blue Screen BSOD 0x50 after applying update KB2982791 to Windows 7 64 bit from the Patch Tuesday Windows Updates from Aug 2014
Page fault in non-paged area - win32k.sys
References:
Microsoft Security Bulletin MS14-045
https://technet.microsoft.com/library/security/MS14-045
http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/blue-screen-stop-0x50-after-applying-update/6da4d264-02d8-458e-89e2-a78fe68766fd
These are the Updates that are related to this problem with win32k.sys
For all supported x64-based editions of Windows 7:
Windows6.1-KB2982791-x64.msu
Windows6.1-KB2976897-x64.msu
Windows6.1-KB2982791-x64.msu
Windows6.1-KB2976897-x64.msu
For all supported 32-bit editions of Windows 7:
Windows6.1-KB2982791-x86.msu
Windows6.1-KB2976897-x86.msu
Windows6.1-KB2982791-x86.msu
Windows6.1-KB2976897-x86.msu
HOW TO FIX THE BSOD
Solution #1 - (Easy Fix) Delete the Font Cache
Delete c:WindowsSystem32FNTCACHE.DAT
Something in that file is triggering the BSOD.
Delete that file and the system will reboot without a bsod.
FNTCACHE.DAT will be recreated upon reboot, so there is no risk to deleting it.
http://www.reddit.com/r/sysadmin/comments/2dkc3g/warning_kb2976897_kb2982791_and_kb2970228_causing/cjqfl1ySomething in that file is triggering the BSOD.
Delete that file and the system will reboot without a bsod.
FNTCACHE.DAT will be recreated upon reboot, so there is no risk to deleting it.
Solution #2 - Uninstall Update KB2982791
When the BSOD (0x00000050) happens it will try to do a repair. After that fails, click the link that says:
View Advanced Options for System recovery and support
Login to the recover console
Open the Command Prompt
Remove KB2982791 using DISM using the following directions:
I have included the package name for Win7 x64.
I have included the package name for Win7 x64.
If you need to find your package name, here is the command:
DISM.exe /image:d: /get-packages
If you get an error, you might still find the package name in dism.log. Save the log from x:windowslogsDISMdism.log to a thumb drive if you need to find the package name using notepad on another PC.
I found this package name in the log file by searching the log for 2982791:
Package_for_KB2982791~31bf3856ad364e35~amd64~~6.1.1.1
KB2976897 was not installed on this PC
My windows 8.1 x64 PC has this package:
Package_for_KB2982791~31bf3856ad364e35~amd64~~6.3.1.3
dism /image:d: /remove-package /packagename:Package_for_KB2982791~31bf3856ad364e35~amd64~~6.1.1.1 /scratchdir:d: emp
Now your PC should boot.
Now run hotfix KB2908190 to fix the font problems linked to the BSOD.
http://hotfixv4.microsoft.com/Windows%207/Windows%20Server2008%20R2%20SP1/sp2/Fix463450/7600/free/470342_intl_x64_zip.exe
wusa /uninstall /kb:2982791 doesn’t work in the recovery console, you have to use DISM.

Subscribe to:
Post Comments (Atom)
Certain news blogs other than attract perusers to have their very own unique exchanges. The space attracts you to make a gander at the aftereffects of different events and separate current issues. mediosindependientes
ReplyDelete