BSOD while on chrome and sometimes when shutting down comp 0x00000050

[skyler56]

Randomly started getting bsod's as far as I can tell it's pretty random while i'm on chrome and sometimes it will stop when I go to shut down.

 

[Arc]

Hi skyler56.

Install Service pack 1 and all other windows updates. Otherwise the system will remain vulnerable to threats.

[COLOR=Red]Windows 7 Kernel Version 7600 MP[/COLOR] (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.17273.amd64fre.win7_gdr.130318-1532

Learn how to install Windows 7 Service Pack 1 (SP1)
Service Pack and Update Center - Microsoft Windows

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

If it start showing errors/red lines, stop testing. A single error is enough to determine that something is going bad there.

If memtest does not show any error, enable Driver Verifier to monitor the drivers.
Driver Verifier - Enable and Disable
Run Driver Verifier for 24 hours or the occurrence of the next crash, whichever is earlier.

   Information

Why Driver Verifier:
It puts a stress on the drivers, ans so it makes the unstable drivers crash. Hopefully the driver that crashes is recorded in the memory dump.

How Can we know that DV is enabled:
It will make the system bit of slow, laggy.

   Warning

Before enabling DV, make it sure that you have earlier System restore points made in your computer. You can check it easily by using CCleaner looking at Tools > System Restore.

If there is no points, make a System Restore Point manually before enabling DV.

   Tip

• If you fail to get on the Desktop because of DV, Boot into Advanced Boot Options > Safe mode. Disable DV there. Now boot normally again, and try following the instruction of enabling DV again.
• If you cannot boot in Safe mode too, do a System Restore to a point you made earlier.

Let us know the results, with the subsequent crash dumps, if any.
_________________________________________________________________________________________

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c3000030, 0, fffff960002f260d, 0}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d )

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

6: 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: fffff900c3000030, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960002f260d, 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 fffff800034f40e0
 fffff900c3000030 

FAULTING_IP: 
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d
fffff960`002f260d 488b4f20        mov     rcx,qword ptr [rdi+20h]

MM_INTERNAL_CODE:  0

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  dwm.exe

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88009f628e0 -- (.trap 0xfffff88009f628e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000011 rbx=0000000000000000 rcx=fffff900c1f52b00
rdx=0000000021121af0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960002f260d rsp=fffff88009f62a70 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000410 r10=fffff8000324d000
r11=000000000000001f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x2d:
fffff960`002f260d 488b4f20        mov     rcx,qword ptr [rdi+20h] ds:2b00:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff8000333c694 to fffff800032bc880

STACK_TEXT:  
fffff880`09f62778 fffff800`0333c694 : 00000000`00000050 fffff900`c3000030 00000000`00000000 fffff880`09f628e0 : nt!KeBugCheckEx
fffff880`09f62780 fffff800`032ba96e : 00000000`00000000 fffff900`c1f52b00 00000000`00000000 fffff960`000cb98f : nt! ?? ::FNODOBFM::`string'+0x41db7
fffff880`09f628e0 fffff960`002f260d : 00000000`00000265 00000000`21121af0 00000000`21121af0 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`09f62a70 fffff960`002f1b1e : fffff900`c1f52b00 00000000`00000000 00001af0`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x2d
fffff880`09f62aa0 fffff960`002f2a23 : 00000000`00000000 00000000`21121af0 fffff900`c1f52b00 00000000`05590230 : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`09f62ae0 fffff960`0024f197 : 00000000`00000000 fffff900`c00b9010 fffff900`c1f52b00 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`09f62b20 fffff960`002706e8 : 00000800`00000001 00000000`00000001 fffff880`09f62c60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`09f62b60 fffff800`032bbad3 : fffffa80`097f02d0 00000000`0353f490 000007fe`f663d610 00000000`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`09f62be0 000007fe`feaf4efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0353eee8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`feaf4efa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d
fffff960`002f260d 488b4f20        mov     rcx,qword ptr [rdi+20h]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5130212e

FAILURE_BUCKET_ID:  X64_0x50_win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d

BUCKET_ID:  X64_0x50_win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d

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