Çözüldü Memory Management Mavi Ekran Hatası

  • Konuyu başlatan Zel
  • Başlangıç Tarihi
  • Mesaj 8
  • Görüntüleme 974
Bu konu çözüldü olarak işaretlenmiştir. Çözülmediğini düşünüyorsanız konuyu rapor edebilirsiniz.
Çözüm
Çok yüksek ihtimalle bellek arızası. Test edin Memtest ile:


Kod:
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
    the pagefile offset. Parameter 3 contains the page CRC value.
    Parameter 4 contains the expected CRC value.
Arg2: 000000000000d317
Arg3: 000000000000d117
Arg4: 00000000e97751cd

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 34

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  1a

BUGCHECK_P1: 3f

BUGCHECK_P2: d317

BUGCHECK_P3: d117

BUGCHECK_P4: e97751cd

ADDITIONAL_DEBUG_TEXT:  Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  NVIDIA Web Helper.exe

PAGE_HASH_ERRORS_DETECTED: 1

STACK_TEXT: 
fffff588`61d9f568 fffff800`5d064004 : 00000000`0000001a 00000000`0000003f 00000000`0000d317 00000000`0000d117 : nt!KeBugCheckEx
fffff588`61d9f570 fffff800`5ce8df82 : ffffdb07`d11b49a0 ffffffff`ffffffff 00000000`00000000 ffffdb07`d11b4a90 : nt!MiValidatePagefilePageHash+0x101848
fffff588`61d9f650 fffff800`5ce8d4cd : 00000000`00000002 fffff588`00000000 fffff588`61d9f808 fffff800`00000000 : nt!MiWaitForInPageComplete+0x472
fffff588`61d9f760 fffff800`5ce72fab : 00000000`c0033333 00000000`00000001 00000000`02bbc0d4 fffff800`5cfc861f : nt!MiIssueHardFault+0x1ad
fffff588`61d9f860 fffff800`5cfcf520 : ffffdb07`d0f79080 ffffdb07`d0b03080 00000000`0262a000 00000000`00000001 : nt!MmAccessFault+0x40b
fffff588`61d9fa00 00000000`00d8d7fd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x360
00000000`0259e6f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xd8d7fd


SYMBOL_NAME:  PAGE_HASH_ERRORS_INPAGE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  PAGE_HASH_ERRORS_0x1a_3f

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6a2d4548-0eec-578d-e8f1-9e2239aa9a00}

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

 *** Memory manager detected 1 instance(s) of corrupted pagefilepage(s) while performing in-page operations.
Çok yüksek ihtimalle bellek arızası. Test edin Memtest ile:


Kod:
MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 000000000000003f, An inpage operation failed with a CRC error. Parameter 2 contains
    the pagefile offset. Parameter 3 contains the page CRC value.
    Parameter 4 contains the expected CRC value.
Arg2: 000000000000d317
Arg3: 000000000000d117
Arg4: 00000000e97751cd

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.Sec
    Value: 4

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 34

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

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  1a

BUGCHECK_P1: 3f

BUGCHECK_P2: d317

BUGCHECK_P3: d117

BUGCHECK_P4: e97751cd

ADDITIONAL_DEBUG_TEXT:  Memory Manager detected corruption of a pagefile page while performing an in-page operation.
The data read from storage does not match the original data written.
This indicates the data was corrupted by the storage stack, or device hardware.


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  NVIDIA Web Helper.exe

PAGE_HASH_ERRORS_DETECTED: 1

STACK_TEXT: 
fffff588`61d9f568 fffff800`5d064004 : 00000000`0000001a 00000000`0000003f 00000000`0000d317 00000000`0000d117 : nt!KeBugCheckEx
fffff588`61d9f570 fffff800`5ce8df82 : ffffdb07`d11b49a0 ffffffff`ffffffff 00000000`00000000 ffffdb07`d11b4a90 : nt!MiValidatePagefilePageHash+0x101848
fffff588`61d9f650 fffff800`5ce8d4cd : 00000000`00000002 fffff588`00000000 fffff588`61d9f808 fffff800`00000000 : nt!MiWaitForInPageComplete+0x472
fffff588`61d9f760 fffff800`5ce72fab : 00000000`c0033333 00000000`00000001 00000000`02bbc0d4 fffff800`5cfc861f : nt!MiIssueHardFault+0x1ad
fffff588`61d9f860 fffff800`5cfcf520 : ffffdb07`d0f79080 ffffdb07`d0b03080 00000000`0262a000 00000000`00000001 : nt!MmAccessFault+0x40b
fffff588`61d9fa00 00000000`00d8d7fd : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x360
00000000`0259e6f0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0xd8d7fd


SYMBOL_NAME:  PAGE_HASH_ERRORS_INPAGE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  PAGE_HASH_ERRORS_0x1a_3f

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6a2d4548-0eec-578d-e8f1-9e2239aa9a00}

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

 *** Memory manager detected 1 instance(s) of corrupted pagefilepage(s) while performing in-page operations.
 
Çözüm
Hocam cevabınız içi teşekkürler ama inceledim konuyu galiba memtesti Windows başlatırken açılışa onu koyacakmışız. Ben bir çok kez denediğimde Windows'u pert etmiştim. Başka bir yol yok mu?
 
Uyarı! Bu konu 7 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ı