MEMORY_MANAGEMENT Hatası

Levoo

Megapat
Katılım
26 Haziran 2015
Mesajlar
726
Makaleler
2
Çözümler
1
Merhaba, son 40-50 günde ikinci defa başıma geldi. Öncesinde internette gezinirken olmuştu şimdi ise bu sabah PC açarken MEMORY_MANAGEMENT hatası verdi.

Öncesinde 1 saate kadar AIDA64 test yapmıştım sıkıntı yok.
RAM'lerden şüphelendim, Windows bellek tanılama yapmıştım geçenlerde sıkıntı yok.
Bugün Memtest86 ile test yaptım. Hiçbir sorun çıkmadı. Sizce sorun ne olabilir? Yazılımsal bir şey gibi duruyor. Başka konulara baktığımda genel olarak RAM sorunları çıkıyor fakat bende o da yok. Ekstra bilgi lazım olursa verebilirim.

-ASUS Maximus XI Hero.
- G.Skill Sniper X kamuflaj 3200MHz RAM.

Minidump: minidump dosyaları
 
Şöyle basit bir öneride bulunayım. Sanal bellek dosyanızı silin, sonra yenisini oluşturun. Hard disk varsa da disk hatalarına bir bakın. Sanal belleğin bulunduğu noktada disk problemi varsa ondan da yapıyor olabileceğini düşündüm.

Sistem dosyalarını da her ihtimale karşı kontrol ettirin.
 

Harddisk ve SSD var evet. Teşekkür ederim ona da bakacağım.
 
Öncelikle BIOS güncel değil güncelle.

ROG MAXIMUS XI HERO | ROG Maximus | Gaming Anakartlar｜ROG - Republic of Gamers｜ROG Türkiye

M.2 soğutma bloğu, Aura Sync RGB LED, DDR4 4400MHz, çift M.2, SATA 6Gb/s ve USB 3.1 Gen 2’ye sahip Intel Z390 ATX oyuncu anakartı
www.asus.com

Ayrıca Memtest86 ile yaptığın testin fotoğrafını atar mısın?

Kod: 
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000061941, The subtype of the bugcheck.
Arg2: 0000012f8c302022
Arg3: 000000000000000d
Arg4: ffff8a84cb147a00

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-JC78BRD

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  1a

BUGCHECK_P1: 61941

BUGCHECK_P2: 12f8c302022

BUGCHECK_P3: d

BUGCHECK_P4: ffff8a84cb147a00

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  svchost.exe

STACK_TEXT:
ffff8a84`cb147858 fffff800`1e64288c : 00000000`0000001a 00000000`00061941 0000012f`8c302022 00000000`0000000d : nt!KeBugCheckEx
ffff8a84`cb147860 fffff800`1e5d041e : ffffbf83`1e8b2080 00000000`00000000 ffff8a84`cb147a80 00000000`00000000 : nt!MmAccessFault+0x179a2c
ffff8a84`cb147a00 00007ffd`8b778d9d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
00000005`2a6ff4c0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`8b778d9d


MODULE_NAME: hardware

IMAGE_NAME:  hardware_ram

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  0x1a_61941_PAGE_TABLE_RESERVED_BITS_SET_IMAGE_hardware_ram

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
Kod: 
SYSTEM_SERVICE_EXCEPTION (3b)
An exception happened while executing a system service routine.
Arguments:
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff8018123b580, Address of the instruction which caused the bugcheck
Arg3: ffffe10971116b50, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-JC78BRD

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 38

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  3b

BUGCHECK_P1: c0000005

BUGCHECK_P2: fffff8018123b580

BUGCHECK_P3: ffffe10971116b50

BUGCHECK_P4: 0

CONTEXT:  ffffe10971116b50 -- (.cxr 0xffffe10971116b50)
rax=0000000000000004 rbx=ffff380de4ad83b0 rcx=0000000000000004
rdx=ffffb80de39bc6c0 rsi=0000000000000004 rdi=ffffb80de2b3a5f0
rip=fffff8018123b580 rsp=ffffe10971117540 rbp=0000000000000000
r8=ffffb80de268b8b0  r9=0000000000000004 r10=7ffffffffffffffc
r11=ffffe109711175b8 r12=ffffe109711176c0 r13=ffffe10971117698
r14=ffffb80de1103688 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050282
nt!CmpReportNotifyHelper+0xf0:
fffff801`8123b580 488b5320        mov     rdx,qword ptr [rbx+20h] ds:002b:ffff380d`e4ad83d0=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Registry

STACK_TEXT:
ffffe109`71117540 fffff801`8123b448 : ffffb80d`e2b3a5f0 00000000`00000004 ffffe109`711176c0 0000026e`00000001 : nt!CmpReportNotifyHelper+0xf0
ffffe109`711175c0 fffff801`8123ae09 : 00000000`ffffffff ffffe109`71117700 00000000`00000000 ffffb80d`e2b3a5f0 : nt!CmpReportNotifyForKcbStack+0x48
ffffe109`71117600 fffff801`8123a8b6 : 000000e0`00000001 ffffe109`711178a0 00000000`00000000 ffffb80d`f1798401 : nt!CmSetValueKey+0x3f9
ffffe109`711177a0 fffff801`80dd3c15 : 00000000`0000056c 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtSetValueKey+0x646
ffffe109`71117990 00007ffc`eda9cc64 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
000000e0`3e77ef78 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`eda9cc64


SYMBOL_NAME:  nt!CmpReportNotifyHelper+f0

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.836

STACK_COMMAND:  .cxr 0xffffe10971116b50 ; kb

BUCKET_ID_FUNC_OFFSET:  f0

FAILURE_BUCKET_ID:  0x3B_c0000005_nt!CmpReportNotifyHelper

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {4c488f7e-349e-437d-f688-7a5338bf648e}

Followup:     MachineOwner
---------
Kod: 
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: ffff8209dcee73e0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffff8209dcee7338, 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.Sec
    Value: 3

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-JC78BRD

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 5

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

    Key  : Analysis.System
    Value: CreateObject


ADDITIONAL_XML: 1

BUGCHECK_CODE:  139

BUGCHECK_P1: 3

BUGCHECK_P2: ffff8209dcee73e0

BUGCHECK_P3: ffff8209dcee7338

BUGCHECK_P4: 0

TRAP_FRAME:  ffff8209dcee73e0 -- (.trap 0xffff8209dcee73e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffff8d0cda7bd9c8 rbx=0000000000000000 rcx=0000000000000003
rdx=ffff8d0cda7bd910 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8027f7c12b4 rsp=ffff8209dcee7570 rbp=fffff8027f7f5310
r8=ffff8209dcee7578  r9=7fffa28beca27058 r10=fffff8027b111b50
r11=ffff8209dcee7540 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
Ntfs!NtfsCommonClose+0xb64:
fffff802`7f7c12b4 cd29            int     29h
Resetting default scope

EXCEPTION_RECORD:  ffff8209dcee7338 -- (.exr 0xffff8209dcee7338)
ExceptionAddress: fffff8027f7c12b4 (Ntfs!NtfsCommonClose+0x0000000000000b64)
   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:
ffff8209`dcee70b8 fffff802`7b1d41e9 : 00000000`00000139 00000000`00000003 ffff8209`dcee73e0 ffff8209`dcee7338 : nt!KeBugCheckEx
ffff8209`dcee70c0 fffff802`7b1d4610 : ffff8209`dcee7700 fffff802`7b6b10a2 ffffa28b`eca5e120 01000000`00100000 : nt!KiBugCheckDispatch+0x69
ffff8209`dcee7200 fffff802`7b1d29a3 : ffff8d0c`da363660 00000000`00000000 ffff8209`dcee77f0 ffff8209`dcee7501 : nt!KiFastFailDispatch+0xd0
ffff8209`dcee73e0 fffff802`7f7c12b4 : fffff802`7f7f5310 ffff8d0c`00000000 ffff8209`00000000 ffff8209`dcee77f0 : nt!KiRaiseSecurityCheckFailure+0x323
ffff8209`dcee7570 fffff802`7f7bfaf1 : ffff8209`dcee77f0 ffff8d0c`da7bd740 ffff8d0c`da7bd5e0 ffffa28b`bcecf180 : Ntfs!NtfsCommonClose+0xb64
ffff8209`dcee7650 fffff802`7f7f5398 : 00000000`0000001c fffff802`7b58f240 00000000`00000000 00000000`00000000 : Ntfs!NtfsFspCloseInternal+0x241
ffff8209`dcee77b0 fffff802`7b0f43b5 : ffffa28b`b7ead9a0 fffff802`7b468300 00000000`00000000 ffffa28b`c5c85040 : Ntfs!NtfsFspClose+0x88
ffff8209`dcee7a70 fffff802`7b06bcd5 : ffffa28b`c5c85040 00000000`00000080 ffffa28b`b7ea2280 ffffffff`fffefefe : nt!ExpWorkerThread+0x105
ffff8209`dcee7b10 fffff802`7b1c9998 : ffffde81`70979180 ffffa28b`c5c85040 fffff802`7b06bc80 14000000`14000000 : nt!PspSystemThreadStartup+0x55
ffff8209`dcee7b60 00000000`00000000 : ffff8209`dcee8000 ffff8209`dcee1000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!KiFastFailDispatch+d0

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.18362.836

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  d0

FAILURE_BUCKET_ID:  0x139_3_CORRUPT_LIST_ENTRY_nt!KiFastFailDispatch

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3aede96a-54dd-40d6-d4cb-2a161a843851}

Followup:     MachineOwner
---------
 
Son düzenleme:

Memtest'te hiç hata olmadığı için fotoğraf çekmemiştim fakat tekrar yapacağım o halde. BIOS'u da güncelleyip döneceğim size tamamdır.
 
Son düzenleme:
Dumplardan bakıldığına göre RAM'lerin ikisinden biri arızalı gibi memtest86 ile tek tek test yapman gerek.
 
[url=https://hizliresim.com/gpp7lM] [/URL]

[url=https://hizliresim.com/4aU4HO] [/URL]

[url=https://hizliresim.com/y5O3WC] [/URL]

[url=https://hizliresim.com/v2ZQBr] [/URL]
Baya uzun sürdü test. BIOS'u da güncelledim. Sitede 2020/05/07 tarihi var, msinfo32 kısmından BIOS tarihine bakınca 21.02.2020 gösteriyor ama doğru kurdum.
 
Uzun sürmesi normal. Driver Booster veya herhangi bir otomatik sürücü güncelleme/yükleme yazılımı kullandınız mı? Ayrıca CMD'yi yönetici olarak çalıştırıp aşağıdaki kodları tek tek çalıştırır mısınız?

Kod: 
sfc /scannow
DISM.exe /Online /Cleanup-image /Restorehealth
 
Hayır kullanmadım, hemen yapıyorum.
Dediklerinizi yaptım %100 oldu en son.
 
Son düzenleme:
İkisi de %100 olduysa kapatabilirsiniz. Sorun tekrar ederse mesaj yazın. Bu mesajıma da cevap vermeyin beğenmeniz yeterli, cevap verince sonra attığınız mesajın bildirimi düşmüyor.
 
Konuyu cevapla
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…