Solved PAGE_FAULT_IN_NONPAGED_AREA, 0x00000050. Attached jcgriff2.

[zharek]

every game I play either crashes or BSOD'S

Windows 7 64 bit
motherboard TF520 A2+
Processor Amd athlon 64 x2 dual core 3.2 ghz
memory: 4096MB Ram
graphics card: geforce gtx 550TI

 

[zharek]

Does anyone know what to do. it is still happening. cant play a game for more than 10 minutes.

 

[writhziden]

Problem Devices:

Realtek RTL8169/8110 Family PCI Gigabit Ethernet NIC (NDIS 6.20)	PCI\VEN_10EC&DEV_8167&SUBSYS_23041565&REV_10\4&3019DE45&0&4840	This device is disabled.

Security Software:

mpcmdrun.exe	c:\program files\microsoft security client\antimalware\mpcmdrun.exe	3920	8	200	1380	3/15/2012 6:31 PM	3.0.8402.0	266.95 KB (273,352 bytes)	4/27/2011 5:21 PM
mpcmdrun.exe	c:\program files\microsoft security client\antimalware\mpcmdrun.exe	3980	8	200	1380	3/15/2012 6:31 PM	3.0.8402.0	266.95 KB (273,352 bytes)	4/27/2011 5:21 PM
msmpeng.exe	c:\program files\microsoft security client\antimalware\msmpeng.exe	876	8	200	1380	3/15/2012 6:21 PM	3.0.8402.0	12.48 KB (12,784 bytes)	4/27/2011 5:21 PM
nissrv.exe	c:\program files\microsoft security client\antimalware\nissrv.exe	2080	8	200	1380	3/15/2012 6:22 PM	3.0.8402.0	281.52 KB (288,272 bytes)	4/27/2011 5:21 PM
msseces.exe	c:\program files\microsoft security client\msseces.exe	2128	8	200	1380	3/15/2012 6:22 PM	2.1.1116.0	1.37 MB (1,436,736 bytes)	6/15/2011 2:35 PM

There seems to be a duplicate file running with your security software. Uninstall and re-install the software. Post back your reports. This may be malware in disguise.


Possible out of date drivers:

[B][COLOR="Red"]scmndisp	fffff880`01948000	fffff880`01952000	Wed Jan 17 00:48:03 2007 (45add4b3)	00008b81		scmndisp.sys[/COLOR][/B]
mcdbus	fffff880`0f000000	fffff880`0f03c880	Tue Feb 24 03:34:07 2009 (49a3cd1f)	00041e84		mcdbus.sys

scmndisp.sys
mcdbus.sys
Out of date USB wireless network adapter solutions are known to cause crashes with Windows 7. Wireless network adapter USB is unstable as it is because USB ports do not supply the necessary power to keep wireless network adapters stable. We see crashes related to these a lot. I would recommend replacing yours with something more up to date, and strongly suggest switching to an actual wireless adapter PCI card within a motherboard slot.

[list=1]
[*]
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Kingston\BSODDmpFiles\zharek\Windows_NT6_BSOD_jcgriff2\031512-23556-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 x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17727.amd64fre.win7sp1_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c0c000 PsLoadedModuleList = 0xfffff800`02e50650
Debug session time: Thu Mar 15 19:20:27.370 2012 (UTC - 6:00)
System Uptime: 0 days 8:52:13.962
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff880018da890, 0, fffff80002f381e9, 0}


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

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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eba100
 fffff880018da890 

FAULTING_IP: 
nt!RtlpAtomMapAtomToHandleEntry+15
fffff800`02f381e9 488b4910        mov     rcx,qword ptr [rcx+10h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  itype.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88005f4b7b0 -- (.trap 0xfffff88005f4b7b0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000029 rbx=0000000000000000 rcx=fffff880018da880
rdx=0000000000000029 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002f381e9 rsp=fffff88005f4b940 rbp=fffff88005f4bca0
 r8=fffff8a00785b57e  r9=0000000000000000 r10=0000000000000672
r11=fffff8a0018da880 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlpAtomMapAtomToHandleEntry+0x15:
fffff800`02f381e9 488b4910        mov     rcx,qword ptr [rcx+10h] ds:1060:fffff880`018da890=64747568536f6974
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c3525c to fffff80002c88d40

STACK_TEXT:  
fffff880`05f4b648 fffff800`02c3525c : 00000000`00000050 fffff880`018da890 00000000`00000000 fffff880`05f4b7b0 : nt!KeBugCheckEx
fffff880`05f4b650 fffff800`02c86e6e : 00000000`00000000 fffff880`018da890 00000107`01e74500 ffffffff`ffffffff : nt! ?? ::FNODOBFM::`string'+0x456cf
fffff880`05f4b7b0 fffff800`02f381e9 : fffffa80`063ae760 fffff800`02c91cca fffff8a0`018da880 fffff880`05f4b9f0 : nt!KiPageFault+0x16e
fffff880`05f4b940 fffff800`02f7511a : 00000000`00000000 ffffffff`ffffffff fffff8a0`018da880 00000000`00000000 : nt!RtlpAtomMapAtomToHandleEntry+0x15
fffff880`05f4b970 fffff800`02f7a418 : fffff8a0`018da880 00000000`00000006 00000000`0026da70 00000000`0026da70 : nt!RtlLookupAtomInAtomTable+0xaa
fffff880`05f4b9c0 fffff800`02c87fd3 : fffffa80`063ae760 00000000`0026da08 00000000`0000052c 00000000`0000c029 : nt!NtFindAtom+0xe7
fffff880`05f4bc20 00000000`775c145a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0026d9c8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x775c145a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
nt!RtlpAtomMapAtomToHandleEntry+15
fffff800`02f381e9 488b4910        mov     rcx,qword ptr [rcx+10h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  nt!RtlpAtomMapAtomToHandleEntry+15

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  4ec79dd2

FAILURE_BUCKET_ID:  X64_0x50_nt!RtlpAtomMapAtomToHandleEntry+15

BUCKET_ID:  X64_0x50_nt!RtlpAtomMapAtomToHandleEntry+15

Followup: MachineOwner
---------
[*]
Loading Dump File [D:\Kingston\BSODDmpFiles\zharek\Windows_NT6_BSOD_jcgriff2\031412-27768-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 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16917.amd64fre.win7_gdr.111118-2330
Machine Name:
Kernel base = 0xfffff800`02c4e000 PsLoadedModuleList = 0xfffff800`02e8ae70
Debug session time: Thu Mar 15 00:23:31.120 2012 (UTC - 6:00)
System Uptime: 0 days 0:58:41.056
Loading Kernel Symbols
...............................................................
................................................................
.........................
Loading User Symbols
Loading unloaded module list
...................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff88003172e28, 0, fffff88003d5a0b9, 1}


Could not read faulting driver name
Probably caused by : dxgmms1.sys ( dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169 )

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

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

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002ef50e0
 fffff88003172e28 

FAULTING_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169
fffff880`03d5a0b9 448b54c208      mov     r10d,dword ptr [rdx+rax*8+8]

MM_INTERNAL_CODE:  1

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  LoLLauncher.ex

CURRENT_IRQL:  0

TRAP_FRAME:  fffff880065b80a0 -- (.trap 0xfffff880065b80a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000000001c4 rbx=0000000000000000 rcx=00000000000000e2
rdx=fffff88003172000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff88003d5a0b9 rsp=fffff880065b8230 rbp=fffff880065b8a40
 r8=fffffa800488f010  r9=0000000000000003 r10=fffff8a00319d470
r11=00000000c0003880 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x169:
fffff880`03d5a0b9 448b54c208      mov     r10d,dword ptr [rdx+rax*8+8] ds:8000:fffff880`03172e28=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c6a8ed to fffff80002cbe540

STACK_TEXT:  
fffff880`065b7f38 fffff800`02c6a8ed : 00000000`00000050 fffff880`03172e28 00000000`00000000 fffff880`065b80a0 : nt!KeBugCheckEx
fffff880`065b7f40 fffff800`02cbc62e : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x4236f
fffff880`065b80a0 fffff880`03d5a0b9 : 3d42c4c3`1a1ae40d 3d42c4c3`1a1ae40d 3fe00000`00000000 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`065b8230 fffff880`03d403e7 : fffffa80`04bfd501 fffffa80`0423cc10 00000000`02330010 fffff880`00000026 : dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+0x169
fffff880`065b8320 fffff880`03cb8f12 : fffffa80`04fd7000 00000000`00000200 fffff880`065b8a40 00000000`00000000 : dxgmms1!VidMmReferenceDmaBuffer+0x43
fffff880`065b8370 fffff880`03cb86d7 : fffff8a0`00000001 fffff8a0`0b862130 fffff880`065b89f0 00000000`00000000 : dxgkrnl!DXGCONTEXT::Render+0x326
fffff880`065b8980 fffff960`0023f746 : 00000000`0008e1b0 00000000`0018fc1c 00000000`0008fd20 00000000`7efdb000 : dxgkrnl!DxgkRender+0x3e7
fffff880`065b8bf0 fffff800`02cbd793 : fffffa80`04bd77d0 00000000`000001d4 00000000`00000000 fffffa80`047a42f0 : win32k!NtGdiDdDDIRender+0x12
fffff880`065b8c20 00000000`7516164a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0008e188 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7516164a


STACK_COMMAND:  kb

FOLLOWUP_IP: 
dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169
fffff880`03d5a0b9 448b54c208      mov     r10d,dword ptr [rdx+rax*8+8]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: dxgmms1

IMAGE_NAME:  dxgmms1.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4d3fa174

FAILURE_BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169

BUCKET_ID:  X64_0x50_dxgmms1!VIDMM_GLOBAL::ReferenceDmaBuffer+169

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


[/list]

1. Possible causes are Memory problems... Graphics card memory problems... BIOS... Corrupted hard disk file system... Corrupted System Files... Missing Windows Updates... Antivirus Software... Drivers...
2. Caused by DirectX/Graphics Card. Same other possible causes as 1.

Thanks to Dave76 for help understanding possible causes.


Suggested steps:

• First thing I would suggest is connecting directly to the internet via Ethernet if you are using your USB wireless network adapter. Remove the USB wireless network adapter from the system and see if you experience the same crashes when gaming. If you still experience crashes, proceed to the next steps.
  
  
• Try re-installing DirectX using the Download: DirectX Redist (June 2010) - Microsoft Download Center - Download Details and see how the system responds.
  
  Follow the steps for Diagnosing basic problems with DirectX. To re-install your display card drivers as outlined in the DirectX link, use the following steps.
  
  1. Download the latest drivers for your display card(s)
  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 Display adapters
  7. Do the following for each adapter (in case you have multiple display cards)
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  8. Restart your computer after uninstalling drivers for all display cards
  9. Install the latest driver for the display cards once Windows starts
  
  Alternatively:
  1. Login as an adminstrative user
  2. Download the latest drivers for your display card(s)
  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 Display adapters
  8. Do the following for each adapter (in case you have multiple display cards)
     • Right click the adapter
     • Click Uninstall (do not click OK in the dialog box that pops up after hitting Uninstall)
     • Put a tick in Delete driver software for this device (if this option is available, otherwise just hit OK) and hit OK
  9. Restart your computer after uninstalling drivers for all display cards
  10. Install the latest driver for the display cards once Windows starts
  
  
• 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. Let the memory test run for at least seven passes; the more the better.

 

[zharek]

seems like my processor is the issue, one of the cores fails on a prime95 test after 3 minutes.

 

[writhziden]

Recommend removing the processor and checking for bent pins.

If the processor looks alright, see if you can borrow another processor that will work in your machine to confirm it is the processor and not the motherboard. If you cannot, you could take the processor to a shop that fixes computer hardware and see if they will test the processor for low cost.

Otherwise, I would recommend that you RMA the processor and see if a new one provides more system stability.