Memory.dmp Dosyası içinde ne barındırır?

F.A. Idoll · 14 Ekim 2020

Memory.dmp dosyası hepmizinde bilmiş olduğu gibi içerisinde sistem hatalarının alındığı anda ki Ram'de tutulan bir önbellektir. Peki ya bu önbelleğin içerisinde sadece sistem hatalarıyla ilgili yazılar mı vardır? yoksa güvenlik açığı olduğu söylentilerinde ki gibi kredi kartı veya sistemde ki uygulamalarda kullandığımız şifreleride barındırıyor mu?

38890 · 14 Ekim 2020

GeorgeFlips yazmış:
Memory.dmp dosyası hepmizinde bilmiş olduğu gibi içerisinde sistem hatalarının alındığı anda ki Ram'de tutulan bir önbellektir. Peki ya bu önbelleğin içerisinde sadece sistem hatalarıyla ilgili yazılar mı vardır? yoksa güvenlik açığı olduğu söylentilerinde ki gibi kredi kartı veya sistemde ki uygulamalarda kullandığımız şifreleride barındırıyor mu?

Merhaba GeorgeFlips,

Hayır, alakası yok. Memory DMP dosyasında hata dökümü barınır.

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

---------

İyi günler.

Kaan ÇABUK · 14 Ekim 2020

Treyarch yazmış:
Merhaba GeorgeFlips,

Hayır, alakası yok. Memory DMP dosyasında hata dökümü barınır.

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

---------

İyi günler.

MEMORY.DMP demiş.
Normal minidumpu değil.

38890 · 14 Ekim 2020

xKaanCKx yazmış:
MEMORY.DMP demiş.
Normal minidumpu değil.

Attığım şey bir memory DMP örneği zaten.

F.A. Idoll · 14 Ekim 2020

Treyarch yazmış:
Merhaba GeorgeFlips,

Hayır, alakası yok. Memory DMP dosyasında hata dökümü barınır.

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

---------

İyi günler.

Hacker'lerin "bu dosya üzerinden kredi kartı bilgileri alınabiliyor" yorumuna ne demeli?

Emirhandkee · 14 Ekim 2020

GeorgeFlips yazmış:
Memory.dmp dosyası hepmizinde bilmiş olduğu gibi içerisinde sistem hatalarının alındığı anda ki Ram'de tutulan bir önbellektir. Peki ya bu önbelleğin içerisinde sadece sistem hatalarıyla ilgili yazılar mı vardır? yoksa güvenlik açığı olduğu söylentilerinde ki gibi kredi kartı veya sistemde ki uygulamalarda kullandığımız şifreleride barındırıyor mu?

Hesaplamada, bir çekirdek dökümü, bellek dökümü, çökme dökümü, sistem dökümü veya ABEND dökümü, bir programın çalışma belleğinin belirli bir zamanda, genellikle programın çökmesi veya başka bir şekilde sonlandırılması durumunda kaydedilen durumundan oluşur.

F.A. Idoll · 14 Ekim 2020

Emirhandkee yazmış:
Hesaplamada, bir çekirdek dökümü, bellek dökümü, çökme dökümü, sistem dökümü veya ABEND dökümü, bir programın çalışma belleğinin belirli bir zamanda, genellikle programın çökmesi veya başka bir şekilde sonlandırılması durumunda kaydedilen durumundan oluşur.

Şifrelerimi barındırıyormu bu dosya?

38890 · 14 Ekim 2020

GeorgeFlips yazmış:
Hacker'lerin "bu dosya üzerinden kredi kartı bilgileri alınabiliyor" yorumuna ne demeli?

Bu yorumu Ekşi sözlük’de mi okudunuz?

Emirhandkee · 14 Ekim 2020

GeorgeFlips yazmış:
Şifrelerimi barındırıyormu bu dosya?

Hayır

Venom35 · 14 Ekim 2020

up.......

F.A. Idoll · 14 Ekim 2020

Treyarch yazmış:
Bu yorumu Ekşi sözlük’de mi okudunuz?

Tek ekşide görmemiştim başka yerlerdede ve yabancı forumlarda.

F.A. Idoll · 14 Ekim 2020

Güvenlik açığı konusu doğrumu sizce?

Ara

Ara

Memory.dmp Dosyası içinde ne barındırır?

F.A. Idoll

38890

Kaan ÇABUK

38890

F.A. Idoll

Emirhandkee

F.A. Idoll

38890

Emirhandkee

Venom35

F.A. Idoll

F.A. Idoll

SON KONULAR

En Son İçerikler

Çevrim içi üyeler

Forum istatistikleri