i7-13700K sistemde mavi ekran hataları

İşletim sistemi
Windows 10

Uskaaga

Centipat
Katılım
10 Ağustos 2022
Mesajlar
37
Daha fazla  
Cinsiyet
Erkek
RAM
G Skill Intl F5-6400J3239G162x16GB
SSD veya HDD modeli
Samsung 990 Pro NVMe PCIe M.2 2TB
Ekran kartı
Asus TUF Nvidia RTX 4070-Ti
Anakart
Asus ROG STRIX Z790-E GAMING WIFI
İşlemci
Intel Core i7-13700K
Merhaba, mavi ekran sebebi ile bilgisayardan artık soğudum. Yardımcı olabilecek olan var mıdır? Bazen 1 ay hiç yapmıyor bazen günde 5 kere yapıyor. Parça mı bozuk, Windows mu bozuk anlamanın yolu var mıdır? Güncellemeleri sıksık, Samsung Magician, Armoury Crate, GeForce Experience, Windows Update üzerinden bütün güncellemeleri yapıyorum. Elimden geldiğince 2-3 günde bir kontrol ediyorum ama belli ki güncellemelerle alakası yok. Bilgisayarı ilk aldığımda Windows 11 kurmuştu onda daha çok oluyordu, onu silip temizleyim boş SSD'ye Windows 10 kurdum bunda daha az oluyor ama yine de var. Yani artık ya çözümü bulacağım ya bilgisayarı satacağım o derece gına geldi. Birisi yardımcı olursa çok sevinirim.

Mart ayında da sıkılıp bir destek için kayıt almışım bu o;
Bugün yine bir minidump kaydı aldım;
 
Son düzenleyen: Moderatör:
Kod:
************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 19041 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Kernel base = 0xfffff804`5ee00000 PsLoadedModuleList = 0xfffff804`5fa2a350
Debug session time: Sun Jul 9 20:32:17.153 2023 (UTC + 3:00)
System Uptime: 0 days 0:01:40.753
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..............
Loading User Symbols
PEB is paged out (Peb.Ldr = 0000001d`29013018). Type ".hh dbgerr001" for details
Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`5f1fc030 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff8b8a`449ee550=0000000000000050
0: 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: ffff8b8a449eefc0, memory referenced.
Arg2: 0000000000000011, 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: ffff8b8a449eefc0, If non-zero, the instruction address which referenced the bad memory
 address.
Arg4: 0000000000000002, (reserved)

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

KEY_VALUES_STRING: 1

 Key : AV.PTE
 Value: Valid

 Key : AV.Type
 Value: Execute

 Key : Analysis.CPU.mSec
 Value: 8218

 Key : Analysis.Elapsed.mSec
 Value: 12425

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

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

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

 Key : Bugcheck.Code.LegacyAPI
 Value: 0x50

 Key : Failure.Bucket
 Value: AV_X_(null)_nt!MiSystemFault

 Key : Failure.Hash
 Value: {49578414-34a9-c6dc-c795-b8c5552d5975}

 Key : WER.OS.Branch
 Value: vb_release

 Key : WER.OS.Version
 Value: 10.0.19041.1

BUGCHECK_CODE: 50

BUGCHECK_P1: ffff8b8a449eefc0

BUGCHECK_P2: 11

BUGCHECK_P3: ffff8b8a449eefc0

BUGCHECK_P4: 2

FILE_IN_CAB: 070923-6062-01.dmp

WRITE_ADDRESS: fffff8045fafb390: 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
 ffff8b8a449eefc0

MM_INTERNAL_CODE: 2

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: WmiPrvSE.exe

TRAP_FRAME: ffff8b8a449ee7f0 -- (.trap 0xffff8b8a449ee7f0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=005300410053004d rbx=0000000000000000 rcx=0053004100530040
rdx=005300410053003d rsi=0000000000000000 rdi=0000000000000000
rip=ffff8b8a449eefc0 rsp=ffff8b8a449ee988 rbp=0000000000000008
 r8=0000000000000053 r9=000000000000004f r10=0000000000000001
r11=000000000000000a r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na pe nc
ffff8b8a`449eefc0 42007800 add byte ptr [rax],dil ds:00530041`0053004d=??
Resetting default scope

STACK_TEXT:
ffff8b8a`449ee548 fffff804`5f24af53 : 00000000`00000050 ffff8b8a`449eefc0 00000000`00000011 ffff8b8a`449ee7f0 : nt!KeBugCheckEx
ffff8b8a`449ee550 fffff804`5f06e7b0 : ffffb686`bc0fc700 00000000`00000011 ffff8b8a`449ee870 00000000`00000000 : nt!MiSystemFault+0x1b2563
ffff8b8a`449ee650 fffff804`5f20bad8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MmAccessFault+0x400
ffff8b8a`449ee7f0 ffff8b8a`449eefc0 : ffffca80`8b5a3170 ffffb686`cb4e1d38 ffff8b8a`449eefc0 00000000`00000000 : nt!KiPageFault+0x358
ffff8b8a`449ee988 ffffca80`8b5a3170 : ffffb686`cb4e1d38 ffff8b8a`449eefc0 00000000`00000000 00000000`00000000 : 0xffff8b8a`449eefc0
ffff8b8a`449ee990 ffffb686`cb4e1d38 : ffff8b8a`449eefc0 00000000`00000000 00000000`00000000 00000000`00000000 : 0xffffca80`8b5a3170
ffff8b8a`449ee998 ffff8b8a`449eefc0 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffca80`85c00000 : 0xffffb686`cb4e1d38
ffff8b8a`449ee9a0 00000000`00000000 : 00000000`00000000 00000000`00000000 ffffca80`85c00000 10000000`00000001 : 0xffff8b8a`449eefc0

SYMBOL_NAME: nt!MiSystemFault+1b2563

MODULE_NAME: nt

IMAGE_VERSION: 10.0.19041.3155

STACK_COMMAND: .cxr; .ecxr ; kb

IMAGE_NAME: ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET: 1b2563

FAILURE_BUCKET_ID: AV_X_(null)_nt!MiSystemFault

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {49578414-34a9-c6dc-c795-b8c5552d5975}

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

Hocam belleklerde sıkıntı var MemTest86 ile belleklerinizi test edin. Sonuçları atarsanız sevinirim.
 
Son düzenleme:
Merhaba teşekkür ederim ilginize geçtiğimiz günlerde Memtest86 yaptım benim anladığım kadarıyla bir hata görünmüyordu fakat test sonuçlarının fotoğraflarını çektim bakıp sizde bir yorumlayabilir misiniz?

Memtest Sonuçları
 

Yeni konular

Geri
Yukarı