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: ffffffffc0000096, The exception code that was not handled
Arg2: fffff8076592f9d0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
*** WARNING: Unable to verify timestamp for vgk.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 5702
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 6411
Key : Analysis.Init.CPU.mSec
Value: 1077
Key : Analysis.Init.Elapsed.mSec
Value: 10993
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000096
BUGCHECK_P2: fffff8076592f9d0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff807`68482158 fffff807`626f52ce : 00000000`0000001e ffffffff`c0000096 fffff807`6592f9d0 00000000`00000000 : nt!KeBugCheckEx
fffff807`68482160 fffff807`625fecff : fffff807`626f52ac 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff807`684821a0 fffff807`6252bff7 : fffff807`68482710 00000000`00000000 fffff807`6846dd60 fffff807`625f99ae : nt!RtlpExecuteHandlerForException+0xf
fffff807`684821d0 fffff807`6252abe6 : fffff807`6846cdc8 fffff807`68482e20 fffff807`6846cdc8 ffff8309`fb8dad60 : nt!RtlDispatchException+0x297
fffff807`684828f0 fffff807`625f6cd2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff807`68482fb0 fffff807`625f6ca0 : fffff807`62607ea5 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff807`6846cc88 fffff807`62607ea5 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff807`6846cc90 fffff807`62603be0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125
fffff807`6846ce70 fffff807`6592f9d0 : ffff8309`fb8dad60 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320
fffff807`6846d000 ffff8309`fb8dad60 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vgk+0x4f9d0
fffff807`6846d008 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffff8309`fb8dad60
SYMBOL_NAME: vgk+4f9d0
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 4f9d0
FAILURE_BUCKET_ID: 0x1E_c0000096_vgk!unknown_function
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a12159ce-3331-0cde-43dd-ad042f045e26}
Followup: MachineOwner
---------