Kernel data inpage error ve critical structure corruption hatası

Hasan68_42

Kilopat
Katılım
8 Temmuz 2019
Mesajlar
26
Merhaba, son 1 haftadır bilgisayarım da yavaşlamalar mavi ekran hatası alma, Google Chrome'de hay aksi hatası ve oynadığım oyunları indirememe ve WinRAR dosyalarını çıkaramamaya başladım.
Bu süreçte 6 kere format attım ama hiçbir faydası olmadı son çare olarak size yazıyorum. Minidump dosyalarını paylaşıyorum.


Sorun HDD'den olabilir diye düşündüğüm için Benchmark testi de yaptım.
 

Dosya Ekleri

  • Ekran Alıntısı.PNG
    Ekran Alıntısı.PNG
    20,6 KB · Görüntüleme: 74
Dosya herkese açık değil, dosyayı herkese açık olarak paylaşın.
Fakat ilk bakışta sabit disk sorunu gibi görünüyor. Çünkü hız birçok yerde 1-2 MBps'ye kadar düşmüş. Ortalama olarak da 30 MBps görünüyor. Fakat yine de Minidump dosyalarını herkese açık olarak paylaşmadığınız sürece kesin bir bilgi elde etmek zor. Ancak KERNEL_DATA_INPAGE_ERROR hatası bozuk sabit diskten kaynaklı oluyor diye biliyorum.
 
Dosya herkese açık değil, dosyayı herkese açık olarak paylaşın.
Fakat ilk bakışta sabit disk sorunu gibi görünüyor. Çünkü hız birçok yerde 1-2 MBps'ye kadar düşmüş. Ortalama olarak da 30 MBps görünüyor. Fakat yine de Minidump dosyalarını herkese açık olarak paylaşmadığınız sürece kesin bir bilgi elde etmek zor. Ancak KERNEL_DATA_INPAGE_ERROR hatası bozuk sabit diskten kaynaklı oluyor diye biliyorum.
Minidump.rar
buyrun.
 
Şimdi Minidump dosyalarını analiz ettim, sorun RAM kaynaklı gibi görünüyor. Zira birçok bellek kaynaklı hata var. Memtest86 ile RAM testi yapın ve sonuçları resim olarak paylaşın.
Ayrıca HD Tune programı ile Bad Sector taraması yapın (Error Scan ile, Quick Scan olmayacak) ve sonuçları resim olarak paylaşın. Bir de HD Tune Health sekmesinin resmini atın.

Kod:
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffe000f7ff1010, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff801cb8bf0d3, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2015

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on RED-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 46173

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  50

BUGCHECK_P1: ffffe000f7ff1010

BUGCHECK_P2: 0

BUGCHECK_P3: fffff801cb8bf0d3

BUGCHECK_P4: 2

READ_ADDRESS: fffff801cbaace60: Unable to get Flags value from nt!KdVersionBlock
fffff801cbaace60: Unable to get Flags value from nt!KdVersionBlock
fffff801cbaace60: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff801cbb69298
GetUlongPtrFromAddress: unable to read from fffff801cbb69520
fffff801cbaace60: Unable to get Flags value from nt!KdVersionBlock
 ffffe000f7ff1010 Nonpaged pool

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  IDMan.exe

TRAP_FRAME:  ffffd001bbb56f10 -- (.trap 0xffffd001bbb56f10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8003ccc870 rbx=0000000000000000 rcx=0000058000000000
rdx=fffff801cb806000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801cb8bf0d3 rsp=ffffd001bbb570a0 rbp=ffffc00079228c30
 r8=0000000000000000  r9=00000000050b6f3e r10=0000000000000002
r11=ffffb000762b3d72 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!MmCopyToCachedPage+0x183:
fffff801`cb8bf0d3 498b0424        mov     rax,qword ptr [r12] ds:00000000`00000000=????????????????
Resetting default scope

STACK_TEXT: 
ffffd001`bbb56ca8 fffff801`cb984d65     : 00000000`00000050 ffffe000`f7ff1010 00000000`00000000 ffffd001`bbb56f10 : nt!KeBugCheckEx
ffffd001`bbb56cb0 fffff801`cb85e2b9     : 00000000`00000000 ffffe000`eaf6e500 ffffd001`bbb56f10 ffffb000`7a640000 : nt! ?? ::FNODOBFM::`string'+0x1deb5
ffffd001`bbb56d50 fffff801`cb960c2f     : 00000000`00000000 00000000`00000001 00000000`00000000 00000022`cb87ae70 : nt!MmAccessFault+0x769
ffffd001`bbb56f10 fffff801`cb8bf0d3     : 0000000f`ffffffff 000026d6`447e1ab0 fffffa80`009af650 ffffe000`f2882880 : nt!KiPageFault+0x12f
ffffd001`bbb570a0 fffff801`cb8beb4f     : 00000000`00000000 00000000`03ff3d72 00000000`03ff3000 ffffd001`bbb5744c : nt!MmCopyToCachedPage+0x183
ffffd001`bbb57410 fffff801`cb8f1120     : ffffe000`ea411d60 00000000`050b6f3e ffffd001`bbb57568 ffffe000`00000000 : nt!CcMapAndCopyInToCache+0x21f
ffffd001`bbb57500 fffff801`96141d7c     : 00000000`03ff42eb ffffe000`e8bfcdf0 ffffe000`eae4f8a0 ffffe000`e8bfcdf0 : nt!CcCopyWriteEx+0x260
ffffd001`bbb575a0 fffff801`95fa3061     : 00000000`000002b0 fffff801`cbbf3f95 ffff4ece`90018191 00000000`00000579 : Ntfs!NtfsCopyWriteA+0x2ed
ffffd001`bbb57820 fffff801`95fa37d6     : ffffd001`bbb57910 ffffe000`eae4f800 ffffe000`e8532cf0 ffffe000`e8532c00 : fltmgr!FltpPerformFastIoCall+0x1c1
ffffd001`bbb57880 fffff801`95fc9a4f     : 00000000`00000010 fffff801`cbc13544 ffffe000`00000010 ffffd001`bbb579e0 : fltmgr!FltpPassThroughFastIo+0x165
ffffd001`bbb578e0 fffff801`cbc13064     : ffffe000`eae4f8a0 00000000`00000000 ffffd001`bbb579d8 ffffd001`bbb57a40 : fltmgr!FltpFastIoWrite+0x14f
ffffd001`bbb57990 fffff801`cb9621b3     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x410
ffffd001`bbb57a90 00000000`773a2352     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`05c5ed88 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773a2352


SYMBOL_NAME:  nt!MmCopyToCachedPage+183

MODULE_NAME: nt

IMAGE_VERSION:  6.3.9600.17415

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  183

FAILURE_BUCKET_ID:  AV_nt!MmCopyToCachedPage

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {38463293-a177-b1cf-c39d-543c8a6c902d}

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffc00021d20899, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803f0ddf9fb, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1546

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on RED-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 11646

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  a

BUGCHECK_P1: ffffc00021d20899

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff803f0ddf9fb

READ_ADDRESS: fffff803f0f30e60: Unable to get Flags value from nt!KdVersionBlock
fffff803f0f30e60: Unable to get Flags value from nt!KdVersionBlock
fffff803f0f30e60: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff803f0fed298
GetUlongPtrFromAddress: unable to read from fffff803f0fed520
fffff803f0f30e60: Unable to get Flags value from nt!KdVersionBlock
 ffffc00021d20899 Paged pool

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  ffffd00021d206e0 -- (.trap 0xffffd00021d206e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd00021d20830
rdx=0000000000007ff6 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803f0ddf9fb rsp=ffffd00021d20870 rbp=ffffc00021d208f0
 r8=0000000000000000  r9=00000000000000a8 r10=fffff803f0c8a000
r11=fffff78000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na pe nc
nt!KiDpcInterrupt+0xcb:
fffff803`f0ddf9fb 0fb64da9        movzx   ecx,byte ptr [rbp-57h] ss:0018:ffffc000`21d20899=??
Resetting default scope

STACK_TEXT: 
ffffd000`21d20598 fffff803`f0de64e9     : 00000000`0000000a ffffc000`21d20899 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`21d205a0 fffff803`f0de4d3a     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe001`ae558940 : nt!KiBugCheckDispatch+0x69
ffffd000`21d206e0 fffff803`f0ddf9fb     : 00000000`00000000 ffffd000`677310e0 ffffe001`ab2a6960 00000000`00000000 : nt!KiPageFault+0x23a
ffffd000`21d20870 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0xcb


SYMBOL_NAME:  nt!KiDpcInterrupt+cb

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  6.3.9600.17415

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  cb

FAILURE_BUCKET_ID:  AV_nt!KiDpcInterrupt

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {c1149c79-430d-0297-4e4e-d298390f725f}

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffc0002456f720, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80199a3692b, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1952

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on RED-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 13962

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  a

BUGCHECK_P1: ffffc0002456f720

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80199a3692b

READ_ADDRESS: fffff80199ca6e60: Unable to get Flags value from nt!KdVersionBlock
fffff80199ca6e60: Unable to get Flags value from nt!KdVersionBlock
fffff80199ca6e60: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff80199d63298
GetUlongPtrFromAddress: unable to read from fffff80199d63520
fffff80199ca6e60: Unable to get Flags value from nt!KdVersionBlock
 ffffc0002456f720 Paged pool

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffd0002456ef80 -- (.trap 0xffffd0002456ef80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd0002456f720 rbx=0000000000000000 rcx=ffffc0002456f720
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80199a3692b rsp=ffffd0002456f110 rbp=0000000000000000
 r8=0000000000000000  r9=0000000000000000 r10=ffffc0002456f720
r11=ffffd0002456f338 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!KeSetEvent+0x3fb:
fffff801`99a3692b 488b09          mov     rcx,qword ptr [rcx] ds:ffffc000`2456f720=????????????????
Resetting default scope

STACK_TEXT: 
ffffd000`2456ee38 fffff801`99b5c4e9     : 00000000`0000000a ffffc000`2456f720 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`2456ee40 fffff801`99b5ad3a     : 00000000`00000000 ffffd000`2456f718 ffffd000`2456f000 fffff800`f227fcf2 : nt!KiBugCheckDispatch+0x69
ffffd000`2456ef80 fffff801`99a3692b     : ffffe001`160b8770 fffff800`f28e6f29 ffffe001`18f5f940 ffffe001`160b88c0 : nt!KiPageFault+0x23a
ffffd000`2456f110 fffff800`f24a838a     : ffffc000`2456f720 ffffe001`00000000 00000000`00000000 ffffe001`00000000 : nt!KeSetEvent+0x3fb
ffffd000`2456f1d0 fffff801`99a38bea     : 00000001`00000001 ffffe001`18f5f940 ffffd000`2456f300 00000000`00000000 : Ntfs!NtfsFlushDiskCacheCompletionRoutine+0x12
ffffd000`2456f200 fffff800`f2203f53     : ffffe001`161b6800 ffffbfbd`9f86ca00 ffffe001`15186800 fffff801`99cb2300 : nt!IopfCompleteRequest+0x2ea
ffffd000`2456f340 fffff800`f221738e     : ffff80c2`7ac02b56 00000000`00000000 00000000`00000000 00000000`00000000 : storport!RaidCompleteRequestEx+0x53
ffffd000`2456f410 fffff800`f2202415     : fffff800`f28d1010 00000000`00000000 00000000`00000000 00000000`00000001 : storport!RaUnitScsiIrp+0x15bae
ffffd000`2456f560 fffff800`f28c9458     : ffffe001`160b8ea8 ffffe001`160b8770 ffffe001`160b8e78 00000000`00000000 : storport!RaDriverScsiIrp+0x55
ffffd000`2456f5a0 fffff800`f28c91ad     : ffffe001`160b8d80 ffffe001`160b8770 ffffe001`160b8f60 00000000`00000009 : disk!DiskFlushDispatch+0x128
ffffd000`2456f600 fffff800`f28e6d8d     : 00000000`00000006 ffffc000`78a4bfc0 ffffe001`18f5f940 ffffe001`18f5f940 : disk!DiskShutdownFlush+0xcd
ffffd000`2456f670 fffff800`f23453c8     : ffffe001`161cca30 ffffd000`2456f6f8 ffffe001`161cca30 00000000`00000000 : CLASSPNP!ClassShutdownFlush+0x39
ffffd000`2456f6a0 fffff800`f24a831d     : ffffd000`2456fa61 ffffc000`78a4bfc0 ffffe001`18f5f940 ffffe001`1574a6f0 : volmgr!VmFlushBuffers+0x138
ffffd000`2456f6e0 fffff800`f24a6778     : ffffe001`18f5f940 00000000`1968d73b 00000000`00000000 ffffc000`78a4bf00 : Ntfs!NtfsFlushDiskCache+0xad
ffffd000`2456f740 fffff800`f254541f     : ffffc000`78a4bfc0 00000000`196b3356 ffffd000`2456fa01 00000000`00000000 : Ntfs!LfsFlushDiskCache+0x120
ffffd000`2456f820 fffff801`99aee4ac     : ffffc000`78a4bfc0 00000000`196b3356 7fffffff`ffffffff 7fffffff`ffffffff : Ntfs!LfsFlushToLsn+0x10b
ffffd000`2456f880 fffff801`99a4fbf3     : ffffe001`16817bb0 00000000`00000000 00000000`00000000 ffffd000`2456faf8 : nt!CcAcquireByteRangeForWrite+0x850
ffffd000`2456f9b0 fffff801`99a5042b     : ffffe001`15693b70 00000000`00000000 ffffe001`00000001 ffffd000`2456faf8 : nt!CcFlushCachePriv+0x37b
ffffd000`2456fac0 fffff801`99a9c38c     : ffffe001`168a4c40 ffffe001`15186801 ffffe001`00000000 00000000`000441e4 : nt!CcWriteBehindInternal+0x17b
ffffd000`2456fb50 fffff801`99b01c70     : 00000000`00000000 ffffe001`15186700 00000000`00000080 ffffe001`15186700 : nt!ExpWorkerThread+0x28c
ffffd000`2456fc00 fffff801`99b56fc6     : ffffd001`a8940180 ffffe001`15186700 ffffe001`181c8880 fffff960`000fe544 : nt!PspSystemThreadStartup+0x58
ffffd000`2456fc60 00000000`00000000     : ffffd000`24570000 ffffd000`2456a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_NAME:  disk!DiskFlushDispatch+128

MODULE_NAME: disk

IMAGE_NAME:  disk.sys

IMAGE_VERSION:  6.3.9600.16384

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  128

FAILURE_BUCKET_ID:  AV_disk!DiskFlushDispatch

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {3fe0836c-c708-98ef-41cf-eeab3ff35f71}

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 00001af21c864000
Arg3: 0000000000003e90
Arg4: fffff58010804000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1858

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on RED-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 21149

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1a

BUGCHECK_P1: 41284

BUGCHECK_P2: 1af21c864000

BUGCHECK_P3: 3e90

BUGCHECK_P4: fffff58010804000

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

STACK_TEXT: 
ffffd000`252675b8 fffff802`039f443d     : 00000000`0000001a 00000000`00041284 00001af2`1c864000 00000000`00003e90 : nt!KeBugCheckEx
ffffd000`252675c0 fffff802`038dc728     : e9000001`c17a7867 ffffd000`25267710 fffff68d`790e4320 fffff580`10804000 : nt! ?? ::FNODOBFM::`string'+0x1658d
ffffd000`25267610 fffff802`0394075a     : ffffe001`f46c0340 00000000`00000001 00000000`00000000 ffffe001`00000005 : nt!MiDeleteVirtualAddresses+0x558
ffffd000`252678a0 fffff802`0393f5e9     : ffffe001`f0fa9870 00000000`00000010 ffffe001`00000000 00000000`00000000 : nt!MiDeleteVad+0xbca
ffffd000`252679a0 fffff802`039d91b3     : 00000000`00000001 00000000`00502cf8 00000000`00000001 ffffe001`f4457df0 : nt!NtFreeVirtualMemory+0x879
ffffd000`25267b00 00007ffe`a3e50e2a     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000009a`7b00e6b8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`a3e50e2a


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+1658d

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  6.3.9600.17415

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1658d

FAILURE_BUCKET_ID:  0x1a_41284_nt!_??_::FNODOBFM::_string_

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {c39d115f-eaa3-aeb6-09bd-1a63e83e1077}

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
 or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
 debugger that was not attached when the system was booted. Normal breakpoints,
 "bp", can only be set if the debugger is attached at boot time. Hardware
 breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a01f5928ed053b, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 52f8bcb1b86866dc, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    2a  : Type 4 pool corruption
    2b  : Modification of a function or .pdata
    2c  : Image integrity corruption
    2d  : Processor misconfiguration
    2e  : Type 5 process list corruption
    2f  : Process shadow corruption
    30  : Retpoline code page corruption
    101 : General pool corruption
    102 : Modification of win32k.sys

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2280

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on RED-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 8772

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  109

BUGCHECK_P1: a3a01f5928ed053b

BUGCHECK_P2: 0

BUGCHECK_P3: 52f8bcb1b86866dc

BUGCHECK_P4: 101

MEMORY_CORRUPTOR:  ONE_BIT

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffd001`165c6088 00000000`00000000     : 00000000`00000109 a3a01f59`28ed053b 00000000`00000000 52f8bcb1`b86866dc : nt!KeBugCheckEx


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}

Followup:     MachineOwner
---------
 
Şimdi Minidump dosyalarını analiz ettim, sorun RAM kaynaklı gibi görünüyor. Zira birçok bellek kaynaklı hata var. Memtest86 ile RAM testi yapın ve sonuçları resim olarak paylaşın.
Ayrıca HD Tune programı ile Bad Sector taraması yapın (Error Scan ile, Quick Scan olmayacak) ve sonuçları resim olarak paylaşın. Bir de HD Tune Health sekmesinin resmini atın.

Kod:
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except.
Typically the address is just plain bad or it is pointing at freed memory.
Arguments:
Arg1: ffffe000f7ff1010, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff801cb8bf0d3, If non-zero, the instruction address which referenced the bad memory
    address.
Arg4: 0000000000000002, (reserved)

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


Could not read faulting driver name

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2015

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on RED-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 46173

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  50

BUGCHECK_P1: ffffe000f7ff1010

BUGCHECK_P2: 0

BUGCHECK_P3: fffff801cb8bf0d3

BUGCHECK_P4: 2

READ_ADDRESS: fffff801cbaace60: Unable to get Flags value from nt!KdVersionBlock
fffff801cbaace60: Unable to get Flags value from nt!KdVersionBlock
fffff801cbaace60: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff801cbb69298
GetUlongPtrFromAddress: unable to read from fffff801cbb69520
fffff801cbaace60: Unable to get Flags value from nt!KdVersionBlock
ffffe000f7ff1010 Nonpaged pool

MM_INTERNAL_CODE:  2

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  IDMan.exe

TRAP_FRAME:  ffffd001bbb56f10 -- (.trap 0xffffd001bbb56f10)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=fffffa8003ccc870 rbx=0000000000000000 rcx=0000058000000000
rdx=fffff801cb806000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801cb8bf0d3 rsp=ffffd001bbb570a0 rbp=ffffc00079228c30
r8=0000000000000000  r9=00000000050b6f3e r10=0000000000000002
r11=ffffb000762b3d72 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
nt!MmCopyToCachedPage+0x183:
fffff801`cb8bf0d3 498b0424        mov     rax,qword ptr [r12] ds:00000000`00000000=????????????????
Resetting default scope

STACK_TEXT:
ffffd001`bbb56ca8 fffff801`cb984d65     : 00000000`00000050 ffffe000`f7ff1010 00000000`00000000 ffffd001`bbb56f10 : nt!KeBugCheckEx
ffffd001`bbb56cb0 fffff801`cb85e2b9     : 00000000`00000000 ffffe000`eaf6e500 ffffd001`bbb56f10 ffffb000`7a640000 : nt! ?? ::FNODOBFM::`string'+0x1deb5
ffffd001`bbb56d50 fffff801`cb960c2f     : 00000000`00000000 00000000`00000001 00000000`00000000 00000022`cb87ae70 : nt!MmAccessFault+0x769
ffffd001`bbb56f10 fffff801`cb8bf0d3     : 0000000f`ffffffff 000026d6`447e1ab0 fffffa80`009af650 ffffe000`f2882880 : nt!KiPageFault+0x12f
ffffd001`bbb570a0 fffff801`cb8beb4f     : 00000000`00000000 00000000`03ff3d72 00000000`03ff3000 ffffd001`bbb5744c : nt!MmCopyToCachedPage+0x183
ffffd001`bbb57410 fffff801`cb8f1120     : ffffe000`ea411d60 00000000`050b6f3e ffffd001`bbb57568 ffffe000`00000000 : nt!CcMapAndCopyInToCache+0x21f
ffffd001`bbb57500 fffff801`96141d7c     : 00000000`03ff42eb ffffe000`e8bfcdf0 ffffe000`eae4f8a0 ffffe000`e8bfcdf0 : nt!CcCopyWriteEx+0x260
ffffd001`bbb575a0 fffff801`95fa3061     : 00000000`000002b0 fffff801`cbbf3f95 ffff4ece`90018191 00000000`00000579 : Ntfs!NtfsCopyWriteA+0x2ed
ffffd001`bbb57820 fffff801`95fa37d6     : ffffd001`bbb57910 ffffe000`eae4f800 ffffe000`e8532cf0 ffffe000`e8532c00 : fltmgr!FltpPerformFastIoCall+0x1c1
ffffd001`bbb57880 fffff801`95fc9a4f     : 00000000`00000010 fffff801`cbc13544 ffffe000`00000010 ffffd001`bbb579e0 : fltmgr!FltpPassThroughFastIo+0x165
ffffd001`bbb578e0 fffff801`cbc13064     : ffffe000`eae4f8a0 00000000`00000000 ffffd001`bbb579d8 ffffd001`bbb57a40 : fltmgr!FltpFastIoWrite+0x14f
ffffd001`bbb57990 fffff801`cb9621b3     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtWriteFile+0x410
ffffd001`bbb57a90 00000000`773a2352     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`05c5ed88 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x773a2352


SYMBOL_NAME:  nt!MmCopyToCachedPage+183

MODULE_NAME: nt

IMAGE_VERSION:  6.3.9600.17415

STACK_COMMAND:  .thread ; .cxr ; kb

IMAGE_NAME:  ntkrnlmp.exe

BUCKET_ID_FUNC_OFFSET:  183

FAILURE_BUCKET_ID:  AV_nt!MmCopyToCachedPage

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {38463293-a177-b1cf-c39d-543c8a6c902d}

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffc00021d20899, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff803f0ddf9fb, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1546

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on RED-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 11646

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  a

BUGCHECK_P1: ffffc00021d20899

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff803f0ddf9fb

READ_ADDRESS: fffff803f0f30e60: Unable to get Flags value from nt!KdVersionBlock
fffff803f0f30e60: Unable to get Flags value from nt!KdVersionBlock
fffff803f0f30e60: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff803f0fed298
GetUlongPtrFromAddress: unable to read from fffff803f0fed520
fffff803f0f30e60: Unable to get Flags value from nt!KdVersionBlock
ffffc00021d20899 Paged pool

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

TRAP_FRAME:  ffffd00021d206e0 -- (.trap 0xffffd00021d206e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=ffffd00021d20830
rdx=0000000000007ff6 rsi=0000000000000000 rdi=0000000000000000
rip=fffff803f0ddf9fb rsp=ffffd00021d20870 rbp=ffffc00021d208f0
r8=0000000000000000  r9=00000000000000a8 r10=fffff803f0c8a000
r11=fffff78000000008 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up di ng nz na pe nc
nt!KiDpcInterrupt+0xcb:
fffff803`f0ddf9fb 0fb64da9        movzx   ecx,byte ptr [rbp-57h] ss:0018:ffffc000`21d20899=??
Resetting default scope

STACK_TEXT:
ffffd000`21d20598 fffff803`f0de64e9     : 00000000`0000000a ffffc000`21d20899 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`21d205a0 fffff803`f0de4d3a     : 00000000`00000000 00000000`00000000 00000000`00000000 ffffe001`ae558940 : nt!KiBugCheckDispatch+0x69
ffffd000`21d206e0 fffff803`f0ddf9fb     : 00000000`00000000 ffffd000`677310e0 ffffe001`ab2a6960 00000000`00000000 : nt!KiPageFault+0x23a
ffffd000`21d20870 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0xcb


SYMBOL_NAME:  nt!KiDpcInterrupt+cb

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  6.3.9600.17415

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  cb

FAILURE_BUCKET_ID:  AV_nt!KiDpcInterrupt

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {c1149c79-430d-0297-4e4e-d298390f725f}

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

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: ffffc0002456f720, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
    bit 0 : value 0 = read operation, 1 = write operation
    bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff80199a3692b, address which referenced memory

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1952

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on RED-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 13962

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  a

BUGCHECK_P1: ffffc0002456f720

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80199a3692b

READ_ADDRESS: fffff80199ca6e60: Unable to get Flags value from nt!KdVersionBlock
fffff80199ca6e60: Unable to get Flags value from nt!KdVersionBlock
fffff80199ca6e60: Unable to get Flags value from nt!KdVersionBlock
GetUlongPtrFromAddress: unable to read from fffff80199d63298
GetUlongPtrFromAddress: unable to read from fffff80199d63520
fffff80199ca6e60: Unable to get Flags value from nt!KdVersionBlock
ffffc0002456f720 Paged pool

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

TRAP_FRAME:  ffffd0002456ef80 -- (.trap 0xffffd0002456ef80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffd0002456f720 rbx=0000000000000000 rcx=ffffc0002456f720
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80199a3692b rsp=ffffd0002456f110 rbp=0000000000000000
r8=0000000000000000  r9=0000000000000000 r10=ffffc0002456f720
r11=ffffd0002456f338 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po cy
nt!KeSetEvent+0x3fb:
fffff801`99a3692b 488b09          mov     rcx,qword ptr [rcx] ds:ffffc000`2456f720=????????????????
Resetting default scope

STACK_TEXT:
ffffd000`2456ee38 fffff801`99b5c4e9     : 00000000`0000000a ffffc000`2456f720 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffd000`2456ee40 fffff801`99b5ad3a     : 00000000`00000000 ffffd000`2456f718 ffffd000`2456f000 fffff800`f227fcf2 : nt!KiBugCheckDispatch+0x69
ffffd000`2456ef80 fffff801`99a3692b     : ffffe001`160b8770 fffff800`f28e6f29 ffffe001`18f5f940 ffffe001`160b88c0 : nt!KiPageFault+0x23a
ffffd000`2456f110 fffff800`f24a838a     : ffffc000`2456f720 ffffe001`00000000 00000000`00000000 ffffe001`00000000 : nt!KeSetEvent+0x3fb
ffffd000`2456f1d0 fffff801`99a38bea     : 00000001`00000001 ffffe001`18f5f940 ffffd000`2456f300 00000000`00000000 : Ntfs!NtfsFlushDiskCacheCompletionRoutine+0x12
ffffd000`2456f200 fffff800`f2203f53     : ffffe001`161b6800 ffffbfbd`9f86ca00 ffffe001`15186800 fffff801`99cb2300 : nt!IopfCompleteRequest+0x2ea
ffffd000`2456f340 fffff800`f221738e     : ffff80c2`7ac02b56 00000000`00000000 00000000`00000000 00000000`00000000 : storport!RaidCompleteRequestEx+0x53
ffffd000`2456f410 fffff800`f2202415     : fffff800`f28d1010 00000000`00000000 00000000`00000000 00000000`00000001 : storport!RaUnitScsiIrp+0x15bae
ffffd000`2456f560 fffff800`f28c9458     : ffffe001`160b8ea8 ffffe001`160b8770 ffffe001`160b8e78 00000000`00000000 : storport!RaDriverScsiIrp+0x55
ffffd000`2456f5a0 fffff800`f28c91ad     : ffffe001`160b8d80 ffffe001`160b8770 ffffe001`160b8f60 00000000`00000009 : disk!DiskFlushDispatch+0x128
ffffd000`2456f600 fffff800`f28e6d8d     : 00000000`00000006 ffffc000`78a4bfc0 ffffe001`18f5f940 ffffe001`18f5f940 : disk!DiskShutdownFlush+0xcd
ffffd000`2456f670 fffff800`f23453c8     : ffffe001`161cca30 ffffd000`2456f6f8 ffffe001`161cca30 00000000`00000000 : CLASSPNP!ClassShutdownFlush+0x39
ffffd000`2456f6a0 fffff800`f24a831d     : ffffd000`2456fa61 ffffc000`78a4bfc0 ffffe001`18f5f940 ffffe001`1574a6f0 : volmgr!VmFlushBuffers+0x138
ffffd000`2456f6e0 fffff800`f24a6778     : ffffe001`18f5f940 00000000`1968d73b 00000000`00000000 ffffc000`78a4bf00 : Ntfs!NtfsFlushDiskCache+0xad
ffffd000`2456f740 fffff800`f254541f     : ffffc000`78a4bfc0 00000000`196b3356 ffffd000`2456fa01 00000000`00000000 : Ntfs!LfsFlushDiskCache+0x120
ffffd000`2456f820 fffff801`99aee4ac     : ffffc000`78a4bfc0 00000000`196b3356 7fffffff`ffffffff 7fffffff`ffffffff : Ntfs!LfsFlushToLsn+0x10b
ffffd000`2456f880 fffff801`99a4fbf3     : ffffe001`16817bb0 00000000`00000000 00000000`00000000 ffffd000`2456faf8 : nt!CcAcquireByteRangeForWrite+0x850
ffffd000`2456f9b0 fffff801`99a5042b     : ffffe001`15693b70 00000000`00000000 ffffe001`00000001 ffffd000`2456faf8 : nt!CcFlushCachePriv+0x37b
ffffd000`2456fac0 fffff801`99a9c38c     : ffffe001`168a4c40 ffffe001`15186801 ffffe001`00000000 00000000`000441e4 : nt!CcWriteBehindInternal+0x17b
ffffd000`2456fb50 fffff801`99b01c70     : 00000000`00000000 ffffe001`15186700 00000000`00000080 ffffe001`15186700 : nt!ExpWorkerThread+0x28c
ffffd000`2456fc00 fffff801`99b56fc6     : ffffd001`a8940180 ffffe001`15186700 ffffe001`181c8880 fffff960`000fe544 : nt!PspSystemThreadStartup+0x58
ffffd000`2456fc60 00000000`00000000     : ffffd000`24570000 ffffd000`2456a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


SYMBOL_NAME:  disk!DiskFlushDispatch+128

MODULE_NAME: disk

IMAGE_NAME:  disk.sys

IMAGE_VERSION:  6.3.9600.16384

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  128

FAILURE_BUCKET_ID:  AV_disk!DiskFlushDispatch

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {3fe0836c-c708-98ef-41cf-eeab3ff35f71}

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

MEMORY_MANAGEMENT (1a)
    # Any other values for parameter 1 must be individually examined.
Arguments:
Arg1: 0000000000041284, A PTE or the working set list is corrupt.
Arg2: 00001af21c864000
Arg3: 0000000000003e90
Arg4: fffff58010804000

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1858

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on RED-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 21149

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  1a

BUGCHECK_P1: 41284

BUGCHECK_P2: 1af21c864000

BUGCHECK_P3: 3e90

BUGCHECK_P4: fffff58010804000

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  chrome.exe

STACK_TEXT:
ffffd000`252675b8 fffff802`039f443d     : 00000000`0000001a 00000000`00041284 00001af2`1c864000 00000000`00003e90 : nt!KeBugCheckEx
ffffd000`252675c0 fffff802`038dc728     : e9000001`c17a7867 ffffd000`25267710 fffff68d`790e4320 fffff580`10804000 : nt! ?? ::FNODOBFM::`string'+0x1658d
ffffd000`25267610 fffff802`0394075a     : ffffe001`f46c0340 00000000`00000001 00000000`00000000 ffffe001`00000005 : nt!MiDeleteVirtualAddresses+0x558
ffffd000`252678a0 fffff802`0393f5e9     : ffffe001`f0fa9870 00000000`00000010 ffffe001`00000000 00000000`00000000 : nt!MiDeleteVad+0xbca
ffffd000`252679a0 fffff802`039d91b3     : 00000000`00000001 00000000`00502cf8 00000000`00000001 ffffe001`f4457df0 : nt!NtFreeVirtualMemory+0x879
ffffd000`25267b00 00007ffe`a3e50e2a     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000009a`7b00e6b8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffe`a3e50e2a


SYMBOL_NAME:  nt! ?? ::FNODOBFM::`string'+1658d

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  6.3.9600.17415

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  1658d

FAILURE_BUCKET_ID:  0x1a_41284_nt!_??_::FNODOBFM::_string_

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {c39d115f-eaa3-aeb6-09bd-1a63e83e1077}

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

CRITICAL_STRUCTURE_CORRUPTION (109)
This bugcheck is generated when the kernel detects that critical kernel code or
data have been corrupted. There are generally three causes for a corruption:
1) A driver has inadvertently or deliberately modified critical kernel code
or data. See http://www.microsoft.com/whdc/driver/kernel/64bitPatching.mspx
2) A developer attempted to set a normal kernel breakpoint using a kernel
debugger that was not attached when the system was booted. Normal breakpoints,
"bp", can only be set if the debugger is attached at boot time. Hardware
breakpoints, "ba", can be set at any time.
3) A hardware corruption occurred, e.g. failing RAM holding kernel code or data.
Arguments:
Arg1: a3a01f5928ed053b, Reserved
Arg2: 0000000000000000, Reserved
Arg3: 52f8bcb1b86866dc, Failure type dependent information
Arg4: 0000000000000101, Type of corrupted region, can be
    0   : A generic data region
    1   : Modification of a function or .pdata
    2   : A processor IDT
    3   : A processor GDT
    4   : Type 1 process list corruption
    5   : Type 2 process list corruption
    6   : Debug routine modification
    7   : Critical MSR modification
    8   : Object type
    9   : A processor IVT
    a   : Modification of a system service function
    b   : A generic session data region
    c   : Modification of a session function or .pdata
    d   : Modification of an import table
    e   : Modification of a session import table
    f   : Ps Win32 callout modification
    10  : Debug switch routine modification
    11  : IRP allocator modification
    12  : Driver call dispatcher modification
    13  : IRP completion dispatcher modification
    14  : IRP deallocator modification
    15  : A processor control register
    16  : Critical floating point control register modification
    17  : Local APIC modification
    18  : Kernel notification callout modification
    19  : Loaded module list modification
    1a  : Type 3 process list corruption
    1b  : Type 4 process list corruption
    1c  : Driver object corruption
    1d  : Executive callback object modification
    1e  : Modification of module padding
    1f  : Modification of a protected process
    20  : A generic data region
    21  : A page hash mismatch
    22  : A session page hash mismatch
    23  : Load config directory modification
    24  : Inverted function table modification
    25  : Session configuration modification
    26  : An extended processor control register
    27  : Type 1 pool corruption
    28  : Type 2 pool corruption
    29  : Type 3 pool corruption
    2a  : Type 4 pool corruption
    2b  : Modification of a function or .pdata
    2c  : Image integrity corruption
    2d  : Processor misconfiguration
    2e  : Type 5 process list corruption
    2f  : Process shadow corruption
    30  : Retpoline code page corruption
    101 : General pool corruption
    102 : Modification of win32k.sys

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


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2280

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on RED-PC

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 8772

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: winblue_r4

    Key  : WER.OS.Timestamp
    Value: 2014-10-28T15:00:00Z

    Key  : WER.OS.Version
    Value: 8.1.9600.17415


ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  109

BUGCHECK_P1: a3a01f5928ed053b

BUGCHECK_P2: 0

BUGCHECK_P3: 52f8bcb1b86866dc

BUGCHECK_P4: 101

MEMORY_CORRUPTOR:  ONE_BIT

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:
ffffd001`165c6088 00000000`00000000     : 00000000`00000109 a3a01f59`28ed053b 00000000`00000000 52f8bcb1`b86866dc : nt!KeBugCheckEx


SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

STACK_COMMAND:  .thread ; .cxr ; kb

FAILURE_BUCKET_ID:  MEMORY_CORRUPTION_ONE_BIT

OS_VERSION:  8.1.9600.17415

BUILDLAB_STR:  winblue_r4

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 8.1

FAILURE_ID_HASH:  {e3faf315-c3d0-81db-819a-6c43d23c63a7}

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


bad sector dediğiniz burası mı oluyor ?
1597860972043.png
 
Evet, Bad Sector taraması orası oluyor. Test bitince resim paylaşın fakat Memtest86 testini de unutmayın. Çünkü sorunun RAM kaynaklı olma ihtimali de yüksek.

Sanırım RAM kaynaklı benim Bilgisayarım da 2 tane RAM var hangisinin bozuk olduğunu nasıl anlayacağım ?
 

Dosya Ekleri

  • asf.PNG
    asf.PNG
    13,3 KB · Görüntüleme: 67
  • IMG_20200819_233919_001.jpg
    IMG_20200819_233919_001.jpg
    240,2 KB · Görüntüleme: 56
  • IMG_20200819_233950_760.jpg
    IMG_20200819_233950_760.jpg
    238,8 KB · Görüntüleme: 63
Sanırım RAM kaynaklı benim Bilgisayarım da 2 tane RAM var hangisinin bozuk olduğunu nasıl anlayacağım ?
Tahminim doğru çıktı, RAM arızalı. Hangisinin bozuk olduğunu anlamak için önce iki RAM'i de söküp RAM'lerin bakır iletken kısımlarını silgi ile (normal okul silgisi) silin. Sonra ise ilk olarak tek RAM takıp test yapın. Testte hata çıkarsa o zaman o RAM bozuktur diyebiliriz. Fakat deneme amaçlı bir başka slotta da deneyin. Belki de slot arızalı olabilir. Eğer yine hata çıkarsa o zaman o RAM bozuktur. Eğer her iki slotta da hata çıkmazsa o RAM sağlamdır, kenara ayırın. Sonra aynı işlemi ikinci RAM ile tekrarlayın. Eğer bir slotta hata çıkıp diğerinde çıkmıyorsa slotta sorun vardır. Fakat her iki slotta da hata çıkıyorsa RAM bozuktur.

Eğer uğraşmak istemiyorsanız bilgisayarınızı teknik alanda deneyimli bir bilgisayarcıya (yani bakkal olmayanlara) gönderebilirsiniz. Onlar bu işlemi kendileri yapacaklardır.
 
Tahminim doğru çıktı, RAM arızalı. Hangisinin bozuk olduğunu anlamak için önce iki RAM'i de söküp RAM'lerin bakır iletken kısımlarını silgi ile (normal okul silgisi) silin. Sonra ise ilk olarak tek RAM takıp test yapın. Testte hata çıkarsa o zaman o RAM bozuktur diyebiliriz. Fakat deneme amaçlı bir başka slotta da deneyin. Belki de slot arızalı olabilir. Eğer yine hata çıkarsa o zaman o RAM bozuktur. Eğer her iki slotta da hata çıkmazsa o RAM sağlamdır, kenara ayırın. Sonra aynı işlemi ikinci RAM ile tekrarlayın. Eğer bir slotta hata çıkıp diğerinde çıkmıyorsa slotta sorun vardır. Fakat her iki slotta da hata çıkıyorsa RAM bozuktur.

Eğer uğraşmak istemiyorsanız bilgisayarınızı teknik alanda deneyimli bir bilgisayarcıya (yani bakkal olmayanlara) gönderebilirsiniz. Onlar bu işlemi kendileri yapacaklardır.

Yaptığım testler sonucunda sadece 1 RAM'ın bozulduğunu anladım tek RAM ile bilgisayarımı sorunsuz kullanıyorum en kısa zamanda yeni bir RAM alacağım ilgilendiğiniz için teşekkür ederim.
 
Uyarı! Bu konu 6 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.

Technopat Haberler

Yeni konular

Geri
Yukarı