Çözüldü MEMORY_MANAGEMENT mavi ekran hatası

Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
İşletim sistemi
Windows 10

Yalcin663

Hectopat
Katılım
25 Ağustos 2019
Mesajlar
212
Merhaba, 1 ay dan beri her gün en az 5 kez bu MEMORY_MANAGEMENT mavi ekran hatasını alıyorum. Artık illallah ettirdi.
1-2 ay önce Memtest86 ile test etmeye başladım, 2 saatte en az 9.000 hata sayısına ulaşmıştı. Testi tam bitiremeden kapatmak zorunda kaldım.
Bellekleri değiştirmekten başka çarem kalmadı galiba.
Oyunlarda donmalar da hat safhada.

Screenshot_1.png


Güncel minidump dosyası:

OneDriveMinidump

Sistem:

• PSU: Versatile VR-PSU300W.
• Anakart: ECS G31T-M7 v1.0.
• Işlemci: Intel Core 2 Quad Q8300 2.5 GHz.
• Ekran kartı: Sapphire RX 550 Pulse 2 GB GDDR5 64 Bit.
• Bellek: 2x2 = 4 GB Kingston DDR2 800 MHz.
• SSD: SanDisk SSD Plus 120 GB.
 
Çözüm
Testte de görebileceğiniz üzere RAM'lerde hata var. İki RAM modülünü de teker teker teste sokun, sorunlu olanı sistemden çıkarın. Böylece mavi ekran sorunlarınız da çözülecektir.

Kod:
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041793, A page table page has been corrupted. Parameter 2 contains a pointer to
    the last processed PTE. Parameter 3 contains the number of non-zero PTEs found.
    Parameter 4 contains the expected number of non-zero PTEs in the page table.
Arg2: fffff000f860eff8
Arg3: 0000000000000200
Arg4: 00000000000001ff

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2780

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 16676

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: rs3_release

    Key  : WER.OS.Timestamp
    Value: 2017-09-28T15:34:00Z

    Key  : WER.OS.Version
    Value: 10.0.16299.15


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1a

BUGCHECK_P1: 41793

BUGCHECK_P2: fffff000f860eff8

BUGCHECK_P3: 200

BUGCHECK_P4: 1ff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  opera.exe

STACK_TEXT: 
fffff10b`0bbe9378 fffff800`a4fad7cb     : 00000000`0000001a 00000000`00041793 fffff000`f860eff8 00000000`00000200 : nt!KeBugCheckEx
fffff10b`0bbe9380 fffff800`a4e9d8d6     : 00000000`00000000 ffffc182`9adb2080 00000000`00000000 ffffc182`972965c0 : nt!MiDeleteVirtualAddresses+0x10ca5b
fffff10b`0bbe9670 fffff800`a531da5a     : ffffc182`9adb2080 ffffc182`9a79d4c0 ffffc182`9a79d4c0 ffffc182`9adb2080 : nt!MiDeleteVad+0x3b6
fffff10b`0bbe97c0 fffff800`a531d88e     : ffffffff`00000000 ffffc182`9bd4f100 ffffc182`9a79d4c0 ffffc182`9adb2080 : nt!MiCleanVad+0x3a
fffff10b`0bbe97f0 fffff800`a52dd079     : ffffffff`ffffffff ffffc182`972965c0 ffffc182`972968b8 ffffc182`00000000 : nt!MmCleanProcessAddressSpace+0x12e
fffff10b`0bbe9870 fffff800`a52bfda7     : ffffc182`972965c0 ffffb18a`f4dff060 fffff10b`0bbe9a88 00000000`00000000 : nt!PspRundownSingleProcess+0x129
fffff10b`0bbe98f0 fffff800`a52c0473     : 00000000`00000000 00000000`00000001 000000d3`6d376000 00000000`00000000 : nt!PspExitThread+0x583
fffff10b`0bbe99f0 fffff800`a4e8b4e7     : 00000000`00000000 00000000`00000000 ffffc182`00000000 fffff10b`0bbe9c00 : nt!KiSchedulerApcTerminate+0x33
fffff10b`0bbe9a30 fffff800`a4f6ff20     : 00000000`000007ec fffff10b`0bbe9ac0 00000000`00000000 fffff800`a4e44fe0 : nt!KiDeliverApc+0x337
fffff10b`0bbe9ac0 fffff800`a4f77cfa     : ffffc182`9adb2080 00000000`000080e8 fffff10b`0bbe9bd8 ffffc182`9a901e60 : nt!KiInitiateUserApc+0x70
fffff10b`0bbe9c00 00007ffa`a4d1fec4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
000000d3`6fdff428 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`a4d1fec4


SYMBOL_NAME:  nt!MiDeleteVirtualAddresses+10ca5b

MODULE_NAME: nt

IMAGE_VERSION:  10.0.16299.15

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  10ca5b

FAILURE_BUCKET_ID:  0x1a_41793_nt!MiDeleteVirtualAddresses

OS_VERSION:  10.0.16299.15

BUILDLAB_STR:  rs3_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0730eb34-d667-1bcc-76fe-94b17390a3ef}

Followup:     MachineOwner
---------
Testte de görebileceğiniz üzere RAM'lerde hata var. İki RAM modülünü de teker teker teste sokun, sorunlu olanı sistemden çıkarın. Böylece mavi ekran sorunlarınız da çözülecektir.

Kod:
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041793, A page table page has been corrupted. Parameter 2 contains a pointer to
    the last processed PTE. Parameter 3 contains the number of non-zero PTEs found.
    Parameter 4 contains the expected number of non-zero PTEs in the page table.
Arg2: fffff000f860eff8
Arg3: 0000000000000200
Arg4: 00000000000001ff

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2780

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on BORA

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 16676

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: rs3_release

    Key  : WER.OS.Timestamp
    Value: 2017-09-28T15:34:00Z

    Key  : WER.OS.Version
    Value: 10.0.16299.15


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1a

BUGCHECK_P1: 41793

BUGCHECK_P2: fffff000f860eff8

BUGCHECK_P3: 200

BUGCHECK_P4: 1ff

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXPNP: 1 (!blackboxpnp)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  opera.exe

STACK_TEXT: 
fffff10b`0bbe9378 fffff800`a4fad7cb     : 00000000`0000001a 00000000`00041793 fffff000`f860eff8 00000000`00000200 : nt!KeBugCheckEx
fffff10b`0bbe9380 fffff800`a4e9d8d6     : 00000000`00000000 ffffc182`9adb2080 00000000`00000000 ffffc182`972965c0 : nt!MiDeleteVirtualAddresses+0x10ca5b
fffff10b`0bbe9670 fffff800`a531da5a     : ffffc182`9adb2080 ffffc182`9a79d4c0 ffffc182`9a79d4c0 ffffc182`9adb2080 : nt!MiDeleteVad+0x3b6
fffff10b`0bbe97c0 fffff800`a531d88e     : ffffffff`00000000 ffffc182`9bd4f100 ffffc182`9a79d4c0 ffffc182`9adb2080 : nt!MiCleanVad+0x3a
fffff10b`0bbe97f0 fffff800`a52dd079     : ffffffff`ffffffff ffffc182`972965c0 ffffc182`972968b8 ffffc182`00000000 : nt!MmCleanProcessAddressSpace+0x12e
fffff10b`0bbe9870 fffff800`a52bfda7     : ffffc182`972965c0 ffffb18a`f4dff060 fffff10b`0bbe9a88 00000000`00000000 : nt!PspRundownSingleProcess+0x129
fffff10b`0bbe98f0 fffff800`a52c0473     : 00000000`00000000 00000000`00000001 000000d3`6d376000 00000000`00000000 : nt!PspExitThread+0x583
fffff10b`0bbe99f0 fffff800`a4e8b4e7     : 00000000`00000000 00000000`00000000 ffffc182`00000000 fffff10b`0bbe9c00 : nt!KiSchedulerApcTerminate+0x33
fffff10b`0bbe9a30 fffff800`a4f6ff20     : 00000000`000007ec fffff10b`0bbe9ac0 00000000`00000000 fffff800`a4e44fe0 : nt!KiDeliverApc+0x337
fffff10b`0bbe9ac0 fffff800`a4f77cfa     : ffffc182`9adb2080 00000000`000080e8 fffff10b`0bbe9bd8 ffffc182`9a901e60 : nt!KiInitiateUserApc+0x70
fffff10b`0bbe9c00 00007ffa`a4d1fec4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceExit+0x9f
000000d3`6fdff428 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`a4d1fec4


SYMBOL_NAME:  nt!MiDeleteVirtualAddresses+10ca5b

MODULE_NAME: nt

IMAGE_VERSION:  10.0.16299.15

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  10ca5b

FAILURE_BUCKET_ID:  0x1a_41793_nt!MiDeleteVirtualAddresses

OS_VERSION:  10.0.16299.15

BUILDLAB_STR:  rs3_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {0730eb34-d667-1bcc-76fe-94b17390a3ef}

Followup:     MachineOwner
---------
 
Çözüm
@Yuri09, bağdaştırılabilir. Her zaman olacak diyemeyiz ama genelde öyle oluyor.
 
Şu an alacağınız mavi ekranları pek umursamanıza gerek yok. Sorunun kaynağı belli. Yapmanız gereken tek şey hatalı RAM'leri sisteminizden çıkarmak.
 
Uyarı! Bu konu 5 yıl önce açıldı.
Muhtemelen daha fazla tartışma gerekli değildir ki bu durumda yeni bir konu başlatmayı öneririz. Eğer yine de cevabınızın gerekli olduğunu düşünüyorsanız buna rağmen cevap verebilirsiniz.

Bu konuyu görüntüleyen kullanıcılar

Technopat Haberler

Yeni konular

Geri
Yukarı