C:\kdfe_Dump_Analize>echo off
Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\kdfe_Dump_Analize\DumpS\Mini063009-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*symbols*
http://msdl.microsoft.com/download/symbols
Executable search path is: srv*symbols *
http://msdl.microsoft.com/download/symbols
Windows Server 2008/Windows Vista Kernel Version 6002 (Service Pack 2) MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 6002.18005.amd64fre.lh_sp2rtm.090410-1830
Machine Name:
Kernel base = 0xfffff800`02058000 PsLoadedModuleList = 0xfffff800`0221cdd0
Debug session time: Tue Jun 30 23:09:27.088 2009 (GMT+6)
System Uptime: 0 days 0:06:42.961
Loading Kernel Symbols
...............................................................
................................................................
.............
Loading User Symbols
Loading unloaded module list
........
Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000007E, {ffffffffc0000094, fffffa6002877447, fffffa6008d30e88, fffffa6008d30860}
Probably caused by : nvlddmkm.sys ( nvlddmkm+77447 )
Followup: MachineOwner
---------
0: kd> kd: Reading initial command '!analyze -v; q'
*******************************************************************************
* *
* 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: fffffa6002877447, The address that the exception occurred at
Arg3: fffffa6008d30e88, Exception Record Address
Arg4: fffffa6008d30860, Context Record Address
Debugging Details:
------------------
OVERLAPPED_MODULE: Address regions for 'nvlddmkm' and 'nvlddmkm.sys' overlap
EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {
FAULTING_IP:
nvlddmkm+77447
fffffa60`02877447 f7f9 idiv eax,ecx
EXCEPTION_RECORD: fffffa6008d30e88 -- (.exr 0xfffffa6008d30e88)
ExceptionAddress: fffffa6002877447 (nvlddmkm+0x0000000000077447)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffffa6008d30860 -- (.cxr 0xfffffa6008d30860)
rax=0000000000000690 rbx=fffffa8005e7f918 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000690 rdi=0000000000000000
rip=fffffa6002877447 rsp=fffffa6008d310c0 rbp=0000000000000001
r8=0000000000000000 r9=0000000000000000 r10=000000000000003b
r11=0000000000000001 r12=fffffa8005e7e000 r13=0000000000000016
r14=fffffa8005e7e264 r15=fffffa8005bc3000
iopl=0 nv up ei ng nz na pe cy
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010283
nvlddmkm+0x77447:
fffffa60`02877447 f7f9 idiv eax,ecx
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 - {
LAST_CONTROL_TRANSFER: from fffffa60032b7860 to fffffa6002877447
STACK_TEXT:
fffffa60`08d310c0 fffffa60`032b7860 : fffffa60`02db373e fffffa80`05e7f768 fffffa80`05e7e064 fffffa80`05e7f768 : nvlddmkm+0x77447
fffffa60`08d310c8 fffffa60`02db373e : fffffa80`05e7f768 fffffa80`05e7e064 fffffa80`05e7f768 fffffa80`05e7e064 : nvlddmkm+0xab7860
fffffa60`08d310d0 fffffa80`05e7f768 : fffffa80`05e7e064 fffffa80`05e7f768 fffffa80`05e7e064 fffffa80`05e7e000 : nvlddmkm+0x5b373e
fffffa60`08d310d8 fffffa80`05e7e064 : fffffa80`05e7f768 fffffa80`05e7e064 fffffa80`05e7e000 fffffa60`02878f4f : 0xfffffa80`05e7f768
fffffa60`08d310e0 fffffa80`05e7f768 : fffffa80`05e7e064 fffffa80`05e7e000 fffffa60`02878f4f 00000000`00020000 : 0xfffffa80`05e7e064
fffffa60`08d310e8 fffffa80`05e7e064 : fffffa80`05e7e000 fffffa60`02878f4f 00000000`00020000 00000000`00000000 : 0xfffffa80`05e7f768
fffffa60`08d310f0 fffffa80`05e7e000 : fffffa60`02878f4f 00000000`00020000 00000000`00000000 00000000`00030003 : 0xfffffa80`05e7e064
fffffa60`08d310f8 fffffa60`02878f4f : 00000000`00020000 00000000`00000000 00000000`00030003 fffffa80`05bc3000 : 0xfffffa80`05e7e000
fffffa60`08d31100 00000000`00020000 : 00000000`00000000 00000000`00030003 fffffa80`05bc3000 fffffa60`08d31134 : nvlddmkm+0x78f4f
fffffa60`08d31108 00000000`00000000 : 00000000`00030003 fffffa80`05bc3000 fffffa60`08d31134 00000000`00000000 : 0x20000
FOLLOWUP_IP:
nvlddmkm+77447
fffffa60`02877447 f7f9 idiv eax,ecx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+77447
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a2fc3d4
STACK_COMMAND: .cxr 0xfffffa6008d30860 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+77447
BUCKET_ID: X64_0x7E_nvlddmkm+77447
Followup: MachineOwner
---------
quit:
