BSOD when browsing. PAGE_FAULT_IN_NONPAGED_AREA

Well here we go again...

My computer's been perfectly stable for months now and suddenly it BSODs again. (the previous issues had been entirely accounted for and rectified) I have my hunches but I need someone to take a look at the BSOD logs to find out what exactly caused this one.

I've been doing just fine until I started playing Battlefield 3. My NVIDIA 280.26 drivers weren't good enough, the game told me so and froze every 5 minutes of play, necessitating killing the process through the task manager. I did a clean reinstall complete with driver sweeper of the 285.62 driver version and that fixed my issue. The game requires you to have all sorts of crap running in the background when you play. Punkbuster is normal but now EA has their own version of Steam, 'Origin', which needs to be playing while you run it. It also runs the game through the web browser, which required their own addon through my Firefox browser (v9.0.1).

Things were going well till a couple of days ago. I had just finished up a game of BF3 and was browsing through the game's web site when my screen went black. Everything came back up and my PC told me my video drivers had crashed and recovered. Firefox had oddly crashed as well.

Fast forward to today, I'd finished playing BF3, at least an hour had passed. I was browsing some unrelated web site when my computer popped the blue screen linked in attachments. No warning at all, just browsing the net. My computer has been 100% stable up until now so I'm thinking it's either the new drivers or the funny plugin the game shoved into my Firefox. Whenever I've gone to their web site the browser opens 3 'plugin container' processes which won't close until I shut down the browser entirely. I know Origin wasn't running this last time but I might not have shut down the browser and restarted.

I use Windows 7 64 bit retail on a self-built computer.
I just built the system at the end of last year.
285.62-desktop-win7-winvista-64bit-english-whql (installed)

Any help would be muchly appreciated.

Code:

Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [K:\BSODDmpFiles\DrSNAFU\Windows_NT6_BSOD_jcgriff2\013012-18860-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03003000 PsLoadedModuleList = 0xfffff800`03248670
Debug session time: Mon Jan 30 03:01:23.721 2012 (GMT-7)
System Uptime: 0 days 10:08:20.526
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c2673000, 1, fffff960000b23f4, 0}

Unable to load image \SystemRoot\System32\win32k.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys

Could not read faulting driver name
Probably caused by : win32k.sys ( win32k+223f4 )

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

3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
it must be protected by a Probe.  Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: fffff900c2673000, memory referenced.
Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
Arg3: fffff960000b23f4, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 0000000000000000, (reserved)

Debugging Details:
------------------


Could not read faulting driver name

WRITE_ADDRESS: GetPointerFromAddress: unable to read from fffff800032b2100
 fffff900c2673000 

FAULTING_IP: 
win32k+223f4
fffff960`000b23f4 44891e          mov     dword ptr [rsi],r11d

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  csrss.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88008050b40 -- (.trap 0xfffff88008050b40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000058c5bf2 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000005bf2 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960000b23f4 rsp=fffff88008050cd0 rbp=0000000000009907
 r8=0000000000005bf2  r9=00000000058c3054 r10=0000000000009907
r11=0000000000005bf2 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
win32k+0x223f4:
fffff960`000b23f4 44891e          mov     dword ptr [rsi],r11d ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000302b9fc to fffff8000307fc40

STACK_TEXT:  
fffff880`080509d8 fffff800`0302b9fc : 00000000`00000050 fffff900`c2673000 00000000`00000001 fffff880`08050b40 : nt!KeBugCheckEx
fffff880`080509e0 fffff800`0307dd6e : 00000000`00000001 fffff900`c2673000 ffff0800`00000000 00000000`00000004 : nt! ?? ::FNODOBFM::`string'+0x4611f
fffff880`08050b40 fffff960`000b23f4 : 00000000`00000004 fffff900`c2673000 00000000`0000ffff fffff960`000b1d18 : nt!KiPageFault+0x16e
fffff880`08050cd0 00000000`00000004 : fffff900`c2673000 00000000`0000ffff fffff960`000b1d18 00000000`00000000 : win32k+0x223f4
fffff880`08050cd8 fffff900`c2673000 : 00000000`0000ffff fffff960`000b1d18 00000000`00000000 00000000`000000b7 : 0x4
fffff880`08050ce0 00000000`0000ffff : fffff960`000b1d18 00000000`00000000 00000000`000000b7 fffff880`08050f10 : 0xfffff900`c2673000
fffff880`08050ce8 fffff960`000b1d18 : 00000000`00000000 00000000`000000b7 fffff880`08050f10 00000000`00000000 : 0xffff
fffff880`08050cf0 00000000`00000000 : 00000000`000000b7 fffff880`08050f10 00000000`00000000 fffff880`080510c0 : win32k+0x21d18


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k+223f4
fffff960`000b23f4 44891e          mov     dword ptr [rsi],r11d

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k+223f4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4ecdcd5b

FAILURE_BUCKET_ID:  X64_0x50_win32k+223f4

BUCKET_ID:  X64_0x50_win32k+223f4

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

Possible causes are Memory problems... Graphics card memory problems... CMOS... Corrupted hard disk system files... Corrupted System Files... Missing Windows Updates... Drivers...
Thanks to Dave76 for help understanding possible causes.

I am fairly certain this is a driver issue, so we will start there.

I notice RTCore64.sys on your computer. Please remove RivaTuner/EVGA Precision/MSI Afterburner (known issues w/Win7). See if the problem persists after removing the program. If it does, report back and we will proceed with further steps.

Thanks again for the quick reply. So the break-down is inconclusive? Damn...

I've been down the RTCORE road before with my last problem. I ended up ruling it out as a cause but downloaded a newer version of the program that hopefully didn't have any more win7 issues. Truthfully it's never given me a single problem. The last batch of issues was traced to shoddy mouse drivers, which in turn destabilized my antivirus when they crashed, causing IT to crash. I've been problem free since I removed both and only in the last few weeks reinstalled the old antivirus. (Kaspersky, I have a liscence for it so why not use it?)

The only things I've actually changed recently have been the installation of that game and all the crap that goes with it, and the new video drivers to fix the game. I kind of need the RTCORE to control my fan speeds since the card runs a bit hot when playing intensive games. Unless it's having some new interaction with the newer video drivers. *shrug*

Think it'd be worth it to clean out my video drivers again and go with a beta set to test first? Maybe it's causing a bad paging of video memory or something.

It is difficult to tell if this was video card related. When you were browsing and it crashed, was the site you were on doing anything that might be Video intensive (an HD video, lots of graphical animations, etc)?

When the video drivers themselves crashed on Saturday all I was doing was browsing the web site of the game I had to install the new drivers for the day before.

When the entire computer BSOD'd me, I hadn't been playing games for at least an hour. It had been entirely idle and I jumped on to look at pictures on an art site. I even have ad-block so there were no ads or videos or anything going.

Alright, let's start by testing your graphics card and hardware to make sure it is not a hardware related issue. Since the crash was during idle, the blue screen crash is most likely not temperature related, but your graphics card crash may have been.

• If you are overclocking any hardware, please stop.
  
  
  
• Download and install HWiNFO64 Download to check hardware temperatures by running in sensor-only mode.
  
  
  
• Use FurMark: VGA Stress Test, Graphics Card and GPU Stability Test, Burn-in Test, OpenGL Benchmark and GPU Temperature | oZone3D.Net to test the graphics card GPU. Then use the |MG| Video Memory Stress Test 1.7.116 Download to test your graphics card memory.
  
  
  
• Run Hardware - Stress Test With Prime95 to determine any hardware problems. Run all three tests for a few hours each. If you get errors, stop the test and post back here.

Well the graphics card crash took place while idle too. I'd maybe stopped playing the game for about 15 minutes and was browsing their web site. It didn't have any fancy video ads or anything either, just layout and images.

Without EVGA Extreme Tuning utility (RTCORE), I'd have temps around 85c when gaming. I jumped up the fans a bit to lower that to the mid 70s. But I'll check those temps again.

My thought is, if those stress tests do cause another crash. What will it prove? It could still be either hardware or drivers. I'm at work right now, just fleshing out my options.

cluberti said:

Also, depending on the browser you're using, it could be accelerated using DirectX, which would mean rendering at least partially done on the video card, meaning it could explain crashes whilst simply browsing - accelerated browsers mean "just browsing" isn't as simple, at least code-wise, anymore, and brings in far more than it used to (i.e. acceleration on the video driver itself).

That's what I'm suspicious of. I'm using Firefox, not sure if that's directx-accelerated or not. But that Battlefield game installed a plugin into my browser that opens up 1-3 plugin-container processes every time I visit the game's web site. So there's also the chance that the plugin ties into my video card and that could be causing the problem too. @_@

I've already had an incident of something crapping out, only to cause a crash later. I can't ignore the fact that both of the incidents happened within an hour or two of playing Battlefield 3. And I also can't ignore the fact that I had to update my video drivers once already due to the game crashing and one day after I did that, the video drivers themselves crash. I've been playing other games and they seem to work fine. My gut says there's something funny with either the video drivers or the game.

I have the most recent WHQL video driver installed now but I also have some beta drivers I wisely downloaded as well just in case the new drivers didn't work to fix the game. Funny how I saw this coming...

DrSNAFU said:

Well the graphics card crash took place while idle too. I'd maybe stopped playing the game for about 15 minutes and was browsing their web site. It didn't have any fancy video ads or anything either, just layout and images.

Without EVGA Extreme Tuning utility (RTCORE), I'd have temps around 85c when gaming. I jumped up the fans a bit to lower that to the mid 70s. But I'll check those temps again.

My thought is, if those stress tests do cause another crash. What will it prove? It could still be either hardware or drivers. I'm at work right now, just fleshing out my options.

It depends on what the crash is that is caused. If it is like the ones you have had prior, it could be either the card or drivers. If that is the case, we can run through drivers through Verifier and see if any compatibility problems exist. If you would like to start with checking drivers before checking the graphics card hardware, run Driver Verifier by doing the following:

a. Backup your system and user files
b. Create a system restore point
c. If you do not have a Windows 7 DVD, Create a system repair disc
d. Run Driver Verifier

If Windows cannot start in normal mode with driver verifier running, start in safe mode. If it cannot start in safe mode or normal mode, restore the system restore point using System Restore OPTION TWO.

Thanks to zigzag3143 for contributing to the Verifier steps.
If you are unable to start Windows with all drivers being verified or if the blue screen crashes fail to create .dmp files, run them in groups of 5 or 10 until you find a group that causes blue screen crashes and stores the blue screen .dmp files.