Ne yazık ki yanlış düşünüyorsunuz. Güncelleme sonrası oluşan mavi ekranların hepsinin minidump dosyalarını tek tek inceledim ve tüm sorun Vanguard'da. Vanguard'ı kaldıran her sistemde sorun çözülüyor. Ayrıca 00:00'da birden olmaya başladı ki o saatte güncelleme yayımlandı fakat herhangi bir Windows güncellemesi yayımlanmadı. Valorant tarafından hala resmi bir açıklama yok fakat beklemedeyiz.
[CODE title="Bu da örnek dump dökümü"]*******************************************************************************
* *
* 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: fffff80420acf9d0, 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: 6811
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 14438
Key : Analysis.Init.CPU.mSec
Value: 1234
Key : Analysis.Init.Elapsed.mSec
Value: 6099
Key : Analysis.Memory.CommitPeak.Mb
Value: 74
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: fffff80420acf9d0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: RiotClientServices.exe
TRAP_FRAME: 245c8b48000000c0 -- (.trap 0x245c8b48000000c0)
Unable to read trap frame at 245c8b48`000000c0
STACK_TEXT:
ffff8301`4a3e7158 fffff804`24cf52ce : 00000000`0000001e ffffffff`c0000096 fffff804`20acf9d0 00000000`00000000 : nt!KeBugCheckEx
ffff8301`4a3e7160 fffff804`24bfecff : fffff804`24cf52ac 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
ffff8301`4a3e71a0 fffff804`24b2bff7 : ffff8301`4a3e7710 00000000`00000000 ffffa705`2c03efb0 fffff804`24bfce85 : nt!RtlpExecuteHandlerForException+0xf
ffff8301`4a3e71d0 fffff804`24b2abe6 : ffffa705`2c03e018 ffff8301`4a3e7e20 ffffa705`2c03e018 ffffb30f`32991ba0 : nt!RtlDispatchException+0x297
ffff8301`4a3e78f0 fffff804`24bf6cd2 : 00eb840f`000000a8 850f02c4`f6410000 245c8b48`000000c0 c0854830`438b4870 : nt!KiDispatchException+0x186
ffff8301`4a3e7fb0 fffff804`24bf6ca0 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffa705`2c03ded8 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
---------[/CODE]