BSOD, High memory usage programs, Memory_management

tezz311 said:

When I'm playing armed assualt 2 operation arrowhead (when it mostly happens) my computer will crash giving me a memory_management error I'm not sure how to find more details about the errors specifically. all of my information is in the files attached :)

Hi Mate,

The dump files are missing. Go to C:\Windows\Minidump and upload the files here.

Hello there!

Run a complete Hardware Diagnostic : Hardware Diagnostic | Captain Debugger both RAM & Hard drive

Bugcheck:

Code:

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041790, A page table page has been corrupted. On a 64 bit OS, parameter 2
	contains the address of the PFN for the corrupted page table page.
	On a 32 bit OS, parameter 2 contains a pointer to the number of used
	PTEs, and parameter 3 contains the number of used PTEs.
Arg2: fffffa8003c2c910
Arg3: 000000000000ffff
Arg4: 0000000000000000

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


BUGCHECK_STR:  0x1a_41790

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  chrome.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002b44e10 to fffff80002ad3c40

STACK_TEXT:  
fffff880`040eb128 fffff800`02b44e10 : 00000000`0000001a 00000000`00041790 fffffa80`03c2c910 00000000`0000ffff : nt!KeBugCheckEx
fffff880`040eb130 fffff800`02ac042f : fffffa80`00000000 00000000`065f7fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`040eb2f0 fffff800`02ad2ed3 : ffffffff`ffffffff fffff880`040eb5c0 fffff880`040eb628 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`040eb3f0 fffff800`02acf490 : fffff960`000d70e4 00000000`00000001 00000000`00000000 fffff900`c3471cc0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`040eb588 fffff960`000d70e4 : 00000000`00000001 00000000`00000000 fffff900`c3471cc0 00000000`00000001 : nt!KiServiceLinkage
fffff880`040eb590 fffff960`000df389 : 00000000`00000000 fffff880`00000001 fffff900`c3471cc0 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`040eb6e0 fffff960`000d6920 : 00000000`0000048c fffff880`040eba00 fffff900`c36f9010 fffff880`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`040eb740 fffff960`000d605f : 00000000`00000000 fffff880`040ebae0 fffffa80`0fc5a760 00000000`00000000 : win32k!GdiProcessCallout+0x200
fffff880`040eb7c0 fffff800`02dabfc1 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0fc5a700 : win32k!W32pProcessCallout+0x6b
fffff880`040eb7f0 fffff800`02d9215d : 00000000`c0000005 00000000`c0000001 fffffa80`78457300 fffffa80`0e29ab50 : nt!PspExitThread+0x4d1
fffff880`040eb8f0 fffff800`02ac675a : 00000000`00000100 fffffa80`0fc5a820 00000000`00000001 fffff800`02ac985d : nt!PsExitSpecialApc+0x1d
fffff880`040eb920 fffff800`02ac6aa0 : 00000000`00000246 fffff880`040eb9a0 fffff800`02d920d0 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`040eb9a0 fffff800`02ad2f77 : fffffa80`0fc5a760 00000000`000001c0 00000000`00000000 fffffa80`0ec628b0 : nt!KiInitiateUserApc+0x70
fffff880`040ebae0 00000000`74f82e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`02a3eb28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x74f82e09


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SURFACE::bDeleteSurface+3c8
fffff960`000d70e4 e9b0010000      jmp     win32k!SURFACE::bDeleteSurface+0x57d (fffff960`000d7299)

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+3c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50e64bda

FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

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