Solved BSOD at startup - win32k.sys, PAGE_FAULT_IN_NONPAGED_AREA

[Slashee the Cow]

So I tried turning on my computer this morning, and it wouldn't boot. Every time at startup, after the "Starting Windows", goes to a black screen with a mouse cursor for a second or two, then BSODs - as title says, something about win32k.sys and PAGE_FAULT_IN_NONPAGED_AREA - the technical information says:
STOP: 0x00000050 (0xFFFFF901C064B78C, 0x0000000000000000, 0xFFFFF9600007CCA3, 0x0000000000000005)
win32k.sys - Address FFFFF9600007CCA3 base at FFFFF96000010000, DateStamp 53c5df64

My hardware hasn't changed recently, although yesterday I did install some Windows updates and what I think was a driver update for my keyboard (Razer BlackWidow Ultimate, in case that matters) which leads me to suspect that it's a software problem, not a hardware problem (well, that and I don't want to have to go out and buy some new RAM - I did run the Windows memory test and that didn't report any errors, I realise it's no memtest86, but it's a start).

I also tried booting in safe mode and last known good configuration, both just have the same BSOD. I tried booting off the install CD to run a repair (or a system restore, or something), but my Windows install doesn't appear in the list to repair (nothing does). I'm pretty sure I don't need to install drivers for it to be able to see it, especially since I can see the hard drive. I did run sfc /scannow from a command prompt, but it didn't find any problems.

So I'm mostly out of ideas. I could do a new install over the top, but I'm hoping for something less destructive (also I don't know where I have my key written down, and I can't boot to pull it out of the registry). Since I can't boot, I can't do any configuration in Windows to get crash dumps, although if it makes any by default I can probably boot into Linux or something to upload them.

 

[carwiz]

Sounds like the patch bug that hit the world.

Blue Screen (Stop 0x50) after applying update KB2982791 to - Microsoft Community

Boot from your DVD to a cmd prompt and remove the following file:

c:\Windows\System32\FNTCACHE.DAT

Remove the disk then restart the PC.

This seems to repair it for those with the same problem.

 

[Slashee the Cow]

Uodate: I unplugged all my hard drives (leaving only the SSD that Windows is installed on). It definitely won't boot now - the bootloader was on one of the hard drives (why the bootloader and the OS are on separate drives is a story for another time).

Now when I try to access the repair tools from the setup disc I just get an error saying "This version of System Recovery Options is not compatible with the version of Windows you are trying to repair. Try using a recovery disc that is compatible with this version of Windows.". I get the same thing from the original install disc I used (an upgrade Windows 7 Pro x64 disc from when it came out), a newer SP1 x64 OEM install disc from another computer, and a repair disc I just created using the aforementioned computer.

So what I'm looking for is a solution to stop the BSOD I get on boot that I can enact without being able to boot (best! I'm just not sure how likely it is), a way to access the repair tools on the Windows disc (good), or at worst, an easy way to backup and restore ALL (or as many as possible) of my settings if I have to reinstall Windows entirely.

 

[Slashee the Cow]

Thanks carwiz! That fixed it!
(And here I was thinking I was good at Google, yet my skills have failed me yet again)

Now my only problem is that I accidentally unplugged the power to my CPU cooler when I was unplugging hard drives - d'oh!

 

[carwiz]

Did you do the shift + F10 at the first screen?

I should have given you this tutorial: http://www.sevenforums.com/tutorials/682-command-prompt-startup.html

Are you familiar with the old DOS instructions to Change Directory (CD) and delete a file (del)?

 

[carwiz]

Ok great!

I was looking for tutorial while you were typing.

Glad you got it fixed.

 

[benjam222]

Carwiz, I stumbled on your fix for this error, and it worked. Just before I was going to do a factory reset. I feel like I owe you something for that knowledge... Thanks a bunch.

 

[carwiz]

No problem. Glad we could help.

 

[Kolionr]

I too stumbled on this thread after spending all day trying to fix my pc. This did the trick right away. Thanks a lot carwiz!!! I had to make an account just so I could thank you.

 

[PCfox]

Hi
I had this BSOD issue out of blue
MS advice worked for me vey well
http://support.microsoft.com/kb/2982791


During 3 days of struggle I found this, among other things..

Recover data from a corrupt Windows drive with Linux
https://www.alansitsolutions.com/blog/2014/07/02/recover-data-corrupt-windows-drive-linux/

Just spread it around.

It is magic. I was able to copy the whole intact content of the unbootable windows HDD to external HD. I was wandering what to do next till I found Carwiz post... Up and running again now. Cheers

 

[BBG]

I just came upon this same problem today (Windows 7 Home Premium, 64-bit), when taking my computer out of sleep mode I received the BSOD error (see attached). Restarting will show the same screen, and any attempts at booting in Safe Mode have failed, including Safe Mode with Command Prompt.

I've tried running diagnostic tests (hitting F12 as start up), but these tests haven't found any issues (see attached). I have the Windows 7 Reinitialization disk that came with my Dell, but that doesn't seem to be working when rebooting. I've tried the Shift + F10 as suggested during the start up but haven't had any luck getting the Command Prompt screen to enter. Does anyone know what might give?

I'm not the best with this stuff but I feel like the instructions to solve this problem have been laid out pretty clearly in this thread and I'm getting rather frustrated with myself for not being able to do it myself!

 

[carwiz]

@BBG Only:
Download the Official Windows 7 Home Premium-x64 SP1 ISO from here:
Windows 7 Direct Download Links, Official Disk Images from Digital River

The English version is about half way down the page. There are many language versions listed in columns so be sure to select the correct one. They are large--Almost 4GB. But it will give you a full version that you can also use, with your key, to do a Clean Reinstall should you ever need/want to.

Place a blank DVD in your DVD writer. Right click the downloaded ISO file and click on Burn disc image. This will create a Windows bootable disc you can use in the previous mentioned procedure as well as having an official full copy of your Windows version.

 

[BBG]

Carwiz,

You are a man of great knowledge. Thank you for your quick and helpful assistance with this issue. Removing that one file did the trick.

Thanks again!

 

[carwiz]

Well, I don't know about that but thanks. Knowledge is wasted unless it's shared and the guys and gals on this forum wouldn't be here unless they enjoyed sharing and exchanging what they have learned. I just passed along what I learned during the early hours of the problem.

 

[PCfox]

I read lots of wornings about repair install and who would like to do clean install just to loose all dayta?

The Linux way
Recover data from a corrupt Windows drive with Linux
https://www.alansitsolutions.com/blog/2014/07/02/recover-data-corrupt-windows-drive-linux/


The Ubuntu system can read all on the Windows unbootable HDD
This give you possibility to to anything with all files on your HDD including eraising Widow flies. (in this case at least, when the error is applied to othervise healthy HDD).

I find it is much easier than coping with Windows ISO file

 

[carwiz]

Don't put words in my mouth.

You don't need to do a repair install or a clean install to fix this problem. You don't need Linux nor do you have to download anything. You START the recovery by inserting a Windows disc just to get to the first screen. This allows you to do the shift+F10 to enter a menu that then allows you to choose a command prompt. That command prompt is all that needed to delete the corrupt file. Once the file is deleted, the disc can be removed and PC can be booted as normal.

The suggestion was made to download Windows ISO simply to create a bootable DVD/CD since the respondent said his didn't work and having the ISO could save time ordering one from the OEM. In addition, it gives a PC owner the OPTION to do a clean install, at a later date, should the owner want to rid his system of OEM crapware. You can't do that with Linux or Ubuntu and still keep Windows.

No download of any kind is necessary if you already have a Windows repair disc.

 

[PCfox]

I can not argue with you carwiz, you are the expert. I am just an ordinary user. This experience with unbootable system happened to me first time during my 20 years of using computers. Windows recovery environment looked to me very bizarre, dark and unfriendly. Entering command prompt is like entering black tunnel or trying to navigate inside broken sinking submarine.
The thing which Linux did for me it was, first of all, possibility to copy whole content of the unbootable HDD to an external disk. It was like looking at the thing from outside, illuminated, active and intuitive.
This may be an interesting additional option to recues things before going for actual restoration of Windows.
Luckily enough the error was curable thanks to MS advice, but think about those poor people who get BSOD due to all other possible reasons and do not even have backups...
I am just reading that there are some sophisticated data recovery programs *professional which give you possibility to copy content of unbootable HD to external disc location before attempting repairs. Think about it. Have a look at ShedowProtect Desktop 5.0 www.storagecraft.com. I will get myself a decent backup tools now. Maybe I will not need them during next 20 years / I hope so / but this BSOD made me scared taking into consideration content of my HD...

 

[Dennis1919]

UPDATE: I feel stupid. I realize I had the wrong drive letter in the command line that I was deleting to. I used this line of code to see how many drives I had:
'wmic logicaldisk get name' (no quotes)

and then just like the microsoft tutorial said, i went drive by drive and using DIR to see whats in it.
GREAT GUIDE: Microsoft's Answers Page


Thanks everyone
--------------------------------------------------------------------------------------
Firstly, I hate this patch, and thanks to everyone who is helping anyone out.

I came here because I also am having the exact same issues as all of you.
I CANNOT boot into Safemode, I get BSOD (networking or cmd safemode)
nor can I boot into my machine.

In my case, I boot from CD, go to command prompt, and cd to that location to delete the file. I delete it and can confirm that the FNTCACHE.DAT file is deleted because if i run the code again, it says it could not find it.

I then follow the instructions to reboot and take the disc out, but I still get the BSOD (same error) upon normal boot (and safe mode boot, tried it twice).

Every time i go in and delete that file, because it keeps getting recreated, but after each time, I see the Starting Windows Flag form, i see a black screen with my mouse, and then about 2 seconds after, it BSOD same error. Attached is the error:


Thanks in advanced for ANY replies

 

[PCfox]

@Denis1919
Have you followed all instructions about removing bad MS updates after havein removed the .dat file?

 

[Weiss]

Thanks a lot!

Thanks a lot for the info, carwiz - I wasted a lot of time on this and was getting ready to move to more drastic measures.