Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\013111-17472-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82c05000 PsLoadedModuleList = 0x82d4d810
Debug session time: Mon Jan 31 09:38:30.928 2011 (GMT-5)
System Uptime: 0 days 3:32:14.130
Loading Kernel Symbols
...............................................................
................................................................
........................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 82c8ff21, bafefa94, 0}
Probably caused by : cdd.dll ( cdd!CGuardMutex::Enter+d )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82c8ff21, The address that the exception occurred at
Arg3: bafefa94, Trap Frame
Arg4: 00000000
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!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+1a
82c8ff21 f00fba3000 lock btr dword ptr [eax],0
TRAP_FRAME: bafefa94 -- (.trap 0xffffffffbafefa94)
ErrCode = 00000002
eax=00000000 ebx=89e0a07e ecx=00000000 edx=00000001 esi=00000000 edi=854c2838
eip=82c8ff21 esp=bafefb08 ebp=bafefb28 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x1a:
82c8ff21 f00fba3000 lock btr dword ptr [eax],0 ds:0023:00000000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: SC2.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 968672c9 to 82c8ff21
STACK_TEXT:
bafefb0c 968672c9 ff1be018 9686a8d4 ff1be018 nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x1a
bafefb14 9686a8d4 ff1be018 00000000 00000000 cdd!CGuardMutex::Enter+0xd
bafefb28 9686b7c7 0043bfef ff1be018 fd61b288 cdd!CddBitmap::RemoveFromCddBitmapList+0x28
bafefb5c 96861753 ff1be018 bafefbfc 96a5d47c cdd!CddBitmapHw::Release+0x7d
bafefb68 96a5d47c ff1be018 00000002 bafefc20 cdd!DrvDeleteDeviceBitmapEx+0x39
bafefbfc 96a5e890 00000001 00000000 8e051880 win32k!SURFACE::bDeleteSurface+0x235
bafefc10 96a60d8d 00000001 00000001 fd61b288 win32k!SURFREF::bDeleteSurface+0x14
bafefc24 96a6052d 0000080c 00000001 0000080c win32k!vCleanupSurfaces+0x43
bafefc44 96a5c1ca ff59b260 00000000 00000000 win32k!NtGdiCloseProcess+0xc5
bafefc64 96a5eaaf ff59b260 00000000 86f986b0 win32k!GdiProcessCallout+0x151
bafefc80 82e4db98 85618d40 00000000 a4db267d win32k!W32pProcessCallout+0x5d
bafefcfc 82e66dc7 00000000 ffffffff 0012fe8c nt!PspExitThread+0x46d
bafefd24 82c4844a ffffffff 00000000 0012fe98 nt!NtTerminateProcess+0x1fa
bafefd24 77c764f4 ffffffff 00000000 0012fe98 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fe98 00000000 00000000 00000000 00000000 0x77c764f4
STACK_COMMAND: kb
FOLLOWUP_IP:
cdd!CGuardMutex::Enter+d
968672c9 c7460401000000 mov dword ptr [esi+4],1
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: cdd!CGuardMutex::Enter+d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bd992
FAILURE_BUCKET_ID: 0x8E_cdd!CGuardMutex::Enter+d
BUCKET_ID: 0x8E_cdd!CGuardMutex::Enter+d
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 82c8ff21, The address that the exception occurred at
Arg3: bafefa94, Trap Frame
Arg4: 00000000
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!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+1a
82c8ff21 f00fba3000 lock btr dword ptr [eax],0
TRAP_FRAME: bafefa94 -- (.trap 0xffffffffbafefa94)
ErrCode = 00000002
eax=00000000 ebx=89e0a07e ecx=00000000 edx=00000001 esi=00000000 edi=854c2838
eip=82c8ff21 esp=bafefb08 ebp=bafefb28 iopl=0 nv up ei ng nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010282
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x1a:
82c8ff21 f00fba3000 lock btr dword ptr [eax],0 ds:0023:00000000=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: SC2.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 968672c9 to 82c8ff21
STACK_TEXT:
bafefb0c 968672c9 ff1be018 9686a8d4 ff1be018 nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x1a
bafefb14 9686a8d4 ff1be018 00000000 00000000 cdd!CGuardMutex::Enter+0xd
bafefb28 9686b7c7 0043bfef ff1be018 fd61b288 cdd!CddBitmap::RemoveFromCddBitmapList+0x28
bafefb5c 96861753 ff1be018 bafefbfc 96a5d47c cdd!CddBitmapHw::Release+0x7d
bafefb68 96a5d47c ff1be018 00000002 bafefc20 cdd!DrvDeleteDeviceBitmapEx+0x39
bafefbfc 96a5e890 00000001 00000000 8e051880 win32k!SURFACE::bDeleteSurface+0x235
bafefc10 96a60d8d 00000001 00000001 fd61b288 win32k!SURFREF::bDeleteSurface+0x14
bafefc24 96a6052d 0000080c 00000001 0000080c win32k!vCleanupSurfaces+0x43
bafefc44 96a5c1ca ff59b260 00000000 00000000 win32k!NtGdiCloseProcess+0xc5
bafefc64 96a5eaaf ff59b260 00000000 86f986b0 win32k!GdiProcessCallout+0x151
bafefc80 82e4db98 85618d40 00000000 a4db267d win32k!W32pProcessCallout+0x5d
bafefcfc 82e66dc7 00000000 ffffffff 0012fe8c nt!PspExitThread+0x46d
bafefd24 82c4844a ffffffff 00000000 0012fe98 nt!NtTerminateProcess+0x1fa
bafefd24 77c764f4 ffffffff 00000000 0012fe98 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0012fe98 00000000 00000000 00000000 00000000 0x77c764f4
STACK_COMMAND: kb
FOLLOWUP_IP:
cdd!CGuardMutex::Enter+d
968672c9 c7460401000000 mov dword ptr [esi+4],1
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: cdd!CGuardMutex::Enter+d
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: cdd
IMAGE_NAME: cdd.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5bd992
FAILURE_BUCKET_ID: 0x8E_cdd!CGuardMutex::Enter+d
BUCKET_ID: 0x8E_cdd!CGuardMutex::Enter+d
Followup: MachineOwner
---------