BSOD at startup - win32k.sys, PAGE_FAULT_IN_NONPAGED_AREA

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.

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.

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, 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.

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.

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