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\DMP\012611-15241-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 = 0x82a1f000 PsLoadedModuleList = 0x82b67810
Debug session time: Wed Jan 26 10:32:13.142 2011 (UTC - 5:00)
System Uptime: 0 days 1:36:30.030
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, 9704cca2, a704fc10, 0}
Probably caused by : win32k.sys ( win32k!MulGetBitmapForDisplayDevice+10 )
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: 9704cca2, The address that the exception occurred at
Arg3: a704fc10, 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:
win32k!MulGetBitmapForDisplayDevice+10
9704cca2 f7402400000200 test dword ptr [eax+24h],20000h
TRAP_FRAME: a704fc10 -- (.trap 0xffffffffa704fc10)
ErrCode = 00000000
eax=ffffffff ebx=ffb8f748 ecx=a704fc5c edx=00000001 esi=fe06e008 edi=37050889
eip=9704cca2 esp=a704fc84 ebp=a704fc88 iopl=0 nv up ei ng nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010286
win32k!MulGetBitmapForDisplayDevice+0x10:
9704cca2 f7402400000200 test dword ptr [eax+24h],20000h ds:0023:00000023=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: iexplore.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 96f439f4 to 9704cca2
STACK_TEXT:
a704fc88 96f439f4 ffffffff ffb8f748 37050889 win32k!MulGetBitmapForDisplayDevice+0x10
a704fcc0 96f3cc5e 06011606 37050889 fe86f468 win32k!GreSelectRedirectionBitmap+0x61
a704fcfc 96f3cdb2 fe86f468 00000000 0001401a win32k!_GetDCEx+0x571
a704fd10 96f3ce41 fe86f468 0005068a 0289d584 win32k!_GetDC+0x3a
a704fd28 82a6244a 0005068a 0289d594 778964f4 win32k!NtUserGetDC+0x86
a704fd28 778964f4 0005068a 0289d594 778964f4 nt!KiFastCallEntry+0x12a
WARNING: Frame IP not in any known module. Following frames may be wrong.
0289d594 00000000 00000000 00000000 00000000 0x778964f4
STACK_COMMAND: kb
FOLLOWUP_IP:
win32k!MulGetBitmapForDisplayDevice+10
9704cca2 f7402400000200 test dword ptr [eax+24h],20000h
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: win32k!MulGetBitmapForDisplayDevice+10
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: win32k
IMAGE_NAME: win32k.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4cbe5b31
FAILURE_BUCKET_ID: 0x8E_win32k!MulGetBitmapForDisplayDevice+10
BUCKET_ID: 0x8E_win32k!MulGetBitmapForDisplayDevice+10
Followup: MachineOwner
---------