Çözüldü Valorant oynarken mavi ekran veriyor

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 11

deniz ataman

Centipat
Katılım
10 Temmuz 2024
Mesajlar
18
Daha fazla  
Cinsiyet
Erkek
Valorant oynarken birdenbire mavi ekran hatası alıyorum. Ara sıra oluyor bu nedeni nedir acaba?
Sistem.
AMD Ryzen 5600.
GTX 1050 Ti OC.
B550-HDV
RAM SSD hard disk bilmiyorum.
Dump link: dump.rar
 
Çözüm
Memtest86 ile RAM'lerini test et. Sorun donanımsal ve RAM'den kaynaklı.

Valorant hatayı verdirtse bile, Vanguard çökse bile sebebi RAM'ler yüksek ihtimal
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the BugCheck.
Arg2: ffffd80e002f9000
Arg3: 0000000000000009
Arg4: fffff10aa639f080

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2281

Key : Analysis.Elapsed.mSec
Value: 8828

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x1a

Key : Bugcheck.Code.TargetModel
Value: 0x1a

Key : Failure.Bucket
Value: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

Key : Failure.Hash
Value: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1


BUGCHECK_CODE: 1a

BUGCHECK_P1: 61941

BUGCHECK_P2: ffffd80e002f9000

BUGCHECK_P3: 9

BUGCHECK_P4: fffff10aa639f080

FILE_IN_CAB: 080324-10718-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64-Shipping.exe

STACK_TEXT:
fffff10a`a639ef58 fffff805`34e3f58a : 00000000`0000001a 00000000`00061941 ffffd80e`002f9000 00000000`00000009 : nt!KeBugCheckEx
fffff10a`a639ef60 fffff805`34e26a7e : 00000000`00000002 fffff805`34c78919 aaaaaaaa`aaaaaaab 00000000`00000001 : nt!MmAccessFault+0x1d784a
fffff10a`a639f080 fffff805`34d4d23c : ffff8002`8194b660 00000000`017b8000 00000000`00010000 ffffd80e`002f7000 : nt!KiPageFault+0x37e
fffff10a`a639f218 fffff805`351d6691 : 00000000`00000000 00000000`00000004 00007fff`fffeffff 00000000`00000000 : nt!RtlFindClearBitsEx+0x1cc
fffff10a`a639f240 fffff805`351d64bc : 00000000`00010000 00000000`0003c000 00000000`00010000 00000000`00000000 : nt!MiFindEmptyAddressRange+0x151
fffff10a`a639f2e0 fffff805`351d3bf2 : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`0003c000 : nt!MiSelectUserAddress+0x15c
fffff10a`a639f380 fffff805`351c4c2e : fffff10a`a639f540 00000000`00000000 00000000`00000004 fffff10a`a639f4a8 : nt!MiReserveUserMemory+0x282
fffff10a`a639f440 fffff805`351c41b1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiAllocateVirtualMemory+0x38e
fffff10a`a639f5c0 fffff805`35158424 : 00000023`8dd4f280 fffff10a`a639f8f0 00000000`00000000 ffffffff`ffffffff : nt!MiAllocateVirtualMemoryCommon+0x111
fffff10a`a639f700 fffff805`4f03f9c0 : 00000000`00000000 fffff805`4efd0000 fffff10a`a639fa48 00000000`00000004 : nt!NtAllocateVirtualMemory+0x104
fffff10a`a639f7f0 00000000`00000000 : fffff805`4efd0000 fffff10a`a639fa48 00000000`00000004 ffff8002`00003000 : vgk+0x6f9c0


MODULE_NAME: hardware

IMAGE_NAME: hardware_ram

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

Followup: MachineOwner
Memtest86 ile RAM'lerini test et. Sorun donanımsal ve RAM'den kaynaklı.

Valorant hatayı verdirtse bile, Vanguard çökse bile sebebi RAM'ler yüksek ihtimal
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the BugCheck.
Arg2: ffffd80e002f9000
Arg3: 0000000000000009
Arg4: fffff10aa639f080

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2281

Key : Analysis.Elapsed.mSec
Value: 8828

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

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

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

Key : Bugcheck.Code.LegacyAPI
Value: 0x1a

Key : Bugcheck.Code.TargetModel
Value: 0x1a

Key : Failure.Bucket
Value: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

Key : Failure.Hash
Value: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

Key : WER.OS.Branch
Value: ni_release

Key : WER.OS.Version
Value: 10.0.22621.1


BUGCHECK_CODE: 1a

BUGCHECK_P1: 61941

BUGCHECK_P2: ffffd80e002f9000

BUGCHECK_P3: 9

BUGCHECK_P4: fffff10aa639f080

FILE_IN_CAB: 080324-10718-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: VALORANT-Win64-Shipping.exe

STACK_TEXT:
fffff10a`a639ef58 fffff805`34e3f58a : 00000000`0000001a 00000000`00061941 ffffd80e`002f9000 00000000`00000009 : nt!KeBugCheckEx
fffff10a`a639ef60 fffff805`34e26a7e : 00000000`00000002 fffff805`34c78919 aaaaaaaa`aaaaaaab 00000000`00000001 : nt!MmAccessFault+0x1d784a
fffff10a`a639f080 fffff805`34d4d23c : ffff8002`8194b660 00000000`017b8000 00000000`00010000 ffffd80e`002f7000 : nt!KiPageFault+0x37e
fffff10a`a639f218 fffff805`351d6691 : 00000000`00000000 00000000`00000004 00007fff`fffeffff 00000000`00000000 : nt!RtlFindClearBitsEx+0x1cc
fffff10a`a639f240 fffff805`351d64bc : 00000000`00010000 00000000`0003c000 00000000`00010000 00000000`00000000 : nt!MiFindEmptyAddressRange+0x151
fffff10a`a639f2e0 fffff805`351d3bf2 : 00000000`00000000 00000000`00000000 00000000`00000002 00000000`0003c000 : nt!MiSelectUserAddress+0x15c
fffff10a`a639f380 fffff805`351c4c2e : fffff10a`a639f540 00000000`00000000 00000000`00000004 fffff10a`a639f4a8 : nt!MiReserveUserMemory+0x282
fffff10a`a639f440 fffff805`351c41b1 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiAllocateVirtualMemory+0x38e
fffff10a`a639f5c0 fffff805`35158424 : 00000023`8dd4f280 fffff10a`a639f8f0 00000000`00000000 ffffffff`ffffffff : nt!MiAllocateVirtualMemoryCommon+0x111
fffff10a`a639f700 fffff805`4f03f9c0 : 00000000`00000000 fffff805`4efd0000 fffff10a`a639fa48 00000000`00000004 : nt!NtAllocateVirtualMemory+0x104
fffff10a`a639f7f0 00000000`00000000 : fffff805`4efd0000 fffff10a`a639fa48 00000000`00000004 ffff8002`00003000 : vgk+0x6f9c0


MODULE_NAME: hardware

IMAGE_NAME: hardware_ram

STACK_COMMAND: .cxr; .ecxr ; kb

FAILURE_BUCKET_ID: 0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

OS_VERSION: 10.0.22621.1

BUILDLAB_STR: ni_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {c6e5c6cf-692e-7852-5dc5-b74944540fc0}

Followup: MachineOwner
 
Son düzenleyen: Moderatör:
Çözüm
Memtest86 ile RAM'lerini test et. Sorun donanımsal ve RAM'den kaynaklı.

Valorant hatayı verdirtse bile, Vanguard çökse bile sebebi RAM'ler yüksek ihtimal.
MEMORY_MANAGEMENT (1a)
# Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, the subtype of the bugcheck.
Arg2: FFFFD80E002F9000.
Arg3: 0000000000000009.
Arg4: FffFF10AA639F080.

Debugging details:
------------------

*** Warnıng: Unable to verify timestamp for vgk.sys

Key_values_strıng: 1

Key: Analysis. CPU. Msec.
Value: 2281.

Key: Analysis. Elapsed. Msec.
Value: 8828.

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: 93.

Key: Analysis. Init. Elapsed. Msec.
Value: 10217.

Key: Analysis. Memory.commitpeak. MB.
Value: 86.

Key: Bugcheck. Code. Legacyapı.
Value: 0x1a.

Key: Bugcheck. Code. Targetmodel.
Value: 0x1a.

Key: Failure. Bucket.
Value: 0x1a_61941_Page_table_reserved_bıts_set_ımage_hardware_ram

Key: Failure. Hash.
Value: {C6E5C6CF-692e-7852-5DC5-B74944540FC0}

Key: Wer. OS. Branch.
Value: Ni_release.

Key: Wer. OS. Version.
Value: 10.0.22621.1

Bugcheck_code: 1A.

Bugcheck_p1: 61941.

Bugcheck_p2: FFFFD80E002F9000.

Bugcheck_p3: 9

Bugcheck_p4: FffFF10AA639F080.

Fıle_ın_cab: 080324-10718-01.dmp

Blackboxbsd: 1 (!blackboxbsd)

Blackboxntfs: 1 (!blackboxntfs)

Blackboxpnp: 1 (!blackboxpnp)

Blackboxwınlogon: 1

Customer_crash_count: 1

Process_name: VALORANT-Win64-Shipping.exe

Stack_text:
Fffff10a'A639EF58 fffff805'34e3F58a: 00000000'0000001A 00000000'00061941 ffffd80e'002F9000 00000000'00000009: NT! Kebugcheckex.
Fffff10a'A639EF60 fffff805'34e26a7e: 00000000'00000002 fffff805'34C78919 aaaaaaaa'aaaaaaab 00000000'00000001: NT! Mmaccessfault+0x1D784A
Fffff10a'A639F080 fffff805'34D4D23C: Ffff8002'8194B660 00000000'017b8000 00000000'00010000 ffffd80e'002F7000: NT! Kipagefault+0x37e
Fffff10a'A639F218 fffff805'351D6691: 00000000'00000000 00000000'00000004 00007FFF'fffeffff 00000000'00000000: NT! Rtlfindclearbitsex+0x1CC
Fffff10a'A639F240 fffff805'351D64bc: 00000000'00010000 00000000'0003C000 00000000'00010000 00000000'00000000: NT! Mifindemptyaddressrange+0x151
Fffff10a'A639F2E0 fffff805'351D3BF2: 00000000'00000000 00000000'00000000 00000000'00000002 00000000'0003C000: NT! Miselectuseraddress+0x15C
Fffff10a'A639F380 fffff805'351C4C2e: Fffff10a'A639F540 00000000'00000000 00000000'00000004 fffff10a'A639F4A8: NT! Mireserveusermemory+0x282
Fffff10a'A639F440 fffff805'351C41B1: 00000000'00000000 00000000'00000000 00000000'00000000 00000000'00000000: NT! Miallocatevirtualmemory+0x38e
Fffff10a'A639F5C0 fffff805'35158424: 00000023'8dd4F280 fffff10a'A639F8F0 00000000'00000000 ffffffff'ffffffff: NT! Miallocatevirtualmemorycommon+0x111
Fffff10a'A639F700 fffff805'4F03F9C0: 00000000'00000000 fffff805'4efd0000 fffff10a'A639FA48 00000000'00000004: NT! Ntallocatevirtualmemory+0x104
Fffff10a'A639F7F0 00000000'00000000: Fffff805'4efd0000 fffff10a'A639FA48 00000000'00000004 ffff8002'00003000: Vgk+0x6F9C0

Module_name: Hardware.

Image_name: Hardware_ram.

Stack_command: Cxr. Ecxr; KB.

Faılure_bucket_ıd: 0x1a_61941_Page_table_reserved_bıts_set_ımage_hardware_ram

Os_versıon: 10.0.22621.1

Buıldlab_str: Ni_release.

Osplatform_type: X64.

Osname: Windows 10.

Faılure_ıd_hash: {C6E5C6CF-692e-7852-5DC5-B74944540FC0}

Followup: Machineowner.

Bende öyle düşünüyordum RAM'im bayağı eski. Teşekkür ederim hocam sağ olun başka bir sıkıntı görünüyor mu?
 
Bende öyle düşünüyordum RAM'im bayağı eski. Teşekkür ederim hocam sağ olun başka bir sıkıntı görünüyor mu?

Dediğim gibi, Valorant ve RAM gözüküyor. Diğer modüllere bakmadım.
SteelSeries Sonar var. İstersende chipset falan güncelleyebilirsin fakat sebep RAM. İşine yaradı ise mesajımı çözüm olarak işaretlersen sevinirim. Fakat bundan önce istersen Memtest86 ile RAM testi yap. Sonuçlara bakalım.
 
Dediğim gibi, Valorant ve RAM gözüküyor. Diğer modüllere bakmadım.
SteelSeries Sonar var. İstersende chipset falan güncelleyebilirsin fakat sebep RAM. İşine yaradı ise mesajımı çözüm olarak işaretlersen sevinirim. Fakat bundan önce istersen Memtest86 ile RAM testi yap. Sonuçlara bakalım.

Sonarı kullanmıyorum inaktif chipset güncel. Test yapacağım sonra buraya yazarım.
 

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Geri
Yukarı