Windows 7: Please Help! Multiple BSODs!

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


Loading Dump File [C:\Users\K\Desktop\031410-21044-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a55000 PsLoadedModuleList = 0xfffff800`02c92e50
Debug session time: Sun Mar 14 19:42:24.206 2010 (GMT-4)
System Uptime: 0 days 0:01:43.518
Loading Kernel Symbols
...............................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1E, {ffffffffc0000005, fffff80002af713e, 0, ffffffffffffffff}

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

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

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

KMODE_EXCEPTION_NOT_HANDLED (1e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80002af713e, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

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


EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.

FAULTING_IP: 
nt!MiGetPreviousNode+3e
fffff800`02af713e 488b4810        mov     rcx,qword ptr [rax+10h]

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cfd0e0
 ffffffffffffffff 

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0x1E

PROCESS_NAME:  sidebar.exe

CURRENT_IRQL:  0

LAST_CONTROL_TRANSFER:  from fffff80002b06a17 to fffff80002ac6f00

STACK_TEXT:  
fffff880`08122638 fffff800`02b06a17 : 00000000`0000001e ffffffff`c0000005 fffff800`02af713e 00000000`00000000 : nt!KeBugCheckEx
fffff880`08122640 fffff800`02ac6542 : fffff880`08122e18 00000000`00000000 fffff880`08122ec0 00000000`00000000 : nt! ?? ::FNODOBFM::`string'+0x460da
fffff880`08122ce0 fffff800`02ac4e4a : 00000000`05990000 fffff800`02aff36a 00000000`00000000 fffffa80`06c73b30 : nt!KiExceptionDispatch+0xc2
fffff880`08122ec0 fffff800`02af713e : fffff800`02b0888d 00000000`00000000 fffff880`08123118 fffff880`08123230 : nt!KiGeneralProtectionFault+0x10a
fffff880`08123058 fffff800`02b0888d : 00000000`00000000 fffff880`08123118 fffff880`08123230 fffff960`0008a975 : nt!MiGetPreviousNode+0x3e
fffff880`08123060 fffff800`02ac6153 : ffffffff`ffffffff fffff880`08123320 fffff880`08123388 00000000`00008000 : nt!NtFreeVirtualMemory+0x20d
fffff880`08123150 fffff800`02ac26f0 : fffff960`000c50f0 00000000`00000001 00000000`00000000 fffff900`c0a98690 : nt!KiSystemServiceCopyEnd+0x13
fffff880`081232e8 fffff960`000c50f0 : 00000000`00000001 00000000`00000000 fffff900`c0a98690 00000000`00000000 : nt!KiServiceLinkage
fffff880`081232f0 fffff960`000c544c : ffffffff`00000000 fffff880`00000000 fffff900`c0a98690 0000007f`00000000 : win32k!SURFACE::bDeleteSurface+0x3c8
fffff880`08123440 fffff960`0008661d : ffffffff`bd050f64 fffff900`c0a98690 ffffffff`bd050f64 00000000`0368ad70 : win32k!bDeleteSurface+0x34
fffff880`08123470 fffff800`02ac6153 : fffffa80`06cd3060 00000000`18010bb0 fffff900`c00bf001 00000000`00000000 : win32k!NtGdiDeleteObjectApp+0xd5
fffff880`081234a0 000007fe`ff93118a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`0368abd8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7fe`ff93118a


STACK_COMMAND:  kb

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

SYMBOL_STACK_INDEX:  8

SYMBOL_NAME:  win32k!SURFACE::bDeleteSurface+3c8

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: win32k

IMAGE_NAME:  win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  4a5bc5e0

FAILURE_BUCKET_ID:  X64_0x1E_win32k!SURFACE::bDeleteSurface+3c8

BUCKET_ID:  X64_0x1E_win32k!SURFACE::bDeleteSurface+3c8

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