Vanguard kaldırın. Tekrar yüklenmediği sürece LoL'e girebilirsiniz. Valorant için aynı şeyi söyleyemeyeceğim.
[CODE title="Kodlar"]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: 0000000000000000, The exception code that was not handled
Arg2: 0000000000000000, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: 0000000000000000, Parameter 1 of the exception
Debugging Details:
------------------
DBGENG: vgk.sys - Partial symbol image load missing image info
DBGHELP: No header for vgk.sys. Searching for dbg file
DBGHELP: .\vgk.dbg - file not found
DBGHELP: .\sys\vgk.dbg - path not found
DBGHELP: .\symbols\sys\vgk.dbg - path not found
DBGHELP: vgk.sys missing debug info. Searching for pdb anyway
DBGHELP: Can't use symbol server for vgk.pdb - no header information available
DBGHELP: vgk.pdb - file not found
*** WARNING: Unable to verify timestamp for vgk.sys
DBGHELP: vgk - no symbols loaded
SYMSRV: BYINDEX: 0xD
C:\ProgramData\Dbg\sym
CLFS.SYS
5E98E88560000
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
DBGHELP: SharedUserData - virtual symbol module
*************************************************************************
*** ***
*** ***
*** 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 ***
*** ***
*************************************************************************
GetUlongPtrFromAddress: unable to read from fffff800030f5300
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 1733
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 26027
Key : Analysis.Init.CPU.mSec
Value: 499
Key : Analysis.Init.Elapsed.mSec
Value: 11287
Key : Analysis.Memory.CommitPeak.Mb
Value: 63
Key : WER.OS.Branch
Value: win7sp1_ldr_escrow
Key : WER.OS.Timestamp
Value: 2020-06-10T19:07:00Z
Key : WER.OS.Version
Value: 7.1.7601.24557
BUGCHECK_CODE: 1e
BUGCHECK_P1: 0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: System
TRAP_FRAME: fffff880009c5560 -- (.trap 0xfffff880009c5560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=0000000000000681
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8800a06c9d0 rsp=fffff880009c56f0 rbp=fffff880009c5768
r8=fffffa80057f1b30 r9=0000000000000000 r10=0000000000000001
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
vgk+0x4f9d0:
fffff880`0a06c9d0 ?? ???
Resetting default scope
STACK_TEXT:
fffff880`009c45a8 fffff800`02eeee0e : fffffa80`03ee8030 fffff880`04b8812c fffff880`009c4d20 fffff800`02e76b00 : nt!KeBugCheck
fffff880`009c45b0 fffff800`02ef2efd : fffff800`030cd740 fffff800`0302139c fffff800`02e57000 fffff880`009c54b8 : nt!KiKernelCalloutExceptionHandler+0xe
fffff880`009c45e0 fffff800`02e77765 : fffff800`030018ac fffff880`009c4658 fffff880`009c54b8 fffff800`02e57000 : nt!RtlpExecuteHandlerForException+0xd
fffff880`009c4610 fffff800`02fd2bee : fffff880`009c54b8 fffff880`009c4d20 fffff880`00000000 fffffa80`057f19e0 : nt!RtlDispatchException+0x415
fffff880`009c4cf0 fffff800`02efa0c2 : fffff880`009c54b8 fffff880`009c5840 fffff880`009c5560 fffffa80`057f1b30 : nt!KiDispatchException+0x17e
fffff880`009c5380 fffff800`02ef7978 : 00000002`009c5500 00000000`00000004 00000000`00000000 00000000`0000000f : nt!KiExceptionDispatch+0xc2
fffff880`009c5560 fffff880`0a06c9d0 : fffff880`009c5840 fffffa80`05a287a8 fffffa80`057f1b30 fffffa80`0573d218 : nt!KiGeneralProtectionFault+0x2f8
fffff880`009c56f0 fffff880`009c5840 : fffffa80`05a287a8 fffffa80`057f1b30 fffffa80`0573d218 00000000`00000000 : vgk+0x4f9d0
fffff880`009c56f8 fffffa80`05a287a8 : fffffa80`057f1b30 fffffa80`0573d218 00000000`00000000 fffffa80`05a287a8 : 0xfffff880`009c5840
fffff880`009c5700 fffffa80`057f1b30 : fffffa80`0573d218 00000000`00000000 fffffa80`05a287a8 fffffa80`0573d010 : 0xfffffa80`05a287a8
fffff880`009c5708 fffffa80`0573d218 : 00000000`00000000 fffffa80`05a287a8 fffffa80`0573d010 fffff880`05396a5c : 0xfffffa80`057f1b30
fffff880`009c5710 00000000`00000000 : fffffa80`05a287a8 fffffa80`0573d010 fffff880`05396a5c 03480364`03640380 : 0xfffffa80`0573d218
SYMBOL_NAME: vgk+4f9d0
MODULE_NAME: vgk
IMAGE_NAME: vgk.sys
STACK_COMMAND: .thread ; .cxr ; kb
FAILURE_BUCKET_ID: 0x1E_vgk+4f9d0
OS_VERSION: 7.1.7601.24557
BUILDLAB_STR: win7sp1_ldr_escrow
OSPLATFORM_TYPE: x64
OSNAME: Windows 7
FAILURE_ID_HASH: {7d558631-e160-f552-6bd8-2910dc6a6638}
Followup: MachineOwner
---------
[/CODE]
