Windows 7 Help Forums - View Single Post - Solved BSOD playing Mirrors Edge, **STOP: 0x0000003B
View Single Post
12 Sep 2011  
N3urON

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by seth500 View Post
Please run memtest86 on you computer via this guide:
RAM - Test with Memtest86+

Also please uninstall sptd.sys from your system this is a major cause of BSOD's please download and run this tool and click uninstall:
DuplexSecure - Downloads

Please use magiciso's magic disk instead: Freeware MagicISO Virtual CD/DVD-ROM(MagicDisc) Overview

Code:
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\Administrator\Downloads\Windows_NT6_BSOD_jcgriff2\083111-41933-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\SymCache*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16841.amd64fre.win7_gdr.110622-1503
Machine Name:
Kernel base = 0xfffff800`03060000 PsLoadedModuleList = 0xfffff800`0329de70
Debug session time: Tue Aug 30 20:56:01.012 2011 (UTC - 6:00)
System Uptime: 0 days 9:37:51.214
Loading Kernel Symbols
...............................................................
................................................................
.............................................................
Loading User Symbols
Loading unloaded module list
..........
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c2c93030, 0, fffff9600030f80d, 0}


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

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

2: 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: fffff900c2c93030, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff9600030f80d, 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 fffff800033080e0
 fffff900c2c93030 

FAULTING_IP: 
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d
fffff960`0030f80d 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:  fffff880097c38e0 -- (.trap 0xfffff880097c38e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000011 rbx=0000000000000000 rcx=fffff900c00f8190
rdx=000000007d1221d4 rsi=0000000000000000 rdi=0000000000000000
rip=fffff9600030f80d rsp=fffff880097c3a70 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000410 r10=fffff80003060000
r11=0000000000000022 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x2d:
fffff960`0030f80d 488b4f20        mov     rcx,qword ptr [rdi+20h] ds:8190:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80003150df4 to fffff800030d05c0

STACK_TEXT:  
fffff880`097c3778 fffff800`03150df4 : 00000000`00000050 fffff900`c2c93030 00000000`00000000 fffff880`097c38e0 : nt!KeBugCheckEx
fffff880`097c3780 fffff800`030ce6ae : 00000000`00000000 fffff900`c00f8190 fffffa80`35616c00 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x426f7
fffff880`097c38e0 fffff960`0030f80d : 00000000`00000000 00000000`7d1221d4 00000000`7d1221d4 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`097c3a70 fffff960`0030ed1e : fffff900`c00f8190 00000000`00000000 000021d4`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x2d
fffff880`097c3aa0 fffff960`0030fc23 : 00000000`00000000 00000000`7d1221d4 fffff900`c00f8190 00000000`0bb7507c : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`097c3ae0 fffff960`0026c667 : 00000000`00000000 fffff900`c00bf010 fffff900`c00f8190 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`097c3b20 fffff960`0028d8fc : 00000000`00000001 00000000`00000001 fffff880`097c3c60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`097c3b60 fffff800`030cf813 : fffffa80`046d7b60 fffff880`097c3c60 00000000`00000040 fffffa80`00000000 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`097c3be0 000007fe`fed94efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0976f838 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fed94efa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d
fffff960`0030f80d 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:  4df2d94e

FAILURE_BUCKET_ID:  X64_0x50_win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d

BUCKET_ID:  X64_0x50_win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d

Followup: MachineOwner
---------
Well,i did almost all what u sayd,i couldn't run the ram test with the tool you gave me but,i tested it with ePSA Pre-Boot System Assesment tool,i just found it in the boot menu while tyring to boot the software you gave me.
Anyway looks like no BSOD for today,i played mirrors edge..and other games,and nothing happend.
I'll report news in about couple days and if i'm clean for one week i'll mark the thread as solved. By the way thank you set!
My System SpecsSystem Spec