Şu an Valorant güncelleme ile sıkıntılı bir hal almış durumda. Sizin de dökümünüzde sorunun kaynağı Vanguard diye belirtiliyor. Size tavsiyem yeni güncelleme yayımlanana kadar Vanguard'ı silmenizdir. Güncelleme sonrası da sorununuz çözülecek bu arada.
[CODE title="Dökümler"]*******************************************************************************
* *
* 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: ffffffffc0000096, The exception code that was not handled
Arg2: fffff800b7cae9d0, 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: 8656
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 47037
Key : Analysis.Init.CPU.mSec
Value: 1280
Key : Analysis.Init.Elapsed.mSec
Value: 3053
Key : Analysis.Memory.CommitPeak.Mb
Value: 67
Key : WER.OS.Branch
Value: winblue_r4
Key : WER.OS.Timestamp
Value: 2014-10-28T15:00:00Z
Key : WER.OS.Version
Value: 8.1.9600.17415
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc0000096
BUGCHECK_P2: fffff800b7cae9d0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RiotClientUxRe
DPC_STACK_BASE: FFFFF80245DAFFB0
STACK_TEXT:
fffff802`45dae238 fffff802`4466bc4e : 00000000`0000001e ffffffff`c0000096 fffff800`b7cae9d0 00000000`00000000 : nt!KeBugCheckEx
fffff802`45dae240 fffff802`445e0eed : fffff802`45dae9b0 00000000`00000000 fffff802`45daf1a8 fffff802`45dae3b0 : nt!KiFatalExceptionHandler+0x22
fffff802`45dae280 fffff802`44563125 : 00000000`00000001 fffff802`44489000 fffff802`45daf101 fffff802`00000000 : nt!RtlpExecuteHandlerForException+0xd
fffff802`45dae2b0 fffff802`445674de : fffff802`45daf1a8 fffff802`45daeeb0 fffff802`45daf1a8 ffffe001`894ef190 : nt!RtlDispatchException+0x1a5
fffff802`45dae980 fffff802`445e55c2 : ffffe001`00000004 00000000`00000000 00000000`00000000 fffff802`45daf168 : nt!KiDispatchException+0x646
fffff802`45daf070 fffff802`445e3afe : ffffe001`89303030 00000000`00000000 fffff802`45daf240 ffffe001`89303030 : nt!KiExceptionDispatch+0xc2
fffff802`45daf250 fffff800`b7cae9d0 : ffffe001`860a76c0 00000000`00000000 00000000`00000002 ffffe001`8a1a2c80 : nt!KiGeneralProtectionFault+0xfe
fffff802`45daf3e0 ffffe001`860a76c0 : 00000000`00000000 00000000`00000002 ffffe001`8a1a2c80 00000000`00000000 : vgk+0x4f9d0
fffff802`45daf3e8 00000000`00000000 : 00000000`00000002 ffffe001`8a1a2c80 00000000`00000000 ffffe001`88ee1b70 : 0xffffe001`860a76c0
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: 8.1.9600.17415
BUILDLAB_STR: winblue_r4
OSPLATFORM_TYPE: x64
OSNAME: Windows 8.1
FAILURE_ID_HASH: {a12159ce-3331-0cde-43dd-ad042f045e26}
Followup: MachineOwner
---------[/CODE]