win 7 BSOD while using Chrome

Memtest86+

Run Memtest86+ for at least 8-10 passes. It may take up to 20 passes to find problems. Make sure to run it once after the system has been on for a few hours and is warm, and then also run it again when the system has been off for a few hours and is cold. How to Test and Diagnose RAM Issues with Memtest86+

   Note

Pay close attention to part 3 of the tutorial in order to rule the faulty RAM stick out.

   Tip

Do this test overnight.

BSOD BUGCHECK SUMMARY

Code:

Built by: 7601.18113.amd64fre.win7sp1_gdr.130318-1533
Debug session time: Sun Jun  9 11:47:14.914 2013 (UTC + 6:00)
System Uptime: 1 days 15:30:50.147
BugCheck 1A, {41790, fffffa800705ca80, ffff, 0}
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )
BUGCHECK_STR:  0x1a_41790
PROCESS_NAME:  chrome.exe
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1A, {41790, fffffa800705ca80, ffff, 0}

Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

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

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: fffffa800705ca80
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 fffff80002ef0d40 to fffff80002e7fc00

STACK_TEXT:  
fffff880`227f8128 fffff800`02ef0d40 : 00000000`0000001a 00000000`00041790 fffffa80`0705ca80 00000000`0000ffff : nt!KeBugCheckEx
fffff880`227f8130 fffff800`02e6c3ff : fffffa80`00000000 00000000`09ff9fff 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x35084
fffff880`227f82f0 fffff800`02e7ee93 : ffffffff`ffffffff fffff880`227f85c0 fffff880`227f8628 00000000`00008000 : nt!NtFreeVirtualMemory+0x61f
fffff880`227f83f0 fffff800`02e7b450 : fffff960`000e74b4 00000000`00000001 00000000`00000000 fffff900`c1fe2010 : nt!KiSystemServiceCopyEnd+0x13
fffff880`227f8588 fffff960`000e74b4 : 00000000`00000001 00000000`00000000 fffff900`c1fe2010 00000000`00000001 : nt!KiServiceLinkage
fffff880`227f8590 fffff960`000ef739 : 00000000`00000000 fffff880`00000001 fffff900`c1fe2010 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`227f86e0 fffff960`000e6cf0 : 00000000`000031e4 fffff880`227f8a00 fffff900`c3f393d0 fffff880`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`227f8740 fffff960`000e6417 : 00000000`00000000 fffff880`227f8ae0 fffffa80`0d3a2b50 00000000`00000000 : win32k!GdiProcessCallout+0x200
fffff880`227f87c0 fffff800`03155c21 : 00000000`00000000 00000000`00000000 00000000`00000000 fffffa80`0d3a2b00 : win32k!W32pProcessCallout+0x6b
fffff880`227f87f0 fffff800`0313bdbd : 00000000`c0000005 00000000`c0000001 00000000`78457300 fffffa80`10112b50 : nt!PspExitThread+0x4d1
fffff880`227f88f0 fffff800`02e7271a : 00000000`00000100 fffffa80`0d3a2c10 00000000`00000001 fffff800`02e7581d : nt!PsExitSpecialApc+0x1d
fffff880`227f8920 fffff800`02e72a60 : 00000000`00000246 fffff880`227f89a0 fffff800`0313bd30 00000000`00000001 : nt!KiDeliverApc+0x2ca
fffff880`227f89a0 fffff800`02e7ef37 : fffffa80`0d3a2b50 00000000`0000023c fffff880`227f8ab8 fffffa80`1139a880 : nt!KiInitiateUserApc+0x70
fffff880`227f8ae0 00000000`72e22e09 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`03e2ee78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x72e22e09


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  5

SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+3c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5164dccb

FAILURE_BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

BUCKET_ID:  X64_0x1a_41790_win32k!SURFACE::bDeleteSurface+3c8

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