PAGE FAULT IN NON PAGED AREA windows 10

[theodore_3]

Hello Having problems still, usually happens when i am playing games.

below is the mini dump from the last crash. Thank you in advance.



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


Loading Dump File [C:\Windows\Minidump\040216-10484-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Windows\symbol_cache*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 10586.162.amd64fre.th2_release_sec.160223-1728
Machine Name:
Kernel base = 0xfffff801`d460e000 PsLoadedModuleList = 0xfffff801`d48eccd0
Debug session time: Sat Apr 2 18:19:24.939 2016 (UTC - 6:00)
System Uptime: 0 days 0:14:03.668
Loading Kernel Symbols
...............................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {ffffc00088371000, 2, fffff801d4ae77ad, 2}


Could not read faulting driver name
Probably caused by : ntkrnlmp.exe ( nt!PiDmGetObjectConstraintList+4d )

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

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


Could not read faulting driver name

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

READ_ADDRESS: unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
ffffc00088371000

FAULTING_IP:
nt!PiDmGetObjectConstraintList+4d
fffff801`d4ae77ad 668906 mov word ptr [rsi],ax

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

BUGCHECK_STR: AV

PROCESS_NAME: Uplay.exe

CURRENT_IRQL: 0

ANALYSIS_VERSION: 6.3.9600.17336 (debuggers(dbg).150226-1500) x86fre

TRAP_FRAME: ffffd001f3505f70 -- (.trap 0xffffd001f3505f70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=ffffd001f3506600 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801d4ae77ad rsp=ffffd001f3506100 rbp=ffffd001f3506140
r8=0000000000000000 r9=ffffd001f35061b0 r10=fffff801d4ad3b68
r11=fffff801d475c397 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!PiDmGetObjectConstraintList+0x4d:
fffff801`d4ae77ad 668906 mov word ptr [rsi],ax ds:00000000`00000000=86e4
Resetting default scope

LOCK_ADDRESS: fffff801d4905440 -- (!locks fffff801d4905440)

Resource @ nt!PiEngineLock (0xfffff801d4905440) Available

WARNING: SystemResourcesList->Flink chain invalid. Resource may be corrupted, or already deleted.


WARNING: SystemResourcesList->Blink chain invalid. Resource may be corrupted, or already deleted.

1 total locks

PNP_TRIAGE:
Lock address : 0xfffff801d4905440
Thread Count : 0
Thread address: 0x0000000000000000
Thread wait : 0x0

LAST_CONTROL_TRANSFER: from fffff801d476f395 to fffff801d4750760

STACK_TEXT:
ffffd001`f3505d18 fffff801`d476f395 : 00000000`00000050 ffffc000`88371000 00000000`00000002 ffffd001`f3505f70 : nt!KeBugCheckEx
ffffd001`f3505d20 fffff801`d4646e91 : 00000000`00000002 ffffd001`f3506410 ffffd001`f3505f70 00000000`000000f7 : nt! ?? ::FNODOBFM::`string'+0x10295
ffffd001`f3505e10 fffff801`d47599bc : 00000000`00000001 00000000`00000000 ffffd001`f3506178 00000000`00000000 : nt!MmAccessFault+0x5f1
ffffd001`f3505f70 fffff801`d4ae77ad : ffffc000`88371000 fffff6e0`00441b98 ffffd001`f3506220 fffff801`d46307ad : nt!KiPageFault+0x13c
ffffd001`f3506100 fffff801`d4ae774d : ffffd001`f3506410 00000000`c0000002 00000000`00000000 00000031`00000031 : nt!PiDmGetObjectConstraintList+0x4d
ffffd001`f3506170 fffff801`d4ae7686 : ffffffff`00000000 00000000`00088dfe fffff801`d4843eb0 ffffd001`f3506540 : nt!PiDmGetCmObjectConstraintListFromCache+0x6d
ffffd001`f35061e0 fffff801`d4ad3d2c : ffffffff`80001d20 ffffd001`f3506410 00000000`00000000 ffffd001`f3506540 : nt!PiPnpRtlGetFilteredDeviceInterfaceList+0x9a
ffffd001`f3506280 fffff801`d4ac69c8 : 00000000`00000000 00000000`00000000 00000000`20207050 ffffd001`f35065a0 : nt!PiPnpRtlCmActionCallback+0x1c4
ffffd001`f35063b0 fffff801`d4ac6289 : 00000000`c0000225 00000000`00002000 00000000`c0000023 00000000`00000000 : nt!CmGetMatchingFilteredDeviceInterfaceList+0xdc
ffffd001`f35064d0 fffff801`d4ac5f41 : 00000000`001f0001 ffffd001`f35068f0 00000000`00000000 ffffd001`f3506718 : nt!IopGetDeviceInterfaces+0x279
ffffd001`f35066a0 fffff801`d4ad2c53 : e001efd7`24a054c5 ffffe001`e9c20e90 00000000`00000000 00000000`00000024 : nt!PiCMGetDeviceInterfaceList+0xf5
ffffd001`f35067a0 fffff801`d4ad2bf5 : ffffe001`efd724d0 00000000`00008014 ffffd001`f3506b00 fffff801`00000000 : nt!PiCMFastIoDeviceDispatch+0x53
ffffd001`f35067f0 fffff801`d4a181b0 : 00000000`00000000 ffffe001`00000002 00000000`001f0001 00000000`00000000 : nt!PiDaFastIoDispatch+0x65
ffffd001`f3506850 fffff801`d4a17956 : ffffe001`00000000 00000000`00000001 00000000`00000001 00000000`00000000 : nt!IopXxxControlFile+0x850
ffffd001`f3506a20 fffff801`d475afa3 : ffffd001`f3506b10 ffffe001`ee84c080 ffffd001`f3506b80 00000000`00000001 : nt!NtDeviceIoControlFile+0x56
ffffd001`f3506a90 00000000`65f221bc : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0961ec08 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x65f221bc


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PiDmGetObjectConstraintList+4d
fffff801`d4ae77ad 668906 mov word ptr [rsi],ax

SYMBOL_STACK_INDEX: 4

SYMBOL_NAME: nt!PiDmGetObjectConstraintList+4d

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 56cd4410

IMAGE_VERSION: 10.0.10586.162

BUCKET_ID_FUNC_OFFSET: 4d

FAILURE_BUCKET_ID: AV_nt!PiDmGetObjectConstraintList

BUCKET_ID: AV_nt!PiDmGetObjectConstraintList

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:av_nt!pidmgetobjectconstraintlist

FAILURE_ID_HASH: {82ebeaa3-f062-0f3e-b0a3-da61cf9c5ffb}

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

 

[Shaun o]

The executable file ntkrnlmp.exe.

Executed a command to store or retrieve data from a block of memory or memory address of main system ram.
Where it was outside of the windows cache and paging file.

The start or end point along with the length of the data exceeded the page file size.

And, or tried to access a part of the system memory reserved by a set hardware device in the system.
Or outside of the virtual memory paging file set in windows.
In english that is what it means.

So the driver returned an error, and terminated as a process in windows.

The causes can be memory leakage.
The system does not have enough physical memory.

The page file size setup for windows is too small in size.
And can be altered to prevent the error.

The common cause is when physical ram is very low, and windows has to resort to virtual memory space.
That you may experience on a system that is not equipped with enough installed memory, or ram capacity.
To how many programs or bits of software are running including programs that load on startup of windows.

If your system has 4Gb of memory add more physical memory.
If you have more than 4GB of memory ,check that you are using a 64 bit version of the windows OS.
Over a 32 bit version of the OS. 32 bit only supports 4GB of memory regaurdless of how much physical memory is fitted above 4GB.
https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sysdm_advancd_perform_change_vmpagefile.mspx?mfr=true

 

[theodore_3]

The executable file ntkrnlmp.exe.

Executed a command to store or retrieve data from a block of memory or memory address of main system ram.
Where it was outside of the windows cache and paging file.

The start or end point along with the length of the data exceeded the page file size.

And, or tried to access a part of the system memory reserved by a set hardware device in the system.
Or outside of the virtual memory paging file set in windows.
In english that is what it means.

So the driver returned an error, and terminated as a process in windows.

The causes can be memory leakage.
The system does not have enough physical memory.

The page file size setup for windows is too small in size.
And can be altered to prevent the error.

The common cause is when physical ram is very low, and windows has to resort to virtual memory space.
That you may experience on a system that is not equipped with enough installed memory, or ram capacity.
To how many programs or bits of software are running including programs that load on startup of windows.

If your system has 4Gb of memory add more physical memory.
If you have more than 4GB of memory ,check that you are using a 64 bit version of the windows OS.
Over a 32 bit version of the OS. 32 bit only supports 4GB of memory regaurdless of how much physical memory is fitted above 4GB.
https://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sysdm_advancd_perform_change_vmpagefile.mspx?mfr=true

i just double checked my specs and i am running windows 10 pro 64 bit with 32gb of ram any other thoughts?