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: fffff8801012c3db, The address that the exception occurred at
Arg3: fffff88006dcb3c8, Exception Record Address
Arg4: fffff88006dcac30, Context Record Address
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {EXCEPTION} Integer division by zero.
FAULTING_IP:
nvlddmkm+c03db
fffff880`1012c3db 41f7f0 div eax,r8d
EXCEPTION_RECORD: fffff88006dcb3c8 -- (.exr 0xfffff88006dcb3c8)
ExceptionAddress: fffff8801012c3db (nvlddmkm+0x00000000000c03db)
ExceptionCode: c0000094 (Integer divide-by-zero)
ExceptionFlags: 00000000
NumberParameters: 0
CONTEXT: fffff88006dcac30 -- (.cxr 0xfffff88006dcac30)
rax=00000000deaddead rbx=fffff8a01395e4a6 rcx=0000000000000001
rdx=0000000000000000 rsi=0000000000000000 rdi=fffffa80097d99c0
rip=fffff8801012c3db rsp=fffff88006dcb600 rbp=0000000000000000
r8=0000000000000000 r9=00000000000f92a9 r10=fffff88010778390
r11=fffff8a01395e46f r12=fffff8a01395e49f r13=00000000000f92a9
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00010246
nvlddmkm+0xc03db:
fffff880`1012c3db 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 - {EXCEPTION} Integer division by zero.
LAST_CONTROL_TRANSFER: from 0000000100000000 to fffff8801012c3db
STACK_TEXT:
fffff880`06dcb600 00000001`00000000 : fffff880`1012b92d 00000bf0`000f2374 0000000c`00000bf0 00000000`d804e000 : nvlddmkm+0xc03db
fffff880`06dcb608 fffff880`1012b92d : 00000bf0`000f2374 0000000c`00000bf0 00000000`d804e000 00000001`0000001a : 0x1`00000000
fffff880`06dcb610 00000bf0`000f2374 : 0000000c`00000bf0 00000000`d804e000 00000001`0000001a 00000000`00000000 : nvlddmkm+0xbf92d
fffff880`06dcb618 0000000c`00000bf0 : 00000000`d804e000 00000001`0000001a 00000000`00000000 fffffa80`0c41e010 : 0xbf0`000f2374
fffff880`06dcb620 00000000`d804e000 : 00000001`0000001a 00000000`00000000 fffffa80`0c41e010 00000000`00000000 : 0xc`00000bf0
fffff880`06dcb628 00000001`0000001a : 00000000`00000000 fffffa80`0c41e010 00000000`00000000 fffffa80`07728000 : 0xd804e000
fffff880`06dcb630 00000000`00000000 : fffffa80`0c41e010 00000000`00000000 fffffa80`07728000 00000000`00000000 : 0x1`0000001a
FOLLOWUP_IP:
nvlddmkm+c03db
fffff880`1012c3db 41f7f0 div eax,r8d
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nvlddmkm+c03db
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c37918e
STACK_COMMAND: .cxr 0xfffff88006dcac30 ; kb
FAILURE_BUCKET_ID: X64_0x7E_nvlddmkm+c03db
BUCKET_ID: X64_0x7E_nvlddmkm+c03db
Followup: MachineOwner
