Çözüldü Valorant'a girince mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 10
Çözüm
EgeN7
Evet şimdi bir problem yok.

* BIOS güncel.
* Ekran kartı sürücüleri ile alakalı bir problem var gibi.

* Ekran kartı sürücünüz 17 Mart 2023'ten kalma.
Rich (BB code): 
    Image path: \SystemRoot\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_50916785244854f2\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Mar 17 02:16:07 2023 (6413A337)
    CheckSum:         037956CA
    ImageSize:        03897000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:


* İlk etapta onu güncelleyerek başlayın.
* Garanti olsun diyorsanız Rehber: DDU ile Sürücü Kaldırma Rehberi bu rehberi takip ederek sürücüleri temizleyin ve yenisini yükleyin.
* Zorunlu değil, ama öneririm.

Güncel sürüm:
www.nvidia.com

GeForce Game Ready Driver | 535.98 | Windows 10 64-bit, Windows 11 | NVIDIA

Download the English (US) GeForce Game Ready Driver for Windows 10 64-bit, Windows 11 systems. Released 2023.5.30
www.nvidia.com


Ekran kartı sürücü güncellemesinden sonra mavi ekran alırsanız yeni minidump dosyalarınızı paylaşın.



* Buradan sonrasını yapmasanız da olur, genel performans ve güncel olmak adına öneriyorum.

* Ses sürücünüz eski kalmış, güncelleyebilirsiniz.

SSD'niz Adata Legend 700 512GBPCIe Gen3 x4 M.2 NVMe SSD mi?

* Adata'nın yazılımı var mı sistemde? Varsa firmware güncellemelerini kontrol edin.
* Yoksa indirip kurun, firmware güncellemesi var mı diye bir bakın.
* Sağlığını da bir kontrol edin.
ADATA SSD ToolBox


* Windows eski görünüyor. Bazen dökümlerden güncel mi değil mi anlaşılmıyor, güncel değilse Windows Update aracılığıyla güncelleyin işletim sisteminizi.


Dökümler:
Kod: 
*******************************************************************************
*                                                                             *
*                        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: ffffa9405d6bf558, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
    bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the processor decided the fault was due to a corrupted PTE.
    bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
    - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8064be57804, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1499

    Key  : Analysis.Elapsed.mSec
    Value: 4078

    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: 187

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Failure.Bucket
    Value: AV_R_(null)_nt!ExpAllocateHandleTableEntry

    Key  : Failure.Hash
    Value: {057ca722-8246-3c91-57a3-2501ef38bce9}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  50

BUGCHECK_P1: ffffa9405d6bf558

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8064be57804

BUGCHECK_P4: 2

FILE_IN_CAB:  060423-7359-01.dmp.dmp

READ_ADDRESS: fffff8064c4fb390: 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
 ffffa9405d6bf558

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  StartMenuExperienceHost.exe

TRAP_FRAME:  ffffa202b34474a0 -- (.trap 0xffffa202b34474a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffff920b731832c0
rdx=ffffa9005aec5b40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8064be57804 rsp=ffffa202b3447630 rbp=0000000000000008
 r8=ffffa202b3447640  r9=0000000000000000 r10=0000000000000000
r11=ffffa900619914b6 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
nt!ExpAllocateHandleTableEntry+0xe4:
fffff806`4be57804 498b4708        mov     rax,qword ptr [r15+8] ds:00000000`00000008=????????????????
Resetting default scope

STACK_TEXT:
ffffa202`b34471f8 fffff806`4bc4af53     : 00000000`00000050 ffffa940`5d6bf558 00000000`00000000 ffffa202`b34474a0 : nt!KeBugCheckEx
ffffa202`b3447200 fffff806`4ba6e7b0     : 00000000`00000000 00000000`00000000 ffffa202`b3447520 00000000`00000000 : nt!MiSystemFault+0x1b2563
ffffa202`b3447300 fffff806`4bc0bad8     : ffffa900`619d4030 ffffa202`b34476a0 ffffa900`5d606980 ffffa202`b34477f0 : nt!MmAccessFault+0x400
ffffa202`b34474a0 fffff806`4be57804     : ffffa900`5aec5b40 00000000`00000001 00000000`00000000 00000000`00000006 : nt!KiPageFault+0x358
ffffa202`b3447630 fffff806`4be576a8     : 00000000`00000400 00000000`00000000 ffffa900`5aec5b00 ffff920b`731832c0 : nt!ExpAllocateHandleTableEntry+0xe4
ffffa202`b3447680 fffff806`4becebd6     : 00000000`00000000 00000000`00000000 ffffa202`b3447ac0 ffff920b`00000000 : nt!ExCreateHandleEx+0x78
ffffa202`b34476d0 fffff806`4ba33d8c     : 00000000`00000000 ffffa900`61991450 00000000`00000000 0000004f`c8cfd1d0 : nt!RtlpInsertStringAtom+0x2a
ffffa202`b3447710 fffff806`4bec4034     : ffffa900`5aed6630 00000000`00000026 0000004f`c8cfd1c0 0000004f`c8cfd1c0 : nt!RtlAddAtomToAtomTableEx+0x13c
ffffa202`b34477b0 fffff806`4bc0f7f5     : ffff920b`731832c0 000001ea`75350000 ffffa202`b3447ac0 ffff920b`730a3080 : nt!NtAddAtomEx+0x124
ffffa202`b3447a40 00007fff`0a98ddc4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000004f`c8cfd118 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`0a98ddc4


SYMBOL_NAME:  nt!ExpAllocateHandleTableEntry+e4

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3031

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  e4

FAILURE_BUCKET_ID:  AV_R_(null)_nt!ExpAllocateHandleTableEntry

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {057ca722-8246-3c91-57a3-2501ef38bce9}

Followup:     MachineOwner
---------


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffffffffffffff9f, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff8059da8cda6, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1531

    Key  : Analysis.Elapsed.mSec
    Value: 4122

    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: 187

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key  : Failure.Bucket
    Value: AV_dxgmms2!VidSchiProfilePerformanceTick

    Key  : Failure.Hash
    Value: {cb0b1289-fb87-52e2-f284-4f9f64401311}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  d1

BUGCHECK_P1: ffffffffffffff9f

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8059da8cda6

FILE_IN_CAB:  060423-7125-01.dmp.dmp

READ_ADDRESS: fffff805650fb390: 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
 ffffffffffffff9f

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  VALORANT-Win64-Shipping.exe

TRAP_FRAME:  ffff8806cca8a1e0 -- (.trap 0xffff8806cca8a1e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=3e2f5f2515890000
rdx=000000000000000e rsi=0000000000000000 rdi=0000000000000000
rip=fffff8059da8cda6 rsp=ffff8806cca8a370 rbp=0000000000000000
 r8=ffff8806cca89ee0  r9=0000000000000000 r10=0000000000000000
r11=fffff8059dab2680 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
dxgmms2!VidSchiProfilePerformanceTick+0x12926:
fffff805`9da8cda6 4c8b559f        mov     r10,qword ptr [rbp-61h] ss:0018:ffffffff`ffffff9f=????????????????
Resetting default scope

STACK_TEXT:
ffff8806`cca8a098 fffff805`64810029     : 00000000`0000000a ffffffff`ffffff9f 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffff8806`cca8a0a0 fffff805`6480bbe3     : 00000000`00000000 fffff805`9da93d62 00000000`00000000 fffff805`7f2cd5cf : nt!KiBugCheckDispatch+0x69
ffff8806`cca8a1e0 fffff805`9da8cda6     : ffffca03`bd5b9000 00000000`00000001 ffff8806`cca8a418 ffffca03`c5f5a240 : nt!KiPageFault+0x463
ffff8806`cca8a370 fffff805`9daabf1c     : ffffca03`c2bfc630 ffff8806`cca8a4b4 ffffca03`c693f010 ffffca03`bd5b9000 : dxgmms2!VidSchiProfilePerformanceTick+0x12926
ffff8806`cca8a490 fffff805`9daaa0ca     : ffffca03`c693f010 ffffca03`bd561000 ffffca03`c693f120 ffffca03`c2d99010 : dxgmms2!VidSchiSubmitCommandPacketToHwQueue+0xc8
ffff8806`cca8a510 fffff805`7f4fee0c     : 00000000`00000000 00000000`00000000 00000000`08000000 ffffca03`c2d99010 : dxgmms2!VidSchSubmitCommandToHwQueue+0x2da
ffff8806`cca8a570 fffff805`7f501c6a     : ffff8806`cca8aac0 ffff8806`cca8a908 ffff8806`cca8a908 ffff8806`cca8a941 : dxgkrnl!DXGHWQUEUE::SubmitCommand+0x5d4
ffff8806`cca8a880 fffff805`7f5018db     : 000000a6`79ccfa80 ffffca03`c4ace080 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkSubmitCommandToHwQueueInternal+0x382
ffff8806`cca8aa10 fffff805`6480ff9a     : ffffca03`c4ace080 ffffca03`c36e82e0 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkSubmitCommandToHwQueue+0xb
ffff8806`cca8aa40 00007ffc`aa5e5b04     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x3ef
000000a6`79ccf9e8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`aa5e5b04


SYMBOL_NAME:  dxgmms2!VidSchiProfilePerformanceTick+12926

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.2965

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  12926

FAILURE_BUCKET_ID:  AV_dxgmms2!VidSchiProfilePerformanceTick

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {cb0b1289-fb87-52e2-f284-4f9f64401311}

Followup:     MachineOwner
---------


*******************************************************************************
*                                                                             *
*                        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: ffffa40d609a1378, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
    bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the processor decided the fault was due to a corrupted PTE.
    bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
    - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff804e473220b, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1437

    Key  : Analysis.Elapsed.mSec
    Value: 3899

    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: 13946

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Failure.Bucket
    Value: AV_R_(null)_WdNisDrv!unknown_function

    Key  : Failure.Hash
    Value: {277a463a-5282-a91c-e1d6-c17eaf8303e7}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  50

BUGCHECK_P1: ffffa40d609a1378

BUGCHECK_P2: 0

BUGCHECK_P3: fffff804e473220b

BUGCHECK_P4: 2

FILE_IN_CAB:  060423-7390-01.dmp.dmp

READ_ADDRESS: fffff8046d2fb390: 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
 ffffa40d609a1378

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

TRAP_FRAME:  ffffb58d5332d980 -- (.trap 0xffffb58d5332d980)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa40f5feb8480 rbx=0000000000000000 rcx=0000000000000136
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff804e473220b rsp=ffffb58d5332db10 rbp=ffffb58d5332dc60
 r8=ffffb58d5332db80  r9=0000000000000108 r10=ffffa40d609a1350
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
WdNisDrv+0x220b:
fffff804`e473220b 418b7a28        mov     edi,dword ptr [r10+28h] ds:ffffa40d`609a1378=????????
Resetting default scope

STACK_TEXT:
ffffb58d`5332d6d8 fffff804`6ca4af53     : 00000000`00000050 ffffa40d`609a1378 00000000`00000000 ffffb58d`5332d980 : nt!KeBugCheckEx
ffffb58d`5332d6e0 fffff804`6c86e7b0     : 00000000`00000008 00000000`00000000 ffffb58d`5332da00 00000000`00000000 : nt!MiSystemFault+0x1b2563
ffffb58d`5332d7e0 fffff804`6ca0bad8     : ffffa40f`627dc790 ffffa40f`627dc790 ffffa40f`627d020c 00000000`00000000 : nt!MmAccessFault+0x400
ffffb58d`5332d980 fffff804`e473220b     : ffffb58d`5332db98 ffffb58d`5332db90 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x358
ffffb58d`5332db10 ffffb58d`5332db98     : ffffb58d`5332db90 00000000`00000000 00000000`00000000 00000000`00000000 : WdNisDrv+0x220b
ffffb58d`5332db18 ffffb58d`5332db90     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : 0xffffb58d`5332db98
ffffb58d`5332db20 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000001 ffffa40f`627d020c : 0xffffb58d`5332db90


SYMBOL_NAME:  WdNisDrv+220b

MODULE_NAME: WdNisDrv

IMAGE_NAME:  WdNisDrv.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  220b

FAILURE_BUCKET_ID:  AV_R_(null)_WdNisDrv!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {277a463a-5282-a91c-e1d6-c17eaf8303e7}

Followup:     MachineOwner
---------


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffc40a62bc92b0, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff8021f6b4694, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1593

    Key  : Analysis.Elapsed.mSec
    Value: 3467

    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: 186

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xa

    Key  : Failure.Bucket
    Value: AV_nt!MiGetPageProtection

    Key  : Failure.Hash
    Value: {41372a35-237d-1281-82f6-8f5f9bf6044a}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  a

BUGCHECK_P1: ffffc40a62bc92b0

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff8021f6b4694

FILE_IN_CAB:  060223-7812-01.dmp.dmp

READ_ADDRESS: fffff802200fb390: 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
 ffffc40a62bc92b0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WmiPrvSE.exe

TRAP_FRAME:  ffffec854bb872f0 -- (.trap 0xffffec854bb872f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc40a62bc92b0 rbx=0000000000000000 rcx=00000000ffffffff
rdx=00000000000003ff rsi=0000000000000000 rdi=0000000000000000
rip=fffff8021f6b4694 rsp=ffffec854bb87480 rbp=0000000000000000
 r8=ffffec854bb87558  r9=ffffec854bb87554 r10=fffff77bbddee7f8
r11=fffff77bbddee000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
nt!MiGetPageProtection+0x4d4:
fffff802`1f6b4694 488b08          mov     rcx,qword ptr [rax] ds:ffffc40a`62bc92b0=????????????????
Resetting default scope

STACK_TEXT:
ffffec85`4bb871a8 fffff802`1f810029     : 00000000`0000000a ffffc40a`62bc92b0 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffec85`4bb871b0 fffff802`1f80bbe3     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffec85`4bb872f0 fffff802`1f6b4694     : 0000007f`fffffff8 00000000`00000000 ffff8802`e740e038 00000000`00000000 : nt!KiPageFault+0x463
ffffec85`4bb87480 fffff802`1f6b3005     : 00000000`00000000 00000000`00000000 ffffec85`4bb87558 ffffec85`4bb87554 : nt!MiGetPageProtection+0x4d4
ffffec85`4bb87500 fffff802`1f62c2bf     : 00000000`00000000 0000024f`76e60000 c40263f5`b050ff4d 00000000`00001400 : nt!MiQueryAddressState+0x4b5
ffffec85`4bb87710 fffff802`1fa22a6c     : ffffec85`4bb80000 00000000`00000000 ffffc402`00000000 ffffc402`00000000 : nt!MiQueryAddressSpan+0xcf
ffffec85`4bb877d0 fffff802`1fa22215     : ffffeb03`b6b8ca6c 00000000`00000000 00000192`99f5e7c0 00000000`00001634 : nt!MmQueryVirtualMemory+0x83c
ffffec85`4bb87980 fffff802`1f80f7f5     : 00000000`00000000 00000192`99f5e7b8 00000000`00000000 00000000`00000000 : nt!NtQueryVirtualMemory+0x25
ffffec85`4bb879d0 00007fff`60e8d514     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000004c`6197d3e8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007fff`60e8d514


SYMBOL_NAME:  nt!MiGetPageProtection+4d4

MODULE_NAME: nt

IMAGE_VERSION:  10.0.19041.3031

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  4d4

FAILURE_BUCKET_ID:  AV_nt!MiGetPageProtection

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {41372a35-237d-1281-82f6-8f5f9bf6044a}

Followup:     MachineOwner
---------


*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff8006c063d37, Address of the instruction which caused the BugCheck
Arg3: ffffc686ae06e1b0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1530

    Key  : Analysis.Elapsed.mSec
    Value: 5004

    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: 202

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x3b

    Key  : Failure.Bucket
    Value: AV_dxgmms2!McGenEventWrite_EtwWriteTransfer

    Key  : Failure.Hash
    Value: {5f66c0bb-d30c-22d8-775d-3fe51eb41150}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8006c063d37

BUGCHECK_P3: ffffc686ae06e1b0

BUGCHECK_P4: 0

FILE_IN_CAB:  060123-7531-01.dmp.dmp

CONTEXT:  ffffc686ae06e1b0 -- (.cxr 0xffffc686ae06e1b0)
rax=0000000000000002 rbx=0000000000000000 rcx=ffff908ad6514310
rdx=fffff8006c082d50 rsi=0000000000000004 rdi=ffff908a83ca2520
rip=fffff8006c063d37 rsp=ffffc686ae06ebb0 rbp=ffffc686ae06ec59
 r8=ffffc686ae06ec20  r9=0000000000000006 r10=0000000000002df4
r11=0000000000000006 r12=0000000000000000 r13=0000000000160000
r14=ffff908a83ca2548 r15=0000000000160000
iopl=0         nv up ei pl nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050202
dxgmms2!McGenEventWrite_EtwWriteTransfer+0x27:
fffff800`6c063d37 450fb70a        movzx   r9d,word ptr [r10] ds:002b:00000000`00002df4=????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  VALORANT-Win64-Shipping.exe

STACK_TEXT:
ffffc686`ae06ebb0 fffff800`6c067e27     : 00000000`00000000 ffffc686`ae06fa40 00000000`00000004 00000000`00802000 : dxgmms2!McGenEventWrite_EtwWriteTransfer+0x27
ffffc686`ae06ebf0 fffff800`6c0d6b20     : ffff908a`83ca2520 00000000`00010001 00000000`00000004 0000020b`a7d20000 : dxgmms2!McTemplateK0pxqqt_EtwWriteTransfer+0x8b
ffffc686`ae06eca0 fffff800`6c0a0292     : ffffc686`ae06edf0 00000000`02000000 ffff908a`83ca2520 fffff800`6c063d62 : dxgmms2!VIDMM_RECYCLE_BLOCK::Allocate+0x36860
ffffc686`ae06ed00 fffff800`6c0a05da     : 00000000`00000000 00000000`00010000 ffffe084`dd3ac978 ffffe084`dd3ac920 : dxgmms2!VIDMM_RECYCLE_HEAP::CreateBlockForType+0x66
ffffc686`ae06ed30 fffff800`6c0a1fa8     : 00000000`00000000 00000000`00010000 00000000`00000001 ffffc686`0000001c : dxgmms2!VIDMM_RECYCLE_HEAP::CreateBlockAndRange+0x42
ffffc686`ae06eda0 fffff800`6c0a1d87     : ffffe084`dd3ac978 00000000`00160000 00000000`00000001 ffffc686`ae06ef70 : dxgmms2!VIDMM_RECYCLE_HEAP::Allocate+0x128
ffffc686`ae06ee70 fffff800`6c0ba1c8     : ffffe084`ce010300 00000000`00000000 ffffe084`ce013900 00000000`00000002 : dxgmms2!VIDMM_RECYCLE_HEAP_MGR::Allocate+0x127
ffffc686`ae06ef00 fffff800`6c0b9b36     : 00000000`00000001 00000000`33306956 00000000`00000000 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::CommitLocalBackingStore+0x498
ffffc686`ae06f000 fffff800`6c0b91fd     : ffffe084`e2e87490 00000000`00000002 ffffb600`00000000 ffff908a`db8f0010 : dxgmms2!VIDMM_GLOBAL::OpenLocalAllocation+0x116
ffffc686`ae06f0c0 fffff800`6c0b8d96     : ffffc686`ae06f388 ffffe084`e39adbd0 ffff908a`db8f0010 00000000`00000000 : dxgmms2!VIDMM_GLOBAL::OpenOneAllocation+0x42d
ffffc686`ae06f240 fffff800`6c052523     : 00000000`00000000 00000000`01001002 00000000`00000000 ffffc686`00000005 : dxgmms2!VIDMM_GLOBAL::OpenAllocation+0x52
ffffc686`ae06f290 fffff800`4e55067e     : 00000000`00000000 fffff692`9fee79ff ffff908a`851055c0 00000000`00000000 : dxgmms2!VidMmOpenAllocation+0x53
ffffc686`ae06f2f0 fffff800`4e4f3a9e     : 00000000`00000000 ffffc686`ae06f830 ffff908a`80598860 ffff908a`80598b30 : dxgkrnl!DXGDEVICE::CreateVidMmAllocations+0x8ee
ffffc686`ae06f400 fffff800`4e4f01f3     : ffffe084`d8b96c30 ffffc686`ae06fac0 00000000`00000000 ffff908a`88d2a820 : dxgkrnl!DXGDEVICE::CreateAllocation+0x124e
ffffc686`ae06f770 fffff800`4e5574ed     : ffffe084`ddac0f34 00000000`00501802 ffffe084`ddac35c0 00000000`00000001 : dxgkrnl!DxgkCreateAllocationInternal+0xbd3
ffffc686`ae06fa00 fffff800`3440ff9a     : ffffe084`ddac35c0 ffffe084`e2cc5260 00000000`00000000 00000000`00000000 : dxgkrnl!DxgkCreateAllocation+0xd
ffffc686`ae06fa40 00007ff8`f7d94784     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExitPico+0x3ef
000000ea`f2bdb258 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`f7d94784


SYMBOL_NAME:  dxgmms2!McGenEventWrite_EtwWriteTransfer+27

MODULE_NAME: dxgmms2

IMAGE_NAME:  dxgmms2.sys

IMAGE_VERSION:  10.0.19041.2965

STACK_COMMAND:  .cxr 0xffffc686ae06e1b0 ; kb

BUCKET_ID_FUNC_OFFSET:  27

FAILURE_BUCKET_ID:  AV_dxgmms2!McGenEventWrite_EtwWriteTransfer

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5f66c0bb-d30c-22d8-775d-3fe51eb41150}

Followup:     MachineOwner
---------
Tarihe göre sırala Puana göre sırala
İlgi ve alakanız için çok teşekkür ederim hocam kurulum yapıp sorunların gidip gitmediğini kontrol edeceğim

hocam win11 yükledim en son driverları güncelleyerek ama hala oyunlarda mavi ekran hatası alıyorum takılıp kalıyor minidump dosyalarımı yolluyorum.

minidump: Masaüstü.rar

@EgeN7

İnceleyebildiniz mi hocam dosyayı neden acaba sorun? @EgeN7
 
Son düzenleme:
Artı 0 Eksi
* Birinden pek bir şey anlaşılmıyor ancak diğeri biraz daha anlaşılır.

* ATTEMPTED_WRITE_TO_READONLY_MEMORY (be) genelde sürücü kaynaklı oluyor. Zaman zaman da RAM.

* Hatanın kaynağı NTIOLib_X64.sys sürücüsü gibi görünüyor. Başka bir sürücü ile çakışmış olabilir. MSI Afterburner var galiba sistemde.


Name:NTIOLib_X64.sys
Info:MSI Afterburner driver known BSOD issues with Windows Also found to be a part of MSI Live Update 5, MSI Super Charger & MSI Smart Utilities.

Recently (Nov 2014) there have been numerous instances of this driver in memory dumps. Analysis reveals that they are scattered throughout the filesystem by the installed MSI command utilities. For now I suggest uninstalling them all.
Source:http://event.msi.com/vga/afterburner/download.htm


* Bu listedeki herhangi bir sürücü/program varsa bunları şimdilik kaldırın. Yüksek ihtimalle güncel değiller, bozuklar veya başka bir sürücüyle çakışıyorlar.

* Kaldırdıktan sonra yine de NTIOLib_X64.sys diye bir dosya kalmış mı diye aratın her bir diskinizde.

* Ayrıca sistemde Windows'un Hyper-V (sanallaştırma sistemi) açık. Sanal makine, sanal makine yazılımı, emülatör (BlueStacks vs.) kullanmıyorsanız Hyper-V'yi kapatın gitsin. BIOS'tan da SVM (sanallaştırma) modunu kapatabilirsiniz sanallaştırmayla işiniz yoksa. Özellikle Hyper-V bazı oyunlar ve anti-hileler ile problem çıkarmasıyla ünlü.


* Problem RAM'de de olabilir, hatalarınız devam ederse yeni dökümleri paylaşın. Duruma göre Memtest86 ile test gerekebilir.



Kod: 
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

ATTEMPTED_WRITE_TO_READONLY_MEMORY (be)
An attempt was made to write to readonly memory.  The guilty driver is on the
stack trace (and is typically the current instruction pointer).
When possible, the guilty driver's name (Unicode string) is printed on
the BugCheck screen and saved in KiBugCheckDriver.
Arguments:
Arg1: ffff9a8029d5b6c8, Virtual address for the attempted write.
Arg2: 8a00000000200121, PTE contents.
Arg3: ffffa98ab2161c80, (reserved)
Arg4: 000000000000000a, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1515

    Key  : Analysis.Elapsed.mSec
    Value: 1583

    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: 187

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xbe

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    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_nt!MiRaisedIrqlFault

    Key  : Failure.Hash
    Value: {3b24175f-7f5b-9c9f-8aaf-822c248bf0f5}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  be

BUGCHECK_P1: ffff9a8029d5b6c8

BUGCHECK_P2: 8a00000000200121

BUGCHECK_P3: ffffa98ab2161c80

BUGCHECK_P4: a

FILE_IN_CAB:  060523-6843-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  VALORANT-Win64

TRAP_FRAME:  ffffa98ab2161c80 -- (.trap 0xffffa98ab2161c80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=11d145c078680000
rdx=ffffcf67b3d9e000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80481081313 rsp=ffffa98ab2161e10 rbp=ffff9a8029d5b6b0
 r8=ffffcf67806f8ce0  r9=0000000000000000 r10=ffffcf67b3d9e7f8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe cy
nt!MiAgePteWorker+0x353:
fffff804`81081313 f0480fba6d183f  lock bts qword ptr [rbp+18h],3Fh ss:0018:ffff9a80`29d5b6c8=0000000000000000
Resetting default scope

STACK_TEXT:
ffffa98a`b2161b08 fffff804`812dbf5e     : 00000000`000000be ffff9a80`29d5b6c8 8a000000`00200121 ffffa98a`b2161c80 : nt!KeBugCheckEx
ffffa98a`b2161b10 fffff804`8103794f     : 8a000000`00200121 00000000`00000003 ffffa98a`b2161c19 00000000`00000000 : nt!MiRaisedIrqlFault+0x1a100e
ffffa98a`b2161b60 fffff804`8123cd29     : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : nt!MmAccessFault+0x3af
ffffa98a`b2161c80 fffff804`81081313     : ffffd584`e91bb780 ffff9a80`07297680 00000000`00000000 ffffd584`f0f2a000 : nt!KiPageFault+0x369
ffffa98a`b2161e10 fffff804`81080c87     : 00000000`00000000 00000000`00000003 ffff9a80`29d5b6b0 81000004`6149f225 : nt!MiAgePteWorker+0x353
ffffa98a`b2161e70 fffff804`81034f96     : ffffa98a`b21623d0 ffffa98a`b21623d0 ffffa98a`b21623d0 00000000`00000000 : nt!MiAgePte+0x147
ffffa98a`b2161f10 fffff804`8103535a     : ffffa98a`00000000 ffffd584`e91bb780 ffffcf67`00000000 ffffa98a`b2162420 : nt!MiWalkPageTablesRecursively+0x266
ffffa98a`b2161fa0 fffff804`8103535a     : ffffa98a`00000000 ffffd584`e91bb780 ffffcf67`00000000 ffffa98a`b2162430 : nt!MiWalkPageTablesRecursively+0x62a
ffffa98a`b2162030 fffff804`8103535a     : ffffa98a`b21623d0 ffffd584`e91bb780 ffffcf67`00000000 ffffa98a`b2162440 : nt!MiWalkPageTablesRecursively+0x62a
ffffa98a`b21620c0 fffff804`8104c711     : 00000000`00000000 ffffd584`e91bb780 00000000`00000000 ffffa98a`b2162450 : nt!MiWalkPageTablesRecursively+0x62a
ffffa98a`b2162150 fffff804`8104c0ac     : ffffa98a`b21623d0 ffffa98a`00000002 ffffd584`00000002 00000000`00000000 : nt!MiWalkPageTables+0x371
ffffa98a`b2162250 fffff804`8104bc65     : ffffd584`00000000 00000000`00000000 ffffd584`e91bb780 fffff804`81015d9b : nt!MiAgeWorkingSet+0x21c
ffffa98a`b2162750 fffff804`81015677     : ffffa98a`b21628d0 ffffd584`e91bb780 ffffa98a`00000400 00000000`00000000 : nt!MiTrimOrAgeWorkingSet+0xd5
ffffa98a`b21627d0 fffff804`81014468     : 00000000`00000000 fffff804`81a6b280 fffff804`81a6b280 ffffd584`e105c1a0 : nt!MiProcessWorkingSets+0x2f7
ffffa98a`b2162980 fffff804`811d42b7     : 00000000`00000007 00000000`00000007 00000000`ffffffff ffffaa80`769d6180 : nt!MiWorkingSetManager+0xe8
ffffa98a`b2162a40 fffff804`810ccfd7     : ffffd584`e119e040 00000000`00000080 fffff804`81a6b280 00000000`ed03a29b : nt!KeBalanceSetManager+0x157
ffffa98a`b2162b30 fffff804`81231054     : ffffaa80`769d6180 ffffd584`e119e040 fffff804`810ccf80 00000000`dbfc821c : nt!PspSystemThreadStartup+0x57
ffffa98a`b2162b80 00000000`00000000     : ffffa98a`b2163000 ffffa98a`b215c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  nt!MiRaisedIrqlFault+1a100e

MODULE_NAME: nt

IMAGE_VERSION:  10.0.22621.1778

STACK_COMMAND:  .cxr; .ecxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  1a100e

FAILURE_BUCKET_ID:  AV_nt!MiRaisedIrqlFault

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3b24175f-7f5b-9c9f-8aaf-822c248bf0f5}

Followup:     MachineOwner
---------




*******************************************************************************
*                                                                             *
*                        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: ffff8109997dfa00, memory referenced.
Arg2: 0000000000000000, X64: bit 0 set if the fault was due to a not-present PTE.
    bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the processor decided the fault was due to a corrupted PTE.
    bit 4 is set if the fault was due to attempted execute of a no-execute PTE.
    - ARM64: bit 1 is set if the fault was due to a write, clear if a read.
    bit 3 is set if the fault was due to attempted execute of a no-execute PTE.
Arg3: fffff8037f49aab3, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


KEY_VALUES_STRING: 1

    Key  : AV.Type
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 1687

    Key  : Analysis.Elapsed.mSec
    Value: 1873

    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: 124

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x50

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    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_(null)_nt!PsQueryProcessEnergyValues

    Key  : Failure.Hash
    Value: {5715fb98-07f8-2033-cc59-765f0443f745}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 21631230

    Key  : Hypervisor.Flags.ValueHex
    Value: 14a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7


BUGCHECK_CODE:  50

BUGCHECK_P1: ffff8109997dfa00

BUGCHECK_P2: 0

BUGCHECK_P3: fffff8037f49aab3

BUGCHECK_P4: 2

FILE_IN_CAB:  060523-6921-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

READ_ADDRESS: fffff8037fb1c468: 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
 ffff8109997dfa00

MM_INTERNAL_CODE:  2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  steam.exe

TRAP_FRAME:  ffffc30547ece9a0 -- (.trap 0xffffc30547ece9a0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffc30547ecee60 rbx=0000000000000000 rcx=ffffc30547ecef30
rdx=ffffc30547eceb50 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8037f49aab3 rsp=ffffc30547eceb30 rbp=ffff810da6170080
 r8=0000000000000000  r9=0000000000000014 r10=ffff8109997df940
r11=ffff810d997df578 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!PsQueryProcessEnergyValues+0x313:
fffff803`7f49aab3 498b82c0000000  mov     rax,qword ptr [r10+0C0h] ds:ffff8109`997dfa00=????????????????
Resetting default scope

STACK_TEXT:
ffffc305`47ece778 fffff803`7f28c861     : 00000000`00000050 ffff8109`997dfa00 00000000`00000000 ffffc305`47ece9a0 : nt!KeBugCheckEx
ffffc305`47ece780 fffff803`7f03783c     : 00000000`00000001 00000000`00000000 00000000`00000000 ffff8109`997dfa00 : nt!MiSystemFault+0x258a61
ffffc305`47ece880 fffff803`7f23cd29     : ffffc305`47eceba8 fffff803`7f0bad8a ffff810d`97544620 00000000`00000000 : nt!MmAccessFault+0x29c
ffffc305`47ece9a0 fffff803`7f49aab3     : ffff810d`a6170080 fffff803`00000000 00000000`00000000 ffff810d`97544040 : nt!KiPageFault+0x369
ffffc305`47eceb30 fffff803`7f4e0ea0     : ffff810d`97544040 ffff810d`97544040 00000000`00000315 ffff810d`97544be8 : nt!PsQueryProcessEnergyValues+0x313
ffffc305`47eceba0 fffff803`7f535239     : 00000048`041002ff 00000000`00010400 ffff810d`a6170080 00000000`00000000 : nt!ExpGetProcessInformation+0x840
ffffc305`47ecf1b0 fffff803`7f5346fb     : ffff810d`a6170080 00000000`00000000 00000000`00000000 00007ffd`721d5301 : nt!ExpQuerySystemInformation+0xad9
ffffc305`47ecf9e0 fffff803`7f240ee5     : ffff810d`a6170000 ffff810d`97546680 ffffc305`47ecfa38 ffffffff`ff676980 : nt!NtQuerySystemInformation+0x7b
ffffc305`47ecfa20 00007ffd`7448f314     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`0abadf08 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`7448f314


SYMBOL_NAME:  nt!PsQueryProcessEnergyValues+313

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.1778

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  313

FAILURE_BUCKET_ID:  AV_R_(null)_nt!PsQueryProcessEnergyValues

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {5715fb98-07f8-2033-cc59-765f0443f745}

Followup:     MachineOwner
---------
 
Son düzenleme:
Artı 0 Eksi
böyle bi test yaptım sonuç böyle hocam ramlerde mi sıkıntı var acaba ?

@EgeN7
 

Dosya Ekleri

  • stabilitytest.png
    stabilitytest.png
    54,5 KB · Görüntüleme: 21
Artı 0 Eksi
Tam olarak ne olduğu anlaşılmıyor.
Memtest86 ile de yapar mısınız RAM testini?
İşlemcide OC var mıydı?

www.technopat.net

Memtest86 ile Bozuk RAM Testi

Bu rehberimizde Memtes86 ile RAM testi yaparak bozuk RAM modüllerini nasıl tespit edeceğinize bakıyoruz. Bilgisayarda karşılaşılan mavi ekran hataları
www.technopat.net www.technopat.net
 
Artı 0 Eksi
RAM'lerde genel olarak iki çeşit OC var.

- Biri manuel yapılan yani voltaj, timing, CL, MHz gibi değerlerin elle değiştirildiği OC.
- Diğeri ise bunlara dokunmayıp direk hazır XMP profili etkinleştirme, oto OC.

Eğer daha önce RAM ayarlarına dokunmadıysanız yani sadece XMP açtıysanız voltaj ile alakalı bir problem olacağını sanmam. Ama her ihtimale karşı BIOS'a girip Load Defaults > Save yapıp çıkabilirsiniz. Daha sonra tekrar BIOS'a girin ve önemli ayarlarınızı yapın.

Sadece Valorant'ta mavi ekran alıyorsanız XMP'yi kapatıp oynamayı dener misiniz?
 
Artı 0 Eksi
Ben el ile yaptım onuda tam anlamayarak yaptım çünki biosta mesela 3200 var ama yanında bi sayılar daha veriyor anlamadım rasgele seçtim o yüzden galiba bios ayarlarını nasıl yaparım temiz bir şekilde hocam
 
Artı 0 Eksi

Benzer konular

iitricker
  • Soru
Valorant'a girince mavi ekran hatası
Mesaj
5
Görüntüleme
287
iitricker
iitricker
S
  • Soru
Valorant'a girince mavi ekran hatası
Mesaj
4
Görüntüleme
244
Stachen
S
K
  • Soru
Valorant'a girince mavi ekran hatası
2
Mesaj
14
Görüntüleme
894
Damon Salvatore
Damon Salvatore
Mece
  • Soru
Valorant'a girince mavi ekran hatası
Mesaj
1
Görüntüleme
347
denizsevim
denizsevim
mynameisbugra
  • Soru
Valorant'a girince "PAGE_FAULT_IN_NONPAGED_AREA" mavi ekran hatası
Mesaj
2
Görüntüleme
517
altotziki
altotziki

Yeni konular

Yeni mesajlar

Geri
Yukarı