DH Anasayfa
İndirim Kodu
Ara
Popüler
Foruma Git
Hakkımızda
Destek
Mobil Sürüm
Standart Site Görünümü
Bu Konuda
  • Tüm Forumlar
  • Donanım / Hardware
  • Teknik Yardım
  • Bu Konuda
Arama butonu
Bağlan:
Facebook
Google+
Twitter
Aşağı Git Tüm Forumlar Donanım / Hardware Teknik Yardım Memory.DMP hatası nasıl çözülür?
Bu konudaki kullanıcılar: 1 misafir
3
Cevap 830
Tıklama 0
Öne Çıkarma
Memory.DMP hatası nasıl çözülür?
Cevap Yaz
Konuya Özel
S
suns3t
5 yıl (25 mesaj)
Onbaşı
Konu Sahibi

Daha önce sistemim bir kez Memory.DMP hatası vermişti, onun içeriğini kontrol edip not etmiştim. Şimdi ikinci kez verdi onun da içeriğine baktım. İkisinin 'de farklı sebeplerden kaynaklı gibi duruyor.

1. Memory.DMP dosya içeriği;

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Users\emana\OneDrive\Masaüstü\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff803`2f600000 PsLoadedModuleList = 0xfffff803`2fa48150
Debug session time: Wed Aug 12 02:24:33.380 2020 (UTC + 3:00)
System Uptime: 0 days 20:51:59.053
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................

Loading User Symbols
PEB address is NULL !
Loading unloaded module list

..................................................

For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff803`2f7c23c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffffa8c`5fc6e740=000000000000007e
7: kd> !analyze -v

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)

This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.

Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8032f745b44, The address that the exception occurred at
Arg3: fffffa8c5fc6f758, Exception Record Address
Arg4: fffffa8c5fc6efa0, Context Record Address

Debugging Details:

------------------

KEY_VALUES_STRING: 1
    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.mSec
    Value: 2687

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

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 6223

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

    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:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8032f745b44

BUGCHECK_P3: fffffa8c5fc6f758

BUGCHECK_P4: fffffa8c5fc6efa0

EXCEPTION_RECORD:  fffffa8c5fc6f758 -- (.exr 0xfffffa8c5fc6f758)

ExceptionAddress: fffff8032f745b44 (nt!RtlCompressBufferXpressLzStandard+0x0000000000000144)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000

NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff


CONTEXT:  fffffa8c5fc6efa0 -- (.cxr 0xfffffa8c5fc6efa0)
rax=00000000000008fc rbx=ffffaf04b24d59cc rcx=0000000000000073
rdx=ffffaf04b24c63c0 rsi=0000000000100000 rdi=000000000000047e
rip=fffff8032f745b44 rsp=fffffa8c5fc6f990 rbp=ffffaf04b42f5c20
r8=3abed0cbb24d4f4f  r9=ffffaf04b24d5f29 r10=ffffaf04b42f5c20
r11=ffffaf04b42f6000 r12=ffffaf04b24d5f29 r13=ffffaf04b42f5fd7
r14=ffffaf04b42f5c38 r15=ffffaf04b24c6028
iopl=0         nv up ei pl nz ac po nc

cs=0010  ss=0018  ds=002b  es=002b  fs=0053  gs=002b             efl=00050216

nt!RtlCompressBufferXpressLzStandard+0x144:
fffff803`2f745b44 413808          cmp     byte ptr [r8],cl ds:002b:3abed0cb`b24d4f4f=??
Resetting default scope



BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME:  MemCompression

READ_ADDRESS:  ffffffffffffffff

ERRR_CODE: (NTSTATUS) 0xc0000005 - 0x%p adresindeki y nerge 0x%p adresindeki belle e ba vurdu. Bellek  u olamaz %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

EXCEPTION_STR:  0xc0000005

STACK_TEXT:

fffffa8c`5fc6f990 fffff803`2f7459f1     : ffffaf04`b24d5f29 fffff803`2f6ecee9 ffffaf04`b42f5070 ffffaf04`b24d4f4f : nt!RtlCompressBufferXpressLzStandard+0x144
fffffa8c`5fc6fa40 fffff803`2f71667f     : fffff803`2fb8df10 fffff803`2fb8df20 00000000`00000000 ffffd269`349a4af0 : nt!RtlCompressBufferXpressLz+0x61
fffffa8c`5fc6faa0 fffff803`2f7495cd     : fffff803`2fb8deb0 ffffaf04`a46c20e0 ffffaf04`b37d1028 ffffaf04`b24d4f4f : nt!RtlCompressBuffer+0x6f
fffffa8c`5fc6fb00 fffff803`2f7493ed     : fffff803`2fb8deb0 fffff803`2fb8d9c0 ffffaf04`b42f5028 fffff803`2fb8de00 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmCompressCtxProcessEntry+0x91
fffffa8c`5fc6fb90 fffff803`2f71e155     : ffffffff`fd050f80 ffffaf04`ad1f2540 fffff803`2f749280 ffffffff`00000001 : nt!SMKM_STORE_MGR<SM_TRAITS>::SmCompressCtxWorkerThread+0x16d
fffffa8c`5fc6fc10 fffff803`2f7c99c8     : ffff8281`14679180 ffffaf04`ad1f2540 fffff803`2f71e100 fffffa8c`5fc6fcd0 : nt!PspSystemThreadStartup+0x55
fffffa8c`5fc6fc60 00000000`00000000     : fffffa8c`5fc70000 fffffa8c`5fc6a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  nt!RtlCompressBufferXpressLzStandard+144

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

STACK_COMMAND:  .cxr 0xfffffa8c5fc6efa0 ; kb

BUCKET_ID_FUNC_OFFSET:  144

FAILURE_BUCKET_ID:  AV_nt!RtlCompressBufferXpressLzStandard

OS_VERSION:  10.0.18362.1

BUILDLAB_STR:  19h1_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {ecd29322-2063-7ed6-1d71-1cd65a0a5eee}

Followup:     MachineOwner

---------


2. Memory.DMP dosya içeriği;

Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff805`5aa00000 PsLoadedModuleList = 0xfffff805`5ae480f0
Debug session time: Thu Aug 13 21:25:14.791 2020 (UTC + 3:00)
System Uptime: 0 days 1:02:02.462
Loading Kernel Symbols
...............................................................
................................................................
..............Page 24df0e not present in the dump file. Type ".hh dbgerr004" for details
..................................................
.....................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000010`f6fb6018). Type ".hh dbgerr001" for details
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`5abc23c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffff9b0f`a6725740=0000000000000192
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

KERNEL_AUTO_BOOST_LOCK_ACQUISITION_WITH_RAISED_IRQL (192)
A lock tracked by AutoBoost was acquired while executing at DISPATCH_LEVEL or
above.
Arguments:
Arg1: ffffc48a997b3080, The address of the thread.
Arg2: ffffc48a8b4f78c0, The lock address.
Arg3: 0000000000000000, The IRQL at which the lock was acquired.
Arg4: 0000000000000000, Reserved.

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

Page 24df0e not present in the dump file. Type ".hh dbgerr004" for details

KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 3265

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

Key : Analysis.DebugData
Value: CreateObject

Key : Analysis.DebugModel
Value: CreateObject

Key : Analysis.Elapsed.mSec
Value: 3359

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

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: 192

BUGCHECK_P1: ffffc48a997b3080

BUGCHECK_P2: ffffc48a8b4f78c0

BUGCHECK_P3: 0

BUGCHECK_P4: 0

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: ModernWarfare.exe

STACK_TEXT:
ffff9b0f`a6725738 fffff805`5aaa163d : 00000000`00000192 ffffc48a`997b3080 ffffc48a`8b4f78c0 00000000`00000000 : nt!KeBugCheckEx
ffff9b0f`a6725740 fffff805`5d6e4b95 : ffffc48a`8b4f78c0 ffffc48a`00000000 ffffc48a`8f53fb30 ffffc48a`99fb8c40 : nt!ExAcquireCacheAwarePushLockSharedEx+0x14d
ffff9b0f`a6725780 fffff805`5d6e2f5c : ffff9b0f`a6725920 ffff9b0f`a6725900 00000000`00000003 fffff805`5d6e6400 : FLTMGR!FltpPerformPreCallbacks+0x435
ffff9b0f`a6725890 fffff805`5d71c7c5 : ffff9b0f`a67259f8 ffff9b0f`a6725b80 ffffc48a`997b3080 ffffc48a`97d816c0 : FLTMGR!FltpPassThroughFastIo+0x8c
ffff9b0f`a67258f0 fffff805`5b00407f : ffffc48a`97d816c0 00000000`00000000 00000000`00000000 ffffc48a`00000000 : FLTMGR!FltpFastIoRead+0x165
ffff9b0f`a67259a0 fffff805`5abd3c18 : 00000000`00000000 00000000`00000000 00000000`00000000 00000010`f7dfd718 : nt!NtReadFile+0x39f
ffff9b0f`a6725a90 00007ff9`a62fc134 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000010`f7dfd658 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff9`a62fc134


SYMBOL_NAME: nt!ExAcquireCacheAwarePushLockSharedEx+14d

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 14d

FAILURE_BUCKET_ID: 0x192_nt!ExAcquireCacheAwarePushLockSharedEx

OS_VERSION: 10.0.18362.1

BUILDLAB_STR: 19h1_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {0b3e94d6-ae37-4afe-1a69-72779fd6e91e}

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


< Resime gitmek için tıklayın >

İlkini hatırlamıyorum ama, ikinci olan oyun içerisinde iken oldu şimdi. Diğeri de belki oyunda iken olmuş olabilir. Oyun: Call Of Duty: Warzone.
Memtest86 İle RAM'larımı test ettim bir sorun çıkmadı. Yardımlarınızı bekliyorum...

* Oyun daha önce DEV ERROR 6328 hatası ve çeşitli hatalar veriyordu, dün akşam bazı ayarlamalar yaptım oyun için internet'den araştırıp uyguladığım.

Sistem:
Windows 10 Home
R5 3600
RX 5700 XT Nitro+
Corsair Vengeance RGB Pro 16GB (2x8GB) 3200MHz

DH forumlarında vakit geçirmekten keyif alıyor gibisin ancak giriş yapmadığını görüyoruz.

Üye olduğunda özel mesaj gönderebilir, beğendiğin konuları favorilerine ekleyip takibe alabilir ve daha önce gezdiğin konulara hızlıca erişebilirsin.

Üye Ol Şimdi Değil
Bir Daha Gösterme





< Bu mesaj bu kişi tarafından değiştirildi suns3t -- 14 Ağustos 2020; 1:50:37 >

T
TheArchaeologist
5 yıl (2155 mesaj)
Binbaşı

Sürücülerinizi yeniden ve en güncel olanları ile güncelleyin, biosu default ayarlara getirin, kayıt defterini kontrol edin, dual channel ram mı kullanıyorsunuz?



< Bu ileti DH mobil uygulamasından atıldı >
S
suns3t
5 yıl (25 mesaj)
Onbaşı
Konu Sahibi

Sürücülerim güncel, bios'um default değil sadece işlemcimi 4.2 GHz hızında kullanıyorum RAM'a da 1.35V veriyorum. Evet Dual ch. Ram kullanıyorum.
Kayıt defterinde neyi kontrol etmeliyim?



S
suns3t
5 yıl (25 mesaj)
Onbaşı
Konu Sahibi

Güncel.



Cevap Yaz
Tüm Forumlar Donanım / Hardware Teknik Yardım Memory.DMP hatası nasıl çözülür?
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.
App Store'danİndirin Google Play'denİndirin
Gizle ve güncelleme çıkana kadar tekrar gösterme.
DonanımHaber Forum - Mini Sürüm

Hakkımızda | Yukarı

Tam sürüm için tıklayınız
Version: 1.2.885
Donanım Sponsoru: incehesap.com