Yeni RX 6600 sistem Valorant'ta mavi ekran veriyor

Nuri3535

Femtopat
Katılım
16 Nisan 2023
Mesajlar
3
Daha fazla  
Cinsiyet
Erkek
Merhaba. Sistemi yeni topladım bazı ürünlerim 2. el olarak aldım her şeyi kurdum ve en son oyunları indirmeye başladım. İlk oyunmu indirdikden sonra (Valorant) direk mavi ekran aldım ve sürekli tekrarlamaya başladı sistemi onar dedim ve.
Windows System32 srttrail.txt hatası aldım onar dedim vs derken hiçbir şey yapamaz oldum formatladim tekrar RAM'leri Memtest86 kontrol için denedim çünkü ikinci el aldım çift slotta hata verirken tek tek işlem yaptırdığım da herhangi bir hata sorun bulmadı SSD sıfır aldım PSU 600 watt Bronze 22 garanti var.
Sistemim i3 12100 F 8x2 3200 RAM B660 Gigabyte anakart 512 SSD Hikvision RX6600 ekran kartı ne yapmam lazım sorunun ne olduğunu nerede olduğunu nasıl bulurum yardımlarınızı bekliyorum.

Yeni klasör.rar merhaba tekrardan rapor yukarıda yardımlarınızı bekliyorum.
 
Son düzenleme:
Memtest yaparak sorunun zaten ram kaynaklı olduğunu bulmuşsunuz. Ramleriniz farklı marka ve model mi ?

*******************************************************************************
* *
* 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: ffffb2d44383b8f0, 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: ffffb2d40350a23b, 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: 3577

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 29422

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x50

Key : Bugcheck.Code.Register
Value: 0x50

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: 041623-5593-01.dmp

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffb2d44383b8f0

BUGCHECK_P2: 0

BUGCHECK_P3: ffffb2d40350a23b

BUGCHECK_P4: 2

READ_ADDRESS: fffff80336afb390: 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
ffffb2d44383b8f0

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

TRAP_FRAME: ffffb30b2c33a560 -- (.trap 0xffffb30b2c33a560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb2d402e51e30 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=ffffb2d40350a23b rsp=ffffb30b2c33a6f0 rbp=ffffb30b2c33a7f0
r8=ffffb30b2c33a650 r9=0000000000000000 r10=0000000000000000
r11=ffffb30b2c33a670 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
win32kfull!RawInputThread+0x80b:
ffffb2d4`0350a23b 8b05af163300 mov eax,dword ptr [win32kfull!UmfdHostLifeTimeManager::s_CsrssAddInitialFontsThread+0x8 (ffffb2d4`0383b8f0)] ds:ffffb2d4`0383b8f0=????????
Resetting default scope

STACK_TEXT:
ffffb30b`2c33a2b8 fffff803`3624ab53 : 00000000`00000050 ffffb2d4`4383b8f0 00000000`00000000 ffffb30b`2c33a560 : nt!KeBugCheckEx
ffffb30b`2c33a2c0 fffff803`3606e7b0 : 00000000`00000000 00000000`00000000 ffffb30b`2c33a5e0 00000000`00000000 : nt!MiSystemFault+0x1b2173
ffffb30b`2c33a3c0 fffff803`3620b6d8 : fffff803`00000000 fffff803`32359740 fffff803`32355ac0 fffff803`36066b4f : nt!MmAccessFault+0x400
ffffb30b`2c33a560 ffffb2d4`0350a23b : 00000000`0000002f 00000000`000bc202 00000000`00000001 00000000`00000004 : nt!KiPageFault+0x358
ffffb30b`2c33a6f0 ffffb2d4`02c44564 : ffffcb03`4283a2c0 ffffcb03`4283a2c0 00000000`00000000 00000000`00000005 : win32kfull!RawInputThread+0x80b
ffffb30b`2c33a8b0 ffffb2d4`0354e9f1 : ffffcb03`4283a2c0 00000000`00000000 00000000`00000005 00000000`00000005 : win32kbase!xxxCreateSystemThreads+0xc4
ffffb30b`2c33a9e0 ffffb2d4`0303476e : ffffcb03`4283a2c0 ffffcb03`4283a2c0 00000000`00000000 00000000`00000000 : win32kfull!NtUserCallNoParam+0x71
ffffb30b`2c33aa10 fffff803`3620f3f5 : ffffcb03`00000005 00000000`00000005 0000018a`f2604030 00000000`00000228 : win32k!NtUserCallNoParam+0x16
ffffb30b`2c33aa40 00007ff9`cf7610e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000075`561bfb48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`cf7610e4


SYMBOL_NAME: win32kfull!RawInputThread+80b

MODULE_NAME: win32kfull

IMAGE_NAME: win32kfull.sys

IMAGE_VERSION: 10.0.19041.1223

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 80b

FAILURE_BUCKET_ID: AV_R_(null)_win32kfull!RawInputThread

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a9a6e391-d04b-d104-61ff-72fa1b030f98}

Followup: MachineOwner
 
Tamam demek ki birbiriyle uyumlu çalışmıyorlar.
 
Memtest yaparak sorunun zaten ram kaynaklı olduğunu bulmuşsunuz. Ramleriniz farklı marka ve model mi ?

*******************************************************************************
* *
* 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: ffffb2d44383b8f0, 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: ffffb2d40350a23b, 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: 3577

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 29422

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

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

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

Key : Bugcheck.Code.DumpHeader
Value: 0x50

Key : Bugcheck.Code.Register
Value: 0x50

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Timestamp
Value: 2019-12-06T14:06:00Z

Key : WER.OS.Version
Value: 10.0.19041.1


FILE_IN_CAB: 041623-5593-01.dmp

BUGCHECK_CODE: 50

BUGCHECK_P1: ffffb2d44383b8f0

BUGCHECK_P2: 0

BUGCHECK_P3: ffffb2d40350a23b

BUGCHECK_P4: 2

READ_ADDRESS: fffff80336afb390: 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
ffffb2d44383b8f0

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: csrss.exe

TRAP_FRAME: ffffb30b2c33a560 -- (.trap 0xffffb30b2c33a560)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffb2d402e51e30 rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=ffffb2d40350a23b rsp=ffffb30b2c33a6f0 rbp=ffffb30b2c33a7f0
r8=ffffb30b2c33a650 r9=0000000000000000 r10=0000000000000000
r11=ffffb30b2c33a670 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
win32kfull!RawInputThread+0x80b:
ffffb2d4`0350a23b 8b05af163300 mov eax,dword ptr [win32kfull!UmfdHostLifeTimeManager::s_CsrssAddInitialFontsThread+0x8 (ffffb2d4`0383b8f0)] ds:ffffb2d4`0383b8f0=????????
Resetting default scope

STACK_TEXT:
ffffb30b`2c33a2b8 fffff803`3624ab53 : 00000000`00000050 ffffb2d4`4383b8f0 00000000`00000000 ffffb30b`2c33a560 : nt!KeBugCheckEx
ffffb30b`2c33a2c0 fffff803`3606e7b0 : 00000000`00000000 00000000`00000000 ffffb30b`2c33a5e0 00000000`00000000 : nt!MiSystemFault+0x1b2173
ffffb30b`2c33a3c0 fffff803`3620b6d8 : fffff803`00000000 fffff803`32359740 fffff803`32355ac0 fffff803`36066b4f : nt!MmAccessFault+0x400
ffffb30b`2c33a560 ffffb2d4`0350a23b : 00000000`0000002f 00000000`000bc202 00000000`00000001 00000000`00000004 : nt!KiPageFault+0x358
ffffb30b`2c33a6f0 ffffb2d4`02c44564 : ffffcb03`4283a2c0 ffffcb03`4283a2c0 00000000`00000000 00000000`00000005 : win32kfull!RawInputThread+0x80b
ffffb30b`2c33a8b0 ffffb2d4`0354e9f1 : ffffcb03`4283a2c0 00000000`00000000 00000000`00000005 00000000`00000005 : win32kbase!xxxCreateSystemThreads+0xc4
ffffb30b`2c33a9e0 ffffb2d4`0303476e : ffffcb03`4283a2c0 ffffcb03`4283a2c0 00000000`00000000 00000000`00000000 : win32kfull!NtUserCallNoParam+0x71
ffffb30b`2c33aa10 fffff803`3620f3f5 : ffffcb03`00000005 00000000`00000005 0000018a`f2604030 00000000`00000228 : win32k!NtUserCallNoParam+0x16
ffffb30b`2c33aa40 00007ff9`cf7610e4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000075`561bfb48 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`cf7610e4


SYMBOL_NAME: win32kfull!RawInputThread+80b

MODULE_NAME: win32kfull

IMAGE_NAME: win32kfull.sys

IMAGE_VERSION: 10.0.19041.1223

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 80b

FAILURE_BUCKET_ID: AV_R_(null)_win32kfull!RawInputThread

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {a9a6e391-d04b-d104-61ff-72fa1b030f98}

Followup: MachineOwner
hocam ramler aynı her hangi bir fark yok 1ve 3 slotlara takmıştım şimdi 2 ve 4 slotlaranı taktım sorunsuz devam ediyoruz galiba anakartta bir sorun vardı pcyi uzun zamandır toplamaya çalışıyordum garanti ile uğraşmadım şuan için dedğim gibi maşallah sorun yok ama biraz daha sisteme doyunca anakartı bir garantiye yollayıp kontrollerini yaptırıcağım.
 

Technopat Haberler

Yeni konular

Geri
Yukarı