Two BSOD caused by "ntoskrnl.exe" on Windows 7 64 bit

ok.. i will remove avast this time! thank you!

well, i removed avast but my pc BSOD again.. I noticed that the BSODs only appear when i'm playing zinga poker or other stupid games in facebook.. they use flash player.. anyway tonight I will run memtest again :)

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 50, {fffffa800c86a810, 0, fffff80002aba3fa, 2}


Could not read faulting driver name
Probably caused by : win32k.sys ( win32k!SURFACE::bDeleteSurface+3c8 )

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

3: 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: fffffa800c86a810, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80002aba3fa, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cc10e0
 fffffa800c86a810 

FAULTING_IP: 
nt!MiDeleteVirtualAddresses+481
fffff800`02aba3fa 448b2b          mov     r13d,dword ptr [rbx]

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  6

DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

BUGCHECK_STR:  0x50

PROCESS_NAME:  plugin-contain

CURRENT_IRQL:  0

TRAP_FRAME:  fffff88006929130 -- (.trap 0xfffff88006929130)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000042ce2b rbx=0000000000000000 rcx=0000058000000000
rdx=0000000000000022 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80002aba3fa rsp=fffff880069292c0 rbp=000000000c224000
 r8=0000000000000001  r9=fffffa8003e2ab30 r10=0000000fffffffff
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe cy
nt!MiDeleteVirtualAddresses+0x481:
fffff800`02aba3fa 448b2b          mov     r13d,dword ptr [rbx] ds:00000000`00000000=????????
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002b088f2 to fffff80002a89740

STACK_TEXT:  
fffff880`06928fc8 fffff800`02b088f2 : 00000000`00000050 fffffa80`0c86a810 00000000`00000000 fffff880`06929130 : nt!KeBugCheckEx
fffff880`06928fd0 fffff800`02a8782e : 00000000`00000000 fffffa80`0c86a810 00000000`00000000 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x40ec0
fffff880`06929130 fffff800`02aba3fa : 00000000`00000000 fffff680`00060ff8 fffffa80`03e2ab30 00000000`00000000 : nt!KiPageFault+0x16e
fffff880`069292c0 fffff800`02acb0da : 00000000`00000000 00000000`0c24bfff fffffa80`00000000 fffffa80`03e2ab30 : nt!MiDeleteVirtualAddresses+0x481
fffff880`06929480 fffff800`02a88993 : ffffffff`ffffffff fffff880`06929740 fffff880`069297a8 00000000`00008000 : nt!NtFreeVirtualMemory+0x5ca
fffff880`06929570 fffff800`02a84f30 : fffff960`001b51d8 00000000`00000001 fffff900`c00bf010 fffff900`c1e0fcd0 : nt!KiSystemServiceCopyEnd+0x13
fffff880`06929708 fffff960`001b51d8 : 00000000`00000001 fffff900`c00bf010 fffff900`c1e0fcd0 00000000`00000001 : nt!KiServiceLinkage
fffff880`06929710 fffff960`001bd5b9 : 00000000`00000000 fffff880`00000001 fffff900`c1e0fcd0 fffff900`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`06929860 fffff960`001b4a10 : 00000000`00000808 fffff880`06929c00 fffff900`c22b4ce0 fffff960`00000000 : win32k!NtGdiCloseProcess+0x2c9
fffff880`069298c0 fffff960`001b4157 : fffffa80`05ac6000 fffff880`06929c20 fffffa80`04128b60 fffff880`06929c20 : win32k!GdiProcessCallout+0x200
fffff880`06929940 fffff800`02d6ea01 : fffffa80`05ac6090 00000000`00000000 00000000`00000000 fffffa80`04128b60 : win32k!W32pProcessCallout+0x6b
fffff880`06929970 fffff800`02d47635 : 00000000`c0000005 00000000`c0000001 00000000`78457300 fffffa80`04141060 : nt!PspExitThread+0x561
fffff880`06929a30 fffff800`02a661db : 00000000`00000100 fffffa80`04128c20 00000000`00000001 fffff800`02a90b9d : nt!PsExitSpecialApc+0x1d
fffff880`06929a60 fffff800`02a66620 : 00000000`00000000 fffff880`06929ae0 fffff800`02d4774c 00000000`00000001 : nt!KiDeliverApc+0x2eb
fffff880`06929ae0 fffff800`02a88a37 : fffffa80`04128b60 00000000`000004d4 fffff880`06929bf8 fffffa80`03ef80e0 : nt!KiInitiateUserApc+0x70
fffff880`06929c20 00000000`732d2dd9 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9c
00000000`0827ec68 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x732d2dd9


STACK_COMMAND:  kb

FOLLOWUP_IP: 
win32k!SURFACE::bDeleteSurface+3c8
fffff960`001b51d8 e9b0010000      jmp     win32k!SURFACE::bDeleteSurface+0x57d (fffff960`001b538d)

SYMBOL_STACK_INDEX:  7

SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+3c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4c1c483f

FAILURE_BUCKET_ID:  X64_0x50_win32k!SURFACE::bDeleteSurface+3c8

BUCKET_ID:  X64_0x50_win32k!SURFACE::bDeleteSurface+3c8

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

Memtest does look like a very good idea at this stage.

I runned memtest for 8 pass... no error!

What is your memory set up? (as in # Sticks and type)

Also, what PSU are you using?

I have 2 stick of A-Data technology (ADQVE1B16) DDR2 800 2GX16

and I can't remember my PSU.. if windows BSOD again I'll look inside the case

anyway, i re-installed mozilla and flash player.. and if I play zinga poker windows doesn't crash, at the moment.... xD

BSOD again -.-"

here dump file..

fede0411 said:

BSOD again -.-"

here dump file..

Points towards Firefox, but could be your flash player.

zigzag3143 said:

fede0411 said:

BSOD again -.-"

here dump file..

Points towards Firefox, but could be your flash player.

But this time firefox was closed, nothing was running..