Valorant oynarken mavi ekran hatası

[CODE title="Kod"]
Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\maksu\Downloads\112020-17953-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff805`81c00000 PsLoadedModuleList = 0xfffff805`820461b0
Debug session time: Fri Nov 20 14:25:50.077 2020 (UTC + 3:00)
System Uptime: 1 days 2:41:42.986
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols
Loading unloaded module list
..........................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`81dc3b20 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff406`4039f290=0000000000000050
11: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: fffffeff7fb8bc58, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff80581c5efce, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 0000000000000002, (reserved)

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

*** WARNING: Unable to verify timestamp for vgk.sys

Could not read faulting driver name
*** WARNING: Unable to verify timestamp for win32k.sys

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5671

Key : Analysis.DebugAnalysisProvider.CPP
Value: Create: 8007007e on DESKTOP-G2EFLS9

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 27881

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 50

BUGCHECK_P1: fffffeff7fb8bc58

BUGCHECK_P2: 0

BUGCHECK_P3: fffff80581c5efce

BUGCHECK_P4: 2

READ_ADDRESS: fffff805821713b8: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
fffff805820283b8: Unable to get Flags value from nt!KdVersionBlock
fffff805820283b8: Unable to get Flags value from nt!KdVersionBlock
unable to get nt!MmSpecialPagesInUse
fffffeff7fb8bc58

MM_INTERNAL_CODE: 2

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: fffff4064039f530 -- (.trap 0xfffff4064039f530)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffeff7fbfd7f8 rbx=0000000000000000 rcx=0a00000425fd1863
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80581c5efce rsp=fffff4064039f6c0 rbp=fffff805981538e8
r8=fffffe8000000000 r9=fffffeff7fb8bc58 r10=0000000000000002
r11=fffffeff7fbfd7f8 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!MI_IS_PHYSICAL_ADDRESS+0x4e:
fffff805`81c5efce 498b09 mov rcx,qword ptr [r9] ds:fffffeff`7fb8bc58=????????????????
Resetting default scope

STACK_TEXT:
fffff406`4039f288 fffff805`81e0de84 : 00000000`00000050 fffffeff`7fb8bc58 00000000`00000000 fffff406`4039f530 : nt!KeBugCheckEx
fffff406`4039f290 fffff805`81ccaaff : ffffb587`93499601 00000000`00000000 00000000`00000000 fffffeff`7fb8bc58 : nt!MiSystemFault+0x198d64
fffff406`4039f390 fffff805`81dd1b5e : 00000000`00000010 fffff805`81b5f37b 00000000`00000008 fffff805`9855b71f : nt!MmAccessFault+0x34f
fffff406`4039f530 fffff805`81c5efce : fffff406`4039f6b0 fffff406`4039f7d0 00000000`00000000 fffff805`98573276 : nt!KiPageFault+0x35e
fffff406`4039f6c0 fffff805`81d24053 : 00000000`00000000 00000000`00000001 fffffeff`7fbfd7f8 0000c5e2`f178b000 : nt!MI_IS_PHYSICAL_ADDRESS+0x4e
fffff406`4039f710 fffff805`81d24009 : 00000000`0000018b fffff406`4039f818 ffffb587`93499601 00000000`00040246 : nt!MiGetPhysicalAddress+0x33
fffff406`4039f760 fffff805`986280b6 : fffff406`4039f7e0 ffffb587`00000000 00000000`00000000 00000000`00000000 : nt!MmGetPhysicalAddress+0x19
fffff406`4039f790 fffff406`4039f7e0 : ffffb587`00000000 00000000`00000000 00000000`00000000 fffff406`4039faa8 : vgk+0x5180b6
fffff406`4039f798 ffffb587`00000000 : 00000000`00000000 00000000`00000000 fffff406`4039faa8 00000000`00000000 : 0xfffff406`4039f7e0
fffff406`4039f7a0 00000000`00000000 : 00000000`00000000 fffff406`4039faa8 00000000`00000000 fffff406`4039f910 : 0xffffb587`00000000


SYMBOL_NAME: vgk+5180b6

MODULE_NAME: vgk

IMAGE_NAME: vgk.sys

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 5180b6

FAILURE_BUCKET_ID: AV_R_INVALID_vgk!unknown_function

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {b36e8bf9-ceaa-edef-4fc4-24c03e23c347}

Followup: MachineOwner
---------
[/CODE]