Arama butonu
Bu konudaki kullanıcılar: 1 misafir, 1 mobil kullanıcı
3
Cevap
87
Tıklama
0
Öne Çıkarma
Mavi ekran MEMORY_MANAGEMENT hatası
C
4 ay
Er
Konu Sahibi

İyi forumlar, Sistemim sürekli ya mavi ekran yiyor ya kendini resetliyor. Mavi ekranda MEMORY_MANAGEMENT olarak hata veriyor.

Sorunun ramlerde olup olmadığını test etmek için,

MEMTEST86 ile test yaptım aşağıdaki gibi hata verdi.
< Resime gitmek için tıklayın >

Daha sonrasında ramleri soketlerinden çıkarıp tekrardan taktım bütün ramleri taradı success oldu herhangi bir sorun yok dedi. Sorunun çözüldüğünü düşündüm fakat yine 1 2 gün bilgisayarı kullandıktan sonra mavi ekran yemeye başladım.

BIOS'u update ettim, tekrardan ram testi yaptım ve yine FAIL verdi. Burada sorun ram kaynaklı mı yoksa sistemde uyuşmazlık mı var emin olamadım konuyla ilgili. Ürünlerin hepsi sıfır bu arada.

Son olarak win 11 temiz kurulum yaptım bilgisayar açık duruyordu herhangi bir kullanımım yoktu yine mavi ekran yemiş mindump dosyalarını eklemeye çalıştım fakat ekleyemedim buraya. Yardımcı olursanız sevinirim.

Sistem:
Intel Core i5-14400F 2.50GHz (Max. 4.70GHz) 10 Çekirdek 20MB L3 Önbellek Soket 1700 Tray İşlemci
GIGABYTE GeForce RTX 4060 Windforce OC 8GB GDDR6 128 Bit DLSS 3 Ekran Kartı
ASUS Prime H610M-E-CSM Intel H610 1700 Soket DDR5 5600Mhz mATX Anakart
Team T-Force Vulcan Black 32GB(2x16GB) 6000Mhz DDR5 CL38 Gaming Ram (FLBD532G6000HC38ADC01)
POWER BOOST 750W 80+ 120mm Fanlı PSU





< Bu mesaj bu kişi tarafından değiştirildi cagrivciko -- 31 Mart 2025; 12:41:17 >

E
4 ay
Binbaşı

biostan ram clok mhz düsürüp denesene





< Bu mesaj bu kişi tarafından değiştirildi ermanozgen -- 31 Mart 2025; 17:41:18 >
Bu mesaja 1 cevap geldi.
C
4 ay
Er
Konu Sahibi

Teşekkürler, XMP yi disable edip ram hızını 4800 mhzye çektim. Chipset driverını da tekrardan temiz bi şekilde kurdum. Bi test edeceğim bir süre kullanmam gerek sistem mavi ekran vermedi şimdilik.



< Bu ileti mobil sürüm kullanılarak atıldı >


Bu mesajda bahsedilenler: @ermanozgen
C
4 ay
Er
Konu Sahibi

Bu değişikliklerin ardından bilgisayarı boşta 2 3 saat açık bıraktım döndüğümde kendini resetlediğini gördüm. Minidump dosyasına baktığımda aşağıdaki gibi bir hata dönüyor.

SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the BugCheck
Arg2: fffff80094407c3b, Address of the instruction which caused the BugCheck
Arg3: ffffe580c3f208d0, Address of the context record for the exception that caused the BugCheck
Arg4: 0000000000000000, zero.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1296

Key : Analysis.Elapsed.mSec
Value: 1331

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27793.1000

Key : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2410.2.2

Key : Bugcheck.Code.LegacyAPI
Value: 0x3b

Key : Bugcheck.Code.TargetModel
Value: 0x3b

Key : Dump.Attributes.AsUlong
Value: 0x21808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0x0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: AV_nt!RtlRbRemoveNode

Key : Failure.Exception.IP.Address
Value: 0xfffff80094407c3b

Key : Failure.Exception.IP.Module
Value: nt

Key : Failure.Exception.IP.Offset
Value: 0x207c3b

Key : Failure.Hash
Value: {9b43c07a-2da2-b63c-46ab-1c788c8a28c1}

Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7417df84

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 55185662

Key : Hypervisor.Flags.ValueHex
Value: 0x34a10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 0x3f7

Key : Stack.Pointer
Value: PRCBException


BUGCHECK_CODE: 3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff80094407c3b

BUGCHECK_P3: ffffe580c3f208d0

BUGCHECK_P4: 0

FILE_IN_CAB: 033125-12687-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffaf0425d79080

CONTEXT: ffffe580c3f208d0 -- (.cxr 0xffffe580c3f208d0)
rax=0001000000000000 rbx=ffffaf042f35ae08 rcx=0000000000000000
rdx=ffffaf04335bfb88 rsi=0000000000000000 rdi=ffffaf0433e91b88
rip=fffff80094407c3b rsp=ffff9185124cf420 rbp=0000000000000008
r8=0000000000000000 r9=ffffaf0433e91b88 r10=ffffaf0433e91b88
r11=ffffaf0411106610 r12=0000000000000000 r13=0000000000000000
r14=0000000000000001 r15=00000000000000c8
iopl=0 nv up ei pl zr na po nc
cs=0010 ss=0018 ds=002b es=002b fs=0053 gs=002b efl=00050246
nt!RtlRbRemoveNode+0x66b:
fffff800`94407c3b f6401001 test byte ptr [rax+10h],1 ds:002b:00010000`00000010=??
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: asus_framework

STACK_TEXT:
ffff9185`124cf420 fffff800`945cc85d : 00000000`00000001 00000000`00000000 ffffaf04`111002c3 ffffaf04`111002c0 : nt!RtlRbRemoveNode+0x66b
ffff9185`124cf450 fffff800`947c5c85 : fffff800`00000000 ffffaf04`11106600 00000000`00000005 00000000`00000000 : nt!RtlpHpVsChunkSplit+0x4d
ffff9185`124cf4c0 fffff800`94636fca : ffffaf04`111002c0 00000000`00000000 00000000`00000000 00000000`00460000 : nt!RtlpHpVsSlotAllocate+0x20d
ffff9185`124cf520 fffff800`944f91c0 : ffff9185`00000046 00000000`00000440 00000000`00460000 fffff800`00000002 : nt!RtlpHpVsContextAllocate+0x11a
ffff9185`124cf5c0 fffff800`944f7aea : ffffaf04`11100000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!RtlpHpAllocateHeap+0x120
ffff9185`124cf650 fffff800`944f7572 : 00000000`00000000 fffff800`9443051e 00000000`6f436f49 00000000`00000000 : nt!ExAllocateHeapPool+0x50a
ffff9185`124cf780 fffff800`94d39189 : 00000000`00000040 ffff9185`124cfaa0 00000000`00000000 00000000`00002710 : nt!ExpAllocatePoolWithTagFromNode+0x52
ffff9185`124cf7c0 fffff800`94ab6cbf : ffffaf04`223d0cc0 00000000`000003d8 ffffaf04`223d0cc0 00000000`00000000 : nt!ExAllocatePool2+0x99
ffff9185`124cf870 fffff800`9488ee55 : ffffaf04`25d79080 00000000`1057f2b0 ffff9185`124cfaa0 00000000`0dd31000 : nt!NtRemoveIoCompletionEx+0x25f
ffff9185`124cf9b0 00007ffb`6947ef94 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000000`0dbfde28 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`6947ef94


SYMBOL_NAME: nt!RtlRbRemoveNode+66b

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.26100.3624

STACK_COMMAND: .cxr 0xffffe580c3f208d0 ; kb

BUCKET_ID_FUNC_OFFSET: 66b

FAILURE_BUCKET_ID: AV_nt!RtlRbRemoveNode

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {9b43c07a-2da2-b63c-46ab-1c788c8a28c1}

Followup: MachineOwner

Buna ek olarak ram çıkar tak yapıp memtest attım yine bir sorun çıkmadı. Sonrasında oyun girerek test ettim 1 2 saat oynadıktan sonra yine bir mavi ekranla kaşılaştım. Bunun hatası da aşağıdaki gib

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: ffffce8b542ef250, Address of the trap frame for the exception that caused the BugCheck
Arg3: ffffce8b542ef1a8, Address of the exception record for the exception that caused the BugCheck
Arg4: 0000000000000000, Reserved

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1265

Key : Analysis.Elapsed.mSec
Value: 8161

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

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

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

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

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

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

Key : Analysis.Version.DbgEng
Value: 10.0.27793.1000

Key : Analysis.Version.Description
Value: 10.2410.02.02 amd64fre

Key : Analysis.Version.Ext
Value: 1.2410.2.2

Key : Bugcheck.Code.LegacyAPI
Value: 0x139

Key : Bugcheck.Code.TargetModel
Value: 0x139

Key : Dump.Attributes.AsUlong
Value: 0x21808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0x0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : FailFast.Name
Value: CORRUPT_LIST_ENTRY

Key : FailFast.Type
Value: 3

Key : Failure.Bucket
Value: 0x139_3_CORRUPT_LIST_ENTRY_win32kfull!zzzUpdateCursorImage

Key : Failure.Exception.Code
Value: 0xffffffffc0000409

Key : Failure.Exception.Record
Value: 0xffffce8b542ef1a8

Key : Failure.Hash
Value: {dbd616d4-4c94-e7bb-71fb-0b6bfb177b47}

Key : Hypervisor.Enlightenments.ValueHex
Value: 0x7417df84

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 0

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 55185662

Key : Hypervisor.Flags.ValueHex
Value: 0x34a10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 0x3f7


BUGCHECK_CODE: 139

BUGCHECK_P1: 3

BUGCHECK_P2: ffffce8b542ef250

BUGCHECK_P3: ffffce8b542ef1a8

BUGCHECK_P4: 0

FILE_IN_CAB: 040125-12859-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffb78f8bb95080

TRAP_FRAME: ffffce8b542ef250 -- (.trap 0xffffce8b542ef250)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe609234f5240 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe6094c045a40 rsi=0000000000000000 rdi=0000000000000000
rip=fffff802907ec5bf rsp=ffffce8b542ef3e0 rbp=ffffce8b542ef900
r8=00000000e789002c r9=000000000000003f r10=ffffe6091e000140
r11=ffffce8b542ef580 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
win32kfull!zzzUpdateCursorImage+0x209f:
fffff802`907ec5bf cd29 int 29h
Resetting default scope

EXCEPTION_RECORD: ffffce8b542ef1a8 -- (.exr 0xffffce8b542ef1a8)
ExceptionAddress: fffff802907ec5bf (win32kfull!zzzUpdateCursorImage+0x000000000000209f)
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: explorer.exe

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:
ffffce8b`542eef28 fffff802`df48f7e9 : 00000000`00000139 00000000`00000003 ffffce8b`542ef250 ffffce8b`542ef1a8 : nt!KeBugCheckEx
ffffce8b`542eef30 fffff802`df48fdf2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffce8b`542ef070 fffff802`df48da28 : 00000000`0000000c 01000000`00100000 00000000`00000103 00000000`00000000 : nt!KiFastFailDispatch+0xb2
ffffce8b`542ef250 fffff802`907ec5bf : ffffe609`4c045900 00000000`00000000 00000000`00000020 00000000`05a00a00 : nt!KiRaiseSecurityCheckFailure+0x368
ffffce8b`542ef3e0 fffff802`907eab88 : 00000000`00000008 ffffe609`234f5010 ffffe609`234f5010 00000000`00000000 : win32kfull!zzzUpdateCursorImage+0x209f
ffffce8b`542ef5b0 fffff802`908219e5 : fffff802`90b22620 ffffce8b`542ef900 ffffe609`234f5010 ffffe609`234f5010 : win32kfull!zzzUpdateCursorImage+0x668
ffffce8b`542ef5e0 fffff802`908213a6 : ffffce8b`542ef900 fffff802`8f73cd5b ffffe609`00000000 00000000`00000000 : win32kfull!NtUserPeekMessage+0x855
ffffce8b`542ef870 fffff802`9082128d : 00000000`00000000 00000000`00d9f7b0 00000000`00000000 00000000`00601802 : win32kfull!NtUserPeekMessage+0x216
ffffce8b`542ef8b0 fffff802`70ba1077 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00d9f7b0 : win32kfull!NtUserPeekMessage+0xfd
ffffce8b`542ef960 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00d9f7b0 00000000`00000001 : win32k+0x1077


SYMBOL_NAME: win32kfull!zzzUpdateCursorImage+209f

MODULE_NAME: win32kfull

IMAGE_NAME: win32kfull.sys

IMAGE_VERSION: 10.0.26100.3624

STACK_COMMAND: .process /r /p 0xffffb78f8bb94080; .thread 0xffffb78f8bb95080 ; kb

BUCKET_ID_FUNC_OFFSET: 209f

FAILURE_BUCKET_ID: 0x139_3_CORRUPT_LIST_ENTRY_win32kfull!zzzUpdateCursorImage

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {dbd616d4-4c94-e7bb-71fb-0b6bfb177b47}

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




DH Mobil uygulaması ile devam edin. Mobil tarayıcınız ile mümkün olanların yanı sıra, birçok yeni ve faydalı özelliğe erişin. Gizle ve güncelleme çıkana kadar tekrar gösterme.