Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\120310-17534-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\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 = 0x82c4a000 PsLoadedModuleList = 0x82d92810
Debug session time: Fri Dec 3 19:22:42.931 2010 (GMT-5)
System Uptime: 0 days 10:33:45.555
Loading Kernel Symbols
...............................................................
................................................................
.............................
Loading User Symbols
Loading unloaded module list
......
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for atikmdag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c000001d, 926f6b46, 97ff9798, 0}
*** WARNING: Unable to verify timestamp for atikmpag.sys
*** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
Probably caused by : atikmdag.sys ( atikmdag+2bdb46 )
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: c000001d, The exception code that was not handled
Arg2: 926f6b46, The address that the exception occurred at
Arg3: 97ff9798, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc000001d - {EXCEPTION} Illegal Instruction An attempt was made to execute an illegal instruction.
FAULTING_IP:
atikmdag+2bdb46
926f6b46 0fb7d2 movzx edx,dx
TRAP_FRAME: 97ff9798 -- (.trap 0xffffffff97ff9798)
ErrCode = 00000000
eax=00000000 ebx=00000000 ecx=000005d2 edx=00000068 esi=86f8c968 edi=00000000
eip=926f6b46 esp=97ff980c ebp=97ff9814 iopl=0 nv up ei pl nz na po nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00010202
atikmdag+0x2bdb46:
926f6b46 0fb7d2 movzx edx,dx
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x8E
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from 926f6251 to 926f6b46
FAILED_INSTRUCTION_ADDRESS:
atikmdag+2bdb46
926f6b46 0fb7d2 movzx edx,dx
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
97ff9814 926f6251 00000000 00000000 000005d2 atikmdag+0x2bdb46
97ff983c 926f6010 000005d2 00000068 00000000 atikmdag+0x2bd251
97ff9860 926ecdbd 00000000 97ff9940 97ff9900 atikmdag+0x2bd010
97ff987c 926d471e 97ff9940 97ff9900 97ff9940 atikmdag+0x2b3dbd
97ff9894 92447855 97ff9900 87158940 00000000 atikmdag+0x29b71e
97ff98b0 91a77670 871588c0 97ff9940 87fe6000 atikmdag+0xe855
97ff98d4 92adec3f 871588c0 97ff9940 87fe6000 atikmpag+0x5670
97ff98fc 92adeb93 97ff9940 00000068 ffb88010 dxgkrnl+0x2ac3f
97ff9928 9867d6b7 87fe6000 97ff9940 00000068 dxgkrnl+0x2ab93
97ff9950 987d9d7d ffb7c018 000005d2 00000068 cdd!DrvMovePointer+0xd3
97ff9974 987dd56d ffb92748 000005d2 00000068 win32k!vMovePointer+0x5d
97ff99b4 988ad858 00b92748 000005d2 00000068 win32k!GreMovePointer+0x120
97ff99f4 9887cb44 000005d2 00000068 00000000 win32k!xxxMoveEventAbsolute+0x17f
97ff9a2c 9887c9c5 00000000 8619b960 97ff9a84 win32k!ProcessMouseInput+0x16f
97ff9a3c 82cf2027 ffa21eb0 ffa21ed8 00000000 win32k!InputApc+0x4e
97ff9a84 82cb8b0d 00000000 00000000 00000000 nt!KiDeliverApc+0x17f
97ff9ac8 82cb7423 8828f458 8829c538 8829c634 nt!KiSwapThread+0x24e
97ff9af0 82cb36ef 8829c538 8829c5f8 00000000 nt!KiCommitThreadWait+0x1df
97ff9c68 9882dc85 00000002 87a12120 00000001 nt!KeWaitForMultipleObjects+0x535
97ff9cc0 98798fff 00000001 87a12120 987a2838 win32k!xxxMsgWaitForMultipleObjects+0xe9
97ff9d04 98798590 87a12120 00000001 989aeaa0 win32k!xxxDesktopThread+0x1b6
97ff9d18 9885c4d0 00000004 01bcf874 97ff9d34 win32k!xxxCreateSystemThreads+0x54
97ff9d28 82c8d44a 00000004 01bcf8b4 778d64f4 win32k!NtUserCallNoParam+0x1b
97ff9d28 778d64f4 00000004 01bcf8b4 778d64f4 nt!KiFastCallEntry+0x12a
01bcf8b4 00000000 00000000 00000000 00000000 0x778d64f4
STACK_COMMAND: kb
FOLLOWUP_IP:
atikmdag+2bdb46
926f6b46 0fb7d2 movzx edx,dx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+2bdb46
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4ca29872
FAILURE_BUCKET_ID: 0x8E_BAD_IP_atikmdag+2bdb46
BUCKET_ID: 0x8E_BAD_IP_atikmdag+2bdb46
Followup: MachineOwner
---------
