i3-12100F & RX6650 XT sistemde mavi ekran hatası

EgeN7 dedi:

23 Haziran'da aldığınız mavi ekran RAM'lerden birinde veya ikisinde de olan donanımsal bir arızadan dolayı kaynaklanıyor.

21 Haziran'da aldığınız ise kaynağı belli olmayan bir sürücü hatası. Ama böyle ne olduğu belli olmayan sürücü hatalarında problem genelde RAM oluyor.


Yine G. Skill Ripjaws V RAM'ler... Bu modelin bazı seri üretimlerinde problemler var.

XMP kapalı oynadığınızda bu hatayla karşılaşıyor musunuz?

RAM'e XMP dışında herhangi bir elle (manuel) OC yaptınız mı?
Yaptıysanız stabil olmayabilir. Bu işlemleri geri alın.

(voltaj, frekans, timing, CL değişimi vs.)


İlk etapta XMP profilini kapatın. Mavi ekran alırsanız tekrar paylaşın.


Yine RAM hatasıysa XMP açık şekilde Memtest86 ile test yapmanız gerekecek.
3-4 saat sürüyor.

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

* Memtest güncel sürüm:

https://www.memtest86.com/downloads/memtest86-usb.zip


Dökümler:

Kod:Panoya kopyala

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the BugCheck.
Arg2: ffffe5074c6015f8
Arg3: 0000000000000009
Arg4: ffffa88068a46fc0

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1327

    Key  : Analysis.Elapsed.mSec
    Value: 8279

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    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: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  1a

BUGCHECK_P1: 61941

BUGCHECK_P2: ffffe5074c6015f8

BUGCHECK_P3: 9

BUGCHECK_P4: ffffa88068a46fc0

FILE_IN_CAB:  062323-5390-01.dmp

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  cod.exe

STACK_TEXT:
ffffa880`68a46e18 fffff800`22a3f276     : 00000000`0000001a 00000000`00061941 ffffe507`4c6015f8 00000000`00000009 : nt!KeBugCheckEx
ffffa880`68a46e20 fffff800`22a0bad8     : 00000000`00000000 00000000`00000000 00000000`00000000 fffff800`22a0f7f5 : nt!MmAccessFault+0x1d0ec6
ffffa880`68a46fc0 fffff800`228179ce     : 00000000`00000010 00000000`00040082 ffffa880`68a47178 fffff800`22867cee : nt!KiPageFault+0x358
ffffa880`68a47150 fffff800`22fb70b9     : ffffe507`00000000 ffffe507`4777adb0 ffffa880`68a47520 01000000`00100000 : nt!ExFreeHeapPool+0x2ee
ffffa880`68a47230 fffff800`22c40a3d     : 00000000`00000078 ffffa880`68a472c0 ffffe507`4777adb0 00000000`00000000 : nt!ExFreePool+0x9
ffffa880`68a47260 fffff800`22c40818     : 00000000`00000040 ffffa880`68a47590 00000000`00000056 00000000`00000040 : nt!_CmOpenCommonClassRegKeyWorker+0x1c9
ffffa880`68a47300 fffff800`22ce97e2     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!_CmOpenCommonClassRegKey+0xf4
ffffa880`68a47410 fffff800`22ce9433     : ffffa880`68a47560 00000000`00000000 00000000`00000000 00000000`00000000 : nt!CmOpenInterfaceClassRegKey+0x3a
ffffa880`68a47460 fffff800`22ce8d55     : 00000000`00000001 ffffa880`68a47898 00000000`00000000 ffffa880`68a476a8 : nt!IopGetDeviceInterfaces+0x117
ffffa880`68a47630 fffff800`22c3cee5     : ac0b63db`c980d077 00000000`00120089 ffffac0b`41010340 00000000`00000000 : nt!PiCMGetDeviceInterfaceList+0x10d
ffffa880`68a47730 fffff800`22c3cd33     : ffffa880`68a47878 00000000`00000003 00000000`000001f8 fffff800`22c11bbe : nt!PiCMHandleIoctl+0x195
ffffa880`68a47770 fffff800`22cc2a5a     : 00000000`00000000 fffff800`22cc29f0 00000000`00000000 fffff800`2281eaba : nt!PiCMFastIoDeviceDispatch+0x53
ffffa880`68a477c0 fffff800`22c104d6     : 00000000`000001f8 00000000`00000000 00000000`00000000 ffffac0b`63dbc9b0 : nt!PiDaFastIoDispatch+0x6a
ffffa880`68a47820 fffff800`22c0fdb6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!IopXxxControlFile+0x706
ffffa880`68a47960 fffff800`22a0f7f5     : 0000007a`24ef38a8 ffffa880`68a47ac0 ffffac0b`5a2d9080 0000007a`24ef38a8 : nt!NtDeviceIoControlFile+0x56
ffffa880`68a479d0 00007ffe`5110d194     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
0000007a`24ef3458 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`5110d194


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.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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: 0000000000000000, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000008, value 0 = read operation, 1 = write operation
Arg4: 0000000000000000, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1280

    Key  : Analysis.Elapsed.mSec
    Value: 4441

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0xd1

    Key  : Failure.Bucket
    Value: AV_CODE_AV_NULL_IP_nt!KiPageFault

    Key  : Failure.Hash
    Value: {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  d1

BUGCHECK_P1: 0

BUGCHECK_P2: 2

BUGCHECK_P3: 8

BUGCHECK_P4: 0

FILE_IN_CAB:  062123-4328-01.dmp

READ_ADDRESS: fffff8027b2fb390: 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
 0000000000000000

PROCESS_NAME:  System

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

TRAP_FRAME:  fffff8027e074e70 -- (.trap 0xfffff8027e074e70)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=000000df8e977e80
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=0000000000000000 rsp=fffff8027e075008 rbp=0000000000000000
 r8=fffff80290f48806  r9=0000000876d8f740 r10=fffff8027a965540
r11=d6bf94d5e57a42bd r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz ac pe nc
00000000`00000000 ??              ???
Resetting default scope

IP_IN_FREE_BLOCK: 0

FAILED_INSTRUCTION_ADDRESS:
+0
STACK_TEXT:
fffff802`7e074d28 fffff802`7aa10029     : 00000000`0000000a 00000000`00000000 00000000`00000002 00000000`00000008 : nt!KeBugCheckEx
fffff802`7e074d30 fffff802`7aa0bbe3     : 00000000`00000000 00000000`00000001 00000000`00000006 00000000`00000000 : nt!KiBugCheckDispatch+0x69
fffff802`7e074e70 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000001 : nt!KiPageFault+0x463


SYMBOL_NAME:  nt!KiPageFault+463

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.3086

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  463

FAILURE_BUCKET_ID:  AV_CODE_AV_NULL_IP_nt!KiPageFault

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4ce35ff9-c5cf-d66d-0323-0f05e33f6692}

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

Genişletmek için tıkla...

EgeN7 dedi:

Bunun için iki aksiyon önerebilirim.

İlki, probleminizi RAM veya teknik destek kategorilerinden birine danışmak.
Orada arkadaşlar birkaç manuel ayar vererek XMP profili ile otomatik OC yapmak yerine manuel OC yaparak problemi çözebiliyorlar.

İkincisi ise, Memtest86 ile test yapmak ve eğer FAIL gelirse -ki yüksek ihtimalle gelecek- sonuçları alarak RAM'i aldığınız yere götürmek ve servise göndermelerini sağlamak. İnceleme sonucu iade/değişim çıkacaktır. Sonuçta XMP profili ile vadedilen değerlere çıkamıyorsunuz.

Genişletmek için tıkla...