Blue Screen ..Pls help!

Error code 50, PAGE_FAULT_IN_NONPAGED_AREA - usual cause are Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS

Code:

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


Loading Dump File [C:\Users\Owner\Downloads\082510-32417-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 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02c5d000 PsLoadedModuleList = 0xfffff800`02e9ae50
Debug session time: Wed Aug 25 09:51:25.936 2010 (GMT-4)
System Uptime: 0 days 1:23:21.967
Loading Kernel Symbols
...............................................................
................................................................
.................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff8a02f73b008, 0, fffff80002f53970, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!HvCheckHive+90 )

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

6: 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: fffff8a02f73b008, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002f53970, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002f050e0
 fffff8a02f73b008 

FAULTING_IP: 
nt!HvCheckHive+90
fffff800`02f53970 45394c2408      cmp     dword ptr [r12+8],r9d

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  rundll32.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009ecb0e0 -- (.trap 0xfffff88009ecb0e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8a00ecb6420 rbx=0000000000000000 rcx=fffff8a00ecb0000
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f53970 rsp=fffff88009ecb270 rbp=fffff8a00a92b000
 r8=fffff8a011b7f420  r9=0000000001c05000 r10=fffff8a011b7f420
r11=fffff88009ecb330 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!HvCheckHive+0x90:
fffff800`02f53970 45394c2408      cmp     dword ptr [r12+8],r9d ds:0fa8:00000000`00000008=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002d4c8f2 to fffff80002ccd740

STACK_TEXT:  
fffff880`09ecaf78 fffff800`02d4c8f2 : 00000000`00000050 fffff8a0`2f73b008 00000000`00000000 fffff880`09ecb0e0 : nt!KeBugCheckEx
fffff880`09ecaf80 fffff800`02ccb82e : 00000000`00000000 fffff880`09ecb5f0 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`09ecb0e0 fffff800`02f53970 : fffff880`09ecb5f0 fffff880`09ecb5f0 fffff880`09ecb318 fffff880`09ecb5f0 : nt!KiPageFault+0x16e
fffff880`09ecb270 fffff800`02f4ea94 : fffff8a0`11b7f420 fffff8a0`11b7f420 fffff880`09ecb330 fffff800`001fbf30 : nt!HvCheckHive+0x90
fffff880`09ecb300 fffff800`02f4e251 : 00000000`00000000 00000000`00000002 fffff8a0`00010000 00000000`00380a00 : nt!CmCheckRegistry+0xc0
fffff880`09ecb380 fffff800`02f4ed89 : fffff880`09ecb520 fffff880`09ecb5f0 ffffffff`800013b0 fffff880`09ecba28 : nt!CmpInitializeHive+0x505
fffff880`09ecb470 fffff800`02f51c5a : 00000000`00000000 fffff800`00000000 fffff880`09ecb7d8 fffff880`09ecb7d1 : nt!CmpInitHiveFromFile+0x249
fffff880`09ecb590 fffff800`02f545d7 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmpCmdHiveOpen+0x8a
fffff880`09ecb780 fffff800`02f5032b : fffff8a0`00000020 fffff880`09ecbaa0 00000000`00000000 00000000`00000021 : nt!CmLoadKey+0x1a7
fffff880`09ecb970 fffff800`02f525e4 : 00000000`000001b8 00000000`0020f050 fffff8a0`00000000 00000000`00000000 : nt!NtLoadKeyEx+0x4c5
fffff880`09ecbbd0 fffff800`02ccc993 : fffffa80`08e63060 fffff880`09ecbca0 00000000`00000000 00000000`00008000 : nt!NtLoadKey+0x24
fffff880`09ecbc20 00000000`76f90cba : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0020eff8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x76f90cba


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!HvCheckHive+90
fffff800`02f53970 45394c2408      cmp     dword ptr [r12+8],r9d

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!HvCheckHive+90

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c44a9

FAILURE_BUCKET_ID:  X64_0x50_nt!HvCheckHive+90

BUCKET_ID:  X64_0x50_nt!HvCheckHive+90

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

This dump points to a memory issue and you have already determined that you have a RAM problem. YOu must get that problem resolved before proceeding further. After you test your RAM sticks individually and test your RAM slots with a known good stick, you can try running with one good stick.

By the way, good job on updating your drivers.