Çözüldü MEMORY_MANAGAMENT mavi ekran hatası

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

CordiSepS

Picopat
Katılım
20 Haziran 2020
Mesajlar
46
Çözümler
1
Arkadaşlar MEMORY_MANAGAMENT mavi ekran hatası alıyorum oyundayken oluyor. Windows bellek tanılama da problem gözükmüyor, nasıl atılcagını söylerseniz minidump dosyalarını atarım (acemiyim)

minidump

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
 
Son düzenleme:
Tarihe göre sırala Puana göre sırala

Hocam 5 saat sonra Memtest86 şu an tamamlandı ve hiçbir problem yok.

Yusuf koca dedi:
Zaten minidump dosyalarından bellekte sorun olduğunu görüyoruz yani baktık.
Genişletmek için tıkla...

Hocan problem yok derken RAM'lerde problem yok Sorun hala devam ediyor ve ben nedenini çözemedim başka neden kaynaklanıyor olabilir?

Arkadaşlar son 3 gündür bilgisayarımda mavi ekran hatası alıyorum.
MEMORY_MANAGAMENT hatası alıyorum, Memtest yaptım ve RAM'lerde hiçbir sorun görmedim. Sebebi ne olabilir? Yardımcı olursanız sevinirim

minidump

MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
 
Son düzenleyen: Moderatör:
Artı 0 Eksi
Testte sorun çıkmaması şu an bir önem arz etmiyor, belleklerde kesin arıza görünüyor. Bellekleri değiştirin, modelleri nedir?
 
Artı 0 Eksi
OK. Sabit diskinizde arıza olabilir. HD Tune ile Health sekmesinden bir ekran görüntüsü paylaşın.

HD Tune Pro

Sabit disk, harici disk, SSD ve flash diskler de dahil birçok diski test etmenize yarayan yazılım. Disklerinizin sağlık durumunu, yazma ve okuma değerlerini kontrol edebilirsiniz. Bu sürüm Pro versiyonu olup 15 günlük deneme süresi bulunmaktadır.
www.technopat.net

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: 0000000000028507
Arg3: 0000000065b7994c
Arg4: 00000000b346ea5d

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2796

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 19674

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1a

BUGCHECK_P1: 3f

BUGCHECK_P2: 28507

BUGCHECK_P3: 65b7994c

BUGCHECK_P4: b346ea5d

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.


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Blitz.exe

PAGE_HASH_ERRORS_DETECTED: 1

STACK_TEXT: 
fffffa05`5f892668 fffff800`76865c44     : 00000000`0000001a 00000000`0000003f 00000000`00028507 00000000`65b7994c : nt!KeBugCheckEx
fffffa05`5f892670 fffff800`76694402     : ffffa001`368cd080 ffffffff`ffffffff 00000000`00000000 ffffa001`368cd170 : nt!MiValidatePagefilePageHash+0x102c28
fffffa05`5f892750 fffff800`7669465d     : 00000000`00000002 fffffa05`00000000 fffffa05`5f892908 fffff800`00000000 : nt!MiWaitForInPageComplete+0x472
fffffa05`5f892860 fffff800`7665895b     : 00000000`c0033333 00000000`00000001 00000000`18111098 00000000`00000000 : nt!MiIssueHardFault+0x1ad
fffffa05`5f892960 fffff800`767d0a5e     : ffffa001`36ed0080 00000000`00000000 00000000`0ac4e000 ffffffff`f9bd5e90 : nt!MmAccessFault+0x40b
fffffa05`5f892b00 00000000`6a026db6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
00000000`0aeff484 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x6a026db6


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.

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: 0000000000039842
Arg3: 000000001519f77e
Arg4: 0000000044da7a0e

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

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 3796

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 12064

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1a

BUGCHECK_P1: 3f

BUGCHECK_P2: 39842

BUGCHECK_P3: 1519f77e

BUGCHECK_P4: 44da7a0e

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.


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  MemCompression

PAGE_HASH_ERRORS_DETECTED: 1

TRAP_FRAME:  ffff9681b6ffc050 -- (.trap 0xffff9681b6ffc050)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffff8002ff5e6c0 rbx=0000000000000000 rcx=ffff8100078fc000
rdx=ffff8100078fc000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8002ff5e710 rsp=ffff9681b6ffc1e8 rbp=ffff8100078fc000
 r8=000001e30535a340  r9=0000000000000643 r10=ffff8100078fcea0
r11=000001e30535a983 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!RtlDecompressBufferXpressLz+0x50:
fffff800`2ff5e710 418b08          mov     ecx,dword ptr [r8] ds:000001e3`0535a340=????????
Resetting default scope

STACK_TEXT: 
ffff9681`b6ffbbb8 fffff800`30065c44     : 00000000`0000001a 00000000`0000003f 00000000`00039842 00000000`1519f77e : nt!KeBugCheckEx
ffff9681`b6ffbbc0 fffff800`2fe94402     : ffff988f`b2f85d80 ffffffff`ffffffff 00000000`00000000 ffff988f`b2f85e70 : nt!MiValidatePagefilePageHash+0x102c28
ffff9681`b6ffbca0 fffff800`2fe9465d     : 00000000`00000002 ffff9681`00000000 ffff9681`b6ffbe58 fffff800`00000000 : nt!MiWaitForInPageComplete+0x472
ffff9681`b6ffbdb0 fffff800`2fe5895b     : 00000000`c0033333 00000000`00000000 000001e3`0535a340 ffff8100`07424ff0 : nt!MiIssueHardFault+0x1ad
ffff9681`b6ffbeb0 fffff800`2ffd0a5e     : 00000000`00000000 00000000`00000000 ffff9681`b6ffc478 00000000`00000000 : nt!MmAccessFault+0x40b
ffff9681`b6ffc050 fffff800`2ff5e710     : ffff8100`078fc000 ffff988f`b1b91050 fffff800`2fe05470 ffff8100`078fc000 : nt!KiPageFault+0x35e
ffff9681`b6ffc1e8 fffff800`2fe05470     : ffff8100`078fc000 ffff8100`078fc000 00000000`00000002 000001e3`0535a340 : nt!RtlDecompressBufferXpressLz+0x50
ffff9681`b6ffc200 fffff800`2ff60499     : 00000000`00000000 fffff800`00000001 00000000`00000000 ffff988f`b1b92788 : nt!RtlDecompressBufferEx+0x60
ffff9681`b6ffc250 fffff800`2ff60324     : 00000000`00000004 ffff9681`b6ffc460 00000000`00000000 00000000`000011d5 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+0x155
ffff9681`b6ffc330 fffff800`2ff601a2     : 00000000`00000001 00000000`0001a340 ffff988f`0001a340 ffff988f`00001000 : nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+0xa0
ffff9681`b6ffc380 fffff800`2ff5ffcb     : 00000000`ffffffff ffff988f`b2def000 ffff9681`b6ffc460 ffff988f`b56ee5d0 : nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+0x186
ffff9681`b6ffc420 fffff800`2ff5fe11     : ffff988f`b2def000 00000000`00000000 00000000`00000001 ffff988f`b1b92788 : nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+0xcb
ffff9681`b6ffc4d0 fffff800`2ff5fd21     : ffff988f`b1b91000 ffff988f`b56ee5d0 ffff988f`b2def000 ffff988f`b1b929b0 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+0x85
ffff9681`b6ffc550 fffff800`2fe4f698     : ffff988f`b318c080 ffff988f`b1b91000 00000000`00000000 00000000`00000000 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+0x21
ffff9681`b6ffc580 fffff800`2ff636b1     : fffff800`2ff5fd00 ffff9681`b6ffc630 00000000`00000003 00000000`00000000 : nt!KeExpandKernelStackAndCalloutInternal+0x78
ffff9681`b6ffc5f0 fffff800`2ff4cb71     : ffff9681`b6ffc6f0 fffff800`3038bb78 ffff988f`b1b91000 ffff9681`b6ffc840 : nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+0xcd
ffff9681`b6ffc6c0 fffff800`2ff4c757     : 00000000`0000000c ffff988f`b1b91000 ffff9681`b6ffc770 ffff988f`b56ee5d0 : nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+0x1a5
ffff9681`b6ffc710 fffff800`2ff62593     : 00000000`0000000c ffff988f`b56ee5d0 00000000`00000001 00000000`00000001 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxQueueWork+0xbf
ffff9681`b6ffc7a0 fffff800`2ff6409f     : ffff988f`00000001 ffff988f`b2f88650 00000000`00000000 ffff988f`b1b91000 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+0x167
ffff9681`b6ffc810 fffff800`2fe93e0f     : ffff988f`b1f48580 00000000`00000001 ffff988f`b1f48640 fffff800`2fe5a8a6 : nt!SmPageRead+0x33
ffff9681`b6ffc860 fffff800`2fe94939     : 00000000`00000002 ffff9681`b6ffc8f0 ffff9681`b6ffca58 ffffbbdd`c0839f38 : nt!MiIssueHardFaultIo+0x117
ffff9681`b6ffc8b0 fffff800`2fe5895b     : 00000000`c0033333 00000000`00000001 0000020e`7ce08e50 fffff800`2ffc9b05 : nt!MiIssueHardFault+0x489
ffff9681`b6ffc960 fffff800`2ffd0a5e     : ffff988f`b318c080 ffff988f`b351f080 00000000`00000001 ffffffff`94b62e00 : nt!MmAccessFault+0x40b
ffff9681`b6ffcb00 00007ff9`50555c61     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
00000084`2797f470 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`50555c61


CHKIMG_EXTENSION: !chkimg -lo 50 -d !nt
    fffff8002fe0548a-fffff8002fe0548f  6 bytes - nt!RtlDecompressBufferEx+7a
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe054de-fffff8002fe054e3  6 bytes - nt!RtlGetCompressionWorkSpaceSize+4e (+0x54)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe05526-fffff8002fe0552b  6 bytes - nt!SmAcquireReleaseCharges+42 (+0x48)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe055b2-fffff8002fe055b7  6 bytes - nt!MmChargeResources+86 (+0x8c)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe055f6-fffff8002fe055fb  6 bytes - nt!MmReleaseResourceCharge+3e (+0x44)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe4f6fa-fffff8002fe4f6ff  6 bytes - nt!KeExpandKernelStackAndCalloutInternal+da (+0x4a104)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe5a93a-fffff8002fe5a93f  6 bytes - nt!MiUnlockWorkingSetShared+fa (+0xb240)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe93e3a-fffff8002fe93e3f  6 bytes - nt!MiIssueHardFaultIo+142 (+0x39500)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe93e5a-fffff8002fe93e5f  6 bytes - nt!RtlLengthSid+1a (+0x20)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe93eba-fffff8002fe93ebf  6 bytes - nt!RtlGetAce+5a (+0x60)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe9440e-fffff8002fe94413  6 bytes - nt!MiWaitForInPageComplete+47e (+0x554)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe9445e-fffff8002fe94463  6 bytes - nt!MiUnlockFaultPageTable+4a (+0x50)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe944aa-fffff8002fe944af  6 bytes - nt!MiGetSessionIdForVa+46 (+0x4c)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002fe94a0a-fffff8002fe94a0f  6 bytes - nt!MiIssueHardFault+55a (+0x560)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002feaa51a-fffff8002feaa51f  6 bytes - nt!RtlpHpReleaseQueuedLockExclusive+28a (+0x15b10)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff2c42a-fffff8002ff2c42f  6 bytes - nt!IoPageReadEx+24a (+0x81f10)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff2c452-fffff8002ff2c457  6 bytes - nt!MmIsRecursiveIoFault+22 (+0x28)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff36c5a-fffff8002ff36c5f  6 bytes - nt!PopReleaseRwLock+2a (+0xa808)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff49e6e-fffff8002ff49e73  6 bytes - nt!SMKM_STORE_MGR<SM_TRAITS>::SmIoCtxWorkItemComplete+196 (+0x13214)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff4cc5e-fffff8002ff4cc63  6 bytes - nt!SMKM_STORE<SM_TRAITS>::SmStWorkItemQueue+292 (+0x2df0)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff5b23a-fffff8002ff5b23f  6 bytes - nt!MiStoreWriteModifiedCompleteApc+1a (+0xe5dc)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff5fd5a-fffff8002ff5fd5f  6 bytes - nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadCallout+5a (+0x4b20)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff5fd86-fffff8002ff5fd8b  6 bytes - nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadComplete+26 (+0x2c)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff5fea2-fffff8002ff5fea7  6 bytes - nt!SMKM_STORE<SM_TRAITS>::SmStDirectReadIssue+116 (+0x11c)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff5fefa-fffff8002ff5feff  6 bytes - nt!ST_STORE<SM_TRAITS>::StDmLazyWorkItemQueue+52 (+0x58)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff60016-fffff8002ff6001b  6 bytes - nt!ST_STORE<SM_TRAITS>::StDmPageRetrieve+116 (+0x11c)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff6023e-fffff8002ff60243  6 bytes - nt!ST_STORE<SM_TRAITS>::StDmpSinglePageRetrieve+222 (+0x228)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff6027e-fffff8002ff60283  6 bytes - nt!SmSetThreadSystemPagePriority+3a (+0x40)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff6033e-fffff8002ff60343  6 bytes - nt!ST_STORE<SM_TRAITS>::StDmSinglePageTransfer+ba (+0xc0)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff6052e-fffff8002ff60533  6 bytes - nt!ST_STORE<SM_TRAITS>::StDmSinglePageCopy+1ea (+0x1f0)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff62656-fffff8002ff6265b  6 bytes - nt!SMKM_STORE_MGR<SM_TRAITS>::SmPageRead+22a (+0x2128)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff6373a-fffff8002ff6373f  6 bytes - nt!SMKM_STORE<SM_TRAITS>::SmStDirectRead+156 (+0x10e4)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff637ae-fffff8002ff637b0  3 bytes - nt!ST_STORE<SM_TRAITS>::StDmCombineTargetCompare+6e (+0x74)
    [ cc cc cc:4c 87 00 ]
    fffff8002ff640aa-fffff8002ff640af  6 bytes - nt!SmPageRead+3e (+0x8fc)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff640fa-fffff8002ff640ff  6 bytes - nt!RtlpMakeXpressCallback+4a (+0x50)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff763ea-fffff8002ff763ef  6 bytes - nt!EmpCheckErrataList+a (+0x122f0)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ff76426-fffff8002ff7642b  6 bytes - nt!IoAllocateErrorLogEntry+36 (+0x3c)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff8002ffc296a-fffff8002ffc296b  2 bytes - nt!ZwLoadKey3+2a (+0x4c544)
    [ 84 00:4c 87 ]
    fffff8002ffc296d-fffff8002ffc296f  3 bytes - nt!ZwLoadKey3+2d (+0x03)
    [ 00 00 00:98 c3 90 ]
    fffff8002ffc298a-fffff8002ffc298b  2 bytes - nt!KiBugCheckReturn+16 (+0x1d)
    [ 84 00:4c 87 ]
    fffff8002ffc298d-fffff8002ffc298f  3 bytes - nt!KiBugCheckReturn+19 (+0x03)
    [ 00 00 00:98 c3 90 ]
    fffff8002ffc2aba-fffff8002ffc2abb  2 bytes - nt!KeBugCheckEx+12a (+0x12d)
    [ 84 00:4c 87 ]
    fffff8002ffc2abd-fffff8002ffc2abf  3 bytes - nt!KeBugCheckEx+12d (+0x03)
    [ 00 00 00:98 c3 90 ]
    fffff8002ffc2bba-fffff8002ffc2bbb  2 bytes - nt!KeContextToKframes+fa (+0xfd)
    [ 84 00:4c 87 ]
    fffff8002ffc2bbd-fffff8002ffc2bbf  3 bytes - nt!KeContextToKframes+fd (+0x03)
    [ 00 00 00:98 c3 90 ]
    fffff8002ffc2c0a-fffff8002ffc2c0b  2 bytes - nt!KiSaveInitialProcessorControlState+4a (+0x4d)
    [ 84 00:4c 87 ]
    fffff8002ffc2c0d-fffff8002ffc2c0f  3 bytes - nt!KiSaveInitialProcessorControlState+4d (+0x03)
    [ 00 00 00:98 c3 90 ]
    fffff8002ffc2cda-fffff8002ffc2cdf  6 bytes - nt!KiRestoreProcessorControlState+ca (+0xcd)
    [ 66 0f 1f 44 00 00:4c 87 00 98 c3 90 ]
    fffff8002ffc2e5a-fffff8002ffc2e5b  2 bytes - nt!KiSaveProcessorControlState+17a (+0x180)
    [ 84 00:4c 87 ]
    fffff8002ffc2e5d-fffff8002ffc2e5f  3 bytes - nt!KiSaveProcessorControlState+17d (+0x03)
    [ 00 00 00:98 c3 90 ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view  entire output.
    fffff800304afc66-fffff800304afc6b  6 bytes - nt!PopEtInternerLock+36
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff800304b6582-fffff800304b6587  6 bytes - nt!PopEtInternerEntryInitialize+82 (+0x691c)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff800304b901a-fffff800304b901f  6 bytes - nt!PopEtInternerUnlock+1a (+0x2a98)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff800304b9062-fffff800304b9067  6 bytes - nt!PsTerminateProcess+42 (+0x48)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff800304bceea-fffff800304bceef  6 bytes - nt!PopEtInternerFree+1a (+0x3e88)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff800304bcf12-fffff800304bcf17  6 bytes - nt!FsRtlNotifyUninitializeSync+22 (+0x28)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff800304bcf5a-fffff800304bcf5f  6 bytes - nt!HvUnlockHiveFilePages+42 (+0x48)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff800304bcf76-fffff800304bcf7b  6 bytes - nt!HvLockHiveWriter+16 (+0x1c)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff800304bd71a-fffff800304bd71f  6 bytes - nt!PopEtInternerAllocate+1a (+0x7a4)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff800304c0822-fffff800304c0827  6 bytes - nt!TlgEnableCallback+72 (+0x3108)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff800304c085a-fffff800304c085f  6 bytes - nt!MiDereferenceFailedControlArea+32 (+0x38)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff80030543a8a-fffff80030543a8f  6 bytes - nt!TraceLoggingRegisterEx+96 (+0x83230)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff80030543b0a-fffff80030543b0f  6 bytes - nt!IoWMIHandleToInstanceName+7a (+0x80)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff80030587e3a-fffff80030587e3f  6 bytes - nt!EtwpKernelProvEnableCallback+1a (+0x44330)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff80030587e76-fffff80030587e7b  6 bytes - nt!PopSetupHighPerfPowerRequest+36 (+0x3c)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
    fffff80030587eda-fffff80030587edf  6 bytes - nt!WheaCrashDumpInitializationComplete+5e (+0x64)
    [ cc cc cc cc cc cc:4c 87 00 98 c3 90 ]
393 errors : !nt (fffff8002fe0548a-fffff80030587edf)

MODULE_NAME: memory_corruption

IMAGE_NAME:  memory_corruption

MEMORY_CORRUPTOR:  LARGE

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_LARGE

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {e29154ac-69a4-0eb8-172a-a860f73c0a3c}

Followup:     memory_corruption
---------

 *** Memory manager detected 1 instance(s) of corrupted pagefilepage(s) while performing in-page operations.

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: 000000000003e184
Arg3: 000000006630f255
Arg4: 0000000039ac189f

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2577

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 3651

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: 19h1_release

    Key  : WER.OS.Timestamp
    Value: 2019-03-18T12:02:00Z

    Key  : WER.OS.Version
    Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1a

BUGCHECK_P1: 3f

BUGCHECK_P2: 3e184

BUGCHECK_P3: 6630f255

BUGCHECK_P4: 39ac189f

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.


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Blitz.exe

PAGE_HASH_ERRORS_DETECTED: 1

STACK_TEXT: 
fffff28f`def3a668 fffff803`57c65c44     : 00000000`0000001a 00000000`0000003f 00000000`0003e184 00000000`6630f255 : nt!KeBugCheckEx
fffff28f`def3a670 fffff803`57a94402     : ffffe10b`1b0cf420 ffffffff`ffffffff 00000000`00000000 ffffe10b`1b0cf510 : nt!MiValidatePagefilePageHash+0x102c28
fffff28f`def3a750 fffff803`57a9465d     : 00000000`00000002 fffff28f`00000000 fffff28f`def3a908 fffff803`00000000 : nt!MiWaitForInPageComplete+0x472
fffff28f`def3a860 fffff803`57a5895b     : 00000000`c0033333 00000000`00000001 00000000`0afc9ff8 00000000`00000000 : nt!MiIssueHardFault+0x1ad
fffff28f`def3a960 fffff803`57bd0a5e     : 00000000`74c2dd9c fffff28f`def3ab80 00000000`0abcdc30 00000000`0b2fe49c : nt!MmAccessFault+0x40b
fffff28f`def3ab00 00007ffa`d9e41249     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
00000000`0abcdb00 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`d9e41249


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.

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: 000000000001781a
Arg3: 0000000050fb42cd
Arg4: 0000000087ef34f0

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

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

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2468

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 10169

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

Key : Analysis.System
Value: CreateObject

Key : WER.OS.Branch
Value: 19h1_release

Key : WER.OS.Timestamp
Value: 2019-03-18T12:02:00Z

Key : WER.OS.Version
Value: 10.0.18362.1


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE: 1a

BUGCHECK_P1: 3f

BUGCHECK_P2: 1781a

BUGCHECK_P3: 50fb42cd

BUGCHECK_P4: 87ef34f0

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.


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: LeagueClientUx.exe

PAGE_HASH_ERRORS_DETECTED: 1

STACK_TEXT:
ffffe20a`ce230668 fffff800`1b265c44 : 00000000`0000001a 00000000`0000003f 00000000`0001781a 00000000`50fb42cd : nt!KeBugCheckEx
ffffe20a`ce230670 fffff800`1b094402 : ffffbb0a`6e61b330 ffffffff`ffffffff 00000000`00000000 ffffbb0a`6e61b420 : nt!MiValidatePagefilePageHash+0x102c28
ffffe20a`ce230750 fffff800`1b09465d : 00000000`00000002 ffffe20a`00000000 ffffe20a`ce230908 fffff800`00000000 : nt!MiWaitForInPageComplete+0x472
ffffe20a`ce230860 fffff800`1b05895b : 00000000`c0033333 00000000`00000001 00000000`03e1a3ac 00000000`00040000 : nt!MiIssueHardFault+0x1ad
ffffe20a`ce230960 fffff800`1b1d0a5e : 00000000`08149c74 ffffe20a`ce230b80 00000000`003dd000 ffffbb0a`6a9214c0 : nt!MmAccessFault+0x40b
ffffe20a`ce230b00 00000000`03e1a3ac : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiPageFault+0x35e
00000000`0a61e32c 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x3e1a3ac


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.
 
Son düzenleme:
Artı 0 Eksi
Benimde şuan kullandığım laptop çöküyor nadiren. Büyük ihtimalle 4+2 GB ve farklı marka olmasından dolayı. Aynı MHz ve CL olmasına rağmen uyumsuz oluyor. Hatta aynı sürüm olması bile önemli olduğunu söylemişti Recep bey bir videoda.
 
Artı 0 Eksi
 

Dosya Ekleri

  • 2020-10-14 (2).png
    660,6 KB · Görüntüleme: 45
Artı 0 Eksi
Error scan altından bir yüzey taraması yapar mısınız, Quick seçili olmasın. Bir de bellek testini Memtest86 ile mi yaptınız?

Kod: 
Machine ID Information [From Smbios 2.8, DMIVersion 0, Size=2219]
BiosMajorRelease = 4
BiosMinorRelease = 6
BiosVendor = American Megatrends Inc.
BiosVersion = V1.0
BiosReleaseDate = 08/30/2016
SystemManufacturer = MSI
SystemProductName = MS-7A83
SystemFamily = To be filled by O.E.M.
SystemVersion = 1.0
SystemSKU = To be filled by O.E.M.
BaseBoardManufacturer = MSI
BaseBoardProduct = A68HM GAMING (MS-7A83)
BaseBoardVersion = 1.0
 
Artı 0 Eksi
Mavi ekranın sebebi diskten dolayı gözüküyordu zaten. Error Scande yüzey sorunları çıkacaktır. HDD Regenerator ile onarmayi deneyebilirsiniz. Ya da komut sistemini yönetici olarak çalıştırıp şu komutu girin Chkdsk /f /r sonra çıkan soruya y yazıp yeniden başlatın sistemi. Dosya sistemindeki sorunları ve bozuk sektörlerdeki verileri kurtarıp kullanmayacaktır belki düzelecektir sorun.

HDD Regenerator

Hızlı sabit disk sorunları algılama. Bir sabit disk sürücüsü yüzeyinde fiziksel bozuk sektörleri tespit etme yeteneği. Histerezis döngüler jeneratör kullanarak bir sabit disk yüzeyinde kötü sektörleri (manyetik hatalar) onarmak için yeteneği.* *...
www.technopat.net
Bir tane dosyada sorun RAM'den kaynaklı gözüküyordu.
 
Artı 0 Eksi
Mesaj yazmak için giriş yapmalı ya da kaydolmalısınız.

Benzer konular

  • Soru
Mavi ekran hatası "memory_managament"
Mesaj
2
Görüntüleme
392
Sinha
  • Soru
MEMORY_MANAGAMENT mavi ekran hatası
Mesaj
7
Görüntüleme
544
byiyuel
  • Soru
MEMORY_MANAGAMENT mavi ekran hatası
2
Mesaj
15
Görüntüleme
990
283156
2
Y
  • Soru
"MEMORY_MANAGAMENT" mavi ekran hatası
Mesaj
2
Görüntüleme
440
Yasin A.
Y
  • Soru
Valorant oynarken MEMORY_MANAGAMENT mavi ekran hatası
Mesaj
1
Görüntüleme
317
Berrkay
Menü
Giriş yap
Kaydol
Bu siteyi kullanmak için çerezler gereklidir. Siteyi kullanmaya devam etmek için çerezleri kabul etmelisiniz. Daha Fazlasını Öğren.…