drive.google.com
| Name: | vgk.sys |
| Info: | Riot Vanguard Anti Cheat |
| Source: | VALORANT (only VALORANT for now, source could be any Riot Games game in future) |
www.gigabyte.com.tr
*******************************************************************************
* *
* 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: ffffffffc000001d, The exception code that was not handled
Arg2: fffff806399af06a, The address that the exception occurred at
Arg3: ffffcb81f35e9080, Parameter 0 of the exception
Arg4: fffff8061d41e680, Parameter 1 of the exception
Debugging Details:
------------------
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ExceptionRecord ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: ContextRecord ***
*** ***
*************************************************************************
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: 2750
Key : Analysis.Elapsed.mSec
Value: 6464
Key : Analysis.IO.Other.Mb
Value: 0
Key : Analysis.IO.Read.Mb
Value: 0
Key : Analysis.IO.Write.Mb
Value: 0
Key : Analysis.Init.CPU.mSec
Value: 171
Key : Analysis.Init.Elapsed.mSec
Value: 1213
Key : Analysis.Memory.CommitPeak.Mb
Value: 145
Key : Bugcheck.Code.LegacyAPI
Value: 0x1e
Key : Failure.Bucket
Value: 0x1E_C000001D_BAD_IP_vgk!unknown_function
Key : Failure.Hash
Value: {5c6f14a0-f218-b89f-2d25-d884e68c50e0}
Key : WER.OS.Branch
Value: vb_release
Key : WER.OS.Version
Value: 10.0.19041.1
BUGCHECK_CODE: 1e
BUGCHECK_P1: ffffffffc000001d
BUGCHECK_P2: fffff806399af06a
BUGCHECK_P3: ffffcb81f35e9080
BUGCHECK_P4: fffff8061d41e680
FILE_IN_CAB: 061623-12421-01.dmp
EXCEPTION_PARAMETER1: ffffcb81f35e9080
EXCEPTION_PARAMETER2: fffff8061d41e680
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: svchost.exe
FAILED_INSTRUCTION_ADDRESS:
vgk+6f06a
fffff806`399af06a db ???
STACK_TEXT:
fffff806`2288b158 fffff806`1d6f910e : 00000000`0000001e ffffffff`c000001d fffff806`399af06a ffffcb81`f35e9080 : nt!KeBugCheckEx
fffff806`2288b160 fffff806`1d60671f : fffff806`1d6f90ec 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HvlpVtlCallExceptionHandler+0x22
fffff806`2288b1a0 fffff806`1d4e5b37 : fffff806`2288b710 00000000`00000000 fffff806`2287dfb0 fffff806`1d604525 : nt!RtlpExecuteHandlerForException+0xf
fffff806`2288b1d0 fffff806`1d4e7b06 : fffff806`2287cf68 fffff806`2288be20 fffff806`2287cf68 00000000`00000000 : nt!RtlDispatchException+0x297
fffff806`2288b8f0 fffff806`1d5fd142 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchException+0x186
fffff806`2288bfb0 fffff806`1d5fd110 : fffff806`1d610165 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
fffff806`2287ce28 fffff806`1d610165 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
fffff806`2287ce30 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatch+0x125
SYMBOL_NAME: vgk+6f06a
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 6f06a
FAILURE_BUCKET_ID: 0x1E_C000001D_BAD_IP_vgk!unknown_function
OS_VERSION: 10.0.19041.1
BUILDLAB_STR: vb_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {5c6f14a0-f218-b89f-2d25-d884e68c50e0}
Followup: MachineOwner
---------
Evet önceki mesajımda dediğim gibi, %100 olunca işlem tamamlandığı için anakart kendini kapatıyor. Mesela bende de %100 olunca sistem kapanıyor, 2-3 saniye sonra geri açılıyor. Bazı anakartlarda direkt kapanıyor ve sizin açmanızı bekliyor. O yüzden merak etmeyin, siz işlemleri doğru yaparsanız ve BIOS güncellemesi sırasında herhangi bir kesinti, müdahale olmazsa yüklenir.
