BSOD playing Heroes of Newerth error: Page fault in nonpaged area

Code:

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


Loading Dump File [D:\Kingston\BSODDmpFiles\pugmastaflex\Windows_NT6_BSOD_jcgriff2\040712-9984-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*C:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02e51000 PsLoadedModuleList = 0xfffff800`03095650
Debug session time: Sat Apr  7 10:07:26.764 2012 (UTC - 6:00)
System Uptime: 0 days 0:11:38.592
Loading Kernel Symbols
...............................................................
................................................................
.............................................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 3B, {c0000005, fffff80003318b6e, fffff88008876690, 0}

Probably caused by : ntkrnlmp.exe ( nt!PfpRpFileKeyUpdate+35e )

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

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

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff80003318b6e, Address of the instruction which caused the bugcheck
Arg3: fffff88008876690, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!PfpRpFileKeyUpdate+35e
fffff800`03318b6e 488b4208        mov     rax,qword ptr [rdx+8]

CONTEXT:  fffff88008876690 -- (.cxr 0xfffff88008876690)
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000885
rdx=00000000fffff800 rsi=fffff800030698b0 rdi=ffffffffffffffff
rip=fffff80003318b6e rsp=fffff88008877070 rbp=d3236a5ce06880ff
 r8=0000000000001000  r9=fffff8a018b9e7a0 r10=ffffffffffffffff
r11=fffff8a018b9e7a0 r12=fffff80003069938 r13=fffff8a018b75600
r14=fffff800030698e0 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00010246
nt!PfpRpFileKeyUpdate+0x35e:
fffff800`03318b6e 488b4208        mov     rax,qword ptr [rdx+8] ds:002b:00000000`fffff808=????????????????
Resetting default scope

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x3B

PROCESS_NAME:  svchost.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from 0000000000000000 to fffff80003318b6e

STACK_TEXT:  
fffff880`08877070 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!PfpRpFileKeyUpdate+0x35e


FOLLOWUP_IP: 
nt!PfpRpFileKeyUpdate+35e
fffff800`03318b6e 488b4208        mov     rax,qword ptr [rdx+8]

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  nt!PfpRpFileKeyUpdate+35e

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

STACK_COMMAND:  .cxr 0xfffff88008876690 ; kb

FAILURE_BUCKET_ID:  X64_0x3B_nt!PfpRpFileKeyUpdate+35e

BUCKET_ID:  X64_0x3B_nt!PfpRpFileKeyUpdate+35e

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

Unfortunately, this .dmp file provided inconclusive results. Possible causes are Memory problems... Corrupted hard disk file system... Corrupted System Files... Graphics Driver... Drivers...

I suspect an underlying driver since your crashes are less frequent now than they were.

• An underlying driver may be incompatible\conflicting with your system. Run Driver Verifier to find any issues. To run Driver Verifier, do 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. In Windows 7:

  • Click the Start Menu
  • Type verifier in Search programs and files (do not hit enter)
  • Right click verifier and click Run as administrator
  • Put a tick in Create custom settings (for code developers) and click next
  • Put a tick in Select individual settings from a full list and click next
  • Set up the individual settings as in the image and click next
    Attachment 206182
  • Put a tick in Select driver names from a list
  • Put a tick next to all non-Microsoft drivers.
  • Click Finish.
  • Restart your computer.

  
  
  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.
  The idea with Verifier is to cause the system to crash, so do the things you normally do that cause crashes. After you have a few crashes, upload the crash reports for us to take a look and try to find patterns.

I changed the steps for Verifier since last time, and hopefully the new settings will provide more conclusive results.

Thanks my man, I will definitely try this and get back to you ASAP. I hope this isn't an irritating thread for you

Nah, we all learn as we go. All of those helping on here went through the same process to get to where we are now, so no worries. :)

Let us know after you've had a few crashes with Verifier running. It could take anywhere between a few minutes to a few days for that to occur. We'll be keeping an eye out for your post no matter how long it takes.

This may be a major clue. When I turn on the driver verifier....my internet does not work. So basically, the router is detected and connects, but with no internet connection (with that exclamation sign on the internet strength bars). When I delete the verifier settings...then the internet works again...

So the drivers that are causing a clash MAY stem from the internet somehow? But I already installed the ASUS motherboard intel ethernet driver. Perhaps it is the wifi card...

Regardless, I also noticed that the last couple of crashes occurred when I was downloading something via my browser. I don't know if this helps, but those are some of the facts...

What do you use primarily to connect to the internet: wireless or Ethernet? I suspect wireless since your Ethernet Controller was not installed prior to us helping you. What wireless device do you have on your system? Was it pre-installed or did you install it yourself?

Code:

netr6164	fffff880`048d1000	fffff880`04944000	Thu Oct 15 21:15:23 2009 (4ad7e54b)	0006d6bf		netr6164.sys

There may be an update to your wireless driver at Ralink-A MEDIATEK COMPANY

Yeah, I have wireless (ASUS PCI-G31). My old Windows 7 build used the same card without a problem. I also have an Asus Mobo, so I don't see why it would cause issues, but those are the specs.

It is probably not the device itself that is causing issues. My guess is the drivers have become corrupted and need a full re-install. There is a driver update, but you should install it only after uninstalling the old driver.

1. First, download the latest driver from ASUS - Networks- ASUS PCI-G31. Then do the next steps.
2. Click Start Menu
3. Right Click My Computer/Computer
4. Click Manage
5. Click Device Manager from the list on the left
6. Expand Network adapters
7. Right click the wireless network adapter device
8. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
9. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
10. Restart your computer only if Windows asks you to.
11. Install the latest driver for the device.

Alternatively:

1. Login as an adminstrative user.
2. First, download the latest driver from ASUS - Networks- ASUS PCI-G31. Then do the next steps.
3. Click Start Menu
4. Click Control Panel
5. Click Hardware and Sound
6. Click Device Manager (the last link under Devices and Printers)
7. Expand Network adapters
8. Right click the wireless network adapter device
9. Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
10. Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
11. Restart your computer only if Windows asks you to.
12. Install the latest driver for the device.

Done, will update if there are any crashes.

How is the system currently running?

Hey! I haven't had a chance to use my computer in a few days. I was at the Coachella music festival. I will update you ASAP if there are any crashes. Thanks for checking up though. Been appreciating the kindness shown in these forums.:)