Blue screen problem

You are welcome. Helping others is why we are here. :)

This is an error code 50, PAGE_FAULT_IN_NONPAGED_AREA - usual causes are Defective hardware (particularly memory - but not just RAM), Faulty system service, Antivirus, Device driver, NTFS corruption, BIOS.

Code:

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


Loading Dump File [C:\Users\Owner\Downloads\082910-17331-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*c:\symbols*Symbol information
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.amd64fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0xfffff800`02a11000 PsLoadedModuleList = 0xfffff800`02c4ee50
Debug session time: Sun Aug 29 01:08:39.128 2010 (GMT-4)
System Uptime: 0 days 3:26:04.970
Loading Kernel Symbols
...............................................................
................................................................
....................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffff900c20089b0, 0, fffff960002bc88d, 0}


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

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

1: 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: fffff900c20089b0, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff960002bc88d, 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 fffff80002cb90e0
 fffff900c20089b0 

FAULTING_IP: 
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d
fffff960`002bc88d 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:  fffff8800554a8e0 -- (.trap 0xfffff8800554a8e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000011 rbx=0000000000000000 rcx=fffff900c2190f30
rdx=0000000006120e50 rsi=0000000000000000 rdi=0000000000000000
rip=fffff960002bc88d rsp=fffff8800554aa70 rbp=0000000000000001
 r8=0000000000000000  r9=0000000000000410 r10=fffff80002a11000
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`002bc88d 488b4f20        mov     rcx,qword ptr [rdi+20h] ds:0f30:00000000`00000020=????????????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b01f14 to fffff80002a81740

STACK_TEXT:  
fffff880`0554a778 fffff800`02b01f14 : 00000000`00000050 fffff900`c20089b0 00000000`00000000 fffff880`0554a8e0 : nt!KeBugCheckEx
fffff880`0554a780 fffff800`02a7f82e : 00000000`00000000 fffff900`c2190f30 fffffa80`35616c00 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x42837
fffff880`0554a8e0 fffff960`002bc88d : 00000000`00000000 00000000`06120e50 00000000`06120e50 00000000`00000001 : nt!KiPageFault+0x16e
fffff880`0554aa70 fffff960`002bbd9e : fffff900`c2190f30 00000000`00000000 00000e50`624d4653 00000000`0000001d : win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x2d
fffff880`0554aaa0 fffff960`002bcca3 : 00000000`00000000 00000000`06120e50 fffff900`c2190f30 00000000`070bb3fc : win32k!SFMLOGICALSURFACE::DeInitialize+0x4e
fffff880`0554aae0 fffff960`00219777 : 00000000`00000000 fffff900`c00bf010 fffff900`c2190f30 00000000`00000020 : win32k!bhLSurfDestroyLogicalSurfaceObject+0x4b
fffff880`0554ab20 fffff960`0023aa50 : 00000000`00000001 00000000`00000001 fffff880`0554ac60 00000000`00000000 : win32k!GreSfmCloseCompositorRef+0x10f
fffff880`0554ab60 fffff800`02a80993 : fffffa80`05b55060 fffff880`0554ac60 00000000`00000020 fffffa80`05b3e9c0 : win32k!NtGdiHLSurfSetInformation+0x1a8
fffff880`0554abe0 000007fe`fdd54efa : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`01d2f728 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`fdd54efa


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d
fffff960`002bc88d 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:  4c1c483f

FAILURE_BUCKET_ID:  X64_0x50_win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d

BUCKET_ID:  X64_0x50_win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+2d

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

Let's test your RAM using Memtest 86+. Read the tutorial below and follow the instructions. If you have any questions, post back. Let us know the results.

RAM - Test with Memtest86+

I also find a very old driver on your system. This is an XP driver. It could be the cause of your problem

RTCore64.sys Wed May 25 02:39:12 2005 - RivaTuner/EVGA Precision RivaTuner

Uninstall this tuner; it is obsolete. You can try to update it to version that is certified Win 7 compatible.

Thanks!!i tested RAM by Memtest86+ and this my pics:).
When i testing pass 6,i eject my CD(it's an accident)then i insert it again.So Memtest86 can run after i do that?
I install RivasTuner then uninstall it

Hey there, this is me Tuan, and I'm from Vietnam. I just got back to states today.

Based on the result, it looks like either your RAM is defective, or motherboard slots, or it can be compatibility issue. Just remember, any time Memtest reports errors, it can be either bad RAM or a bad motherboard slot. Test the sticks individually, and if you find a good one, test it in all slots. If all individual sticks and slots are ok

Hi, John and welcome to the forum. Please read and follow the instructions in the link below and start a new thread. We will be glad to help you. It gets too confusing to try to work with two separate problems in the same thread.

https://www.sevenforums.com/crashes-d...tructions.html