Microsoft (R) Windows Debugger Version 6.12.0002.633 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\062611-10155-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 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17592.amd64fre.win7sp1_gdr.110408-1631
Machine Name:
Kernel base = 0xfffff800`02c1b000 PsLoadedModuleList = 0xfffff800`02e60650
Debug session time: Sun Jun 26 07:04:44.275 2011 (UTC + 2:00)
System Uptime: 0 days 0:00:10.446
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, fffff88013737639, fffff88005edccc8, fffff88005edc520}
Probably caused by : nvlddmkm.sys ( nvlddmkm+69f639 )
Followup: MachineOwner
---------
1: 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: fffff88013737639, The address that the exception occurred at
Arg3: fffff88005edccc8, Exception Record Address
Arg4: fffff88005edc520, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {AUSNAHME} Ganze Zahl-Fehler:Division durch Null
FAULTING_IP:
nvlddmkm+69f639
fffff880`13737639 f7f1 div eax,ecx
EXCEPTION_RECORD: fffff88005edccc8 -- (.exr 0xfffff88005edccc8)
ExceptionAddress: fffff88013737639 (nvlddmkm+0x000000000069f639)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff88005edc520 -- (.cxr 0xfffff88005edc520)
rax=0000000000000000 rbx=0000000000000001 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa8006a329f8
rip=fffff88013737639 rsp=fffff88005edcf08 rbp=0000000000000001
r8=fffffa8006a329f8 r9=0000000000000000 r10=fffff88005edd000
r11=fffff88005edceb0 r12=fffffa8006a32e60 r13=fffffa8008438000
r14=fffffa8006a32948 r15=fffffa8006a30000
iopl=0 nv up ei pl zr ac po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010256
nvlddmkm+0x69f639:
fffff880`13737639 f7f1 div eax,ecx
Resetting default scope
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT
BUGCHECK_STR: 0x7E
PROCESS_NAME: csrss.exe
CURRENT_IRQL: 0
ERROR_CODE: (NTSTATUS) 0xc0000094 - {AUSNAHME} Ganze Zahl-Fehler:Division durch Null
LAST_CONTROL_TRANSFER: from fffff88013624947 to fffff88013737639
STACK_TEXT:
fffff880`05edcf08 fffff880`13624947 : 00000000`00000001 00000000`00000000 fffffa80`06a30000 fffffa80`06a30000 : nvlddmkm+0x69f639
fffff880`05edcf10 00000000`00000001 : 00000000`00000000 fffffa80`06a30000 fffffa80`06a30000 fffffa80`06a30000 : nvlddmkm+0x58c947
fffff880`05edcf18 00000000`00000000 : fffffa80`06a30000 fffffa80`06a30000 fffffa80`06a30000 fffff880`13305f00 : 0x1
FOLLOWUP_IP:
nvlddmkm+69f639
fffff880`13737639 f7f1 div eax,ecx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+69f639
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a68
STACK_COMMAND: .cxr 0xfffff88005edc520 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+69f639
BUCKET_ID: X64_0x7E_nvlddmkm+69f639
Followup: MachineOwner
---------
