Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\110610-20389-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e39000 PsLoadedModuleList = 0x82f81810
Debug session time: Sat Nov 6 06:23:21.913 2010 (UTC - 5:00)
System Uptime: 0 days 3:14:42.880
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 82ec3f21, 8ce13a94, 0}
Probably caused by : cdd.dll ( cdd!CGuardMutex::Enter+d )
Followup: MachineOwner
---------
0: 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: 82ec3f21, The address that the exception occurred at
Arg3: 8ce13a94, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+1a
82ec3f21 f00fba3000 lock btr dword ptr [eax],0
TRAP_FRAME: 8ce13a94 -- (.trap 0xffffffff8ce13a94)
ErrCode = 00000002
eax=00000000 ebx=8922207e ecx=00000000 edx=00000001 esi=00000000 edi=8560ea38
eip=82ec3f21 esp=8ce13b08 ebp=8ce13b28 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:
82ec3f21 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: firefox.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 963572c9 to 82ec3f21
STACK_TEXT:
8ce13b0c 963572c9 ffa0d018 9635a8d4 ffa0d018 nt!ExEnterCriticalRegionAndAcquireFastMutexUnsafe+0x1a
8ce13b14 9635a8d4 ffa0d018 00000000 00000000 cdd!CGuardMutex::Enter+0xd
8ce13b28 9635b7c7 0043bfef ffa0d018 fe7105d0 cdd!CddBitmap::RemoveFromCddBitmapList+0x28
8ce13b5c 96351753 ffa0d018 8ce13bfc 9618d50c cdd!CddBitmapHw::Release+0x7d
8ce13b68 9618d50c ffa0d018 00000002 8ce13c20 cdd!DrvDeleteDeviceBitmapEx+0x39
8ce13bfc 9618e920 00000001 00000000 fb051d03 win32k!SURFACE::bDeleteSurface+0x235
8ce13c10 96190e1d 00000001 00000001 fe7105d0 win32k!SURFREF::bDeleteSurface+0x14
8ce13c24 961905bd 00000f34 00000001 00000f34 win32k!vCleanupSurfaces+0x43
8ce13c44 9618c25a ffa85ba8 00000000 00000000 win32k!NtGdiCloseProcess+0xc5
8ce13c64 9618eb3f ffa85ba8 00000000 86b203c8 win32k!GdiProcessCallout+0x151
8ce13c80 83081b98 84fb8110 00000000 ad1bd2d7 win32k!W32pProcessCallout+0x5d
8ce13cfc 8309adc7 00000000 ffffffff 0017f918 nt!PspExitThread+0x46d
8ce13d24 82e7c44a ffffffff 00000000 0017f924 nt!NtTerminateProcess+0x1fa
8ce13d24 776d64f4 ffffffff 00000000 0017f924 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0017f924 00000000 00000000 00000000 00000000 0x776d64f4
STACK_COMMAND: kb
FOLLOWUP_IP:
cdd!CGuardMutex::Enter+d
963572c9 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
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\112610-16988-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e05000 PsLoadedModuleList = 0x82f4d810
Debug session time: Fri Nov 26 14:46:57.801 2010 (UTC - 5:00)
System Uptime: 0 days 2:02:32.768
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 961bbf11, 9a0c3b98, 0}
Probably caused by : win32k.sys ( win32k!HmgLockEx+67 )
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: 961bbf11, The address that the exception occurred at
Arg3: 9a0c3b98, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
win32k!HmgLockEx+67
961bbf11 0fb74f08 movzx ecx,word ptr [edi+8]
TRAP_FRAME: 9a0c3b98 -- (.trap 0xffffffff9a0c3b98)
ErrCode = 00000000
eax=84f6ac10 ebx=00000000 ecx=ffbbf000 edx=00000950 esi=ff800000 edi=00000000
eip=961bbf11 esp=9a0c3c0c ebp=9a0c3c30 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!HmgLockEx+0x67:
961bbf11 0fb74f08 movzx ecx,word ptr [edi+8] ds:0023:00000008=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 961bd68f to 961bbf11
STACK_TEXT:
9a0c3c30 961bd68f 00000000 96171966 fe7aa8e8 win32k!HmgLockEx+0x67
9a0c3c38 96171966 fe7aa8e8 9a0c3c70 9616cd17 win32k!HmgLock+0x7
9a0c3c44 9616cd17 00000000 00000000 fe7aa8e8 win32k!GreReferenceObject+0x16
9a0c3c54 9616cda6 4d120ede 00000001 00000000 win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x27
9a0c3c70 961bf730 4d120ede 4d120ede fe7aa8e8 win32k!SFMLOGICALSURFACE::DeInitialize+0x21
9a0c3c88 9616d313 fe7aa8e8 00000001 00000000 win32k!bhLSurfDestroyLogicalSurfaceObject+0x31
9a0c3cac 96171d88 ffb8b748 00000000 0c3c4c8e win32k!GreSfmCloseCompositorRef+0x8b
9a0c3d1c 82e4844a 4d120ede 00000008 00000000 win32k!NtGdiHLSurfSetInformation+0x110
9a0c3d1c 775c64f4 4d120ede 00000008 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
02e7f6e0 00000000 00000000 00000000 00000000 0x775c64f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!HmgLockEx+67
961bbf11 0fb74f08 movzx ecx,word ptr [edi+8]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!HmgLockEx+67
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c7dbbb5
FAILURE_BUCKET_ID: 0x8E_win32k!HmgLockEx+67
BUCKET_ID: 0x8E_win32k!HmgLockEx+67
Followup: MachineOwner
---------
Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\a\Minidump\D M P\120210-19531-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16617.x86fre.win7_gdr.100618-1621
Machine Name:
Kernel base = 0x82e4f000 PsLoadedModuleList = 0x82f97810
Debug session time: Thu Dec 2 13:35:29.010 2010 (UTC - 5:00)
System Uptime: 0 days 1:07:12.977
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 961dbf11, 9b71bb98, 0}
Probably caused by : win32k.sys ( win32k!HmgLockEx+67 )
Followup: MachineOwner
---------
0: 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: 961dbf11, The address that the exception occurred at
Arg3: 9b71bb98, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - <Unable to get error code text>
FAULTING_IP:
win32k!HmgLockEx+67
961dbf11 0fb74f08 movzx ecx,word ptr [edi+8]
TRAP_FRAME: 9b71bb98 -- (.trap 0xffffffff9b71bb98)
ErrCode = 00000000
eax=84fd1d48 ebx=00000000 ecx=ffbbf000 edx=00000a08 esi=ff800000 edi=00000000
eip=961dbf11 esp=9b71bc0c ebp=9b71bc30 iopl=0 nv up ei pl zr na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010246
win32k!HmgLockEx+0x67:
961dbf11 0fb74f08 movzx ecx,word ptr [edi+8] ds:0023:00000008=????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: dwm.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 961dd68f to 961dbf11
STACK_TEXT:
9b71bc30 961dd68f 00000000 96191966 fdebc370 win32k!HmgLockEx+0x67
9b71bc38 96191966 fdebc370 9b71bc70 9618cd17 win32k!HmgLock+0x7
9b71bc44 9618cd17 00000000 00000000 fdebc370 win32k!GreReferenceObject+0x16
9b71bc54 9618cda6 aa121666 00000001 00000000 win32k!SFMLOGICALSURFACE::OwnsSurfaceCleanup+0x27
9b71bc70 961df730 aa121666 aa121666 fdebc370 win32k!SFMLOGICALSURFACE::DeInitialize+0x21
9b71bc88 9618d313 fdebc370 00000001 00000000 win32k!bhLSurfDestroyLogicalSurfaceObject+0x31
9b71bcac 96191d88 ffb8b748 00000000 0d43cc84 win32k!GreSfmCloseCompositorRef+0x8b
9b71bd1c 82e9244a aa121666 00000008 00000000 win32k!NtGdiHLSurfSetInformation+0x110
9b71bd1c 76f764f4 aa121666 00000008 00000000 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0163f708 00000000 00000000 00000000 00000000 0x76f764f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!HmgLockEx+67
961dbf11 0fb74f08 movzx ecx,word ptr [edi+8]
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!HmgLockEx+67
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c7dbbb5
FAILURE_BUCKET_ID: 0x8E_win32k!HmgLockEx+67
BUCKET_ID: 0x8E_win32k!HmgLockEx+67
Followup: MachineOwner
---------