In most cases an error in a Windows system file (such as win32k.sys) is indicative of a problem elsewhere in the system. The reason for this is that, if Windows files are corrupted seriously enough to cause a BSOD - then you'll likely see other severe problems before this occurs. This isn't an "always" thing - but it's reliable enough that the first step is trying out other options to see what's causing the error.
FYI - this error is caused because something accessed memory at an address that doesn't exist in the memory. This access attempt caused win32k.sys to crash. It's sorta like running out of gas in your car - the motor stops (the crash in win32k.sys) - but the cause is that you ran out of gas.
In this case, it was an attempt to read something from memory (rather than writing to memory). That's less common than the write error and may be a significant clue - but I haven't seen many of the Read errors, so I'm a bit shakey on this.
The possibilities are (in the order of my experience):
1) corrupt program/driver
3) bad RAM
4) corrupt pagefile
5) Windows corruption
If you're able to predict what'll cause the error (or if it occurs fairly frequently), I'd suggest running Driver Verifier to see if we can coax a bit more information out of the crash. Use this article to set it running: http://support.microsoft.com/kb/244617
At first, only enable it for Unsigned drivers (you'll slow your system way down if you do all drivers). Also, when you're done using it, go back in and select the "delete existing settings" to turn it off - otherwise you'll still have a performance issue because of it's background process.
Then, reboot and wait for the next BSOD (if you can make it happen, go ahead and do it). If we're lucky, it'll Blue Screen as soon as you reboot - and that'll likely give us the name of the driver that's causing it. If it doesn't Blue Screen immediately, I've found that the results aren't as reliable - but they still do give us clues as to where to look.
If you get a Blue Screen and it doesn't give you the info, then use this link ( http://forums.majorgeeks.com/showthread.php?t=35246
) to perform an analysis of the memory dump file (usually located in C:\Windows\Minidump (a hidden folder)) Then post the results here for us to have a look at.
My browser caused a flood of traffic, sio my IP address was banned. Hope to fix it soon. Will get back to posting as soon as Im able. - John
(my website: http://www.carrona.org/
)**If you need a more detailed explanation, please ask for it. I have the Knack
. ** If I haven't replied in 48 hours, please send me a message. My eye problems have recently increased and I'm having difficult reading posts. (23 Nov 2017)FYI - I am completely blind in the right eye and ~30% blind in the left eye.
<p>If the eye problems get worse suddenly, I may not be able to respond.If that's the case and help is needed, please PM a staff member for assistance.