Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\072410-20560-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 Personal
Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Machine Name:
Kernel base = 0xfffff800`03006000 PsLoadedModuleList = 0xfffff800`03243e50
Debug session time: Sat Jul 24 23:40:25.987 2010 (UTC + 2:00)
System Uptime: 0 days 9:28:03.782
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
Unable to load image \SystemRoot\system32\DRIVERS\atikmdag.sys, Win32 error 0n2
*** 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, {ffffffffc0000094, fffff880041a5d85, fffff88005ef2ee8, fffff88005ef2750}
Probably caused by : atikmdag.sys ( atikmdag+35ed85 )
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: ffffffffc0000094, The exception code that was not handled
Arg2: fffff880041a5d85, The address that the exception occurred at
Arg3: fffff88005ef2ee8, Exception Record Address
Arg4: fffff88005ef2750, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {UNDANTAG} Heltalsdivision med noll.
FAULTING_IP:
atikmdag+35ed85
fffff880`041a5d85 41f7f0 div eax,r8d
EXCEPTION_RECORD: fffff88005ef2ee8 -- (.exr 0xfffff88005ef2ee8)
ExceptionAddress: fffff880041a5d85 (atikmdag+0x000000000035ed85)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff88005ef2750 -- (.cxr 0xfffff88005ef2750)
rax=00000000008b2900 rbx=fffff88005ef3170 rcx=00000000008b2900
rdx=0000000000000000 rsi=fffffa8006807400 rdi=fffff88003e47000
rip=fffff880041a5d85 rsp=fffff88005ef3120 rbp=0000000000000026
r8=0000000000000000 r9=00000000000067c0 r10=fffff88005ef3170
r11=fffff880043b86f0 r12=0000000000000000 r13=00000000ffffffff
r14=00000000000009dd r15=00000000000009de
iopl=0 nv up ei pl nz na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010206
atikmdag+0x35ed85:
fffff880`041a5d85 41f7f0 div eax,r8d
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: System
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000094 - {UNDANTAG} Heltalsdivision med noll.
LAST_CONTROL_TRANSFER: from fffffa8006aa99bc to fffff880041a5d85
STACK_TEXT:
fffff880`05ef3120 fffffa80`06aa99bc : 00000000`00000286 fffff880`05ef3148 00000000`00000018 fffff880`05ef3200 : atikmdag+0x35ed85
fffff880`05ef3128 00000000`00000286 : fffff880`05ef3148 00000000`00000018 fffff880`05ef3200 fffff880`041a4ee1 : 0xfffffa80`06aa99bc
fffff880`05ef3130 fffff880`05ef3148 : 00000000`00000018 fffff880`05ef3200 fffff880`041a4ee1 00000000`00000027 : 0x286
fffff880`05ef3138 00000000`00000018 : fffff880`05ef3200 fffff880`041a4ee1 00000000`00000027 fffff880`bebe0031 : 0xfffff880`05ef3148
fffff880`05ef3140 fffff880`05ef3200 : fffff880`041a4ee1 00000000`00000027 fffff880`bebe0031 fffffa80`05e38000 : 0x18
fffff880`05ef3148 fffff880`041a4ee1 : 00000000`00000027 fffff880`bebe0031 fffffa80`05e38000 00000000`00000000 : 0xfffff880`05ef3200
fffff880`05ef3150 00000000`00000027 : fffff880`bebe0031 fffffa80`05e38000 00000000`00000000 fffff880`05ef3200 : atikmdag+0x35dee1
fffff880`05ef3158 fffff880`bebe0031 : fffffa80`05e38000 00000000`00000000 fffff880`05ef3200 fffffa80`06807400 : 0x27
fffff880`05ef3160 fffffa80`05e38000 : 00000000`00000000 fffff880`05ef3200 fffffa80`06807400 008b2900`00000000 : 0xfffff880`bebe0031
fffff880`05ef3168 00000000`00000000 : fffff880`05ef3200 fffffa80`06807400 008b2900`00000000 000067a0`008b2900 : 0xfffffa80`05e38000
FOLLOWUP_IP:
atikmdag+35ed85
fffff880`041a5d85 41f7f0 div eax,r8d
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: atikmdag+35ed85
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: atikmdag
IMAGE_NAME: atikmdag.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4add2400
STACK_COMMAND: .cxr 0xfffff88005ef2750 ; kb
FAILURE_BUCKET_ID: X64_0x7E_atikmdag+35ed85
BUCKET_ID: X64_0x7E_atikmdag+35ed85
Followup: MachineOwner
---------
