Microsoft (R) Windows Debugger Version 6.11.0001.404 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\Jonathan\Desktop\042310-16848-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
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`02a17000 PsLoadedModuleList = 0xfffff800`02c54e50
Debug session time: Fri Apr 23 15:01:40.842 2010 (GMT-4)
System Uptime: 0 days 3:32:08.309
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
..........
Unable to load image 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 1000007E, {ffffffffc0000005, fffff88003e66051, fffff8800495d9f8, fffff8800495d260}
Probably caused by : atikmdag.sys ( atikmdag+24c051 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff88003e66051, The address that the exception occurred at
Arg3: fffff8800495d9f8, Exception Record Address
Arg4: fffff8800495d260, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
FAULTING_IP:
atikmdag+24c051
fffff880`03e66051 390a cmp dword ptr [rdx],ecx
EXCEPTION_RECORD: fffff8800495d9f8 -- (.exr 0xfffff8800495d9f8)
ExceptionAddress: fffff88003e66051 (atikmdag+0x000000000024c051)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff
CONTEXT: fffff8800495d260 -- (.cxr 0xfffff8800495d260)
rax=000000000000159f rbx=000000000000159f rcx=00000000d1ff159f
rdx=00802484c7fff6d0 rsi=fffff880040e1120 rdi=000000000000d1ff
rip=fffff88003e66051 rsp=fffff8800495dc30 rbp=0000000000000000
r8=000000000000005e r9=fffff8800495dc70 r10=0000240c01962e53
r11=0000000000017710 r12=0000240c0196620d r13=fffff880040e3280
r14=0000000000000020 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010286
atikmdag+0x24c051:
fffff880`03e66051 390a cmp dword ptr [rdx],ecx ds:002b:00802484`c7fff6d0=????????
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000000
EXCEPTION_PARAMETER2: ffffffffffffffff
READ_ADDRESS: GetPointerFromAddress: unable to read from fffff80002cbf0e0
ffffffffffffffff
FOLLOWUP_IP:
atikmdag+24c051
fffff880`03e66051 390a cmp dword ptr [rdx],ecx
BUGCHECK_STR: 0x7E
LAST_CONTROL_TRANSFER: from 0000000000000004 to fffff88003e66051
STACK_TEXT:
fffff880`0495dc30 00000000`00000004 : cccccccc`00000000 00000000`00000000 00000000`00000000 fffff800`02c01e80 : atikmdag+0x24c051
fffff880`0495dc38 cccccccc`00000000 : 00000000`00000000 00000000`00000000 fffff800`02c01e80 00000001`1e2da60c : 0x4
fffff880`0495dc40 00000000`00000000 : 00000000`00000000 fffff800`02c01e80 00000001`1e2da60c 0000000e`0000023e : 0xcccccccc`00000000
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+24c051
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4b0ca832
STACK_COMMAND: .cxr 0xfffff8800495d260 ; kb
FAILURE_BUCKET_ID: X64_0x7E_atikmdag+24c051
BUCKET_ID: X64_0x7E_atikmdag+24c051
Followup: MachineOwner
---------