Use !analyze -v to get detailed debugging information.
BugCheck 1E, {ffffffffc0000094, fffff88004eefb1e, 0, fffff8800098f180}
*** WARNING: Unable to verify timestamp for NETwew02.sys
*** ERROR: Module load completed but symbols could not be loaded for NETwew02.sys
Probably caused by : NETwew02.sys ( NETwew02+c9b1e )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
KMODE_EXCEPTION_NOT_HANDLED (1e)
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.
Arguments:
Arg1: ffffffffc0000094, The exception code that was not handled
Arg2: fffff88004eefb1e, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: fffff8800098f180, Parameter 1 of the exception
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000094 - {UITZONDERING} Integer: deling door nul.
FAULTING_IP:
NETwew02+c9b1e
fffff880`04eefb1e 48f7f1 div rax,rcx
EXCEPTION_PARAMETER2: fffff8800098f180
BUGCHECK_STR: 0x1E_c0000094
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
PROCESS_NAME: System
CURRENT_IRQL: 2
ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre
DPC_STACK_BASE: FFFFF880009BFFB0
LAST_CONTROL_TRANSFER: from fffff8000318c902 to fffff8000306c440
STACK_TEXT:
fffff880`009b6e18 fffff800`0318c902 : 00000000`0000001e ffffffff`c0000094 fffff880`04eefb1e 00000000`00000000 : nt!KeBugCheckEx
fffff880`009b6e20 fffff800`030d847d : fffff880`009b7470 00000000`00000002 fffff880`009b6f90 fffff880`01d61607 : nt!KiFatalExceptionHandler+0x22
fffff880`009b6e60 fffff800`03100364 : 00000000`00000000 fffff880`009b6f90 fffffa80`00008910 fffff880`009b3000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009b6e90 fffff800`030da1d6 : fffff880`009b7d98 fffff880`009b7ad0 fffff880`009b7d98 fffffa80`09014c80 : nt!RtlDispatchException+0x458
fffff880`009b75a0 fffff800`0306b842 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x455
fffff880`009b7c60 fffff800`03068c34 : 00000000`00000004 fffff880`04ef251c 00000000`00000037 fffff880`009b7e70 : nt!KiExceptionDispatch+0xc2
fffff880`009b7e40 fffff880`04eefb1e : fffffa80`090f7a18 00000000`00000000 fffffa80`0f795250 00000000`00000000 : nt!KiDivideErrorFault+0xf4
fffff880`009b7fd0 fffffa80`090f7a18 : 00000000`00000000 fffffa80`0f795250 00000000`00000000 00000002`624e62aa : NETwew02+0xc9b1e
fffff880`009b7fd8 00000000`00000000 : fffffa80`0f795250 00000000`00000000 00000002`624e62aa fffff880`04eef87b : 0xfffffa80`090f7a18
STACK_COMMAND: kb
FOLLOWUP_IP:
NETwew02+c9b1e
fffff880`04eefb1e 48f7f1 div rax,rcx
SYMBOL_STACK_INDEX: 7
SYMBOL_NAME: NETwew02+c9b1e
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: NETwew02
IMAGE_NAME: NETwew02.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 53038dbe
FAILURE_BUCKET_ID: 0x1E_c0000094_NETwew02+c9b1e
BUCKET_ID: 0x1E_c0000094_NETwew02+c9b1e
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x1e_c0000094_netwew02+c9b1e
FAILURE_ID_HASH: {637e7b5f-d09c-dc26-28a2-cf0a16de941d}
Followup: MachineOwner