Valorant'a girerken KMODE_EXCEPTION_NOT_HANDLED hatası veriyor

İşletim sistemi
Windows 11
Hata Vanguard Anti-Cheat yazılımı sebebiyle olmuş, çok rahatlıkla söyleyebilirim.

Kod:
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: ffffffffc0000005, The exception code that was not handled
Arg2: fffff805354aa793, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception

Debugging Details:
------------------

*** WARNING: Unable to verify timestamp for vgk.sys
*************************************************************************
***                                                                   ***
***                                                                   ***
***    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                                 ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2093

    Key  : Analysis.Elapsed.mSec
    Value: 3576

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 500

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3489

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 101

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1e

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1e

    Key  : Dump.Attributes.AsUlong
    Value: 0x21008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: AV_R_vgk!unknown_function

    Key  : Failure.Exception.IP.Address
    Value: 0xfffff805354aa793

    Key  : Failure.Exception.IP.Module
    Value: vgk

    Key  : Failure.Exception.IP.Offset
    Value: 0x5a793

    Key  : Failure.Hash
    Value: {b93bf423-3535-1218-531c-8c08e172e67f}

    Key  : Stack.Pointer
    Value: PRCBException


BUGCHECK_CODE:  1e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff805354aa793

BUGCHECK_P3: 0

BUGCHECK_P4: ffffffffffffffff

FILE_IN_CAB:  070825-6437-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffff928ddf3b8080

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

READ_ADDRESS: fffff805839c44c0: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
 ffffffffffffffff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  VALORANT-Win64

STACK_TEXT: 
ffffde00`e0f5c898 fffff805`82dc56ab     : 00000000`0000001e ffffffff`c0000005 fffff805`354aa793 00000000`00000000 : nt!KeBugCheckEx
ffffde00`e0f5c8a0 fffff805`830a4eb2     : 00256cb0`0014f074 0014f074`00257042 0025727c`00257050 00257290`00157250 : nt!KiDispatchException+0xb0b
ffffde00`e0f5cfb0 fffff805`830a4e80     : fffff805`830b8d3e 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxExceptionDispatchOnExceptionStack+0x12
ffffa285`f3046e38 fffff805`830b8d3e     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExceptionDispatchOnExceptionStackContinue
ffffa285`f3046e40 fffff805`830b3a25     : ffffcb8f`3c41adb8 00000000`00000000 ffffa285`f3046fb8 fffff805`82dff12d : nt!KiExceptionDispatch+0x13e
ffffa285`f3047020 fffff805`354aa793     : fffff805`354a07a5 ffff8283`ad090a18 00000000`00000000 ffffa285`00000000 : nt!KiGeneralProtectionFault+0x365
ffffa285`f30471b8 fffff805`354a07a5     : ffff8283`ad090a18 00000000`00000000 ffffa285`00000000 ffffde00`e0f38100 : vgk+0x5a793
ffffa285`f30471c0 ffff8283`ad090a18     : 00000000`00000000 ffffa285`00000000 ffffde00`e0f38100 ffff928d`bf79a280 : vgk+0x507a5
ffffa285`f30471c8 00000000`00000000     : ffffa285`00000000 ffffde00`e0f38100 ffff928d`bf79a280 fffff805`82e412e0 : 0xffff8283`ad090a18


SYMBOL_NAME:  vgk+5a793

MODULE_NAME: vgk

IMAGE_NAME:  vgk.sys

STACK_COMMAND: .process /r /p 0xffff928ddded2080; .thread 0xffff928ddf3b8080 ; kb

BUCKET_ID_FUNC_OFFSET:  5a793

FAILURE_BUCKET_ID:  AV_R_vgk!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {b93bf423-3535-1218-531c-8c08e172e67f}
Vanguard yazılımını kaldırın, oyun tekrar kurar. Bu arada bu hata bir tek sizde yok. Genel. Forumda bugün bir sürü Vanguard kaynaklı mavi ekran konusu açıldı. Çözülmezse Riot'a bilet açın.
 

Technopat Haberler

Geri
Yukarı