BSOD : w/ Chrome - FAULT_PAGE_IN_NON_PAGED_AREA - 0x050 - win32k.sys

[Bajawah]

Hello,

First, thank you for having such a support network here!

Decoding BSoD have always been somewhat greek to me so aside from hopefully helping me find the issue, please point me to any resources I can use to debug this myself ( at least partially ) in the future.


Issue :

• BSoD Error = FAULT_PAGE_IN_NON_PAGED_AREA - 0x050 - win32k.sys
• BSoD only when using Chrome. Otherwise, zero issues.
• Currently, I cannot launch Chrome at all without getting a BSoD.
• This has happened a few times before. But each time choosing not to "restore" my browsing session has kept the BSoD from returning.
• No hardware changes recent enough to be related. ( 6+ months )
• I have a strong feeling that this is driver related because aside from Nvidia and Windows Update, everything else has not been manually updated. /shame...

On a ranting note, the first BSoD today caused my SABnzbd installation to become corrupted ( correlation == causation rite? lol ) and then throw an error on boot. That error opens Chrome to display it... which then would BSoD the box. I was not amused. :sarc:

Thanks!

 

[kotpl]

Can you upload dmp files? Usualy, in such situations, graphics drivers causes BSOD.

 

[Bajawah]

Can you upload dmp files? Usualy, in such situations, graphics drivers causes BSOD.

Are the ones inside the attached zip the incorrect ones?

Thanks!

 

[Golden]

There is no need to download additional software. Everything is already contained in the attachment.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR="Red"][B]BugCheck 50[/B][/COLOR], {fffffffffffffff8, 0, fffff9600005bda9, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!itrp_InnerExecute+49 )

Followup: MachineOwner
---------

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[Bajawah]

There is no need to download additional software. Everything is already contained in the attachment.

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

[COLOR="Red"][B]BugCheck 50[/B][/COLOR], {fffffffffffffff8, 0, fffff9600005bda9, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!itrp_InnerExecute+49 )

Followup: MachineOwner
---------

Run a minimum of 8 passes, preferably overnight, or until errors occur using MemTest86+.

Use this tutorial to help you use MemTest86+:
http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

Thanks Golden!

I am getting Memtest onto a USB now. On pass 5, no errors yet.

 

[Bajawah]

Memory error on pass 7. Crap!

I am going to order more ram. Can't afford to have the box down for multiple days trying to guess what stick it is in.

Thanks for the help.

 

[Golden]

OK. Test one stick in each motherboard RAM slot to make sure its not the motherboard.