Ryzen 5 2600 sistem XMP açınca mavi ekran veriyor

Gezgin618 · 30 Nisan 2023

GSKILL 2x8GB RipjawsV DDR4 3000MHz CL16 1.35V RAM'larım var. XMP'den profil1(2800mhz) ve profil2(2933mhz) yapınca mavi ekran hatası veriyor. 2133 mhz'de ise sorunsuz çalışıyor. Anakart tamir görmüştü. Tamir neden elektriksel bir sorundan dolayıydı. Tamirden sonra ramleri 2-4 slotlarında test edince sorun çıkmıştı. 1-3 slotarında memtest86 testi yaptım ve sorun çıkmadı. Aşağıda ise XMP açtıktan sonra (profil1 ve profil2'de) bilgisayar açıldıktan sonra 1-2 dakika içerisinde aldığım mavi ekran hatalarının minidumpları var.

Kod:

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\ossas\Desktop\043023-7078-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff800`5fa00000 PsLoadedModuleList = 0xfffff800`60613420
Debug session time: Sun Apr 30 15:39:56.224 2023 (UTC + 3:00)
System Uptime: 0 days 0:00:16.912
Loading Kernel Symbols
...............................................................
................................................................
......................................................
Loading User Symbols
Loading unloaded module list
.......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`5fe293a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc283`6d73fe60=000000000000007e
7: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M (1000007e)
This is a very common BugCheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003.  This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG.  This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG.  This will let us see why this breakpoint is
happening.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff80075d796ad, The address that the exception occurred at
Arg3: ffffc2836d740ec8, Exception Record Address
Arg4: ffffc2836d7406e0, Context Record Address

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


KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 3327

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 13512

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x1000007e

    Key  : Bugcheck.Code.Register
    Value: 0x7e

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Timestamp
    Value: 2022-05-06T12:50:00Z

    Key  : WER.OS.Version
    Value: 10.0.22621.1


FILE_IN_CAB:  043023-7078-01.dmp

BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff80075d796ad

BUGCHECK_P3: ffffc2836d740ec8

BUGCHECK_P4: ffffc2836d7406e0

EXCEPTION_RECORD:  ffffc2836d740ec8 -- (.exr 0xffffc2836d740ec8)
ExceptionAddress: fffff80075d796ad (vgk+0x00000000014796ad)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffc2836d7406e0 -- (.cxr 0xffffc2836d7406e0)
rax=ffbbdcf90782a9b0 rbx=000031040089c000 rcx=0000738448d9d630
rdx=001c695f76644157 rsi=0000000000000000 rdi=ffffcefbff763fff
rip=fffff80075d796ad rsp=ffffc2836d741108 rbp=00004ef8da523f3f
 r8=000007ff8b6fffff  r9=fffff80074a7229b r10=00003d7c928be90f
r11=0000000000000000 r12=93b7d49d44ce6d1b r13=ffffc57ce61be6cf
r14=ffffc2836d7416f0 r15=ffffffffff7efff7
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050286
vgk+0x14796ad:
fffff800`75d796ad 488b441001      mov     rax,qword ptr [rax+rdx+1] ds:002b:ffd84658`7de6eb08=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

READ_ADDRESS: fffff8006071c468: 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
 ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

EXCEPTION_STR:  0xc0000005

STACK_TEXT:
ffffc283`6d741108 fffff800`74a7229b     : 93b7d49d`44ce6d1b 00000000`00000000 ffffc283`6d741930 00000000`000002c0 : vgk+0x14796ad
ffffc283`6d741110 93b7d49d`44ce6d1b     : 00000000`00000000 ffffc283`6d741930 00000000`000002c0 00000000`00000000 : vgk+0x17229b
ffffc283`6d741118 00000000`00000000     : ffffc283`6d741930 00000000`000002c0 00000000`00000000 ffffc283`6d741666 : 0x93b7d49d`44ce6d1b


SYMBOL_NAME:  vgk+14796ad

MODULE_NAME: vgk

IMAGE_NAME:  vgk.sys

STACK_COMMAND:  .cxr 0xffffc2836d7406e0 ; kb

BUCKET_ID_FUNC_OFFSET:  14796ad

FAILURE_BUCKET_ID:  AV_vgk!unknown_function

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {56c5cf79-d160-8711-720f-03c630d4c72b}

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

Kod:

Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\ossas\Desktop\043023-11062-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 22621 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22621.1.amd64fre.ni_release.220506-1250
Machine Name:
Kernel base = 0xfffff801`80600000 PsLoadedModuleList = 0xfffff801`81213420
Debug session time: Sun Apr 30 15:58:04.680 2023 (UTC + 3:00)
System Uptime: 0 days 0:01:36.370
Loading Kernel Symbols
...............................................................
................................................................
.......................................................
Loading User Symbols
Loading unloaded module list
........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801`80a293a0 48894c2408      mov     qword ptr [rsp+8],rcx ss:ffffeb0e`d9721400=0000000000000139
4: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure.  The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffeb0ed9721720, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffffeb0ed9721678, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3343

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 29039

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 2

    Key  : Analysis.Init.CPU.mSec
    Value: 515

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x139

    Key  : Bugcheck.Code.Register
    Value: 0x139

    Key  : FailFast.Name
    Value: CORRUPT_LIST_ENTRY

    Key  : FailFast.Type
    Value: 3

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Timestamp
    Value: 2022-05-06T12:50:00Z

    Key  : WER.OS.Version
    Value: 10.0.22621.1


FILE_IN_CAB:  043023-11062-01.dmp

BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: ffffeb0ed9721720

BUGCHECK_P3: ffffeb0ed9721678

BUGCHECK_P4: 0

TRAP_FRAME:  ffffeb0ed9721720 -- (.trap 0xffffeb0ed9721720)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffa48dc84ee8f0 rbx=0000000000000000 rcx=0000000000000003
rdx=ffff910796465ea0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80184855008 rsp=ffffeb0ed97218b0 rbp=ffffeb0ed9721970
 r8=ffffa48e27aee400  r9=ffff910796465ea0 r10=0000000000008001
r11=ffffffffffffffff r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na po nc
tpm!Tpm20ResourceMgr::RemovedLoadedResource+0xc0:
fffff801`84855008 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffffeb0ed9721678 -- (.exr 0xffffeb0ed9721678)
ExceptionAddress: fffff80184855008 (tpm!Tpm20ResourceMgr::RemovedLoadedResource+0x00000000000000c0)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
Subcode: 0x3 FAST_FAIL_CORRUPT_LIST_ENTRY

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

ERROR_CODE: (NTSTATUS) 0xc0000409 - Sistem, bu uygulamada y   n tabanl  bir arabelle in ta t   n  alg lad . Bu ta ma, k t  niyetli bir kullan c n n bu uygulaman n denetimini ele ge irmesine olanak verebilir.

EXCEPTION_CODE_STR:  c0000409

EXCEPTION_PARAMETER1:  0000000000000003

EXCEPTION_STR:  0xc0000409

STACK_TEXT:
ffffeb0e`d97213f8 fffff801`80a3e9a9     : 00000000`00000139 00000000`00000003 ffffeb0e`d9721720 ffffeb0e`d9721678 : nt!KeBugCheckEx
ffffeb0e`d9721400 fffff801`80a3ef32     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffeb0e`d9721540 fffff801`80a3cd06     : 00000000`00000000 fffff801`848953d0 ffff9107`88b46080 fffff801`808511e3 : nt!KiFastFailDispatch+0xb2
ffffeb0e`d9721720 fffff801`84855008     : ffffa48d`b8bfd570 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0x346
ffffeb0e`d97218b0 fffff801`84862707     : 00000000`0000002c ffffa48d`b8bfd570 00000000`0000000e ffffa48e`29e30010 : tpm!Tpm20ResourceMgr::RemovedLoadedResource+0xc0
ffffeb0e`d97218f0 fffff801`84853497     : ffffa48d`b8bfd570 ffff9107`885fb610 00000000`00000000 00000000`0000002c : tpm!Tpm20ResourceMgr::SubmitRequest+0xef37
ffffeb0e`d97219b0 fffff801`8485315e     : ffff9107`00000003 00000000`00000000 ffffeb0e`d9721b50 00000000`00000050 : tpm!Tpm20Scheduler::DoUserRequest+0xb7
ffffeb0e`d9721a50 fffff801`8485165c     : ffff9107`885fb610 ffff9107`885fb610 fffff801`848515f0 ffff9107`885fb610 : tpm!Tpm20Scheduler::SchedulerThreadFunction+0x19e
ffffeb0e`d9721b90 fffff801`8080dc67     : ffff9107`00000003 fffff801`848515f0 ffff9107`885fb610 000f806f`b4bbbdff : tpm!Tpm20Scheduler::SchedulerThreadWrapper+0x6c
ffffeb0e`d9721bf0 fffff801`80a2e304     : fffff801`7daa0180 ffff9107`88b46080 fffff801`8080dc10 01d972bc`35ec61d6 : nt!PspSystemThreadStartup+0x57
ffffeb0e`d9721c40 00000000`00000000     : ffffeb0e`d9722000 ffffeb0e`d971c000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


SYMBOL_NAME:  tpm!Tpm20ResourceMgr::RemovedLoadedResource+c0

MODULE_NAME: tpm

IMAGE_NAME:  tpm.sys

IMAGE_VERSION:  10.0.22621.1626

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  c0

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_tpm!Tpm20ResourceMgr::RemovedLoadedResource

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1764a007-36a0-ad2e-affa-7bb93db2d908}

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

lazye · 30 Nisan 2023

Hocam spesifik bir şey söylediklerin şeyler sadece şunu diyebilirim. Windows 10 hata yaşamayabilirsin. "tpm.sys" bildiğin gibi Windows 11 ile birlikte geldi, sorunun kaynağı bu görünüyor lakin anakart bildiğin C4 olmuş dengesiz voltaj verirse ekran kartı işlemci RAM HDD ve SSD bir anda kullanılmaz hale gelebilir. Ayrıca minidump klasörünü paylaşın kendiniz analiz edip buraya atarsanız her şey görülemediği için sonuca ulaşmak daha da zorlaşır.

Gezgin618 · 1 Mayıs 2023

lazye dedi:
Hocam spesifik bir şey söylediklerin şeyler sadece şunu diyebilirim. Windows 10 hata yaşamayabilirsin. "tpm.sys" bildiğin gibi Windows 11 ile birlikte geldi, sorunun kaynağı bu görünüyor lakin anakart bildiğin C4 olmuş dengesiz voltaj verirse ekran kartı işlemci RAM HDD ve SSD bir anda kullanılmaz hale gelebilir. Ayrıca minidump klasörünü paylaşın kendiniz analiz edip buraya atarsanız her şey görülemediği için sonuca ulaşmak daha da zorlaşır.

Valla anakartı tamir eden kişi çok zor tamir ettiğini söyledi. Bir önceki konumda mevcut. İşlemciyi ryzen 5 5600'a yükseltmeyi düşünüyorum ama anakartın böyle sorunlar çıkartması geriyor. Aşağıdaki linklerde minidump dosyları mevcut.

https://www.mediafire.com/file/m5y2ij5o7osp2km/043023-11062-01.dmp/file

https://www.mediafire.com/file/exy68b32mlwpw7y/043023-7078-01.dmp/file

claus · 1 Mayıs 2023

Anakart tamiri randıman vermez. Yeni bir anakart al.

Gezgin618 · 4 Mayıs 2023

Anakart değişimine 2-3K vermek istemiyorum. Biraz araştırdığımda XMP ile sorunu olan bayağı bir kişinin olduğunu fark ettim. XMP'nin kendi profili yetersiz geliyor olabilir mi? Ramlari kendim overclock etsem sorunum çözülür mü?

claus · 4 Mayıs 2023

Deneyebilirsin.

Ryzen 5 2600 sistem XMP açınca mavi ekran veriyor

Ayrıntılı düzenleme

Gezgin618

Hectopat

lazye

Kilopat

Gezgin618

Hectopat

claus

Zettapat

Gezgin618

Hectopat

claus

Zettapat

Benzer konular

Yeni konular

Yeni mesajlar

Gizliliğinize önem veriyoruz