Blue Screen 0x00000050 PAGE_FAULT_IN_NONPAGED_AREA Error

[Branston]

My computer just keeps random shutting down and never leaves a blue screen but this time its done a blue screen with the code in the title. What should I do ive ran the "SF Diagnostic Tool" and ill add the .ZIP file too a attachment.
Thanks Bran

 

[koolkat77]

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


Loading Dump File [C:\Users\Usra\Downloads\Branston\SF_27-02-2014\022714-18595-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 (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18247.x86fre.win7sp1_gdr.130828-1532
Machine Name:
Kernel base = 0x82e42000 PsLoadedModuleList = 0x82f8b4d0
Debug session time: Thu Feb 27 06:37:44.049 2014 (UTC + 6:00)
System Uptime: 0 days 7:00:45.844
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {c6c7f348, 0, 82efe322, 2}

Probably caused by : memory_corruption ( nt!MiGetWorkingSetInfo+23f )

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

0: 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: c6c7f348, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 82efe322, If non-zero, the instruction address which referenced the bad memory
	address.
Arg4: 00000002, (reserved)

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


READ_ADDRESS: GetPointerFromAddress: unable to read from 82fab84c
Unable to read MiSystemVaType memory at 82f8ae20
 c6c7f348 

FAULTING_IP: 
nt!MiGetWorkingSetInfo+23f
82efe322 8b4a18          mov     ecx,dword ptr [edx+18h]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

TRAP_FRAME:  9d6ffbb0 -- (.trap 0xffffffff9d6ffbb0)
ErrCode = 00000000
eax=9acf98f4 ebx=00000fff ecx=00080000 edx=c6c7f330 esi=852b9030 edi=8549c0c0
eip=82efe322 esp=9d6ffc24 ebp=9d6ffc78 iopl=0         nv up ei ng nz na pe nc
cs=0008  ss=0010  ds=0023  es=0023  fs=0030  gs=0000             efl=00010286
nt!MiGetWorkingSetInfo+0x23f:
82efe322 8b4a18          mov     ecx,dword ptr [edx+18h] ds:0023:c6c7f348=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from 82e82aa8 to 82ecf879

STACK_TEXT:  
9d6ffb98 82e82aa8 00000000 c6c7f348 00000000 nt!MmAccessFault+0x104
9d6ffb98 82efe322 00000000 c6c7f348 00000000 nt!KiTrap0E+0xdc
9d6ffc78 8309ec18 c08115fc 84f5a6a8 b82780e6 nt!MiGetWorkingSetInfo+0x23f
9d6ffd14 82e7f8c6 00000430 00000000 00000001 nt!NtQueryVirtualMemory+0x196
9d6ffd14 776970f4 00000430 00000000 00000001 nt!KiSystemServicePostCall
WARNING: Frame IP not in any known module. Following frames may be wrong.
062cf484 00000000 00000000 00000000 00000000 0x776970f4


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!MiGetWorkingSetInfo+23f
82efe322 8b4a18          mov     ecx,dword ptr [edx+18h]

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  nt!MiGetWorkingSetInfo+23f

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

DEBUG_FLR_IMAGE_TIMESTAMP:  521e9cb6

IMAGE_NAME:  memory_corruption

FAILURE_BUCKET_ID:  0x50_nt!MiGetWorkingSetInfo+23f

BUCKET_ID:  0x50_nt!MiGetWorkingSetInfo+23f

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

Start with Memtest. Take memtest. Run for 8 passes and test each stick in a know good slot for an additional 6 passes.

• RAM - Test with Memtest86+

The goal is to test all the RAM sticks and all the motherboard slots.

Check your motherboard manual to ensure the RAM sticks are in the recommended motherboard slots. Some motherboards have very specific slots required for the number of RAM sticks installed.

If you get errors, stop the test and continue with the next step.

1. Remove all but one stick of RAM from your computer (this will be RAM stick #1), and run Memtest86 again, for 7 passes.

*Be sure to note the RAM stick, use a piece of tape with a number, and note the motherboard slot.
​

If this stick passes the test then go to step #3.

2. If RAM stick #1 has errors, repeat the test with RAM stick #2 in the same motherboard slot.

*If RAM stick #2 passes, this indicates that RAM stick #1 may be bad. If you want to be absolutely sure, re-test RAM stick #1 in another known good slot.
​

*If RAM stick #2 has errors, this indicates another possible bad RAM stick, a possible motherboard slot failure or inadequate settings.
​

3. Test the next stick of RAM (stick #2) in the next motherboard slot.

*If this RAM stick has errors repeat step #2 using a known good stick if possible, or another stick.
​

*If this RAM stick has no errors and both sticks failed in slot#1, test RAM stick #1 in this slot.
​

4. If you find a stick that passes the test, test it in all the other motherboard slots.

If Part 2 testing shows errors, and all tests in Part 3 show errors, you will need to test the RAM sticks in another computer and/or test other RAM in your computer to identify the problem.

In this way, you can identify whether it is a bad stick of RAM, a bad motherboard, or incompatibility between the sticks.

   Information

Errors are sometimes found after 8 passes.

   Tip

Do this test overnight, before going to bed.