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: fffff80026b9f9d0, 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
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 12421
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 27141
Key : Analysis.Init.CPU.mSec
Value: 1140
Key : Analysis.Init.Elapsed.mSec
Value: 6253
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000096
BUGCHECK_P2: fffff80026b9f9d0
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:
fffff800`2e682158 fffff800`2baf52ce : 00000000`0000001e ffffffff`c0000096 fffff800`26b9f9d0 00000000`00000000 : nt!KeBugCheckEx
fffff800`2e682160 fffff800`2b9fecff : fffff800`2baf52ac 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff800`2e6821a0 fffff800`2b92bff7 : fffff800`2e682710 00000000`00000000 fffff800`2e66dd60 fffff800`2b9f99ae : nt!RtlpExecuteHandlerForException+0xf
fffff800`2e6821d0 fffff800`2b92abe6 : fffff800`2e66cdc8 fffff800`2e682e20 fffff800`2e66cdc8 ffff8503`dfd69be0 : nt!RtlDispatchException+0x297
fffff800`2e6828f0 fffff800`2b9f6cd2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff800`2e682fb0 fffff800`2b9f6ca0 : fffff800`2ba07ea5 ffff7abd`c6f3be00 ffff8503`df1e0000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff800`2e66cc88 fffff800`2ba07ea5 : ffff7abd`c6f3be00 ffff8503`df1e0000 00000000`00000000 fffff800`26462180 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff800`2e66cc90 fffff800`2ba03be0 : 00000000`0000000d ffff8503`df12a470 fffff800`2e66ce00 ffff8503`df13b008 : nt!KiExceptionDispatch+0x125
fffff800`2e66ce70 fffff800`26b9f9d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320
fffff800`2e66d000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vgk+0x4f9d0
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
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a12159ce-3331-0cde-43dd-ad042f045e26}
Followup: MachineOwner
---------
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: fffff8057c19f9d0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
Unable to load image \??\C:\Program Files\Riot Vanguard\vgk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vgk.sys
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 12624
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 27295
Key : Analysis.Init.CPU.mSec
Value: 1186
Key : Analysis.Init.Elapsed.mSec
Value: 7979
Key : Analysis.Memory.CommitPeak.Mb
Value: 80
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000096
BUGCHECK_P2: fffff8057c19f9d0
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:
fffff805`82282158 fffff805`7eaf52ce : 00000000`0000001e ffffffff`c0000096 fffff805`7c19f9d0 00000000`00000000 : nt!KeBugCheckEx
fffff805`82282160 fffff805`7e9fecff : fffff805`7eaf52ac 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff805`822821a0 fffff805`7e92bff7 : fffff805`82282710 00000000`00000000 fffff805`82274fb0 fffff805`7e9fce85 : nt!RtlpExecuteHandlerForException+0xf
fffff805`822821d0 fffff805`7e92abe6 : fffff805`82274018 fffff805`82282e20 fffff805`82274018 ffffd28f`f78e0da0 : nt!RtlDispatchException+0x297
fffff805`822828f0 fffff805`7e9f6cd2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff805`82282fb0 fffff805`7e9f6ca0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff805`82273ed8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
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
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a12159ce-3331-0cde-43dd-ad042f045e26}
Followup: MachineOwner
---------
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: fffff8000981f9d0, 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
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 13452
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 24089
Key : Analysis.Init.CPU.mSec
Value: 1171
Key : Analysis.Init.Elapsed.mSec
Value: 9988
Key : Analysis.Memory.CommitPeak.Mb
Value: 81
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000096
BUGCHECK_P2: fffff8000981f9d0
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:
fffff800`0ba82158 fffff800`06af52ce : 00000000`0000001e ffffffff`c0000096 fffff800`0981f9d0 00000000`00000000 : nt!KeBugCheckEx
fffff800`0ba82160 fffff800`069fecff : fffff800`06af52ac 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff800`0ba821a0 fffff800`0692bff7 : fffff800`0ba82710 00000000`00000000 fffff800`0ba6dd60 fffff800`069f99ae : nt!RtlpExecuteHandlerForException+0xf
fffff800`0ba821d0 fffff800`0692abe6 : fffff800`0ba6cdc8 fffff800`0ba82e20 fffff800`0ba6cdc8 ffffc48b`37a35d60 : nt!RtlDispatchException+0x297
fffff800`0ba828f0 fffff800`069f6cd2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff800`0ba82fb0 fffff800`069f6ca0 : fffff800`06a07ea5 fffff0cb`00000000 fffff800`06803b71 00000000`00000008 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff800`0ba6cc88 fffff800`06a07ea5 : fffff0cb`00000000 fffff800`06803b71 00000000`00000008 fffff800`037a2180 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff800`0ba6cc90 fffff800`06a03be0 : 00000000`00000002 00000000`00000000 00000000`00000002 ffffd880`9abe8180 : nt!KiExceptionDispatch+0x125
fffff800`0ba6ce70 fffff800`0981f9d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320
fffff800`0ba6d000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vgk+0x4f9d0
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
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a12159ce-3331-0cde-43dd-ad042f045e26}
Followup: MachineOwner
---------
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: fffff8068402f9d0, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
Unable to load image \??\C:\Program Files\Riot Vanguard\vgk.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for vgk.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 12155
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 21210
Key : Analysis.Init.CPU.mSec
Value: 1280
Key : Analysis.Init.Elapsed.mSec
Value: 11929
Key : Analysis.Memory.CommitPeak.Mb
Value: 73
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000096
BUGCHECK_P2: fffff8068402f9d0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RiotClientUxRender.exe
STACK_TEXT:
fffff806`80682158 fffff806`7c8f52ce : 00000000`0000001e ffffffff`c0000096 fffff806`8402f9d0 00000000`00000000 : nt!KeBugCheckEx
fffff806`80682160 fffff806`7c7fecff : fffff806`7c8f52ac 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff806`806821a0 fffff806`7c72bff7 : fffff806`80682710 00000000`00000000 fffff806`80674fb0 fffff806`7c7fce85 : nt!RtlpExecuteHandlerForException+0xf
fffff806`806821d0 fffff806`7c72abe6 : fffff806`80674018 fffff806`80682e20 fffff806`80674018 ffff840f`7ffaac80 : nt!RtlDispatchException+0x297
fffff806`806828f0 fffff806`7c7f6cd2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff806`80682fb0 fffff806`7c7f6ca0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff806`80673ed8 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
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
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a12159ce-3331-0cde-43dd-ad042f045e26}
Followup: MachineOwner
---------
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: fffff8034e15f9d0, 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
*** WARNING: Unable to verify checksum for win32k.sys
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 14171
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 28315
Key : Analysis.Init.CPU.mSec
Value: 1140
Key : Analysis.Init.Elapsed.mSec
Value: 2988
Key : Analysis.Memory.CommitPeak.Mb
Value: 82
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000096
BUGCHECK_P2: fffff8034e15f9d0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
STACK_TEXT:
fffff803`51082158 fffff803`4b8f52ce : 00000000`0000001e ffffffff`c0000096 fffff803`4e15f9d0 00000000`00000000 : nt!KeBugCheckEx
fffff803`51082160 fffff803`4b7fecff : fffff803`4b8f52ac 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff803`510821a0 fffff803`4b72bff7 : fffff803`51082710 00000000`00000000 fffff803`5106dd60 fffff803`4b7f99ae : nt!RtlpExecuteHandlerForException+0xf
fffff803`510821d0 fffff803`4b72abe6 : fffff803`5106cdc8 fffff803`51082e20 fffff803`5106cdc8 ffffe20b`74c14d60 : nt!RtlDispatchException+0x297
fffff803`510828f0 fffff803`4b7f6cd2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff803`51082fb0 fffff803`4b7f6ca0 : fffff803`4b807ea5 ffffe20b`73d4c4c0 fffff803`4bdb1094 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff803`5106cc88 fffff803`4b807ea5 : ffffe20b`73d4c4c0 fffff803`4bdb1094 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff803`5106cc90 fffff803`4b803be0 : 00000000`00000040 00000000`00000000 fffff803`5106cf71 fffff803`4b6501c1 : nt!KiExceptionDispatch+0x125
fffff803`5106ce70 fffff803`4e15f9d0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiGeneralProtectionFault+0x320
fffff803`5106d000 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : vgk+0x4f9d0
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
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a12159ce-3331-0cde-43dd-ad042f045e26}
Followup: MachineOwner
---------